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

Re: ISSUE-18: How do we parse "18." in Turtle?

From: Steve Harris <steve.harris@garlik.com>
Date: Fri, 1 Apr 2011 02:20:46 +0100
Cc: Pat Hayes <phayes@ihmc.us>, public-rdf-wg@w3.org
Message-Id: <185FAF44-960F-4B73-A8F9-46DF8807A1CA@garlik.com>
To: Sandro Hawke <sandro@w3.org>
On 2011-03-31, at 22:27, Sandro Hawke wrote:

> On Wed, 2011-03-30 at 15:11 -0500, Pat Hayes wrote:
>> 
>> +1  I feel Sandro's pain, but the advantages of fast greedy lexers has
>> to outweigh visual aesthetics. And in any case, I kind of like the
>> spaces, they help my mental lexer when reading. 
> 
> To be clear, I'm fine with greedy lexers, I just want to require at
> least one digit after the decimal point for it to be considered a
> decimal point, instead of a statement-ending period.   I believe it's a
> trivial change to the grammar and no other change to code.

XSD says that leading and trailing zeros can be omitted, I suspect that's the source of it. I'm not a fan of 18. either though. The canonical form requires a digit either side of the ".".

http://www.w3.org/TR/xmlschema-2/#decimal-lexical-representation

- Steve

-- 
Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203  http://www.garlik.com/
Registered in England and Wales 535 7233 VAT # 849 0517 11
Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Friday, 1 April 2011 01:21:27 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:41 GMT