YADIS best practice?

[Peter Davis]

On 1/20/2006 3:14 PM, "Josh Hoyt" <josh at janrain.com> wrote:

>>> <Service>
>>>    <Type>http://openid.net/signon/1.0</Type>
>>>    <URI>http://openid.example.com/</URI>
>>> </Service>
>>> <Service>
>>>    <Type>http://openid.net/signon/1.1</Type>
>>>    <URI>http://openid.example.com/</URI>
>>> </Service>
>>> 
>>> or is this better practice:
>>> 
>>> <Service>
>>>    <Type>http://openid.net/signon/1.0</Type>
>>>    <Type>http://openid.net/signon/1.1</Type>
>>>    <URI>http://openid.example.com/</URI>
>>> </Service>
>>> 
>>> or doesn't it matter?

> 
> I'm not sure I understand the difference. It seems to me that the
> first version also implies that the URI supports both protocols as
> well.
> 

If, as an implementation, I'd like to advertise support for both 1.1 and
1.0, but my deployment conditions require me to use 2 different endpoints,
than you can only use option one. Option 2 provides no means to indicate
which endpoint supports which protocol version.

But using the first case, I can do:

<Service>
  <Type>http://openid.net/signon/1.0</type>
  <URI>http://my.example.biz/verion1/endpoint</URI>
</Service>
<Service>
  <Type>http://openid.net/signon/1.1</type>
  <URI>http://my.example.biz/verion11/endpoint</URI>
</Service>

The spec should let you do either.  I'm just pointing out the issue in the
second example.

=peterd  (http://public.xdi.org/=peterd)