On 20/09/13 18:47, Joshua TAYLOR wrote:
On Fri, Sep 20, 2013 at 1:37 PM, Joshua TAYLOR <[email protected]> wrote:
Try the "sparql" command:
sparql --strict --data empty.n3 "select * where { ?s <p>{2} ?o }"
"arq" implies the extended language and "--strict" really refers to
execution semantics. "arq --strict" could be made to be (strict) SPARQL
1.1.
sparql doesn't choke on <p>{2} either:
$ sparql --data empty.n3 "select * where { ?s <p>{2} ?o }"
---------
| s | o |
=========
---------
I misread that, and didn't include --strict when I did it. However,
it doesn't reject the query with --strict, either:
$ sparql --strict --data empty.n3 "select * where { ?s <p>{2} ?o }"
---------
| s | o |
=========
---------
However, I figured out the right --syntax argument to use:
$ sparql --syntax SPARQL_11 --data empty.n3 "select * where { ?s <p>{2} ?o }"
Encountered " "{" "{ "" at line 1, column 24.
Hmm - it looks like a command line string is always parsed in exended
mode. This is not intended.
Complains:
sparql --data empty.n3 --file Q.rq
Does not.
arq --data empty.n3 --file Q.rq
arq --data empty.n3 --file Q.arq
sparql --data empty.n3 --file Q.arq
JIRA time.
Andy
…
Sure enough, that works with arq, as well:
$ arq --syntax SPARQL_11 --data empty.n3 "select * where { ?s <p>{2} ?o }"
Encountered " "{" "{ "" at line 1, column 24.
…
