OASIS Extensible Resource Identifier (XRI) TC
Defining a syntax for abstract structured identifiers to share semantics across different URI schemes, domains, and applications (XRI); plus defining a simple XML format for uniform metadata discovery for all URIs (XRD)
Completed:
The Technical Committee was closed by OASIS TC Administration on 08 July 2015 and is no longer active. Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.Table of Contents
- Announcements
- Overview
- Subcommittees
- Technical Work Produced by the Committee
- External Resources
- Mailing Lists and Comments
5 April 2010:The XRI TC began a 30-day public review of Extensible Resource Descriptor (XRD) 1.0 Committee Draft 02. It is available in HTML and PDF formats. Comments are welcome - please see the full public announcement for more details.
7 November 2009:The XRI TC began a 60-day public review of Extensible Resource Descriptor (XRD) 1.0 Committee Draft 01. It is available in HTML and PDF formats. This new simple XML format supercedes the XRDS format defined in XRI 2.0. Comments are welcome - please see the full public announcement for more details.
15 November 2008: The XRI TC commenced work on its third generation of specifications with a face-to-face meeting. The XRI 3.0 specification will address concerns about XRI 2.0 raised by the W3C TAG. In addition they will include a new standalone specification for XRD 1.0, a simple XML format uniform metadata discovery for both URIs and XRI based on the XRDS format defined in XRI 2.0.
The purpose of this TC is to define a syntax for abstract structured identifiers -- identifiers that can be used within other URI schemes (such as http: and https: URIs) to share semantics across any number of domains and applications. The TC is also defining a simple XML descriptor format and HTTP(S) protocol for uniform resource metadata discovery.
The XRI Syntax specification is based on the URI (Uniform Resource Identifier) specification, RFC 3986, and the IRI (Internationalized Resource Identifier) specification, RFC 3987.
For more information, see the TC Charter and FAQ
See also the Wikipedia articles on XRI and XRDS.
- XRI Editors SC (no longer active) (9 members, 28 documents)
Technical Work Produced by the Committee
14 April 2008: The XRI TC published updated editions (in the new OASIS template format) of the XRI Syntax 2.0 Committee Specification originally approved 14 November 2005. It is available in the following formats:
14 April 2008: The XRI TC announced the XRI Resolution 2.0 Committee Specification. It is available in the following formats:
11-March-2008: The XRI TC published Committee Draft 03 of XRI Resolution 2.0 and began a 15-day public review. NOTE: This has been superceded by the XRI Resolution 2.0 Committee Specification 02 referenced above.
2-December-2007: The XRI TC published Committee Draft 02 of XRI Resolution 2.0 and began a 60-day public review. NOTE: This has been superceded by the XRI Resolution 2.0 Committee Specification 03 referenced above.
19-March-2006: The XRI TC published Working Draft 10 of XRI Resolution 2.0. NOTE: This has been superceded by the XRI Resolution 2.0 Committee Specification 02 referenced above.
14-November-2005: The XRI TC approved XRI Syntax 2.0 as a Committee Specification. NOTE: This has been superceded by the newer edition of this specification (in the new OASIS template format) referenced above.
15-March-2005: The XRI TC approved the following specifications as Committee Drafts and submitted them for public review.
- XRI Syntax V2.0 Committee Draft 01defines
the normative ABNF grammar for XRIs, transformations from XRIs into
IRIs and URIs, relative XRI references, and normalization/comparison. NOTE: This has been superceded by the XRI Syntax 2.0 Committee Specification referenced above.
- XRI Resolution V2.0 Committee Draft 01
defines an HTTP/HTTPS-based resolution protocol for XRIs, including
both generic and trusted resolution. The latter uses SAML assertions
based on the new SAML 2.0 specifications. NOTE: This has been superceded by the XRI Resolution 2.0 Committee Draft 03 specification referenced above.
- XRI Metadata V2.0 Committee Draft 01
defines four namespaces under the XRI global context symbol "$" for
common types of identifier metadata, including language tags, date/time
stamps, version identifiers, and annotations. NOTE: This is being further revised to incorporate public feedback.
- Introduction to XRIs Working Draft 04 is a non-normative introduction to the uses and features of XRIs. This work-in-progress is intended to serve as an entry point for the XRI 2.0 suite. The XRI TC encourages feedback and input on this document from other OASIS members. NOTE: This has been superceded by the XRI 2.0 FAQ – see the 1-December-2005 announcement above.
Wiki for OASIS XRI TC member collaboration
Although not produced by the OASIS XRI TC, the following information offers useful insights into its work.
IDtrust XML.org is a community-driven site hosted by OASIS that provides reliable background information on the standard. The site also serves as a community bulletin board and directory where readers post news, ideas, opinions, and recommendations. It incorporates wiki functionality to let users edit and add new pages to the site. The public is encouraged to contribute content.
OpenID Discovery Using XRI and XRDS.
ACM Paper given at the 7th Annual IDtrust Symposium, 4 March 2008
OASIS TC Promotes Extensible Resource Identifier (XRI) Specification.
Cover Pages, 19 January 2004
Call for Public Review of Draft Extensible Resource Identifier (XRI) Specification.
CoverPages, 4 August 2003
xri: the list used by TC members to conduct Committee work. TC membership required to post. TC members are automatically subscribed; the public may view archives.
xri-comment: a public mail list for providing input to the OASIS xri Technical Committee members. Send a comment or view archives.
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.