[XRI] XRI 2.0 Resolution Sec 6 / XRDS-Simple

The XRI-TC and the W3C TAG have stated that they would like to produce  
a list of points that they can both agree on.

I would like to explore XRI 2.0 resolution Sec 6, Discovering an XRDS  
Document from a HTTP(S) URI
http://docs.oasis-open.org/xri/xri-resolution/2.0/specs/cs01/xri-resolution-V2.0-cs-01.html

A profile of the XRDS document and Sec 6 resolution is used by XRDS- 
Simple.
http://xrds-simple.net/core/1.0/

The final change to the XRI spec was adding the XRD Type element to  
allow the oAuth developers to indicate that a XRD contains only  
elements appropriate for there simple parser.

The irony is that the profile defined by <Type>xri://$xrds*simple</ 
Type> is now in some ways more complicated than the original.

While processing refs, redirects, match,  and  select elements are  
excluded.   They have added new URI construction rules and a  
XRD:simple namespace.

I believe that they are looking at expanded URI templating rules in an  
upcoming draft.
Perhaps based on http://tools.ietf.org/html/draft-gregorio-uritemplate-03

I know that John Panzer at Google has expanded URI templating rules in  
the XRD:os namespace for Open Social.

The work on using XRDS documents for service discovery is ongoing in  
many projects and organizations like Google and Yahoo.

My questions to the TAG are:

Are there questions the TAG has specific to this area of XRI?

Are there any known objections the TAG has to this part of the spec?

Should the XRI-TC move the XRDS document format to its own spec so it  
can be referenced independently of XRI resolution?

Should the XRI-TC seek the contribution of IPR that has been created  
outside of the OASIS process for contribution to a revised spec.    
This would guarantee royalty free IPR protection for all of the XRDS- 
Simple profile.

A number of groups are caught in the XRI / TAG crossfire.

Lets see if we can sort something out in this area to allow some  
certainty for those groups in a reasonable timeframe.

I have copied a number of related parties on this email who aren't  
necessarily on the TAG list.
For them this thread can be found at http://lists.w3.org/Archives/Public/www-tag/

Regards
John Bradley
OASIS IDTRUST-SC
http://xri.net/=jbradley
五里霧中