Extensible Resource Descriptor (XRD) Version 1.0

Working Draft 11

17 December 2009

Specification URIs:
This Version:
http://docs.oasis-open.org/xri/xrd/v1.0/wd11/xrd-1.0-wd11.xml (Authoritative)
Previous Version:
http://docs.oasis-open.org/xri/xrd/v1.0/wd10/xrd-1.0-wd10.xml (Authoritative)
Latest Version:
http://docs.oasis-open.org/xri/xrd/v1.0/xrd-1.0.xml (Authoritative)
Technical Committee:
OASIS Extensible Resource Identifier (XRI) TC
Peter Davis, NeuStar Inc.
Drummond Reed, XDI.org
Eran Hammer-Lahav
Will Norris, Internet2
Related Work:

This specification replaces or supersedes:

This specification is related to:

Declared XML Namespace:

This document defines XRD, a simple generic format for describing and discovering resources.


This document was last revised or approved by the XRI Technical Committee on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at http://www.oasis-open.org/committees/xri.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/xri/ipr.php).

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/xri.


Copyright İ OASIS Open 2009. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.


OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Final Deliverable, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this deliverable.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this OASIS Final Deliverable by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this OASIS Final Deliverable. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this OASIS Final Deliverable or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Final Deliverable, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

Table of Contents

1. Introduction
1.1. Terminology
1.2. Normative References
1.3. Non-Normative References
1.4. Schema Organization and Namespaces
1.5. Common Data Types
1.5.1. String Values
1.5.2. URI Values
1.5.3. Time Values
2. XRD Document Structure
2.1. XRD Elements
2.1.1. Element <XRD>
2.1.2. Element <Expires>
2.1.3. Element <Subject>
2.1.4. Element <Alias>
2.1.5. Element <Property>
2.2. Linked Resource Elements
2.2.1. Element <Link>
2.2.2. Element <Title>
3. XRD Extensibility
3.1. Identifier Extension
3.2. Schema Extension
4. Processing XRD Documents
4.1. Linked Resource Selection
5. XRD Signature
5.1. Signing Formats and Algorithms
5.2. References
5.3. Canonicalization
5.4. Transforms
5.5. KeyInfo
6. XRD Sequence
7. Conformance
7.1. XRD Consumer
7.2. XRD Provider


A. Acknowledgments (Non-Normative)
B. XRD Examples (Non-Normative)
C. Media Type Definition for application/xrd+xml (Non-Normative)
D. Revision History (Non-Normative)

1. Introduction

This document defines XRD, a simple generic format for describing resources. Resource descriptor documents provide machine-readable information about resources (resource metadata) for the purpose of promoting interoperability, and assist in interacting with unknown resources that support known interfaces.

For example, a web page about an upcoming meeting can provide in its descriptor document the location of the meeting organizer's free/busy information to potentially negotiate a different time. The descriptor for a social network profile page can identify the location of the user's address book as well as accounts on other sites. A web service implementing an API protocol can advertise which of the protocol's optional components are supported.

1.1. Terminology

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC 2119].

1.2. Normative References

[Exclusive Canonicalization] J. Boyer, D. Eastlake, J. Reagle Exclusive XML Canonicalization . W3C Recommendation. 2002

[RFC 2046] N. Freed, N. Borenstein Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types . IETF (Internet Engineering Task Force). 1996.

[RFC 2119] S. Bradner Key words for use in RFCs to Indicate Requirement Levels . IETF (Internet Engineering Task Force). 1997.

[RFC 3023] M. Murata, S. St. Laurent, D. Kohn XML Media Types. IETF (Internet Engineering Task Force). 2001.

[RFC 4288] N. Freed, J. Klensin Media Type Specifications and Registration Procedures . IETF (Internet Engineering Task Force). 2005.

[Web Linking] M. Nottingham Web Linking . IETF (Internet Engineering Task Force) Draft. 2009.

[XML 1.0] T. Bray, J. Paoli, C. Sperberg-McQueen, E. Maler, F. Yergeau Extensible Markup Language (XML) 1.0 W3 Recommendation. 2008

[XML Schema] H. Thompson, D. Beech, M. Maloney, N. Mendelsohn XML Schema Part 1: Structures Second Edition . W3C Recommendation. 2004

[XML Schema Datatypes] P. Biron, A. Malhotra XML Schema Part 2: Datatypes Second Edition . W3 Recommendation. 2004

[XML Signature] D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler XML Signature Syntax and Processing . W3 Recommendation. 2008

[xml:id] J. Marsh, D. Veillard, N. Walsh xml:id. W3 Recommendation. 2005

1.3. Non-Normative References

[Atom 1.0] M. Nottingham, R. Sayre The Atom Syndication Format . IETF (Internet Engineering Task Force). 2005.

[HTML 4.01] D. Raggett, A. Le Hors, I. Jacobs HTML 4.01 Specification. W3C Recommendation. 1999

[XRI Resolution 2.0] G. Wachob, D. Reed, L. Chasen, W. Tan, S. Churchill Extensible Resource Identifier (XRI) Resolution V2.0 . February 2008.

1.4. Schema Organization and Namespaces

The XRD document structure is defined in a schema associated with the following XML namespace:


The schema for [XML 1.0] (the "xml:" namespace) is imported into the XRD schema, which is associated with the following XML namespace:


The following [XML Schema] fragment defines the XML namespaces and other header information for the XRD schema:

<schema targetNamespace="http://docs.oasis-open.org/ns/xri/xrd-1.0"

    <import namespace="http://www.w3.org/XML/1998/namespace"

            Document identifier: xrd-schema-1.0
            Location: http://docs.oasis-open.org/xri/xrd/v1.0/

The location of the normative XML Schema file for an XRD document as defined by this specification is: http://docs.oasis-open.org/xri/xrd/v1.0/wd11/xrd-1.0-wd11.xsd

The following URI will always reference the latest version of this file: http://docs.oasis-open.org/xri/xrd/v1.0/xrd-1.0.xsd

1.5. Common Data Types

The following sections define how to use and interpret common data types that appear throughout the XRD schema.

1.5.1. String Values

All XRD string values have or extend the type xs:string, which is built in to the W3C [XML Schema Datatypes] specification. Unless otherwise noted in this specification or particular profiles, all strings in XRD documents MUST consist of at least one non-whitespace character (whitespace is defined in section 2.3 of [XML 1.0]).

The following schema fragment defines the xrd:string complex type, which extends xs:string to allow for arbitrary attributes (see Section 3.2, “Schema Extension”):

<complexType name="string">
        <extension base="string">
            <anyAttribute namespace="##other" processContents="lax"/>

1.5.2. URI Values

All XRD URI reference values have or extend the type xs:anyURI, which is built in to the W3C [XML Schema Datatypes] specification. Unless otherwise noted in this specification or particular profiles, all URIs in XRD documents MUST consist of at least one non-whitespace character.

The following schema fragment defines the xrd:anyURI complex type, which extends xs:anyURI to allow for arbitrary attributes (see Section 3.2, “Schema Extension”):

<complexType name="anyURI">
        <extension base="anyURI">
            <anyAttribute namespace="##other" processContents="lax"/>

1.5.3. Time Values

All XRD time values have the type xs:dateTime, which is built in to the W3C [XML Schema Datatypes] specification, and MUST be expressed in UTC form, with no time zone component (represented by the UTC 'Z' timezone). XRD providers MUST NOT generate time instants that specify leap seconds.

2. XRD Document Structure

XRD provides a simple and extensible XML format for describing resources. An XRD document may describe the properties of the resource itself, as well as the relations the resource has with other resources. XRD builds directly on the typed link relations framework defined by [Web Linking], and used by [HTML 4.01], [Atom 1.0], and other protocols.

