On 10/01/14 19:46, Phil Ashworth wrote:
Thanks Andy
One quick question:
Should I stop using the QueryExecutionFactory.sparqlService
method completely or are are there circumstances where it is good to
use it?
If you are just putting a SERVICE inside a WHERE clause of SELECT * ,
with no other pattern (local or other SERVICE) then it is two routes to
much the same thing.
If the top-level (local) query has ORDER BY, LIMIT etc then it makes a
difference - using QueryExecutionFactory.sparqlService sends it all to
the far end and result stream back. Otherwise the ORDER BY, LIMIT is
done locally which can be less efficient.
And personally I'd use QueryExecutionFactory.sparqlService so the
service URI is not in the query.
If you want to abstract away from local vs remote, you may find this
experimental module useful:
https://svn.apache.org/repos/asf/jena/Experimental/jena-client/
and there is also:
https://github.com/AKSW/jena-sparql-api
Andy
Many thanks again.
Phil
On Fri, Jan 10, 2014 at 7:29 PM, Andy Seaborne <[email protected]> wrote:
On Fri, Jan 10, 2014 at 2:04 PM, Phil Ashworth <[email protected]>
wrote:
I can't find an exact code example but I did find the documentation about
using the Syntax.syntaxARQ.
Out of date documentation - it's part of standard SPARQL 1.1 these days.
Andy
