W3C home > Mailing lists > Public > public-rdf-wg@w3.org > October 2011

Re: Scope of blank nodes in TriG?

From: Richard Cyganiak <richard@cyganiak.de>
Date: Mon, 17 Oct 2011 15:19:51 +0100
Cc: RDF Working Group WG <public-rdf-wg@w3.org>
Message-Id: <C3791BB4-2C7D-4DC2-8A47-0545B51A55FD@cyganiak.de>
To: Steve Harris <steve.harris@garlik.com>
On 17 Oct 2011, at 14:56, Steve Harris wrote:
>> The original use case for TriG (this is years before SPARQL existed) was serializing collections of RDF documents in a single document. In that use case there can be no blank nodes shared between documents, so graph scope made sense and had the convenient side effect of simplifying serializer implementation.
> It also simplifies the parse process.
> Suppose I start parsing a TriG document and see:
> <G1> { _:x a <Foo> }
> then 100GB later in the file I find:
> <G1734> { <x> :seeAlso _:x }
> If there was document scope I would have to carry the assigned skolem form* for _:x around in my parser for the entire parse - that's fine if you only have a handful of bNodes, but with billions of them it can be quite resource intensive.

I'm not sure if I understand. Don't you have a problem already if you import a single large N-Triples file?

Received on Monday, 17 October 2011 14:20:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:09 UTC