- From: Andy Seaborne <andy.seaborne@talis.com>
- Date: Tue, 13 Jul 2010 10:21:11 +0100
- To: SPARQL Working Group <public-rdf-dawg@w3.org>
Looking at Matt's tests for delete ...
SPARQL queries have a registered media type, "application/sparql-query",
which includes the file extension ".rq":
http://www.w3.org/TR/rdf-sparql-query/#mediaType
What should we do for SPARQL Update? Register a SPARQL Update media
type, and extension (?? .ru) or reuse application/sparql-query? I
prefer to register a new media type and associated file extension - it
would be helpful to be able to spot incoming SPARQL Update requests by
MIME type. And it is two languages, not one.
And the protocol question:
One of the confusions I encountered is the difference between sending an
update from a HTML form, with param "request=" in the body, compared to
simply POSTing the request. Joseki attempts to detect the different
situations; the confusion arises when client app code sends a malformed
request, just putting the request in the body, but still setting
application/x-www-form-urlencoded.
I had assumed that the SPARQL protocol for updates ovr HTTP would be
POSTing the update request, together with an appropriate MIME type.
Or does a client need to send "update-request=" (and
application/x-www-form-urlencoded).
A design issue is that some SPARQL Update requests might be very large
(e.g. INSERT DATA { .... }) and so designing so streaming processing
that request could be helpful.
Andy
Received on Tuesday, 13 July 2010 09:21:43 UTC