--- a/model/prov-dm.html Mon Jul 09 08:20:15 2012 +0100
+++ b/model/prov-dm.html Mon Jul 09 08:38:00 2012 +0100
@@ -713,7 +713,7 @@
<h2>Entity and Activity</h2>
-<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspect. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
+<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspects. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
physical things such as a mountain, a building, a printed book, or a car as well as abstract concepts and ideas.
</p>
@@ -1055,7 +1055,7 @@
<section id="section-prov-extended-approach-further-relations">
<h2>Further Relations</h2>
-<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</p>
+<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations (such as <a>specialization</a>, <a>alternate</a>).</p>
</section>
@@ -1094,7 +1094,7 @@
<h2>Collections</h2>
<p>
-<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> Many different types of collections exist, such as a <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
+<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
<div class="anexample conceptexample" id="collection-example">
@@ -1160,7 +1160,7 @@
<li>Most expressions
include an identifier
and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the set of attribute-value pairs in the <em>last position</em>.
-Consistent with the convention on arguments, the marker '<span class="name">-</span>' can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising. To further disambiguate expressions that contains an optional identifier, the optional identifier or marker must be followed by '<span class="name">;</span>'.
+Consistent with the convention on arguments, the marker '<span class="name">-</span>' can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising. To further disambiguate expressions that contain an optional identifier, the optional identifier or marker must be followed by '<span class="name">;</span>'.
</li>
</ul>
@@ -1990,7 +1990,7 @@
-<p>The second component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes <a>Revision</a>, <a>Quotation</a>, and <a>Primary Source</a>.
+<p>The third component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes <a>Revision</a>, <a>Quotation</a>, and <a>Primary Source</a>.
<a href="#figure-component2">Figure 6</a> depicts the third component
with PROV core structures in the yellow area, including two classes
(<a>Entity</a>, <a>Activity</a>) and binary association
@@ -2222,7 +2222,7 @@
<p>The second component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the notions of
<a>Attribution</a>, <a>Association</a>, <a>Delegation</a>, relating agents to entities, activities, and agents, respectively.
- Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise and UML association classes to express expanded n-ary relations, and subclasses <a>Plan</a>, <a>Person</a>, <a title="software-agent">SofwareAgent</a>, and <a>Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>
+ Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a>Plan</a>, <a>Person</a>, <a title="software-agent">SofwareAgent</a>, and <a>Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>
</p>
@@ -2774,7 +2774,7 @@
<p>The fifth component of PROV-DM is concerned with
-relations <a>specialization</a> and <a>alternate</a> between entities.
+relations <a>specialization</a>, <a>alternate</a>, and <a>mention</a> between entities.
<a href="#figure-component5">Figure 9</a> depicts
the fifth component with a single class, two binary associations, and a ternary association.
</p>
@@ -2794,7 +2794,7 @@
<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific IRI, as she might edit the article later. Alternatively, user Bob refers to the article in general, independently of its variants over time.</p>
</div>
<p>
-The PROV data model introduces relations, called specialization and alternate
+The PROV data model introduces relations, called specialization, alternate, and mention
that allow entities to be linked together. They are defined as follows. </p>
@@ -2902,7 +2902,8 @@
</div>
-<p>The following notion is a relation between two entities with regard to a bundle. </p>
+<p>The following notion is a relation between two entities with regard to a bundle.
+It is a special case of specialization.</p>
<span class="glossary-ref" data-ref="glossary-mention"></span>
@@ -2927,7 +2928,7 @@
<li><span class='attribute' id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
<li><span class='attribute' id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being mentioned.</li>
-<li><span class='attribute' id="mention.bundle">bundle</span>: an OPTIONAL identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
+<li><span class='attribute' id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>