ISSUE-148: wasScheduledAfter definition is difficult to understand

WasScheduledAfter

wasScheduledAfter definition is difficult to understand

State:
CLOSED
Product:
prov-dm
Raised by:
Khalid Belhajjame
Opened on:
2011-11-10
Description:
Hi,

Trying to model wasScheduledAfter in PROV-O, I found it difficult to understand what wasScheduledAfter means.

According to the definition: "Given two activity records identified by pe1 and pe2, the record wasScheduledAfter(pe2,pe1) holds, if and only if there are two entity records identified by e1 and e2, such that wasControlledBy(pe1,e1,qualifier(prov:role="end")) and wasControlledBy(pe2,e2,qualifier(prov:role="start")) and wasDerivedFrom(e2,e1)."

There are three issues:
1- Why does the agent e2 needs to be derived from the agent e1?

2- Can an agent be derived from another? (This second issue is secondary).

3- There is an assumption in the definition that the activity pe1 needs to be explicitly terminated by an agent? I guess there are cases, the activity will terminates without an agent intervention, and will be followed by the execution of other activity. According to the above definition, in those cases, we will not be able to use wasScheduledAfter.

khalid
Related Actions Items:
No related actions
Related emails:
  1. Re: prov-dm: outstanding issues to close (from Khalid.Belhajjame@cs.man.ac.uk on 2012-05-17)
  2. prov-dm: outstanding issues to close (from L.Moreau@ecs.soton.ac.uk on 2012-05-08)
  3. Re: PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand (from L.Moreau@ecs.soton.ac.uk on 2012-04-17)
  4. Re: PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand (from L.Moreau@ecs.soton.ac.uk on 2012-03-23)
  5. Re: PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand (from lebot@rpi.edu on 2011-11-21)
  6. PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand (from sysbot+tracker@w3.org on 2011-11-10)

Related notes:

No additional notes.

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 148.html,v 1.1 2013-06-20 07:37:24 vivien Exp $