XRI root authority is the first subsegment in an XRI authority segment. An XRI root authority may either be a GCS character or a cross-reference. For example, xri://@foo*bar uses the "@" root authority and xri://(http://example.com) uses the "(http://example.com)" root authority. Root authorities allow communities to share a common namespace and uniquely identify shared resources (or resources that are used by multiple parties).

Global context symbols (GCS)-single-character symbols used to indicate the global context of the authority type (see below). Both GCS characters and cross-references support delegation to other authorities using either reassignable or persistent subsegments. Note that a GCS character may only be used as the first authority subsegment, called the root authority, while a cross-reference may be used as the root or at any level of delegation.

Each subsegment in the authority segment of an XRI corresponds to a separate authority. For example, in @us*california*oakland, the following prefixes identify four separate authorities: ? @? @us? @us*california? @us*california*oakland Note that an authority may be identified with several different "paths" of authority subsegments. The following two authority identifiers may resolve to the same authority: ? @san.

We are very much a trusted Certification Authority (CA). In fact New Zealand's first CA, established three years ago, supplying to New Zealand government, law firms, health, education, and commerce. We specialise in providing strong security with a high level of trust, predominantly to support business-to-business requirements. Although our root certificate is not currently embedded in browsers off-the-shelf, it is a simple one-time action to import the root certificates from our web site.

Early Web architecture divided Web addresses (URIs) into two types: URLs (Uniform Resource Locators) and URNs (Uniform Resource Names). The former are "concrete" addresses that identify resources at a specific location on the Internet (and thus can "break" if a resource moves). The latter are "abstract" addresses that persistently identify resources independent of any specific location, domain, or application.

IDCommons I-Broker (http://ibroker.idcommons.net/) - a system building on top of XRI to provide i-name and i-number registration and related identity services for individuals and organizations. Includes an XRI resolver. Built in PHP. Gabe Wachob's XRI Escaping Tool (http://www.wachob.com/xriescape) - an online tool (with Python source) of the URI and IRI normal form escaping mechanism.

Underneath your tooth's outer enamel and within the dentin is an area of soft tissue called the pulp, which carries the tooth's nerves, veins, arteries and lymph vessels. Root canals are very small, thin divisions that branch off from the top pulp chamber down to the tip of the root. A tooth has at least one but no more than four root canals.

A Certificate of Authority is a document that verifies that a foreign entity is registered in the state of Georgia.

In the context of identifiers, an authority is the entity that controls a namespace. With XRIs, an authority may host a server that provides XRI resolution services. These servers are analogous to nameservers for DNS. Multiple authority namespaces may be hosted on a single server.

URI (RFC 3986) is the IETF/W3C standard for addressing on the Web. IRI (Internationalized Resource Identifier, RFC 3987) builds on top of the URI specification by extending the syntax to include Unicode characters. It also defined a transformation from an IRI into a valid URI for applications that can only accept URIs. XRI follows this same model.

XRI 2.0 is the product of the XRI Technical Committee at OASIS. Members of this technical committee include a variety of software and service vendors as well as XRI users of all types: major corporations, non-profit organizations, and community-based digital identity organizations.

XRI Syntax 2.0 defines the syntax, relative reference rules, normalization/comparison rules, and IRI/URI transformation rules. XRI Resolution 2.0 defines a lightweight HTTP(S)- and XML-based resolution protocol that may be used with XRIs, together with a trusted version based on SAML 2.0 assertions. XRI Metadata 2.

No. The XRI specifications are licensed on Royalty-Free terms based on the OASIS IPR policy (http://www.oasis-open.org/who/intellectualproperty.php). See the XRI TC IPR page for details (http://www.oasis-open.org/committees/xri/ipr.php).

XRI could be used to identify an individual or an organization across multiple methods of access. For example, the same XRI could be mapped to a contact web page, an instant messaging identifier, an email address, or even be used directly as an identifier in a completely decentralized P2P system such as JXTA.

The iSSO protocol under development at XDI.org uses XRI resolution to bootstrap usage of SAML 2.0 authentication assertions for cross-domain single sign-on. The i-tag initiative for intelligent, identity-enabled tagging of structured content in the blogging and RSS syndication industries uses XRI. XRIs also form the basis for the XDI trusted data sharing protocol under development by the OASIS XDI Technical Committee (http://www.oasis-open.org/committees/xdi).

The ability to combine identifiers from multiple identifier schemes in order to share/reuse identifiers across contexts and express shared identifier metadata (similar to the way XML standardizes the use of structured data and metadata) Allowing one identifier authority to control some subset of another identifier authority's namespace. Bringing together two or more identifier namespaces under a common root or otherwise enabling two or more communities to access each other's identifiers.

The structure of XRIs derives directly from the structure of URIs. XRIs usually start with the string "xri://" followed by an authority segment and then the path portion of the XRI (if any). As with in generic URI syntax, the authority and path parts may be followed by optional query and fragment components.

By using all persistent subsegments (including persistent cross-references), both in the authority segment and in any path segments. For example, all of the examples below are fully-persistent XRIs: ? xri://!!1002? xri://!!1002!82A7? xri://!!1002!82A7/!C345.D22A Note that these XRIs begin with "!" as the special starting character reserved for fully-persistent identifiers. It must always be followed by a persistent subsegment, which explains the second "!".

discussed above, the authority portion of an XRI may also contain an IRI authority, which may be either a DNS name or an IP address. These are unambiguous because they start with either a letter or a number, respectively, while a GCS character is always symbol and a cross-reference always starts with a left parentheses. For example, the following are all valid IRI authority segments in an XRI. ? xri://www.example.com? xri://10.0.0.1/index? xri://[fec0::7]/user/docs/some.