Actually, back in Nov. 2010, a new URL syntax was decided to be: <div><br></div><div><a href="http://openid.net/specs/">http://openid.net/specs/</a><spec_abbrv>/<spec_ver>/#<feature></div><div><br></div><div>
See <a href="http://lists.openid.net/pipermail/openid-specs/2010-November/007303.html">http://lists.openid.net/pipermail/openid-specs/2010-November/007303.html</a><br><br><div class="gmail_quote">I am just asking about the syntax for <spec_abbrv>. </div>
<div class="gmail_quote">Let us make the <spec_abbrv> syntax a topic of the next call. </div><div class="gmail_quote"><br></div><div class="gmail_quote">Best, </div><div class="gmail_quote"><br></div><div class="gmail_quote">
=nat</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Fri, Jul 8, 2011 at 7:24 PM, Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;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" target="_blank">http://openid.net/specs/openid-connect-core-1_0.html</a> and
<a href="http://openid.net/specs/openid-connect-core-1_0.txt" target="_blank">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/" target="_blank">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"> Best wishes,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"><u></u> <u></u></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">From:</span></b><span style="font-size:10.0pt"> sakimura [mailto:<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>]
<br>
<b>Sent:</b> Friday, July 08, 2011 2:26 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> RE: [Openid-specs-ab] Spec URL<u></u><u></u></span></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<pre>I think it will be "<a href="http://openid.net/specs/connect/1.0/#issuer" target="_blank">http://openid.net/specs/connect/1.0/#issuer</a>" instead of "<a href="http://openid.net/specs/connect/1.0/issuer" target="_blank">http://openid.net/specs/connect/1.0/issuer</a>". <u></u><u></u></pre>
<pre>By doing so, clicking on the link will make the browser jump to the intended section. <u></u><u></u></pre>
<pre><u></u> <u></u></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. <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>So even if we are not using "<a href="http://openid.net/specs/connect-userinfo/1.0/" target="_blank">http://openid.net/specs/connect-userinfo/1.0/</a>" in the protocol, we need to decide on it. <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>Do we have consensus on using "-" as the delimiter for the sub-specs and bindings? Or do we want "/"? <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>By the way, most referenced URL will be that of HTTP Redirect Binding. Is it OK to be <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre> <a href="http://openid.net/specs/connect-http-redirect-binding/1.0/" target="_blank">http://openid.net/specs/connect-http-redirect-binding/1.0/</a> <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>or do we want it to be<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre> <a href="http://openid.net/specs/connect/http-redirect-binding/1.0/" target="_blank">http://openid.net/specs/connect/http-redirect-binding/1.0/</a> ? <u></u><u></u></pre>
<pre><u></u> <u></u></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. <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>=nat<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>On Fri, 8 Jul 2011 08:58:04 +0000, Mike Jones wrote:<u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0/" target="_blank">http://openid.net/specs/connect/1.0/</a> works for me (and then we can<u></u><u></u></pre>
<pre>> have URIs like <a href="http://openid.net/specs/connect/1.0/issuer" target="_blank">http://openid.net/specs/connect/1.0/issuer</a> as well).<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> I don't see a reason to have URIs for the related specs, other than<u></u><u></u></pre>
<pre>> perhaps on a case-by-case basis. But if we do need them, they should<u></u><u></u></pre>
<pre>> probably be as you suggest below in option 1.<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> -- Mike<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> -----Original Message-----<u></u><u></u></pre>
<pre>> From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a><u></u><u></u></pre>
<pre>> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of<u></u><u></u></pre>
<pre>> sakimura<u></u><u></u></pre>
<pre>> Sent: Friday, July 08, 2011 1:34 AM<u></u><u></u></pre>
<pre>> To: <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre>> Subject: [Openid-specs-ab] Spec URL<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> On Monday call, we agreed to use<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0" target="_blank">http://openid.net/specs/connect/1.0</a><u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> as the spec identifier URL for the core.<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> On the hind site, this may not be optimal. At the very least, we <u></u><u></u></pre>
<pre>> probably want to put the traling slash "/".<u></u><u></u></pre>
<pre>> Otherwise, we would not be able to make that a publishing point for <u></u><u></u></pre>
<pre>> multiple representation of the same spec unless we do something<u></u><u></u></pre>
<pre>> creative with mod_rewrite. I would rather use Apache's default<u></u><u></u></pre>
<pre>> content negotiation capability.<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> We also have to decide on the URL for all the other companion specs. <u></u><u></u></pre>
<pre>> Would they be something like:<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect-userinfo/1.0/" target="_blank">http://openid.net/specs/connect-userinfo/1.0/</a><u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect-framework/1.0/" target="_blank">http://openid.net/specs/connect-framework/1.0/</a><u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> etc.?<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> In that case, would it be more appropriate to make the core like below?<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect-core/1.0/" target="_blank">http://openid.net/specs/connect-core/1.0/</a><u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> Other option (Option 2) is like:<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect/core/1.0/" target="_blank">http://openid.net/specs/connect/core/1.0/</a><u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect/userinfo/1.0/" target="_blank">http://openid.net/specs/connect/userinfo/1.0/</a><u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> etc. for the individual specs, and<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <a href="http://openid.net/specs/connect/1.0/" target="_blank">http://openid.net/specs/connect/1.0/</a><u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> for the "Index" page giving the list of all of the sub-specs.<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> I am fine either-way, but Option 2 seems a little more attractive in<u></u><u></u></pre>
<pre>> the sense that it has grouping notion embodied.<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> Thoughts?<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> =nat<u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> <u></u><u></u></pre>
<pre>> _______________________________________________<u></u><u></u></pre>
<pre>> Openid-specs-ab mailing list<u></u><u></u></pre>
<pre>> <a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><u></u><u></u></pre>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>
</div>