The XRD schema defines only the elements necessary to support the most common use cases, with the explicit intention that applications will extend XRD as defined in Section 3, “XRD Extensibility” to include any other metadata about the resources and links they describe.

2.1. XRD Elements

The XRD elements provide information about the resource described by the XRD document and list its properties. They also provide administrative information as to how the document should be cached, as well as information necessary for the authentication and trust verification of the XRD document.

2.1.1. Element <XRD>

The <XRD> element encapsulates the entire resource descriptor, and is most commonly the root element of the document. It contains the following attributes and elements:

xml:id [Optional]

This attribute, of type xs:ID, is defined by [xml:id]. It provides a unique identifier for this XRD, and is most commonly used as a signature reference.

<Expires> [Zero or One]

Specifies when this document expires, as described in Section 2.1.2, “Element <Expires>.

<Subject> [Zero or One]

Provides the identifier of the resource described by this XRD. See Section 2.1.3, “Element <Subject>.

<Alias> [Zero or More]

Provides an additional identifier for the resource described by this XRD. See Section 2.1.4, “Element <Alias>.

<Property> [Zero or More]

Declares a property of the resource described by this XRD, as described in Section 2.1.5, “Element <Property>.

<Link> [Zero or More]

Identifies another resource which is related to the resource described by this XRD, and describes the semantics of that relation. See Section 2.2.1, “Element <Link>.

<ds:Signature> [Zero or More]

This is an XML Signature, included from the [XML Signature] schema, that protects the integrity of the document, as described in Section 5, “XRD Signature”.

Although [XML Signature] allows a single document to contain multiple signatures, the signing profile described in Section 5, “XRD Signature” requires only a single <Signature> element. Use of multiple <Signature> elements in an XRD document is therefore undefined. In order to aid certain types of XRD consumers, it is RECOMMENDED that XRD providers place the <Signature> element of a signed XRD as near the beginning of the document as possible.

The following schema fragment defines the <XRD> element and its XRDType complex type:

<element name="XRD" type="xrd:XRDType"/>
<complexType name="XRDType">
        <element ref="xrd:Expires" minOccurs="0"/>
        <element ref="xrd:Subject" minOccurs="0"/>
        <choice minOccurs="0" maxOccurs="unbounded">
            <element ref="xrd:Alias"/>
            <element ref="xrd:Property"/>
            <element ref="xrd:Link"/>
            <any namespace="##other" processContents="lax"/>
    <attribute ref="xml:id" use="optional"/>
    <anyAttribute namespace="##other" processContents="lax"/>

2.1.2. Element <Expires>

This dateTime value indicates the time instant after which the document is no longer valid. The value MUST use the UTC "Z" time zone, as specified in Section 1.5.3, “Time Values”, and MUST NOT use fractional seconds. The semantics of this element apply to the metadata available in the XRD document and are independent of the caching semantics of any transport protocol used to retrieve the document.

The following schema fragment defines the <Expires> element and its ExpiresType complex type:

<element name="Expires" type="xrd:ExpiresType"/>
<complexType name="ExpiresType">
        <extension base="dateTime">
            <anyAttribute namespace="##other" processContents="lax"/>

2.1.3. Element <Subject>

<Subject> is a URI value which identifies a resource. This value MUST be an absolute URI. If <Subject> is not specified, it is expected that the resource described by this XRD will be identified by other means.

The following schema fragment defines the <Subject> element.

<element name="Subject" type="xrd:anyURI"/>

2.1.4. Element <Alias>

This URI value provides an additional identifier for the resource described by the XRD. This value MUST be an absolute URI. The <Alias> element does not identify additional resources the XRD is describing, but rather provides additional identifiers for the same resource.

The following schema fragment defines the <Alias> element:

<element name="Alias" type="xrd:anyURI"/>

2.1.5. Element <Property>

