Re: HTTP Methods. MGET.

:
: It's probably been mentioned already, but switching on the mime type
doesn't
: work as-is, as the RDF/XML won't usually be about the resource identified
by
: the uri. I've a feeling Patrick also had an answer for the suggestion of a
: different mime type...

Abstracting from the actual protocol implementations for a second, is it
true that all that is needed is some way to unambiguously mark a GET
request so it's clear that it's asking for resource.description, as opposed
to resource.representation?  I don't believe I've ever witnessed consensus
on that yet in this thread.

[snip]

: Incidentally, Roy states "doubling method space is evil", and shows a
: similar sentiment about halving method space, as HTML forms tends towards.
: Is this because it has been determined (through formal reasoning?) we have
: *exactly* the methods we'll ever need, or merely that only minor,
: incremental additions/reductions should be considered?

Sorry if I failed to find the answer to this in Patrick's publications, but
if
MGET is the vehicle into description space, and descriptions are properly
identified resources, then are the other M* methods really needed?  If not,
then the "doubling" problem is mitigated, right?

--Walden

Received on Saturday, 28 February 2004 10:01:48 UTC