[Openid-specs-ab] Spec URL

[Mike Jones]

http://openid.net/specs/connect/1.0/ works for me (and then we can have URIs like http://openid.net/specs/connect/1.0/issuer as well).

I don't see a reason to have URIs for the related specs, other than perhaps on a case-by-case basis.  But if we do need them, they should probably be as you suggest below in option 1.

				-- Mike

-----Original Message-----
From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of sakimura
Sent: Friday, July 08, 2011 1:34 AM
To: openid-specs-ab at lists.openid.net
Subject: [Openid-specs-ab] Spec URL

 On Monday call, we agreed to use

   http://openid.net/specs/connect/1.0

 as the spec identifier URL for the core.

 On the hind site, this may not be optimal. At the very least, we  probably want to put the traling slash "/".
 Otherwise, we would not be able to make that a publishing point for  multiple representation of the same spec unless we do something creative  with mod_rewrite. I would rather use Apache's default content  negotiation capability.

 We also have to decide on the URL for all the other companion specs. 
 Would they be something like:

   http://openid.net/specs/connect-userinfo/1.0/
   http://openid.net/specs/connect-framework/1.0/

 etc.?

 In that case, would it be more appropriate to make the core like below?

   http://openid.net/specs/connect-core/1.0/

 Other option (Option 2) is like:

   http://openid.net/specs/connect/core/1.0/
   http://openid.net/specs/connect/userinfo/1.0/

 etc. for the individual specs, and

   http://openid.net/specs/connect/1.0/

 for the "Index" page giving the list of all of the sub-specs.

 I am fine either-way, but Option 2 seems a little more attractive in  the sense that it has grouping notion embodied.

 Thoughts?

 =nat


_______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net
http://lists.openid.net/mailman/listinfo/openid-specs-ab