--- a/model/releases/REC-prov-n-20130430/Overview.html Mon Apr 15 14:58:13 2013 -0400
+++ b/model/releases/REC-prov-n-20130430/Overview.html Wed Apr 17 21:56:23 2013 +0100
@@ -960,7 +960,7 @@
<ul>
<li>Technology independence. PROV-N provides a simple syntax that can be mapped to several technologies.
-</li><li>Human readability. PROV-N follows a functional syntax style that is meant to be easily human-readable so it can be used in illustrative examples, such as those presented in the PROV documents suite
+</li><li>Human readability. PROV-N follows a functional syntax style that is meant to be easily human-readable so it can be used in illustrative examples, such as those presented in the PROV documents suite.
</li><li>Formality. PROV-N is defined through a formal grammar amenable to be used with parser generators.
@@ -1511,8 +1511,8 @@
<pre class="codeexample">wasInformedBy(ex:a1, ex:a2)
wasInformedBy(ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
-wasInformedBy(i; ex:a1, ex:a2)
-wasInformedBy(i; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
+wasInformedBy(ex:i; ex:a1, ex:a2)
+wasInformedBy(ex:i; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
</pre>
</div>
</section>
@@ -1553,7 +1553,7 @@
<p>Here <span class="name">start</span> is the optional start identifier, <span class="name">ex:act2</span> is the identifier of the started activity,
<span class="name">ex:trigger</span> is the optional identifier for the entity that triggered the activity start,
<span class="name">ex:act1</span> is the optional identifier for the activity that generated the (possibly unspecified) entity <span class="name">ex:trigger</span>,
- <span class="name">2011-11-16T16:00:00</span> is the optional start time, and <span class="name"> [ex:param="a"]</span> are optional attributes.</p>
+ <span class="name">2011-11-16T16:00:00</span> is the optional start time, and <span class="name"> [ex:param="a"]</span> is a list of optional attributes.</p>
The remaining examples show cases where some of the optionals are omitted.
<pre class="codeexample">wasStartedBy(ex:act2, -, ex:act1, -)
@@ -1604,7 +1604,7 @@
<span class="name">ex:act2</span> is the identifier of the ending activity,
<span class="name">ex:trigger</span> is the identifier of the entity that triggered the activity end,
<span class="name">ex:act3</span> is the optional identifier for the activity that generated the (possibly unspecified) entity <span class="name">ex:trigger</span>,
- <span class="name">2011-11-16T16:00:00</span> is the optional usage time, and <span class="name"> [ex:param="a"]</span> are optional attributes. </p>
+ <span class="name">2011-11-16T16:00:00</span> is the optional usage time, and <span class="name"> [ex:param="a"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
@@ -1656,7 +1656,7 @@
<pre class="codeexample">wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
</pre>
<p> Here <span class="name">ex:inv</span> is the optional invalidation identifier, <span class="name">tr:WD-prov-dm-20111215</span> is the identifier of the entity being invalidated,
- <span class="name">ex:edit1</span> is the optional identifier of the invalidating activity, <span class="name">2011-11-16T16:00:00</span> is the optional invalidation time, and <span class="name"> [ex:fct="save"]</span> are optional attributes. </p>
+ <span class="name">ex:edit1</span> is the optional identifier of the invalidating activity, <span class="name">2011-11-16T16:00:00</span> is the optional invalidation time, and <span class="name"> [ex:fct="save"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
<pre class="codeexample">wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
@@ -1727,7 +1727,7 @@
<span class="name">a</span> is the optional identifier of the activity which used/generated the entities,
<span class="name">g2</span> is the optional identifier of the generation,
<span class="name">u1</span> is the optional identifier of the usage,
- and <span class="name">[ex:comment="a righteous derivation"]</span> are optional attributes. </p>
+ and <span class="name">[ex:comment="a righteous derivation"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
@@ -1857,7 +1857,7 @@
<pre class="codeexample">agent(ag4, [ prov:type='prov:Person', ex:name="David" ])
</pre>
<p>Here <span class="name">ag</span> is the agent identifier, and
- <span class="name">[ prov:type='prov:Person', ex:name="David" ]</span> are optional attributes. </p>
+ <span class="name">[ prov:type='prov:Person', ex:name="David" ]</span> is a list of optional attributes. </p>
In the next example, the optional attributes are omitted.
<pre class="codeexample">agent(ag4)
@@ -1899,7 +1899,7 @@
</pre>
<p> Here <span class="name">attr</span> is the optional attribution identifier, <span class="name">e</span> is an entity identifier,
<span class="name">ag</span> is the identifier of the agent to whom the entity is abscribed,
-and <span class="name">[ex:license='cc:attributionURL' ]</span> are optional attributes. </p>
+and <span class="name">[ex:license='cc:attributionURL' ]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
<pre class="codeexample">wasAttributedTo(e, ag)
@@ -1947,23 +1947,30 @@
<div class="anexample" id="example_25"><div class="anexampleTitle"><a class="internalDFN" href="#example_25">Example 25</a></div>
-<pre class="codeexample">wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:e1, [ex:param1="a", ex:param2="b"])
+<p>The following expression illustrates a plan.
+</p><pre class="codeexample"> entity(ex:pl1, [ prov:type='prov:Plan' ])
+</pre>
+</div>
+
+
+<div class="anexample" id="example_26"><div class="anexampleTitle"><a class="internalDFN" href="#example_26">Example 26</a></div>
+<pre class="codeexample">wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:pl1, [ex:param1="a", ex:param2="b"])
</pre>
<p> Here <span class="name">ex:assoc</span> is the optional attribution identifier,
<span class="name">ex:a1</span> is an activity identifier,
<span class="name">ex:ag1</span> is the optional identifier of the agent associated to the activity,
- <span class="name">ex:e1</span> is the optional identifier of the plan used by the agent in the context of the activity,
- and <span class="name"> [ex:param1="a", ex:param2="b"]</span> are optional attributes. </p>
+ <span class="name">ex:pl1</span> is the optional identifier of the plan used by the agent in the context of the activity,
+ and <span class="name"> [ex:param1="a", ex:param2="b"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">wasAssociatedWith(ex:a1, -, ex:e1)
+<pre class="codeexample">wasAssociatedWith(ex:a1, -, ex:pl1)
wasAssociatedWith(ex:a1, ex:ag1)
-wasAssociatedWith(ex:a1, ex:ag1, ex:e1)
-wasAssociatedWith(ex:a1, ex:ag1, ex:e1, [ex:param1="a", ex:param2="b"])
-wasAssociatedWith(a; ex:a1, -, ex:e1)
+wasAssociatedWith(ex:a1, ex:ag1, ex:pl1)
+wasAssociatedWith(ex:a1, ex:ag1, ex:pl1, [ex:param1="a", ex:param2="b"])
+wasAssociatedWith(a; ex:a1, -, ex:pl1)
</pre>
</div>
@@ -1971,12 +1978,6 @@
<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>
-<div class="anexample" id="example_26"><div class="anexampleTitle"><a class="internalDFN" href="#example_26">Example 26</a></div>
-<p>The following expression illustrates a plan.
-</p><pre class="codeexample"> entity(ex:pl1, [ prov:type='prov:Plan' ])
-</pre>
-</div>
-
<!--
<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,
@@ -2025,7 +2026,7 @@
<span class="name">ag2</span> is the identifier for the delegate agent,
<span class="name">ag1</span> is the identifier of the responsible agent,
<span class="name">a</span> is the optional identifier of the activity for which the delegation link holds,
- and <span class="name">[prov:type="contract"]</span> are optional attributes. </p>
+ and <span class="name">[prov:type="contract"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
@@ -2108,7 +2109,7 @@
<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-bundle-constructor">Bundle</a></b></td><td><b>Non-Terminal</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/2013/REC-prov-dm-20130430/#bundle.constructor.id"><span class="attribute" id="bundle.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.id"><span class="attribute" id="bundle.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.descriptions"><span class="attribute" id="bundle.descriptions">descriptions</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code></td></tr>
@@ -2145,7 +2146,7 @@
<div class="anexample" id="example_30"><div class="anexampleTitle"><a class="internalDFN" href="#example_30">Example 30</a></div>
<p>The bundle of
-<a href="#anexample-bundle1" class="anexample-ref"><span>Example 29</span></a> can be referred to as an an entity, and its provenance described.</p>
+<a href="#anexample-bundle1" class="anexample-ref"><span>Example 29</span></a> can be referred to as an entity, and its provenance described.</p>
<pre class="codeexample"> entity(ex:author-view, [ prov:type='prov:Bundle' ])
</pre>
</div>
@@ -2372,7 +2373,7 @@
-->
-<p>A PROV-N qualified name (production <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code>) has a more permissive syntax then XML's <code class="content"><a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-QName">QName</a></code> [<cite><a class="bibref" href="#bib-XML-NAMES">XML-NAMES</a></cite>]
+<p>A PROV-N qualified name (production <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code>) has a more permissive syntax than XML's <code class="content"><a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-QName">QName</a></code> [<cite><a class="bibref" href="#bib-XML-NAMES">XML-NAMES</a></cite>]
and SPARQL <code class="content"><a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#rPrefixedName">PrefixedName</a></code> [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>].
A <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> consists of a prefix and a local part. Prefixes follow the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> defined by SPARQL [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. Local parts have to be conformant with <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, which extends the original SPARQL <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a></code> definition
by allowing further characters (see <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></code>):</p>
@@ -2813,7 +2814,7 @@
<p>A <dfn id="dfn-document">document</dfn> is a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations. A document forms a self-contained package of provenance descriptions for the purpose of <em>exchanging</em> them. A document may be used
to package up PROV-N expressions in response to a request for the provenance of something ([<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]).</p>
-<p> Given its status of house keeping construct for the purpose of exchanging provenance expressions, a document is not defined as a PROV-N expression (production <code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code>).</p>
+<p> Given its status of house-keeping construct for the purpose of exchanging provenance expressions, a document is not defined as a PROV-N expression (production <code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code>).</p>
@@ -2857,7 +2858,7 @@
endDocument
</pre>
-<p>This container could for instance be returned as the result of a query to a provenance store for the provenance of entity <span class="name">e2</span> [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>].
+<p>This container could, for instance, be returned as the result of a query to a provenance store for the provenance of entity <span class="name">e2</span> [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>].
</p>
</div>