Extensible Resource Identifier: Difference between revisions

(31 intermediate revisions by 3 users not shown)

Line 1:

[[~~Image~~:~~UnderConstruction~~.~~png]~~]

'''XRI''' stands for '''Extensible Resource Identifier,''' an open standard protocol for digital addressing developed by the [[Organization for the Advancement of Structured Information Standards]] (OASIS), a non-profit consortium engaged in developing interoperability protocols for security, Cloud Computing, SOA, web services, the Smart Grid, electronic publishing, emergency management, etc.<ref>[http://www.oasis-open.org/standards www.oasis-open.org About]</ref>

~~'''~~XRI~~''' stands~~ for ~~'''Extensible~~ Resource Identifier,~~''' an open standard protocol for digital identity addressing developed by~~ the ~~Organization~~ for ~~the Advancement~~ of ~~Structured Information Standards),~~ a ~~not-for-profit consortium engaged in developing interoperability protocols for security, Cloud Computing, SOA, Web services, the Smart Grid, electronic publishing, emergency management, etc~~.<ref>[http://~~www~~.oasis-open.org/~~standards www~~.~~oasis~~-~~open~~.~~org About~~]</ref>

XRI Resolution is defined as a simple and easy-to-deploy infrastructure for the purpose of resolving XRIs to [[URI|Uniform Resource Identifier]]s (URIs). It uses the [[HTTP]]s, XRDS documents, and SAML assertions enabling the discovery and selection of service endpoint metadata for any type of service associated with a resource.<ref>[http://docs.oasis-open.org/xri/xri-resolution/2.0/specs/cd03/xri-resolution-V2.0-cd-03.html#_Toc192004428 Extensible Resource Identifier (XRI) Resolution Version 2.0]</ref> XRI is able to meet the functionality requirements of the [[URN]]s (Uniform Resource Names), which is capable of identifying resources both people and organizations as well as sharing data across applications, domains and enterprises.

~~==XRI Syntax==~~

The XRI syntax was developed based on [[RFC]] 3986 on URIs, which provided a simple and extensible way for identifying a resource, and RFC 3987 on [[IRI]]s (Internationalized Resource Identifiers), a protocol with a sequence of characters from the Unicode/ISO 10646. XRI is capable of including characters beyond those used by the generic [[URI]] and incorporates the simplification and enhancements of the URI syntax.<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Extensible Resource Identifier (XRI) Generic Syntax and Resolution Specification, Committee Draft, January 12, 2004]</ref> The OASIS XRI Technical Committee explained that just like the generic URI, the XRI syntax has four optional components with the scheme name xri: For example: <tt>xri: authority / path ? query # fragment</tt>. The HTTP URIs, which use the generic URI syntax, can be changed to a valid XRI by simply changing an http URI to XRI just like this, <tt>xri://www.example.com/pages/index.html</tt> (standard HTTP URI converted to XRI).<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Generic Syntax]</ref>

The XRI ~~Syntax~~ was developed based on RFC 3986 ~~Uniform Resource Identifiers (~~URIs)], which ~~provides~~ a simple and extensible way for identifying a resource and RFC 3987 ~~IRIs~~ (Internationalized Resource Identifiers), a protocol with a sequence of characters from the Unicode/ISO 10646. XRI is capable of including characters beyond ~~what is~~ used by the generic [[URI]] and incorporates the simplification and enhancements of the URI syntax. <ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Extensible Resource Identifier (XRI) Generic Syntax and Resolution Specification, Committee Draft, January 12, 2004]</ref> The OASIS XRI Technical Committee explained that just like the generic URI, the XRI syntax~~, it~~ has four optional components with the scheme name xri: For example: xri: authority / path ? query # fragment. The HTTP URIs which ~~uses~~ the generic URI syntax can be changed to a valid XRI by simply changing an http URI to XRI just like this, ~~'''~~xri://www.example.com/pages/index.html~~'''~~ (standard HTTP URI converted to XRI).<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Generic Syntax]</ref>

==~~OASIS~~ XRI Technical Committee==

===Key Features XRI Provides===

