Re: subgraph/entailment

Enrico Franconi wrote:
> On 8 Sep 2005, at 10:03, wrote:
>>>>>>I should *not* get the bnode coming from the redundant
>>>>>>triple, but simply {<>}.
>>>>>Otoh, for
>>>>>CONSTRUCT { ?x dc:title "SPARQL" }
>>>>>WHERE { ?x dc:title "SPARQL" }
>>>>>I actually get
>>>>><> dc:title "SPARQL".
>>>>>_:b_0_ dc:title "SPARQL".
>>>>>which I assume to be fine, no?
>>>>The result form shouldn't affect the (number of) results
>>>>unless there's something expicit in the form which does that
>>>>(which I don't think is true for construct). At least,
>>>>that's what I would expect!
>>>Indeed. I expect no bnode in this case too, independently on
>>>the type of query, since the answer should be the same as the
>>>one with the dataset without the bnode.
>>The CONSTRUCT result form returns a single RDF graph
>>specified by a graph template. The result is an RDF
>>graph formed by taking each query solution in the
>>solution sequence, substituting for the variables
>>into the graph template and combining the triples
>>into a single RDF graph by set union.
>><> dc:title "SPARQL".
>>_:b_0_ dc:title "SPARQL".
>>is a single RDF graph and a single result and I don't
>>see any issue wrt to bnodes or minimality in it;
>>what is the issue in this case?
> As I argued with my latest long email < 
>>, there only one binding (query  
> solution) for ?x according to RDF-MT semantics, namely <http:// 
> Therefore, substituting the variable ?x in the graph template gives  
> you only the triple
> <> dc:title "SPARQL".
> even in the case of the dataset
> <> dc:title "SPARQL" .
> _:b dc:title "SPARQL" .
> Is there something I'm missing?
> --e.

For SPARQL to be useable, it must be possible to make queries against the 
exact triples in the base data.  Other modes shoudl also be possible 
determined by what service/graph/repository is being queried.

It must be possible to access the base data for SPARQL to be useable for any 
application that is involved in building a graph while at the same time 
accessing it.  I coined the term "zero-entailment" as I couldn't find extsing 

I understand this to be part of the "Local Query" requirement. I had in mind 
that the query language be usable in applications that require access to the 
base data so they can add new triples, and they themselves deliver inference 
services to other applications.

We have already received comments where application require explicit access to 
the base data.  See the long thread starting from:
which includes explaination of the usage.


Received on Thursday, 8 September 2005 08:38:01 UTC