constraints
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 15 Feb 2012 11:20:56 +0000
changeset 1567 ec6cb230a5b8
parent 1566 860fb8ff6164
child 1568 769ed1fc93b6
constraints
model/working-copy/prov-dm-constraints.html
--- a/model/working-copy/prov-dm-constraints.html	Wed Feb 15 11:18:27 2012 +0000
+++ b/model/working-copy/prov-dm-constraints.html	Wed Feb 15 11:20:56 2012 +0000
@@ -459,7 +459,7 @@
 
 
     <section  id="bundle">
-      <h3>Account</h3>
+      <h3>Account and AccountEntity</h3>
 
 
 	<p>It is common for multiple provenance records to co-exist. For instance, when emailing
@@ -469,7 +469,9 @@
 	  programmer of an experiment may be interested in a detailed log of execution, while the scientists may focus more on the scientific-level description.   Given that multiple provenance
 	  records can co-exist, it is important to have details about their origin, who they are attributed to, how they were generated, etc.  In other words, an important requirement is to be able to express the provenance of provenance. </p>
 
-
+<div class='note'>
+TODO: expand on account, distinguish from accoutnEntity.
+</div>
 
     </section>
 </section>