W3C home > Mailing lists > Public > www-tag@w3.org > December 2007

Re: Alternative to 303 response: Description-ID: header

From: Sean B. Palmer <sean@miscoranda.com>
Date: Sat, 15 Dec 2007 15:07:20 +0000
Message-ID: <b6bb4d890712150707i272744desff22375db5e4bbdd@mail.gmail.com>
To: "Tim Berners-Lee" <timbl@w3.org>
Cc: "David Booth" <dbooth@hp.com>, www-tag@w3.org

On Dec 5, 2007 12:53 AM, Tim Berners-Lee <timbl@w3.org> wrote:

> Description-ID:     kynase/data

It took me a little while to understand this, but I get it now from
the analogy to Content-Location. I'm struggling to weigh up its
merits.

One nice use case: it would let people who can't control a document's
headers 200-return a GRDDL document for a property merely by setting
meta[@http-equiv="Description-ID"]. For consumers this would be worse
since we'd have to parse HTML documents.

In other words, having only the 303 solution may be better since it
doesn't force us to read the entity body to disprove something being
an information resource. I'm only just starting to get to grips with
the Tabulator-level ramifications of this, but I have a feeling that
if there's a "Danger, Will Robinson!" reaction to be had, it lies
there.

P.S. I liked the Jabberwocky example. I'm going to start a new thread
summarising these other httpRange-14 happenings.

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Saturday, 15 December 2007 15:07:31 GMT

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