You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If QLever follows the SPARQL specification by the book the default graph of a dataset has no name and is composed of all triples, i.e. all statements not contained in a specific named graph. That however is a bit under-specified in practice which is why most quad stores implement some way to refer to the default graph by name, e.g. urn:x-sparql:default and/or configure it to be the union (or merge) of all triples in the dataset, irrespective of the named graph they are contained in, or some other arrangement. How does Qlever handle this issue, or what are your plans?
The text was updated successfully, but these errors were encountered:
All triples that are not explicitly assigned to a graph, are assigned to the default graph, which in QLever has the name ql:default-graph. For example: https://qlever.cs.uni-freiburg.de/olympics/V85gwp
When you don't specify a FROM, FROM NAMED, or GRAPH in the query, you effectively query the union graph
That looked the most natural to us. What do you suggest?
@hannahbast That looks good to me too . Although not to spec it is probably the most sensible default configuration. At least it covers my use cases, and you are not alone with this approach.
AFAICT most quad stores either default to the union graph as the default graph, or provide this configuration as an option in addition to the configuration as specified in SPARQL.
Providing a reference to the default graph is very useful too. Some quad stores provide specific identifiers also for the union graph, i.e. all triples in the store, inclusive the default graph and/or the union of all named graphs, but exclusive the default graph. Those would seem like sensible companions to ql:default-graph. I'm not aware of stores that even differentiate between union and merge, and unless one would strive for completeness that seems unlikely to happen.
You probably are aware of the discussions in the SPARQL 1.2 Community Group, e.g. here, here and here (and I'm adding the links here just for completeness, or other readers).
If QLever follows the SPARQL specification by the book the default graph of a dataset has no name and is composed of all triples, i.e. all statements not contained in a specific named graph. That however is a bit under-specified in practice which is why most quad stores implement some way to refer to the default graph by name, e.g. urn:x-sparql:default and/or configure it to be the union (or merge) of all triples in the dataset, irrespective of the named graph they are contained in, or some other arrangement. How does Qlever handle this issue, or what are your plans?
The text was updated successfully, but these errors were encountered: