update to derivation following GK's comments
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 07 Mar 2012 12:11:14 +0000
changeset 1796 22edc54bf1be
parent 1795 b4f3e101503b
child 1797 5b4187ee9c86
update to derivation following GK's comments
model/working-copy/wd5-prov-dm-derivation.html
--- a/model/working-copy/wd5-prov-dm-derivation.html	Wed Mar 07 12:03:28 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-derivation.html	Wed Mar 07 12:11:14 2012 +0000
@@ -296,7 +296,7 @@
 using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
  derived the
 entity <span class="name">e2</span> and generated it according to generation
- <span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>. With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity <span class="name">e1</span> was used by  the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was (say, for a function returning multiple results).</p>
+ <span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>. With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity <span class="name">e1</span> was used by  the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was obtained from (say, for a function returning multiple results).</p>
 </div>