- From: mike amundsen <mamund@yahoo.com>
- Date: Thu, 16 Jun 2011 12:20:29 -0400
- To: ashok.malhotra@oracle.com
- Cc: www-tag@w3.org
WebDAV shows that it is possible to create a new set of request methods and response codes to meet the needs of a specific set of use cases while still relying on the same app-level protocol (HTTP) all the while allowing other "non-WebDAV" clients and servers to safely co-exist on the same Web. I am surprised that the RDF community has not spent more time exploring a similar approach in order to reduce ambiguity and increase the value of both requests and responses at the transfer level (HTTP). mca http://amundsen.com/blog/ http://twitter.com@mamund http://mamund.com/foaf.rdf#me #RESTFest 2011 - Aug 18-20 http://restfest.org On Thu, Jun 16, 2011 at 12:09, ashok malhotra <ashok.malhotra@oracle.com> wrote: > > On 6/16/2011 8:28 AM, Tim Berners-Lee wrote: >> >> That said, this leaves open that if we want to invent a 209 response where >> the response contains information ABOUT the thing identified by the URI but >> not its contents, that could be useful. > > Yes, we could do that but in the situation where there is a representation > and some metadata, > you would never get a 209. So, I have been leaning toward a new getMetadata > HTTP verb but > I've been told that this is too radical. > >
Received on Thursday, 16 June 2011 16:21:07 UTC