W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > August 2005

Re: SPARQL Protocol: inconsistent parameter names

From: Kendall Clark <kendall@monkeyfist.com>
Date: Mon, 29 Aug 2005 12:46:16 -0400
To: Arjohn Kampman <arjohn.kampman@aduna.biz>
Cc: public-rdf-dawg-comments@w3.org, kendall@monkeyfist.com
Message-ID: <20050829164616.GC4806@monkeyfist.com>

On Mon, Aug 29, 2005 at 03:32:53PM +0200, Arjohn Kampman wrote:
> Both the latest WD and the current editor's working copy specify a
> parameter/element 'sparql-query' for the actual query in the abstract
> protocol and the SOAP bindings. For the HTTP bindings, however, this
> parameter is consistently named 'query'. Is this allowed in WSDL and is
> this inconsistency intentional?

1. WSDL does allow this, but not with the way I've written the bindings.
WSDL allows someone to define a new binding that changes the parameter names
in HTTP. And, as the spec is written presently, it does not say that the
bindings (either SOAP or HTTP or both) are normative and have to be
supported for a service to be compliant.

These are issues that the WG will be taking up and we'll get back to you
with an answer.

2. The inconsistency is a mistake on my part, i.e., not intentional.

3. I'm going to rename the parameter in the HTTP bindings from "query" to
"sparql-query" -- which will also mean renaming all of the examples, too.

Thanks for yr feedback, Arjohn. Stay tuned for a response from the WG about
the issues raised in (1).

Received on Monday, 29 August 2005 16:46:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:21 UTC