W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2012

Re: whitespace in Turtle

From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
Date: Tue, 15 May 2012 11:33:24 -0400
Message-ID: <4FB27744.7020902@gmail.com>
To: Gavin Carothers <gavin@carothers.name>, public-rdf-wg <public-rdf-wg@w3.org>

On 05/15/2012 11:01 AM, Gavin Carothers wrote:
> On Tue, May 15, 2012 at 7:46 AM, Peter F. Patel-Schneider
> <pfpschneider@gmail.com>  wrote:
>> The Turtle editor's draft says that WS is needed to prevent mis-recognition
>> of tokens, but doesn't explicitly define a token.
> token, terminal, whatever ;)
>> If the parsing Turtle depends on tokenizing, then there needs to be an
>> explicit definition of what a token is, and, further, what mis-recognizing a
>> token means.
> Preposed new language:
> White space (production WS) is used to separate two terminals which
> would otherwise be (mis-)recognized as one terminal. Rule names below
> in capitals indicate where white space is significant; these form a
> possible choice of terminals for constructing a Turtle parser.
> White space is significant in terminal IRIREF and the production String.
> ---
Umm, terminals are usually terminal in a grammar, not simply things that one 
might like to think of as tokens.

> Also, split that grammar table and identify all terminals with more
> than just all caps.
>> For example, is
>> @prefixprefix:<foo>.
>> a valid Turtle statement?
> Yes.
I expect that this was is not intended to be valid.
>> Things would get even worse if the @ was allowed to be dropped, which is a
>> good reason to vote against allowing dropping of @.
> Yes, while it is possible to create a grammar that allows this in
> general removing @ is likely to reduce human readability.
>> peter

Received on Tuesday, 15 May 2012 15:34:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:05 UTC