--- a/model/ProvenanceModel.html Wed Nov 16 17:07:26 2011 +0000
+++ b/model/ProvenanceModel.html Wed Nov 16 17:10:20 2011 +0000
@@ -410,7 +410,7 @@
<li>An <strong>Entity Record</strong> (noted <samp>entity</samp> in the diagram, to reflect the term used in the ASN) is a representation of an <em>entity</em>. The EntityRecord may specify a set of <strong>attributes</strong>. The
<strong>wasComplementOf</strong> relationship is used to denote that two <samp>entities</samp> <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.</li>
- <li>An <strong>Activity Record </strong>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an <samp>entity</samp> in a <samp>activity</samp>. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
+ <li>An <strong>Activity Record </strong>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Usage and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an <samp>entity</samp> in a <samp>activity</samp>. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
Note that multiple <samp>activities</samp> may <em>use</em> the same <samp>entity</samp>, and each may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.</li>
<li>An <strong>Agent Record</strong> represent a particular <samp>entity</samp> that can be associated to activities, meaning it is capable of controlling <samp>activitys</samp>.
@@ -551,7 +551,7 @@
<p>
-Records of type <strong>UsedRecords</strong> (described in <a href="#record-Usage">Section Use</a>) represent the event by which a file is read by an activity.
+Records of type <strong>Usage Records</strong> (described in <a href="#record-Usage">Section Usage</a>) represent the event by which a file is read by an activity.
Likewise, attributes describe the modalities according to which the various entities are used by activities. Illustrations of such attributes are:
<span class="name">e1</span> is used in the context of <span class="name">pe1</span>'s <span class="name">load</span> functionality; <span class="name">e2</span> is used by <span class="name">pe2</span> in the context of its attach functionality; <span class="name">e3</span> is used on the standard input by <span class="name">pe5</span>. </p>
@@ -565,7 +565,7 @@
<p>
-Derivation Records (described in <a href="#Derivation-Relation">Section Derivation Relation</a>) express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the activity underpinning the derivation, and relevant attribute describing the use and generation of entities.</p>
+Derivation Records (described in <a href="#Derivation-Relation">Section Derivation Relation</a>) express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the activity underpinning the derivation, and relevant attribute describing the usage and generation of entities.</p>
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -1060,7 +1060,7 @@
-<p>In PROV-DM, a <dfn id="dfn-Use">usage record</dfn> is a representation of a world event: the consumption of an entity by an activity. The representation includes a description of the modalities of use of this entity by this activity.</p>
+<p>In PROV-DM, a <dfn id="dfn-Use">usage record</dfn> is a representation of a world event: the consumption of an entity by an activity. The representation includes a description of the modalities of usage of this entity by this activity.</p>
<p>A usage record, written <span class="name">used(id,a,e,attrs,t)</span> in PROV-ASN, has the following constituent:</p>
@@ -1068,8 +1068,8 @@
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the usage record;</li>
<li><em>activity</em>: an identifier <span class="name">a</span> for an activity record, which represents the consuming activity;</li>
<li><em>entity</em>: an identifier <span class="name">e</span> for an entity record, which represents the entity that is consumed;</li>
-<li><em>attributes</em>: a set of attribute-value pairs <span class="name">attrs</span> that describe the modalities of use of this entity by this activity;</li>
-<li><em>time</em>: an OPTIONAL "use time" <span class="name">t</span>, the time at which the entity was used.</li>
+<li><em>attributes</em>: a set of attribute-value pairs <span class="name">attrs</span> that describe the modalities of usage of this entity by this activity;</li>
+<li><em>time</em>: an OPTIONAL "usage time" <span class="name">t</span>, the time at which the entity was used.</li>
</ul>
<p>In PROV-ASN, a usage record's text matches the <span class='nonterminal'>usageRecord</span> production of the grammar defined in this specification document.</p>
@@ -1093,7 +1093,7 @@
-<p>The following use assertions</p>
+<p>The following usage records</p>
<pre class="example">
used(pe1,e1,[ex:parameter="p1"),t1)
used(pe1,e2,[ex:parameter="p2"),t2)
@@ -1109,7 +1109,7 @@
<p>A reference to a given entity record MAY appear in multiple usage records that share
- a given activity record identifier. If one wants to annotate a usage record or if one wants to express a <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a> referring to this entity and activity records, the attributes occuring in this use assertion MUST be unique among the attributes of other usage records for this activity
+ a given activity record identifier. If one wants to annotate a usage record or if one wants to express a <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a> referring to this entity and activity records, the attributes occuring in this usage assertion MUST be unique among the attributes of other usage records for this activity
</p>
@@ -1122,7 +1122,7 @@
<div class='interpretation' id='use-pe-ordering'>Given an activity record identified by <span class="name">pe</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
assertion <span class="name">used(pe,e,attrs)</span> or <span class="name">used(pe,e,attrs,t)</span> holds, <span class='conditional'>then</span>
- the use of the entity represented by entity record identified by <span class="name">e</span> precedes the end of activity represented by record identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the entity denoted by entity record identified by <span class="name">e</span> always precedes
+ the usage of the entity represented by entity record identified by <span class="name">e</span> precedes the end of activity represented by record identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the entity denoted by entity record identified by <span class="name">e</span> always precedes
its use.
</div>
@@ -1247,7 +1247,7 @@
<p>
-The following inference rule states that a generation and use event can be inferred from an activity linked derivation record.
+The following inference rule states that a generation and usage event can be inferred from an activity linked derivation record.
</p>
<div class="constraint" id='derivation-events'>
@@ -1273,7 +1273,7 @@
<p>
-Note that inferring derivation from use and generation does not hold
+Note that inferring derivation from usage and generation does not hold
in general. Indeed, when a generation <span class="name">wasGeneratedBy(e2,pe,attrs2)</span>
precedes <span class="name">used(pe,e1,attrs1)</span>, for
some <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">attrs1</span>, <span class="name">attrs2</span>, and <span class="name">pe</span>, one
@@ -1333,9 +1333,9 @@
<p>Note that temporal ordering is between generations of <span class="name">e1</span>
and <span class="name">e2</span>, as opposed to activity linked derivation,
-which implies temporal ordering between the use of <span class="name">e1</span> and
+which implies temporal ordering between the usage of <span class="name">e1</span> and
generation of <span class="name">e2</span> (see <a href="#derivation-use-generation-ordering">derivation-use-generation-ordering</a>). Indeed, in the case of
-wasEventuallyDerivedFrom, nothing is known about the use of <span class="name">e1</span>,
+wasEventuallyDerivedFrom, nothing is known about the usage of <span class="name">e1</span>,
since there is no associated activity.</p>
<p>An activity linked derivation record is a richer than an activity independent derivation record, since it
@@ -1483,7 +1483,7 @@
a representation of an entity involved in this activity.
</ul>
-<p>An entity's participation in an activity can be by direct use or direct control. But also, if an entity and situation are characterized in two complementary manners (and are represented by two entity records related by <span class="name">isComplementOf</span>), if one of them participates in an activity, so does the other. The following captures the definition of participation.</p>
+<p>An entity's participation in an activity can be by direct usage or direct control. But also, if an entity and situation are characterized in two complementary manners (and are represented by two entity records related by <span class="name">isComplementOf</span>), if one of them participates in an activity, so does the other. The following captures the definition of participation.</p>
<div class='constraint' id='participation'>
Given two identifiers <span class="name">pe</span> and <span class="name">e</span>, respectively identifying an activity record and an entity record, the record <span class="name">hadParticipant(pe,e)</span> holds <span class='conditional'>if and only if</span>:
@@ -1901,10 +1901,10 @@
<p>
-By definition, a use (resp. generation, control) record does not contain an identifier.
-If one wants to annotate a use (resp. generation, control) record, this record MUST be identifiable from its constituents, i.e. its source's identifier, its destination's identifier, and its attributes.</p>
-
-<p> To be able to annotate use (resp. generation, control) records that refer to a given activity identifier,
+By definition, a usage (resp. generation, control) record does not contain an identifier.
+If one wants to annotate a usage (resp. generation, control) record, this record MUST be identifiable from its constituents, i.e. its source's identifier, its destination's identifier, and its attributes.</p>
+
+<p> To be able to annotate usage (resp. generation, control) records that refer to a given activity identifier,
any attribute-value set occurring in usage records (resp. generation, control) with this identifier and a given entity record identifier MUST be unique.</p>
<div class='note'>It may seem strange that we do not require usage records to have an identifier. Mandating the presence of identifiers in usage records would facilitate their annotation. However, this would make it difficult for usage records to be encoded as properties in OWL2.
@@ -2013,7 +2013,7 @@
Four kinds of discrete events underpin the PROV-DM data model. They are:
<ol>
<li>Generation of an entity by an activity: identifies the final instant of an entity's creation timespan, after which it becomes available for use.</li>
-<li>Use of an entity by an activity: identifies the first instant of an entity's consumption timespan.</li>
+<li>Usage of an entity by an activity: identifies the first instant of an entity's consumption timespan.</li>
<li>Start of an activity: identifies the instant an activity, represented by an activity, starts;</li>
<li>End of an activity: identifies the instant an activity, represented by an activity, ends.</li>
</ol>