<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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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","serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#002060;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">If we follow existing OpenID conventions, the specs will be located at URLs like
<a href="http://openid.net/specs/openid-connect-core-1_0.html">http://openid.net/specs/openid-connect-core-1_0.html</a> and
<a href="http://openid.net/specs/openid-connect-core-1_0.txt">http://openid.net/specs/openid-connect-core-1_0.txt</a> - just like they are now. The spec location URLs are arguably completely separate from the URIs in the specs used to identify logical entities.
In particular, while <a href="http://openid.net/specs/connect/1.0/">http://openid.net/specs/connect/1.0/</a> is a perfectly good URI, I don’t expect there to be any document at that URL. For that reason also, changing to “#issuer” rather than “issuer” seems
like it’s overly complicating the issuer URI.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">Unless you agree, I suspect this whole issue will be more productively resolved on the next spec call, rather than in e-mail. Until then, let’s leave the URIs
in the specs and URLs of the spec locations as they are.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><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""> sakimura [mailto:sakimura@gmail.com]
<br>
<b>Sent:</b> Friday, July 08, 2011 2:26 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> RE: [Openid-specs-ab] Spec URL<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<pre>I think it will be "<a href="http://openid.net/specs/connect/1.0/#issuer">http://openid.net/specs/connect/1.0/#issuer</a>" instead of "<a href="http://openid.net/specs/connect/1.0/issuer">http://openid.net/specs/connect/1.0/issuer</a>". <o:p></o:p></pre>
<pre>By doing so, clicking on the link will make the browser jump to the intended section. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The reason I raised this issue is because it is very closely related to the spec publishing point which enables the above behavior, which we would be doing in next couple of days. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>So even if we are not using "<a href="http://openid.net/specs/connect-userinfo/1.0/">http://openid.net/specs/connect-userinfo/1.0/</a>" in the protocol, we need to decide on it. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Do we have consensus on using "-" as the delimiter for the sub-specs and bindings? Or do we want "/"? <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>By the way, most referenced URL will be that of HTTP Redirect Binding. Is it OK to be <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <a href="http://openid.net/specs/connect-http-redirect-binding/1.0/">http://openid.net/specs/connect-http-redirect-binding/1.0/</a> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>or do we want it to be<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <a href="http://openid.net/specs/connect/http-redirect-binding/1.0/">http://openid.net/specs/connect/http-redirect-binding/1.0/</a> ? <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Now that I have encountered with this example, it just occurs to me now that the later seems to be more consistent in the sense that "/" represents the hierarchic relationship and "-" is just a replacement for a space, but I can live either way. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>=nat<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Fri, 8 Jul 2011 08:58:04 +0000, Mike Jones wrote:<o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0/">http://openid.net/specs/connect/1.0/</a> works for me (and then we can<o:p></o:p></pre>
<pre>> have URIs like <a href="http://openid.net/specs/connect/1.0/issuer">http://openid.net/specs/connect/1.0/issuer</a> as well).<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> I don't see a reason to have URIs for the related specs, other than<o:p></o:p></pre>
<pre>> perhaps on a case-by-case basis. But if we do need them, they should<o:p></o:p></pre>
<pre>> probably be as you suggest below in option 1.<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> -- Mike<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> -----Original Message-----<o:p></o:p></pre>
<pre>> From: openid-specs-ab-bounces@lists.openid.net<o:p></o:p></pre>
<pre>> [mailto:openid-specs-ab-bounces@lists.openid.net] On Behalf Of<o:p></o:p></pre>
<pre>> sakimura<o:p></o:p></pre>
<pre>> Sent: Friday, July 08, 2011 1:34 AM<o:p></o:p></pre>
<pre>> To: openid-specs-ab@lists.openid.net<o:p></o:p></pre>
<pre>> Subject: [Openid-specs-ab] Spec URL<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> On Monday call, we agreed to use<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0">http://openid.net/specs/connect/1.0</a><o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> as the spec identifier URL for the core.<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> On the hind site, this may not be optimal. At the very least, we <o:p></o:p></pre>
<pre>> probably want to put the traling slash "/".<o:p></o:p></pre>
<pre>> Otherwise, we would not be able to make that a publishing point for <o:p></o:p></pre>
<pre>> multiple representation of the same spec unless we do something<o:p></o:p></pre>
<pre>> creative with mod_rewrite. I would rather use Apache's default<o:p></o:p></pre>
<pre>> content negotiation capability.<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> We also have to decide on the URL for all the other companion specs. <o:p></o:p></pre>
<pre>> Would they be something like:<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect-userinfo/1.0/">http://openid.net/specs/connect-userinfo/1.0/</a><o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect-framework/1.0/">http://openid.net/specs/connect-framework/1.0/</a><o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> etc.?<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> In that case, would it be more appropriate to make the core like below?<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect-core/1.0/">http://openid.net/specs/connect-core/1.0/</a><o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> Other option (Option 2) is like:<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect/core/1.0/">http://openid.net/specs/connect/core/1.0/</a><o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect/userinfo/1.0/">http://openid.net/specs/connect/userinfo/1.0/</a><o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> etc. for the individual specs, and<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0/">http://openid.net/specs/connect/1.0/</a><o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> for the "Index" page giving the list of all of the sub-specs.<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> I am fine either-way, but Option 2 seems a little more attractive in<o:p></o:p></pre>
<pre>> the sense that it has grouping notion embodied.<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> Thoughts?<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> =nat<o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> <o:p></o:p></pre>
<pre>> _______________________________________________<o:p></o:p></pre>
<pre>> Openid-specs-ab mailing list<o:p></o:p></pre>
<pre>> <a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><o:p></o:p></pre>
<pre>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><o:p></o:p></pre>
</div>
</body>
</html>