- From: Provenance Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 08 Feb 2012 10:22:06 +0000
- To: public-prov-wg@w3.org
PROV-ISSUE-247: Regarding Collections in prov-dm [prov-dm] http://www.w3.org/2011/prov/track/issues/247 Raised by: Khalid Belhajjame On product: prov-dm Hi, In section 6.8, two relations are introduced to model insertion and deletion of key-value pairs: "CollectionAfterInsertion(c2,c1, k, v) denotes that collection c2 represents the new state of collection c1, following the insertion of pair (k,v) into c1" "CollectionAfterRemoval(c2,c1, k) denotes that collection c2 represents the removal of pair (k,v) from c1, where v is the value corresponding to key k in c1." I am wondering if the above relations should be introduced as "operations" not as "relations". Defining them as relation would mean IMO that the collections c1 and c2 can be created independently and the only thing that matters is that one collection contains a key-value pair that the other does not. Instead, from the definition, I think that both CollectionAfterInsertion(c2,c1, k, v) and CollectionAfterRemoval(c2,c1, k) were intended to modify the state of the world. For example, CollectionAfterInsertion(c2,c1, k, v) would change the state of the collection of c2 and replace it with the collection that is obtained by inserting the pair <k,v> to c1. The second observation is with respect to the definition of CollectionAfterRemoval. "CollectionAfterRemoval(c2,c1, k) denotes that collection c2 represents the removal of pair (k,v) from c1, where v is the value corresponding to key k in c1." I don't think we should specify the value "v". Thanks, khalid
Received on Wednesday, 8 February 2012 10:24:08 UTC