RE: get metadata (was RE: WS-Addr issues

Mark,

There's a big difference between GETting the state of a resource (which
may or may not be a metadata resource), GETting the metadata of a
resource (which may or may not be a metadata resource), and GETting the
state of a metadata resource.  There are only 2 solutions to GET
metadata about a resource that you don't know is a metadata resource:
either have 2 different operations (GET state and GETMETADATA state) or
have mechanism to convert an identifier into a metadata URI (URI +=
"?WSDL" ? ).  

To a great deal, http-range-14 is TimBL's attempt to make all http:
resources into metadata so as to avoid the 2 verb problem for the
semantic web.

Cheers,
Dave

> -----Original Message-----
> From: public-ws-addressing-request@w3.org
[mailto:public-ws-addressing-
> request@w3.org] On Behalf Of Mark Baker
> Sent: Thursday, November 04, 2004 7:03 AM
> To: public-ws-addressing@w3.org
> Subject: get metadata (was RE: WS-Addr issues
> 
> 
> > I agree that there should be a getmetadata operation that should be
> > usable by anyone not just ws-addressing.  That safely removes it
from
> > the scope of ws-addressing without us having to talk about charter
and
> > timelines :-)
> 
> Well, I think a much stronger case could be made for doing this if the
> operation were simply "GET" (I thought you were an 80/20 GET guy now,
> Dave? 8-) and a derefencable URI is used.  Then you only have to
> specify a new term that means "this resource is metadata about this
> other resource".  There might already be done, for all I know; a quick
> scan of Dublin Core didn't turn anything up, but somebody else might
> have defined one.
> 
> Mark.
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Received on Thursday, 4 November 2004 17:07:33 UTC