W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2012

changes on update (ACTION-693 & adding anchors for #operation and #request)

From: Polleres, Axel <axel.polleres@siemens.com>
Date: Wed, 3 Oct 2012 16:49:53 +0200
To: "public-rdf-dawg@w3.org" <public-rdf-dawg@w3.org>
Message-ID: <9DA51FFE5E84464082D7A089342DEEE80149E378BAC0@ATVIES9917WMSX.ww300.siemens.net>
Dear all,


In completion of ACTION-693, I changed (and actually simplified) wording in Section 
as follows (basically just removing superfluous text now):

   <p>The function sk<sub></sub> guarantees 
-  on the one hand 
   that "fresh" blank nodes in the QuadPattern are 
   re-instantiated "per solution"  (analogous to the 
-  <a href="http://www.w3.org/TR/sparql11-query/#tempatesWithBNodes">treatment 
+  <a href="http://www.w3.org/TR/sparql11-query/#tempatesWithBNodes"> treatment 
   of blank nodes in <code>CONSTRUCT</code> templates</a> in the 
   <a href="http://www.w3.org/TR/sparql11-query/">SPARQL1.1 Query Language</a>) 
-  and on the other hand that blank nodes reused within an update request are scoped over the entire request
   ; cf. also the respective <a href="http://www.w3.org/TR/sparql11-query/#grammarBNodeLabels"> 
   remarks on scoping of blank nodes within requests in the SPARQL grammar</a>. 
-  Note that two solution mappings <sub>1</sub> and <sub>2</sub>, stemming from two 
-  different WHERE clauses within the same request yield different 
-  blank nodes with regards to sk, even if <sub>1</sub> and <sub>2</sub> 
-  agree on domain and variable assignments.

2) I have added anchors for "#operation and "#request" in the terminology section as per Andy's suggestion.

Received on Wednesday, 3 October 2012 14:50:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:07 UTC