On Mon, Jul 2, 2012 at 3:11 PM, Joshua TAYLOR <[email protected]> wrote:
> Is this the expected behavior? BINDINGS doesn't seem to be rejected,
> but silently ignored. I know that initial bindings can be set
> programmatically through the API, so I figured that BINDINGS would
> work too, but it doesn't seem to.
It occurred to me that I wasn't using the latest Jena and ARQ, so I
just downloaded those, and BINDINGS still doesn't work, but now, at
least, it triggers a parsing error:
$ /usr/local/lib/apache-jena-2.7.2/bin/arq --version
Jena: VERSION: 2.7.2
Jena: BUILD_DATE: 2012-06-28T14:39:01+0100
ARQ: VERSION: 2.9.2
ARQ: BUILD_DATE: 2012-06-28T14:39:01+0100
$ /usr/local/lib/apache-jena-2.7.2/bin/arq -v --debug --query
book_query.sparql --data book_data.n3
Encountered " "bind" "BIND "" at line 10, column 1.
Was expecting one of:
<EOF>
"limit" ...
"offset" ...
"order" ...
"values" ...
"group" ...
"having" ...
This is, at least, a different behavior, but still not one that works
with BINDINGS.
--
Joshua Taylor, http://www.cs.rpi.edu/~tayloj/
