4 Effect on OpenID, XRI and LID
OpenID MUST support the Yadis Protocol.
The OASIS XRI technical committee will consider interoperation of XRI Resolution with sites supporting the Yadis Protocol.
LID MUST support the Yadis Protocol as part of MinimumLID.
Going forward, OpenID implementations SHOULD recognize when non-OpenID authentication is requested and respond appropriately. They are encouraged to support LID authentication as well.
Going forward, LID implementations SHOULD recognize when a non-LID authentication is requested and respond appropriately. They are encouraged to support OpenID authentication as well.
4.2 Specific effects on LID and OpenID
Both OpenID and LID Relying Parties are affected by Yadis. In order to support Yadis they must include support for the Yadis Protocol. The use of the Yadis Protocol by LID and OpenID are described in the following sections. Once the Yadis Resource Descriptor is obtained and a service is chosen by the Relying Party, LID and OpenID authentication proceeds as normal.
OpenID servers are not affected by Yadis.
LID servers are not affected by Yadis.
We expect that both LID and OpenID Relying Parties will in future expand to support other signon protocols which are declared by a Yadis Resource Descriptor.
The Type identifier for OpenID authentication is http://openid.net/signon, and the current version is 1.0. An OpenID service declaration is as follows:
http://openid.net/signon/1.0 http://myid.example.com/openid http://john.example.net/openid/
The URI element gives the URL of the OpenID Identity Server which can authenticate the user of this identifier, and is required. The Delegate element gives the OpenID Identity URL to use for signon, and is optional. If the Delegate field is not present, the Yadis ID is used for signon.
OpenID delegation is not supported, since Yadis itself provides equivalent delegation support.
OpenID URLs may go on including openid.server and openid.delegate LINK elements for backwards compatibility, but the behavior when the configuration in the legacy fields and in the identity document differ is undefined so care must be taken to keep the settings in sync.
The Type identifier for LID authentication is http://lid.netmesh.org/sso/ and the current beta test version is 2.0b5. A LID service declaration is as follows:
The Type identifier for the LID Traversal Profile is http://lid.netmesh.org/traversal and the current version is 2.0b5. The service declaration is the same as for LID authentication aside from the Type identifier.
The Type identifier for the LID VCard Profile is http://lid.netmesh.org/traversal/vcard and the current version is 2.0b5. The service declaration is the same as for LID authentication aside from the Type identifier.