- From: Peter Waher <Peter.Waher@clayster.com>
- Date: Sun, 3 Jun 2012 16:50:42 +0000
- To: Andy Seaborne <andy.seaborne@epimorphics.com>, "public-rdf-dawg-comments@w3.org" <public-rdf-dawg-comments@w3.org>
Hello Andy Thanks for the quick response. I'll take your word for it. Looking at the document you linked to, I cannot see that the grammar has been updated to include variable bindings in the DESCRIBE clause [11], as is allowed in [9] for SELECT: http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#sparqlGrammar Sincerely, Peter Waher -----Original Message----- From: Andy Seaborne [mailto:andy.seaborne@epimorphics.com] Sent: den 3 juni 2012 17:32 To: public-rdf-dawg-comments@w3.org Subject: Re: Bindings in the DESCRIBE clause Hi Peter, This has been fixed http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#sparqlGrammar By the way: BINDINGS is set to change to generalise it -- some discussion: http://lists.w3.org/Archives/Public/public-sparql-dev/2012AprJun/0018.html Andy On 03/06/12 13:00, Peter Waher wrote: > Hello > > Any reason why bindings in the DESCRIBE clause using expressions is > not permitted in SPARQL 1.1, when they are permitted in the SELECT clause? > > Compare [11] and [9] in: > > http://www.w3.org/TR/sparql11-query/#sparqlGrammar > > Example: Describe the first iri that is well defined, using the > COALESCE function. > > This could be done using BIND [62], but a SPARQL user would expect > syntax to be consistent. > > Sincerely, > > Peter Waher >
Received on Sunday, 3 June 2012 16:51:32 UTC