- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Wed, 29 May 2013 22:28:34 -0400
- To: Sandro Hawke <sandro@w3.org>
- Cc: Gavin Carothers <gavin@carothers.name>, RDF-WG WG <public-rdf-wg@w3.org>
* Sandro Hawke <sandro@w3.org> [2013-05-29 20:26-0400] > On 05/29/2013 12:29 PM, Gavin Carothers wrote: > >Turtle Proposals > > > > Thanks for bringing these up. > > >1. Keywords should all have the same case rules. @prefix, @base > >and a should allow for upper-casing > > +1 > > >2. Directives should all have optional trailing periods. > > +0.75. I think this is right long term, but this un-aligns things > from SPARQL until/unless SPARQL does the same. If we do this, I'd > advocate outreach to SPARQL folks suggesting they do the same > > >3. Turtle should include examples of both forms of PREFIX @prefix > >directives. > > +1 > > I'd really like an explanation that the @-form is older and the > non-@-non-dot-form is what SPARQL uses. > > >4. Turtle serializes SHOULD output directives using the '@' > >notation with trailing periods. > > > > -0.25 Do we have any other SHOULDs about serializers? I > figure that'll sort out in the pretty-printer market. > > (plus, of course, I prefer the opposite advice.) > > >If there are no loud objections to these changes, will update the > >document accordingly. > > > >Example grammar change from gkellog: > > > >[4] prefixID ::= '@'? [Pp][Rr][Ee][Ff][Ii][Xx] PNAME_NS IRIREF "."? > >[5] base ::= '@'? [Bb][Aa][Ss][Ee] IRIREF "."? > > > > There's a lot to be said for that, yes. Is the intention that these all be valid:? prefix : <> PREfix : <> prefix : <> . PREfix : <> . @ prefix : <> @ PREfix : <> @ prefix : <> . @ PREFIX : <> . Grammar nit: I like that SPARQL separates tokenizing from parsing (as does Turtle). We could follow suite with: prefixID ::= '@'? PREFIX PNAME_NS IRIREF "."? base ::= '@'? BASE IRIREF "."? Terminals: PREFIF ::= [Pp][Rr][Ee][Ff][Ii][Xx] BASE ::= [Bb][Aa][Ss][Ee] or we use our current approach: Keywords in single quotes ('@base', '@prefix', 'a', 'true', 'false') are case-sensitive. Keywords in double quotes ("BASE", "PREFIX") are case-insensitive. by striking the '@base', '@prefix'. > -s > >Cheers, > >Gavin > > -- -ericP
Received on Thursday, 30 May 2013 02:29:08 UTC