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

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

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Wed, 30 Mar 2011 22:06:10 +0100
Message-ID: <4D939B42.1020507@epimorphics.com>
To: Peter Frederick Patel-Schneider <pfps@research.bell-labs.com>
CC: sandro@w3.org, nathan@webr3.org, public-rdf-wg@w3.org


On 30/03/11 21:59, Peter Frederick Patel-Schneider wrote:
> From: Andy Seaborne<andy.seaborne@epimorphics.com>
> Subject: Re: ISSUE-18: How do we parse "18." in Turtle?
> Date: Wed, 30 Mar 2011 15:50:51 -0500
>
>>
>>
>> On 30/03/11 21:33, Peter Frederick Patel-Schneider wrote:
>>> From: Andy Seaborne<andy.seaborne@epimorphics.com>
>>> Subject: Re: ISSUE-18: How do we parse "18." in Turtle?
>>> Date: Wed, 30 Mar 2011 14:51:57 -0500
>>> [...]
>>>
>>>> By the way, this is not the only place that "longest token" is important:
>>>>
>>>> { :x :p18. }
>>>>
>>>> is that ":p1 8."  or ":p 18" or ":p18" and an error?  That has not been
>>>> a practical issue raised.
>>>
>>> Where is this legal in Turtle at all?
>>
>> With a normal tokenizer? Not.
>> With a backtracking one, :x :p18.
>>
>> 	Andy
>
> But what about the { } ?
>
> peter

The context was SPARQL in Sandro's message. {} is legal in SPARQL :-)

"""
How many folks write
SPARQL decimal numbers without trailing digits, relying on this
behavior, before the "}"?
"""

But it would apply to TriG as well.

	Andy
Received on Wednesday, 30 March 2011 21:06:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:04 UTC