W3C home > Mailing lists > Public > www-rdf-interest@w3.org > February 2002

Re: Provenance in RDF

From: Geoff Chappell <geoff@sover.net>
Date: Wed, 27 Feb 2002 14:27:46 -0500
Message-ID: <00bc01c1bfc4$d6407bd0$0400a8c0@GSC866>
To: "Dave Reynolds" <der@hplb.hpl.hp.com>, "RDF Interest \(E-mail\)" <www-rdf-interest@w3.org>

----- Original Message -----
From: "Dave Reynolds" <der@hplb.hpl.hp.com>
To: "RDF Interest (E-mail)" <www-rdf-interest@w3.org>
Sent: Wednesday, February 27, 2002 7:14 AM
Subject: Provenance in RDF


> We are working on a semantic web related application that needs some
provenance
> support. We have various routes for doing this but would be interested in
> hearing of other's experiences. Are there any groups out there that have
> developed applications supporting provenance within RDF that would be
willing to
> share their experiences on what worked well or badly?
>
[...]
>
> Dave

We put up a site to test this and other issues a while back
(http://www.intellidimension.com/itdsw/default.asp). The source and time is
stored for each statement and statement visibility to queries is controlled
by rules (i.e. if the statement comes from a source you trust, you see it --
{?p ?s ?o} <- {[x:sourceOf] ?source {?p ?s ?o}} and {[x:trusts]
[x:CurrentUser] ?source}.

We started with conventional triple-based reification (1 statement = 4
triples + provenance triples) but moved to a quad representation internally
for performance reasons (1 statement = 1 quad + provenance triples).
Performance was workable with triple reification but much improved with
quads.

Geoff
Received on Wednesday, 27 February 2002 14:27:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:34 UTC