--- a/model/comments/issue-438-james.txt Tue Jul 10 23:03:40 2012 +0100
+++ b/model/comments/issue-438-james.txt Tue Jul 10 23:31:43 2012 +0100
@@ -15,10 +15,14 @@
fixed
> 2. Example 2: The sentence in the example has no verb.
+
+fixed
>
> 3. Example 8: It looks strange to me that the three statements all
> use ex:a10 instead of different ids. (Also, why a10? Maybe this used
> to be example 10)
+
+a10 -> a1
>
> 4. S2.5: "cooments" sp.
@@ -37,6 +41,9 @@
>
> 7. Example 25, first statement, the first comma should be semicolon
+
+fixed
+
>
> 8. Many relations (wasStartedBy, etc.) have a "Note" saying that at
> least one of the optional parameters must be present. Please
@@ -44,15 +51,23 @@
> one. Alternatively, they could be expressed by adding grammar rules
> (I think this was suggested and discarded before, it's probably not
> very maintainable.)
+
+TODO
+
>
> 9. S3.4.1. There are no examples exercising the option to declare
> namespaces in this section. Please add one, or link to the later
> section on namespace declarations that does have these examples.
+
+Added example 41
+
>
> 10. S3.6. Cf. my suggestion for PROV-DM to just have a single binary
> relation memberOf(element, collection), without the id, attributes or
> completeness flag. This section would also have to change if this
> suggestion is adopted.
+
+Resolution was to move out dictionaries and keep collections unchanged.
>
> 11. In productions 59-63, it seems that some nonterminals are
> references to SPARQL nonterminals, while others have the same name as
@@ -60,6 +75,12 @@
> include all of these to make the PROV-N grammar self-contained? (It
> also might help to give new names to the SPARQL nonterminals that are
> being redefined.)
+
+I was keen to reuse existing productions to avoid having to justify them.
+The only one not redefined is PN_LOCAL, but I thought it was OK to keep
+the name.
+Thoughts? Such names can still be changed after LC.
+
>
> 12. The hyperlink on PN_PREFIX goes to the wrong place in SPARQL.
@@ -83,15 +104,24 @@
>
> 14. S4. Suggest pointing out that bundles cannot be nested (because
> bundles aren't expressions)
+
+This was added.
+
>
> 15. ProvRDF and ProvXML wiki page citations: I don't see why we need
> these, and if we do, I don't think the authorship is correct - I am
> definitely not the only contributor to ProvRDF, and unlikely to do any
> more work on ProvXML (which should eventually be a note).
+
+Can you provide authors for ProvRDF?
+For now you did this provxml page, so it's appropriate to cite you
>
> 16. PROV-SEM will eventually become a note if published, but I'm not
> sure we need to explicitly reference it here as a wiki page. I guess
> this can change later as appropriate.
+
+It's OK, it's informative.
+
>
> --James
> -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
--- a/model/prov-n.html Tue Jul 10 23:03:40 2012 +0100
+++ b/model/prov-n.html Tue Jul 10 23:31:43 2012 +0100
@@ -175,7 +175,7 @@
"URL: <a href=\"http://www.w3.org/2011/prov/wiki/ProvRDF\">http://www.w3.org/2011/prov/wiki/ProvRDF</a>",
"PROV-XML":
- "James Cheney"+
+ "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>",
@@ -350,18 +350,18 @@
<li> <a href="http://www.w3.org/TR/prov-n/">PROV-N</a>, a notation for provenance aimed at human consumption (this document);</li>
<li> <a href="http://www.w3.org/TR/prov-o/">PROV-O</a>, the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF;</li>
<li> <a href="http://www.w3.org/TR/prov-aq/">PROV-AQ</a>, the mechanisms for accessing and querying provenance; </li>
-<li> <a href="http://www.w3.org/TR/prov-primer/">PROV-PRIMER</a>, a primer for the PROV data model;</li>
-<li> PROV-SEM, a formal semantics for the PROV data model;</li>
-<li> PROV-XML, an XML schema for the PROV data model.</li>
+<li> <a href="http://www.w3.org/TR/prov-primer/">PROV-PRIMER</a>, a primer for the PROV data model.</li>
+<!--<li> PROV-SEM, a formal semantics for the PROV data model;</li>
+<li> PROV-XML, an XML schema for the PROV data model.</li> -->
</ul>
<h4>How to read the PROV Family of Specifications</h4>
<ul>
<li>The primer is the entry point to PROV offering an introduction to the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL2 ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.</li>
-<li>The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.</li>
+<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL2 ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. <!--PROV-SEM provides a mathematical semantics.--></li>
+<!-- <li>The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.</li> -->
<li>Developers seeking to retrieve or publish provenance should focus on PROV-AQ.</li>
<li>Readers seeking to implement other PROV serializations
-should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
+should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
</ul>
</section>
@@ -589,7 +589,7 @@
</ul>
</div>
-<p>Where suitable, the PROV-N grammar shares production and terminal names with SPARQL grammar [[!RDF-SPARQL-QUERY]].</p>
+<p>Where suitable, the PROV-N grammar reuses production and terminal names of the SPARQL grammar [[!RDF-SPARQL-QUERY]].</p>
</section>
@@ -683,13 +683,13 @@
<!-- 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 activities have no attributes, and are equivalent.
+<p>The first and second activity expressions have no attributes, and are equivalent.
<!-- does not have any attributes. The second has an empty list of attributes. -->
-The third activity has two attributes.
+The third activity expression has two attributes.
<pre class="codeexample" >
-activity(ex:a10)
-activity(ex:a10, [])
-activity(ex:a10, [ex:param1="a", ex:param2="b"])
+activity(ex:a1)
+activity(ex:a1, [])
+activity(ex:a1, [ex:param1="a", ex:param2="b"])
</pre>
</div>
@@ -1343,7 +1343,7 @@
<div class="anexample" id="anexample-derivation">
<pre class="codeexample">
-wasDerivedFrom(d, e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
+wasDerivedFrom(d; e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
</pre>
<p> Here
<span class="name">d</span> is the optional derivation identifier,