- From: Paul Gearon <pgearon@revelytix.com>
- Date: Tue, 22 Nov 2011 10:00:51 -0500
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: public-rdf-dawg@w3.org
On Mon, Nov 21, 2011 at 9:22 AM, Andy Seaborne <andy.seaborne@epimorphics.com> wrote: > > > On 21/11/11 11:31, Steve Harris wrote: >> >> On 2011-11-21, at 09:40, Olivier Corby wrote: >> >>> On 11/16/2011 03:57 AM, Paul Gearon wrote: >>>>> >>>>> 3.1.3 DELETE/INSERT >>>>> > >>>>> > >>>>> > The bindings for each solution are then substituted into the DELETE >>>>> > template >>>>> > to remove triples, and then in the INSERT template to create new >>>>> > triples. >>>>> > >>>>> > -> Explain what happens if a variable in the template has no value >>>>> > in a >>>>> > solution: this is processed as in construct-where ... >>>> >>>> Added the following: >>>> "Variables in the template that have no binding in a solution are >>>> equivalent to a blank node. This will create a new node in an INSERT >>>> template and result in no effect in a DELETE template." >>>> >>> >>> I think that insert and construct should behave in the same way when a >>> variable is not bound : >>> >>> http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#construct >>> >>> 16.2 Construct >>> >>> "If any such instantiation produces a triple containing an unbound >>> variable or an illegal RDF construct, such as a literal in subject or >>> predicate position, then that triple is not included in the output RDF >>> graph. " >> >> +1 >> >> - Steve > > +1 Apologies, this should have been the approach in the first place. Replaced with similar text to the Construct wording: If any solution produces a triple containing an unbound variable or an illegal RDF construct, such as a literal in a subject or predicate position, then that triple is not included in the output RDF graph. Regards, Paul
Received on Tuesday, 22 November 2011 15:01:48 UTC