updated derivation following simon's input
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 06 Mar 2012 14:55:37 +0000
changeset 1771 9599aac2f74f
parent 1770 0e27fcca24b8
child 1772 92862c7b2e3c
child 1773 171890606966
updated derivation following simon's input
model/working-copy/wd5-prov-dm-derivation.html
--- a/model/working-copy/wd5-prov-dm-derivation.html	Mon Mar 05 20:31:07 2012 -0500
+++ b/model/working-copy/wd5-prov-dm-derivation.html	Tue Mar 06 14:55:37 2012 +0000
@@ -258,14 +258,14 @@
 
 <p>According to <a href="#conceptualization">Section Overview</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
 underpinning activities performing the necessary actions resulting in such a derivation.  
-A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to describe modalities of derivation. <!-- Again, optionally, time information can be provided, as a convenient way to express the time at which the entity was generated.  --> If the derivation is the result of a single activity, then the activity can also be optionally expressed. And to provide a completely accurate description of derivation, the generation and usage of the generated and used entities, respectively, can be provided.  </p>
+A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to describe modalities of derivation. <!-- Again, optionally, time information can be provided, as a convenient way to express the time at which the entity was generated.  --> If the derivation is the result of a single known activity, then this activity can also be optionally expressed. And to provide a completely accurate description of derivation, the generation and usage of the generated and used entities, respectively, can be provided.  </p>
 
 
 <p><div class="attributes" id="attributes-derivation">A <dfn>derivation</dfn><span class="withAsn">, written <span class="name">wasDerivedFrom(id, e2, e1, a, g2, u1, t, attrs)</span> in PROV-ASN,</span> contains:</p>
 <ul>
 <li><em>id</em>:  an OPTIONAL identifier  for a derivation;</li> 
-<li><em>generatedEntity</em>: the identifier of the generated entity;</li>
-<li><em>usedEntity</em>: the identifier of the used entity;</li>
+<li><em>generatedEntity</em>: the identifier of the entity generated by the derivation;</li>
+<li><em>usedEntity</em>: the identifier of the entity used by the derivation;</li>
 <li><em>activity</em>: an OPTIONAL identifier for the activity using and generating the above entities;</li>
 <li><em>generation</em>: an OPTIONAL identifier for the generation involving the generated entity and activity;</li> 
 <li><em>usage</em>: an OPTIONAL identifier for the usage involving the used entity and activity;</li> 
@@ -326,7 +326,7 @@
 <b>Section <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm-constraints.html#Derivation-Relation">Derivation-Relation</a> edited as follows</b>.
 
 
-<p>Derivation with are more informative in the presence of activity, generation and usage. Hence, the following implication
+<p>A derivation is more informative if it contains a reference to an activity, generation, and usage. Hence, the following implication
 holds.</p>
 <div class='inference' id='derivation-implication'>
 Given two entities denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion  <span class="name">wasDerivedFrom(e2,