YADIS best practice?

[Josh Hoyt]

On 1/20/06, Peter Davis <peter.davis at neustar.biz> wrote:
> On 1/20/2006 2:37 PM, "Johannes Ernst" <jernst+lists.danga.com at netmesh.us>
> wrote:
>
> > I'm trying to decide whether there is, or should be, a "best
> > practice" on how to declare two YADIS services that only differ in
> > their version number.
> > For example, most OpenID implementation today seem to support both
> > V1.1 and V1.0. In YADIS, should this be declared as:
> >
> > <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?
>
> It matters to define the behaviour when encountering on or the other.  At
> least for conformance ;-)
>
> The issue to think about for the second example is the endpoints described
> by <URI> MUST support both protocols versions, which in some deployments may
> not be possible or practical.

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.

Josh