Yadis Service Types

From yadis.org

(Redirected from Yadis Services Listing)
Jump to: navigation, search

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.

NamePurposeService Type URIRequires XRDS URI elementExtends XRDS Namespace
AddId!Creating "Add this"-linkshttp://addid.identity20.eu/0.2dYesYes
Minimum LIDMinimum requirements for a URL to be a LID URLhttp://lid.netmesh.org/minimum-lid/1.0, http://lid.netmesh.org/minimum-lid/2.0OptionalNo
LID SSOLID's Single-Sign-On protocolhttp://lid.netmesh.org/sso/2.0OptionalNo
LID Relying PartyEnables a LID Relying Party to state that facthttp://lid.netmesh.org/relying-party/2.0OptionalNo
LID Traversals and SelectionsVocabulary-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.0OptionalNo
LID Format NegotiationEnables clients to specify the representation in which they would like to obtain information, e.g. but not limited to MIME typehttp://lid.netmesh.org/format-negotiation/2.0OptionalNo
LID Authenticated Message SenderEnables identity URLs to specify that they can send authenticated LID messageshttp://lid.netmesh.org/post/sender/2.0OptionalNo
LID Authenticated Message ReceiverEnables URLs to specify that they can receive authenticated LID messageshttp://lid.netmesh.org/post/receiver/2.0OptionalNo
OpenID Authentication 1.0OpenID's Single-Sign-On protocolhttp://openid.net/signon/1.0YesOptional
OpenID Authentication 1.1OpenID's Single-Sign-On protocolhttp://openid.net/signon/1.1YesOptional
OpenID Authentication 2.0OpenID's Single-Sign-On protocolhttp://specs.openid.net/auth/2.0/signonYesOptional
OpenID SReg ExtensionExtension for profile data submissionhttp://openid.net/sreg/1.0uses OpenID sign-on URLNo


Authors and developers: add the service types for your Yadis-compatible specifications here!

Some hints:

  • 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.
Personal tools