W3C home > Mailing lists > Public > public-rdf-wg@w3.org > June 2011

Re: Two thoughts on Turtle

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Sat, 11 Jun 2011 18:36:15 +0100
Message-ID: <4DF3A78F.1040909@epimorphics.com>
To: Steve Harris <steve.harris@garlik.com>
CC: Richard Cyganiak <richard@cyganiak.de>, Sandro Hawke <sandro@w3.org>, public-rdf-wg <public-rdf-wg@w3.org>
>>> Would it be useful to allow bare dates/dateTimes?

Because this has been mentioned (elswhere, before) I wanted to get all 
the synatx possibilities on the list.

>>> :x dc:date 2010-06-08 .
>> I would like to see that. It would complete the set of syntactic sugar for the commonly used XSD types, and I'd hope that it'd eventually also make its way into SPARQL implementations. Although there might be problems here; this is valid SPARQL:
>>     SELECT (2011-06-09 as ?today) WHERE { }
>> but it doesn't do what you think :-)


Well, it does for me, but maybe not what everyone might see:

It would be an xsd:date - greedy tokenizing means it is not a numeric 
expression:  2011 - 06 - 09

Seriously, some reduced, indicator syntax would be better:


which is less nice but better than the clunky ^^xsd:dateTime.

But we're not starting from a  clean sheet so it probably fails the 
"sufficent value for change from submission" test.

> xsd:date is not an required SPARQL type, but xsd:datetime is, and 2011-06-09T00:00:00Z is not an integer :)
> That said, I'm not a parser expert, and I'm scared of things that seem like they ought to be fine, but cause crazy shift-reduce conflicts with sensible future syntax.
> SPARQL already caused itself a lot of pain by making WHERE optional, and not allowing "," between clauses e.g. in SELECT and ORDER BY, it makes the project expression syntax grotty, for one.
> - Steve

OK - It does not seem there is sufficient value and Turtle-SPARQL 
alignment is much more important.

Received on Saturday, 11 June 2011 17:36:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:59 UTC