<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body 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 class="moz-txt-link-freetext" href="http://specs.openid.net/auth/2.0">http://specs.openid.net/auth/2.0</a> as ns
and spec is <br>
stored at <a class="moz-txt-link-freetext" href="http://openid.net/specs/openid-authentication-2_0.html">http://openid.net/specs/openid-authentication-2_0.html</a><br>
<br>
AX1.0 uses <a class="moz-txt-link-freetext" href="http://openid.net/srv/ax/1.0">http://openid.net/srv/ax/1.0</a> as ns and spec is <br>
stored at <a class="moz-txt-link-freetext" href="http://openid.net/specs/openid-attribute-exchange-1_0.html">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 class="moz-txt-link-freetext" href="http://openid.net/specs/">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 class="moz-txt-link-freetext" href="http://openid.net/specs/auth/2.0/">http://openid.net/specs/auth/2.0/</a><br>
<br>
Note the trailing slash. <br>
<br>
Other examples: <br>
<br>
<a class="moz-txt-link-freetext" href="http://openid.net/specs/ab/1.0/">http://openid.net/specs/ab/1.0/</a><br>
<a class="moz-txt-link-freetext" href="http://openid.net/specs/jwt/1.0/">http://openid.net/specs/jwt/1.0/</a><br>
<a class="moz-txt-link-freetext" href="http://openid.net/specs/pape/1.1/">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 class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject: </th>
<td>SubVersion projects on svn.openid.net and file access on
openid.net host</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Tue, 16 Nov 2010 01:18:35 +0000</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Mike Jones <a class="moz-txt-link-rfc2396E" href="mailto:Michael.Jones@microsoft.com"><Michael.Jones@microsoft.com></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:support@osuosl.org">support@osuosl.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:support@osuosl.org"><support@osuosl.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
<td>John Bradley <a class="moz-txt-link-rfc2396E" href="mailto:ve7jtb@ve7jtb.com"><ve7jtb@ve7jtb.com></a>, Nat Sakimura
<a class="moz-txt-link-rfc2396E" href="mailto:n-sakimura@nri.co.jp"><n-sakimura@nri.co.jp></a>, "Don Thibeau"
<a class="moz-txt-link-rfc2396E" href="mailto:don@oidf.org"><don@oidf.org></a>, John Ehrig
<a class="moz-txt-link-rfc2396E" href="mailto:jehrig@inventures.com"><jehrig@inventures.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Dear OSL folks,
Can you please create these three new specification subtrees on svn.openid.net:
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 class="moz-txt-link-abbreviated" href="mailto:mbj@microsoft.com">mbj@microsoft.com</a><a class="moz-txt-link-rfc2396E" href="mailto:mbj@microsoft.com"><mailto:mbj@microsoft.com></a>
John Bradley <a class="moz-txt-link-abbreviated" href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a><a class="moz-txt-link-rfc2396E" href="mailto:ve7jtb@ve7jtb.com"><mailto:ve7jtb@ve7jtb.com></a>
Nat Sakimura <a class="moz-txt-link-abbreviated" href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a><a class="moz-txt-link-rfc2396E" href="mailto:n-sakimura@nri.co.jp"><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 openid.net 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 class="moz-txt-link-freetext" href="http://openid.net/specs/">http://openid.net/specs/</a> directory, which when I last did it was at the location /var/www/openid.net/docs/specs.
Thanks a bunch!
-- Mike
OAuth 2.0 Bearer Token spec editor
JSON Web Token spec editor
OpenID Artifact Binding committee member
</pre>
</body>
</html>