PROV-DM fixed typos (Miles). PROV-N fixed typos (Khalid)
--- a/model/releases/REC-prov-dm-20130430/Overview.html Wed Apr 17 21:56:23 2013 +0100
+++ b/model/releases/REC-prov-dm-20130430/Overview.html Wed Apr 17 22:14:28 2013 +0100
@@ -1607,7 +1607,7 @@
<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component2">5.2</a></td><td style="text-align: left;">about derivation and its subtypes</td></tr>
<tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component3">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
<tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
-<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
+<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring to the same thing</td></tr>
<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections</td></tr>
</tbody></table>
</div>
@@ -1717,7 +1717,7 @@
</li>
<li>There was an editing activity.
-<pre>activity(ex:edit1, [ prov:type="edit" ])
+<pre>activity(ex:edit1, [ prov:type="editing" ])
</pre>
</li>
@@ -2618,7 +2618,7 @@
from which they were derived, so that their reliability can be
investigated.</p>
-<p>It is also important to note that a given entity might be a primary source for one entity but not another. It the reason why Primary Source is defined as a relation as opposed to a subtype of Entity.</p>
+<p>It is also important to note that a given entity might be a primary source for one entity but not another. It is the reason why Primary Source is defined as a relation as opposed to a subtype of Entity.</p>
<p>A <dfn id="dfn-primary-source" class="internalDFN">primary source</dfn><sup><a class="internalDFN" href="#dfn-primary-source"><span class="diamond"> ◊</span></a></sup> relation is a kind of a <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation from
secondary materials to their primary sources. It is recognized that
@@ -2659,8 +2659,8 @@
<h3><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
<p>The third component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="Agent" href="#concept-agent" class="internalDFN">agents</a> and the relations WasAttributedTo
-(<a href="#concept-attribution" class="internalDFN">Attribution</a>), WasAssociatedWith (<a href="#concept-association" class="internalDFN">Association</a>), ActedOnBehalfOf (<a href="#concept-delegation" class="internalDFN">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 UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">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>.
+(<a href="#concept-attribution" class="internalDFN">Attribution</a>), WasAssociatedWith (<a href="#concept-association" class="internalDFN">Association</a>), and ActedOnBehalfOf (<a href="#concept-delegation" class="internalDFN">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 UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SoftwareAgent</a>, and <a title="software-organization" href="#concept-organization" class="internalDFN">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>
@@ -2904,7 +2904,7 @@
</ul></div>
<p>
-A <a href="#concept-usage" class="internalDFN">Usage</a>, <a title="Start" href="#concept-start" class="internalDFN">start</a>, <a title="End" href="#concept-end" class="internalDFN">end</a>, <a title="Generation" href="#concept-generation" class="internalDFN">generation</a>, <a title="Invalidation" href="#concept-invalidation" class="internalDFN">invalidation</a>, <a title="Communication" href="#concept-communication" class="internalDFN">communication</a>, <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a>, <a title="Attribution" href="#concept-attribution" class="internalDFN">attribution</a>, <a title="Association" href="#concept-association" class="internalDFN">association</a>, and <a title="Delegation" href="#concept-delegation" class="internalDFN">delegation</a> is also an <a title="Influence" href="#concept-influence" class="internalDFN">influence</a>. It is <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
+A <a href="#concept-usage" class="internalDFN">usage</a>, <a title="Start" href="#concept-start" class="internalDFN">start</a>, <a title="End" href="#concept-end" class="internalDFN">end</a>, <a title="Generation" href="#concept-generation" class="internalDFN">generation</a>, <a title="Invalidation" href="#concept-invalidation" class="internalDFN">invalidation</a>, <a title="Communication" href="#concept-communication" class="internalDFN">communication</a>, <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a>, <a title="Attribution" href="#concept-attribution" class="internalDFN">attribution</a>, <a title="Association" href="#concept-association" class="internalDFN">association</a>, and <a title="Delegation" href="#concept-delegation" class="internalDFN">delegation</a> is also an <a title="Influence" href="#concept-influence" class="internalDFN">influence</a>. It is <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
</p>
@@ -3237,7 +3237,7 @@
entity(tr:WD-prov-dm-20111215)
alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
</pre>
-<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
+<p>They are both specializations of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
</section>
@@ -3293,7 +3293,7 @@
<section id="term-membership">
<h4><span class="secno">5.6.2 </span>Membership</h4>
-<p>A <strong>membership</strong> relation is defined the members of a Collection to be stated. </p>
+<p>A <strong>membership</strong> relation is defined for stating the members of a Collection. </p>
<span class="glossary-ref"> <dfn id="concept-membership" class="internalDFN">Membership</dfn><sup><a class="internalDFN" href="#concept-membership"><span class="diamond"> ◊</span></a></sup> is the belonging of an entity to a collection. </span>
@@ -3901,7 +3901,7 @@
<td><a title="Bundle" href="#concept-bundle" class="internalDFN">Bundle constructor</a></td>
<td> <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#description-bundle">bundle description</a> </td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">bundle</a></code></td>
-<td rowspan="2"><a href="#component5">Component 4: <br> Bundles</a></td>
+<td rowspan="2"><a href="#component4">Component 4: <br> Bundles</a></td>
</tr>
<tr class="component4-color"><td class="provType"><a title="Bundle Type" href="#dfn-bundle-type" class="internalDFN">Bundle type</a></td>
@@ -3916,7 +3916,7 @@
<td><a title="Alternate" href="#concept-alternate" class="internalDFN">Alternate</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#alternateOf">alternateOf</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-alternateExpression">alternateExpression</a></code></td>
-<td rowspan="2"><a href="#component4">Component 5: <br> Alternate</a></td>
+<td rowspan="2"><a href="#component5">Component 5: <br> Alternate</a></td>
</tr>
<tr class="component5-color">
--- a/model/releases/REC-prov-n-20130430/Overview.html Wed Apr 17 21:56:23 2013 +0100
+++ b/model/releases/REC-prov-n-20130430/Overview.html Wed Apr 17 22:14:28 2013 +0100
@@ -1237,7 +1237,7 @@
<h3><span class="secno">2.5 </span>Identifiers and attributes</h3>
<p>Almost all expressions defined in the grammar include an identifier (see <a href="#expression-identifier">Section 3.7.1</a> for the full syntax of identifiers). Most expressions
-can also include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activites, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers <em class="rfc2119" title="MUST">MUST</em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <em class="rfc2119" title="MUST">MUST</em> be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
+can also include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activities, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers <em class="rfc2119" title="MUST">MUST</em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <em class="rfc2119" title="MUST">MUST</em> be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
<div class="anexample" id="example_9"><div class="anexampleTitle"><a class="internalDFN" href="#example_9">Example 9</a></div>
<p>Derivation has an optional identifier. In the first expression, the identifier is not available, while it is explicit in the second. The third example shows that one can optionally indicate the missing identifier using the <span class="name">-</span> marker. This is equivalent to the first expression. </p>
@@ -1898,7 +1898,7 @@
<pre class="codeexample">wasAttributedTo(attr; e, ag, [ex:license='cc:attributionURL' ])
</pre>
<p> Here <span class="name">attr</span> is the optional attribution identifier, <span class="name">e</span> is an entity identifier,
- <span class="name">ag</span> is the identifier of the agent to whom the entity is abscribed,
+ <span class="name">ag</span> is the identifier of the agent to whom the entity is ascribed,
and <span class="name">[ex:license='cc:attributionURL' ]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.