W3C home > Mailing lists > Public > public-rdf-comments@w3.org > August 2012

Re: [TURTLE] Turtle Inverse Properties

From: David Booth <david@dbooth.org>
Date: Fri, 17 Aug 2012 15:58:02 -0400
To: Gavin Carothers <gavin@carothers.name>
Cc: RDF-WG WG <public-rdf-wg@w3.org>, public-rdf-comments@w3.org, Tim Berners-Lee <timbl@w3.org>
Message-ID: <1345233482.28927.4456.camel@dbooth-laptop>
On Fri, 2012-08-17 at 11:30 -0700, Gavin Carothers wrote:
[ . . . ]
> Objections to both original syntax and revised syntax
> =====================================================
> Turtle is a reasonably settled languages, changes made by the working
> group so far have been limited to areas of existing differences in
> implementation.
> No demand over years of implementation experience

I think that may be slightly misleading, because Turtle was not
previously standardized, and hence was on the same footing as N3, and
those who wanted to use this feature simply considered their RDF to be
N3 instead of Turtle.  I.e., there was no *need* to demand it in Turtle
because Turtle was not previously chosen over N3 for standardization.

[ . . . ]
> 2. Add ^ property path syntax to Turtle.

+1.  I like it a lot.  Conciseness improves clarity, which reduces

>     1.1. Allowing "literals" in any subject position by syntax,
> however the RDF model disallows literal as subject. (As SPARQL in
> query blocks, however SPARQL disallows path syntax in triple assertion
> syntax)

+1.  SPARQL could be fixed in the next version to allow path syntax in
triple assertion syntax if the SPARQL WG is too tired to change that in

>     1.2. Attempting to limit use of "literals" in subject position to
> only ^ predicates in grammar (Not as SPARQL and SPARQL disallows path
> syntax in triple assertion syntax.)

-0.5.  No need to complicate the grammar.

> 3. Add both ^ property path syntax and "is ... of" syntax.

-1.  To my mind, that would just add pointless complexity.  Standardize
one or the other but not both.

David Booth, Ph.D.

Opinions expressed herein are those of the author and do not necessarily
reflect those of his employer.
Received on Friday, 17 August 2012 19:58:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:53 UTC