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

Re: Some comments re: the current Turtle working draft

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Fri, 08 Jul 2011 19:05:44 +0100
Message-ID: <4E1746F8.9020901@epimorphics.com>
To: public-rdf-wg@w3.org


On 08/07/11 17:29, Mischa Tuffield wrote:

> 2. I am not sure whether or not we should expand all acronyms used in
> the document before using them, an example would be the use of "LALR" or
> "EBNF", again, this is but a suggestion. I am sure most people
> implementing parsers will know what it stands for, but for completeness
> sakes would be nice for it to be expanded upon before use.

In that section, 5.4, there is nothing that is compiler-technology 
specific.  The section "5. Parsing" is a bit misleading as "parsing" is 
going on at different levels.  This is abstract syntax (output of what 
might more conventionally be a "parser") to triples generated.

Maybe "Generating triples" or "Generating RDF from Turtle"

(the Turtle grammar doesn't require  LALR(1) -- at least I hope not and 
it is possible to write a Turtle grammar using LL(1) which is much 
simpler and what someone hand-writing a parser might use).

For now:
"with an LALR(1) parser" ==> "when parsed"


In the same section;

<_:1>

:-)

> 4. In Section 4.4 - Grammar: the "BooleanLiteral" is presented to be
> either "true" or "false" but in the Section C -Changes (Informative): it
> states that the BooleanLiteral should be implemented to be
> "case-insensitive", what is correct, does SPARQL go with case
> insensitive or otherwise ?

SPARQL is case-insensitive for everything except "a".

	Andy
Received on Friday, 8 July 2011 18:06:16 GMT

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