--- a/model/ProvenanceModel.html Wed Nov 16 15:51:56 2011 +0000
+++ b/model/ProvenanceModel.html Wed Nov 16 17:07:12 2011 +0000
@@ -551,7 +551,7 @@
<p>
-Records of type <strong>UsedRecords</strong> (described in <a href="#record-Use">Section Use</a>) represent the event by which a file is read by an activity.
+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.
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>
@@ -673,7 +673,7 @@
<br/>
<span class="nonterminal">relationRecord</span> :=
<span class="nonterminal">generationRecord</span>
-| <span class="nonterminal">useRecord</span>
+| <span class="nonterminal">usageRecord</span>
| <span class="nonterminal">derivationRecord</span>
| <span class="nonterminal">controlRecord</span>
| <span class="nonterminal">complementRecord</span>
@@ -1055,27 +1055,27 @@
</section>
-<section id="record-Use">
-<h3>Use Record</h3>
-
-
-
-<p>In PROV-DM, a <dfn id="dfn-Use">use 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>A use record, written <span class="name">used(id,a,e,attrs,t)</span> in PROV-ASN, has the following constituent:</p>
+<section id="record-Usage">
+<h3>Usage Record</h3>
+
+
+
+<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>A usage record, written <span class="name">used(id,a,e,attrs,t)</span> in PROV-ASN, has the following constituent:</p>
<ul>
-<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the use record;</li>
+<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>
</ul>
-<p>In PROV-ASN, a use record's text matches the <span class='nonterminal'>useRecord</span> production of the grammar defined in this specification document.</p>
+<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>
<div class='grammar'>
-<span class="nonterminal">useRecord</span> :=
+<span class="nonterminal">usageRecord</span> :=
<span class="name">used</span>
<span class="name">(</span>
[<span class="nonterminal">identifier</span>
@@ -1102,14 +1102,14 @@
<p>
-A use record's id is OPTIONAL, but comes handy when annotating use records (see Section <a href="#record-annotationAssociation">Annotation Association Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
+A usage record's id is OPTIONAL, but comes handy when annotating usage records (see Section <a href="#record-annotationAssociation">Annotation Association Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
</p>
-<p>A reference to a given entity record MAY appear in multiple use records that share
- a given activity record identifier. If one wants to annotate a use 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 use records for this activity
+<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
</p>
@@ -1197,7 +1197,7 @@
<li> refers to an entity record identified by <span class="name">e1</span>, which is a representation of the used entity;</li>
<li> refers to an activity record identified by <span class="name">pe</span>, which is a representation of the activity using and generating the above entities;</li>
<li> contains a set of attribute-value pairs <span class="name">attrs2</span>, which describes the generation record pertaining to <span class="name">e2</span> and <span class="name">pe</span>;</li>
-<li> contains a set of attribute-value pairs <span class="name">attrs1</span>, which describes the use record pertaining to <span class="name">e1</span> and <span class="name">pe</span>.</li>
+<li> contains a set of attribute-value pairs <span class="name">attrs1</span>, which describes the usage record pertaining to <span class="name">e1</span> and <span class="name">pe</span>.</li>
</ul>
@@ -1291,14 +1291,14 @@
<span class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,attrs2)</span> hold, <span class='conditional'>then</span> there exists a set of attribute-value pairs <span class="name">attrs1</span>,
such that <span class="name">used(pe,e1,attrs1)</span> also holds.
</div>
-<p>This inference is justified by the fact that the entity represented by entity record identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this activity record is also the one referred to in the use record of <span class="name">e1</span>.
+<p>This inference is justified by the fact that the entity represented by entity record identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this activity record is also the one referred to in the usage record of <span class="name">e1</span>.
</p>
<p>We note that the "symmetric" inference, does not hold.
From <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">used(pe,e1)</span>, one cannot
-derive <span class="name">wasGeneratedBy(e2,pe,attrs2)</span> because identifier <span class="name">e1</span> may occur in use records referring to
+derive <span class="name">wasGeneratedBy(e2,pe,attrs2)</span> because identifier <span class="name">e1</span> may occur in usage records referring to
many activity records, but they may not be referred to in generation records containing identifier <span class="name">e2</span>.</p>
@@ -1905,15 +1905,15 @@
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,
- any attribute-value set occurring in use 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 use records to have an identifier. Mandating the presence of identifiers in use records would facilitate their annotation. However, this would make it difficult for use records to be encoded as properties in OWL2.
+ 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.
</div>
<p>Attribute-value are used in determining the exact source and destination of a <span class="nonterminal">pe-linked-derivationRecord</span>. Hence,
if one wants to express a <span class="nonterminal">pe-linked-derivationRecord</span> referring to an entity record and an activity record, then:</p>
<ul>
-<li>the set of attribute-values of a use record MUST be unique among the set of attribute-values occurring in use records for this activity;
+<li>the set of attribute-values of a usage record MUST be unique among the set of attribute-values occurring in usage records for this activity;
<li>the set of attribute-values of a generation record MUST be unique among the set of attribute-values occurring in generation records for this activity.
</ul>
@@ -2673,6 +2673,7 @@
<section class="appendix">
<h2>Changes Since Previous Version</h2>
<ul>
+<li>11/16/11: Renamed use record into usage record.</li>
<li>11/16/11: Removed constraint generation-affects-attributes.</li>
<li>11/16/11: Removed constraint use-attributes.</li>
<li>11/16/11: Introduced optional identity for use and generation record.</li>