The extensible resource descriptor sequence ( XRDS) is an XML-based file format that provides a list of services.
Background
The XML format used by XRDS was originally developed in 2004 by the OASIS XRI (extensible resource identifier) Technical Committee as the resolution format for XRIs. The acronym XRDS was coined during subsequent discussions between XRI TC members and
OpenID developers at the first Internet Identity Workshop held in Berkeley, California in October 2005.
The protocol for discovering an XRDS document from a URL was formalized as the Yadis specification published by Yadis.org in March 2006. Yadis became the service discovery format for OpenID 1.1.
A common discovery service for both URLs and XRIs proved so useful that in November 2007 the XRI Resolution 2.0 specification formally added the URL-based method of XRDS discovery (Section 6).
XRDS Simple
In early 2008, work on
OAuth discovery by Eran Hammer-Lahav led to the development of XRDS Simple, a profile of XRDS that restricts it to the most basic elements and introduces some extensions to support
OAuth discovery and other protocols that use specific
HTTP methods. In late 2008, XRDS Simple has been cancelled and merged back into the main XRDS specification resulting in the upcoming XRD 1.0 format.
Example uses
Besides
XRI resolution, examples of typical XRDS usage include:
-
OpenID authentication for discovery and capabilities description of OpenID providers.
-
OAuth discovery for locating OAuth service endpoints and capabilities.
-
Higgins project for discovery of Higgins context providers.
-
XDI.org I-name and I-number digital identity addressing services for generalized digital identity service discovery.
-
The XDI data sharing protocol for discovery of XDI service endpoints and capabilities.
Example XRDS document
Following is an example of an XRDS document for the fictional
XRI i-name =example. This document would typically be requested from a Web server via
HTTP or
HTTPS using the content type
application/xrds+xml. Note that the outer container
element serves as a container for one or more (Extensible Resource Descriptor) elements. Most simple XRDS documents have only one XRD. Other services like XRI resolution may construct a sequence of XRDs within a single XRDS document to reflect a chain of metadata about linked resources.
*example
2008-05-05T00:15:00.000Z
xri://=
!4C72.6C81.D78F.90B2
http://example.com/example-user
http://example.net/blog
xri://=!4C72.6C81.D78F.90B2
xri://=!F83.62B1.44F.2813
xri://$res*auth*($v*2.0)
application/xrds+xml
http://resolve.example.com
http://resolve2.example.com
https://resolve.example.com
http://specs.openid.net/auth/2.0/signon
http://www.myopenid.com/server
http://example.myopenid.com/
http://openid.net/server/1.0
http://www.livejournal.com/openid/server.bml
http://www.livejournal.com/users/example/
/media/pictures
image/jpeg
http://pictures.example.com
Synonyms
XRDS documents can assert zero or more for a resource. In this context, a synonym is another identifier (a URI or XRI) that identifies the same target resource. For instance, the example XRDS document above asserts four synonyms:
-
The local synonym !4C72.6C81.D78F.90B2. This is a relative XRI synonym assigned by the provider of this XRDS document.
-
The equivalent URL http://example.com/example-user with a priority of 10 (1 is the highest priority).
-
The equivalent URL http://example.net/blog with a priority of 15 (a lower priority than the other equivalent URL above).
-
The canonical identifier xri://=!4C72.6C81.D78F.90B2. This is an absolute XRI i-number for the target resource—a persistent identifier that will never be reassigned (the functional equivalent of a Uniform Resource Name).
For full details of XRDS synonym support, see XRI Resolution 2.0, Section 5.
Service endpoints (SEPs)
The other main purpose of XRDS documents is to assert the services associated with a resource, called service endpoints or SEPs. For instance, the example XRDS document above asserts four service endpoints for the represented resource:
-
An XRI resolution service (type xri://$res*auth*($v*2.0)).
-
An OpenID 2.0 authentication service (type http://openid.net/signon/2.0).
-
An OpenID 1.0 authentication service (type http://openid.net/server/1.0).
-
An untyped service for requesting resources with a media type image/jpeg.
For full details of XRDS service endpoints, see XRI Resolution 2.0, Sections 4.2 and 13.
Service types
In XRDS documents, a service is identified using a URI or XRI. Following are listings of well-known service types.
XRI resolution
|
|
| Authority Resolution | xri://$res*auth*($v*2.0) | XRI Resolution 2.0 | March 2005 |
| Proxy Resolution | xri://$res*proxy*($v*2.0) | XRI Resolution 2.0 | March 2005 |
OpenID
|
|
| OpenID 1.0 | http://openid.net/server/1.0 | OpenID Authentication 2.0, Section 14.2.1 | June 2005 |
| OpenID 1.1 | http://openid.net/server/1.1 | OpenID Authentication 2.0, Section 14.2.1 | May 2006 |
| OpenID 2.0 – Standard Login | http://specs.openid.net/auth/2.0/signon | OpenID Authentication 2.0, Section 7.3.2.1.2 | December 2007 |
| OpenID 2.0 – OP Identifier Login | http://specs.openid.net/auth/2.0/server | OpenID Authentication 2.0, Section 7.3.2.1.1 | December 2007 |
| OpenID Attribute Exchange 1.0 | http://openid.net/srv/ax/1.0 | OpenID Attribute Exchange 1.0, Section 2 | December 2007 |
OAuth discovery
|
|
| OAuth Discovery | http://oauth.net/discovery/1.0 | OAuth Discovery Draft 2 | March 2008 |
Licensing
XRDS is an open public royalty-free OASIS specification. The OASIS XRI Technical Committee has operated since its inception in 2003 under a royalty-free licensing policy as stated in its charter and IPR page.
See also
External links
