--- a/model/prov-n.html Thu Jul 12 17:56:43 2012 +0100
+++ b/model/prov-n.html Fri Jul 13 10:05:26 2012 +0100
@@ -331,10 +331,10 @@
<section id="sotd">
<h4>Last Call</h4>
<p>
-Publication as Last Call working draft means that
+Publication as Last Call Working Draft means that
the Working Group believes that it has satisfied the relevant technical requirements outlined in its charter on this document. The design is not expected to change significantly, going forward, and now is the key time for external review.</p>
-<p>This specification identifies one <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">feature at risk</a>: the expression <a href="#expression-mention">Mention</a> might be removed from PROV if implementation experience reveals problems with supporting this construct.</p>
+<p>This specification identifies one <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">feature at risk</a>: the expression <a href="#expression-mention">Mention (section 3.5.3)</a> might be removed from PROV if implementation experience reveals problems with supporting this construct.</p>
<!--<h4>Please Comment By 2012-09-18 (TBC)</h4>
<p>The PROV Working group seeks public feedback on this Working Draft.
@@ -388,7 +388,7 @@
<!-- As such, representations of PROV-DM are available in RDF and XML. -->
-With these two requirements in mind, this document introduces PROV-N, a syntax notation designed to write instances of the PROV data model according to the following design principles:
+With these two requirements in mind, this document introduces PROV-N, the PROV notation, a syntax designed to write instances of the PROV data model according to the following design principles:
<ul>
<li>Technology independence. PROV-N provides a simple syntax that can be mapped to several technologies.
@@ -917,7 +917,7 @@
</pre>
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-generationExpression">generationExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-generationExpression">generationExpression</a></code>.</p>
<!--
<p><strong>Note:</strong> Even though the production allows for expressions <span class="name">wasGeneratedBy(e2, -, -)</span> and <span class="name">wasGeneratedBy(-; e2, -, -)</span>, these expressions are not valid in PROV-N, since at least one of <a href="http://www.w3.org/TR/prov-dm/#generation.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#generation.activity"><span class='attribute'>activity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#generation.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#generation.attributes"><span class='attribute'>attributes</span></a> MUST be present.</p>
@@ -988,7 +988,7 @@
</pre>
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code>.</p>
<!--
<p><strong>Note:</strong> Even though the production <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code> allows for expressions <span class="name">used(a2, -, -)</span> and <span class="name">used(-; a2, -, -)</span>, these expressions are not valid in PROV-N, since at least one of <a href="http://www.w3.org/TR/prov-dm/#usage.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.entity"><span class='attribute'>entity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#usage.attributes"><span class='attribute'>attributes</span></a> MUST be present.</p>
@@ -1104,7 +1104,7 @@
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-startExpression">startExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-startExpression">startExpression</a></code>.</p>
<!--
<p><strong>Note:</strong> Even though the production <code class="content"><a class="grammarRef" href="#prod-startExpression">startExpression</a></code> allows for expressions <span class="name">wasStartedBy(e2, -, -, -)</span> and <span class="name">wasStartedBy(-; e2, -, -, -)</span>, these expressions are not valid in PROV-N,
@@ -1178,7 +1178,7 @@
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-endExpression">endExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-endExpression">endExpression</a></code>.</p>
<!--
<p><strong>Note:</strong>Even though the production <code class="content"><a class="grammarRef" href="#prod-endExpression">endExpression</a></code> allows for expressions <span class="name">wasEndedBy(e2, -, -, -)</span> and <span class="name">wasEndedBy(-; e2, -, -, -)</span>, these expressions are not valid in PROV-N,
@@ -1251,7 +1251,7 @@
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code>.</p>
<!--
<p><strong>Note:</strong> Even though the production <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code> allows for expressions <span class="name">wasInvalidatedBy(e2, -, -)</span> and <span class="name">wasInvalidatedBy(-; e2, -, -)</span>, these expressions are not valid in PROV-N, since
@@ -1654,7 +1654,7 @@
</div>
-<a href="#semantic-rules-summary">Additional semantic rules</a> apply to <code class="content"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></code>.
+<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></code>.</p>
<!--
<p><strong>Note:</strong>The production <code class="content"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></code> allows for expressions <span class="name">wasAssociatedWith(a, -, -)</span> and <span class="name">wasAssociatedWith(-; a, -, -)</span>. However, these expressions are not valid in PROV-N,
@@ -2135,7 +2135,7 @@
<p>
A <dfn id="dfn-qualifiedName">qualified name</dfn> is a name subject to <a>namespace</a> interpretation. It consists of a <a>namespace</a>, denoted by an optional prefix, and a local name.
-The PROV data model stipulates that a qualified name can be mapped into an IRI
+The PROV data model stipulates that a qualified name can be mapped to an IRI
by concatenating the IRI associated with the prefix and the local part. This section provides the exact details of this procedure for qualified names defined by PROV-N. </p>
<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
@@ -2181,12 +2181,12 @@
')' (right bracket),
',' (comma),
':' (colon),
-';' (semi-colon),
+';' (semi-colon),
'"' (double quote),
'[' (left square bracket),
']' (right square bracket) are used by the PROV notation as delimiters, they are not allowed in local parts.
-Instead, those characters permitted in SPARQL
-<code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code>, are also allowed in <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code> if they are escaped by the '\' (backslash character) as per production <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_ESC">PN_CHARS_ESC</a></code>. Furthermore, '.' (dot), ':' (colon), '-' (hyphen) can also be \-escaped.</p>
+Instead, among those characters, those that are permitted in SPARQL
+<code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code> are also allowed in <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code> if they are escaped by the '\' (backslash character) as per production <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_ESC">PN_CHARS_ESC</a></code>. Furthermore, '.' (dot), ':' (colon), '-' (hyphen) can also be \-escaped.</p>
@@ -2532,12 +2532,13 @@
The following table provides a summary of such expressions along with examples of syntactically correct but unacceptable forms, and the additional semantic rules.</p>
<div style="text-align: left;">
-<table border="1" style="margin-left: auto; margin-right: auto;">
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="validity-rules-table">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>
</tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a class="grammarRef" href="#prod-generationExpression">Generation expression</a></td>
<td><span class="name">wasGeneratedBy(e2, -, -)</span><br/><span class="name">wasGeneratedBy(-; e2, -, -)</span></td>
<td>At least one of <a href="http://www.w3.org/TR/prov-dm/#generation.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#generation.activity"><span class='attribute'>activity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#generation.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#generation.attributes"><span class='attribute'>attributes</span></a> MUST be present.</td>
@@ -2612,7 +2613,7 @@
<p>Thus, named bundles can occur inside a toplevel bundle.
-Named bundles are self-contained: each identifier occuring in a named bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that named bundle. In other words, named bundles do not inherit namespaces declarations from the toplevel bundle.
+Named bundles are self-contained: each identifier occuring in a named bundle, including the named bundle's identifier itself, MUST be interpreted with respect to the namespace declarations of that named bundle. In other words, named bundles SHOULD not inherit namespaces declarations from the toplevel bundle.
</p>
@@ -2675,7 +2676,7 @@
<div class="anexample">
<p>
-<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMembers</span> relation. The following example shows how one can express membership for an extension of Collections, namely sets of key-value pairs. The notation is a variation of that used for Collections membership, in which the elements of the set are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
+<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMember</span> relation. The following example shows how one can express membership for an extension of Collections, namely sets of key-value pairs. The notation is a variation of that used for Collections membership, allowing multiple member elements to be declared, and in which the elements are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
</p>
<pre class="codeexample">
prefix dictExt <http://example.org/dictionaries>
@@ -2686,7 +2687,9 @@
href="#prod-extensibilityExpression">extensibilityExpression</a></code> production above allows for alternative notations to be used for expressing membership, if the designers of the extensions so desire. Here is an alternate syntax that is consistent with the productions:
<pre class="codeexample">
prefix dictExt <http://example.org/dictionaries>
- dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1), dictExt:pair("k2",e2), dictExt:pair("k3",e3)),
+ dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1),
+ dictExt:pair("k2",e2),
+ dictExt:pair("k3",e3)),
[dictExt:uniqueKeys="true"])
</pre>
@@ -2824,7 +2827,7 @@
<dt>Security considerations:</dt>
<dd>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [[!RFC3023]] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data.</dd>
<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, 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 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
<a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as