[OpenID] XRDS documents

[Drummond Reed]

>>> On 4/5/07, Martin Foster <martin at ethereal-realms.org> wrote:
>>> What if the user had implemented Yadis some time ago and supports LID
>>> along with OpenID 1.x.   So when he pulls that XRDS document the
>>> consumer would look for the 1.x protocols only since it was not
>>> programmed when 2.x capable clients went out the door.
>>>
>>> Does this make sense or am I being too cautious in my assessment?
>> 
>> Josh Hoyt wrote:
>>
>> I think that what Wil Tan means is:
>> 
>> <Service xmlns="xri://$xrd*($v*2.0)" 
>> xmlns:openid="http://openid.net/xmlns/1.0">
>>   <URI>https://www.exampleprovider.com/endpoint/</URI>
>> 
>>   <Type>http://specs.openid.net/auth/2.0/signon</Type>
>>   <LocalID>https://user.exampleprovider.com/</LocalID>
>> 
>>   <Type>http://openid.net/signon/1.0</Type>
>>   <openid:Delegate>https://user.exampleprovider.com/</openid:Delegate>
>> </Service>
>> 
>> Josh
>
>And you can also throw in the SREG services if your OpenID 
>implementation supports that in any way shape or form.   So to confirm, 
>it is a good idea of put entries for both 2.0 and 1.x support in case 
>you run into older clients?

Yes.

>On a side note, are XRI and Yadis required only for discovery?

Yes. Once you've discovered your OpenID service endpoint metadata, the rest
is handled with the OpenID Authentication protocol (keeping in mind the
identifiers used in the protocol may be either URLs or XRIs).

=Drummond