W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2010

Re: POST & HTTP Update

From: Steve Harris <steve.harris@garlik.com>
Date: Thu, 25 Nov 2010 18:09:33 +0000
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <DD77A996-1BEB-4550-B08F-BAA06146C34D@garlik.com>
To: Andy Seaborne <andy.seaborne@epimorphics.com>
On 2010-11-25, at 16:34, Andy Seaborne wrote:
> 
> On 25/11/10 16:15, Steve Harris wrote:
>> On 2010-11-25, at 14:50, Andy Seaborne wrote:
>>> 
>>> On 25/11/10 10:40, Steve Harris wrote:
>>> ..
>>>> The fact that POST updates are not yet fully specified in http://www.w3.org/TR/sparql11-http-rdf-update/#http-post is a source of concern to us.
>>>> 
>>>> - Steve
>>> 
>>> Could you say what isn't specified and should be?
>> 
>> I don't remember exactly. I think it wasn't clear if the payload should me a mime form, or GET-style URI fields.
>> 
>>> Currently I use the Content-type to get the syntax, the body is the payload and payload = RDF document from earlier in the spec.
>> 
>> Where do you get the graph URI from?
> 
> If it's an http-rdf-update POST, it's ?graph= or ?default as for all the other operations specifically PUT.
> 
> That's hard to drive from a form - need a bit of client-side code to create the URL to POST to).  I don't drive HTTP RDF Update from a plain HTML form.

We do, though we also mostly use libraries / command line tools that construct the POST, but it's closer to the other method you were discussing.

- Steve

-- 
Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203  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 Thursday, 25 November 2010 18:10:12 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:44 GMT