|
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. The goal of XRI is to provide a universal format for abstract, structured identifiers that are domain-, location-, application-, and transport-independent, so they can be shared across any number of domains, directories, and interaction protocols.
Background & Motivations URIs have been very successful identifiers over the Internet. However the growth of the Web has led to new requirements for resource identifiers that are not easily met by standard URI syntax. One of these key requirements — internationalization — was ultimately met by the W3C and IETF by developing a new form of URI called an Internationalized Resource Identifier (IRI). The IRI specifications built on the URI standard by extending the character set to support the full range of Unicode characters. With the growth of XML, Web services, and other ways of adapting the Web to automated, machine-to-machine communications, another set of requirements has emerged. These are the requirements to be able to identify a resource independent of a specific physical network path, location, or protocol because you need to: By early 2003, these requirements led to the establishment of a new technical committee at OASIS whose goal was to create a new type of identifier that built on top of the IRI specification the same way the IRI specification built on top of the URI specification. The XRI TC was also charged with creating an optional resolution protocol based on HTTP and simple XML documents called Extensible Resource Descriptors (XRDs). Features As a specific example, say a library system uses URNs in the ISBN namespace to identify books and DNS subdomains to identify its library branches. HTTP URI syntax does not provide a standard way to express the URN for the book title in the context of the DNS name for the library branch. XRI cross-reference syntax solves this problem by allowing the library (and even automated programs running at the library) to programmatically construct the XRIs necessary to address any book at any branch. Examples: xri://broadview.library.example.com/(urn:isbn:0-395-36341-1) xri://shoreline.library.example.com/(urn:isbn:0-395-36341-1) xri://northgate.library.example.com/(urn:isbn:0-395-36341-1) This ability to create structured, self-describing identifiers can be extended to many other uses. For example, say the library wanted to indicate the type of each book available. By establishing a simple XRI dictionary of book types, it can now programmatically construct XRIs that include this metadata, xri://broadview.library.example.com/(urn:isbn:0-395-36341-1)/(+hardcover) xri://broadview.library.example.com/(urn:isbn:0-395-36341-1)/(+softcover) xri://broadview.library.example.com/(urn:isbn:0-395-36341-1)/(+reference) Note that there those who disagree that these are problems. For example, the W3C Technical Architecture Group is working on a draft document which attempts to refute some of the claims made by XRI proponents. Applications Examples of applications being developed using XRI infrastructure include: Examples (Note that none of these show the prefix "xri://", which is optional in XRIs when they are not in URI normal form, i.e, they have not undergone the specified transformation between XRI format and URI format.) Example XRIs composed entirely of reassignable segments: =Mary.Jones @Jones.and.Company +phone.number +phone.number/(+area.code) =Mary.Jones/(+phone.number) @Jones.and.Company/(+phone.number) @Jones.and.Company/((+phone.number)/(+area.code)) Example XRIs composed entirely of persistent segments: !!1002!A7C5 !!1002!A7C5/!D90F.88 Example of XRIs with mixes of persistent and reassignable segments (XRI allows any combination of the two): !!1002!A745/(+phone.number) @Jones.and.Company/!D90F.88/(+area.code) Licensing OASIS, which is the organization supervising the development this new standard, has been criticized by the Free Software Foundation for their patent policies *. The FSF claims that their patent policies may not allow conformance of software implementing them to the definition of Open Source. Fortunately, the committees responsible for developing the XRI and XDI standards have expressly declared their intention to make sure that the standards are unencumbered and completely Open Source compatible. The relevant text from their charter pages * and * reads: 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. In addition, XDI.org, an international non-profit public trust organization that holds an exclusive license to the original patents underlying XRI and XDI technologies as well as their predecessor, XNS, has contributed these rights to the OASIS XRI and XDI technical committees. See also | ||||||||
|
| |||||||||
 |
|
| |