W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2005

Re: subgraph/entailment

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Wed, 7 Sep 2005 21:10:24 -0400 (EDT)
To: jos.deroo@agfa.com, franconi@inf.unibz.it
Cc: connolly@w3.org, public-rdf-dawg@w3.org, public-rdf-dawg-request@w3.org
Message-Id: <20050907211024.DBE02040@isrmail.isr.umd.edu>

---- Original message ----
>Date: Thu, 8 Sep 2005 01:26:14 +0200
>From: jos.deroo@agfa.com  
>Subject: Re: subgraph/entailment  
>To: franconi@inf.unibz.it
>Cc: bparsia@isr.umd.edu, connolly@w3.org, public-rdf-
dawg@w3.org, public-rdf-dawg-request@w3.org
>> I should *not* get the bnode coming from the redundant
>> triple, but simply {<http://example.org/book/book1>}.
>Otoh, for
>CONSTRUCT { ?x dc:title "SPARQL" }
>WHERE { ?x dc:title "SPARQL" }
>I actually get
><http://example.org/book/book1> 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!

Received on Thursday, 8 September 2005 01:10:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:36 UTC