W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

Re: Operations on containers

From: Henry Story <henry.story@bblfish.net>
Date: Fri, 19 Oct 2012 18:01:16 +0200
Cc: Andy Seaborne <andy.seaborne@epimorphics.com>, Arnaud Le Hors <lehors@us.ibm.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-Id: <D09803C1-3E1F-4C15-B61A-CD0B8C091454@bblfish.net>
To: Roger Menday <roger.menday@uk.fujitsu.com>

On 19 Oct 2012, at 17:14, Roger Menday <roger.menday@uk.fujitsu.com> wrote:

>> 
>>> A logical consequence would then be to allow creating a resource within
>>> a container using PUT in the same way.
>> 
>> Could you explain that?  My understanding is that PUT replaces the 
>> entire contents at the target.
>> 
>> ---------
>> PUT /foo
>> Host: example.com
>> 
>> <> a foaf:document .
>> ---------
>> had better put that RDF at the requests target (adding server 
>> properties) and have <> as <http://example.com/foo>
> 
> Well, I agree that the PUT would need to name the resource - which actually, would help in the "what is URI of POSTed document" discussion :) 


A PUT with a relative URI should also be able to work fine. That would allow
one to build templates which one could then PUT at locations, without the client
needing to serialise and deserialise the document locally.

It is not as serious as the issue with POST, but it is a nice consequence of allowing
it for POST that it should work with PUT too.


> 
> but, really, I think we need to think about how we are using POST. 
> Would it be possible to have a new issue to re-consider this assumption please Arnaud ? 
> 
> thanks, 
> Roger
> 
>> or things get very 
>> weird in the relationship of PUT then a GET on the same URI.
>> 
>> 	Andy
>> 
>> 
> 

Social Web Architect
http://bblfish.net/


Received on Friday, 19 October 2012 16:01:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC