- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Sat, 26 May 2012 14:43:31 +0100
- To: public-rdf-dawg@w3.org
On 26/05/12 14:34, Alexandre Passant wrote: > I agree that it makes sense - any disagreement on the following update ? > >> [30] Update ::= Prologue ( Update1 ( ';' Update )? (';')? )? It is allowed already: [29] Update = Prologue ( Update1 ( ';' Update )? )? 'Update' can be empty which is a trailing ';' http://www.sparql.org/update-validator.html Andy > > Alex. > > Begin forwarded message: > >> *Resent-From: *public-rdf-dawg-comments@w3.org >> <mailto:public-rdf-dawg-comments@w3.org> >> *From: *David Booth <david@dbooth.org <mailto:david@dbooth.org>> >> *Subject: **Please allow trailing semicolon (";") after update statement* >> *Date: *25 May 2012 17:56:04 GMT+01:00 >> *To: *public-rdf-dawg-comments <public-rdf-dawg-comments@w3.org >> <mailto:public-rdf-dawg-comments@w3.org>> >> >> The SPARQL Update syntax currently PROHIBITS a trailing semicolon at the >> end of the last update statement: >> >> [30] Update ::= Prologue ( Update1 ( ';' Update )? )? >> >> although it REQUIRES a semicolon after all other update statements in an >> update operation. I realize that the semicolon was intended to be a >> separator rather than a terminator, but in practice this restriction >> just becomes a pointless annoyance to users. Programming language >> designers learned this lesson many years ago. >> >> Please relax this restriction to allow extra semicolons. >> >> Thanks! >> >> >> -- >> David Booth, Ph.D. >> http://dbooth.org/ >> >> Opinions expressed herein are those of the author and do not necessarily >> reflect those of his employer. >> >> >
Received on Saturday, 26 May 2012 13:44:01 UTC