W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

RE: Reviving HTTP Header Linking: Some code and use-cases

From: Brian Smith <brian@briansmith.org>
Date: Wed, 12 Mar 2008 06:03:47 -0700
To: <ietf-http-wg@w3.org>
Message-ID: <002001c88441$830e6b00$4001a8c0@T60>

Roy T. Fielding wrote:
> However, RDF pretty much screwed us all on that one, so the 
> reasonable next step is to allow URIs and have all flat names 
> be relative to the same link relationship registry as Atom.

HTTP cannot share the same link registry as Atom unless the Atom link
registry is completely redone. The whole registry is specific to Atom or
feed processing.

Furthermore, the Atom mechanism for registration means that any
registered link relation has two names: "xxx" and
"http://www.iana.org/assignments/relation/xxx". This has made processing
links in Atom feeds unnecessarily tedious. It would be better to come up
with a new mechanism that either required everything to be an IRI or at
least didn't allow registered link relations to be used with the IRI
form.

The Atom mechanism does comparisons character-for-character. An IRI and
its URI equivalent do not match. That means that RFC 3987 IRI-URI
conversion cannot be used for the Link header; instead, something like
percent-encoded Unicode would be needed.

The "title" subfield is also problematic. It must be properly
internationalized, including proper support for Ruby annotations and
BIDI text. If that can happen, then I would like to see a "Title:"
header field too, so that I can HEAD a document to get its title. 

- Brian
Received on Wednesday, 12 March 2008 13:03:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:37 GMT