RE: Semantic content negotiation (was Re: expectations of vocabulary)

--Danny,
 
> (I don't know either way if Accept-Vocabulary specifically is 
> a good idea, but it illustrates the point, there doesn't seem 
> to be any architectural obstacle to content negotiation at a 
> semantic level).

Any specification must have semantics to drive certain actions.  The
semantic domain dealt in HTTP protocol does not and should not overlap with
the semantic domain of the RDF model.  The semantic domain of HTTP is
Information Resources.  Each IR is treated as an atomic unit and HTTP GET
worries how to get a representation of that resource across the network.
Whether the representation is in what langauge and in what format does not
break that the assumption that the resource is atomic.  Accept langauge,
character encoding, Synonymy etc., is all fine because it does not break
that assumption.  But if you extend the HTTP in a way that you will break
the resource into various pieces, you goes out of the semantic domain of the
HTTP GET. You probably need to do an HTTP POST or use a different URI, such
as by appending some query parameters, to alter the state of the
representation, but not by HTTP GET.

It is a misguided argument to say: ... at a semantic level.  Without a
clearly defined semantic domain, this kind of sentences can be used to argue
for anything.  Is this what you want?

Xiaoshu

Received on Wednesday, 26 July 2006 18:24:59 UTC