Final outstanding issues with the OpenID 2.0Authenticationspecification

Recordon, David drecordon at verisign.com
Fri May 18 17:54:02 UTC 2007


Hey Dmitry,
When using Yadis you're able to advertise if you're speaking OpenID 1.1
or 2.0 and thus the RP know which version of the protocol the request
should be made in.  When using HTML-Based Discovery this is not possible
unless the attributes are renamed or a third "version" tag is added
which was not the preferred option.

--David 

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Dmitry Shechtman
Sent: Friday, May 18, 2007 1:00 AM
To: 'Josh Hoyt'; 'OpenID specs list'
Subject: RE: Final outstanding issues with the OpenID
2.0Authenticationspecification

7.3.3. HTML-Based Discovery

A <LINK> tag MUST be included with attributes "rel" set to
openid2.provider"
and "href" set to an OP Endpoint URL

A <LINK> tag MAY be included with attributes "rel" set to
"openid2.local_id"
and "href" set to the end user's OP-Local Identifier


Could somebody please enlighten me as to what's wrong with leaving those
as "openid.server" and "openid.delegate" respectfully (i.e.
backward-compatible)?


Regards,
Dmitry
=damnian

_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs



More information about the specs mailing list