W3C home > Mailing lists > Public > public-prov-comments@w3.org > December 2011

Contributions and Supersedes

From: James Leigh <james@3roundstones.com>
Date: Wed, 14 Dec 2011 13:33:01 -0500
Message-ID: <1323887581.1807.28.camel@james-laptop>
To: public-prov-comments@w3.org

I am the author of the AliBaba auditing ontology[1] and I would like to
seem more relationships from Activities defined in the POV ontology.

prov:generated rdfs:domain prov:Activity; rdfs:range prov:Entity.

An inverse of prov:wasGeneratedBy would be very useful in cases when the
activity itself has a stronger identity than the entity created. Such a
case would be when the entity produced is not identified by a URI.
Perhaps the entity produced is a triple or a set of triples (g-snap)
without an explicit identifier. Such a relationship would also allow
someone using Linked Data to follow their nose between activities and
the entities their produced.

prov:contributedTo rdfs:domain prov:Activity; rdfs:range prov:Entity.

In some cases it may not be possible (or desirable) to uniquely identify
every entity revision. Instead a single entity may actually have been
generated, in part, by multiple activities over time. In this case it
may be desirable to have a relationships that is weaker than
prov:generated and allows multiple contributions.

prov:supersedes rdfs:domain prov:Activity; rdfs:range prov:Activity.

The prov:wasDerivedFrom is useful to link new versions of an entity to
its predecessor, however, it would be equally useful to link their
activities together as well. A sub property of prov:wasInformedBy that
implies this activity makes an entity, generated from this another
activity, obsolete.


[1] http://www.openrdf.org/doc/alibaba/2.0-beta14/owldocs/auditing-ontology.html
Received on Wednesday, 14 December 2011 18:36:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:08:58 UTC