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

Re: ISSUE-110: Renaming prov:Role -> prov:EntityInRole

From: Timothy Lebo <lebot@rpi.edu>
Date: Tue, 4 Oct 2011 09:12:58 -0400
Cc: Provenance Working Group WG <public-prov-wg@w3.org>
Message-Id: <1D05D344-82CD-474C-8495-803F9DE185AE@rpi.edu>
To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Stian and Khalid,

I think qualifying prov:Role to prov:EntityInRole makes sense.

I've written the OWL component:

http://dvcs.w3.org/hg/prov/file/tip/ontology/components/EntityInRole.ttl

and reused the Toyota purchase example from previous threads to illustrate how it can be used:

http://dvcs.w3.org/hg/prov/file/tip/ontology/components/EntityInRole/car-purchase.ttl



The example uses two new example extension ontologies:

http://dvcs.w3.org/hg/prov/file/tip/ontology/examples/ontology-extensions/vehicle/vehicle.ttl

to extend prov:Entity to describe a vehicle with make, model, vin, and owner.

and

http://dvcs.w3.org/hg/prov/file/tip/ontology/examples/ontology-extensions/commerce/commerce.ttl

to extend prov:ProcessExecution to describe a Purchase between a Buyer and Seller, using some form of Payment and ReceivedGoods.



Note that the extension ontologies allow me to simply rdf:type the prov:Entity prov:used by the prov:ProcessExecution:

    42    prov:used [
    43       a commerce:Buyer;
    44       prov:assumedBy <http://data.semanticweb.org/person/luc-moreau>;
    45       a prov:EntityInRole, prov:Entity; # Since :Buyer subClassOf EntityInRole.
    46    ];

the prov:assumedRole is "filledIn" by inference, while non-inferencing applications can just use the rdf:type directly (e.g. Buyer).

Please let me know if you have any concerns with this modeling.

Regards,
Tim


On Oct 4, 2011, at 5:22 AM, Stian Soiland-Reyes wrote:

> On Mon, Oct 3, 2011 at 18:11, Provenance Working Group Issue Tracker
> <sysbot+tracker@w3.org> wrote:
>> 
>> ISSUE-110: Renaming prov:Role -> prov:EntityInRole
>> 
>> http://www.w3.org/2011/prov/track/issues/110
> 
> We might or might not later introduce prov:Role as an owl:Thing
> subclass, depending on if roles are done as subclasses of
> prov:EntityInRole (forces the roles to be a class) or by a property
> prov:assumedRole (role can be any object).
> 
> Definition and structure of the roles themselves is outside the scope
> of PROV, just like Recipe and Location.
> 
> 
> -- 
> Stian Soiland-Reyes, myGrid team
> School of Computer Science
> The University of Manchester
> 
> 
Received on Tuesday, 4 October 2011 13:13:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 13:06:43 GMT