Re: HTTP Methods

On Feb 26, 2004, at 21:27, ext Norman Walsh wrote:

> / was heard to say:
> | I'm not sure we're completely on the same page here.
> |
> | You refer to "service descriptions". I'm talking about descriptions
> | about any arbitrary resource whatsoever. Consider an agent that
> | is harvesting knowledge from the SW, crawling from description to
> | description. For each URI encountered, having to go through the
> | gymnastics  of negotations with each server just to work out how
> | to ask for, much less get the description of each resource is not
> | my idea of a good design.
> Maybe this is covered in the URIQA paper and I've just forgotten it,
> I've printed it out again and I'll take another look on the plane this
> weekend, but...
> If you need MGET to get metadata for the data that GET would give you,
> how do you get the metadata about the data that MGET gives you?

I see I forgot to add this to the FAQ section... need to fix that..

In short, a description is a resource distinct from the resource it
is a description of. As such, it can/should have a distinct URI.

Thus, you can, using the URI of the description (which is distinct from
the URI of the resource it is a description of) MGET a description of
the description.


>                                         Be seeing you,
>                                           norm
> -- 
> Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution is prohibited.
> If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.


Patrick Stickler
Nokia, Finland

Received on Monday, 8 March 2004 08:11:10 UTC