- From: Steve Harris <steve.harris@garlik.com>
- Date: Tue, 19 May 2009 11:46:12 +0100
- To: Kjetil Kjernsmo <Kjetil.Kjernsmo@computas.com>
- Cc: public-rdf-dawg@w3.org
On 18 May 2009, at 16:09, Kjetil Kjernsmo wrote: > On Wednesday 13 May 2009 19:06:40 Paul Gearon wrote: >> I'd like to see a standard for POSTing a file to a graph on a server, >> as this can be done easily with code or even a web form. >> Personally, I >> also like having a command that does a load (we have one in Mulgara) >> but the issues that I described make it seem difficult to standardize >> in a way that will be suitable for any type of configuration. > > I think that we also discussed PUT during the F2F, and that PUT > would entirely > replace the graph it is PUT to. Should PUT and POST do different > things? > > LOAD, should, as far as I have understood, add triples to the graph, > so the > main difference between using LOAD and HTTP PUT is that LOAD is > additive and > that HTTP PUT is used to send data on the client, whereas LOAD needs > a remote > URI. > > So, perhaps POST should add triples to the graph it posts to, to > cover all > these cases? That would match the HTTP semantics for POST, http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p2-semantics-06.txt page 16. It's supposed to be additive. - Steve -- Steve Harris Garlik Limited, 2 Sheen Road, Richmond, TW9 1AE, UK +44(0)20 8973 2465 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Tuesday, 19 May 2009 10:46:49 UTC