The <Property> element declares a property of a resource or link relation, expressed as a key-value pair. The key is identified by the type attribute, and the value expressed as the string content of the <Property> element. A Property MAY have no value if the type identifier alone is sufficient. <Property> elements that contain no value MUST include the xsi:nil attribute with a value of true as defined in [XML Schema]. <Property> contains the following attributes:

type [Required]

The type attribute is an absolute URI that identifies the property being declared. This URI value is application-specific, and is used by the XRD provider to declare a property to consumers familiar with the type identifier.

The following schema fragment defines the <Property> element and its PropertyType complex type:

<element name="Property" type="xrd:PropertyType" nillable="true"/>
<complexType name="PropertyType">
        <extension base="xrd:string">
            <attribute name="type" type="anyURI" use="required"/>

2.2. Linked Resource Elements

One of the primary uses of XRD is to describe the relations the resource described by the XRD has with other resources. The following elements identify and describe these related resources.

2.2.1. Element <Link>

The <Link> element serves as a container for metadata about a relation to a related resource, and carries similar semantics as the [HTML 4.01] Link element, the [Atom 1.0] Link element, and the HTTP Link Header. The one distinction is that link relations described by the <Link> element are between the resource described by the XRD (referred to as the context resource by [Web Linking]) and the linked resources (referred to as the target resource by [Web Linking]), and not between the XRD document itself and the linked resource. <Link> has the following elements and attributes:

rel [optional]

This URI value defines the semantics of the relation between the resource described by the XRD and the linked resource. The rel attribute is semantically and syntactically equivalent to the Link Relation Types defined in [Web Linking], with the exception that it only allows for a single relation type and does not allow for multiple space delimited values. It is important to note that this value does not identify any property of the linked resource. Rather, it describes only how the linked resource is related to the resource described by the XRD.

type [optional]

This string value provides a hint as to what the media type of the linked resource should be. The value of this attribute MUST be of the form of a media type defined in [RFC 2046]. The IANA media types registry can be found at http://www.iana.org/assignments/media-types/. Note that this is only a hint and does not override the media type declared by the linked resource itself (e.g. the HTTP Content-Type header of a HTTP response obtained by following the link).

href [optional]

The href attribute provides the URI of the linked resource. If no href attribute is defined, it is assumed the URI can be obtained from a template attribute or by other means outside the scope of this specification.

A <Link> element MAY contain an href attribute or a template attribute, but MUST NOT contain both.

template [optional]

The template attribute provides a URI template which can be used to obtain the URI of the linked resource. Templates provide a mechanism for URI construction, taking a list of variables as input, and producing a URI string as an output. The template syntax and vocabulary are determined by the application through which the XRD document is obtained and processed, and MAY be specific to the link relation type indicated by the rel attribute of the corresponding <Link> element. Applications utilizing the template mechanism must define the template syntax and processing rules (including error handling) as well as the variable vocabulary.

A <Link> element MAY contain an href attribute or a template attribute, but MUST NOT contain both.

<Title> [Zero or More]

Provides a human-readable description of the linked resource. See Section 2.2.2, “Element <Title>.

<Property> [Zero or More]

Declares a property of this link relation, as described in Section 2.1.5, “Element <Property>. It is important to note that this value does not identify any property of the linked resource or the resource described by the XRD, but rather of the link relation between the linked resources.

The following schema fragment defines the <Link> element and its LinkType complex type:

<element name="Link" type="xrd:LinkType"/>
<complexType name="LinkType">
    <choice minOccurs="0" maxOccurs="unbounded">
        <element ref="xrd:Title"/>
        <element ref="xrd:Property"/>
        <any namespace="##other" processContents="lax"/>
    <attribute name="rel" type="anyURI" use="optional"/>
    <attribute name="type" type="string" use="optional"/>
    <attribute name="href" type="anyURI" use="optional"/>
    <attribute name="template" type="string" use="optional"/>
    <anyAttribute namespace="##other" processContents="lax"/>

2.2.2. Element <Title>

