<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Will the frag reference still work with the extra / <div><br></div><div>John B.<br><div><div>On 2010-11-17, at 12:03 PM, Nat Sakimura wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Actually, I should have written as: <div><br></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">/<spec_abbrv>/<spec_ver>/#<feature></span></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">but that is a minor issue, I think. (An extra "/" is there, which is kind of important when we think of the server implementations.) </span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">So, what would be the process to formalize it? </span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Do we just announce it as the specs council or something? </span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">=nat<br></span></font><br><div class="gmail_quote">On Wed, Nov 17, 2010 at 11:07 PM, John Bradley <span dir="ltr"><<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">I think that works.<div><br></div><div>It is always nice to have them dereference-able. </div>
<div><br></div><div>The fragment allows for a single document.</div><div><br></div><div>John B.<div><div></div><div class="h5"><br><div><div>On 2010-11-17, at 5:23 AM, Nat Sakimura wrote:</div><br><blockquote type="cite">
Actually, <div><br></div><div> /<spec_abbrv>/<spec_ver>#<feature></div><div><br></div><div>is quite nice in the sense that it should jump to the location in the spec document that describes the feature. </div>
<div><br></div><div>=nat<br><br><div class="gmail_quote">On Wed, Nov 17, 2010 at 5:12 PM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com" target="_blank">recordond@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sure, seems sane. As John points out some specs may define multiple URLs in which case the format of /<spec_name>/<spec_version>/<feature> seems reasonable.<br><br><div><br><div class="gmail_quote"><div>
<div></div><div>On Tue, Nov 16, 2010 at 2:44 PM, John Bradley <span dir="ltr"><<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><div style="word-wrap:break-word">We also have URI in use like <span style="font-family:verdana, charcoal, helvetica, arial, sans-serif;font-size:small"><a href="http://specs.openid.net/auth/2.0/server" target="_blank">http://specs.openid.net/auth/2.0/server</a> etc.</span><div>
<font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small"><br></span></font></div><div><font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small">I agree with managing the namespace for each spec in a more consistent way.</span></font></div>
<div><font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small"><br></span></font></div><div><font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small">John B.<br>
</span></font><div><div></div><div><div><font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small"><br></span></font></div><div><font face="verdana, charcoal, helvetica, arial, sans-serif"><span style="font-size:small"><br>
</span></font><div><div>On 2010-11-16, at 2:19 AM, Nat Sakimura wrote:</div><br><blockquote type="cite">
<div text="#000000" bgcolor="#ffffff">
I have been pitching this to some folks for sometime, but I think we
should standardize on the URI scheme for each specifications. Chris
also had the same message. <br>
<br>
Currently, the Authn 2.0 uses <a href="http://specs.openid.net/auth/2.0" target="_blank">http://specs.openid.net/auth/2.0</a> as ns
and spec is <br>
stored at <a href="http://openid.net/specs/openid-authentication-2_0.html" target="_blank">http://openid.net/specs/openid-authentication-2_0.html</a><br>
<br>
AX1.0 uses <a href="http://openid.net/srv/ax/1.0" target="_blank">http://openid.net/srv/ax/1.0</a> as ns and spec is <br>
stored at <a href="http://openid.net/specs/openid-attribute-exchange-1_0.html" target="_blank">http://openid.net/specs/openid-attribute-exchange-1_0.html</a><br>
<br>
etc. <br>
<br>
I can point out two issues. <br>
<br>
(1) ns and spec location mismatch<br>
(2) seemingly random ns<br>
<br>
For the specs to come, I would like to propose the following scheme.
<br>
<br>
<a href="http://openid.net/specs/" target="_blank">http://openid.net/specs/</a><spec_name_abbrv>/<spec_version>/<br>
<br>
For example, if it were applied to Auth 2.0, <br>
<br>
<a href="http://openid.net/specs/auth/2.0/" target="_blank">http://openid.net/specs/auth/2.0/</a><br>
<br>
Note the trailing slash. <br>
<br>
Other examples: <br>
<br>
<a href="http://openid.net/specs/ab/1.0/" target="_blank">http://openid.net/specs/ab/1.0/</a><br>
<a href="http://openid.net/specs/jwt/1.0/" target="_blank">http://openid.net/specs/jwt/1.0/</a><br>
<a href="http://openid.net/specs/pape/1.1/" target="_blank">http://openid.net/specs/pape/1.1/</a><br>
<br>
etc. <br>
<br>
Cheers, <br>
<br>
Nat Sakimura<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------- Original Message --------
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">Subject: </th>
<td>SubVersion projects on <a href="http://svn.openid.net/" target="_blank">svn.openid.net</a> and file access on
<a href="http://openid.net/" target="_blank">openid.net</a> host</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">Date: </th>
<td>Tue, 16 Nov 2010 01:18:35 +0000</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">From: </th>
<td>Mike Jones <a href="mailto:Michael.Jones@microsoft.com" target="_blank"><Michael.Jones@microsoft.com></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">To: </th>
<td><a href="mailto:support@osuosl.org" target="_blank">support@osuosl.org</a> <a href="mailto:support@osuosl.org" target="_blank"><support@osuosl.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">CC: </th>
<td>John Bradley <a href="mailto:ve7jtb@ve7jtb.com" target="_blank"><ve7jtb@ve7jtb.com></a>, Nat Sakimura
<a href="mailto:n-sakimura@nri.co.jp" target="_blank"><n-sakimura@nri.co.jp></a>, "Don Thibeau"
<a href="mailto:don@oidf.org" target="_blank"><don@oidf.org></a>, John Ehrig
<a href="mailto:jehrig@inventures.com" target="_blank"><jehrig@inventures.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Dear OSL folks,
Can you please create these three new specification subtrees on <a href="http://svn.openid.net/" target="_blank">svn.openid.net</a>:
specifications/artifact_binding/1.0
specifications/json_web_token/1.0
specifications/oauth/2.0
These people should have write access to the first two repositories:
Mike Jones <a href="mailto:mbj@microsoft.com" target="_blank">mbj@microsoft.com</a><a href="mailto:mbj@microsoft.com" target="_blank"><mailto:mbj@microsoft.com></a>
John Bradley <a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a><a href="mailto:ve7jtb@ve7jtb.com" target="_blank"><mailto:ve7jtb@ve7jtb.com></a>
Nat Sakimura <a href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a><a href="mailto:n-sakimura@nri.co.jp" target="_blank"><mailto:n-sakimura@nri.co.jp></a>
Only I should have write access to the third one (oauth/2.0).
Also, sometime since I was last working on the Provider Authentication Policy Extension (PAPE) specification, my password or account on the host <a href="http://openid.net/" target="_blank">openid.net</a> was reset. My userid there is "mbj". Can you please reset my password and call me at (425) 985-8916 to tell me the new one. I need to be able to log in to write content to the <a href="http://openid.net/specs/" target="_blank">http://openid.net/specs/</a> directory, which when I last did it was at the location /var/www/<a href="http://openid.net/docs/specs" target="_blank">openid.net/docs/specs</a>.
Thanks a bunch!
-- Mike
OAuth 2.0 Bearer Token spec editor
JSON Web Token spec editor
OpenID Artifact Binding committee member
</pre>
</div>
</blockquote></div><br></div></div></div></div></div><br></div></div>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
</div>
_______________________________________________<br>specs mailing list<br><a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
</blockquote></div><br></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>
</blockquote></div><br></div></body></html>