--- a/model/diff-n.html Tue Oct 30 10:07:50 2012 +0000
+++ b/model/diff-n.html Tue Oct 30 11:44:49 2012 +0000
@@ -475,15 +475,13 @@
border-width: 1px;
padding: 0px;
border-style: solid;
- border-color: gray;<span class="insert">
- -moz-border-radius: ;</span>
+ border-color: gray;
}
table.thinborder td {
border-width: 1px;
padding: 2px;
border-style: solid;
- border-color: gray;<span class="insert">
- -moz-border-radius: ;</span>
+ border-color: gray;
}
</style>
@@ -967,7 +965,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-16-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">16 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-30-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">30 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester</dd>
@@ -1336,7 +1334,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 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. Optional 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 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 <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>
@@ -1389,7 +1387,10 @@
<div id="expression-Entity" class="section">
<h4><span class="secno">3.1.1 </span>Entity</h4>
-<div class="withPn">
+
+
+
+
<p>
@@ -1428,7 +1429,7 @@
-</div></div>
+</div>
<div id="expression-Activity" class="section">
<h4><span class="secno">3.1.2 </span>Activity</h4>
@@ -1483,7 +1484,14 @@
<h4><span class="secno">3.1.3 </span>Generation</h4>
-<div class="withPn">
+
+
+
+
+
+
+
+
@@ -1534,7 +1542,7 @@
-</div></div>
+</div>
<div id="expression-Usage" class="section">
<h4><span class="secno">3.1.4 </span>Usage</h4>
@@ -1759,7 +1767,10 @@
<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-<div class="withPn">
+
+
+
+
@@ -1812,7 +1823,7 @@
-</div></div>
+</div>
@@ -1954,7 +1965,9 @@
</pre>
<p>Here, the derivation is provided with a <span class="name">prov:type</span> attribute and value <span class="name">prov:PrimarySource</span>.
-</p></div>
+
+ </p>
+</div>
</div>
@@ -2248,7 +2261,7 @@
<p><span class="insert">The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</span></p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/prov-dm/#dfn-bundle"><span class="insert">Bundle</span></a></b></td><td><b><span class="insert">Non-Terminal</span></b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/prov-dm/#dfn-bundle-constructor"><span class="insert">Bundle</span></a></b></td><td><b><span class="insert">Non-Terminal</span></b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a href="http://www.w3.org/TR/prov-dm/#bundle.constructor.id"><span class="attribute" id="bundle.id"><span class="insert">id</span></span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier"><span class="insert">optionalIdentifier</span></a></code></td></tr>
@@ -2680,7 +2693,7 @@
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-literal" name="prod-literal"></a>[<span class="prodNo">42</span>] </td> <td><code class="production prod">literal</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-typedLiteral">typedLiteral</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></span></code></td> </tr> </tbody>
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-typedLiteral" name="prod-typedLiteral"></a>[<span class="prodNo">43</span>] </td> <td><code class="production prod">typedLiteral</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> "%%" <span class="prod"><a class="grammarRef" href="#prod-datatype">datatype</a></span></code></td> </tr> </tbody>
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-datatype" name="prod-datatype"></a>[<span class="prodNo">44</span>] </td> <td><code class="production prod">datatype</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span></code></td> </tr> </tbody>
-<tbody><tr valign="baseline"><td></td><td></td><td></td></tr></tbody>
+
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-convenienceNotation" name="prod-convenienceNotation"></a>[<span class="prodNo">45</span>] </td> <td><code class="production prod">convenienceNotation</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> (<span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rLANGTAG">LANGTAG</a></span>)?<br> | <span class="prod"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME_LITERAL">QUALIFIED_NAME_LITERAL</a></span></code></td> </tr> </tbody>
<tbody class="term"> <tr valign="baseline"> <td><a id="prod-STRING_LITERAL" name="prod-STRING_LITERAL"></a>[<span class="prodNo"><span class="delete">67</span><span class="insert">60</span></span>] </td> <td><<code class="production term">STRING_LITERAL</code>></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL2">STRING_LITERAL2</a></span><br> | <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></span></code></td> </tr> </tbody>
<tbody class="term"> <tr valign="baseline"> <td><a id="prod-INT_LITERAL" name="prod-INT_LITERAL"></a>[<span class="prodNo"><span class="delete">69</span><span class="insert">62</span></span>] </td> <td><<code class="production term">INT_LITERAL</code>></td> <td> ::= </td> <td><code class="content">("-")? (<span class="prod"><a class="grammarRef" href="#prod-DIGIT">DIGIT</a></span>)+</code></td> </tr> </tbody>
@@ -2828,7 +2841,7 @@
<span class="delete">
the scope of a namespace declaration directly occurring in a</span> <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel </span>bundle</a></code> <span class="insert">itself.</span></li>
<li><span class="insert">
-The scope of a namespace declaration directly occurring in a </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code> is<span class="insert"> the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> itself, exclunding</span> the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel bundle</span><span class="delete"> itself, except and </span><span class="delete">namedBundle</span><span class="insert">bundles</span></a></code> it may contain.</li>
+The scope of a namespace declaration directly occurring in a </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code> is<span class="insert"> the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> itself, excluding</span> the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel bundle</span><span class="delete"> itself, except and </span><span class="delete">namedBundle</span><span class="insert">bundles</span></a></code> it may contain.</li>
</ul>
<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> <em class="rfc2119" title="must not">must not</em> re-declare the same prefix.</p>
@@ -2881,8 +2894,8 @@
<div id="semantic-rules-summary" class="section">
<h4><span class="secno">3.7.5 </span>Summary of additional semantic rules</h4>
-Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] they are not acceptable, because additional semantic rules are defined for those expressions.
- The following table provides a summary of such expressions along with examples of syntactically correct but unacceptable forms, and the additional semantic rules.<p></p>
+<p>Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] they are not acceptable, because additional semantic rules are defined for those expressions.
+ 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 class="thinborder" style="margin-left: auto; margin-right: auto;">
@@ -2899,7 +2912,8 @@
<tr><td><a class="grammarRef" href="#prod-usageExpression">Usage expression</a></td>
<td><span class="name">used(a2, -, -)</span><br><span class="name">used(-; a2, -, -)</span></td>
<td>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> <em class="rfc2119" title="must">must</em> be present</td>
-</tr><tr>
+</tr>
+<tr>
<td><a class="grammarRef" href="#prod-startExpression">Start expression</a></td>
<td> <span class="name">wasStartedBy(e2, -, -, -)</span><br><span class="name">wasStartedBy(-; e2, -, -, -)</span></td>
<td>At least one of <a href="http://www.w3.org/TR/prov-dm/#start.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.starter"><span class="attribute">starter</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#start.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present</td>
@@ -2999,13 +3013,17 @@
<h2><span class="secno">5. </span>Extensibility</h2>
<p>The PROV data model is extensible by means of attributes <span class="name">prov:type</span> and <span class="name">prov:role</span> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.
-</p><ul>
+</p>
+<ul>
<li> PROV-N compliant parsers <em class="rfc2119" title="must">must</em> be able to parse expressions matching the <code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production defined below.
</li><li> As PROV provides no definition for these expressions, PROV compliant implementations
<em class="rfc2119" title="may">may</em> ignore these expressions.</li>
<li> Extensions to PROV and PROV-N <em class="rfc2119" title="may">may</em> specify more specific productions and interpretations for these expressions, which applications <em class="rfc2119" title="may">may</em> adopt to follow. </li>
</ul>
-<p></p>
+
+
+
+
<table class="grammar">
@@ -3024,7 +3042,7 @@
<div class="anexample" id="example_43"><div class="anexampleTitle"><a class="internalDFN" href="#example_43">Example 43</a></div>
<p>
-<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 <em><span class="insert">dictionaries</span></em><span class="insert">, </span>an <span class="insert">illustrative </span>extension of <span class="delete">Collections, namely</span><span class="insert">Collections consisting of</span> sets of <span class="delete">key-value pairs.</span><span class="insert">key-entity pairs, where a key is a </span><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a><span class="insert">.</span> 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>.
+<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 <em><span class="insert">dictionaries</span></em><span class="insert">, </span>an <span class="insert">illustrative </span>extension of <span class="delete">Collections, namely</span><span class="insert">Collections consisting of</span> sets of <span class="delete">key-value pairs.</span><span class="insert">key-entity pairs, where a key is a </span><code><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a></code><span class="insert">.</span> 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>
dictExt:hadMembers(mId; d, {("k1",e1), ("k2",e2), ("k3",e3)}, [])
@@ -3076,12 +3094,12 @@
<dt>Subtype name:</dt>
<dd>provenance-notation</dd>
<dt>Required parameters:</dt>
- <dd>None</dd>
+ <dd><span class="delete">None</span><kbd><span class="insert">charset</span></kbd><span class="insert"> — the value of </span><kbd><span class="insert">charset</span></kbd> <em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> always be </span><kbd><span class="insert">UTF-8</span></kbd><span class="insert">.</span></dd>
<dt>Optional parameters:</dt>
- <dd><tt>charset</tt> — this parameter is mandatory. The value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd>
-
- <dt>Encoding considerations:</dt>
- <dd>The syntax of PROV-N is expressed over code points in Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE5">UNICODE5</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" rel="biblioentry" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
+ <dd><span class="delete">charset</span><span class="delete"> — this parameter is mandatory. The value of </span><span class="delete">charset</span><span class="delete"> is always </span><span class="delete">UTF-8</span><span class="delete">.</span><span class="insert">None</span></dd>
+
+ <dt>Encoding considerations:<span class="insert"> 8bit</span></dt>
+ <dd>The syntax of PROV-N is expressed over code points in Unicode [<cite><span class="delete">UNICODE5</span><a class="bibref" rel="biblioentry" href="#bib-UNICODE"><span class="insert">UNICODE</span></a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" rel="biblioentry" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3023">RFC3023</a></cite>] 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>
@@ -3111,7 +3129,7 @@
<dd>PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
<a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd>
<dt>Applications which use this media type:</dt>
- <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+ <dd><span class="delete">No widely deployed applications are known</span><span class="insert">It may be used by any application for publishing provenance information. This format is designed</span> to <span class="delete">use this media type. It may </span>be <span class="delete">used by some web services and clients consuming their data.</span><span class="insert">a human-readable form of provenance. </span></dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
<dd>PROV-N documents may have the strings <span class="delete">'bundle'</span><span class="insert">'document'</span> near the beginning of the document.</dd>
@@ -3122,7 +3140,7 @@
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
- <dd>public-prov-comments@w3.org</dd>
+ <dd><span class="delete">public-prov-comments@w3.org</span><span class="insert">Ivan Herman, ivan@w3.org</span></dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
@@ -3143,11 +3161,12 @@
<h2><span class="secno">A. </span><span class="insert">Changes since last version</span></h2><p><em><span class="insert">This section is non-normative.</span></em></p>
<p>
</p><ul>
-<p> <a href="http://www.w3.org/2011/prov/track/issues/543"><span class="insert">ISSUE-543</span></a><span class="insert">: uses key-entity pair terminology for example 43.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/538"><span class="insert">ISSUE-538</span></a><span class="insert">: rephrasing of text in example 10.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/547"><span class="insert">ISSUE-547</span></a><span class="insert">: aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/496"><span class="insert">ISSUE-496</span></a><span class="insert">: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
-</span></p></ul>
+<li> <a href="http://www.w3.org/2011/prov/track/issues/543"><span class="insert">ISSUE-543</span></a><span class="insert">: Uses key-entity pair terminology for example 43.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/538"><span class="insert">ISSUE-538</span></a><span class="insert">: Rephrasing of text in example 10.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/547"><span class="insert">ISSUE-547</span></a><span class="insert">: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/496"><span class="insert">ISSUE-496</span></a><span class="insert">: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/573"><span class="insert">ISSUE-573</span></a><span class="insert">: Updated Media Type section.
+</span></li></ul>
</div>
<div class="appendix informative section" id="acknowledgements">
@@ -3229,6 +3248,7 @@
</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd>M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-UNICODE"><span class="insert">[UNICODE]</span></dt><dd><span class="insert">The Unicode Consortium. </span><a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite><span class="insert">The Unicode Standard.</span></cite></a><span class="insert">. Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: </span><a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><span class="insert">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</span></a>
</dd><dt id="bib-URI">[URI]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifiers (URI): generic syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd>F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd>Richard Tobin; et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third Edition).</cite></a> 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a>
@@ -3240,9 +3260,7 @@
</dd><dt id="bib-PROV-RDF">[PROV-RDF]</dt><dd>James Cheney<a href="http://www.w3.org/2011/prov/wiki/ProvRDF"><cite>PROV-RDF Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvRDF">http://www.w3.org/2011/prov/wiki/ProvRDF</a>
</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman"><cite>Formal Semantics Strawman</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>
</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/ProvXML"><cite>PROV-XML Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvXML">http://www.w3.org/2011/prov/wiki/ProvXML</a>
-</dd><dt id="bib-UNICODE5">[UNICODE5]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/versions/Unicode5.1.0/"><cite>The Unicode Standard, Version 5.1.0.</cite></a> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: <a href="http://www.unicode.org/versions/Unicode5.1.0/">http://www.unicode.org/versions/Unicode5.1.0/</a>
-</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis and Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
+</dd><span class="delete">[UNICODE5]</span><span class="delete">The Unicode Consortium. </span><span class="delete">The Unicode Standard, Version 5.1.0.</span><span class="delete"> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: </span><span class="delete">http://www.unicode.org/versions/Unicode5.1.0/</span>
+<dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis and Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
</dd></dl></div></div></body></html>
-
-
--- a/model/prov-n.html Tue Oct 30 10:07:50 2012 +0000
+++ b/model/prov-n.html Tue Oct 30 11:44:49 2012 +0000
@@ -216,6 +216,10 @@
"2011, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+ "UNICODE" :
+ "The Unicode Consortium. "+
+ " <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html\"><cite>The Unicode Standard.</cite></a>. " +
+ " Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html\">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> ",
"UNISEC":
" Mark Davis and Michel Suignard. " +
"<a href=\"http://www.unicode.org/reports/tr36/\"><cite>Unicode Security Considerations<cite></a>. " +
@@ -2451,12 +2455,12 @@
<dt>Subtype name:</dt>
<dd>provenance-notation</dd>
<dt>Required parameters:</dt>
- <dd>None</dd>
+ <dd><kbd>charset</kbd> — the value of <kbd>charset</kbd> MUST always be <kbd>UTF-8</kbd>.</dd>
<dt>Optional parameters:</dt>
- <dd><kbd>charset</kbd> — this parameter is mandatory. The value of <kbd>charset</kbd> is always <kbd>UTF-8</kbd>.</dd>
-
- <dt>Encoding considerations:</dt>
- <dd>The syntax of PROV-N is expressed over code points in Unicode [[UNICODE5]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
+ <dd>None</dd>
+
+ <dt>Encoding considerations: 8bit</dt>
+ <dd>The syntax of PROV-N is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<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>
@@ -2486,7 +2490,7 @@
<dd>PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
<a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd>
<dt>Applications which use this media type:</dt>
- <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+ <dd>It may be used by any application for publishing provenance information. This format is designed to be a human-readable form of provenance. </dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
<dd>PROV-N documents may have the strings 'document' near the beginning of the document.</dd>
@@ -2497,7 +2501,7 @@
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
- <dd>public-prov-comments@w3.org</dd>
+ <dd>Ivan Herman, ivan@w3.org</dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
@@ -2526,10 +2530,11 @@
<h2>Changes since last version</h2>
<p>
<ul>
-<li> <a href="http://www.w3.org/2011/prov/track/issues/543">ISSUE-543</a>: uses key-entity pair terminology for example 43.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: rephrasing of text in example 10.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/543">ISSUE-543</a>: Uses key-entity pair terminology for example 43.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: Rephrasing of text in example 10.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
<li> <a href="http://www.w3.org/2011/prov/track/issues/496">ISSUE-496</a>: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
</ul>
</section>