This string value provides a human-readable description for the linked resource. The semantics of this value are intended only for human consumption and MUST NOT be used to imply any additional meaning. <Title> contains the following attributes:

xml:lang [Optional]

This attribute is defined by the [XML 1.0] specification, and is used to identify the natural language in which this element's content is written.

The following schema fragment defines the <Title> element and its TitleType complex type:

<element name="Title" type="xrd:TitleType"/>
<complexType name="TitleType">
        <extension base="xrd:string">
            <attribute ref="xml:lang" use="optional"/>

3. XRD Extensibility

The XRD schema defines only the elements necessary to support the most common use cases, with the explicit intention that applications will extend XRD to include any other metadata about the resources they describe. XRD documents can be extended by providing custom, meaningful values for certain URI-based elements, as well as by extending the XML elements directly.

3.1. Identifier Extension

XRD uses URI-based identifiers for describing resources as well as for describing the relations between resources. It is expected that applications will use appropriate established URI identifiers for these purposes, or define new identifiers as necessary. It is RECOMMENDED that any new identifiers be defined in a formal specification of use. In no case should the meaning of a given URI used as such an identifier significantly change, or be used to mean two different things.

New relation types between resources MUST follow the extensibility and registration requirements defined in [Web Linking].

3.2. Schema Extension

The XRD schema allows for the inclusion of attributes from arbitrary namespaces (except for the XRD namespace) in almost all XRD elements. Additionally, the <XRD> and <Link> elements allow for the inclusion of child elements from arbitrary namespaces (except for the XRD namespace).

XML extensions MUST NOT require new interpretation of elements defined in this document. If an extension attribute or element is present, an XRD consumer MUST be able to ignore it and still correctly process the XRD document.

4. Processing XRD Documents

Once an XRD document has been obtained, the consumer typically inspects the list of resource properties looking for known values, and performs resource selection to find the links relevant to it. The selection process involves iterating through the list of linked resource descriptions and filtering them based on various metadata.

4.1. Linked Resource Selection

Link selection criteria is determined by the XRD consumer's needs, and is based on the presence, absence, or value of the <Link> element attributes or child elements. The selection criteria is usually based on the value of the rel attribute with the value of the type attribute used as a hint (helping to determine if the linked resource uses a familiar media type).

Selection based on multiple criteria can be handled by performing multiple selections. Each selection is assigned preference order based on the consumer's needs, and the selection results are compared to determine the most desired set. For example, an XRD consumer processing an XRD document describing an article may wish to select linked resources about the article's author. If that consumer prefers HTML documents over plain text, then the linked resource selection would occur in two steps. First, all links with the 'author' relation type would be selected, and if more than one are found, then the most appropriate link would be selected based on its media type.

If multiple <Link> elements are matched by a given selection criteria, they MUST be processed in the order in which they appear in the XRD document. Therefore, XRD providers MAY indicate element priority by placing them in a specific order. If the first <Link> is subsequently disqualified from the set of selected elements, the consumer SHOULD attempt to select the next qualified element in document order. This process SHOULD be continued for all other qualified <Link> elements until success is achieved or all elements are exhausted.

5. XRD Signature

An XRD provider MAY digitally sign an XRD document in order to enable XRD consumers to verify the authenticity and integrity of the document. The [XML Signature] specification defines a general XML syntax for signing data that includes many options for flexibility. This section details constraints on these options so that XRD consumers do not have to implement the full generality of XML Signature processing.

5.1. Signing Formats and Algorithms

While XML Signature has three ways of relating a signature to a document (enveloping, enveloped, and detached), XRD documents MUST use enveloped signatures when signing. Any algorithm defined for use with the XML Signature specification MAY be used.

5.2. References

XRD documents MUST supply a value for the xml:id attribute on the root element of the XRD being signed. The XRD's root element may or may not be the root element of the actual XML document containing the signed XRD (e.g., it might be included within another document schema).

