| Les,
Nothing will change with the native form of an XRI =les is still =les.
Nothing changes with native XRI resolution or authority servers.
This is just the binding to http(s) for the proxy resolver service. We would develop similar proxy resolver bindings for other URI schemes.
Anyone can still set up a proxy resolver on any domain name.
The "special domain names" like the TLD XRI would be used as a signal to applications that they are dealing with a HXRI. If you use proxy.chasen.us applications may not recognize HXRI in documents as HXRI and treat them as http: URI. This is the current situation.
To make this work as a http sub-scheme for arbitrary proxies we need to do something tricky with DNS so that proxy.chasen.us.xri returns the IP address for proxy.chasen.us. Idealy something automated could be set up.
=jbradley
On 14-Oct-08, at 7:02 PM, Chasen, Les wrote: Are we doing away with xri: altogether? Is it still ok to refer to an XRI as =les or does it have to start with a scheme in which a binding exists? http://xri.net, and all of it’s proposed forms, are still considered a proxy server, right? Is there any changes to where authority resolution servers should reside? If no, is there confusion introduced by having at.xri.net and equal.xri.net? Given this plan to change from a pattern of deducing a HXRI from ‘xri.*’ to something like ‘*.xri’ or ‘*.xri.net’ how does one bring up their own proxy. Would I be breaking with compliance if I ran a proxy at proxy.chasen.us? What about running my own authority resolution server at auth.chasen.us? Have we ever determined a criteria for new schemes? From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Tuesday, October 14, 2008 3:06 AM
To: 'OASIS XRI TC'
Subject: [xri] PLEASE REVIEW: Draft of XRI-As-Relative-URI page XRI TC Members and Observers: Per my action item from the last telecon, I have posted a first draft wiki page describing the XRI-As-Relative-URI proposal to: The next step is for TC members to review and comment on this page. As always, being a wiki, feel free to just go in and edit the page. Or, if you prefer, send feedback or question to the list. The goal is to incorporate any feedback by Wednesday so we can begin sending messages to the W3C TAG public mailing list to solicit feedback there before our next telecon this coming Thursday. Thanks, =Drummond
|