Changes

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 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.  

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: xri: authority  / path  ? query  # fragment. 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, '''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>

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>

===Key Features XRI Provides===

===Key Features XRI Provides===

==Internet Community Reaction on XRI==

==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 found that is has functionality that is not readily available from [[HTTP]]: [[URI]]s. According to them the XRI specification 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 is untested and the registration process is confusing.<ref>

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>

[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>