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

Re: about EntityInRole and assumedBy

From: Khalid Belhajjame <Khalid.Belhajjame@cs.man.ac.uk>
Date: Wed, 26 Oct 2011 18:42:41 +0100
Message-ID: <4EA84691.2010901@cs.man.ac.uk>
To: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
CC: Provenance Working Group WG <public-prov-wg@w3.org>

Hi Luc, all,

We are aware of the problems that EntityInRole is introducing. Following 
your comments in last emails, we are contemplating a new alternative, 
that was suggested by James, which seems to be inline with the PROV-DM. 
Not all members of the ontology group have expressed their opinion yet, 
though.

The idea is to have two owl classes Usage and Generation. These two 
classes are connected to Entity and Process Execution (using object 
properties), and qualifiers, such as role, can be defined as object 
properties of Usage and Generation. For example, Usage can be defined as:

prov:Usage a owl:Class.

prov:hasEntity
     a rdf:Property ;
     rdfs:domain prov:Usage ;
     rdfs:range prov:Entity .

prov:hasProcessExecution
     a rdf:Property ;
     rdfs:domain prov:Usage ;
     rdfs:range prov:ProcessExecution .

prov:hasRole
     a rdf:Property ;
     rdfs:domain prov:Usage ;
     rdfs:range prov:Role .
...

Additionally, to be closer to the model, we can define shortcuts 
properties: used and wasGeneratedBy as object properties that connect 
process execution and entities. For example,

prov:used
     a rdf:Property ;
     rdfs:domain prov:ProcessExecution ;
     rdfs:range prov:Entity .

There is at least one issue that we are aware of using this design, but 
IMO, it is better.

khalid

On 26/10/2011 16:22, Luc Moreau wrote:
>
> Dear all,
>
> I would like to reiterate again my concern about the mismatch between
> prov-dm and prov-o. I think the two notions the documents diverge on are
> entityInRole (a subclass of Entity) and assumedBy (which in essence is
> a kind of specialization of wasComplementOf).
>
> They are introduced in the ontology to be able to express time and 
> qualifiers
> (including role) for use and generation.
>
> It is suggested by JamesC and Graham that we write examples to 
> understand the
> differences, it is a very good point that I support.
>
> I would like to explain the problem I have with the EntityInRole 
> solution.
>
> Let's take the case of a used relation (ideas apply similarly to 
> generation).
> Let's imagine there is no qualifier/time information.
> We want to be simple, and express a property, as prov-o does:
>
> Encoding1:
>   pe prov:used e1
>
> If we suddently have time information or role, according to prov-o, we 
> would have to write:
>
> Encoding2:
>
>  pe prov:used e1X
>  e1X  prov:assumedBy e1
>  e1X  prov:assumedAt t1
>  e1X  prov:assumedRole r
>
> My problems are the following:
>
> - Encoding2 is not an extension of encoding1: it  does not just add 
> new edges,
>   it removes some.
>   But according to the data model, we just have added extra information.
>
> - why should I change my "modelling of what happens in the world",
>   encoding2 has got two entities when encoding1 has got only one.
>
> - I believe it would be reasonable to write
>     e1X wasComplementOf e1  (since it looks like e1X has attributes 
> that e1 doesn't have,
>     and have a common time interval).
>
>   What's the difference between e1X WasComplementOf e1 and e1X 
> assumedBy e1?
>    wasComplementOf is hard enough, why do we have to have something so 
> similar to it,
>    but restricted to entityInRole?
>
> - Imagine the scenario is more complex and e1 is used by a second 
> process in another
>   role, at time t2>t1 so we may have another entity e2X.
>   It would also be reasonable to write e2X wasDerivedFrom e1X because 
> e2X follows e1X.
>   But this wouldn't be possible in prov-dm, unless we explictly 
> introduce e1X and e2X.
>
>
> Cheers,
> Luc
>
>
Received on Wednesday, 26 October 2011 17:43:04 GMT

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