Yadis Service Types
This page contains a list of service types that have been specified in a Yadis Resource Descriptor (in alphabetical order). As anybody can define their own Yadis service types, this list is necessarily incomplete; it may be helpful nevertheless.
|Name||Purpose||Service Type URI||Requires XRDS URL element||Extends XRDS Namespace|
|Minimum LID||Minimum requirements for a URL to be a LID URL||http://lid.netmesh.org/minimum-lid/1.0, http://lid.netmesh.org/minimum-lid/2.0||Optional||No|
|LID SSO||LID's Single-Sign-On protocol||http://lid.netmesh.org/sso/2.0||Optional||No|
|LID Relying Party||Enables a LID Relying Party to state that fact||http://lid.netmesh.org/relying-party/2.0||Optional||No|
|LID Traversals and Selections||Vocabulary-independent mechanism to traverse from a LID URL to related information (e.g. profile information, but usable with any vocabulary)||http://lid.netmesh.org/traversal/2.0||Optional||No|
|LID Format Negotiation||Enables clients to specify the representation in which they would like to obtain information, e.g. but not limited to MIME type||http://lid.netmesh.org/format-negotiation/2.0||Optional||No|
|LID Authenticated Message Sender||Enables identity URLs to specify that they can send authenticated LID messages||http://lid.netmesh.org/post/sender/2.0||Optional||No|
|LID Authenticated Message Receiver||Enables URLs to specify that they can receive authenticated LID messages||http://lid.netmesh.org/post/receiver/2.0||Optional||No|
|OpenID sign-on||OpenID's Single-Sign-On protocol||http://openid.net/signon/1.0||Yes||Optional|
Authors and developers: add the service types for your Yadis-compatible specifications here!
- The "Service Type URI" is the content of the Type-element in the Service-element
- In "Use" describe in a word or a few what your service is good for
- For "Requires URL" enter either "Yes" if a server must be specified or "No" if this functionality can be executed on the original Yadis URI or at some known centralized server.
- For "Own Namespace" enter either "None" if no additional elements are introduced to the XRD, "Optional" if a namespace is present but not required for basic functionality or "Required" if service only works with additional elements. The namespace URI and element listing should be found in the specification on the website of the service.