[OpenID] XRDS documents

Tan, William william.tan at neustar.biz
Fri Apr 6 00:44:54 UTC 2007


You shouldn't have to, since the same URI can handle both protocol versions.

XRI resolution, and therefore YADIS should be able to handle multiple types in the service and yield the results that you'd expect.

--
http://xri.net/=wil      

-----Original Message-----
From: "Martin Foster" <martin at ethereal-realms.org>
Date: Thu, 5 Apr 2007 20:32:52 
To:"Drummond Reed" <drummond.reed at cordance.net>,"OpenID General" <general at openid.net>
Subject: Re: [OpenID] XRDS documents

Drummond Reed wrote:
 > Martin,
 >
 > In the examples you cite below, there are three differences (sounds almost
 > like a "spot the differences" game ;-):
 >
 > 1) The second Yadis example is the only one that shows the use of the
 > priority= attribute on the Service element. This can be used on any Service
 > element in any XRDS document to control Service selection if the document
 > has have more than one instance of a specific service type (for redundancy,
 > different service providers, etc.)
 >
 > 2) The final example you cite uses the XRDS native LocalID element which is
 > being added as a child of the Service element in XRI Resolution 2.0 Working
 > Draft 11 (in Working Draft 10, LocalID was only specified at the XRD level).
 > This replaces the need for the openid:Delegate element that is shown in the
 > Yadis examples.
 >
 > 3) The final example uses the service type URI defined in the OpenID
 > Authentication 2.0 working draft spec
 > (http://specs.openid.net/auth/2.0/signon: <http://specs.openid.net/auth/2.0/signon> ) instead of the one used in
 > 1.0/1.1.
 >
 > Hope this helps,
 >
 > =Drummond
 >
 
 So would you realistically be required to add in two entries under the
 displayed XRDS document in order to support both OpenID 2.0 clients and
 OpenID 1.x clients?  In case they make use of YADIS?
 
 If so, would an entry that would look similar to the following:
 
 <Service priority="20" xmlns="xri://$xrd*($v*2.0)">
     <Type>http://specs.openid.net/auth/2.0/signon: <http://specs.openid.net/auth/2.0/signon> </Type>
     <URI>https://www.exampleprovider.com/endpoint/: <https://www.exampleprovider.com/endpoint/> </URI>
     <LocalID>https://user.exampleprovider.com/: <https://user.exampleprovider.com/> </LocalID>
 </Service>
 
 <Service priority="20" xmlns:openid="http://openid.net/xmlns/1.0: <http://openid.net/xmlns/1.0> ">
     <Type>http://openid.net/signon/1.0: <http://openid.net/signon/1.0> </Type>
     <URI>https://www.exampleprovider.com/endpoint/: <https://www.exampleprovider.com/endpoint/> </URI>
     <openid:Delegate>https://user.exampleprovider.com/: <https://user.exampleprovider.com/> </openid:Delegate>
 </Service>
 
 Or am I missing something here?
 
         Martin Foster
         Creator/Designer Ethereal Realms
         martin at ethereal-realms.org
 _______________________________________________
 general mailing list
 general at openid.net
 http://openid.net/mailman/listinfo/general: <http://openid.net/mailman/listinfo/general> 
 
 


More information about the general mailing list