- From: Timothy Lebo <lebot@rpi.edu>
- Date: Fri, 2 Dec 2011 18:00:23 -0500
- To: Stephan Zednik <zednis@rpi.edu>
- Cc: Yolanda Gil <gil@isi.edu>, public-prov-wg@w3.org, Paolo Missier <paolo.missier@newcastle.ac.uk>, Paul Groth <p.t.groth@vu.nl>, Luc Moreau <l.moreau@ecs.soton.ac.uk>, "Reza B'Far" <reza.bfar@oracle.com>, Ryan Golden <ryan.golden@oracle.com>
- Message-Id: <4C9296E0-1365-4531-99ED-902D670BBD1B@rpi.edu>
On Nov 21, 2011, at 1:19 PM, Stephan Zednik wrote: > > On Nov 10, 2011, at 10:32 AM, Yolanda Gil wrote: > >> 1) An "agent" is a type of entity that takes an active role in an activity +1 >> such that it can be assigned some degree of responsibility for the activity taking place. +0 To some extent, I think that any Entity involved (used, participated, controlled) in an Activity could be responsible for what happened. If it weren't responsible, then why would one say it was involved? But I'm fine with running with "responsibility" in the definition. >> >> 2) Many agents can be "associatedWith" a given activity. > > While there is nothing wrong with this statement, 'associatedWith' does not imply an entity with agency nor a relation to an activity. It is too broad. > > associated |əˈsōsēˌātid, -SHē-| > adjective > (of a person or thing) connected with something else: two associated events. > I think associatedWith is a poor replacement for wasControlledBy and hadParticipant. It is too broad and the semantics are not useful. +1 > I suspect that every relation defined in prov-dm could be viewed as a valid specialization of 'associatedWith'. > > wasDerivedFrom, wasQuoteOf, wasGeneratedFrom, etc. are all valid examples of one thing associatedWith another thing. > > The current wasControlledBy and hadParticipant relations have useful semantics. They imply agency by the involved entity (therefore an agent), and the existence of a relation between the agent and some activity, and are clearly distinct from used and wasGeneratedFrom. +1 > >> >> 3) Subclasses of agent are "foaf:person", "foaf:organization", and "software agent". >> >> 4) Agents can run activities on behalf of other agents, indicated by "runOnBehalfOf". > > As long as Agents are a specialization of Entity and not explicitly defined in the context of an association/involvement/participation with an activity, it does not make sense to say that one Agent runOnBehalfOf Agent - we lose connection to the action being performed. +10 > If an Agent was used to describe me, and in an activity I act on behalf of RPI, my agent will now always be acting on behalf of RPI. If my agent description is re-used in the context of other activities, we may be implying the involvement of a party that is not involved. > > I think runOnBehalfOf must be defined within the context of a specific involvement between an agent and an activity - and we can already do that through qualifiers. +1 > > --Stephan
Received on Friday, 2 December 2011 23:01:48 UTC