<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Segoe UI","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
p.Textedebulles, li.Textedebulles, div.Textedebulles
{mso-style-name:"Texte de bulles";
mso-style-link:"Texte de bulles Car";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#002060;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#002060;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#002060;}
span.EmailStyle31
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If it’s common practice </span><span style="color:#002060">for the specs posted at openid.net/specs/ to include a version number as a stable identifier for a particular spec version, then I agree that all WGs
should follow this practice to create consistence among the WGs. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">BR,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">Bjorn</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Openid-specs-mobile-profile [mailto:openid-specs-mobile-profile-bounces@lists.openid.net]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Monday, March 06, 2017 11:41 AM<br>
<b>To:</b> Hjelm, Bjorn<br>
<b>Cc:</b> openid-specs-mobile-profile@lists.openid.net<br>
<b>Subject:</b> [E] Re: [Openid-specs-mobile-profile] Proposed schedule for Implementer's Draft vote - version numbers<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#002060">One more set of questions about the specs, aimed at consistency both with the other OpenID Connect specs and internal consistency within the MODRNA specs. First, despite James’s comments about the spec version
number, it’s common practice for the specs posted at openid.net/specs/ to include a version number as a stable identifier for a particular spec version. Thus, I plan to include the version numbers for the point-in-time specs, as well as posting them without
version numbers. The one without a version number will change over time as new versions are posted.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">Second, all the MODRNA specs except for account porting include “1.0” in the spec title, which is common practice for OpenID specs (even those pre-dating OpenID Connect!). Unless the working group objects, for
consistency reasons, I plan to add “1.0” to the account porting spec title and pathname.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">In summary, these are the pathnames I plan to use for the specifications unless I hear objections:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-modrna-authentication-1_0-06.html (stable version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-modrna-authentication-1_0.html (current version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-account-porting-1_0-07.html (stable version)<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#002060"> openid-connect-account-porting-1_0.html (current version)<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-user-questioning-api-1_0-10.html (stable version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-user-questioning-api-1_0.html (current version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-modrna-client-initiated-backchannel-authentication-1_0-03.html (stable version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> openid-connect-modrna-client-initiated-backchannel-authentication-1_0.html (current version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">I will proceed on this basis after an ack from the chair and/or spec authors and start the 45-day Implementer’s Draft review period.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> -- Mike (writing as OpenID Foundation secretary)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Manger, James [<a href="mailto:James.H.Manger@team.telstra.com">mailto:James.H.Manger@team.telstra.com</a>]
<br>
<b>Sent:</b> Sunday, March 5, 2017 4:19 PM<br>
<b>To:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>><br>
<b>Cc:</b> <a href="mailto:openid-specs-mobile-profile@lists.openid.net">openid-specs-mobile-profile@lists.openid.net</a><br>
<b>Subject:</b> RE: [Openid-specs-mobile-profile] Proposed schedule for Implementer's Draft vote - version numbers<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">draft-account-porting → openid-connect-account-porting is ok. I guess we should make this change in the repo as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">But adding -06 to the file name is a poor idea.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">“-06” is really only an approximate internal-to-working-group hint about when it is worth reviewing a draft again. We deliberately removed -0x from file names in the Bitbucket repo. It prevented
having links that pointed to the latest draft (which is what you almost always want). It caused mismatches with repo commits (which already provides a separate versioning scheme).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">All the current Final Specs and Implementer’s Drafts and some of the Drafts at
<a href="http://openid.net/developers/specs/">http://openid.net/developers/specs/</a> have “-1_0” in their file name. Some have “1.0” in their title, but not all. Fewer have “1.0” in the label that links to the spec. This is a spec version, not a draft number.
The Drafts are a mixed bag: some mention a 1.0 version, a couple mention draft numbers.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">My personal preference is to omit a “1.0” version number. If there is ever an alternative approach that can introduce “v2” in its title.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">For the account porting spec, I would suggest:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"> Label (on web pages listing specs): “OpenID Connect Account Porting”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"> Title (in spec): “OpenID Connect Account Porting — draft 06”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"> File: openid-connect-account-porting.html<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">Plus a link to the Bitbucket repo if you want the full history, diffs etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">I wonder if repo tags would be helpful in marking revisions that we want to remember (eg proposed & approved implementer’s draft, final spec, and spec with errata)?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">--<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">James Manger<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Mike Jones [<a href="mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsoft.com</a>]
<br>
<b>Sent:</b> Saturday, 4 March 2017 6:43 AM<br>
<b>To:</b> Manger, James <<a href="mailto:James.H.Manger@team.telstra.com">James.H.Manger@team.telstra.com</a>><br>
<b>Cc:</b> <a href="mailto:openid-specs-mobile-profile@lists.openid.net">openid-specs-mobile-profile@lists.openid.net</a><br>
<b>Subject:</b> RE: [Openid-specs-mobile-profile] Proposed schedule for Implementer's Draft vote<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-AU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">Got ‘em – thanks. The one thing I will do to avoid future naming conflicts is rename all the pathname occurrences of “draft-account-porting” to “draft-account-porting-06” before posting. I realize that this
means that I’ll have to edit the path to the .png file in the document.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Manger, James [<a href="mailto:James.H.Manger@team.telstra.com">mailto:James.H.Manger@team.telstra.com</a>]
<br>
<b>Sent:</b> Friday, March 3, 2017 3:44 AM<br>
<b>To:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>><br>
<b>Cc:</b> <a href="mailto:openid-specs-mobile-profile@lists.openid.net">openid-specs-mobile-profile@lists.openid.net</a><br>
<b>Subject:</b> RE: [Openid-specs-mobile-profile] Proposed schedule for Implementer's Draft vote<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">Hi Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">The Implementer’s Draft version of OpenID Connect Account Porting.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">In repo:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><a href="https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.xml">https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.xml</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><a href="https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.html">https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><a href="https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.eg.png">https://bitbucket.org/openid/mobile/src/a5de40ec3b19227b002846a1d5d8ca5581b5c917/draft-account-porting.eg.png</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">The draft has a *.png image in an appendix. I’m not sure how (or if) this works with the process.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">--<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="color:#1F497D">James Manger<o:p></o:p></span></p>
</div>
</body>
</html>