|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
OASIS - XRI SYNTAX
|
|
Title:
|
Extensible Resource Identifier (XRI) / 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)
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
An extensible resource identifier (abbreviated XRI) is a scheme and resolution protocol for abstract identifiers compatible with uniform resource identifiers and internationalized resource identifiers, developed by the XRI Technical Committee at OASIS. It has been used in several technical implementation of OpenID and consequently agreed that NGN Identity Management has a need for a syntax which abstract structured identifiers.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information is available in the OASIS archives at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri while the IPR policy describes at https://www.oasis-open.org/policies-guidelines/ipr .
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
See also at http://middleware.internet2.edu/idtrust/2008/papers/01-reed-openid-xri-xrds.pdf as a reference.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred documents are "approved documents".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The following file is maintained by OASIS and has all the requested information: https://www.oasis-open.org/standards
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1737] K. Sollins, L. Masinter, Functional Requirements for Uniform Resource Names, http://www.ietf.org/rfc/rfc1737.txt, RFC 1737, December 1994./
[RFC2046] N. Borenstein, N. Freed, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types, http://www.ietf.org/rfc/rfc2046.txt, RFC 2046, November 1996./
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, RFC 2119, March 1997./
[RFC2141] R. Moats, URN Syntax, http://www.ietf.org/rfc/rfc2141.txt, IETF RFC 2141, May 1997./
[RFC2234] D. H. Crocker and P. Overell, Augmented BNF for Syntax Specifications: ABNF, http://www.ietf.org/rfc/rfc2234.txt, RFC 2234, November 1997./
[RFC2396] T. Berners-Lee, R. Fielding, L. Masinter, Uniform Resource Identifiers (URI): Generic Syntax, http://www.ietf.org/rfc/rfc2396.txt, RFC 2396, August 1998./
[RFC2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Hypertext Transfer Protocol -- HTTP/1.1, http://www.ietf.org/rfc/rfc2616.txt, RFC 2616, June 1999./
[RFC2718] L. Masinter, H. Alvestrand, D. Zigmond, R. Petke, Guidelines for New URL Schemes, http://www.ietf.org/rfc/rfc2718.txt, RFC 2718, November 1999./
[RFC2732] R. Hinden, B. Carpenter, L. Masinter, Format for Literal IPv6 Addresses in URL's, http://www.ietf.org/rfc/rfc2732.txt, RFC 2732, December, 1999. /
[RFC3066] H. Alvestrand, Tags for the Identification of Languages, http://www.ietf.org/rfc/rfc3066.txt, RFC 3066, January, 2001. /
[RFC3305] M. Mealing, R. Denenberg, Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations, http://www.ietf.org/rfc/rfc3305.txt, RFC 3305, August 2002./
[RFC3490] P. Faltstrom, P. Hoffman, A. Costello, Internationalizing Domain Names in Applications (IDNA), http://www.ietf.org/rfc/rfc3490, RFC 3490, March 2003./
[RFC3491] P. Hoffman, M. Blanchet, Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN), http://www.ietf.org/rfc/rfc3491, RFC 3491, March 2003./
[UML] Object Management Group, Unified Modeling Language (UML) Version 1.5, http://www.omg.org/technology/documents/formal/uml.htm, March 1, 2003./
[Unicode] The Unicode Consortium. The Unicode Standard, Version 4.0.0, defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1)/
[UniXML] Duerst, M. and A. Freytag, Unicode in XML and other Markup Languages, Unicode Technical Report #20, World Wide Web Consortium Note, February 2002./
[UTR15] M. Davis, M. Duerst, Unicode Normalization Forms, http://www.unicode.org/unicode/reports/tr15/tr15-23.html, April 17, 2003./
[XML] T. Bray, J. Paoli, C.M. Sperberg-McQueen, E. Maler, Extensible Markup Language (XML) 1.0 (Second Edition) W3C Recommendation, http://www.w3.org/TR/REC-xml, October 2000./
[XMLSchema2] P. Biron, A. Malhotra, XML Schema Part 2: Datatypes W3C Recommendation, http://www.w3.org/TR/xmlschema-2/, May 2001.
|
|
9.
|
Qualification of
OASIS:
|
|
|
OASIS is recognized under the provisions of ITU-T Recommendations A.5 and A.4. Qualifying information is on file at TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None.
|
|