Signatures MUST contain a single <ds:Reference> containing a same-document reference to the xml:id attribute value of the root element of the XRD being signed. For example, if the xml:id attribute value is foo, then the URI attribute in the <ds:Reference> element MUST be #foo.

5.3. Canonicalization

XRD implementations MUST use [Exclusive Canonicalization] without comments, both in the <ds:CanonicalizationMethod> element of <ds:SignedInfo>, and as a <ds:Transform> algorithm. Use of Exclusive Canonicalization facilitates the verification of signatures created over XRD instances when placed into a different XML context than present during signing.

Note that use of this algorithm alone does not guarantee that a particular signed object can be moved from one context to another safely, nor is that a requirement of signed XRD instances in general, though it MAY be required by particular profiles.

5.4. Transforms

Signatures in XRD documents MUST NOT contain transforms other than the enveloped signature transform (with the identifier http://www.w3.org/2000/09/xmldsig#enveloped-signature) or the exclusive canonicalization transform (with the identifier http://www.w3.org/2001/10/xml-exc-c14n#).

5.5. KeyInfo

XML Signature defines usage of the <ds:KeyInfo> element. XRD does not require the use of <ds:KeyInfo>, nor does it impose any restrictions on its use. Therefore, <ds:KeyInfo> MAY be absent.

6. XRD Sequence

In cases where an application requires a sequence of <XRD> elements in a single XML document, this specification defines an alternate top-level element, <XRDS>. Its semantics are very simple: it contains a sequence of <XRD> elements, one optional attribute, and is not otherwise extensible.

ref [Optional]

This attribute, of type xs:anyURI, identifies the resource described by the sequence of <XRD> elements.

<XRD> [Zero or More]

See Section 2.1.1, “Element <XRD>.

The following schema fragment defines the <XRDS> element and its XRDSType complex type:

<element name="XRDS" type="xrd:XRDSType"/>
<complexType name="XRDSType">
        <element ref="xrd:XRD" minOccurs="0" maxOccurs="unbounded"/>
    <attribute name="ref" type="anyURI"/>

IMPORTANT: In past practice, <XRDS> was often used as the root element even if it contained only a single <XRD>. That practice is now deprecated. The <XRDS> element SHOULD NOT be used unless it contains a sequence of two or more <XRD> elements.

7. Conformance

An implementation is a conforming XRD consumer if the implementation meets the conditions in Section 7.1, “XRD Consumer”. An implementation is a conforming XRD provider if the implementation meets the conditions in Section 7.2, “XRD Provider”. An implementation may serve as both an XRD consumer and provider.

7.1. XRD Consumer

An implementation conforms to this specification as an XRD consumer if it meets the following conditions:

  1. It MUST implement parsing of XRD documents which conform to the XRD schema as specified in Section 2, “XRD Document Structure”.

  2. It MUST conform to the processing rules as specified in Section 4, “Processing XRD Documents”.

  3. In calculating XRD Signatures, it SHOULD support the use of RSA signing and verification for public key operations in accordance with the signing algorithm identified by http://www.w3.org/2000/09/xmldsig#rsa-sha256.

7.2. XRD Provider

An implementation conforms to this specification as an XRD provider if it meets the following conditions:

  1. Any published XRD documents MUST conform to the XRD schema as specified in Section 2, “XRD Document Structure”.

  2. Any published XRD documents that are digitally signed using [XML Signature] MUST conform to the signature profile specified in Section 5, “XRD Signature”.

A. Acknowledgments (Non-Normative)

The editors would like to thank the following current and former members of the OASIS XRI TC for their particular contributions to this and previous versions of this specification:

  • Dirk Balfanz, Google

  • Bill Barnhill, Booz Allen Hamilton

  • John Bradley

  • Scott Cantor, Internet2

  • Les Chasen, NeuStar

  • Steven Churchill, XDI.org

  • Brian Eaton, Google

  • George Fletcher, AOL

  • Victor Grey, Planetwork

  • Joseph Holsten

  • Nika Jones

  • Breno de Medeiros, Google

  • Bob Morgan, Internet2

  • Markus Sabadello, XDI.org

  • Nat Sakimura, NRI

  • Tatsuki Sakushima, NRI

  • William Tan, NeuStar

  • Gabe Wachob

The editors would also like to acknowledge the contributions of the other members of the OASIS XRI Technical Committee, whose other voting members at the time of publication were:

  • Giovanni Bartolomeo, University of Rome "Tor Vergata"

  • Owen Davis, Planetwork

  • Jeff Hodges

  • Fen Labalme, Planetwork

  • Ben Laurie, Google

  • XiaoDong Lee, China Internet Network Information Center

  • Nick Nicholas, Australian Department of Education

  • Marty Schleiff, The Boeing Company

  • Paul Trevithick

B. XRD Examples (Non-Normative)

Example B.1. Simple XRD Example

<XRD xmlns="http://docs.oasis-open.org/ns/xri/xrd-1.0">
  <Property type="http://spec.example.net/type/person" xsi:nil="true" />
  <Link rel="http://spec.example.net/auth/1.0"
    href="http://services.example.com/auth" />
  <Link rel="http://spec.example.net/photo/1.0" type="image/jpeg"
    <Title xml:lang="en">User Photo</Title>

Example B.2. Signed XRD Example

Following is an example of a signed XRD document. Line breaks have been added for readability; the signatures are not valid and cannot be successfully verified.

<XRD xmlns="http://docs.oasis-open.org/ns/xri/xrd-1.0" xml:id="foo">
  <Property type="http://spec.example.net/version">1.0</Property>
  <Property type="http://spec.example.net/version">2.0</Property>
  <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
      <ds:Reference URI="#foo">
          <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
            <InclusiveNamespaces PrefixList="#default xrd ds xs xsi"
        <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
  <Link rel="http://spec.example.net/auth/1.0"
    href="http://services.example.com/auth" />

C. Media Type Definition for application/xrd+xml (Non-Normative)

This section is prepared in anticipation of filing a media type registration meeting the requirements of [RFC 4288].

Type name:


Subtype name:


Required parameters:


Optional parameters:

"charset": This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in [RFC 3023].

Encoding considerations:

Identical to those of application/xml as described by [RFC 3023] section 3.2.

Security considerations:

As defined in this specification. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC 3023], Section 10.

