Are you sure you are using the latest version of ARQ? What version are
you using?
For reference current version is the newly released 2.9.4 and current
snapshot version is 2.9.5-SNAPSHOT
ARQ has supported the values clause for some time and is 100% SPARQL 1.1
compliant, so either you have the wrong version of ARQ in your class path
or you are somehow invoking the query parser in SPARQL 1.0 mode instead of
SPARQL 1.1 mode (SPARQL 1.1 is the default)
You can add the following to your code to print out the version
information from the ARQ JAR at runtime:
Version jenaVer = new Version();
jenaVer.addClass(Jena.class);
jenaVer.addClass(ARQ.class);
jenaVer.print();
This will allow you to see if you have a mismatch between the version of
ARQ you think you are using and the version being picked up at runtime.
You can also run Fuseki with the --version option to just print version
information and exit to confirm that you are using an up to date version
of Fuseki as well.
Hope this helps?
Rob
On 10/25/12 9:10 AM, "Audun Stolpe" <audunsto...@gmail.com> wrote:
>Hi I am experiencing trouble getting ARQ to parse a query with the new
>VALUES keyword in it. A simple select like
>
>SELECT ?area WHERE {
>
>?person <http://dbpedia.org/ontology/birthPlace> ?area.
>VALUES ?person {<http://dbpedia.org/resource/Peder_Christian_Andersen>}
>
>}
>
>Passed to the QueryExecutionFactory.sparqlService(endpoint, test), where
>'test' is the above query and 'endpoint' is a local Fuseki instance of the
>latest build, gives the following error message:
>
>Exception in thread "main" com.hp.hpl.jena.query.QueryParseException:
>Lexical error at line 1, column 88. Encountered: " " (32), after :
>"VALUES".
>
>I'm using the latest snapshot of ARQ, which leads me to believe that
>VALUES
>isn't yet implemented? Would anyone want to enlighten me?
>
>Best,
>
>Audun
