--- a/model/ProvenanceModel.html Tue Sep 20 01:02:00 2011 -0400
+++ b/model/ProvenanceModel.html Tue Sep 20 13:34:01 2011 +0100
@@ -707,7 +707,7 @@
<p>The activity that a process execution expression is a representation of has a duration, delimited by its start and its end events; hence, it occurs over an interval delimited by two events. However, a process execution expression need not mention time information, nor duration, because they may not be known.</p>
-<p>Such start and end times constitute <em>attributes</em> of an activity, where the meaning of attribute in the context of a process execution expression is similar to the meaning of attribute for entity expression. A process execution expression's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world world can be represented by other attribute-value pairs, which also remain unchanged during the activity duration.</p>
+<p>Such start and end times constitute <em>attributes</em> of an activity, where the meaning of attribute in the context of a process execution expression is similar to the meaning of attribute for entity expression. A process execution expression's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world can be represented by other attribute-value pairs, which MUST also remain unchanged during the activity duration.</p>
<p> An instance of a process execution expression, noted <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:
<ul>
@@ -767,10 +767,10 @@
<p> An agent expression, written <span class="name">agent(e)</span> in PROV-ASN,
- refers to an entity denoted by identifier <span class="name">e</span> and representing the characterized thing capable of activity.
+ refers to an entity expression denoted by identifier <span class="name">e</span> and representing the characterized thing capable of activity.
</p>
-<p>For a characterized thing, one can assert an agent expresson or alternatively, one can infer an agent expression
+<p>For a characterized thing, one can assert an agent expression or alternatively, one can infer an agent expression
by involvement in an activity represented by a process execution expression. </p>
@@ -783,7 +783,7 @@
entity(e2) and wasControlledBy(pe,e2,qualifier(role="author"))
</pre>
-the entity expression identified by <span class="name">e1</span> is accompanied of an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the contrary, from the entity expression identified by <span class="name">e2</span>, one can inferred an agent expression, as per the following inference.
+the entity expression identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the contrary, from the entity expression identified by <span class="name">e2</span>, one can inferred an agent expression, as per the following inference.
</p>
<div class='constraint' id='control-agent'>
@@ -800,7 +800,7 @@
<h4>Annotation</h4>
-<p>An <dfn id="dfn-annotation">annotation expression</dfn> is a set of name value pairs, whose meaning is application specific. It may or may not be a representation of something in the world.</p>
+<p>An <dfn id="dfn-annotation">annotation expression</dfn> is a set of name-value pairs, whose meaning is application specific. It may or may not be a representation of something in the world.</p>
<p>In PROV-ASN, an annotation expression's text matches the <span class="nonterminal">annotationExpression</span> production of the grammar defined in this specification document.
</p>
@@ -842,7 +842,7 @@
</p>
<p>
-Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration.
+Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration. If name-value pairs are a representation of something in the world that does not change, they are not regarded as determining characteristics of a characterized thing or activity, for the purpose of provenance. Indeed, it is not expectede that provenance would contain an explanation for these attribute-values.
</p>
@@ -895,17 +895,17 @@
<p>
-The following generation assertion
+The following generation assertions
<pre class="example">
wasGeneratedBy(e1,pe1,qualifier(port="p1", order=1),t1)
wasGeneratedBy(e2,pe1,qualifier(port="p1", order=2),t2)
</pre>
-states the existence of two events in the world, at which new characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span> are created by an activity, itself represented by a process execution expression identified by <span class="name">pe1</span>.
+state the existence of two events in the world (with respective times <span class="name">t1</span> and <span class="name">t2</span>), at which new characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by a process execution expression identified by <span class="name">pe1</span>.
The first one is available as the first value on port p1, whereas the other is the second value on port p1. The semantics of port and order in these expressions are application specific.
</p>
-<p>A given entity can be generated at most by one process execution in the scope of a given <a href="#expression-Account">account</a>.
+<p>A given entity expression can be referred to in a single generation expression in the scope of a given <a href="#expression-Account">account</a>.
The rationale for this constraint is as follows.
If two process executions sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities. Alternatively, for two process executions to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single process execution. This unicity constraint is formalized as follows.
@@ -924,7 +924,7 @@
attributes are determined by the activity represented by process execution expression identified by <span class="name">pe</span> and the
entity expressions used by <span class="name">pe</span>.
Only some (possibly none) of the attributes values may be determined
-since, in an open world, not all used entitie expressions may have been
+since, in an open world, not all used entity expressions may have been
asserted.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0002">PIL:0002</a>]
</div>