--- a/model/prov-n.html Mon Nov 26 19:59:16 2012 +0000
+++ b/model/prov-n.html Mon Nov 26 20:11:04 2012 +0000
@@ -1171,7 +1171,7 @@
<h3>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 aslo 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 MUST be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' MUST 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, Activites, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers MUST be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' MUST 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">
<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>
@@ -1187,7 +1187,7 @@
<!-- Expressions with no attributes A distinction is made between expressions with no attributes, and expressions that include an empty list of attributes. -->
<div class="anexample">
-<p>The first and second activity expressions do not speciy any attributes, and are equivalent.
+<p>The first and second activity expressions do not specify any attributes, and are equivalent.
<!-- does not have any attributes. The second has an empty list of attributes. -->
The third activity expression specifies two attributes.
<pre class="codeexample" >
@@ -1547,7 +1547,7 @@
<div class="anexample">
<pre class="codeexample">
-wasEndedBy(end; ex:act2, ex:trigger,ex:act3, 2011-11-16T16:00:00, [ex:param="a"])
+wasEndedBy(end; ex:act2, ex:trigger, ex:act3, 2011-11-16T16:00:00, [ex:param="a"])
</pre>
<p> Here <span class="name">end</span> is the optional end identifier,
<span class="name">ex:act2</span> is the identifier of the ending activity,
@@ -1936,7 +1936,7 @@
<div class="anexample">
-<p>The following expressions illustrates a plan.
+<p>The following expression illustrates a plan.
<pre class="codeexample">
entity(ex:pl1, [ prov:type='prov:Plan' ])
</pre>
@@ -2068,7 +2068,7 @@
<p>Bundles cannot be nested because a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is not an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, and therefore cannot occur inside another <code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</p>
-<p>Each identifier occuring in a bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle, or if the identifier's prefix is not declared in the bundle, with respect to the namespace declarations in the document. </p>
+<p>Each identifier occurring in a bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle, or if the identifier's prefix is not declared in the bundle, with respect to the namespace declarations in the document. </p>
<p>The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</p>
@@ -2447,7 +2447,7 @@
</div>
-<p><b>Note:</b>The productions for the terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> are conflicting.
+<p><b>Note:</b> The productions for the terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> are conflicting.
Indeed, for a tokenizer operating independently of the parse tree, <code>abc</code> matches both
<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and
<code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code>.
@@ -2534,7 +2534,7 @@
<p> In particular, a Literal may be an IRI-typed string (with datatype <span class="name">xsd:anyURI</span>); such IRI has no specific interpretation in the context of PROV.</p>
-<p><b>Note:</b>The productions for terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and
+<p><b>Note:</b> The productions for terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and
<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> are conflicting.
Indeed, for a tokenizer operating independently of the parse tree, <code>1234</code> matches both <code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> and <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> (local name without prefix). In the context of
a <code class="content"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></code>, a tokenizer should give preference to the production
@@ -2666,7 +2666,7 @@
<li>
The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is the <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> itself.</li>
<li>
-The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-document">document</a></code> is the <code><a class="grammarRef" href="#prod-document">document</a></code> including the <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> it contains but excluding those <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> that redeclare this prefix.</li>
+The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-document">document</a></code> is the <code><a class="grammarRef" href="#prod-document">document</a></code> including the <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> it contains but excluding those <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> that re-declare this prefix.</li>
</ul>
<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> MUST NOT re-declare the same prefix.</p>
@@ -2744,7 +2744,7 @@
<div style="text-align: left;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="validity-rules-table">Summary of additional semantic rules for grammar productions</caption>
+<caption id="validity-rules-table">Table 2: Summary of additional semantic rules for grammar productions</caption>
<tr><td><a><b>Production</b></a></td>
<td><b>Examples of syntactically correct expressions</b></td>
<td><b>Additional semantic rule</b></td>
@@ -2950,7 +2950,7 @@
<dd>PROV-N is used to express the provenance of arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on PROV-N documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information. </dd>
<dd>PROV-N can express data which is presented to the user, for example, by means of label attributes. Application rendering strings retrieved from untrusted PROV-N documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
<dd>PROV-N is a language for describing the provenance of things, and therefore a PROV-N document is metadata for other resources. Untrusted PROV-N documents may mislead its consumers by indicating that a third-party resource has a reputable lineage, when it has not. Provenance of PROV-N document should be sought. </dd>
- <dd>PROV-N uses qualified names mappeable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
+ <dd>PROV-N uses qualified names mappable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
<a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as
<a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [[!RFC3986]] Section 7.</dd>
<dd>Multiple IRIs may have the same appearance. Characters in different scripts may