--- a/model/working-copy/wd5-prov-dm-derivation.html Mon Mar 05 11:49:24 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-derivation.html Mon Mar 05 12:55:37 2012 +0000
@@ -258,7 +258,7 @@
<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 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>
<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>
@@ -269,7 +269,7 @@
<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>
-<li><em>time</em>: an OPTIONAL "generation time", the time at which the entity was created;</li>
+<!-- <li><em>time</em>: an OPTIONAL "generation time", the time at which the entity was created;</li>-->
<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs that describe the modalities of this derivation.</li>
</ul>
</div>
@@ -287,7 +287,7 @@
wasDerivedFrom(e2,e1,a,g2,u1)
wasDerivedFrom(e2,e1)
wasDerivedFrom(e2,e1,[prov:type="physical transform"])
-wasDerivedFrom(e2,e1,2012-01-18T16:00:00)
+<!-- wasDerivedFrom(e2,e1,2012-01-18T16:00:00) -->
</pre>
<p>
The first description expresses that activity <span class="name">a</span>,
@@ -299,7 +299,7 @@
<p>
The second and third lines are about derivations between <span class="name">e2</span> and <span class="name">e1</span>, but no information is provided as to the identity of activity (and usage and generation) underpinning the derivation. In the third line, a type attribute is provided.</p>
-<p> The fourth derivation extends the second with the derivation time of <span class="name">e2</span>.
+<!--<p> The fourth derivation extends the second with the derivation time of <span class="name">e2</span>.-->
</p>
</div>
@@ -353,6 +353,7 @@
</p>
+<!--
<p>The effective placeholder for an entity generation time is <a>generation</a>. The presence of
time information in derivations is merely a convenience notation for a timeless derivation and a generation with this generation time information. </p>
@@ -360,6 +361,7 @@
<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,t,attrs)</span> holds, <span class='conditional'>then</span> the following expressions also hold:
<span class="name">wasDerivedFrom(e2,e1,attrs)</span> and <span class="name">wasGeneratedBy(e2,t)</span>.
</div>
+-->
<p></p>
<div class="structural-forward">