review response
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 11 Apr 2012 10:06:37 +0100
changeset 2261 47300e17565f
parent 2260 2202a421b65e
child 2262 4e1dede485bc
review response
model/comments/issue-331-Khalid.txt
--- a/model/comments/issue-331-Khalid.txt	Wed Apr 11 09:59:41 2012 +0100
+++ b/model/comments/issue-331-Khalid.txt	Wed Apr 11 10:06:37 2012 +0100
@@ -107,9 +107,13 @@
   > a2 was started by a1. There is an assumption that the reader will
   > understand that a sub-workflow will be started by the parent
   > workflow. I think this should explicitly stated.
+
+OK to add.
   > 
   > - 4.4.1 Specialization In the first paragraph: "common entity" ->
   > "common thing"
+
+I don't see this. Where is it?
   > 
   > -4.5 Component 5: Collections I think that there is a need for
   > defining collection here.  Although it is stated that a collection is
@@ -124,3 +128,16 @@
   > For example, we can define a collection c1 as
   > entity (c1, [prov:type="Collection", prov:members = {<k1,v1>,...,<kn,vn>}]
   > 
+
+It goes against the convention we adopted in prov-dm that all
+relations between entities that matter from a provenance viewpoint are
+expressed by means of prov-dm relations, and not by means of
+attributes.
+
+
+This is expressed with 
+derivedByInsertionFrom(c1, c0, {("k1", e1), ("k2", e2), ...})       
+
+where c0 is an empty collection.
+
+Do we need another relation for this?