W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2004

Re: query parameter name clashes?

From: Steve Harris <S.W.Harris@ecs.soton.ac.uk>
Date: Fri, 17 Dec 2004 18:38:38 +0000
To: public-rdf-dawg@w3.org
Message-ID: <20041217183838.GE21159@login.ecs.soton.ac.uk>

On Fri, Dec 17, 2004 at 12:19:25 -0500, Kendall Clark wrote:
> 1. prefix all these query parameter names with a string: "dawg-" or
>    "sparql-". However, this alters or distorts the meanings of some of
>    the parameters, so perhaps a less meaningful string like "s-" is
>    better? String could be a pseudo NS local name, like: "sparql:" or
>    "dawg:". Some examples,
>    
>    /qsp?dawg:query=...&dawg:graph=...&dawg:query-lang=...
>    /qsp?sparql:query=...&sparql:graph=...&sparql:query-lang=...
>    /qsp?sparql-query=...&sparql-graph=...&sparql-query-lang=...

I'm not sure its neccesary, but I'd prefer dawg_ or dawg:, etc. to 2. 2
will not play well with HTML forms.
 
> 2. steal/pervert the XPointer syntax for a sparql() namespace in URIs
>    (not sure if there's a relevant difference here between URIs and
>    URIRefs...?).
> 
>    /qsp?dawg(query=...&query-uri=...)
>    
>    and with a "safe clash":
> 
>    /qsp?dawg(query=...)&query=...
> 
>    This isn't real XPointer, since there are no other schemes (and
>    this isn't really an XPointer scheme anyway, since it's not
>    identifying resource parts)
> 
>    Also, I don't know if wrapping our query key-value pairs in "dawg("
>    and ")" will break existing tools.

Yeah, anything that builds/parses HTTP GET URIs.

- Steve
Received on Friday, 17 December 2004 18:38:43 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:21 GMT