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

A different idea, unblogged, and not mine - but belonging to a colleague is the idea of a header (pick a name) whose value is the URI of an RDF property that states a relation (:reprentationOf, :descriptionOf ... other possible relations) between the requested resource and the returned representation.  Of course, in the absense of such a header, the default value would be :representationOf.

I thought it interesting and general.

Regards

Stuart
--
Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

> -----Original Message-----
> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]
> On Behalf Of Ian Davis
> Sent: 05 December 2007 01:57
> To: Tim Berners-Lee
> Cc: Sean B. Palmer; Booth, David (HP Software - Boston);
> www-tag@w3.org
> Subject: Re: Alternative to 303 response: Description-ID: header
>
>
>
> On Tue, 2007-12-04 at 19:53 -0500, Tim Berners-Lee wrote:
> >
> > I did wonder about the following:  in the case when the URI
> is not of
> > document, when currently we use 303, then the  server can return a
> > document *about* it with  an extra header to explain to the browser
> > that it is actually giving you a description of it not the
> content of
> > it.  (Pick a header name)
>
>
> Strange synchronicity... I posted the same idea a few minutes
> ago to my
> blog:
>
> http://iandavis.com/blog/2007/12/303-asymmetry
>
> I called my header "resource-description"
>
> Ian
>
>