Interoperability considerations:

There are no known interoperability issues.

Published specification:

This specification

Applications that use this media type:

No known applications currently use this media type.

Magic Number:

As specified for [RFC 3023] section 3.2.

File Extension:


Fragment Identifiers:

As specified for [RFC 3023] section 5.

Base URI:

As specified for [RFC 3023] section 6.

Macintosh File Type code:


Person & email address to contact for further information:

Eran Hammer-Lahav, eran@hueniverse.com

Intended usage:


Author / Change controller:

OASIS XRI Technical Committee

D. Revision History (Non-Normative)

Table D.1. 

RevisionDateEditorChanges Made
Working Draft 1117 December 2009willnorris
  • Clarify that XRD Signatures must use Exclusive Canonicalization without comments.

Working Draft 1019 November 2009willnorris
  • Replace Type element with Property, which allows for a key-value pair. Add Property as a child element of Link

  • Change Rel, MediaType, URI, and URITemplate elements to be attributes of Link named rel, type, href, and template respectively.

  • Fix cardinality of XRD child elements of XRDS.

  • Additional text to clarify intended use of Subject, Alias, and Property elements, as well as type attribute.

  • Links MUST NOT contain both 'uri' and 'template' attributes.

  • Focus link selection on 'rel', using 'type' only as a useful hint.

  • Replace text about ignoring links with unknown template syntax with instructions to follow the protocol-specific rules on handling bad templates

  • Update examples to reflect new schema and demonstrate use of a few more elements.

