RE: Resources and representations (was RE: Subgroup to handle semantics of HTTP etc?)

> From: Williams, Stuart (HP Labs, Bristol)
> [ . . . ]
> If you're using # URIs then you arrange things thus:
>
>   http://example.com/things#dog               refers to a dog;
>   http:///example.com/things                  refers to a
> resource that includes (maybe amongst other things) a
> description the referenced dog.
>
> The request line of the HTTP protocol does NOT carry the
> fragment part of the URI.
> You do not, cannot, get a representation of the #dog URI by
> doing HTTP get using that URI.
> What you get is a representation of something else... using
> David Booths terminology,
> you get a representation of whatever the radix of the URI
> refers to (or at least you try to).

I think you meant "racine" instead of "radix".  And BTW, I did not coin the term "racine", I got it from CWM code that TimBL checked in on 29-Dec-2001:
http://dev.w3.org/cvsweb/2000/10/swap/log.n3?rev=1.14&content-type=text/x-cvsweb-markup


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

Opinions expressed herein are those of the author and do not represent the official views of HP unless explicitly stated otherwise.

Received on Wednesday, 24 October 2007 14:28:25 UTC