W3C home > Mailing lists > Public > public-prov-wg@w3.org > February 2012

Re: Tim's approach on Involvement

From: Khalid Belhajjame <Khalid.Belhajjame@cs.man.ac.uk>
Date: Tue, 21 Feb 2012 10:51:06 +0000
Message-ID: <4F43771A.7030000@cs.man.ac.uk>
To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
CC: Timothy Lebo <lebot@rpi.edu>, "public-prov-wg@w3.org Group" <public-prov-wg@w3.org>
On 21/02/2012 10:31, Stian Soiland-Reyes wrote:
> On Tue, Feb 21, 2012 at 04:58, Timothy Lebo<lebot@rpi.edu>  wrote:
>> I'm adopting your naming of the new properties (activity, entity, qualified)
>> Based on your lead, I deleted the subprops of qualified, which trims the ontology up nicely, but I'm wondering how one figures out the pattern.
> This looks pretty good. Thanks for also updating ProvRDF. I'll go
> through it with  my changes from below.
> I changed some of the equivalent classes to subclasses to avoid
> unwanted side-effects.
> For instance we don't want to have Involvement to be equivalent with
> hadSpatialExtent min 0 Location - because then it is equivalent to
> owl:Thing (!)
> Inform is also an ActivityInvolvement.

> I put equivalence on ActivityInvolvement and EntityInvolvement to have
> "activity some Activity" and "entity some Entity". Start is not
> defined as either ActivityInvolvement or EntityInvolvement as it can
> play double-role and might not always be both. (However it should be
> either, so this is incomplete!)
> Association is not equivalent to an involvement having entity to an
> agent - it could just accidentally be an agent.
Do you mean that we may have an instance of EntityInvolvement  that does 
not denote an agent association and in which the entity involved happens 
to be an agent? For example, an activity that used as input an agent?

> However I introduced AgentInvolvement that requires the subclass (not
> equivalent!!) "entity only Agent" - we could lax this to require
> "entity only Agent" - but none of the subclasses would allow a
> non-agent entity by my view.  This contains Association, Attribution,
> End, Responsibility.
> I notice Derivation is no longer a subclass of Trace - but
> wasDerivedFrom is subproperty of tracedTo. Any reason for not keeping
> the same hierarchy for the involvement here?
> I moved hadQuoterAgent and hadQuotedAgent to be subproperties of
> entity - this is a special case of Quotation as we basically need
> 'roles' for the 'entity' - this should be looked at later.
> I moved so hadOriginalSource is not a subproperty of wasAssociatedWith
> (the source is not necessarily an agent)

Yes. Agreed.

Received on Tuesday, 21 February 2012 10:51:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:58:12 UTC