W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2011

Re: SPARQL 1.1 Protocol Conformance

From: Steve Harris <steve.harris@garlik.com>
Date: Tue, 2 Aug 2011 09:35:00 +0100
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <29A51A8F-21BA-4A34-8E0A-B879B4863D67@garlik.com>
To: Lee Feigenbaum <lee@thefigtrees.net>
I think it's probably harmless in the grand scheme of things.

Other than direct POSTing (which some toolkits may have trouble with?) it's not that tricky to support, even to just return a "method not implemented" error.

- Steve

On 2011-08-02, at 03:08, Lee Feigenbaum wrote:

> In SPARQL 1.0, conformance to the SPARQL Protocol required that an implementation implement the abstract query interface, and that if the implementation implemented the HTTP or SOAP bindings to that interface, that that be done in the manner specified in the document. (See http://www.w3.org/TR/rdf-sparql-protocol/#conformance)
> In the SPARQL 1.1 Protocol, we have these changes:
> * Added an update operation
> * Removed an abstract definition of the operation
> * Removed SOAP bindings
> * Added the ability to directly POST a query or update, in addition to via HTTP GET & POST
> So what should conformance be?
> Suggestion:
> * Implement either the query or the update operation or both
> * For any implemented operations, implement it in at least one of the ways normatively defined in the document
> This feels to me to be in the spirit of the SPARQL 1.0 Protocol... that said, I'm not thrilled with it since this is a protocol and this gives you 5 different things you can implement to be a conformant SPARQL 1.1 Protocol implementation -- that doesn't seem great to be for interoperability.
> What do you think?
> Lee

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 Tuesday, 2 August 2011 08:35:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:04 UTC