- From: Dave Beckett <dave@dajobe.org>
- Date: Thu, 04 Feb 2010 06:12:09 -0800
- To: Steven Pemberton <Steven.Pemberton@cwi.nl>
- CC: Eric Prud'hommeaux <eric@w3.org>, Toby Inkster <tai@g5n.co.uk>, pfps@research.bell-labs.com, semantic-web@w3.org, sandro@w3.org, Mark Birbeck <mark.birbeck@gmail.com>
(replying to the latest msg in this thread) Jeremy Carroll wrote: ... > > ?s?o:n1.?s2?p2:n2 as a single CURIE ... > > ?s?o:n1. ?s2?p2:n2 OK, that's line noise. Turtle should be readable and this is why whitespace is a good idea to sometimes mandate or VERY strongly suggest. The turtle spec doesn't say that very well and the sparql spec does let you get away with this. I'm tempted to make mandatory spaces between components now. I don't see the user need to allow such things. If you are worried about the storage or network cost of extra spaces, you should compress. We probably don't need to go all the way to "represent any URI in a compact form" (Steven) as CURIES need to do in a constrained place - xml/html attribute value, since Turtle has a place to write full URIs in all cases, and also has additional syntax constraints in order to allow other abbreviated forms. The nearest we could get would be any URI that doesn't use the Turtle syntax symbols (anywhere) - [];,_. etc. Dave
Received on Thursday, 4 February 2010 14:12:40 UTC