[Openid-specs-igov] Draft vote

[John Bradley]

Working on the updates.

On Tue, Oct 2, 2018, 4:13 PM Mike Jones <Michael.Jones at microsoft.com> wrote:

> Wearing my secretary hat, a few things need to be cleaned up in these
> drafts before I can post them to openid.net/specs/.
>
>
>
> First, the draft numbers somehow regressed to Draft 01.  The current
> drafts posted at openid.net/specs/ are both Draft 02, per:
>
>    - http://openid.net/specs/openid-igov-oauth2-1_0.html
>    - http://openid.net/specs/openid-igov-openid-connect-1_0.html
>
> The draft numbers in the specification source and outputs need to be
> updated to Draft 03 – or whatever greater draft number is actually correct.
>
>
>
> Next, the pathnames in the drafts and of the files are wrong.  They should
> be updated as follows:
>
>    - openid-igov-oauth2 -> openid-igov-oauth2-1_0
>    - openid-igov-profile -> openid-igov-openid-connect-1_0
>
> Please rename the sources and outputs in the bitbucket repository in this
> way as well, to prevent recurrences of this confusion.
>
>
>
> The versions to be posted will not include the “-id1” suffix.  That’s
> something that’s added after an Implementer’s Draft is approved.  (Versions
> will be posted with the -03 (or whatever the actual draft numbers are)
> suffix and with no suffix.)  When you check things in, please just check in
> versions with no suffixes.  I’ll add the suffixes at posting time.
>
>
>
> The reference to [iGov.OAuth2] in the Connect profile should point to
> http://openid.net/specs/openid-igov-oauth2-1_0.html - not the xml2rfc
> path that’s presently there.
>
>
>
> The date on the [HEART.OAuth2] reference is incorrect.  You should
> likewise check all the other referenced spec dates and have them be current.
>
>
>
> When you edit the XML sources to correct the draft numbers and spec paths,
> please also update the spec dates to the current date in October.
>
>
>
>                                                                 Thanks,
>
>                                                                 -- Mike
>
>
>
> *From:* Openid-specs-igov <openid-specs-igov-bounces at lists.openid.net> *On
> Behalf Of *Paul Grassi via Openid-specs-igov
> *Sent:* Monday, October 1, 2018 7:23 PM
> *To:* John Bradley <ve7jtb at ve7jtb.com>; openid-specs-igov at lists.openid.net
> *Subject:* Re: [Openid-specs-igov] Draft vote
>
>
>
> Thanks John,
>
> Bjorn and I talked and we will start use cases for attribute metadata.
> It’s coming up more and more as a value add to assertions/claims in
> multiple sectors.
>
>
>
> Paul
>
>
>
> *From: *Openid-specs-igov <openid-specs-igov-bounces at lists.openid.net> on
> behalf of John Bradley via Openid-specs-igov <
> openid-specs-igov at lists.openid.net>
> *Reply-To: *John Bradley <ve7jtb at ve7jtb.com>
> *Date: *Monday, October 1, 2018 at 9:37 PM
> *To: *"openid-specs-igov at lists.openid.net" <
> openid-specs-igov at lists.openid.net>
> *Subject: *Re: [Openid-specs-igov] Draft vote
>
>
>
> The Candidate implementers drafts are linked from
> https://openid.net/wg/igov/
>
> I am working on getting the official announcement.
>
> John B.
>
> On 10/1/2018 3:20 PM, Paul Grassi via Openid-specs-igov wrote:
>
> Can we get this to draft vote before the workshop. I am not claiming that
> I am any more important than anyone spending time and money to get to the
> valley, but I seriously doubt the value prop for me to go if my update is
> “we’ve been waiting to initiate a vote for 3 months.”
>
>
>
>
>
>
>
> _______________________________________________
>
> Openid-specs-igov mailing list
>
> Openid-specs-igov at lists.openid.net
>
> http://lists.openid.net/mailman/listinfo/openid-specs-igov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-igov/attachments/20181002/c055f475/attachment.html>