Protocol

From SPARQL Working Group
Revision as of 15:28, 11 January 2011 by Lfeigenb (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

SPARQL Protocol open issues & TODOs

Protocol HTTP Only

Consensus at 2011-01-11 teleconference that the protocol should be HTTP only and not bebased on WSDL.

JSON-P

Relationship to CORS?


What do you send for a SPARQL update request?

PROPOSED: SPARQL Update requests can be POSTed as either application/x-www-form-urlencoded or application/sparql-update, pending discovery of how to do the latter in WSDL 2


Response content

See http://www.w3.org/2009/sparql/track/issues/60

Agreement that there's no mandataed response value. Suggest text:

If an update request is successful, a 2xx or 303 HTTP status code must be returned?

Stay silent and include examples.


Faults

See http://www.w3.org/2009/sparql/track/issues/33 .

Content (and content type) of error messages

...implementations SHOULD return a text/plain response with human-readable information about the error.

Include HTTP Patch?

http://www.w3.org/2009/sparql/track/issues/56

Recommend not including anything about HTTP Patch at this time.

MIME type?

http://www.w3.org/2009/sparql/track/issues/58

RDF Datasets and protocol for update

PROPOSED: SPARQL Update protocol requests can include default-graph-uri and named-graph-uri parameters that define an RDF dataset for all operations within the update request that make use of an RDF dataset (i.e. have a WHERE { ... } part. The RDF dataset specified in the protocol replaces any RDF dataset that appears in the operations in the update request string.

Examples of SPARQL Update requests

Security section

See http://www.w3.org/2009/sparql/track/issues/19 .

Service description

Protocol document should mention that doing a GET on an endpoint gives you the service description.