Will the frag reference still work with the extra / John B. On 2010-11-17, at 12:03 PM, Nat Sakimura wrote:
> Actually, I should have written as: > > /<spec_abbrv>/<spec_ver>/#<feature> > > but that is a minor issue, I think. (An extra "/" is there, which is kind of > important when we think of the server implementations.) > > So, what would be the process to formalize it? > Do we just announce it as the specs council or something? > > =nat > > On Wed, Nov 17, 2010 at 11:07 PM, John Bradley <[email protected]> wrote: > I think that works. > > It is always nice to have them dereference-able. > > The fragment allows for a single document. > > John B. > > On 2010-11-17, at 5:23 AM, Nat Sakimura wrote: > >> Actually, >> >> /<spec_abbrv>/<spec_ver>#<feature> >> >> is quite nice in the sense that it should jump to the location in the spec >> document that describes the feature. >> >> =nat >> >> On Wed, Nov 17, 2010 at 5:12 PM, David Recordon <[email protected]> wrote: >> 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. >> >> >> On Tue, Nov 16, 2010 at 2:44 PM, John Bradley <[email protected]> wrote: >> We also have URI in use like http://specs.openid.net/auth/2.0/server etc. >> >> I agree with managing the namespace for each spec in a more consistent way. >> >> John B. >> >> >> On 2010-11-16, at 2:19 AM, Nat Sakimura wrote: >> >>> 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. >>> >>> Currently, the Authn 2.0 uses http://specs.openid.net/auth/2.0 as ns and >>> spec is >>> stored at http://openid.net/specs/openid-authentication-2_0.html >>> >>> AX1.0 uses http://openid.net/srv/ax/1.0 as ns and spec is >>> stored at http://openid.net/specs/openid-attribute-exchange-1_0.html >>> >>> etc. >>> >>> I can point out two issues. >>> >>> (1) ns and spec location mismatch >>> (2) seemingly random ns >>> >>> For the specs to come, I would like to propose the following scheme. >>> >>> http://openid.net/specs/<spec_name_abbrv>/<spec_version>/ >>> >>> For example, if it were applied to Auth 2.0, >>> >>> http://openid.net/specs/auth/2.0/ >>> >>> Note the trailing slash. >>> >>> Other examples: >>> >>> http://openid.net/specs/ab/1.0/ >>> http://openid.net/specs/jwt/1.0/ >>> http://openid.net/specs/pape/1.1/ >>> >>> etc. >>> >>> Cheers, >>> >>> Nat Sakimura >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -------- Original Message -------- >>> Subject: SubVersion projects on svn.openid.net and file access on >>> openid.net host >>> Date: Tue, 16 Nov 2010 01:18:35 +0000 >>> From: Mike Jones <[email protected]> >>> To: [email protected] <[email protected]> >>> CC: John Bradley <[email protected]>, Nat Sakimura <[email protected]>, >>> "Don Thibeau" <[email protected]>, John Ehrig <[email protected]> >>> >>> 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 >>> [email protected]<mailto:[email protected]> >>> John Bradley >>> [email protected]<mailto:[email protected]> >>> Nat Sakimura >>> [email protected]<mailto:[email protected]> >>> 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 http://openid.net/specs/ >>> 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 >>> >>> >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> >> >> >> -- >> Nat Sakimura (=nat) >> http://www.sakimura.org/en/ >> http://twitter.com/_nat_en >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs > > > > > -- > Nat Sakimura (=nat) > http://www.sakimura.org/en/ > http://twitter.com/_nat_en
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
