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

Changes since LC for Update

From: Polleres, Axel <axel.polleres@siemens.com>
Date: Tue, 30 Oct 2012 14:26:52 +0100
To: "public-rdf-dawg@w3.org" <public-rdf-dawg@w3.org>
Message-ID: <9DA51FFE5E84464082D7A089342DEEE8014E00D9B53F@ATVIES9917WMSX.ww300.siemens.net>
Dear all,

I don't have CVS access at the moment, but as for 
http://www.w3.org/2009/sparql/meeting/2012-10-23#line0058

here is the list of changes since LC which I had promised 
for Update (which I generated mostly summarizing the CVS History in the end of the document) :

---------------------------------------


The following editorial changes have been made since LC:

1) We have updated Section 2.2 to describe the use of the word 'atomically'   
2) We changed the explaining text for MOVE and COPY in sections 3.2.3 and 3.2.4 
   to describe *similarity* to DROP/INSERT (instead of equivalence), and explaining the differences.
3) We fixed the example in Section 3.1.3 illustrating the use of the 'WITH' clause.
4) We fixed the explaining note after the Definition of the Clear Operation in Seciton 4.3.5.
5) We have added explaining text in Section 3.2.1 clarifying that a CREATE (SILENT) operation 
   does not affect the contents of already existing graphs.
6) We fixed a syntax error in Table 1 in Section 4.5 for the LOAD INTO operation (which was missing the non-optional GRAPH keyword)
7) We have added explaining wording in Section 3.1.4 clarifying that if the destination graph already exists in a LOAD INTO operation, then no data in that graph will be removed.
8) We have added an explanation of "QuadData" in Section "1.1.2 Terminology".
9) We have added a link to the remarks on scoping of blank nodes within requests in the SPARQL grammar, http://www.w3.org/TR/sparql11-query/#grammarBNodeLabels
   in the explaining note after the Definition of Dataset( QuadPattern,  , DS, GS ) in section 4.2.3
10) We added an editorial note in Section 2.3 noting that Updates may interact with entailment regimes in RDF stores that support these
11) We refined the clarifying text in Section 3.1.3 explaining how invalid triples resulting from instantiating 
    DELETE or INSERT clauses are treated.
12) several typos have been fixed across the document 

---------------------------------------


I think this should be detailed enough.

Best,
Axel
Received on Tuesday, 30 October 2012 13:27:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:49 GMT