Difference between revisions of "CommentResponse:RV-10"

From SPARQL Working Group
Jump to: navigation, search
Line 48: Line 48:
 
1. http://lists.w3.org/Archives/Public/public-rdf-dawg/2012AprJun/0163.html
 
1. http://lists.w3.org/Archives/Public/public-rdf-dawg/2012AprJun/0163.html
  
>> From: Rob Vesse [mailto:rvesse@dotnetrdf.org]
+
>> From: Rob Vesse [mailto:rvesse@dotnetrdf.org]
>> Sent: Dienstag, 18. September 2012 18:05
+
>> Sent: Dienstag, 18. September 2012 18:05
>> To: Polleres, Axel
+
>> To: Polleres, Axel
>> Subject: Re: Further comment on SPARQL 1.1 Test Cases
+
>> Subject: Re: Further comment on SPARQL 1.1 Test Cases
>>  
+
>>  
>> Hi Axel
+
>> Hi Axel
>>  
+
>>  
>> Perhaps if the group were to amending the following text from 3.1.1 INSERT
+
>> Perhaps if the group were to amending the following text from 3.1.1 INSERT
>> DATA
+
>> DATA
>>  
+
>>  
>> Variables in QuadDatas are disallowed in INSERT DATA requests (see Notes 8 in
+
>> Variables in QuadDatas are disallowed in INSERT DATA requests (see Notes 8 in
>> the grammar <http://www.w3.org/TR/sparql11-query/#sparqlGrammar> ). That is,
+
>> the grammar <http://www.w3.org/TR/sparql11-query/#sparqlGrammar> ). That is,
>> the INSERT DATA statement only allows to insert ground triples. Blank nodes
+
>> the INSERT DATA statement only allows to insert ground triples. Blank nodes
>> in QuadDatas are assumed to be disjoint from the blank nodes in the Graph
+
>> in QuadDatas are assumed to be disjoint from the blank nodes in the Graph
>> Store, i.e., will be inserted with "fresh" blank nodes.
+
>> Store, i.e., will be inserted with "fresh" blank nodes.
>>  
+
>>  
>> And add additional text something like the following:
+
>> And add additional text something like the following:
>>  
+
>>  
>> Per Note 10 in the grammar blank node identifiers may be reused across graph
+
>> Per Note 10 in the grammar blank node identifiers may be reused across graph
>> blocks in QuadData but users should note that distinct fresh blank nodes will
+
>> blocks in QuadData but users should note that distinct fresh blank nodes will
>> be generated for each usage in each block.
+
>> be generated for each usage in each block.
>>  
+
>>  
>> That's a little clunky but I'm sure the WG can come up with something a
+
>> That's a little clunky but I'm sure the WG can come up with something a
>> little more flowing that gets the clarification across, it's primarily just a
+
>> little more flowing that gets the clarification across, it's primarily just a
>> case of referring back to that note in the main query document.
+
>> case of referring back to that note in the main query document.
>>  
+
>>  
>> Thanks,
+
>> Thanks,
>>  
+
>>  
>> Rob
+
>> Rob

Revision as of 09:33, 25 September 2012

Hi Rob,

This is a joint response to

http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2012Sep/0024.html

and

http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2012Sep/0025.html

First of all thanks for your concrete editorial suggestions! We implemented them as follows:

1) We have adapted your editorial suggestion in Update:

--------------------------
Variables in QuadDatas are disallowed in INSERT DATA requests
(see Note 8 in the grammar). That is, the INSERT DATA statement
only allows to insert ground triples. Blank nodes in QuadData
are assumed to be disjoint from the blank nodes in the Graph Store,
i.e., will be inserted with "fresh"  blank nodes.
--------------------------

2) We have edited Note 10. in the Grammar

    http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#sparqlGrammar

as follows

--------------------------
A blank label can be used in only a single basic graph 
pattern in a query. This only applies to graph patterns 
in the where clause, not to QuadPattern nor QuadData./
--------------------------

Please note that the further text you proposes, namely

"users should note that distinct fresh blank nodes will be generated for each usage in each block."

disagrees with what we had discussed in thread thread [1], that is, shared blank nodes across QuadPatterns within the same insert operation are allowed and behave similar as in test case http://www.w3.org/2009/sparql/docs/tests/data-sparql11/basic-update/manifest#insert-05a. We have created a new test case

http://www.w3.org/2009/sparql/docs/tests/data-sparql11/basic-update/manifest#insert-data-same-bnode

that is a variant of insert-05a to make this clear.

3) To further clarify the spec text, we have also added clarifying text to Section 19.6

 of the Query document, cf. http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#grammarBNodeLabels

We hope this answers your concerns and would appreciate a response to the list acknowledging this.

Thanks, Axel, on behalf of the SPARQL WG.

1. http://lists.w3.org/Archives/Public/public-rdf-dawg/2012AprJun/0163.html

>> From: Rob Vesse [1]
>> Sent: Dienstag, 18. September 2012 18:05
>> To: Polleres, Axel
>> Subject: Re: Further comment on SPARQL 1.1 Test Cases
>> 
>> Hi Axel
>> 
>> Perhaps if the group were to amending the following text from 3.1.1 INSERT
>> DATA
>> 
>> Variables in QuadDatas are disallowed in INSERT DATA requests (see Notes 8 in
>> the grammar <http://www.w3.org/TR/sparql11-query/#sparqlGrammar> ). That is,
>> the INSERT DATA statement only allows to insert ground triples. Blank nodes
>> in QuadDatas are assumed to be disjoint from the blank nodes in the Graph
>> Store, i.e., will be inserted with "fresh" blank nodes.
>> 
>> And add additional text something like the following:
>> 
>> Per Note 10 in the grammar blank node identifiers may be reused across graph
>> blocks in QuadData but users should note that distinct fresh blank nodes will
>> be generated for each usage in each block.
>> 
>> That's a little clunky but I'm sure the WG can come up with something a
>> little more flowing that gets the clarification across, it's primarily just a
>> case of referring back to that note in the main query document.
>> 
>> Thanks,
>> 
>> Rob