Committee Draft 0122 October 2009willnorris
  • Approved by the XRI Technical Committee as Committee Draft 01.

Working Draft 0915 October 2009willnorris
  • Cleanup references section (some where no longer referenced at all, some were only informative).

  • Fix acknowledgements to properly include XRI Resolution 2.0 editors

Working Draft 0814 October 2009willnorris
  • Remove "Subject" "ds:keyInfo" as child elements of Link. These only had clear meaning in the context of a linked XRD.

  • Remove default URI template syntax and change text to make it application+relation specific

  • Clarified that rel values are not allowed to contain space-delimited relation types

Working Draft 0712 October 2009willnorris
  • Remove "Extensions" element. Revert to previous extension model, resolving the "ambiguous schema" issue by simply not defining the signature elements in the XRD schema.

  • Add "Title" element under "Link" for human readable name of linked resource

  • Add signature algorithm support to conformance

  • Greatly reduce complexity of Link element. Reduce cardinality of Rel, MediaType, URI, and URITemplate elements to zero or one. URI or URITemplate is allowed, but not both. Processing section updated to reflect these changes.

  • Remove definition of linked XRD documents.

  • Various minor editorial changes

Working Draft 0604 September 2009willnorris
  • Combine "Document Property Elements" and "Resource Property Elements" into "XRD Elements"

  • Move schema and references to first section

  • Promote "XRD Extensions" section, and move schema fragment

  • Add example for URI / URITemplate processing order

  • Move XRD Example into an appendix

  • Various minor rewording

Working Draft 0501 September 2009willnorris
  • Remove priority attribute on Link, URI, and URITemplate elements. Instead, element priority is implied by document order. Additionally, requirement for consumers to respect priority strengthened from "should" to "must".

  • New "Extensions" element added to XRD and Link elements as the sole location to extend XRD with arbitrary child elements.

  • Define "XRDS" element to contain a sequence of XRD elements.

  • Removed "match" attribute from Subject.

  • Added requirement to follow normal rules for Rel values (either use a URI, or register value with IANA)

  • Switched from Relax NG to XSD as the authoritative schema language for the XRD Schema. (Primarily due to the lack of a Relax NG schema for XML DSig)

  • Clarify language regarding URIs and URI Templates

  • Define "Common Data Types" for XRD

  • Various minor editorial and grammatical changes

Working Draft 0412 August 2009willnorris
  • Remove XRD Trust section, pushing that work to separate trust profiles. Move XRD Signature section up one level.

  • Remove requirement for explicit Link Subject on linked XRDs

  • Use non-information URI for rel value to designate linked XRD

  • Flesh out subject matching rules

  • Remove "must not be used" from Expires element description

Working Draft 0304 August 2009willnorris
  • Revert to previous processing flow for related resources -- first filter, then sort by priority

  • Add media type definition for "application/xrd+xml"

  • Clarify text for URI templates

  • Strengthen requirement to use excl-c14n from "should" to "must"

  • Move Signature element to bottom of the document for readability

  • Add conformance section

  • Add "match" attribute to Subject element. Also add stub section for subject matching.

  • Add XSD schema (in addition to RELAX NG)

  • Various editorial and grammatical changes.

Working Draft 0203 July 2009willnorris
  • Remove XRD Trust namespace and elements (TargetSubject replaced by Subject, TargetAuthority replaced by ds:KeyInfo)

  • Section added for XML Digital Signature, primarily copied from SAML 2.0, which changes as necessary

  • Language clarified on priority attribute values ('null' is not a valid value)

  • Add section for XRD Extensibility

  • Only require XML element order for elements with cardinality of "zero or one"

  • Add section for defining linked XRD documents

  • Processing rules changed for related resources to first sort by priority, then filter. Also add processing rule for linked XRD documents.

  • Various editorial and grammatical changes.

Working Draft 0109 May 2009willnorrisInitial Publication