RE: [xri] Incorporating Yadis into XRI Resolution Working Draft 11

This is additional functionality that someone deploying an 
HTTP-URI-identified resource could also deploy to associate an XRDS with that 
HTTP-URI-identified resource.

 

If you are building resolution for XRI, I think this is 
completely out of scope. 

 

It may affect you if you say "implements all of XRI 
resolution" -- this is an optional feature dealing with resolution that (if you 
will) starts with HTTP URIs instead of XRIs (or HXRIs). 

 

   -Gabe

  

  
  From: Drummond Reed 
  [mailto:] 
Sent: Monday, May 22, 2006 2:14 
  PM
To: 'Chasen, Les'; Wachob, Gabe; 
  
Cc: 'Johannes Ernst'; 'Recordon, David'; 
  'Larry Drebes'; 'James Bryce Clark (James Bryce Clark)'; 'Ram 
  Kumar'
Subject: RE: [xri] Incorporating Yadis into XRI Resolution 
  Working Draft 11

  

  

  
Les,

  
 

  
We anticipate zero 
  impact on authority resolution or service selection. The Yadis spec deals only 
  with the process of retreiving an XRDS docment from an HTTP(S) 
  URI.

  
 

  
=Drummond 
  

  
 

  

  

  
  

  
From: Chasen, 
  Les [mailto:] 
Sent: Monday, May 22, 2006 11:41 
  AM
To: Wachob, Gabe; Drummond 
  Reed; 
Cc: Johannes Ernst; Recordon, David; 
  Larry Drebes; James Bryce Clark (James Bryce Clark); Ram Kumar
Subject: RE: [xri] Incorporating Yadis 
  into XRI Resolution Working Draft 11

  
 

  
How does this impact 
  authority resolution and service selection?  If there are no impacts than 
  I think this makes perfect sense.

  
 

  

  
 

  
=les.chasen 
  

  
http://xri.net/=les.chasen

  

  

  

  
  

  
From: Wachob, 
  Gabe [mailto:] 
Sent: Monday, May 22, 2006 2:04 
  PM
To: Drummond Reed; 
  
Cc: 
  Johannes Ernst; Recordon, David; Larry Drebes; James Bryce Clark (James Bryce 
  Clark); Ram Kumar
Subject: 
  RE: [xri] Incorporating Yadis into XRI Resolution Working Draft 
  11

  
 

  
XRI TC 
  Members-

  
 

  
Drummond 
  posted this notice on Saturday May 22. I want to make sure anyone who wants to 
  object to this additional material has the chance to do so before we consider 
  the decision made. 

  
 

  
I think 
  the synergy with a significant grassroots community such as the one building 
  around YADIS will help *our* effort significantly. That being said, it is 
  beyond awfully late and I have pushed back on other changes due to the 
  lateness of the timing -- if you have this sort of pushback to this proposal, 
  please speak up now. 

  
 

  
Basically, what we 
  are proposing to do is add a section to XRI resolution which includes the 
  contents of section 6 of the YADIS spec [1]. As Drummond mentioned, this 
  section will describe how to discover an XRDS associated with an *HTTP 
  URI*-identified resource - for the YADIS purposes or (more in alignment with 
  things we've been doing) to discover a *synonym* for an HTTP URI that might be 
  an XRI (the possibilities here are interesting, to say the least). 
  

  
 

  
   
  -Gabe

  
 

  
[1] http://yadis.org/papers/yadis-v1.0.pdf

  
    
 

    

    

    
    

    
From: 
    Drummond Reed [mailto:] 
Sent: Saturday, May 20, 2006 1:44 
    PM
To: 
    
Cc: 'Johannes Ernst'; Recordon, David; 
    Larry Drebes; James Bryce Clark (James Bryce Clark); Ram Kumar
Subject: [xri] Incorporating Yadis into 
    XRI Resolution Working Draft 11

    
XRI TC Members and 
    Observers:  
     

    
 

    
Most of you are aware that the 
    XRI resolution document format, XRDS, was adopted late last year by the 
    Yadis project (http://www.yadis.org) as 
    their format for simple service discovery. After the Internet Identity 
    Workshop two weeks ago (http://iiw.windley.com/wiki/Main_Page), 
    at which there were several sessions on XRI, members of the Yadis community 
    mentioned to Gabe and I that they were interested in Yadis becoming an 
    “official” standard from a recognized standards body. 
    

    
 

    
Since Yadis already uses a 
    substantial part of the XRI Resolution 2.0 specification, they asked if the 
    XRI TC would be interested in having it be incorporated as part of the 
    spec.

    
 

    
Gabe and I subsequently reviewed 
    the Yadis 1.0 specification (http://yadis.org/papers/yadis-v1.0.pdf) 
    and agreed that it should fit cleanly as a section of the XRI Resolution 2.0 
    specification on obtaining XRDS documents from HTTP 
    URIs.

    
 

    
At the OASIS Symposium last week 
    we checked with Jamie Clark, OASIS Director of Standards Development, to see 
    if there were any impediments to doing this, and he said that it should be 
    very easy and straightforward, especially considering that several XRI TC 
    members were contributors to Yadis.

    
 

    
So, in an email conversation 
    yesterday between Gabe and myself and several of the principal contributors 
    to Yadis, we concluded that we should proceed full steam ahead provided both 
    communities were in support of this effort. Messages are going to both 
    mailing lists today to request any further feedback. Provided that there are 
    no major objections, a contribution will be made on behalf of the Yadis 
    community and we will begin work ASAP on the integration of Yadis into 
    Working Draft 11 of XRI Resolution 2.0 with the goal of completing the work 
    no later than the start of the Berkman Identity Mashup on June 19 (http://www.identitymash-up.org/).

    
 

    
Please do post with any feedback 
    you might have.

    
 

    
Best,

    
 

    
=Drummond 
    (http://xri.net/=drummond.reed)