Jump to content

Extensible Resource Identifier: Difference between revisions

From ICANNWiki
← Older editNewer edit →
VisualWikitext
Marie Cabural (talk | contribs)
9,082 edits
Marie Cabural (talk | contribs)
9,082 edits
Line 5: Line 5:
==XRI Syntax==
==XRI Syntax==
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>
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>
==XRDS==
An Extensible Resource Descriptor Sequence (XRDS), is an XML document format for discovery and resoultion of XRI-identified resources based on the definition given by the XRI Resolution specification.<ref>[http://www.oasis-open.org/committees/xri/faq.php General Question about XRI]</ref>


==XRI Open Source Projects==
==XRI Open Source Projects==

Revision as of 23:45, 9 October 2011

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.[1]

XRI Syntax[edit | edit source]

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. [2] 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).[3]

XRI Open Source Projects[edit | edit source]

There are different XRI open resource projects maintained by the XRI community which include:[4]

  • OpenXRI
  • Barx
  • JanRain
  • DotNetOpenId
  • FoXRI
  • AuthSrv
  • PyAuthSrv
  • Linksafe

XRI Technical Committee[edit | edit source]

The XRI Technical Committee (XRI TC) 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 URNs (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:[5] [6]

  • 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

References[edit | edit source]

Retrieved from "https://icannwiki.org/index.php?title=Extensible_Resource_Identifier&oldid=44243"