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

RE: [XRI] Back to XRI

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Fri, 12 Sep 2008 19:46:02 +0000
To: John Bradley <john.bradley@wingaa.com>
CC: "elharo@metalab.unc.edu" <elharo@metalab.unc.edu>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <CD2B872281385A439B98164F5351E6DD24CF9F5B3A@GVW1144EXB.americas.hpqcorp.net>

> From: John Bradley [mailto:john.bradley@wingaa.com]
> [ . . . ]
> One of the things that we need the most work on is how to
> perform what
> might be thought of meta-data content negotiation for URI that are
> about "things".
>
> The best solution we have found at this point is to use Link Headers
> to indicate where the related meta-data can be found at distinct URI.
> This is would be consistent with Mark Nottingham's draft
> recommendations:
> http://www.mnot.net/drafts/draft-nottingham-http-link-header-01.txt
> This clearly requires an extra GET that some users are resistant to.

If the metadata can be in an arbitrary location then it does sound like the extra GET may be unavoidable.  But if the metadata can always be at a predictable location relative to the original URI, and you can figure out a simple pattern matching rule to convert the original URI to the metadata URI, then a smart agent could inspect the first URI, determine that it uses the XRI http subscheme convention, and use the pattern match to transform it into the metadata URI without doing a GET on the original URI.  Would that be a viable approach for you?



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, 12 September 2008 19:48:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:06 GMT