- From: Sandro Hawke <sandro@w3.org>
- Date: Sun, 06 May 2012 15:31:47 -0400
- To: Lee Feigenbaum <lee@thefigtrees.net>
- Cc: Gavin Carothers <gavin@carothers.name>, Manu Sporny <msporny@digitalbazaar.com>, public-rdf-wg@w3.org
On Sun, 2012-05-06 at 13:49 -0400, Lee Feigenbaum wrote:
> On 5/6/2012 9:01 AM, Sandro Hawke wrote:
> > On Sat, 2012-05-05 at 21:08 -0700, Gavin Carothers wrote:
> >> The nearness of a Turtle LC and the ongoing
> >> confusion/conversation/whatever on named graphs is reducing my own
> >> support for trying to support "named graphs" in Turtle.
> >
> > I understand.
> >
> > I wonder if there's any way to thread this needle -- not holding back
> > Turtle, but not closing the door to this thing that I suspect is going
> > to seem like a no-brainer, looking back in a couple of years.
>
> Why isn't doing Turtle and also doing TriG accomplishing this? In a
> couple of years, if named graphs are ubiquitous, then folks will just
> use TriG. Is it a concern over media types? Something else?
Two different issues here:
- The braces around the default graph in TriG make it fail in this role.
The syntax is always disjoint from Turtle, instead of being an
extension/subset thing.
- I'm also suggesting we allow (and prefer) "prefix" to "@prefix", and
require a "graph" keyword, to be closer to SPARQL.
I'm pretty sure these things will bug people for a good long time if we
don't change them now. Only PREFIX/@prefix needs to be handled before
Turtle goes to LC.
Manu also makes the point that we have way too many syntaxes, but I
think that can be handled separately.
We could rename Turtle/TriG as the SPARQL Data Language or something,
and (someday) make it usable inside SPARQL. :-)
-- Sandro
> Lee
>
Received on Sunday, 6 May 2012 19:31:59 UTC