Re: XRIs *are* intended to be used where URIs are used

Henry-
    At [1] and [2], you and Vincent Quint relay the TAG's strong
recommendation that we implement XRI functionality using http: URIs. I
assume from the unqualified nature of your responses that members of the
TAG have read and understood the XRI Requirements [3] and XRI
Introduction [4] documents and still believe that HTTP URIs meet our
needs. We have carefully considered a number of ways of supporting the
functionality and requirements we've been working towards and we don't
see how HTTP URIs can be used to meet all of our needs. 
 
    The TAG discussions at [5] and [6] (linked from [2]) are hard to
follow and seem to focus on persistence as the only use case for XRIs.
Could you please be more specific about how  HTTP URIs could be used to
provide all of the functionality of XRI?  
    
    Thanks.
 
    -Gabe
 
[1] http://lists.w3.org/Archives/Public/www-tag/2005May/0035.html
[2] http://lists.w3.org/Archives/Public/www-tag/2005Apr/0095.html
[3]
http://www.oasis-open.org/committees/download.php/2523/xri-requirements-
and-glossary-v1.0.doc
[4]
http://www.oasis-open.org/committees/download.php/11857/xri-intro-V2.0-w
d-04.pdf
[5] http://lists.w3.org/Archives/Public/www-tag/2005Apr/0076.html
<http://lists.w3.org/Archives/Public/www-tag/2005Apr/0076.html> 
[6] http://lists.w3.org/Archives/Public/www-tag/2005Apr/0088.html
<http://lists.w3.org/Archives/Public/www-tag/2005Apr/0088.html> 
__________________________________________________ 
gwachob@visa.com 
Chief Systems Architect 
Technology Strategies and Standards 
Visa International 
Phone: +1.650.432.3696   Fax: +1.650.554.6817