OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xri] Res decision #1: spec refactor strawman


+1


From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Wed 11/2/2005 6:56 PM
To: xri@lists.oasis-open.org
Subject: [xri] Res decision #1: spec refactor strawman

Per our agenda below, this is a strawman proposal for decision #1 on refactoring the XRI Resolution 2.0 Committee Draft 01 spec into a new format for Committee Draft 02. This is Issue #7 on the Resolution change management page (http://wiki.oasis-open.org/xri/Xri2Cd02/ResolutionChanges), however there is no specific proposal yet.

 

Having spent time working on a potential revision already, here is a strawman for the general proposed reorganization:

 

1) Introduction

Simple explanation of the role of XRI resolution and the contents of this spec.

 

2) XRI Descriptors

An explanation of the structure of XRIDs and the usage of global attributes in the XRID schema (version, priority, etc.)

 

3) Generic Authority Resolution

Covers the HTTP URI construction algorithm and HTTP operations for generic authority resolution.

 

4) Trusted Authority Resolution

Covers the additional elements and processing rules for trusted authority resolution.

 

5) Local Resolution

Covers the HTTP URI construction algorithm and HTTP operations for local path/query resolution.

 

6) Proxy Resolution

Covers HXRIs, the HTTP URI construction algorithm, and HTTP operations for proxy resolution.

 

7) Use of HTTP

Covers the same material as in CD01.

 

8) Extensibility and Versioning

Covers the same material as in CD01.

 

9) Security and Privacy Considerations

Covers the same material as in CD01.

 

Same reference sections.

 

The other refactoring rule to be applied during this reorganization would be to move most non-normative material to a separate document (the XRI Implementer's Guide). The only examples that would remain are those short examples that are needed to make sure the intent of a normative requirement is clear.

 

The goal would be to reduce the spec to roughly half its current size.

 

=Drummond

 


From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Wednesday, November 02, 2005 11:42 AM
To: xri@lists.oasis-open.org
Subject: [xri] XRI Res CD02 proposed decision tree

 

I've talked with Gabe and there is a clear sense at this point that we need to move from the high-level conceptual definition of XRI resolution down into the concrete decisions we need to make to arrive at XRI Resolution 2.0 Committee Draft 02. As best we can tell, these decisions fall into four buckets:

 

1) Refactoring the Res CD01 spec (for readability and to remove most of the non-normative material).

 

2) Structure of an XRID.

 

3) Structure of an HXRI (HTTP XRI – the form of an XRI that can be resolved using an HTTP proxy resolver).

 

4) Rules/requirements for proxy resolution.

 

We would like to suggest that:

 

a) This week's two calls (Thurs. 9AM PT and Fri 8:30AM PT) focus on these four topics, with the goal of driving to consensus on each of the four as quickly as possible so that the editors can proceed into drafting ASAP.

 

b) TC members who care about these topics submit and discuss strawman proposals on each of the four via email prior to the the calls so that we're not starting discussion from scratch.

 

No response = agreement on this process, so you feel we should use a different process, speak up. Otherwise we'll make this our call agenda for Thursday/Friday and invite submissions/discussions of strawmen beginning immediately.

 

=Drummond

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]