- From: Gavin Carothers <gavin@topquadrant.com>
- Date: Sun, 14 Aug 2011 21:36:38 -0700
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: RDF Working Group WG <public-rdf-wg@w3.org>
On Sat, Aug 13, 2011 at 12:08 PM, Richard Cyganiak <richard@cyganiak.de> wrote: > Gavin, > > On 12 Aug 2011, at 19:14, RDF Working Group Issue Tracker wrote: >> New Turtle: >> >> Allowed: >> @prefix bob: http://example.org/bob/ . >> bob:goldfish\u002F1 > > Is that allowed? Section 4.3 [1] says that all the backslash escapes are only allowed inside strings and IRI_REF. I don't see anything that allows them inside prefixed names. Then section 4.3 doesn't agree with the grammar: http://www.w3.org/TR/turtle/#term-turtle2-PN_CHARS_BASE One of them gets to give. > >> I'm not sure what the rational for continuing to disallow /'s in the local part of prefixed name is. RDFa via the CURIE spec via the IRI fragement production allows them. > > Turtle follows SPARQL. SPARQL has property paths: foaf:knows/foaf:name. So the slash character is taken. Except in the case of escaping. Which was one of the divergence points. IRIs,URIs,UR**s are a good bit older then property paths, so the slash character was taken already. ;) It's okay(ish) that SPARQL has decided to use / for property paths but will require some clear text on the subject in Turtle, as I the happy editor of Turtle went ahead and wrote a fair bit of turtle by hand without noticing that /'s were going to cause problems. Specific example: @prefix turtleDocLoc: <http://www.w3.org/TR/2011/WD-turtle-20110809/> turtleDocLoc:examples/example1.ttl It's very surprising not to be able to write that. You can get around it by using @base a lot more, or by defining a LOT of prefixes. :\ Neither solution is very readable. > > Best, > Richard > > [1] http://www.w3.org/TR/turtle/#sec-strings >
Received on Monday, 15 August 2011 04:37:06 UTC