--- a/model/ProvenanceModel.html Thu Sep 01 14:50:35 2011 +0100
+++ b/model/ProvenanceModel.html Mon Sep 05 13:07:27 2011 +0100
@@ -199,10 +199,10 @@
<p>
Derivations (construct described in <a href="#concept-Derivation">Section Derivation</a>): derivations express that an entity is derived from another.
<pre>
-isDerivedFrom(e2,e1)
-isDerivedFrom(e3,e2)
-isDerivedFrom(e4,e2)
-isDerivedFrom(e5,e3)
+wasDerivedFrom(e2,e1)
+wasDerivedFrom(e3,e2)
+wasDerivedFrom(e4,e2)
+wasDerivedFrom(e5,e3)
</pre>
</p>
@@ -221,37 +221,37 @@
<p>
Generations (construct described in <a href="#concept-Generation">Section Generation</a>): generation is the event at which a file is created in a specific form. To distinguish the function that the various entities generated by a given process execution have in the context of this process execution, a role (construct described in <a href="#concept-Role">Section Role</a>) is introduced. Illustrations of such roles are outFile, outContent, out, attachment.
<pre>
-isGeneratedBy(e0,pe0,outFile)
-isGeneratedBy(e1,pe0,outContent)
-isGeneratedBy(e2,pe1,out)
-isGeneratedBy(e3,pe3,out)
-isGeneratedBy(e4,pe2,attachment)
-isGeneratedBy(e5,pe4,attachment)
-isGeneratedBy(e6,pe5,out)
+wasGeneratedBy(e0,pe0,outFile)
+wasGeneratedBy(e1,pe0,outContent)
+wasGeneratedBy(e2,pe1,out)
+wasGeneratedBy(e3,pe3,out)
+wasGeneratedBy(e4,pe2,attachment)
+wasGeneratedBy(e5,pe4,attachment)
+wasGeneratedBy(e6,pe5,out)
</pre>
</p>
<p>
-Uses (construct described in <a href="#concept-Use">Section Use</a>): use is the event by which a file is read by a process execution. To distinguish the various entities used by a given process execution, a role (construct described in <a href="#concept-Role">Section Role</a>) is introduced. Illustrations of such roles are in and fileIn.
+Used (construct described in <a href="#concept-Use">Section Use</a>): use is the event by which a file is read by a process execution. To distinguish the various entities used by a given process execution, a role (construct described in <a href="#concept-Role">Section Role</a>) is introduced. Illustrations of such roles are in and fileIn.
<pre>
-uses(pe1,e1,in)
-uses(pe3,e2,in)
-uses(pe2,e2,in)
-uses(pe4,e3,in)
-uses(pe5,e3,fileIn)
+used(pe1,e1,in)
+used(pe3,e2,in)
+used(pe2,e2,in)
+used(pe4,e3,in)
+used(pe5,e3,fileIn)
</pre>
</p>
<p>
-isComplementOf: (this relation is described in <a href="#concept-IVP-of">Section isComplementOf</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="#concept-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.
<pre>
-isComplementOf(e1,e0)
-isComplementOf(e2,e0)
-isComplementOf(e3,e0)
-isComplementOf(e6,e3)
+wasComplementOf(e1,e0)
+wasComplementOf(e2,e0)
+wasComplementOf(e3,e0)
+wasComplementOf(e6,e3)
</pre>
</p>
@@ -280,11 +280,11 @@
<p>
Control (construct described in <a href="#concept-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by a role (construct described in <a href="#concept-Role">Section Role</a>). Illustrations of such roles are creator, author and communicator.
<pre>
-isControlledBy(pe0,a1, creator)
-isControlledBy(pe1,a2, author)
-isControlledBy(pe2,a3, communicator)
-isControlledBy(pe3,a4, author)
-isControlledBy(pe4,a5, communicator)
+wasControlledBy(pe0,a1, creator)
+wasControlledBy(pe1,a2, author)
+wasControlledBy(pe2,a3, communicator)
+wasControlledBy(pe3,a4, author)
+wasControlledBy(pe4,a5, communicator)
</pre>
</p>
</section>
@@ -484,7 +484,7 @@
-<p>A Generation assertion, noted <b>isGeneratedBy(e,pe,r,t)</b>:
+<p>A Generation assertion, noted <b>wasGeneratedBy(e,pe,r,t)</b>:
<ul>
<li> refers to an entity <b>e</b>, which represents the characterized thing that is created;
<li> refers to a process execution <b>pe</b>;
@@ -495,7 +495,7 @@
<p>
<pre class="example">
-isGeneratedBy(e2,pe1,out)
+wasGeneratedBy(e2,pe1,out)
</pre>
</p>
@@ -505,8 +505,8 @@
</p>
<div class='constraint'><a name="PIL:0002">Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>,
-if the assertion <b>isGeneratedBy(e,pe,r)</b>
-or <b>isGeneratedBy(e,pe,r,t)</b> holds, the values of <em>some</em> of <b>e</b>'s
+if the assertion <b>wasGeneratedBy(e,pe,r)</b>
+or <b>wasGeneratedBy(e,pe,r,t)</b> holds, the values of <em>some</em> of <b>e</b>'s
attributes are determined by the activity denoted by <b>pe</b> and the
entities used by <b>pe</b>.
Only some (possibly none) of the attributes values may be determined
@@ -514,7 +514,7 @@
asserted.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0002">PIL:0002</a>]
</div>
-<div class='constraint'><a name="PIL:0003">Given an assertion <b>isGeneratedBy(x,pe,r)</b> or <b>isGeneratedBy(x,pe,r,t)</b>, one can
+<div class='constraint'><a name="PIL:0003">Given an assertion <b>wasGeneratedBy(x,pe,r)</b> or <b>wasGeneratedBy(x,pe,r,t)</b>, one can
infer that the generation of the thing denoted by <b>x</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0003">PIL:0003</a>]
</div>
@@ -540,7 +540,7 @@
<p><dfn id="dfn-Use">Use</dfn> represents the consumption of a characterized thing by an activity.</p>
-<p>A Use assertion, <b>uses(pe,e,r,t)</b>:
+<p>A Use assertion, <b>used(pe,e,r,t)</b>:
<ul>
<li> refers to a process execution <b>pe</b>;
<li> refers to an entity <b>e</b>, representing the characterized thing that is used;
@@ -551,7 +551,7 @@
<p>
<pre class="example">
-uses(pe1,e1,in,t)
+used(pe1,e1,in,t)
</pre>
</p>
@@ -566,7 +566,7 @@
<div class='constraint'><a name="PIL:0005">
Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
- assertion <b>uses(pe,e,r)</b> or <b>uses(pe,e,r,t)</b> holds,
+ assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds,
the existence of the value of an attribute of <b>e</b>' is a
pre-condition for the activity denoted by <b>pe</b> to terminate.</a>
[<a href="../ontology/ProvenanceFormalModel.html#PIL:0005">PIL:0005</a>]</div>
@@ -574,7 +574,7 @@
<div class='constraint'><a name="PIL:0006">Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
- assertion <b>uses(pe,e,r)</b> or <b>uses(pe,e,r,t)</b> holds, one can
+ assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
infer that the use of the thing denoted by <b>e</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
can infer that the generation of the thing denoted by <b>e</b> always precedes
@@ -606,7 +606,7 @@
<p>A process execution linked derivation, which, by definition of derivation, expresses that some characterized thing is transformed from, created from, or affected by another characterized thing, entails a process execution that transforms, creates or affects this characterized thing.</pe>
-<p>In its full form, a process-execution linked derivation assertion, noted <b>isDerivedFrom(e2,e1,pe,r2,r1)</b>:
+<p>In its full form, a process-execution linked derivation assertion, noted <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>:
<ul>
<li> refers to an entity <b>e2</b>, denoting the used characterized thing;
<li> refers to an entity <b>e1</b>, denoting the generated characterized thing;
@@ -625,13 +625,13 @@
</p>
<div class="inference">
-<a name="PIL:0010">If <b>isDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then
- <b>isGeneratedBy(e2,pe,r2)</b> and <b>uses(pe,e1,r1)</b> also
+<a name="PIL:0010">If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then
+ <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also
hold. </a> [<a href=""../ontology/ProvenanceFormalModel.html#PIL:0010">PIL:0010</a>]
</div>
-<p>For convenience, PIL allows for a compact, process-execution linked derivation assertion, written <b>isDerivedFrom(e2,e1)</b>, which:
+<p>For convenience, PIL allows for a compact, process-execution linked derivation assertion, written <b>wasDerivedFrom(e2,e1)</b>, which:
<ul>
<li> refers to an entity <b>e2</b>, denoting the generated characterized thing;
<li> refers to an entity <b>e1</b>, denoting the used characterized thing.
@@ -643,9 +643,9 @@
This is formalized by the following inference rule, referred to as <em>process execution introduction</em>:<br/>
<div class='inference'>
<a name="PIL:0009">
-If <b>isDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
+If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
such that:
- <b>isGeneratedBy(e2,pe,r2)</b> and <b>uses(pe,e1,r1)</b>. [<a href="../ontology/ProvenanceFormalModel.html#PIL:0009">PIL:0009</a>]
+ <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>. [<a href="../ontology/ProvenanceFormalModel.html#PIL:0009">PIL:0009</a>]
</div></p>
@@ -654,8 +654,8 @@
<p>If <b>e2</b> is derived from <b>e1</b>, then
this means that the thing represented by <b>e1</b> has an influence on the thing represented by <b>e2</b>, which is captured by a dependency between their attribute values; it also implies temporal ordering. These are specified as follows:</p>
-<div class='constraint'><a name="PIL:0007">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>isDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>isDerivedFrom(e2,e1)</b> holds, if and only if:
+<div class='constraint'><a name="PIL:0007">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
the values of some attributes
of <b>e2</b> are partly or fully determined by the values of some
attributes of <b>e1</b>.</a> [<a
@@ -665,8 +665,8 @@
-<div class='constraint'><a name="PIL:0008">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>isDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>isDerivedFrom(e2,e1)</b> holds, then
+<div class='constraint'><a name="PIL:0008">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> holds, then
the use
of characterized thing denoted by <b>e1</b> precedes the generation of
the characterized thing denoted by <b>e2</b>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0008">PIL:0008</a>]
@@ -676,11 +676,11 @@
<p>
Note that inferring derivation from use and generation does not hold
-in general. Indeed, when a generation <b>isGeneratedBy(e2,pe,r2)</b>
-precedes <b>uses(pe,e1,r1)</b>, for
+in general. Indeed, when a generation <b>wasGeneratedBy(e2,pe,r2)</b>
+precedes <b>used(pe,e1,r1)</b>, for
some <b>e1</b>, <b>e2</b>, <b>r1</b>, <b>r2</b>, and <b>pe</b>, one
-cannot infer derivation <b>isDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>isDerivedFrom(e2,e1)</b> since the values of attributes
+cannot infer derivation <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> since the values of attributes
of <b>e2</b> cannot possibly be determined by the values of attributes
of <b>e1</b>, given the creation of <b>e2</b> precedes the use
of <b>e1</b>.
@@ -688,26 +688,26 @@
<p>
<pre class="example">
-isDerivedFrom(e5,e3)
+wasDerivedFrom(e5,e3)
</pre>
</p>
<p>A further inference is permitted from the compact version of derivation:
<div class='inference'>
<a name="PIL:0011">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
-if <b>isDerivedFrom(e2,e1)</b> and <b>isGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
-such that <b>uses(pe,e1,r1)</b> also holds.</a>
+if <b>wasDerivedFrom(e2,e1)</b> and <b>wasGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
+such that <b>used(pe,e1,r1)</b> also holds.</a>
[<a href="../ontology/ProvenanceFormalModel.html#PIL:0011">PIL:0011</a>]
</div>
-This inference is justified by the fact that <b>e2</b> is generated by at most one process execution. Hence, this process execution is also the one that uses <b>e1</b>.
+This inference is justified by the fact that <b>e2</b> is generated by at most one process execution. Hence, this process execution is also the one that used <b>e1</b>.
</p>
<div class='note'>There is a suggestion by Simon that this notion of derivation is only meaningful in the context of an account. <a href="http://lists.w3.org/Archives/Public/public-prov-wg/2011Aug/0101.html">See email</a>. It is not clear it is the case anymore. However, the inference above is only meaning full if unicity of generation hold.</div>
<p>We note that the "symmetric" inference, does not hold.
-From <b>isDerivedFrom(e2,e1)</b> and <b>uses(pe,e1)</b>, one cannot
-derive <b>isGeneratedBy(e2,pe,r2)</b> because <b>e1</b> may be used by
+From <b>wasDerivedFrom(e2,e1)</b> and <b>used(pe,e1)</b>, one cannot
+derive <b>wasGeneratedBy(e2,pe,r2)</b> because <b>e1</b> may be used by
many process execution, not all of them generating <b>e2</b>.</p>
@@ -722,20 +722,20 @@
<p>A process execution independent derivation states the existence of a derivation, by any means whether direct or not, and regardless of any process executions. </p>
-<p>A process execution independent derivation, written <b>isEventuallyDerivedFrom (e2, e1)</b>,
+<p>A process execution independent derivation, written <b>wasEventuallyDerivedFrom (e2, e1)</b>,
<ul>
<li> refers to an entity <b>e2</b>, denoting the used characterized thing;
<li> refers to an entity <b>e1</b>, denoting the generated characterized thing;
</ul>
-<p>If <b>e2</b> is derived (isEventuallyDerivedFrom) from <b>e1</b>, then
+<p>If <b>e2</b> is derived (wasEventuallyDerivedFrom) from <b>e1</b>, then
this means that the thing represented by <b>e1</b> has an influence on the thing represented by <b>e2</b>,
which at the minimum implies temporal ordering, specified as follows:</p>
<div class='constraint'>
<p>
- <a name="PIL:0012">Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>isEventuallyDerivedFrom(e2,e1)</b>
+ <a name="PIL:0012">Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>wasEventuallyDerivedFrom(e2,e1)</b>
holds, then:
generation of the characterized thing denoted by <b>e1</b> precedes the generation of
the characterized thing denoted by <b>e2</b>.</a>
@@ -747,10 +747,10 @@
and <b>e2</b>, as opposed to process execution linked derivation,
which implied temporal ordering between the use of <b>e1</b> and
generation of <b>e2</b>. Indeed, in the case of
-isEventuallyDerivedFrom, nothing is known about the use of <b>e1</b>,
+wasEventuallyDerivedFrom, nothing is known about the use of <b>e1</b>,
since there is no associated process execution.</p>
-<div class='note'>Should we link isEventuallyDerivedFrom to attributes as we did for isDerivedFrom? If so, this type of inference should be presented upfront, for both.</div>
+<div class='note'>Should we link wasEventuallyDerivedFrom to attributes as we did for wasDerivedFrom? If so, this type of inference should be presented upfront, for both.</div>
@@ -763,20 +763,20 @@
<p>
-If <b>isDerivedFrom(e2,e1)</b> holds because attribute <b>a2.1</b> of <b>e2</b> is determined by attribute <b>a1.1</b> of <b>e1</b>,
-and if <b>isDerivedFrom(e3,e2)</b> holds because attribute <b>a3.1</b>of <b>e3</b> is determined by attribute <b>a2.2</b> of <b>e1</b>, it is not necessarily the case that an attribute of <b>e3</b> is determined by an attribute of <b>e1</b>, so, an asserter may not be able to assert <b>isDerivedFrom(e3,e1)</b>. Hence, constraints on attributes invalidate transitivity in the general case.
+If <b>wasDerivedFrom(e2,e1)</b> holds because attribute <b>a2.1</b> of <b>e2</b> is determined by attribute <b>a1.1</b> of <b>e1</b>,
+and if <b>wasDerivedFrom(e3,e2)</b> holds because attribute <b>a3.1</b>of <b>e3</b> is determined by attribute <b>a2.2</b> of <b>e1</b>, it is not necessarily the case that an attribute of <b>e3</b> is determined by an attribute of <b>e1</b>, so, an asserter may not be able to assert <b>wasDerivedFrom(e3,e1)</b>. Hence, constraints on attributes invalidate transitivity in the general case.
</p>
<p>However, there is sense that <b>e3</b> still depends on <b>e1</b>, since <b>e3</b> could not be generated without <b>e1</b> existing. Hence, we introduce a weaker notion of derivation, which is transitive.</p>
-<p>The relationship <dfn id="dfn-dependsOn">dependsOn</dfn> is defined as follows:
+<p>The relationship <dfn id="dfn-dependedOn">dependedOn</dfn> is defined as follows:
<ul>
-<li>If <b>isDerivedFrom(e2,e1)</b> or <b>isDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>dependsOn(e2,e1)</b>.</li>
-<li>If <b>isEventuallyDerivedFrom(e2,e1)</b> holds, then <b>dependsOn(e2,e1)</b>.</li>
-<li>If <b>dependsOn(e3,e2)</b> and <b>dependsOn(e2,e1)</b> hold, then <b>dependsOn(e3,e1)</b>.</li>
+<li>If <b>wasDerivedFrom(e2,e1)</b> or <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>dependedOn(e2,e1)</b>.</li>
+<li>If <b>wasEventuallyDerivedFrom(e2,e1)</b> holds, then <b>dependedOn(e2,e1)</b>.</li>
+<li>If <b>dependedOn(e3,e2)</b> and <b>dependedOn(e2,e1)</b> hold, then <b>dependedOn(e3,e1)</b>.</li>
</ul>
-<p>We note that <b>dependsOn</b> cannot be asserted but can only be inferred.</p>
+<p>We note that <b>dependedOn</b> cannot be asserted but can only be inferred.</p>
</section>
@@ -819,7 +819,7 @@
entity(alice, [Employee="1234"]) and agent(alice)
-entity(david) and isControlledBy(pe,david)
+entity(david) and wasControlledBy(pe,david)
</pre>
</p>
@@ -833,7 +833,7 @@
<p> <dfn id="dfn-Control">Control</dfn> represents the involvement of an agent or an entity in a process execution; a role qualifies this involvement.</p>
-<p>A Control assertion, noted <b>isControlledBy(pe,ag,r)</b>:
+<p>A Control assertion, noted <b>wasControlledBy(pe,ag,r)</b>:
<ul>
<li> refers to a process execution <b>pe</b>;
<li> refers to an agent or an entity <b>ag</b>;
@@ -843,16 +843,16 @@
<p>
<pre class="example">
-isControlledBy(pe3,david,"author")
+wasControlledBy(pe3,david,"author")
</pre>
</p>
</section>
-<section id="concept-IVP-of">
+<section id="concept-complement-of">
-<h3>Is Complement Of</h3>
+<h3>was Complement Of</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/>
@@ -875,7 +875,7 @@
-->
</p>
-<p>An isComplementOf assertion is denoted <b>isComplementOf(B,A)</b>, where A and B are two entities.
+<p>An wasComplementOf assertion is denoted <b>wasComplementOf(B,A)</b>, where A and B are two entities.
<p>
<pre class="example">
@@ -888,20 +888,20 @@
entity(rs_m2,[membership: "300", year: "1945"])
entity(rs_m3,[membership: "270", year: "2010"])
-isComplementOf(rs_m3, rs_l2)
-isComplementOf(rs_m2, rs_l1)
-isComplementOf(rs_m2, rs_l2)
-isComplementOf(rs_m1, rs_l1)
+wasComplementOf(rs_m3, rs_l2)
+wasComplementOf(rs_m2, rs_l1)
+wasComplementOf(rs_m2, rs_l2)
+wasComplementOf(rs_m1, rs_l1)
-isComplementOf(rs_l1, rs)
-isComplementOf(rs_l2, rs)
+wasComplementOf(rs_l1, rs)
+wasComplementOf(rs_l2, rs)
</pre>
</p>
<div class='constraint'>
<p>
- <a name="PIL:0013">An assertion "isComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
+ <a name="PIL:0013">An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
<ol>
<li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B must be consistent with that mapping</em> </li>
<li>B has some attribute that A does not have
@@ -995,7 +995,7 @@
<b>unspecified0</b>, <b>unspecified1</b>, <b>unspecified2</b>, ....
<pre class="example">
- uses(pe,e) expands to uses(pe,e,unspecified1)
+ used(pe,e) expands to used(pe,e,unspecified1)
</pre>
where unspecified1 is an unspecified role.
</p>
@@ -1064,7 +1064,7 @@
<p> <dfn id="dfn-Revision">Revision</dfn> represents the creation of a characterized thing considered to be a variant of another. Deciding whether something is made available as a revision of something else usually involves an agent who is responsible for declaring that the former is variant of the latter. </p>
-<p>An assertion isRevisionOf, noted <b>isRevisionOf(e2,e1,ag)</b>:
+<p>An assertion wasRevisionOf, noted <b>wasRevisionOf(e2,e1,ag)</b>:
<ul>
<li> refers to an entity <b>e2</b>, denoting a newer version of a thing;
<li> refers to an entity <b>e1</b>, denoting a older version of a thing;
@@ -1074,21 +1074,21 @@
<p>
-From an assertion <b>isRevisionOf(new,old,ag)</b>, one can infer that:
+From an assertion <b>wasRevisionOf(new,old,ag)</b>, one can infer that:
<ul>
<li> The characterized thing denoted by <b>new</b> is derived from the characterized thing denoted by <b>old</b>
<li> There exists an entity <b>X</b>, such that:
<ul>
-<li> <b>new</b> isComplementOf <b>X</b>;
-<li> <b>old</b> isComplementOf <b>X</b>;
+<li> <b>new</b> wasComplementOf <b>X</b>;
+<li> <b>old</b> wasComplementOf <b>X</b>;
<li> <b>X</b> MAY have been asserted.
</ul>
</ul>
</p>
-<p><b>isRevisionOf</b> is a strict sub-relation
- of <b>isDerivedFrom</b> since two entities <b>e2</b> and <b>e1</b>
- may satisfy <b>isDerivedFrom(e2,e1)</b> without being a variant of
+<p><b>wasRevisionOf</b> is a strict sub-relation
+ of <b>wasDerivedFrom</b> since two entities <b>e2</b> and <b>e1</b>
+ may satisfy <b>wasDerivedFrom(e2,e1)</b> without being a variant of
each other.
</p>
@@ -1114,9 +1114,9 @@
<a name="PIL:0014">
Given a process execution <b>pe</b> and entity <b>e</b>, <b>hasParticipant(pe,e)</b> holds if and only if:
<ul>
-<li> <b>uses(pe,e)</b> holds, or</li>
-<li> <b>isControlledBy(pe,e)</b> holds, or</li>
-<li> <b>isComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and
+<li> <b>used(pe,e)</b> holds, or</li>
+<li> <b>wasControlledBy(pe,e)</b> holds, or</li>
+<li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and
<b>hasParticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
</ul>
</a> [<a
@@ -1196,7 +1196,7 @@
Specifically, the following relations are envisioned (to be made precise later):
<ul>
- <li> current containment: <strong>isMemberOf(<entity>, <collection>, <position>)</strong>
+ <li> current containment: <strong>wasMemberOf(<entity>, <collection>, <position>)</strong>
<li> former containment: <strong>wasRemovedFRom(<entity>, <collection>, <position>)</strong>
<li> new containment: <strong>wasAddedTo(<entity>, <collection>, <position>)</strong>
</ul>
@@ -1217,7 +1217,7 @@
Quotation represents the repeating or copying of some part of a characterized thing.
-<p> An assertion isQuoteOf, noted <b> isQuoteOf(e2,e1,ag,ag2)</b>:
+<p> An assertion wasQuoteOf, noted <b> wasQuoteOf(e2,e1,ag,ag2)</b>:
<ul>
<li>refers to an entity <b>e2</b>, denoting the quote;
<li>refers to an entity <b>e1</b>, denoting the entity being quoted;
@@ -1226,7 +1226,7 @@
</ul>
</p>
<p>
-<b>isQuoteOf</b> is a sub-relation of <b>isRevisionOf</b>
+<b>wasQuoteOf</b> is a sub-relation of <b>wasRevisionOf</b>
</p>
</section>
@@ -1236,14 +1236,14 @@
Attribution represents that a characterized thing is ascribed to an agent.
-<p> An assertion isAttributedTo, noted <b> isAttributedTo(e1,ag)</b>:
+<p> An assertion wasAttributedTo, noted <b> wasAttributedTo(e1,ag)</b>:
<ul>
<li>refers to an entity <b>e2</b>, denoting the entity;
<li>refers to an agent who the entity is attributed to <b>ag</b>.
</ul>
</p>
<p>
-<b>isQuoteOf</b> is a strict sub-relation of <b>isEventuallyDerivedFrom</b>
+<b>wasQuoteOf</b> is a strict sub-relation of <b>wasEventuallyDerivedFrom</b>
</p>
@@ -1253,14 +1253,14 @@
<h3>Summary</h3>
Represents a characterized thing that is a synopsis or abbreviation of another entity.
-<p> An assertion isSummaryOf, noted <b> isSummaryOf(e2,e1)</b>:
+<p> An assertion wasSummaryOf, noted <b> wasSummaryOf(e2,e1)</b>:
<ul>
<li>refers to an entity <b>e2</b>, denoting the summary;
<li>refers to an entity <b>e1</b>, denoting the entity being summarized.
</ul>
</p>
<p>
-<b>isSummaryOf</b> is a strict sub-relation of <b>isEventuallyDerivedFrom</b>
+<b>wasSummaryOf</b> is a strict sub-relation of <b>wasEventuallyDerivedFrom</b>
</p>
@@ -1278,7 +1278,7 @@
</ul>
</p>
<p>
-<b>hasOriginalSource</b> is a strict sub-relation of <b>isEventuallyDerivedFrom</b>
+<b>hasOriginalSource</b> is a strict sub-relation of <b>wasEventuallyDerivedFrom</b>
</p>
@@ -1316,7 +1316,7 @@
<section id='PASN-convention'>
<h3>Provenance Abstract Syntax Notation Conventions</h3>
<ul>
-<li>Language constructs are represented as <b>name(arg0, arg1, ...)</b>, where the name of the construct occurs first, and is followed by its arguments.</li>
+<li>Constructs are expressed as <b>name(arg0, arg1, ...)</b>, 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>
<li> Preliminary BNF grammar for the Provenance Abstract Syntax Notation