Working Draft 12
XX January 2010
- Specification URIs:
- This Version:
- http://docs.oasis-open.org/xri/xrd/v1.0/wd12/xrd-1.0-wd12.xml
(Authoritative)
http://docs.oasis-open.org/xri/xrd/v1.0/wd12/xrd-1.0-wd12.html
http://docs.oasis-open.org/xri/xrd/v1.0/wd12/xrd-1.0-wd12.pdf
- Technical Committee:
- OASIS Extensible Resource Identifier (XRI) TC
- Chairs:
- Peter Davis, NeuStar Inc.
Drummond Reed, XDI.org
- Editors:
- Eran Hammer-Lahav
Will Norris, Internet2
- Status:
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.
- Notices:
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.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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
- 2. XRD Document Structure
- 3. XRD Extensibility
- 4. Processing XRD Documents
- 5. XRD Signature
- 6. XRD Sequence
- 7. Conformance
Appendixes
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.
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].
[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
[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.
The XRD document structure is defined in a schema associated with the following XML namespace:
http://docs.oasis-open.org/ns/xri/xrd-1.0
The schema for [XML 1.0] (the "xml:" namespace) is imported into the XRD schema, which is associated with the following XML namespace:
http://www.w3.org/XML/1998/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"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:xrd="http://docs.oasis-open.org/ns/xri/xrd-1.0"
elementFormDefault="unqualified"
attributeFormDefault="unqualified"
blockDefault="substitution"
version="1.0">
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<annotation>
<documentation>
Document identifier: xrd-schema-1.0
Location: http://docs.oasis-open.org/xri/xrd/v1.0/
</documentation>
</annotation>
...
</schema>
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/wd12/xrd-1.0-wd12.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.
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">
<simpleContent>
<extension base="string">
<anyAttribute namespace="##other" processContents="lax"/>
</extension>
</simpleContent>
</complexType>
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">
<simpleContent>
<extension base="anyURI">
<anyAttribute namespace="##other" processContents="lax"/>
</extension>
</simpleContent>
</complexType>
All XRD time values have the type xs:dateTime, which is built in
to the W3C [XML Schema Datatypes] specification. Time values
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.
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.
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 used as a signature reference.<Expires>[Zero or One]Specifies when this document expires. See Section 2.2, “Element
<Expires>”.<Subject>[Zero or One]Provides the identifier of the resource described by this XRD. See Section 2.3, “Element
<Subject>”.<Alias>[Zero or More]Provides an additional identifier for the resource described by this XRD. See Section 2.4, “Element
<Alias>”.<Property>[Zero or More]Declares a property of the resource described by this XRD. See Section 2.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.6, “Element
<Link>”.<ds:Signature>[Zero or More]This XML Signature, included from the [XML Signature] schema, 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"> <sequence> <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"/> </choice> </sequence> <attribute ref="xml:id" use="optional"/> <anyAttribute namespace="##other" processContents="lax"/> </complexType>
The <Expires> element contains a time value which specifies the
instant at and after which the document has expired and SHOULD NOT
be used. The value MUST be expressed in UTC form, 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. If present, any
cache expiration date specified by the transport protocol SHOULD NOT
be later than the time instant indicated by the <Expires> element.
The following schema fragment defines the <Expires> element and its
ExpiresType complex type:
<element name="Expires" type="xrd:ExpiresType"/> <complexType name="ExpiresType"> <simpleContent> <extension base="dateTime"> <anyAttribute namespace="##other" processContents="lax"/> </extension> </simpleContent> </complexType>
The <Subject> element contains 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"/>
The <Alias> element contains a URI value that is 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"/>
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> has the following
attributes:
type[Required]The
typeattribute 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"> <simpleContent> <extension base="xrd:string"> <attribute name="type" type="anyURI" use="required"/> </extension> </simpleContent> </complexType>
The <Link> element serves as a container for metadata about a
relation between the resource described by the XRD and a related resource.
This element 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.
The <Link> element contains the following attributes and elements:
rel[Optional]This URI value defines the semantics of the relation between the resource described by the XRD and the linked resource. This value MUST be an absolute URI or a registered relation type, as defined in [Web Linking].
The
relattribute 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 identifies the media type of the linked resource, and 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 Content-Type header of a HTTP response obtained by following the link).
href[Optional]The
hrefattribute provides the URI of the linked resource. If nohrefattribute is defined, it is assumed the URI can be obtained from atemplateattribute or by application-specific means.A
<Link>element MAY contain anhrefattribute or atemplateattribute, but MUST NOT contain both.template[Optional]The
templateattribute 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 therelattribute 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 anhrefattribute or atemplateattribute, but MUST NOT contain both.<Title>[Zero or More]Provides a human-readable description of the linked resource. See Section 2.7, “Element
<Title>”.<Property>[Zero or More]Declares a property of this link relation, as described in Section 2.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"/> </choice> <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"/> </complexType>
The <Title> element contains a string value that provides a
human-readable description for the linked resource. This value is intended only for human consumption
and MUST NOT be used by an XRD consumer to affect the processing of the
document. <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"> <simpleContent> <extension base="xrd:string"> <attribute ref="xml:lang" use="optional"/> </extension> </simpleContent> </complexType>
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.
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.
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.
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.
Link selection criteria is determined by the XRD consumer's needs, and
SHOULD be 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 SHOULD 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 matching element in document order. This process
SHOULD be continued for all other matching
<Link> elements until success is achieved or all elements are exhausted.
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.
XRD documents MUST use enveloped signatures as defined by [XML Signature] when signing. Any signature algorithm defined by [XML Signature] MAY be used.
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).
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.
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.
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#).
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>. This element SHOULD contain either
zero or more than one <XRD> elements. It has the following attributes and
elements, and is not otherwise extensible:
ref[Optional]This URI value identifies the resource described by the sequence of
<XRD>elements.<XRD>[Zero or More]
The following schema fragment defines the <XRDS> element and its
XRDSType complex type:
<element name="XRDS" type="xrd:XRDSType"/>
<complexType name="XRDSType">
<sequence>
<element ref="xrd:XRD" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="ref" type="anyURI"/>
</complexType>
An XML document is a conforming XRD document if it meets the conditions in Section 7.1, “XRD Document”. An implementation is a conforming XRD consumer if the implementation meets the conditions in Section 7.2, “XRD Consumer”. An implementation is a conforming XRD provider if the implementation meets the conditions in Section 7.3, “XRD Provider”. An implementation may serve as both an XRD consumer and provider.
An XML document conforms to this specification as an XRD document if it meets the following conditions:
It MUST be a well-formed XML document, as defined by [XML 1.0], and MUST validate against the normative XRD schema identified in Section 1.4, “Schema Organization and Namespaces”.
Documents that are digitally signed using [XML Signature] MUST conform to the signature profile specified in Section 5, “XRD Signature”.
An implementation conforms to this specification as an XRD consumer if it meets the following conditions:
It MUST implement parsing of conforming XRD documents, as defined in Section 7.1, “XRD Document”. Support for the
<XRDS>element is OPTIONAL.It MUST conform to the processing rules as specified in Section 4, “Processing XRD Documents”.
If an implementation supports XRD Signatures, it MUST 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.
An implementation conforms to this specification as an XRD provider if it meets the following conditions:
Any provided XRD document MUST meet the conditions in Section 7.1, “XRD Document”.
If an implementation supports XRD Signatures, it MUST 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.
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">
<Expires>1970-01-01T00:00:00Z</Expires>
<Subject>http://example.com/gpburdell</Subject>
<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"
href="http://photos.example.com/gpburdell.jpg">
<Title xml:lang="en">User Photo</Title>
<Title xml:lang="de">Benutzerfoto</Title>
<Property type="http://spec.example.net/created/1.0">1970-01-01</Property>
</Link>
</XRD>
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">
<Expires>1970-01-01T00:00:00Z</Expires>
<Subject>http://example.com/gpburdell</Subject>
<Alias>http://people.example.com/gpburdell</Alias>
<Alias>acct:gpburdell@example.com</Alias>
<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:SignedInfo>
<ds:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<ds:Reference URI="#foo">
<ds:Transforms>
<ds:Transform
Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<InclusiveNamespaces PrefixList="#default xrd ds xs xsi"
xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transform>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>TCDVSuG6grhyHbzhQFWFzGrxIPE=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
x/GyPbzmFEe85pGD3c1aXG4Vspb9V9jGCjwcRCKrtwPS6vdVNCcY5rHaFPYWkf+5
EIYcPzx+pX1h43SmwviCqXRjRtMANWbHLhWAptaK1ywS7gFgsD01qjyen3CP+m3D
w6vKhaqledl0BYyrIzb4KkHO4ahNyBVXbJwqv5pUaE4=
</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>
<ds:X509Certificate>
MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVT
MRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoT
F1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJ
bmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0Eg
LS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsx
CzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFy
Ym9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVk
dTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJj
IHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+
c2MZVeXeTgV3Yz+USLg2Y1on+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE
pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkq
hkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2n
qgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX
8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>
<Link rel="http://spec.example.net/auth/1.0"
href="http://services.example.com/auth" />
</XRD>
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:
application- Subtype name:
xrd+xml- Required parameters:
None
- 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/xmlas 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:
None.
- Fragment Identifiers:
As specified for [RFC 3023] section 5.
- Base URI:
As specified for [RFC 3023] section 6.
- Macintosh File Type code:
TEXT.
- Person & email address to contact for further information:
Eran Hammer-Lahav, eran@hueniverse.com
- Intended usage:
COMMON
- Author / Change controller:
OASIS XRI Technical Committee
D. Revision History (Non-Normative)
Table D.1.
| Revision | Date | Editor | Changes Made |
|---|---|---|---|
| Working Draft 12 | XX January 2010 | willnorris |
|
| Working Draft 11 | 17 December 2009 | willnorris |
|
| Working Draft 10 | 19 November 2009 | willnorris |
|
| Committee Draft 01 | 22 October 2009 | willnorris |
|
| Working Draft 09 | 15 October 2009 | willnorris |
|
| Working Draft 08 | 14 October 2009 | willnorris |
|
| Working Draft 07 | 12 October 2009 | willnorris |
|
| Working Draft 06 | 04 September 2009 | willnorris |
|
| Working Draft 05 | 01 September 2009 | willnorris |
|
| Working Draft 04 | 12 August 2009 | willnorris |
|
| Working Draft 03 | 04 August 2009 | willnorris |
|
| Working Draft 02 | 03 July 2009 | willnorris |
|
| Working Draft 01 | 09 May 2009 | willnorris | Initial Publication |