The ~~OASIS~~ XRI ~~technical~~ Committee was created for the purpose of defining the XRI, an identifier that is attuned or compatible with the URI protocol and able to meet the functionality requirements of the [[URN]]s (Uniform Resource Names) that is capable of identifying resources both people and organizations as well as sharing data across applications, domains and enterprises. Drummond Reed from Cordance and Gabriel Wachob from VISA served as co-chairmen of the technical committee, leading the ~~accomplishment and~~ development of the following:<ref>[http://www.oasis-open.org/committees/xri/charter.php OASIS Extensible Resource Identifier TC]</ref>

* Structured Identifiers

* Robust Synonym Expression and Resolution

* Uniform Extensible Discovery, Resolution, and Description Protocol

==XRI Technical Committee==

The XRI Technical Committee (XRI TC) was created for the purpose of defining the XRI. Drummond Reed from Cordance and Gabriel Wachob from VISA served as co-chairmen of the technical committee, leading the development of the following:<ref>[http://www.oasis-open.org/committees/xri/charter.php OASIS Extensible Resource Identifier TC]</ref><ref>[http://xml.coverpages.org/ni2004-01-19-a.html OASIS TC Promotes Extensible Resource Identifier (XRI) Specification]</ref>

* XRI Primer v1.0 - Introduction to XRI and its uses

* XRI Metadata Specification v1.0 - A registry of special XRI identifiers which describes other XRI identifiers

* XRI Secure Resolution Specification v1.0 - Extensions to the base XRI resolution protocol for digitally verifying resolution results

* XRI Syntax and Resolution Specification v1.1 - A revision incorporating implementation experience and feedback

==XRI Open Source Projects==

There are different XRI open resource projects maintained by the XRI community, which include:<REF>[http://dev.inames.net/wiki/Open_Source_Projects XRI Open Source Projects]</ref>

* OpenXRI

* Barx

* JanRain

* DotNetOpenId

* FoXRI

* AuthSrv

* PyAuthSrv

* Linksafe

==Internet Community Reaction on XRI==

The introduction of XRI stirred discussion within the Internet community. [[Tim Berners-Lee]] and [[Stuart Williams]], co-chairs of the [[W3C]] Technical Architecture Group, expressed their dissatisfaction with the XRI technology. Berners-Lee and Williams explained that they reviewed XRI and had not found that XRIs had functionality not readily available from URIs; as such, the XRI specification was unnecessary and should not be supported.<ref>[http://lists.w3.org/Archives/Public/www-tag/2008May/0078 TAG recommends against XRI]</ref> Some members of the Internet community expressed that the technology was untested and the registration process was confusing.<ref>

[http://lists.openid.net/pipermail/openid-general/2007-January/010335.html why is xri so obtuse?]</ref> Others advised consumers to avoid the service and commented that the Internet community did not need another centralized body to manage Internet addressing services.<ref>[http://lists.oasis-open.org/archives/xri/200707/msg00021.html Avoid XRI]</ref>

==References==

__NOTOC__

[[Category:Glossary]]

@@ Line 1: / Line 1: @@
-[[Image:UnderConstruction.png]]
+'''XRI''' stands for '''Extensible Resource Identifier,''' an open standard protocol for digital addressing developed by the [[Organization for the Advancement of Structured Information Standards]] (OASIS), a non-profit consortium engaged in developing interoperability protocols for security, Cloud Computing, SOA, web services, the Smart Grid, electronic publishing, emergency management, etc.<ref>[http://www.oasis-open.org/standards www.oasis-open.org About]</ref>
-'''XRI''' stands for '''Extensible Resource Identifier,''' an open standard protocol for digital identity addressing developed by the Organization for the Advancement of Structured Information Standards), a not-for-profit consortium engaged in developing interoperability protocols for security, Cloud Computing, SOA, Web services, the Smart Grid, electronic publishing, emergency management, etc.<ref>[http://www.oasis-open.org/standards www.oasis-open.org About]</ref>
+XRI Resolution is defined as a simple and easy-to-deploy infrastructure for the purpose of resolving XRIs to [[URI|Uniform Resource Identifier]]s (URIs). It uses the [[HTTP]]s, XRDS documents, and SAML assertions enabling the discovery and selection of service endpoint metadata for any type of service associated with a resource.<ref>[http://docs.oasis-open.org/xri/xri-resolution/2.0/specs/cd03/xri-resolution-V2.0-cd-03.html#_Toc192004428 Extensible Resource Identifier (XRI) Resolution Version 2.0]</ref> XRI is able to meet the functionality requirements of the [[URN]]s (Uniform Resource Names), which is capable of identifying resources both people and organizations as well as sharing data across applications, domains and enterprises.
-==XRI Syntax==
+The XRI syntax was developed based on [[RFC]] 3986 on URIs, which provided a simple and extensible way for identifying a resource, and RFC 3987 on [[IRI]]s (Internationalized Resource Identifiers), a protocol with a sequence of characters from the Unicode/ISO 10646. XRI is capable of including characters beyond those used by the generic [[URI]] and incorporates the simplification and enhancements of the URI syntax.<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Extensible Resource Identifier (XRI) Generic Syntax and Resolution Specification, Committee Draft, January 12, 2004]</ref> The OASIS XRI Technical Committee explained that just like the generic URI, the XRI syntax has four optional components with the scheme name xri: For example: <tt>xri: authority  / path  ? query  # fragment</tt>. The HTTP URIs, which use the generic URI syntax, can be changed to a valid XRI by simply changing an http URI to XRI just like this, <tt>xri://www.example.com/pages/index.html</tt> (standard HTTP URI converted to XRI).<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Generic Syntax]</ref>
-The XRI Syntax was developed based on RFC 3986 Uniform Resource Identifiers (URIs)], which provides a simple and extensible way for identifying a resource and RFC 3987  IRIs (Internationalized Resource Identifiers), a protocol with a sequence of characters from the Unicode/ISO 10646. XRI is capable of including characters beyond what is used by the generic [[URI]] and incorporates the simplification and enhancements of the URI syntax. <ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Extensible Resource Identifier (XRI) Generic Syntax and Resolution Specification, Committee Draft, January 12, 2004]</ref>  The OASIS XRI Technical Committee explained that just like the generic URI, the XRI syntax, it has four optional components with the scheme name xri: For example: xri: authority  / path  ? query  # fragment. The HTTP URIs which uses the generic URI syntax can be changed to a valid XRI by simply changing an http URI to XRI just like this, '''xri://www.example.com/pages/index.html''' (standard HTTP URI converted to XRI).<ref>[http://www.oasis-open.org/committees/download.php/5109/xri-syntax-resolution-1.0-cd.pdf Generic Syntax]</ref>
-==OASIS XRI Technical Committee==
+===Key Features XRI Provides===
-The OASIS XRI technical Committee was created for the purpose of defining the XRI, an identifier that is attuned or compatible with the URI protocol and able to meet the functionality requirements of the [[URN]]s (Uniform Resource Names) that is capable of identifying resources both people and organizations as well as sharing data across applications, domains and enterprises. Drummond Reed from Cordance and Gabriel Wachob from VISA served as co-chairmen of the technical committee, leading the accomplishment and development of the following:<ref>[http://www.oasis-open.org/committees/xri/charter.php OASIS Extensible Resource Identifier TC]</ref>
+* Structured Identifiers
+* Robust Synonym Expression and Resolution
+* Uniform Extensible Discovery, Resolution, and Description Protocol
+==XRI Technical Committee==
+The XRI Technical Committee (XRI TC) was created for the purpose of defining the XRI. Drummond Reed from Cordance and Gabriel Wachob from VISA served as co-chairmen of the technical committee, leading the development of the following:<ref>[http://www.oasis-open.org/committees/xri/charter.php OASIS Extensible Resource Identifier TC]</ref><ref>[http://xml.coverpages.org/ni2004-01-19-a.html OASIS TC Promotes Extensible Resource Identifier (XRI) Specification]</ref>
 * XRI Primer v1.0 - Introduction to XRI and its uses
 * XRI Metadata Specification v1.0 - A registry of special XRI identifiers which describes other XRI identifiers
 * XRI Secure Resolution Specification v1.0 - Extensions to the base XRI resolution protocol for digitally verifying resolution results
 * XRI Syntax and Resolution Specification v1.1 - A revision incorporating implementation experience and feedback
+==XRI Open Source Projects==
+There are different XRI open resource projects maintained by the XRI community, which include:<REF>[http://dev.inames.net/wiki/Open_Source_Projects XRI Open Source Projects]</ref>
+* OpenXRI
+* Barx
+* JanRain
+* DotNetOpenId
+* FoXRI
+* AuthSrv
+* PyAuthSrv
+* Linksafe
+==Internet Community Reaction on XRI==
+The introduction of XRI stirred discussion within the Internet community. [[Tim Berners-Lee]] and [[Stuart Williams]], co-chairs of the [[W3C]] Technical Architecture Group, expressed their dissatisfaction with the XRI technology. Berners-Lee and Williams explained that they reviewed XRI and had not found that XRIs had functionality not readily available from URIs; as such, the XRI specification was unnecessary and should not be supported.<ref>[http://lists.w3.org/Archives/Public/www-tag/2008May/0078 TAG recommends against XRI]</ref> Some members of the Internet community expressed that the technology was untested and the registration process was confusing.<ref>
+[http://lists.openid.net/pipermail/openid-general/2007-January/010335.html why is xri so obtuse?]</ref> Others advised consumers to avoid the service and commented that the Internet community did not need another centralized body to manage Internet addressing services.<ref>[http://lists.oasis-open.org/archives/xri/200707/msg00021.html Avoid XRI]</ref>
 ==References==
 {{reflist}}
+__NOTOC__
 [[Category:Glossary]]