Re: Some comments re: the current Turtle working draft

Thanks for clarifying Andy. 

Mischa
On 8 Jul 2011, at 19:05, Andy Seaborne wrote:

> 
> 
> 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
> 

___________________________________
Mischa Tuffield PhD
Email: mischa.tuffield@garlik.com
Homepage - http://mmt.me.uk/
+44(0)208 439 8200  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