--- a/model/ProvenanceModel.html Mon Sep 19 09:23:49 2011 +0100
+++ b/model/ProvenanceModel.html Mon Sep 19 09:48:22 2011 +0100
@@ -337,11 +337,11 @@
-<div class='pending'>Alter example to cater for multiple ivpOf. This is <a href="http://www.w3.org/2011/prov/track/issues/33">ISSUE-33</a>.</div>
+<div class='resolved'>Alter example to cater for multiple ivpOf. This is <a href="http://www.w3.org/2011/prov/track/issues/33">ISSUE-33</a>.</div>
<div class='resolved'>Some comments on the example. This is <a href="http://www.w3.org/2011/prov/track/issues/63">ISSUE-63</a>.</div>
-<div class='issue'>Comments on section 3.2. This is <a href="http://www.w3.org/2011/prov/track/issues/71">ISSUE-71</a></div>
+<div class='pending'>Comments on section 3.2. This is <a href="http://www.w3.org/2011/prov/track/issues/71">ISSUE-71</a></div>
<section>
<h3>A File Scenario</h3>
@@ -368,7 +368,7 @@
</p>
<p>Event evt3: Charles emails (pe2) the contents of /share/crime.txt, as an
-attachment, which we refer to as e4. (Our description is not precise about the nature of e4, it could be a copy of the file that is local the mail client, that is uploaded on the mail server, or even in transit to a recipient.)
+attachment, which we refer to as e4. (We specifically refer to a copy of the file that is uploaded on the mail server.)
</p>
<p>
@@ -391,9 +391,9 @@
<section id="example-prov-asn-encoding">
<h3>Encoding using PROV-ASN</h3>
-In this section, the example is encoded according to the provenance data model (specified in section <a href="#data-model-concepts">concepts</a>) and expressed in PROV-ASN.
+In this section, the example is encoded according to the provenance data model (specified in section <a href="#data-model-concepts">PROV-DM: The Provenance Data Model</a>) and expressed in PROV-ASN.
<p>
-Entity Expressions (described in <a href="#expression-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entities.
+Entity Expressions (described in <a href="#expression-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entity expressions, corresponding to multiple characterizations, as per scenario. The entity expressions are identified by <span class="name">e0</span>, ..., <span class="name">e6</span>.
<pre>
entity(e0, [ type= "File", location= "/shared/crime.txt", creator= "Alice" ])
entity(e1, [ type= "File", location= "/shared/crime.txt", creator= "Alice", content= "" ])
@@ -406,7 +406,7 @@
</p>
-<p>The entities are characterized by attributes that have given values during intervals delimited by events; such intervals are referred to as <em>characterization intervals</em>. The following table lists all entities and their corresponding characterization intervals. When the end of the characterization interval is not delimited by an event described in this scenario, it is marked by "...".
+<p>These entity expression list attributes that have been given values during intervals delimited by events; such intervals are referred to as <em>characterization intervals</em>. The following table lists all entity identifiers and their corresponding characterization intervals. When the end of the characterization interval is not delimited by an event described in this scenario, it is marked by "...".
<blockquote>
<table>
<tr><td>Entity</td><td>Characterization Interval</td></tr>
@@ -423,7 +423,7 @@
<p>
-Process Execution Expressions (described in <a href="#expression-ProcessExecution">Section Process Execution</a>): process execution represents an activity in the scenario.
+Process Execution Expressions (described in <a href="#expression-ProcessExecution">Section Process Execution</a>) represent activities in the scenario.
<pre>
processExecution(pe0,create-file,t,,[])
processExecution(pe1,add-crime-in-london,t+1,,[])
@@ -435,36 +435,36 @@
</p>
<p>
-Generation Expressions (described in <a href="#expression-Generation">Section Generation</a>): generation is the event at which a file is created in a specific form. To describe the modalities according to which the various entities are generated by a given process execution, a qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. The interpretation of qualifiers is application specific. Illustrations of such qualifiers are: no specific qualifier is provided for <span class="name">e0</span>;
+Generation Expressions (described in <a href="#expression-Generation">Section Generation</a>) represent the event at which a file is created in a specific form. To describe the modalities according to which the various characterized things are generated by a given activity, a qualifier (expression described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. The interpretation of qualifiers is application specific. Illustrations of such qualifiers for the scenario are: no qualifier is provided for <span class="name">e0</span>;
<span class="name">e2</span> was generated by the editor's save function; <span class="name">e4</span> can be found on the smtp port, in the attachment section of the mail message; <span class="name">e6</span> was produced on the standard output of <span class="name">pe5</span>.
<pre>
wasGeneratedBy(e0, pe0, qualifier())
wasGeneratedBy(e1, pe0, qualifier(fct="create"))
wasGeneratedBy(e2, pe1, qualifier(fct="save"))
wasGeneratedBy(e3, pe3, qualifier(fct="save"))
-wasGeneratedBy(e4, pe2, qualifier(port=smtp, section="attachment"))
-wasGeneratedBy(e5, pe4, qualifier(port=smtp, section="attachment"))
-wasGeneratedBy(e6, pe5, qualifier(file=stdout))
+wasGeneratedBy(e4, pe2, qualifier(port="smtp", section="attachment"))
+wasGeneratedBy(e5, pe4, qualifier(port="smtp", section="attachment"))
+wasGeneratedBy(e6, pe5, qualifier(file="stdout"))
</pre>
</p>
<p>
-Used Expressions (described in <a href="#expression-Use">Section Use</a>): use is the event by which a file is read by a process execution.
-
-Likewise, to describe the modalities according to which the various entities are used by a given process execution, a qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. Illustrations of such qualifiers are:
+UsedExpressions (described in <a href="#expression-Use">Section Use</a>) represent the event by which a file is read by a process execution.
+
+Likewise, to describe the modalities according to which the various things are used by activities, a qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. Illustrations of such qualifiers are:
<span class="name">e1</span> is used in the context of <span class="name">pe1</span>'s <span clasfs="name">load</span> functionality; <span class="name">e2</span> is used by <span class="name">pe2</span> in the context of its attach functionality; <span class="name">e3</span> is used on the standard input by <span class="name">pe5</span>.
<pre>
used(pe1,e1,qualifier(fct="load"))
used(pe3,e2,qualifier(fct="load"))
used(pe2,e2,qualifier(fct="attach"))
used(pe4,e3,qualifier(fct="attach"))
-used(pe5,e3,qualifier(file=stdin))
+used(pe5,e3,qualifier(file="stdin"))
</pre>
</p>
<p>
-Derivation Expressions (described in <a href="#expression-Derivation">Section Derivation</a>): derivations express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the process execution underpinnng the derivation, and relevant qualifier qualifying the use and generation of entities.
+Derivation Expressions (described in <a href="#expression-Derivation">Section Derivation</a>) express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the process execution underpinnng the derivation, and relevant qualifiers qualifying the use and generation of entities.
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -475,7 +475,7 @@
<p>
-wasComplementOf: (this relation is described in <a href="#expression-complement-of">Section wasComplementOf</a>). The crime statistics file (e0) has various contents over its existence (e1,e2,e3); the entites e1,e2,e3 complement e0 with an attribute content. Likewise, e6 complements e3 with an attributed spellchecked.
+wasComplementOf: (this relation is described in <a href="#expression-complement-of">Section wasComplementOf</a>). The crime statistics file (<span class="name">e0</span>) has various contents over its existence (<span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span>); the entity expressions identified by <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span> complement <span class="name">e0</span> with an attribute content. Likewise, the one denoted by <span class="name">e6</span> complements the expression denoted by <span class="name">e3</span> with an attribute spellchecked.
<pre>
wasComplementOf(e1,e0)
wasComplementOf(e2,e0)
@@ -2348,19 +2348,9 @@
</section>
-<section id='PASN-convention'>
- <h3>PROV-ASN Conventions</h3>
-
-
-<div class='note'>This appendix is now obsolete. It should be deleted, making sure all information has been transcribed where appropriate, and all cross-references delete.</div>
-
-<ul>
-<li>Constructs are expressed as <span class="name">name(arg0, arg1, ...)</span>, where the name of the construct occurs first, and is followed by its arguments.</li>
+<!--
<li>For use, generation, and derivation event, the first argument is the 'effect' (i.e. most recent item) and the second argument is the 'cause' (i.e. least recent item). This order is compatible with the temporal layout of the graphical notation.
-</li>
-
-</ul>
-</section>
+-->
</section>