Re: Carrying raw query strings (public API change).
On 13/04/12 17:00, Robert Vesse wrote:
The more I think about this the less I think it actually solves our
problem (it being carrying raw query strings) because we are still
left with the issue that a query may turn into multiple queries
internally and our developers wanted the query string to associate
with each of those internal queries but that isn't a 1:1
relationship
Maybe it is for the best if I just go ahead and revert those
changes?
I was removing some unfinished stuff in Query so I took the liberty of
reverting the changes in passing. Hope that's OK.
The "unfinished stuff" was the syntax part of having inline data (AKA
BINDINGS anywhere in a query). It wasn't going anywhere and there is a
better way.
Stephen's comment to SPARQL-WG is one of several:
http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2012Apr/0010.html
The SPARQL-WG is considering (but has not decided whether to do or not
do yet) allowing BINDINGS anywhere in a {}-block, which generalises the
subquery, or removes the need for placeholder { SELECT * WHERE { } }
just to attach the BINDINGS.
Going as far as referencing external data (the results of a previous
query) is too radical at this stage for standardisation but it's a
logical step for an ARQ extension.
Andy
