--- a/model/comments/issue-438-graham.txt Tue Jul 10 18:05:48 2012 -0400
+++ b/model/comments/issue-438-graham.txt Tue Jul 10 18:06:03 2012 -0400
@@ -6,7 +6,7 @@
> PROV-DM than as a separate document.
PROV-DM is already too long, it's better to keep it separate,
-also making it clear that model and serialization are distinct.
+also making it clear that concept model and serialization are distinct.
>
> Some comments for consideration before or after last call:
@@ -14,7 +14,7 @@
> Section 1.1: since we don't have a candidate for PROV-XML going into
> last call, I think that the reference to [PROV-XML] should be dropped.
-TODO?
+TODO
>
> Also, for a section titled "purpose of this document...", I find it
@@ -25,8 +25,7 @@
> reference the corresponding section in PROV-DM (reducing possibilities
> for key information getting out of phase).
-We are not expect prov-o do refer to prov-dm for the namespace.
-The namespace for all our specs. It's reasonable to mention it here.
+It's reasonable to mention the namespace once, here.
>
> Section 2.4: I would have expected to see this section deal with the
@@ -36,7 +35,7 @@
> of resulting URIs, such a central aspect of PROV-N in particular, and
> provenance in general.
-TODO: as a minimum, add cross reference
+Added cross reference.
>
> Section 3.*; there are several references to "non-terminal". This is
@@ -45,7 +44,7 @@
> audience. For example, "how each constituent of a PROV-DM Entity maps
> to a syntax element" would be more descriptive.
-TODO.
+Done.
>
> As I write this, I'm thinking that this aspect of mapping from PROV-DM
@@ -58,7 +57,7 @@
> separate document isn't really a useful separation - see comment at
> top).
-Whether we have prov-n as an appendix or not, wouldn't change the fact
+Whether we have prov-n as an appendix or not wouldn't change the fact
that we have those tables with cross reference to dm definitions.
>
@@ -92,7 +91,7 @@
>
all-or-nothing is what was agreed by the WG.
-It used to be that we could drop the trailing identifiers, but this was
+It used to be that we could drop the trailing arguments, but this was
deemed ambiguous.
@@ -101,14 +100,14 @@
> This section introduces reserved attribute names, but there's no
> indication of where to look for a description of what they mean.
-Stian made the comment also: add ref to DM.
+Stian made the comment also: added ref to DM.
>
> SECTION 3.7.3.1
>
> This section introduces reserved type values, but there's no
> indication of where to look for a description of what they mean.
-Stian made the comment also: add ref to DM.
+Stian made the comment also: added ref to DM.
>
> Section 3.7.4:
>
@@ -117,11 +116,14 @@
> here is a bit confusing - I would expect the namespace URI to *refer
> to* the namespace. I'd say something more like "belongs to" or "is
> part of".
+
+OK, fixed.
+
>
> I would not repeat the namespace URIs here.
>
-TODO
+Removed.
> Section 4
>
@@ -142,10 +144,8 @@
> A PROV-N expression matches the _bundle_ syntax production.
> ]]
-This is the purpose of section 2.2.
-
-In fact, we may want to break section 2.2 in two subsections, just
-after the definition of production.
+This is the purpose of section 2.3 (separated from section 2.2 to make this clearer).
+Text has been streamlined.
>
@@ -177,6 +177,9 @@
> registration makes it seem that it's all a but of an afterthought.
> Also, I suspect it won't get reviewed so carefully here, and security
> is one area which really *needs* as much review as it can get.
+
+To be discussed by email on this issue.
+
>
> The second paragraph doesn't make sense to me: PROV-N does NOT express
> arbitrary application data.
--- a/model/prov-n.html Tue Jul 10 18:05:48 2012 -0400
+++ b/model/prov-n.html Tue Jul 10 18:06:03 2012 -0400
@@ -381,7 +381,7 @@
</p>
<section id="purpose">
-<h2>Purpose of this Document and target audience</h2>
+<h2>Purpose of this Document and Target Audience</h2>
A key goal of PROV is the specification of a machine-processable data model for provenance. However, communicating provenance between humans is also important when teaching, illustrating, formalizing, and discussing provenance-related issues.
@@ -408,8 +408,8 @@
<p>Its target audience is twofold:
<ul>
<li>Developers of provenance management applications, as well as implementors of new PROV data model encodings, and thus in particular of PROV-N parsers. These readers may be interested in the entire structure of the grammar, starting from the top level nonterminal
-<a class="grammarRef" href="#prod-bundle">bundle</a>.</li>
-<li>Readers of the [[PROV-DM]] and of [[PROV-CONSTRAINTS]] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the <a class="grammarRef" href="#prod-expression">expression</a> nonterminal a useful entry point into the grammar.</li>
+<code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</li>
+<li>Readers of the [[PROV-DM]] and of [[PROV-CONSTRAINTS]] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the <code><a class="grammarRef" href="#prod-expression">expression</a></code> nonterminal a useful entry point into the grammar.</li>
</ul>
</section>
@@ -425,8 +425,9 @@
<p><a href="#toplevelBundle">Section 4</a> defines the grammar of toplevel bundles, a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations.</p>
-
-<p><a href="#media-type">Section 5</a> defines media type for the PROV-N notation.</p>
+<p><a href="#extensibility">Section 5</a> defines the extensibility mechanism for the PROV-N notation.</p>
+
+<p><a href="#media-type">Section 6</a> defines media type for the PROV-N notation.</p>
</section>
@@ -533,7 +534,7 @@
<p>
EBNF specifies a series of production rules (<dfn>production</dfn>).
A production rule in the grammar defines a symbol
- <code class="grammarRef">expr</code> (<dfn>non-terminal symbol</dfn>)
+ <code class="grammarRef">expr</code> (<dfn>nonterminal symbol</dfn>)
using the following form:</p>
@@ -556,7 +557,7 @@
<em>term</em>s are used to match strings of one or more characters:
<ul>
<li>
- <code class="grammarRef">expr</code>: matches production for non-terminal symbol <code class="grammarRef">expr</code>
+ <code class="grammarRef">expr</code>: matches production for nonterminal symbol <code class="grammarRef">expr</code>
</li>
@@ -587,81 +588,33 @@
</ul>
</div>
+
+<p>Where suitable, the PROV-N grammar shares production and terminal names with SPARQL grammar [[!RDF-SPARQL-QUERY]].</p>
+
</section>
<section id="main-productions">
<h3>Main Productions</h3>
-The grammar groups the general PROV-N <em>non-terminals</em> in a
-<em>production rule</em> called <code class="grammarRef">expression</code>
-(shown below). This production is introduced as it provides an
-entry point for the core expressions of this grammar. Note that parser
-developers should use the production rule for the <a href="#prod-bundle">top
-level <span class="grammarRef">bundle</span></a> as a starting point
-instead.
-
-
-<!--
-<div class='grammar'>
-<table style="background: white; border=0; ">
-<tr><td><span class="nonterminal">expression</span> <br/><br/><br/><br/><br/><br/><br/>
-</td><td> ::=<br/><br/><br/><br/><br/><br/><br/></td><td>
--->
-<!-- Component 1-->
-<!--
-<a href="#expression-Entity"><span class="nonterminal">entityExpression</span></a>
-| <a href="#expression-Activity"><span class="nonterminal">activityExpression</span> </a>
-| <a href="#expression-Generation"><span class="nonterminal">generationExpression</span> </a>
-| <a href="#expression-Usage"><span class="nonterminal">usageExpression</span> </a>
-<br/>
- | <span class="nonterminal">startExpression</span>
-| <span class="nonterminal">endExpression</span>
-| <span class="nonterminal">invalidationExpression</span>
-| <span class="nonterminal">communicationExpression</span>
-| <span class="nonterminal">startByActivityExpression</span>
-<br/>
--->
-<!-- Component 2-->
-<!--
- | <span class="nonterminal">agentExpression</span>
-| <span class="nonterminal">attributionExpression</span>
-| <span class="nonterminal">associationExpression</span>
-| <span class="nonterminal">responsibilityExpression</span>
-<br/>
--->
-<!-- Component 3-->
-<!--
- | <span class="nonterminal">derivationExpression</span>
-| <span class="nonterminal">revisionExpression</span>
-| <span class="nonterminal">quotationExpression</span> <br/>
- | <span class="nonterminal">hadOriginalSourceExpression</span>
-| <span class="nonterminal">traceExpression</span>
-<br/>
--->
-<!-- Component 4-->
-<!--
- | <span class="nonterminal">alternateExpression</span>
-| <span class="nonterminal">specializationExpression</span>
-<br/>
--->
-<!-- Component 5 TODO-->
-<!-- Component 6-->
-<!--
- | <span class="nonterminal">noteExpression</span>
-| <span class="nonterminal">annotationExpression</span>
-<br/>
-</td></tr>
-</table>
-</div>
--->
+
+<p>Two productions are entry points to the grammar.</p>
+
+<p>The production <code class="grammarRef"><a class="grammarRef" href="#prod-expression">expression</a></code>
+provides the structure for the <em>core expressions</em> of PROV-N.
+
+
+
<table class="grammar">
<tbody class="grammar-ref" data-ref="prod-expression"></tbody>
</table>
-<p>Each of the symbols included in <code>expression</code> above, i.e., <code><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code>, <code><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></code> etc., corresponds to one element (e.g., entity, activity, etc.) of the PROV data model.</p>
-
-<p>A PROV-N document consists of a collection of <a title="expression">expressions</a>, wrapped in a <a class="grammarRef" href="#prod-bundle">toplevel bundle</a> with some namespace declarations, such that the text for an element matches the corresponding <a class="grammarRef" href="#prod-expression">expression</a> production of the grammar.
+<p>Each of the symbols included in <code>expression</code> above, i.e., <code><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code>, <code><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></code> etc., corresponds to one concept (e.g., Entity, Activity, etc.) of the PROV data model.</p>
+
+
+<p>Alternatively, the production rule <code><a href="#prod-bundle"><span class="grammarRef">bundle</span></a></code>
+provides the overall structure of PROV-N descriptions. It is a wrapper for
+ a set of expressions, such that the text for an element matches the corresponding <code><a class="grammarRef" href="#prod-expression">expression</a></code> production, and some namespace declarations.</p>
</section>
@@ -713,7 +666,7 @@
<section id="prov-n-standard-terms">
<h3>Identifiers and attributes</h3>
-<p>Almost all expressions defined in the grammar include an identifier. Most expressions
+<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>
<div class="anexample">
@@ -808,7 +761,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Entity maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Entity maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Entity</b></td><td><b>Non-Terminal</b></td></tr>
@@ -860,7 +813,7 @@
<tbody class="grammar-ref" data-ref="prod-timeOrMarker"></tbody>
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Activity maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Activity maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Activity</b></td><td><b>Non-Terminal</b></td></tr>
@@ -928,7 +881,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Generation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Generation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Generation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -998,7 +951,7 @@
</div>
-->
-<p>The following table summarizes how each constituent of a PROV-DM Usage maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Usage maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Usage</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1063,7 +1016,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Communication maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Communication maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Communication</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1105,7 +1058,7 @@
<tbody class="grammar-ref" data-ref="prod-startExpression"></tbody>
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Start maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Start maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Start</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1172,7 +1125,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM End maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM End maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>End</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1246,7 +1199,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Invalidation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Invalidation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Invalidation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1358,7 +1311,7 @@
<tbody class="grammar-ref" data-ref="prod-derivationExpression"></tbody>
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Derivation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Derivation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Derivation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1501,7 +1454,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Agent maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Agent maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Agent</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1553,7 +1506,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Attribution maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Attribution maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Attribution</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1614,7 +1567,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Association maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Association maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Association</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1687,7 +1640,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Delegation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Delegation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Delegation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1743,7 +1696,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Influence maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Influence maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Influence</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1841,7 +1794,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Alternate maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Alternate maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Alternate</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1887,7 +1840,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Specialization maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Specialization maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Specialization</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1931,7 +1884,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Mention</b></td><td><b>Non-Terminal</b></td></tr>
@@ -2032,7 +1985,7 @@
</table>
-<p>The following table summarizes how each constituent of a PROV-DM Membership maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Membership maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<tr><td><b>Collection Membership</b></td><td><b>Non-Terminal</b></td></tr>
@@ -2178,11 +2131,11 @@
<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
- by concatenating the IRI associated with the prefix and the local part. This section provides the exact details of this procedure for qualified names supported by PROV-N. </p>
+ 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
- qualified name, it MUST refer to a <a>namespace</a> declared in a namespace declaration. In the absence of prefix, the qualified name
- refers to the <a title="default namespace declaration">default namespace</a>.</p>
+ qualified name, the prefix MUST refer to a <a>namespace</a> declared in a namespace declaration. In the absence of prefix, the qualified name
+ belongs to the <a title="default namespace declaration">default namespace</a>.</p>
<!--
<div class='grammar'>
@@ -2511,8 +2464,8 @@
</table>
-<p>A <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration refers to this namespace.
-A <code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></code> consists of a namespace. Every qualified name without prefix in the scope of this declaration refers to this namespace. Scope of a declaration is specified as follows:</p>
+<p>A <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration belongs to this namespace.
+A <code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></code> consists of a namespace. Every qualified name without prefix in the scope of this declaration belongs to this namespace. Scope of a declaration is specified as follows:</p>
<ul>
<li>
The scope of a namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-namedBundle">namedBundle</a></code> is the <code><a class="grammarRef" href="#prod-namedBundle">namedBundle</a></code> itself;</li>
@@ -2674,14 +2627,15 @@
</p>
<pre class="codeexample">
prefix dictExt <http://example.org/dictionaries>
- dictExt:hadMembers(mId; d, {(k1,e1), (k2,e2), (k3,e3)}, [])
+ dictExt:hadMembers(mId; d, {("k1",e1), ("k2",e2), ("k3",e3)}, [])
</pre>
Note that the generic <code class="content"><a class="grammarRef"
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:uniqueKeys="true"])
+ dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1), dictExt:pair("k2",e2), dictExt:pair("k3",e3)),
+ [dictExt:uniqueKeys="true"])
</pre>
@@ -2790,12 +2744,6 @@
The media type of PROV-N is <span class="name">text/provenance-notation</span>. The content encoding of PROV-N content is UTF-8.
</p>
-<div class="note">
-<p>
-See <a href="http://www.w3.org/2002/06/registering-mediatype">http://www.w3.org/2002/06/registering-mediatype</a> for Register an Internet Media Type for a W3C Spec.</p>
-Following text adapted from <a href="http://www.w3.org/TeamSubmission/turtle/#sec-mediaReg">turtle</a>.
-</div>
-
<dl>
<dt>Contact:</dt>
@@ -2845,7 +2793,7 @@
<dt>Interoperability considerations:</dt>
<dd>There are no known interoperability issues.</dd>
<dt>Published specification:</dt>
- <dd>PROV-N: The Provenance Notation, Moreau and Missier, eds,
+ <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>