W3C home > Mailing lists > Public > www-tag@w3.org > July 2008

RE: Boeing XRI Use Cases

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Fri, 18 Jul 2008 19:46:19 +0000
To: John Bradley <john.bradley@wingaa.com>, "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>
CC: Drummond Reed <drummond.reed@cordance.net>, 'Paul Prescod' <paul@prescod.net>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <184112FE564ADF4F8F9C3FA01AE50009FCFC5E79DF@G1W0486.americas.hpqcorp.net>

> From: John Bradley [mailto:john.bradley@wingaa.com]
> [ . . . ]
> An idea I have kicked around with a number of people that may
> fit David's model is to use a domain or TLD as the "clear
> chain of authority" root.
>
> The difference being that all identifiers under that DNS root
> would be interpreted as the appropriate sub scheme.
>
> As an example the domain name boeing.com.xri.net would be
> interpreted as an XRI by the client software.  DNS would be
> configured to return the ip address of Boeing's HXRI proxy server.
>
> I could use
> http://plaxo.com.xri.net/(http://boeing.com)*jbradley if that
> was the proxy that was optimal for me,  a client application
> could also recognize it as being a synonym for
> http://boeing.com.xri.net/(http://boeing.com)*jbradley

Cute!  That is semantically similar to what I had suggested, but would better exploit DNS.  That looks like a good approach:

 - it retains a clear chain of authority for determining how the URI should be interpreted;

 - its XRI semantics would be recognizable by XRI-aware clients; and

 - it is still usable by clients that are not XRI-aware.

My concerns would be fully addressed if the XRI TC dropped the xri: scheme and adopted this form as the canonical serialization for XRIs.



David Booth, Ph.D.
HP Software
+1 617 629 8881 office  |  dbooth@hp.com
http://www.hp.com/go/software

Statements made herein represent the views of the author and do not necessarily represent the official views of HP unless explicitly so stated.
Received on Friday, 18 July 2008 19:47:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:23 UTC