- From: Steve Harris <steve.harris@garlik.com>
- Date: Thu, 25 Nov 2010 10:40:45 +0000
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
On 2010-11-25, at 10:16, Andy Seaborne wrote: > HTML form file upload is a POST of multipart/form-data [RFC1867]. For most current browsers, it can contain a single file and some other parameters. The protocol allows multiple files. > > Is this in/out scope for the SPARQL protocol and SPARQL HTTP Update? > > It would be good for standard, documented behavior here. What is needed is: > > 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. This seems sensible, I see filename= as problematic though, as we really need a URI in there for it to be useful. 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 > A file upload is RFC 1867 and looks like: > --------------------------------------------------- > ... > Content-type: multipart/form-data, boundary=AaB03x > > --AaB03x > content-disposition: form-data; name="pics"; filename="file1.ttl" > Content-Type: text/turtle > > ... contents of file1.ttl ... > --AaB03x-- > --------------------------------------------------- > > If multiple files are selected, you get a 2 level nested multipart/form-data (outer level for the form, inner level for the files). > > Java systems can use: http://commons.apache.org/fileupload/ > > Andy > > RFC1867 > http://www.faqs.org/rfcs/rfc1867.html > http://www.ietf.org/rfc/rfc1867.txt > > -- 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 10:41:21 UTC