- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Thu, 25 Nov 2010 16:30:12 +0000
- To: Steve Harris <steve.harris@garlik.com>
- CC: SPARQL Working Group <public-rdf-dawg@w3.org>
>> As the content-type is often application/octet-stream, it can be useful for determining the syntax. :-) >> >> I have a prototype that adds a form field named-graph-uri (same name as SPARQL query protocol, different meaning). If it's "", absent or "default" it means the default graph. > > Right we use graph= as per the rest of HTTP Update, though it's pre-existing code. From a form doing an upload, the POST URL does not contain the parameters - they are in the multipart/form-data body. >> Would that be what you want? Tricky for more than one file but we could just restrict ourselves to one file for some text. > > Yes, we limit to one file at a time too. It's not been a big issue in practice. > >> 1/ Note that the 2 specs do apply to multipart/form-data >> 2/ Define it so every content-disposition: filename= means load >> as per POST for each of the SPARQL protocols. >> 3/ Define a form field "graph-uri" > > Why graph-uri? No reason - "graph" is a better choice. Changed in my prototype. Andy
Received on Thursday, 25 November 2010 16:30:44 UTC