- From: Polleres, Axel <axel.polleres@siemens.com>
- Date: Thu, 5 Jul 2012 11:51:31 +0200
- To: "public-rdf-dawg@w3.org" <public-rdf-dawg@w3.org>
A student of mine just pointed me to a small thing which I wanted to ask your opinions on: For DROP, CLEAR, CREATE, and LOAD the GRAPH keyword is obligatory, i.e. you have to write: DROP GRAPH iri LOAD INTO GRAPH iri ... but can't simply write DROP iri LOAD INTO iri The student realized this, since we have some example in http://www.w3.org/TR/sparql11-update/#mappingRequestsToOperations in Table 1 where we forgot the GRAPH keyword... Couldn't we make 'GRAPH' optional here, just as 'WHERE' is optional in WhereClause, i.e. change the GraphRef production s/ [46] GraphRef ::= 'GRAPH' iri / [46] GraphRef ::= 'GRAPH'? iri / This would seem to be a minor, but handy change and still possible as long as we are still before LC publication for the grammar along with the Query document: I think making the GRAPH keyword OPTIONAL here would still be a minor enough change for Update to call it "editorial", since it doesn't invalidate anything from the LC version. The implied changes would be: Query: Update: mark the GRAPH keyword optional in Section 3.1.4 LOAD, 3.1.5 CLEAR, 3.2.1 CREATE, 3.2.2 DROP Please note that the GRAPH keyword is already optional in ADD, MOVE, COPY, cf. [45] GraphOrDefault ::= 'DEFAULT' | 'GRAPH'? Iri So, I think this minor change would make the Update language more coherent, or would there be any problems with it? Best regards, Axel -- Dr. Axel Polleres Siemens AG Österreich Corporate Technology Central Eastern Europe Research & Technologies CT T CEE Tel.: +43 (0) 51707-36983 Mobile: +43 (0) 664 88550859 Fax: +43 (0) 51707-56682 mailto:axel.polleres@siemens.com
Received on Thursday, 5 July 2012 09:51:56 UTC