XRI Wiki
Introduction
This page summarizes the overall requirements motivating many of the change proposals for XRI Resolution 2.0 Committee Draft 02 (see Xri2Cd02/ResolutionChanges).
Restated Proxy Resolution Requirements
RR1. Any service provider should be able to provide HTTP XRI proxy resolution (i.e. resolution of an XRI embedding in an HTTP URI, called an “HXRI”) as long as they follow a set of rules specified in the XRI resolution specification.
RR2. Proxy resolution needs to enable an HXRI to work as a link in a web browser that results in GETting a representation of a resource that the browser understands (e.g., a resource that has a well-known HTTP Accept header content type value).
RR3. Proxy resolution should be able to figure out what Local Access Service to use based only on the HXRI and browser HTTP request headers.
RR4. (moved to become HX1, below).
RR5. The solution should not be too complicated.
RR6. A Local Access Service should be able to know the original XRI in order determine the final redirect URI.
HXRI (HTTP XRI) Requirements
Note that these were discussed in the minutes of the 2005/10/14 TC meeting.
HX1. Minimize the chance of mistaking a valid HTTP URI that is not intended to be an HXRI as an HXRI.
HX2. People and software agents should be able to unambiguously extract the XRI from an HXRI to support comparison of XRIs.
HX3. There should be at least one form of an HXRI that is easy for humans to understand and use (e.g., put on a business card and type into an address bar.)
Proposed Service Description Requirements
SD1 Any Service Endpoint (currently called a Local Access Service in CD01) should be able to use the same trust model as that currently provided for trusted authority resolution, i.e., it should be able to describe an authority identifier for the service and keyinfo for the service.
SD2 The provider of a Service Endpoint should be able to support multiple services at the same endpoint if the messages or methods of interaction supported by the different services can be distinguish in ways that do not require using different URIs.
SD2A As a specific subrequirement, an XRI authority should be able to advertise that the same Service Endpoint supports generic authority resolution, trusted authority resolution, proxy resolution, and the service currently known as X2R service.