|
The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200212/msg00001.html
At a meeting of the TC on 6 February 2003 the TC approved changes to the charter as minuted at http://lists.oasis-open.org/archives/xri/200302/msg00017.html
The TC charter was further revised by vote of the TC ending 4 April 2003, as recorded at http://www.oasis-open.org/apps/org/workgroup/xri/ballot.php?id=18
The charter for this TC is as follows.
Name
Extensible Resource Identifier (XRI) Technical Committee
Statement of Purpose
Increasingly, there is a demand for distributed directory services that enable the identification of any type of resource, both those directly on the network and those abstract from it, and the sharing of data across domains, enterprises, and applications.
Meeting this need requires an extensible, location-, application-, and transport-independent identification scheme that provides addressability not just of resources, but of their attributes and versions. The scheme should support both persistent and reassignable identifiers that can be optimized for either human usage or machine efficiency. It should ideally impose no limits on the underlying directory, data, or delegation models and thus be interoperable across the greatest possible number of systems and domains.
The purpose of this committee is to define a URI scheme and a corresponding URN namespace that meet these requirements. The URI scheme will conform to RFC 2396 and will act as a superset of the URN namespace, enabling both simple human-readable names for resources as well as persistent identifiers. The URN namespace will be compliant with RFC 2141 and be guided by the requirements in RFC 1737 for resources that need the ability to be persistently identified and linked.
This TC will also define basic mechanisms for resolving the identifiers in these schemes/namespaces including examining extensible solutions such as the IETF DDDS framework for resolution (RFC 3401-3405).
Subsequent to the completion of this work, a follow-on TC is expected to define a mechanism for exchanging data associated with an XRI, including a schema for associating metadata with XRI-identified resources and a REST-like (Representational State Transfer) service to operate on this metadata and the data it describes. Such a service would provide a platform for integrating XRIs with directory-related specifications such as LDAP, DSML, and SPML.
This TC's work may be influenced by the general architecture described in XNS and specifically by the XNS Addressing Specification. The XNS specifications published by the XNS Public Trust Organization (XNSORG) will be contributed to the TC for consideration in the committee's work. XNS is licensed under royalty-free (RF) terms as described in http://www.xns.org/pages/XNS_License.pdf.
In no event shall this Technical Committee finalize or approve any technical specification if it believes that the use, distribution, or implementation of such specification would necessarily require the unauthorized infringement of any third party rights known to the Technical Committee, and such third party has not agreed to provide necessary license rights on perpetual, royalty-free, non-discriminatory terms.
List of Deliverables
Delivery schedule.
The TC deliverables will include:
- Use cases & requirements
- A syntax specification for the URI scheme & URN namespace
- A resolution specification for the URI scheme & URN namespace
The TC intends to deliver its first specifications in Spring 2003 and continue to release additional deliverables at least quarterly.
|
