This article has an unclear citation style. The reason given is: Violates Wikipedia:External links: "Wikipedia articles may include links to web pages outside Wikipedia (external links), but they should not normally be used in the body of an article." The references used may be made clearer with a different or consistent style of citation and footnoting.(May 2013) (Learn how and when to remove this template message)
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 first Internet Identity Workshop held in Berkeley, CA 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).[1] This format and discovery protocol subsequently became part of OpenID Authentication 2.0.[2]
XRDS Simpleedit
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 usesedit
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.
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 documentedit
Following is an example of an XRDS document for the fictional XRIi-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 <XRDS> element serves as a container for one or more <XRD> (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.
<?xml version="1.0" encoding="UTF-8"?><xrds:XRDSxmlns:xrds="xri://$xrds"xmlns="xri://$xrd*($v*2.0)"xmlns:openid="http://openid.net/xmlns/1.0"><XRDref="xri://=example"><Query>*example</Query><Statusceid="off"cid="verified"code="100"/><Expires>2008-05-05T00:15:00.000Z</Expires><ProviderID>xri://=</ProviderID><!-- synonym section --><LocalIDpriority="10">!4C72.6C81.D78F.90B2</LocalID><EquivIDpriority="10">http://example.com/example-user</EquivID><EquivIDpriority="15">http://example.net/blog</EquivID><CanonicalID>xri://=!4C72.6C81.D78F.90B2</CanonicalID><!-- service section --><Service><!-- XRI resolution service --><ProviderID>xri://=!F83.62B1.44F.2813</ProviderID><Type>xri://$res*auth*($v*2.0)</Type><MediaType>application/xrds+xml</MediaType><URIpriority="10">http://resolve.example.com</URI><URIpriority="15">http://resolve2.example.com</URI><URI>https://resolve.example.com</URI></Service><!-- OpenID 2.0 login service --><Servicepriority="10"><Type>http://specs.openid.net/auth/2.0/signon</Type><URI>http://www.myopenid.com/server</URI><LocalID>http://example.myopenid.com/</LocalID></Service><!-- OpenID 1.0 login service --><Servicepriority="20"><Type>http://openid.net/server/1.0</Type><URI>http://www.livejournal.com/openid/server.bml</URI><openid:Delegate>http://www.livejournal.com/users/example/</openid:Delegate></Service><!-- untyped service for access to files of media type JPEG --><Servicepriority="10"><Typematch="null"/><Pathselect="true">/media/pictures</Path><MediaTypeselect="true">image/jpeg</MediaType><URIappend="path">http://pictures.example.com</URI></Service></XRD></xrds:XRDS>
Synonymsedit
XRDS documents can assert zero or more synonyms 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)edit
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 typesedit
In XRDS documents, a service is identified using a URI or XRI. Following are listings of well-known service types.[3]
XRI resolutionedit
Common Name
URI or XRI
Source
Established
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
OpenIDedit
Common Name
URI or XRI
Source
Established
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 discoveryedit
Common Name
URI or XRI
Source
Established
OAuth Discovery
http://oauth.net/discovery/1.0
OAuth Discovery Draft 2
March 2008
Licensingedit
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.
^"Announcing xrdstype.net". Gabe Wachob. Retrieved 2023-02-23.
External linksedit
OASIS XRI Technical Committee
December 15, 2023
xrds, this, article, about, format, magazine, magazine, this, article, multiple, issues, please, help, improve, discuss, these, issues, talk, page, learn, when, remove, these, template, messages, this, article, unclear, citation, style, reason, given, violates. This article is about the XML format For the magazine see XRDS magazine This article has multiple issues Please help improve it or discuss these issues on the talk page Learn how and when to remove these template messages This article has an unclear citation style The reason given is Violates Wikipedia External links Wikipedia articles may include links to web pages outside Wikipedia external links but they should not normally be used in the body of an article The references used may be made clearer with a different or consistent style of citation and footnoting May 2013 Learn how and when to remove this template message This article includes a list of references related reading or external links but its sources remain unclear because it lacks inline citations Please help to improve this article by introducing more precise citations November 2012 Learn how and when to remove this template message This article has no lead section Please improve this article by adding one in your own words November 2022 Learn how and when to remove this template message Learn how and when to remove this template message Contents 1 Background 2 XRDS Simple 3 Example uses 4 Example XRDS document 5 Synonyms 6 Service endpoints SEPs 7 Service types 7 1 XRI resolution 7 2 OpenID 7 3 OAuth discovery 8 Licensing 9 See also 10 References 11 External linksBackground editThe 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 first Internet Identity Workshop held in Berkeley CA 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 1 This format and discovery protocol subsequently became part of OpenID Authentication 2 0 2 XRDS Simple editIn 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 editBesides 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 The 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 editFollowing 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 lt XRDS gt element serves as a container for one or more lt XRD gt 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 lt xml version 1 0 encoding UTF 8 gt lt xrds XRDS xmlns xrds xri xrds xmlns xri xrd v 2 0 xmlns openid http openid net xmlns 1 0 gt lt XRD ref xri example gt lt Query gt example lt Query gt lt Status ceid off cid verified code 100 gt lt Expires gt 2008 05 05T00 15 00 000Z lt Expires gt lt ProviderID gt xri lt ProviderID gt lt synonym section gt lt LocalID priority 10 gt 4C72 6C81 D78F 90B2 lt LocalID gt lt EquivID priority 10 gt http example com example user lt EquivID gt lt EquivID priority 15 gt http example net blog lt EquivID gt lt CanonicalID gt xri 4C72 6C81 D78F 90B2 lt CanonicalID gt lt service section gt lt Service gt lt XRI resolution service gt lt ProviderID gt xri F83 62B1 44F 2813 lt ProviderID gt lt Type gt xri res auth v 2 0 lt Type gt lt MediaType gt application xrds xml lt MediaType gt lt URI priority 10 gt http resolve example com lt URI gt lt URI priority 15 gt http resolve2 example com lt URI gt lt URI gt https resolve example com lt URI gt lt Service gt lt OpenID 2 0 login service gt lt Service priority 10 gt lt Type gt http specs openid net auth 2 0 signon lt Type gt lt URI gt http www myopenid com server lt URI gt lt LocalID gt http example myopenid com lt LocalID gt lt Service gt lt OpenID 1 0 login service gt lt Service priority 20 gt lt Type gt http openid net server 1 0 lt Type gt lt URI gt http www livejournal com openid server bml lt URI gt lt openid Delegate gt http www livejournal com users example lt openid Delegate gt lt Service gt lt untyped service for access to files of media type JPEG gt lt Service priority 10 gt lt Type match null gt lt Path select true gt media pictures lt Path gt lt MediaType select true gt image jpeg lt MediaType gt lt URI append path gt http pictures example com lt URI gt lt Service gt lt XRD gt lt xrds XRDS gt Synonyms editXRDS documents can assert zero or more synonyms 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 editThe 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 editIn XRDS documents a service is identified using a URI or XRI Following are listings of well known service types 3 XRI resolution edit Common Name URI or XRI Source EstablishedAuthority Resolution xri res auth v 2 0 XRI Resolution 2 0 March 2005Proxy Resolution xri res proxy v 2 0 XRI Resolution 2 0 March 2005OpenID edit Common Name URI or XRI Source EstablishedOpenID 1 0 http openid net server 1 0 OpenID Authentication 2 0 Section 14 2 1 June 2005OpenID 1 1 http openid net server 1 1 OpenID Authentication 2 0 Section 14 2 1 May 2006OpenID 2 0 Standard Login http specs openid net auth 2 0 signon OpenID Authentication 2 0 Section 7 3 2 1 2 December 2007OpenID 2 0 OP Identifier Login http specs openid net auth 2 0 server OpenID Authentication 2 0 Section 7 3 2 1 1 December 2007OpenID Attribute Exchange 1 0 http openid net srv ax 1 0 OpenID Attribute Exchange 1 0 Section 2 December 2007OAuth discovery edit Common Name URI or XRI Source EstablishedOAuth Discovery http oauth net discovery 1 0 OAuth Discovery Draft 2 March 2008Licensing editXRDS 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 editLight weight Identity Social WebReferences edit XRI Resolution 2 0 docs oasis open org Retrieved 2023 02 23 Final OpenID Authentication 2 0 Final openid net Retrieved 2023 02 23 Announcing xrdstype net Gabe Wachob Retrieved 2023 02 23 External links editOASIS XRI Technical Committee Retrieved from https en wikipedia org w index php title XRDS amp oldid 1141097287, wikipedia, wiki, book, books, library,
