--- a/model/working-copy/prov-dm-constraints.html Tue Feb 14 10:32:40 2012 +0000
+++ b/model/working-copy/prov-dm-constraints.html Tue Feb 14 12:04:02 2012 +0000
@@ -410,7 +410,7 @@
- <section id="representation-record-assertion-inference">
+ <section id="representation-term-assertion-inference">
<h3>Description, Assertion, and Inference</h3>
<p>
@@ -463,7 +463,7 @@
</p>
- <section id="record-Account">
+ <section id="term-Account">
<h3>Account</h3>
<p>It is common for multiple provenance records to co-exist. For instance, when emailing
@@ -536,9 +536,9 @@
<p> An identifier in a record within the scope of an account is intended to denote a single record. However, nothing prevents an asserter from asserting an account containing, for example,
multiple entity records with a same identifier but different attribute-values. In that case, they should be understood as a single entity record with this identifier and the union of all
- attributes values, as formalized in <a href="#identifiable-record-in-account">identifiable-record-in-account</a>.</p>
-
- <div class='constraint' id='identifiable-record-in-account'>
+ attributes values, as formalized in <a href="#identifiable-term-in-account">identifiable-term-in-account</a>.</p>
+
+ <div class='constraint' id='identifiable-term-in-account'>
<p>Given an entity record identifier <span class="name">e</span>, two sets of attribute-values denoted by <span class="name">av1</span> and <span class="name">av2</span>,
two entity records <span class="name">entity(e,av1)</span> and <span class="name">entity(e,av2)</span> occurring in an account are equivalent to the entity record <span
class="name">entity(e,av)</span> where <span class="name">av</span> is the set of attribute-value pairs formed by the union of <span class="name">av1</span> and <span
@@ -549,7 +549,7 @@
</div>
- <p>Whilst constraint <a href="#identifiable-record-in-account">identifiable-record-in-account</a> specifies how to understand multiple entity records with a same identifier within a given account, it does not guarantee that the entity record formed with the union of all attribute-value pairs satisfies the <a>attribute occurrence validity</a> property, as illustrated by the following example.</p>
+ <p>Whilst constraint <a href="#identifiable-term-in-account">identifiable-term-in-account</a> specifies how to understand multiple entity records with a same identifier within a given account, it does not guarantee that the entity record formed with the union of all attribute-value pairs satisfies the <a>attribute occurrence validity</a> property, as illustrated by the following example.</p>
<div class="anexample">
@@ -563,7 +563,7 @@
...)
</pre>
- <p>Application of <a href="#identifiable-record-in-account">identifiable-record-in-account</a> results in an entity record containing the attribute-value pairs <span class="name">age=20</span>, <span class="name">weight=50</span>, and <span class="name">age=30</span>. The namespace referred to by prefix <span class="name">ex</span> declares the number of occurrences that are permitted for each attribute. The resulting entity record may or may not satisfy the <a>attribute occurrence validity</a>, depending on this namespace. For instance, if the namespace referred to by <span class="name">ex</span> declares that <span class="name">age</span> must have at most one occurrence, then the resulting entity record does not satisfy the <a>attribute occurrence validity</a> property. This document does not specify how to handle such an entity record.
+ <p>Application of <a href="#identifiable-term-in-account">identifiable-term-in-account</a> results in an entity record containing the attribute-value pairs <span class="name">age=20</span>, <span class="name">weight=50</span>, and <span class="name">age=30</span>. The namespace referred to by prefix <span class="name">ex</span> declares the number of occurrences that are permitted for each attribute. The resulting entity record may or may not satisfy the <a>attribute occurrence validity</a>, depending on this namespace. For instance, if the namespace referred to by <span class="name">ex</span> declares that <span class="name">age</span> must have at most one occurrence, then the resulting entity record does not satisfy the <a>attribute occurrence validity</a> property. This document does not specify how to handle such an entity record.
</p></div>
<p>Account records can be nested since an account record can occur among the records being wrapped by another account. </p>
@@ -577,7 +577,7 @@
<p> The union of two accounts is another account,
containing the unions of their respective records, where
- records with a same identifier should be understood according to constraint <a href="#identifiable-record-in-account">identifiable-record-in-account</a>. Well-formed
+ records with a same identifier should be understood according to constraint <a href="#identifiable-term-in-account">identifiable-term-in-account</a>. Well-formed
accounts are not
closed under union because the
constraint <a href="#generation-uniqueness">generation-uniqueness</a> may no
@@ -674,7 +674,7 @@
- <section id="record-element">
+ <section id="term-element">
<h3>Element</h3>
<div class="issue">
@@ -684,7 +684,7 @@
href="http://www.w3.org/2011/prov/track/issues/145">ISSUE-145</a>.
</div>
- <section id="record-Entity">
+ <section id="term-Entity">
<h4>Entity</h4>
@@ -722,7 +722,7 @@
</section>
- <section id="record-Activity">
+ <section id="term-Activity">
<h3>Activity</h3>
@@ -734,18 +734,19 @@
</p>
<div class="interpretation-forward">
-For the interpretation of an activity record, see <a href="#start-precedes-end">start-precedes-end</a>.
+For the interpretation of an activity, see <a href="#start-precedes-end">start-precedes-end</a>.
</div>
</section>
-<section id="record-Agent">
+<section id="term-Agent">
<h3>Agent</h3>
-
+<div class='issue'> Shouldn't we allow for entities (not agent) to be associated with an activity? Should we drop the inference association-agent? <a
+href="http://www.w3.org/2011/prov/track/issues/203">ISSUE-203</a>.
<p>One can assert an agent record or alternatively, one can infer an agent record
by its association with an activity. </p>
@@ -758,16 +759,17 @@
the record <span class="name">agent(e,attrs)</span> also holds.
</div>
-<div class='issue'> Shouldn't we allow for entities (not agent) to be associated with an activity? Should we drop the inference association-agent? <a
-href="http://www.w3.org/2011/prov/track/issues/203">ISSUE-203</a>.</div>
+</div>
</section>
- <section id="record-note">
+ <section id="term-note">
<h4>Note</h4>
-
+<p>Attribute-value pairs occurring in notes are application specific. Thus, their interpretation is outside the scope of this document, and they are not subject to any of the constraints listed in this document. </p>
+
+<!--
<p>
Attribute-value pairs occurring in notes differ from attribute-value pairs occurring in entity records and activity records. In entity and activity records, attribute-value pairs MUST be a
representation of something in the world, which remain constant for the duration of the characterization interval (for entity record) or the activity duration (for activity records).
@@ -778,81 +780,74 @@
in the world, no requirement is made on this situation to be unchanged for
the entitys' characterization interval.
</p>
-
-<div class='issue'> Comments on notes and their attributes appear in <a href="http://www.w3.org/2011/prov/track/issues/189">ISSUE-189</a>.</div>
+-->
</section>
</section>
-<section id="record-relation">
+<section id="term-relation">
<h3>PROV-DM Relations</h3>
-<section id="record-Generation">
+<section id="term-Generation">
<h4>Generation</h4>
-<p>In PROV-DM, a <dfn id="dfn-Generation">generation record</dfn> is a representation of an instantaneous world <a title="entity generation event">event</a>, the completed creation of a new
+<p>A <dfn id="dfn-Generation">generation</dfn> is an instantaneous world <a title="entity generation event">event</a>, the completed creation of a new
entity by an activity. This entity become available for usage after this <a title="event">instantaneous
-event</a>. This entity did not exist before creation (though another with a different characterization may have existed before).
-The representation of this <a title="event">instantaneous event</a> encompasses a description of the modalities of generation of this entity by this activity.</p>
+event</a>. This entity did not exist before creation.
+ This <a title="event">instantaneous event</a> encompasses a description of the modalities of generation of this entity by this activity, by means of key-value pairs.</p>
<p>
-A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotation">Annotation</a>) or when defining precise-1
+A generation's id is OPTIONAL. It MUST be used when annotating generations (see Section <a href="#term-annotation">Annotation</a>) or when defining precise-1
derivations (see <a href="#Derivation-Relation">Derivation</a>).
</p>
-<p></p>
<div class="interpretation-forward">
-For the interpretation of a generation record, see <a href="#generation-within-activity">generation-within-activity</a>.
+For the interpretation of a generation, see <a href="#generation-within-activity">generation-within-activity</a>.
</div>
<p></p>
<div class="structural-forward">
-See <a href="#generation-uniqueness">generation-uniqueness</a> for a structural constraint on generation records.
+See <a href="#generation-uniqueness">generation-uniqueness</a> for a structural constraint on generations.
</div>
-<div class='pending'> We may want to assert the time at which an entity is created. The placeholder for such time information is a generation record. But a generation mandates the presence of an activity identifier. But it may not be known.
-It would be nice if the activity identifier was made optional in the generation record.
-This is <a href="http://www.w3.org/2011/prov/track/issues/205">ISSUE-205</a>.
-<em>This is now implemented. See also <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</em></div>
</section>
-<section id="record-Usage">
+<section id="term-Usage">
<h3>Usage</h3>
-<p>In PROV-DM, a <dfn id="dfn-Use">usage record</dfn> is a representation of an instantaneous world <a title="entity usage event">event</a>: an activity beginning to consume an entity.
+<p>A <dfn id="dfn-Use">usage</dfn> is an instantaneous world <a title="entity usage event">event</a>: an activity beginning to consume an entity.
Before this event, the activity had not begun to consume or use to this entity.
- The representation includes a description of the modalities of usage of this entity by this activity.</p>
+ The description includes the modalities of usage of this entity by this activity.</p>
<p>
-A usage record's id is OPTIONAL. It MUST be present when annotating usage records (see Section <a href="#record-annotation">Annotation</a>) or when defining precise-1 derivations (see
+A usage id is OPTIONAL. It MUST be present when annotating usages (see Section <a href="#term-annotation">Annotation</a>) or when defining precise-1 derivations (see
<a href="#Derivation-Relation">Derivation</a>).</p>
<p>
-A reference to a given entity record MAY appear in multiple usage records that share
- a given activity record identifier.
+A reference to a given entity MAY appear in multiple usages for a given activity identifier.
</p>
<div class="interpretation-forward">
-For the interpretation of a usage record, see <a href="#generation-precedes-usage">generation-precedes-usage</a> and <a href="#usage-within-activity">usage-within-activity</a>.
+For the interpretation of a usage, see <a href="#generation-precedes-usage">generation-precedes-usage</a> and <a href="#usage-within-activity">usage-within-activity</a>.
</div>
@@ -864,9 +859,12 @@
-<section id="record-ActivityAssociation">
+<section id="term-ActivityAssociation">
<h4>Activity Association</h4>
+<div class="interpretation-forward">
+For the interpretation of an activity association, see <a href="#wasAssociatedWith-ordering">wasAssociatedWith-ordering</a>.
+</div>
<div class='issue'> The activity association record does not allow for a plan to be asserted without an agent.
@@ -879,7 +877,7 @@
</section>
-<section id="record-Start-End">
+<section id="term-Start-End">
<h4>Start and Ends</h4>
@@ -897,7 +895,7 @@
-<section id="record-responsibility">
+<section id="term-responsibility">
<h4>Responsibility Chain</h4>
@@ -911,62 +909,24 @@
-<p>An precise-1 derivation record is richer than an imprecise-1 derivation record, itself, being more informative that an imprecise-n derivation record. Hence, the following implications
+<p>A precise-1 derivation is richer than an imprecise-1 derivation, itself, being more informative that an imprecise-n derivation Hence, the following implications
hold.</p>
<div class='inference' id='derivation-implications'>
-Given two entity records 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,
+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,
e1, a, g2, u1, attrs)</span>
- holds for some generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, then <span
+ holds for some generation identified by <span class="name">g2</span>, and usage identified by <span class="name">u1</span>, then <span
class="name">wasDerivedFrom(e2,e1,[prov:steps="single"] ∪ attrs)</span> also holds.<br>
-Given two entity records 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,
+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,
e1, [prov:steps="single"] ∪ attrs)</span>
holds, then <span class="name">wasDerivedFrom(e2,e1,attrs)</span> also holds.<br>
</div>
<div class="interpretation-forward">
-For the interpretation of a derivation record, see <a href="#derivation-usage-generation-ordering">derivation-usage-generation-ordering</a> and <a
+For the interpretation of a derivation, see <a href="#derivation-usage-generation-ordering">derivation-usage-generation-ordering</a> and <a
href="#derivation-generation-generation-ordering">derivation-generation-generation-ordering</a>
</div>
-<!--
-<p>
-<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then
-this means that the entity represented by entity record identified by <span class="name">e1</span> has an influence on the entity represented entity record identified by <span
-class="name">e2</span>,
- which at the minimum implies temporal ordering, specified as follows.
-First, we consider one-activity derivations.</p>
-
-<div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity record identified by <span class="name">a</span>, entity records identified by <span
-class="name">e1</span> and <span class="name">e2</span>, generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, <span
-class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
-or <span class="name">wasDerivedFrom(e2,e1,[prov:steps="single"] ∪ attrs)</span> holds, <span class='conditional'>then</span>
-the following temporal constraint holds:
-the <a title="entity usage event">usage</a>
-of entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation</a> of
-the entity denoted by <span class="name">e2</span>.
-</div>
-
-<p>Then, imprecise-n derivations.</p>
-
-<div class='interpretation' id='derivation-generation-generation-ordering'>
-Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the record <span
-class="name">wasDerivedFrom(e2,e1,[prov:steps="n"] ∪ attrs)</span>
- holds, <span class='conditional'>then</span> the following temporal constraint holds:
-the <a title="entity generation event">generation event</a> of the entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a>
-of
-the entity denoted by <span class="name">e2</span>.
- </div>
-
-<p>Note that temporal ordering is between generations of <span class="name">e1</span>
-and <span class="name">e2</span>, as opposed to precise-1 derivation,
-which implies temporal ordering between the usage of <span class="name">e1</span> and
-generation of <span class="name">e2</span>. Indeed, in the case of
-imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
-since there is no associated activity.</p>
-
--->
-
<p>The imprecise-1 derivation has the same meaning as the precise-1
derivation, except that an activity
@@ -974,8 +934,8 @@
asserted. This is formalized by the following inference rule,
referred to as <em>activity introduction</em>:</p>
<div class='inference' id="activity-introduction">
-<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> there exist an activity record identified by <span
-class="name">a</span>, a usage record identified by <span class="name">u</span>, and a generation record identified by <span class="name">g</span>
+<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> there exist an activity, with identifier <span
+class="name">a</span>, a usage identified by <span class="name">u</span>, and a generation identified by <span class="name">g</span>
such that:
<pre class="codeexample">
activity(a,aAttrs)
@@ -1002,24 +962,22 @@
</p>
-<p>In PROV-DM, the effective placeholder for an entity generation time is the <a>generation record</a>. The presence of
-time information in imprecise derivation records is merely a convenience notation for a timeless derivation record and a generation record with this generation time information. </p>
+<p>The effective placeholder for an entity generation time is <a>generation</a>. The presence of
+time information in imprecise derivations is merely a convenience notation for a timeless derivation and a generation with this generation time information. </p>
<div class='inference' id="derivation-time-elimination">
-<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,t,attrs)</span> holds, <span class='conditional'>then</span> the following records also hold:
+<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">
-See <a href="#derivation-use">derivation-use</a> for a structural constraint on derivation records.
+See <a href="#derivation-use">derivation-use</a> for a structural constraint on derivations.
</div>
-<div class='pending'>Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.<em>This is now addressed in this text. Optional time in derivation is generation time. See also <a href="http://www.w3.org/2011/prov/track/issues/205">ISSUE-205</a>.</em></div>
-
<div class='issue'>Several points were raised about the attribute steps.
Its name, its default value <a href="http://www.w3.org/2011/prov/track/issues/180">ISSUE-180</a>.
@@ -1027,14 +985,19 @@
<div class='issue'> Emphasize the notion of 'affected by' <a href="http://www.w3.org/2011/prov/track/issues/133">ISSUE-133</a>.</div>
+<div class='issue'> Simplify derivation <a href="http://www.w3.org/2011/prov/track/issues/249">ISSUE-249</a>.</div>
+
</section>
-<section id="record-alternate-specialization">
+<section id="term-alternate-specialization">
<h4>Alternate and Specializations</h4>
+<p>Nothing to add here</p>
+
+ <div class="note">
In order to further convey the intended meaning, the following properties are associated to these two relations.
<ul>
@@ -1046,7 +1009,7 @@
<li><span class="name">alternateOf(e2,e1)</span> is <strong>symmetric</strong>: <span class="name">alternateOf(e2,e1)</span> implies <span class="name">alternateOf(e1,e2)</span>.
</ul>
- <div class="note">There are proposals to make alternateOf a transitive property. This is still under discussion and the default is for alternateOf <strong>not</strong> to be transitive, and this is what the current text reflects.</div>
+There are proposals to make alternateOf a transitive property. This is still under discussion and the default is for alternateOf <strong>not</strong> to be transitive, and this is what the current text reflects.</div>
<div class='issue'>A discussion on alternative definition of these relations has not reached a satisfactory conclusion yet. This is <a
@@ -1078,15 +1041,15 @@
-<section id="record-traceability">
+<section id="term-traceability">
<h3>Traceability</h3>
-<p>A traceability record can be inferred from existing records, or can be asserted stating that such a dependency path exists without the asserter knowing its individual steps, as expressed
+<p>Traceability can be inferred from existing descriptions, or can be asserted stating that a dependency path exists without its individual steps being expressed. This is captured
by the following inference and constraint, respectively.
<div class='inference' id='traceability-inference'>
-Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> identifying entity records,
+Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> for entities,
the following statements hold:
<ol>
@@ -1107,11 +1070,11 @@
</ol>
</div>
-<p>We note that the inference rule <a href="#traceability-inference">traceability-inference</a> does not allow us to infer attributes, which are record and application specific. </p>
+<p>We note that the inference rule <a href="#traceability-inference">traceability-inference</a> does not allow us to infer attributes, which are application specific. </p>
<div class='constraint' id='traceability-assertion'>
-<span class='conditional'>If</span> the record <span class="name">tracedTo(r2,r1,attrs)</span> holds for two identifiers <span class="name">r2</span> and <span class="name">r1</span>
-identifying entity records, and attribute-value pairs <span class="name">attrs</span>,
+<span class='conditional'>If</span> <span class="name">tracedTo(r2,r1,attrs)</span> holds for two identifiers <span class="name">r2</span> and <span class="name">r1</span>
+identifying entities, and attribute-value pairs <span class="name">attrs</span>,
<span class='conditional'>then</span> there exist
<span class="name">e<sup>0</sup></span>, <span class="name">e<sup>1</sup></span>, ..., <span class="name">e<sup>n</sup></span> for <span class="name">n≥1</span>, with <span
class="name">e<sup>0</sup></span>=<span class="name">r2</span> and <span class="name">e<sup>n</sup></span>=<span class="name">r1</span>, and
@@ -1131,12 +1094,12 @@
</div>
<p>We note that the previous constraint is not really an inference <em>rule</em>, since there is nothing that we can actually infer. Instead, this constraint should simply be seen as part
-of the definition of the traceability record. </p>
+of the definition of the traceability relation. </p>
</section>
-<section id="record-OrderingOfActivities">
+<section id="term-OrderingOfActivities">
<h3>Activity Ordering</h3>
@@ -1211,7 +1174,7 @@
</section>
-<section id="record-Revision">
+<section id="term-Revision">
<h3>Revision</h3>
@@ -1262,7 +1225,7 @@
</section>
-<section id="record-quotation">
+<section id="term-quotation">
<h3>Quotation</h3>
@@ -1281,7 +1244,7 @@
</section>
-<section id="record-summary">
+<section id="term-summary">
<h3>Summary</h3>
<div class='issue'>Drop this relation <a href="http://www.w3.org/2011/prov/track/issues/220">ISSUE-220</a>.</div>
@@ -1290,7 +1253,7 @@
</section>
-<section id="record-orignal-source">
+<section id="term-orignal-source">
<h3>Original Source</h3>
<p>Nothing specific.</p>
@@ -1299,7 +1262,7 @@
-<section id="record-Collection">
+<section id="term-Collection">
<h3>Collections</h3>
<div class='issue'>
@@ -1455,7 +1418,7 @@
<div style="text-align: center;">
<figure>
-<img src="constraints.png" alt="constraints between events" />
+<img src="../constraints.png" alt="constraints between events" />
<figcaption id="constraint-summary">Summary of <a title="event">instantaneous event</a> ordering constraints</figcaption>
</figure>
</div>
@@ -1575,7 +1538,7 @@
<div style="text-align: center;">
<figure>
-<img src="constraints2.png" alt="further constraints between events" />
+<img src="../constraints2.png" alt="further constraints between events" />
<figcaption id="constraint-summary2">Summary of <a title="event">instantaneous event</a> ordering constraints (continued)</figcaption>
</figure>
</div>
@@ -1634,12 +1597,12 @@
<h3>Stuff</h3>
<li>
The entity identifier <span class="name">id</span> contained in an entity record is expected to be unique among all the identifiers contained in the current account's records.
-This constraint is elaborated upon in <a href="#identifiable-record-in-account">identifiable-record-in-account</a>. It means that the current account does not contain any other record for
+This constraint is elaborated upon in <a href="#identifiable-term-in-account">identifiable-term-in-account</a>. It means that the current account does not contain any other record for
this identifier. Effectively, <span class="name">id</span> acts as a <em>local</em> identifier for this record. In this specification, whenever we write "an entity record identified by ...
", this identification is to be understood in the context of the account that defines it. </li>
<li>The activity identifier <span class="name">id</span> contained in an activity record is also expected to be unique among all the identifiers contained in the current account's records.
-This constraint is elaborated upon in <a href="#identifiable-record-in-account">identifiable-record-in-account</a>. It means that the current account does not contain any other record for
+This constraint is elaborated upon in <a href="#identifiable-term-in-account">identifiable-term-in-account</a>. It means that the current account does not contain any other record for
this identifier, and that effectively <span class="name">id</span> acts as a <em>local</em> identifier for this record in the current account.</li>
<li>An entity assertion
@@ -1652,7 +1615,7 @@
<li id='attribute-occurrence-in-entity-record'>The attributes
occurring in an entity record MUST be declared in the namespace
referred to by their prefix according to
-<a href="#record-attribute">Section record-attribute</a>. Furthermore,
+<a href="#term-attribute">Section term-attribute</a>. Furthermore,
for each attribute, a namespace also declares the number of
occurrences it may have in a list of attributes. An entity record is
valid if the number of occurrences of any of its attributes is
@@ -1728,7 +1691,7 @@
<!--
-<p>A given entity record can be referred to in a single generation record in the scope of a given <a href="#record-Account">account</a>.
+<p>A given entity record can be referred to in a single generation record in the scope of a given <a href="#term-Account">account</a>.
The rationale for this constraint is as follows.
If two activities sequentially set different values to some attribute by means of two different <a title="entity generation event">generation events</a>, then they generate distinct
entities. Alternatively, for two activities to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this
@@ -1777,7 +1740,7 @@
<p> The union of two accounts is another account,
containing the unions of their respective records, where
- records with a same identifier should be understood according to constraint <a href="#identifiable-record-in-account">identifiable-record-in-account</a>. Structurally well-formed
+ records with a same identifier should be understood according to constraint <a href="#identifiable-term-in-account">identifiable-term-in-account</a>. Structurally well-formed
accounts are not
closed under union because the
constraint <a href="#generation-uniqueness">generation-uniqueness</a> may no
@@ -1949,7 +1912,7 @@
<p>Given that the report is a resource denoted by the URI <span class="name">http://example.org/crime.txt</span>, we could simply use this URI as the identifier of an entity. This would
avoid us minting new URIs. Hence, the report URI would play a double role: as a URI it denotes a resource accessible at that URI, and as an identifier in a PROV-DM record, it helps identify
a specific characterization of this report. A given identifier occurring in an entity record must be unique within the scope of an account. Hence, below, all entities records have been given
-the same identifier but appear in the scope of different accounts, so as to satisfy <a href="#identifiable-record-in-account">identifiable-record-in-account</a>.</p>
+the same identifier but appear in the scope of different accounts, so as to satisfy <a href="#identifiable-term-in-account">identifiable-term-in-account</a>.</p>
<pre>
container