- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Tue, 8 May 2012 14:39:32 +0100
- To: Timothy Lebo <lebot@rpi.edu>
- Cc: Khalid Belhajjame <Khalid.Belhajjame@cs.man.ac.uk>, Jun Zhao <jun.zhao@zoo.ox.ac.uk>, W3C provenance WG <public-prov-wg@w3.org>
On Mon, May 7, 2012 at 3:48 PM, Timothy Lebo <lebot@rpi.edu> wrote: > +1, repositioning wasStartedByActivity as a "blurrier" form of wasStartedBy seems to finally find a place for it in the model. > Though, like Khalid, I'm not sure it will be used much, or correctly. It will certainly still be confusing, as it was for me. As you said, most wasStartedBy() would also come with a twin used() relationship (and therefore imply a wasInformedBy() relation). At some point wasStartedBy was sub-property of wasInformedBy (making the choice simple) - but not anymore. As Luc raised, why not also wasEndedByActivity, wasStartedByAgent etc.? So it might just not be worth it to keep wasStartedByActivity(). It's a bad sign if it's confusing to even the ontology designers, then how is any meaningful provenance exchange happen, where one party apply wasInformedBy like wasStartedByActivity, and the other the opposite? A second solution would be to remove the constraint that activity and entity are disjoint. Then you could say wasStartedBy(a2, a1), wasEndedBy(a2, a3) etc. - the activity can play the role of an entity as well, rather than inventing invisible phantom token entities. We are talking blurry provenance here, right, we don't know quite the nature of the interaction. > How can it be reframed so that wasStartedByActivity can "grow" in details like Derivation does with hadActivity, hadUsage, and hadGeneration? By adding a separate wasStartedBy() I would believe you have given all the information (as an activity can only be started once). Or is it allowed to be wasStartedBy() two or more entities..? Luc? -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester
Received on Tuesday, 8 May 2012 13:40:21 UTC