--- a/model/ProvenanceModel.html Wed Sep 07 17:11:25 2011 +0100
+++ b/model/ProvenanceModel.html Wed Sep 07 17:30:11 2011 +0100
@@ -710,6 +710,59 @@
<div class='resolved'>Should process execution be defined as a subclass of BOB. This is <a href="http://www.w3.org/2011/prov/track/issues/66">ISSUE-66</a>.</div>
</section>
+<section id="expression-Agent">
+<h3>Agent</h3>
+
+
+
+<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation a characterized thing capable of
+activity.</p>
+
+<p>In the Provenance Abstract Syntax Notation, an agent expression's text matches the <span class="nonterminal">agent</span> production of the grammar defined in this specification document.
+</p>
+
+
+<div class='grammar'>
+<span class="nonterminal">agent</span> :=
+<span class="name">agent</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">)</span>
+</div>
+
+
+
+<p> An agent expression, written <span class="name">agent(e)</span> in the Provenance Abstract Syntax Notation:
+ refers to an entity denoted by identifier <span class="name">e</span> and representing the entity capable of activity.
+</p>
+
+<p>A characterized thing can be asserted to be an agent or can be inferred to be
+an agent by involvement in a process execution. </p>
+
+
+
+<p>
+With the following assertions,
+
+<pre class="example">
+entity(e1, [employee: "1234", name: "Alice"]) and agent(e1)
+
+entity(e2) and wasControlledBy(pe,e2)
+</pre>
+entity denoted by <span class="name">e1</span> is asserted to be an agent, and this assertion holds irrespective of process executions it may be involved in, whereas entity denoted by <span class="name">e2</span> can be inferred to be an agent, as per the following inference.
+</p>
+
+<div class='constraint' id='control-agent'>
+<span class='conditional'>If</span>
+ <span class="name">entity(e,av)</span>
+and
+<span class="name">wasControlledBy(pe,e)</span> hold for some identifiers
+<span class="name">pe</span>, <span class="name">e</span>, and attribute-values <span class="name">av</span>, then
+ <span class="name">agent(e)</span> also holds.
+</div>
+</section>
+
+
<section id="expression-Generation">
<h3>Generation<br>
</h3>
@@ -1124,7 +1177,7 @@
<div class='constraint' id='transitive-derivation'>
<ul>
<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds..</li>
+<li><span class='conditional'>If</span> <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
<li><span class='conditional'>If</span> <span class="name">dependedOn(e3,e2)</span> and <span class="name">dependedOn(e2,e1)</span> hold, <span class='conditional'>then</span> <span class="name">dependedOn(e3,e1)</span> holds.</li>
</ul>
</div>
@@ -1149,61 +1202,6 @@
-<section id="expression-Agent">
-<h3>Agent</h3>
-
-
-
-<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation a characterized thing capable of
-activity.</p>
-
-<p>In the Provenance Abstract Syntax Notation, an agent expression's text matches the <span class="nonterminal">agent</span> production of the grammar defined in this specification document.
-</p>
-
-
-<div class='grammar'>
-<span class="nonterminal">agent</span> :=
-<span class="name">agent</span>
-<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">)</span>
-</div>
-
-
-
-<p> An agent expression, written <span class="name">agent(e)</span> in the Provenance Abstract Syntax Notation:
- refers to an entity denoted by identifier <span class="name">e</span> and representing the entity capable of activity.
-</p>
-
-<p>A characterized thing can be asserted to be an agent or can be inferred to be
-an agent by involvement in a process execution. </p>
-
-
-
-<p>
-With the following assertions,
-
-<pre class="example">
-entity(e1, [employee: "1234", name: "Alice"]) and agent(e1)
-
-entity(e2) and wasControlledBy(pe,e2)
-</pre>
-entity denoted by <span class="name">e1</span> is asserted to be an agent, and this assertion holds irrespective of process executions it may be involved in, whereas entity denoted by <span class="name">e2</span> can be inferred to be an agent, as per the following inference.
-</p>
-
-<div class='constraint' id='control-agent'>
-<span class='conditional'>If</span>
- <span class="name">entity(e,av)</span>
-and
-<span class="name">wasControlledBy(pe,e)</span> hold for some identifiers
-<span class="name">pe</span>, <span class="name">e</span>, and attribute-values <span class="name">av</span>, then
- <span class="name">agent(e)</span> also holds.
-</div>
-
-
-
-
-</section>
<section id="expression-Control">
@@ -1247,7 +1245,7 @@
<section id="expression-complement-of">
-<h3>was Complement Of</h3>
+<h3>Complementarity</h3>
<p><dfn id="IVP-of">Is Complement Of</dfn> is a relationship between two characterized things asserted to have compatible characterization over some continuous time interval.<br/>
@@ -1313,115 +1311,6 @@
</section>
-<section id="expression-Time">
-<h3>Time</h3>
-
-<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
-
-
-
-<p>It is OPTIONAL to assert time in use, generation, and process execution.</p>
-
-<div class='resolved'> Is it appropriate to refer to ISO8601. Point in Time, Interval? This is <a href="http://www.w3.org/2011/prov/track/issues/58">ISSUE-58</a>.</div>
-
-<section>
-<h4>Temporal Events</h4>
-Four kinds of discrete events underpin the PIDM data model. They are:
-<ol>
-<li>Generation of an entity by a process execution: identifies the final instant of an entity's creation timespan, after which the characterized thing represented by an entity becomes available for use.</li>
-<li>Use of an entity by a process execution: identifies the first instant of an entity's consumption timespan.</li>
-<li>Start of a process execution: identifies the instant an activity represented by a process execution starts</li>
-<li>End of a process execution: identifies the instant an activity represented by a process execution ends</li>
-</ol>
-</section>
-
-<section>
-<h4>Event Ordering</h4>
-
-
-<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-follows">precedes</dfn> is defined as the symmetric of follows. </p>
-
-<p>This specification introduces inference rules allowing such event ordering to be inferred from provenance constructs.</p>
-</section>
-
-
-</section>
-
-<section id="expression-RecipeLink">
-<h3>Recipe Link</h3>
-
-
-<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between a process execution and a process specification that underpins the process execution.
-</p>
-
-<p>
-It is OPTIONAL to assert recipe links in process executions.
-</p>
-
-
-<p>
-Process specifications, as referred to by recipe links, are out of scope of this specification.
-</p>
-
-</section>
-
-<section id="expression-Role">
-<h3>Role</h3>
-
-
-<p>A <dfn id="dfn-Role">role</dfn> is a label that names the function assumed by an entity or
-an agent with respect to a specific process execution.</p>
-
-<div class='note'>It may be useful to distinguish between a role name and a role type, similarly to
- parameter names and parameter types in a programming language procedure.
-Currently, all the constraints and definitions pertaining to roles in the
-specification should be understood as role names.</div>
-
-
-
-<p>Use, Generation, and Control assertions MUST contain a role. Roles
-are mandatory since they allow for uniform data structures. To facilitate
-the writing of these assertions when a role is unknown by the
-asserter, syntactic notations MAY allow these to be written without a role. In such a case, a default, uniquely named role from the set
-'unspecified role' will be assumed. A countable set of unique labels can be used to denote unspecified roles, as in:
-<span class="name">unspecified0</span>, <span class="name">unspecified1</span>, <span class="name">unspecified2</span>, ....
-
-<pre class="example">
- used(pe,e) expands to used(pe,e,unspecified1)
-</pre>
-where unspecified1 is an unspecified role.
-</p>
-
-<p> The set of all Use (resp. Generation, Control) assertions that refer to a given process execution MUST contain at most one occurrence of a given role. The rationale for this requirement is that when provenance is used to replay execution, roles are used to determine which values must be associated with which input (resp. output, control channel) of a process execution.</p>
-
-<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. MUST is confirmed. </div>
-
-
-<p>The interpretation of a role is specific to the process execution it relates
-to, which means that a same role may appear in relation to two different process executions with different interpretations.
-From this specification's viewpoint, a role's interpretation is out of
-scope.</p>
-
-
-
-
-
-</section>
-
-<section id="expression-Location">
-<h3>Location</h3>
-
-<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be specified, such as by a coordinate, address, landmark, row, column, and so forth.</p>
-
-
-<p>
-Location is an OPTIONAL characteristics of
-entity, process execution, and agent.
-</p>
-
-
-
-</section>
<section id="expression-OrderingOfProcessExecutions">
<h3>Ordering of Process Executions</h3>
@@ -1715,6 +1604,115 @@
</section>
+<section id="expression-Time">
+<h3>Time</h3>
+
+<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
+
+
+
+<p>It is OPTIONAL to assert time in use, generation, and process execution.</p>
+
+<div class='resolved'> Is it appropriate to refer to ISO8601. Point in Time, Interval? This is <a href="http://www.w3.org/2011/prov/track/issues/58">ISSUE-58</a>.</div>
+
+<section>
+<h4>Temporal Events</h4>
+Four kinds of discrete events underpin the PIDM data model. They are:
+<ol>
+<li>Generation of an entity by a process execution: identifies the final instant of an entity's creation timespan, after which the characterized thing represented by an entity becomes available for use.</li>
+<li>Use of an entity by a process execution: identifies the first instant of an entity's consumption timespan.</li>
+<li>Start of a process execution: identifies the instant an activity represented by a process execution starts</li>
+<li>End of a process execution: identifies the instant an activity represented by a process execution ends</li>
+</ol>
+</section>
+
+<section>
+<h4>Event Ordering</h4>
+
+
+<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-follows">precedes</dfn> is defined as the symmetric of follows. </p>
+
+<p>This specification introduces inference rules allowing such event ordering to be inferred from provenance constructs.</p>
+</section>
+
+
+</section>
+
+<section id="expression-RecipeLink">
+<h3>Recipe Link</h3>
+
+
+<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between a process execution and a process specification that underpins the process execution.
+</p>
+
+<p>
+It is OPTIONAL to assert recipe links in process executions.
+</p>
+
+
+<p>
+Process specifications, as referred to by recipe links, are out of scope of this specification.
+</p>
+
+</section>
+
+<section id="expression-Role">
+<h3>Role</h3>
+
+
+<p>A <dfn id="dfn-Role">role</dfn> is a label that names the function assumed by an entity or
+an agent with respect to a specific process execution.</p>
+
+<div class='note'>It may be useful to distinguish between a role name and a role type, similarly to
+ parameter names and parameter types in a programming language procedure.
+Currently, all the constraints and definitions pertaining to roles in the
+specification should be understood as role names.</div>
+
+
+
+<p>Use, Generation, and Control assertions MUST contain a role. Roles
+are mandatory since they allow for uniform data structures. To facilitate
+the writing of these assertions when a role is unknown by the
+asserter, syntactic notations MAY allow these to be written without a role. In such a case, a default, uniquely named role from the set
+'unspecified role' will be assumed. A countable set of unique labels can be used to denote unspecified roles, as in:
+<span class="name">unspecified0</span>, <span class="name">unspecified1</span>, <span class="name">unspecified2</span>, ....
+
+<pre class="example">
+ used(pe,e) expands to used(pe,e,unspecified1)
+</pre>
+where unspecified1 is an unspecified role.
+</p>
+
+<p> The set of all Use (resp. Generation, Control) assertions that refer to a given process execution MUST contain at most one occurrence of a given role. The rationale for this requirement is that when provenance is used to replay execution, roles are used to determine which values must be associated with which input (resp. output, control channel) of a process execution.</p>
+
+<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. MUST is confirmed. </div>
+
+
+<p>The interpretation of a role is specific to the process execution it relates
+to, which means that a same role may appear in relation to two different process executions with different interpretations.
+From this specification's viewpoint, a role's interpretation is out of
+scope.</p>
+
+
+
+
+
+</section>
+
+<section id="expression-Location">
+<h3>Location</h3>
+
+<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be specified, such as by a coordinate, address, landmark, row, column, and so forth.</p>
+
+
+<p>
+Location is an OPTIONAL characteristics of
+entity, process execution, and agent.
+</p>
+
+
+
+</section>
</section>