<Service priority="50"> <Type>http://openid.net/signon/1.0</Type> <URI>http://www.myopenid.com/server</URI> <openid:Delegate>http://smoker.myopenid.com/</openid:Delegate> </Service> <Service priority="10"> <Type>http://openid.net/signon/1.0</Type> <URI>http://www.livejournal.com/openid/server.bml</URI> <openid:Delegate>http://www.livejournal.com/users/frank/</openid:Delegate> </Service> <Service priority="20"> <Type>http://lid.netmesh.org/sso/2.0</Type> <URI>http://mylid.net/liddemouser</URI> </Service> <Service> <Type>http://lid.netmesh.org/sso/1.0</Type> </Service> </XRD> </xrds:XRDS> If this XRDS document was returned, using one of the listed mechanisms, for a URL, it would express the following information: The URL is a Yadis identity URL. This URL supports the OpenID protocol, through two servers and two delegates. This URL supports version 1.0 and version 2.0 of the LID protocol, with a delegate. The owner of this identity URL prefers to sign-on using their LiveJournal account and the OpenID protocol (priority 10). If that is not possible (e.g. because a relying party does not support OpenID, or because the LiveJournal server is unavailable), the owner would like to use the LID URL http://mylid.net/liddemouser (priority 20), followed by the MyOpenID service (priority 50). LID, OpenID and the developer community Yadis was initiated by developers of the Light-weight Identity (LID) and OpenID protocols. This collaboration was then joined by members of the OASIS XRI Technical Committee, particularly those working on i-names. However, Yadis is an open initiative, so other developers will start using XRDS lightweight capabilities description, making possible a "mix and match" approach to building Yadis-enabled applications, enabling application developers to choose their own balance between ease of implementation on one hand, and range of features on the other. See also XRDS Liberty Alliance InfoCard OpenID Light-weight Identity (LID) i-name XRI External links Yadis Documentation Federated identity