W3C home > Mailing lists > Public > public-rdf-comments@w3.org > May 2013

Re: N-Quads TR

From: Eric Prud'hommeaux <eric@w3.org>
Date: Sun, 26 May 2013 10:14:47 -0400
To: Henry Story <henry.story@bblfish.net>
Cc: Andreas Harth <harth@kit.edu>, public-rdf-comments@w3.org, Aidan Hogan <aidan.hogan@deri.org>, richard@cyganiak.de
Message-ID: <20130526141446.GC12155@w3.org>
* Henry Story <henry.story@bblfish.net> [2013-05-26 15:06+0200]
> 
> On 26 May 2013, at 13:14, Andreas Harth <harth@kit.edu> wrote:
> 
> > Hi,
> > 
> > I've just stumpled across the Note about N-Quads.
> > 
> > You might want to reference our earlier document specifying
> > N-Quads [1].  Actually, you should.
> 
> I wonder if this cannot be reduced down to triples again by going
> through a content relation, relating a URI to the representation received 
> from it:
> 
> <http://server.example/doc> :content [ turtle "<http://server.example/doc#me> a <http://xmlns.com/foaf/0.1/Person> ." ] .
> 
> or in short 
> 
> <http://server.example/doc> :content "<http://server.example/doc#me> a <http://xmlns.com/foaf/0.1/Person> ."^^lang:turtle .
> 
> No need for quads. You get the quad by indirection through a literal.

In theory, this seems like a clever way to write and refer to
non-asserted triples, but in practice, we're always going to want to
associate them with some label (i.e. we'll only know what to do with
it when we see the :content predicate) and this triples-as-literal
approach requires a recursive parser. I prefer to have the surface
syntax express the expected behavior and to have the parser do all the
work in one pass.


> Now the question is can the :content relation be made to be equivalent to cwm's log:semantics ? Ie. can we have
> the datatype lang:turtle be a map from a string to a graph where the string is interpreted as turtle?
> 
> 
> Henry
> 
> 
> > 
> > Regards,
> > Andreas.
> > 
> > [1] http://sw.deri.org/2008/07/n-quads/
> > 
> 
> Social Web Architect
> http://bblfish.net/
> 
> 

-- 
-ericP
Received on Sunday, 26 May 2013 14:15:18 UTC

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