Using SERVICE to inject pragma into the query is not exact standard ...
nor exactly spec-compliant :-)
I think that is trying to do something like a traversal of 1 to 4 in
depth and get a picture: {0,4} includes the start.
Standard SPARQL has arbitrary length traversal and can't limit the dep
> I don't know where in particular you got it
https://query.wikidata.org
That is in no way a normal SPARQL query. I don't know where in particular you
got it, but it is an example of Blazegraph/BigData's "GAS" API. It's not an
example of idiomatic SPARQL at all.
https://wiki.blazegraph.com/wiki/index.php/RDF_GAS_API
That is a specialist extension API for one product
> Could you be more specific about these intuitions and difficulties?
with other query languages such as gremlin you start from a vertex (or set of
vertices), and follow links (predicates). This is very intuitive, because it
resemble the picture of a graph that I have in mind. For example, I can
On 04/03/17 13:49, Laura Morales wrote:
well I don't have a specific use case in mind,
I just find SPARQL very counter-intuitive and difficult to reason with
Could you be more specific about these intuitions and difficulties?
Chris
On Sat, 04 Mar 2017 16:10:56 +0100, Laura Morales
wrote:
OK if I get this right, TDB is the actual database storing all
triples/n-quads, and Fuseki is a layer on top of it whose purpose is to
parse SPARQL queries and retrieve triples from TDB.
Right?
YES,
and if you are not working on
