W3C home > Mailing lists > Public > semantic-web@w3.org > February 2010

CURIEs in Turtle

From: Eric Prud'hommeaux <eric@w3.org>
Date: Wed, 3 Feb 2010 12:32:33 -0500
To: Toby Inkster <tai@g5n.co.uk>
Cc: Dave Beckett <dave@dajobe.org>, pfps@research.bell-labs.com, semantic-web@w3.org, sandro@w3.org, Steven.Pemberton@cwi.nl
Message-ID: <20100203173233.GE32619@w3.org>
* Toby Inkster <tai@g5n.co.uk> [2010-02-03 15:44-0000]
> > It also might be worth starting to consider whether to align the terminals
> > (qnames) more with sparql first.
> Or perhaps align both with CURIEs <http://www.w3.org/TR/curie/> ?

I suspect that syntactic differences between the surrounding languages
will make that difficult, but let's give it a look...

CURIEs allow lots of punctuation into qnames, punctuation that serves
as individual tokens in Turtle, and even more in SPARQL. I did model
curies in SPARQL to see how stuff would parse. Examining the part of
SPARQL which is also Turtle, we can sniff around Turtle+CURIEs:

For instance, ASK{?s?o:n1.?s2?p2:n2} includes two triples, but the
trailing dot in CURIEs allows it to produce one (the PNAME_LN terminal
matches "n1.?s2?p2:n2").
compare to

We see similar behavoir for e.g. ',' etc: try ASK{?s?o:n1,:n2 .}

Of course, we can add WS to make it parse correclty:
  ASK{?s?o:n1 ,:n2 .}

Does the world want to add WS to get improved compact expressivity?
Let's hear from the world, here's the microphone.

Conveniently (as we probably want any liberalizations in Turtle to be
available to SPARQL, '{}'s and '<>'s aren't in curie local names. Note
produces two TriplesBlocks and
produces a triple.

> -Toby

Received on Wednesday, 3 February 2010 17:33:11 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:16 UTC