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

Re: PROV-ISSUE-114 (Tlebo): is prov:wasDerivedFrom rdfs:subPropertyOf prov:dependedOn? [Formal Model]

From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Date: Wed, 5 Oct 2011 13:25:02 +0100
Message-ID: <CAPRnXt=jm4UZm4eA8Z7fPbJe_4gUBRYbXwVcOwqpiGPhF9W3JA@mail.gmail.com>
To: Provenance Working Group WG <public-prov-wg@w3.org>
On Wed, Oct 5, 2011 at 00:15, Provenance Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
> PROV-ISSUE-114 (Tlebo): is prov:wasDerivedFrom rdfs:subPropertyOf prov:dependedOn? [Formal Model]

> if:
> :e_2 prov:wasDerivedFrom :e_1,
> "e_2 is transformed from, created from, or affected by e_1."
> Would this also imply:
> "e_1 cannot be generated without the existence of e_1."
> :e_2 prov:dependedOn :e_1 .


1) If wasDerivedFrom(e2,e1) or wasDerivedFrom(e2,e1,pe,r2,r1) holds,
then dependedOn(e2,e1) holds.
2) If wasEventuallyDerivedFrom(e2,e1) holds, then dependedOn(e2,e1) holds.
3) If dependedOn(e3,e2) and dependedOn(e2,e1) hold, then
dependedOn(e3,e1) holds.

However - dependedOn is transitive - but wasDerivedFrom is not. Can
you be a subproperty and loose the transitivity?

prov:wasEventuallyDerivedFrom is transitive, however. So 3) is
captured by making prov:dependedOn transitive, 2) by making
prov:wasEventuallyDerivedFrom subproperty of prov:dependedOn. How to
do 1) in OWL is slightly trickier.

Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
Received on Wednesday, 5 October 2011 12:25:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:02 UTC