- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Thu, 9 Aug 2012 10:20:42 +0100
- To: James Cheney <jcheney@inf.ed.ac.uk>
- Cc: Provenance Working Group <public-prov-wg@w3.org>
Yes, both constraint 48 and 49 looks good. I've closed this issue. On Wed, Aug 8, 2012 at 5:02 PM, James Cheney <jcheney@inf.ed.ac.uk> wrote: > I believe Tom has now replaced this constraint (along with adding some missing constraints Stian had pointed out we might want, to deal with the case of agents that are activities). > > Stian, can you please check that you're happy with the results? Marked pending review. > > --James > > On Aug 6, 2012, at 4:56 PM, James Cheney wrote: > >> This seems easy to fix, by replacing the constraint 48 with the proposed: >> >>> IF wasAttributedTo(_at;e,ag,_attrs) and >>> wasGeneratedBy(genE;e,_a1,_t1,_attrs1) and >>> wasGeneratedBy(genAg;ag,_a1,_t1,_attrs1) THEN genAg precedes genE >> >> and supporting text as suggested. Any objections? >> >> --James >> >> On Aug 6, 2012, at 4:37 PM, Provenance Working Group Issue Tracker wrote: >> >>> PROV-ISSUE-471 (wrong-wasAttributedTo-constraints): wasAttributedTo constraints not sensical [prov-dm-constraints] >>> >>> http://www.w3.org/2011/prov/track/issues/471 >>> >>> Raised by: Stian Soiland-Reyes >>> On product: prov-dm-constraints >>> >>> I find the wasAttributedTo constraint 48 wrong >>> >>>> From Stian's review http://lists.w3.org/Archives/Public/public-prov-wg/2012Aug/0021.html >>> >>> http://dvcs.w3.org/hg/prov/raw-file/default/model/releases/ED-prov-constraints-20120723/prov-constraints.html#wasAttributedTo-ordering_text >>> >>>> An entity that was attributed to an agent must have some overlap with the agent. >>> >>> Why?? >>> >>> >>>> The agent is required to exist before the entity invalidation. >>> >>> I don't agree with that. First of all, why has the attribution need to >>> have anything to do with the invalidation of an entity? If you >>> contribute to an entity, all of that has to happen *before* the entity >>> is generated. It does not matter what happens after that. >>> >>>> Likewise, the entity generation must precede the agent destruction. >>> >>> This also means it is not valid to attribute a book to an author if >>> the book was published after the author's death. (For instance The >>> GIrl with the Dragon Tattoo). >>> >>> By our inferences, it is only a requirement that the agent was >>> associated with an activity that eventually gave birth to the entity. >>> The agent is not required to be there till the end of the activity, >>> that sounds like an artificial constraint to me. Thus I would remove >>> constraint 48. >>> >>> >>> What you can instead say that an agent's association with that >>> activity must precede an entity's generation, because otherwise he >>> can't be associated with its generating activity. This does not >>> directly follow from constraint 47 and Inference 15 >>> (attribution-inference), so we need a constraint to force the >>> generation to be after the *association* started, the first would then >>> follow. Association don't have time, unfortunately, but we can use >>> same reasoning as in constraint 47: >>> >>> IF wasAttributedTo(_at;e,ag,_attrs) and >>> wasGeneratedBy(genE;e,_a1,_t1,_attrs1) and >>> wasGeneratedBy(genAg;ag,_a1,_t1,_attrs1) THEN genAg precedes genE >>> >>> >>> We can't say anything about the entity's invalidation; attribution >>> relates to association with the generation, not invalidation. The >>> agent's invalidation after the start of the activity a1 (which does >>> not affect e) is covered by constraint 47+ inference 15. >>> >>> >>> >>> >>> >> >> >> -- >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >> >> > > > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester
Received on Thursday, 9 August 2012 09:21:44 UTC