Works for me. :) --David
-----Original Message----- From: Granqvist, Hans Sent: Friday, October 20, 2006 6:40 PM To: Recordon, David; specs@openid.net Subject: RE: OpenID.net Service Type Namespaces It has had some voices against it, but how about considering this template (used in for example W3C xmldsig and xmlenc): http://openid.net/[year]/[month]/[project]#[type] Time-dependent (rather than version--dependent) namespaces can evolve freely and will not be tied down to specific versioning numbers. Example: http://openid.net/2006/10/authentication http://openid.net/2006/10/authentication#signon It's cool if an HTTP GET on these links returns the specification. Once a spec is finalized, the then current year/month becomes that spec's namespace. For example, xmlenc's namespace is http://www.w3.org/2001/04/xmlenc Hans > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Recordon, David > Sent: Friday, October 20, 2006 3:09 PM > To: specs@openid.net > Subject: OpenID.net Service Type Namespaces > > Right now we have things like http://openid.net/signon/1.1, > http://openid.net/sreg/1.0, etc. This doesn't really seem to scale, > populating the main http://openid.net namespace. > > Could we do something like > http://specs.openid.net/authentication/2.0/signon or > http://specs.openid.net/authentication/2.0/identifier_select > as well as then http://specs.openid.net/sreg/1.0? > > This would give all the specs their own namespaces, as well as make it > so we can do smart redirection from each of these "type" urls to the > correct anchor in the individual spec. > > --David > _______________________________________________ > specs mailing list > specs@openid.net > http://openid.net/mailman/listinfo/specs > > _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs