--- a/model/ProvenanceModel.html Mon Nov 07 10:34:25 2011 +0000
+++ b/model/ProvenanceModel.html Mon Nov 07 10:54:01 2011 +0000
@@ -137,7 +137,7 @@
<section id="abstract">
<p>
PROV-DM is a core data model for provenance for building
-representations of the entities, people and processes involved in
+representations of the entities, people and activities involved in
producing a piece of data or thing in the world. PROV-DM is
domain-agnotisc, but with well-defined extensibility points allowing
further domain-specific and application-specific extensions to be
@@ -161,7 +161,7 @@
<p>
The term 'provenance' refers to the sources of information, such
-as people, entities, and processes, involved in producing,
+as people, entities, and activities, involved in producing,
influencing, or delivering a piece of data or a thing in the world.
In particular, the provenance of information is crucial in deciding
whether information is to be trusted, how it should be integrated with
@@ -397,10 +397,10 @@
<li>An <strong>Entity Record</strong> (noted <samp>entity</samp> in the diagram, to reflect the term used in the ASN) is a representation of an <em>entity</em>. The EntityRecord may specify a set of <strong>attributes</strong>. The
<strong>wasComplementOf</strong> relationship is used to denote that two <samp>entities</samp> <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.</li>
- <li>A<strong>Process Execution Record </strong>(noted <samp>processExecution</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an <samp>entity</samp> in a <samp>processExecution</samp>. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
-Note that multiple <samp>processExecution</samp>s may <em>use</em> the same <samp>entity</samp>, and each may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.</li>
+ <li>An <strong>Activity Record </strong>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an <samp>entity</samp> in a <samp>activity</samp>. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
+Note that multiple <samp>activity</samp>s may <em>use</em> the same <samp>entity</samp>, and each may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.</li>
- <li>An <strong>Agent Record</strong> represent a particular <samp>entity</samp> that can be associated to activities, meaning it is capable of controlling <samp>processExecutions</samp>.
+ <li>An <strong>Agent Record</strong> represent a particular <samp>entity</samp> that can be associated to activities, meaning it is capable of controlling <samp>activitys</samp>.
Agents have a rather generic connotation: their association with an activity, represented by the <strong>controlledBy</strong> relationship, can take up various meanings (attribution, responsibility, supervision, management, etc.), which are not individually specified in the model.</li>
</ul>
@@ -507,14 +507,14 @@
<p>
-Process Execution Records (described in <a href="#record-ProcessExecution">Section Process Execution</a>) represent activities in the scenario.</p>
+Activity Records (described in <a href="#record-Activity">Section Activity</a>) represent activities in the scenario.</p>
<pre>
-processExecution(pe0,create-file,t,,[])
-processExecution(pe1,add-crime-in-london,t+1,,[])
-processExecution(pe2,email,t+2,,[])
-processExecution(pe3,edit-London-New-York,t+3,,[])
-processExecution(pe4,email,t+4,,[])
-processExecution(pe5,spellcheck,,,[])
+activity(pe0,create-file,t,,[])
+activity(pe1,add-crime-in-london,t+1,,[])
+activity(pe2,email,t+2,,[])
+activity(pe3,edit-London-New-York,t+3,,[])
+activity(pe4,email,t+4,,[])
+activity(pe5,spellcheck,,,[])
</pre>
@@ -534,7 +534,7 @@
<p>
-Records of type <strong>UsedRecords</strong> (described in <a href="#record-Use">Section Use</a>) represent the event by which a file is read by a process execution.
+Records of type <strong>UsedRecords</strong> (described in <a href="#record-Use">Section Use</a>) represent the event by which a file is read by an activity.
Likewise, to describe the modalities according to which the various entities are used by activities, a qualifier (construct described in <a href="#record-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 class="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>. </p>
@@ -548,7 +548,7 @@
<p>
-Derivation Records (described in <a href="#record-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.</p>
+Derivation Records (described in <a href="#record-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 activity underpinning the derivation, and relevant qualifiers qualifying the use and generation of entities.</p>
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -591,7 +591,7 @@
<p>
-Control Records (described in <a href="#record-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 qualifier (construct described in <a href="#record-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agent, as creator, author and communicator.</p>
+Control Records (described in <a href="#record-Control">Section Control</a>): the influence of an agent over an activity is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#record-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agent, as creator, author and communicator.</p>
<pre>
wasControlledBy(pe0,a1, qualifier(role="creator"))
wasControlledBy(pe1,a2, qualifier(role="author"))
@@ -649,7 +649,7 @@
<br/>
<span class="nonterminal">elementRecord</span> :=
<span class="nonterminal">entityRecord</span>
-| <span class="nonterminal">processExecutionRecord</span>
+| <span class="nonterminal">activityRecord</span>
| <span class="nonterminal">agentRecord</span>
| <span class="nonterminal">annotationRecord</span> <br/>
<!-- -->
@@ -712,7 +712,7 @@
-<p>An instance of an entity record, noted <span class="name">entity(id, [ attr1=val1, ...])</span> in PROV-ASN:</p>
+<p>An entity record, noted <span class="name">entity(id, [ attr1=val1, ...])</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span> identifying an entity;</li>
<li> contains a set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing this entity's situation in the world.</li>
@@ -720,7 +720,7 @@
<p>
-The assertion of an instance of an entity record, <span class="name">entity(id, [ attr1=val1, ...])</span>, states, from a given asserter's viewpoint, the existence of an entity, whose situation in the world is represented by the attribute-value pairs, which remain unchanged during a characterization interval, i.e. a continuous interval between two events in the world.
+The assertion of an entity record, <span class="name">entity(id, [ attr1=val1, ...])</span>, states, from a given asserter's viewpoint, the existence of an entity, whose situation in the world is represented by the attribute-value pairs, which remain unchanged during a characterization interval, i.e. a continuous interval between two events in the world.
</p>
@@ -747,8 +747,7 @@
its attributes are given a value as part of that assertion.
</li>
-<li>Activities are not represented by entities, but instead by process
-executions, as explained below.</li>
+<li>Activities are not represented by entity records, but instead by actity records, as explained below.</li>
</ul>
@@ -762,25 +761,25 @@
<div class='note'>The characterization interval of an entity record is currently implicit. Making it explicit would allow us to define wasComplementOf more precisely. It would also allow us to address
<a href="http://www.w3.org/2011/prov/track/issues/108">ISSUE-108</a>.
-Beginning and end of characterization interval could be expressed by attributes (similarly to process executions). </div>
+Beginning and end of characterization interval could be expressed by attributes (similarly to activities). </div>
</section>
- <section id="record-ProcessExecution">
+ <section id="record-Activity">
-<h3>Process Execution Record</h3>
-<p>In PROV-DM, a <dfn id="dfn-ProcessExecution">process execution record</dfn> is a representation of an identifiable activity, which performs a piece of work.</p>
-
-<p>In PROV-ASN, a process execution record's text matches the <span class='nonterminal'>processExecutionRecord</span> production of the grammar defined in this specification document.</p>
+<h3>Activity Record</h3>
+<p>In PROV-DM, an <dfn id="dfn-activity">activity record</dfn> is a representation of an identifiable activity, which performs a piece of work.</p>
+
+<p>In PROV-ASN, an activity record's text matches the <span class='nonterminal'>activityRecord</span> production of the grammar defined in this specification document.</p>
<div class='grammar'>
-<span class="nonterminal">processExecutionRecord</span> :=
-<span class="name">processExecution</span>
+<span class="nonterminal">activityRecord</span> :=
+<span class="name">activity</span>
<span class="name">(</span>
<span class="nonterminal">identifier</span>
[ <span class="name">,</span>
@@ -795,11 +794,11 @@
<span class="nonterminal">other-attribute-values</span> := <span class="nonterminal">attribute-values</span>
</div>
-<p>The activity that a process execution record 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 record 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 interpretation of attribute in the context of a process execution record is the same as the interpretation of attribute for entity record: a process execution record'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 record, written <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
+<p>An activity, represented by an activity record, is delimited by its start and its end events; hence, it occurs over an interval delimited by two events. However, an activity record 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 interpretation of attribute in the context of an activity record is the same as the interpretation of attribute for entity record: an activity record'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 activity record, written <span class="name">activity(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span>;</li>
<li> MAY contain a <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific description of the activity;</li>
@@ -810,19 +809,19 @@
<p>
-The following process execution assertion</p>
+The following activity assertion</p>
<pre class="example">
-processExecution(pe1,add-crime-in-london,t+1,t+1+epsilon,[host="server.example.org",type="app:edit"])
+activity(pe1,add-crime-in-london,t+1,t+1+epsilon,[host="server.example.org",type="app:edit"])
</pre>
<p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">t+1</span>, and end time <span class="name">t+1+epsilon</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span> (declared in some namespace with prefix <span class="name">app</span>). The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity. The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for subtyping to be expressed.
</p>
-<p>The mere existence of a process execution assertion entails some event ordering in the world, since the start event precedes the end event. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
-
-<div class='constraint' id='start-precedes-end'> From a process execution record, one can infer that the
+<p>The mere existence of an activity assertion entails some event ordering in the world, since the start event precedes the end event. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
+
+<div class='constraint' id='start-precedes-end'> From an activity record, one can infer that the
start event precedes the end event of the represented activity.</div>
-<p>A process execution record is not an entity record.
+<p>an activity record is not an entity record.
Indeed, an entity record represents an entity that exists in full at
any point in its characterization interval, persists during this
interval, and preserves the characteristics that makes it
@@ -860,7 +859,7 @@
</p>
<p>For an entity, one can assert an agent record or alternatively, one can infer an agent record
-by involvement in an activity represented by a process execution record. </p>
+by involvement in an activity represented by an activity record. </p>
@@ -872,7 +871,7 @@
entity(e2) and wasControlledBy(pe,e2,qualifier(role="author"))
</pre>
-<p>the entity record identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent record, and this assertion holds irrespective of process executions it may be involved in. On the other hand, from the entity record identified by <span class="name">e2</span>, one can infer an agent record, as per the following inference.
+<p>the entity record identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent record, and this assertion holds irrespective of activities it may be involved in. On the other hand, from the entity record identified by <span class="name">e2</span>, one can infer an agent record, as per the following inference.
</p>
<div class='constraint' id='control-agent'>
@@ -931,7 +930,7 @@
</p>
<p>
-Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity records and process execution records). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity record) or the activity duration (for process execution records). 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 an entity or activity, for the purpose of provenance.
+Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity records and activity records). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity record) or the activity duration (for activity records). 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 an entity or activity, for the purpose of provenance.
</p>
@@ -971,10 +970,10 @@
-<p>An instance of a generation record, written <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
+<p>A generation record, written <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e</span> identifying an entity record that represents the entity that is created; </li>
-<li> contain an identifier <span class="name">pe</span> identifying a process execution record that represents the activity that creates the entity;</li>
+<li> contain an identifier <span class="name">pe</span> identifying an activity record that represents the activity that creates the entity;</li>
<li> contains a <a href="#record-qualifier">generationQualifier</a> <span class="name">q</span> that describes the modalities of generation of this entity by this activity;</li>
@@ -989,16 +988,16 @@
wasGeneratedBy(e1,pe1,qualifier(port="p1", order=1),t1)
wasGeneratedBy(e2,pe1,qualifier(port="p1", order=2),t2)
</pre>
-<p>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 entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by a process execution record identified by <span class="name">pe1</span>.
+<p>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 entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by an activity record 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 <span class="name">port</span> and <span class="name">order</span> in these records are application specific.
</p>
<p>A given entity record can be referred to in a single generation record in the scope of a given <a href="#record-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.
-
-<div class='constraint' id='generation-unicity'>Given an entity record denoted by <span class="name">e</span>, two process execution records denoted by <span class="name">pe1</span> and <span class="name">pe2</span>, and two qualifiers <span class="name">q1</span> and <span class="name">q2</span>,
+If two activities sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities. Alternatively, for two activities 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 activity. This unicity constraint is formalized as follows.
+
+<div class='constraint' id='generation-unicity'>Given an entity record denoted by <span class="name">e</span>, two activity records denoted by <span class="name">pe1</span> and <span class="name">pe2</span>, and two qualifiers <span class="name">q1</span> and <span class="name">q2</span>,
<span class='conditional'>if</span> the records <span class="name">wasGeneratedBy(e,pe1,q1)</span> and <span class="name">wasGeneratedBy(e,pe2,q2)</span> exist in the scope of a given account,
<span class='conditional'>then</span> <span class="name">pe1</span>=<span class="name">pe2</span> and <span class="name">q1</span>=<span class="name">q2</span>.
</div>
@@ -1007,10 +1006,10 @@
A generation event SHOULD have some visibility on the attributes of the generated entity, as expressed by the following constraint.
-<div class='constraint' id='generation-affects-attributes'>Given an identifier <span class="name">pe</span> for a process execution record, an identifier <span class="name">e</span> for an entity record, qualifier <span class="name">q</span>, and optional time <span class="name">t</span>,
+<div class='constraint' id='generation-affects-attributes'>Given an identifier <span class="name">pe</span> for an activity record, an identifier <span class="name">e</span> for an entity record, qualifier <span class="name">q</span>, and optional time <span class="name">t</span>,
<span class='conditional'>if</span> the assertion <span class="name">wasGeneratedBy(e,pe,p)</span>
or <span class="name">wasGeneratedBy(e,pe,q,t)</span> holds, <span class='conditional'>then</span> the values of <em>some</em> of <span class="name">e</span>'s
-attributes are determined by the activity represented by process execution record identified by <span class="name">pe</span> and the
+attributes are determined by the activity represented by activity record identified by <span class="name">pe</span> and the
entity records 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 entity records may have been
@@ -1059,9 +1058,9 @@
</div>
-<p>An instance of a use record, written <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
+<p>A use record, written <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
<ul>
-<li> refers to a process execution record identified by <span class="name">pe</span>, which represents the consuming activity;</li>
+<li> refers to an activity record identified by <span class="name">pe</span>, which represents the consuming activity;</li>
<li> refers to an entity record identified by <span class="name">e</span>, which represents the entity that is consumed;</li>
<li> contains a <a href="#record-qualifier">useQualifier</a> <span class="name">q</span>, which describes the modalities of use of this entity by this activity;</li>
<li> MAY contain a "use time" <span class="name">t</span>, the time at which the entity was used.</li>
@@ -1073,11 +1072,11 @@
used(pe1,e1,qualifier(parameter="p1"),t1)
used(pe1,e2,qualifier(parameter="p2"),t2)
</pre>
-<p>state that the activity, represented by the process execution record identified by <span class="name">pe1</span>, consumed two entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these records is application specific.</p>
+<p>state that the activity, represented by the activity record identified by <span class="name">pe1</span>, consumed two entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these records is application specific.</p>
<p>A reference to a given entity record MAY appear in multiple use records that share
- a given process execution record identifier. If one wants to annotate a use edge record or if one wants to express a <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a> referring to this entity and process execution records, the qualifier occuring in this use assertion MUST be unique among the qualifiers qualifiying use records for this process execution record.
+ a given activity record identifier. If one wants to annotate a use edge record or if one wants to express a <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a> referring to this entity and activity records, the qualifier occuring in this use assertion MUST be unique among the qualifiers qualifiying use records for this activity record.
</p>
<!-- Luc, should we write a constraint for this? It's not clear the
@@ -1086,18 +1085,18 @@
<div class='constraint' id='use-attributes'>
-Given a process execution record identified by <span class="name">pe</span>, an entity record identified by <span class="name">e</span>, a qualifier <span class="name">q</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
+Given an activity record identified by <span class="name">pe</span>, an entity record identified by <span class="name">e</span>, a qualifier <span class="name">q</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
assertion <span class="name">used(pe,e,q)</span> or <span class="name">used(pe,e,q,t)</span> holds,
<span class='conditional'>then</span> the existence of an attribute-value pair in the entity record identified by <span class="name">e</span> is a
-pre-condition for the termination of the activity represented by the process execution record identified by <span class="name">pe</span>.
+pre-condition for the termination of the activity represented by the activity record identified by <span class="name">pe</span>.
</div>
-<div class='constraint' id='use-pe-ordering'>Given a process execution record identified by <span class="name">pe</span>, an entity record identified by <span class="name">e</span>, a qualifier <span class="name">q</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
+<div class='constraint' id='use-pe-ordering'>Given an activity record identified by <span class="name">pe</span>, an entity record identified by <span class="name">e</span>, a qualifier <span class="name">q</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
assertion <span class="name">used(pe,e,q)</span> or <span class="name">used(pe,e,q,t)</span> holds, <span class='conditional'>then</span>
the use of the entity represented by entity record identified by <span class="name">e</span> precedes the end
-time contained in the process execution record identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the entity denoted by entity record identified by <span class="name">e</span> always precedes
+time contained in the activity record identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the entity denoted by entity record identified by <span class="name">e</span> always precedes
its use.
</div>
@@ -1114,7 +1113,7 @@
<p>In PROV-DM, a <dfn id="dfn-Derivation">derivation record</dfn> is a representation that some entity is transformed from, created from, or affected by another entity in the world. </p>
-<p>PROV-DM offers two different forms of derivation records. The first one is tightly connected to the notion of activity (represented by a process execution record), whereas the second one is not. The first kind of assertion is particularly suitable for asserters who have an intimate knowledge of activities, is more prescriptive, but offers a more precise description of derivation, whereas the second does not put such a requirement on the asserter, and allows a less precise description of derivation to be formulated. Both records need to be asserted by asserters, since PROV-DM does not provide the means to infer them; however, from these assertions, further derivations can be inferred by transitive closure. </p>
+<p>PROV-DM offers two different forms of derivation records. The first one is tightly connected to the notion of activity (represented by an activity record), whereas the second one is not. The first kind of assertion is particularly suitable for asserters who have an intimate knowledge of activities, is more prescriptive, but offers a more precise description of derivation, whereas the second does not put such a requirement on the asserter, and allows a less precise description of derivation to be formulated. Both records need to be asserted by asserters, since PROV-DM does not provide the means to infer them; however, from these assertions, further derivations can be inferred by transitive closure. </p>
<p>In PROV-ASN, a derivation record's text matches the <span class='nonterminal'>derivationRecord</span> production of the grammar defined in this specification document.</p>
@@ -1160,15 +1159,15 @@
<section id="pe-linked-derivationRecord">
-<h4>Process Execution Linked Derivation Record</h4>
-
-<p>A process execution linked derivation record, which, by definition of a derivation record, is a representation that some entity is transformed from, created from, or affected by another entity, also entails the existence of a process execution record that represents an activity that transforms, creates or affects this entity.</p>
-
-<p>In its full form, a process-execution linked derivation record, written <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
+<h4>Activity Linked Derivation Record</h4>
+
+<p>an activity linked derivation record, which, by definition of a derivation record, is a representation that some entity is transformed from, created from, or affected by another entity, also entails the existence of an activity record that represents an activity that transforms, creates or affects this entity.</p>
+
+<p>In its full form, a activity linked derivation record, written <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
<ul>
<li> refers to an entity record identified by <span class="name">e2</span>, which is a representation of the generated entity;</li>
<li> refers to an entity record identified by <span class="name">e1</span>, which is a representation of the used entity;</li>
-<li> refers to a process execution record identified by <span class="name">pe</span>, which is a representation of the activity using and generating the above entities;</li>
+<li> refers to an activity record identified by <span class="name">pe</span>, which is a representation of the activity using and generating the above entities;</li>
<li> contains a qualifier <span class="name">q2</span>, which qualifies the generation record pertaining to <span class="name">e2</span> and <span class="name">pe</span>;</li>
<li> contains a qualifier <span class="name">q1</span>, which qualifies in the use record pertaining to <span class="name">e1</span> and <span class="name">pe</span>.</li>
</ul>
@@ -1177,7 +1176,7 @@
-<p>For convenience, PROV-DM allows for a compact, process-execution linked derivation assertion, written <span class="name">wasDerivedFrom(e2,e1)</span> in PROV-ASN, which:</p>
+<p>For convenience, PROV-DM allows for a compact, activity linked derivation assertion, written <span class="name">wasDerivedFrom(e2,e1)</span> in PROV-ASN, which:</p>
<ul>
<li> refers to an entity record identified by <span class="name">e2</span>, which is a representation of the generated entity;
<li> refers to an entity record identified by <span class="name">e1</span>, which is a represenation of the used entity.
@@ -1191,25 +1190,25 @@
wasDerivedFrom(e3,e2)
</pre>
<p>
-state the existence of process-linked derivations;
-the first expresses that the activity represented by the process execution <span class="name">pe4</span>, by
+state the existence of activity-linked derivations;
+the first expresses that the activity represented by the activity <span class="name">pe4</span>, by
using the entity denoted by <span class="name">e3</span> obtained on the <span class="name">in</span> channel
derived the
entity denoted by <span class="name">e5</span> and generated it on
-channel <span class="name">out</span>. The second is similar for <span class="name">e3</span> and <span class="name">e2</span>, but it leaves the process execution record and associated qualifiers implicit. The meaning of "channel" is application specific.
+channel <span class="name">out</span>. The second is similar for <span class="name">e3</span> and <span class="name">e2</span>, but it leaves the activity record and associated qualifiers implicit. The meaning of "channel" is application specific.
</p>
<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then it means that the entity represented by the entity record identified by <span class="name">e1</span> has an influence on the entity represented by the entity record identified by <span class="name">e2</span>, which is captured by a dependency between their attribute values; it also implies temporal ordering. These are specified as follows:</p>
-<div class='constraint' id='derivation-attributes'>Given a process execution record denoted by <span class="name">pe</span>, entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, qualifiers <span class="name">q1</span> and <span class="name">q2</span>, the assertion <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span>
+<div class='constraint' id='derivation-attributes'>Given an activity record denoted by <span class="name">pe</span>, entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, qualifiers <span class="name">q1</span> and <span class="name">q2</span>, the assertion <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span>
or <span class="name">wasDerivedFrom(e2,e1)</span> holds <span class='conditional'>if and only if</span>
the values of some attributes of the entity record identified by
<span class="name">e2</span> are partly or fully determined by the values of some
attributes of the entity record identified by <span class="name">e1</span>. </div>
-<div class='constraint' id='derivation-use-generation-ordering'>Given a process execution record identified by <span class="name">pe</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, qualifiers <span class="name">q1</span> and <span class="name">q2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span>
+<div class='constraint' id='derivation-use-generation-ordering'>Given an activity record identified by <span class="name">pe</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, qualifiers <span class="name">q1</span> and <span class="name">q2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span>
or <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span>
the use
of entity denoted by <span class="name">e1</span> precedes the generation of
@@ -1218,7 +1217,7 @@
<p>
-The following inference rule states that a generation and use event can be inferred from a process execution linked derivation record.
+The following inference rule states that a generation and use event can be inferred from an activity linked derivation record.
</p>
<div class="constraint" id='derivation-events'>
@@ -1229,12 +1228,12 @@
<p>The compact version has the same meaning as the fully formed
-process-execution linked derivation record, except that a process
-execution record is known to exist, though it does not need to be
+activity linked derivation record, except that an activity
+record is known to exist, though it does not need to be
asserted. This is formalized by the following inference rule,
-referred to as <em>process execution introduction</em>:</p>
-<div class='constraint' id="derivation-process-execution">
-<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> there exists a process execution record identified by <span class="name">pe</span>, and qualifiers <span class="name">q1</span>,<span class="name">q2</span>,
+referred to as <em>activity introduction</em>:</p>
+<div class='constraint' id="derivation-activity">
+<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> there exists an activity record identified by <span class="name">pe</span>, and qualifiers <span class="name">q1</span>,<span class="name">q2</span>,
such that:
<span class="name">wasGeneratedBy(e2,pe,q2)</span> and <span class="name">used(pe,e1,q1)</span>.
</div>
@@ -1258,11 +1257,11 @@
<p>A further inference is permitted from the compact version of derivation record: </p>
<div class='constraint' id='derivation-use'>
-<p>Given a process execution record identified by <span class="name">pe</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
+<p>Given an activity record identified by <span class="name">pe</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
<span class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,q2)</span> hold, <span class='conditional'>then</span> there exists a qualifier <span class="name">q1</span>,
such that <span class="name">used(pe,e1,q1)</span> also holds.
</div>
-<p>This inference is justified by the fact that the entity represented by entity record identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this process execution record is also the one referred to in the use record of <span class="name">e1</span>.
+<p>This inference is justified by the fact that the entity represented by entity record identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this activity record is also the one referred to in the use record of <span class="name">e1</span>.
</p>
@@ -1270,21 +1269,21 @@
<p>We note that the "symmetric" inference, does not hold.
From <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">used(pe,e1)</span>, one cannot
derive <span class="name">wasGeneratedBy(e2,pe,q2)</span> because identifier <span class="name">e1</span> may occur in use records referring to
-many process execution records, but they may not be referred to in generation records containing identifier <span class="name">e2</span>.</p>
+many activity records, but they may not be referred to in generation records containing identifier <span class="name">e2</span>.</p>
</section>
<section>
-<h4>Process Execution Independent Derivation Record</h4>
-
-
-
-
-<p>A process execution independent derivation record is a representation of a derivation, which occurred by any means whether direct or not, and regardless of any activity in the world.</p>
-
-<p>A process-execution independent derivation record, written <span class="name">wasEventuallyDerivedFrom (e2, e1)</span> in PROV-ASN,
+<h4>Activity Independent Derivation Record</h4>
+
+
+
+
+<p>an activity independent derivation record is a representation of a derivation, which occurred by any means whether direct or not, and regardless of any activity in the world.</p>
+
+<p>A activity independent derivation record, written <span class="name">wasEventuallyDerivedFrom (e2, e1)</span> in PROV-ASN,
<ul>
<li> contains an identifier <span class="name">e2</span>, denoting an entity record, which represents the generated entity;
<li> contains an identifier <span class="name">e1</span>, denoting an entity record, which represents the used entity.
@@ -1303,21 +1302,21 @@
</div>
<p>Note that temporal ordering is between generations of <span class="name">e1</span>
-and <span class="name">e2</span>, as opposed to process execution linked derivation,
+and <span class="name">e2</span>, as opposed to activity linked derivation,
which implies temporal ordering between the use of <span class="name">e1</span> and
generation of <span class="name">e2</span> (see <a href="#derivation-use-generation-ordering">derivation-use-generation-ordering</a>). Indeed, in the case of
wasEventuallyDerivedFrom, nothing is known about the use of <span class="name">e1</span>,
-since there is no associated process execution.</p>
-
-<p>A process execution linked derivation record is a richer than a process execution independent derivation record, since it
-contains or implies the existence of a process execution record. Hence, from
+since there is no associated activity.</p>
+
+<p>An activity linked derivation record is a richer than an activity independent derivation record, since it
+contains or implies the existence of an activity record. Hence, from
the former, we can infer the latter.</p>
<div class='constraint' id='derivation-linked-independent'>
Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,q12,q1)</span>
holds, <span class='conditional'>then</span> the record <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> also holds.
</div>
-<p>Hence, a process-execution independent derivation record can be directly asserted or can be inferred (by means of <a href="#derivation-linked-independent">derivation-linked-independent</a>).</p>
+<p>Hence, an activity independent derivation record can be directly asserted or can be inferred (by means of <a href="#derivation-linked-independent">derivation-linked-independent</a>).</p>
<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>
@@ -1340,7 +1339,7 @@
<p>However, there is sense that <span class="name">e3</span> still depends on <span class="name">e1</span>, since <span class="name">e3</span> could not be generated without <span class="name">e1</span> existing. Hence, we introduce a weaker notion of derivation record, which is transitive.</p>
-An instance of a transitive derivation record, written <span class="name">dependedOn(e2, e1)</span> in PROV-ASN:
+A transitive derivation record, written <span class="name">dependedOn(e2, e1)</span> in PROV-ASN:
<ul>
<li> contains an identifier <span class="name">e2</span>, denoting an entity record, which represents the entity that is the result of the derivation;
<li> contains an identifier <span class="name">e1</span>, denoting an entity record, which represents the entity that the derivation relies upon.
@@ -1388,7 +1387,7 @@
<section id="record-Control">
<h3>Control Record</h3>
-<p> A <dfn id="dfn-Control">control record</dfn> is a representation of the involvement of entity (represented as an agent record or an entity record) in an activity, which is represented by a process execution record; a control qualifier qualifies this involvement.</p>
+<p> A <dfn id="dfn-Control">control record</dfn> is a representation of the involvement of entity (represented as an agent record or an entity record) in an activity, which is represented by an activity record; a control qualifier qualifies this involvement.</p>
<p>In PROV-ASN, a control record's text matches the <span class="nonterminal">controlRecord</span> production of the grammar defined in this specification document.
</p>
@@ -1405,9 +1404,9 @@
</div>
-<p>An instance of a control record, written <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
+<p>A control record, written <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
<ul>
-<li> contains an identifier <span class="name">pe</span> denoting a process execution record, representing the controlled activity;
+<li> contains an identifier <span class="name">pe</span> denoting an activity record, representing the controlled activity;
<li> refers to an agent record or an entity record identified by <span class="name">ag</span>, representing the controlling entity;
<li> contains a qualifier <span class="name">q</span>, qualifying the involvement of the entity in the activity.
</ul>
@@ -1418,7 +1417,7 @@
<pre class="example">
wasControlledBy(pe3,a4,qualifier[role="author"])
</pre>
-<p>states that the activity, represented by the process execution record denoted by <span class="name">pe3</span> saw the involvement of an entity, represented by entity record denoted by <span class="name">a4</span> in the capacity of author. This specification reserves the qualifier name <span class="name">role</span> (see Section <a href="#record-qualifier">Qualifier</a>) to denote the function of an entity with respect to an activity.
+<p>states that the activity, represented by the activity record denoted by <span class="name">pe3</span> saw the involvement of an entity, represented by entity record denoted by <span class="name">a4</span> in the capacity of author. This specification reserves the qualifier name <span class="name">role</span> (see Section <a href="#record-qualifier">Qualifier</a>) to denote the function of an entity with respect to an activity.
</p>
</section>
@@ -1469,7 +1468,7 @@
-<p>An instance of a complementarity record is written <span class="name">wasComplementOf(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
+<p>A complementarity record is written <span class="name">wasComplementOf(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
<pre class="example">
entity(rs,[created="1870"])
@@ -1525,11 +1524,11 @@
</section>
-<section id="record-OrderingOfProcessExecutions">
-<h3>Process Execution Ordering Record</h3>
+<section id="record-OrderingOfActivities">
+<h3>Activity Ordering Record</h3>
</section>
-<div class="note">Proposal to change the name to "Dependencies amongst Process Executions" to avoid ambiguities</div>
+<div class="note">Proposal to change the name to "Dependencies amongst Activities" to avoid ambiguities</div>
<p>PROV-DM allows two forms of temporal relationships between activities to be expressed.
An <dfn id="InformationFlowOrdering">information flow ordering record</dfn> is a representation that an entity was generated by an activity, before it was used by another activity.
@@ -1537,7 +1536,7 @@
an activity precedes the start of another activity.
</p>
-<p>In PROV-ASN, a process execution ordering record's text matches the <span class="nonterminal">peOrderingRecord</span> production of the grammar defined in this specification document.
+<p>In PROV-ASN, an activity ordering record's text matches the <span class="nonterminal">peOrderingRecord</span> production of the grammar defined in this specification document.
</p>
<div class='grammar'>
@@ -1567,15 +1566,15 @@
<p>
-An instance of an information flow ordering record, written as
+A information flow ordering record, written as
<span class="name">wasInformedBy(pe2,pe1)</span> in PROV-ASN:
<ul>
-<li> refers to a process execution record identified by <span class="name">pe2</span>;
-<li> refers to a process execution record identified by <span class="name">pe1</span>
+<li> refers to an activity record identified by <span class="name">pe2</span>;
+<li> refers to an activity record identified by <span class="name">pe1</span>
</ul>
and states information flow ordering between the activities represented by these records, specified as follows.
-<div class='constraint' id='wasInformedBy'>Given two process execution records identified by <span class="name">pe1</span> and <span class="name">pe2</span>,
+<div class='constraint' id='wasInformedBy'>Given two activity records identified by <span class="name">pe1</span> and <span class="name">pe2</span>,
the record <span class="name">wasInformedBy(pe2,pe1)</span>
holds, <span class='conditional'>if and only if</span>
there is an entity record identified by <span class="name">e</span> and qualifiers <span class="name">q1</span> and <span class="name">q2</span>,
@@ -1595,32 +1594,32 @@
|
----- pe3
</pre>
-<p>The end in process execution record identified by <span class="name">pe3</span> precedes the start in process execution record identified by <span class="name">pe1</span>, while interval for process execution record <span class="name">pe2</span> overlaps with each interval for <span class="name">pe1</span> and <span class="name">pe3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
+<p>The end in activity record identified by <span class="name">pe3</span> precedes the start in activity record identified by <span class="name">pe1</span>, while interval for activity record <span class="name">pe2</span> overlaps with each interval for <span class="name">pe1</span> and <span class="name">pe3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
<p>
-An instance of a control ordering record, written as
+A control ordering record, written as
<span class="name">wasScheduledAfter(pe2,pe1)</span> in PROV-ASN: </p>
<ul>
-<li> refers to a process execution record identified by <span class="name">pe2</span>;
-<li> refers to a process execution record identified by <span class="name">pe1</span>,
+<li> refers to an activity record identified by <span class="name">pe2</span>;
+<li> refers to an activity record identified by <span class="name">pe1</span>,
</ul>
<p>and states control ordering between <span class="name">pe2</span> and <span class="name">pe1</span>, specified as follows.</p>
-<div class='constraint' id='wasScheduledAfter'>Given two process execution records identified by <span class="name">pe1</span> and <span class="name">pe2</span>,
+<div class='constraint' id='wasScheduledAfter'>Given two activity records identified by <span class="name">pe1</span> and <span class="name">pe2</span>,
the record <span class="name">wasScheduledAfter(pe2,pe1)</span>
holds, <span class='conditional'>if and only if</span>
there are two entity records identified by <span class="name">e1</span> and <span class="name">e2</span>,
such that <span class="name">wasControlledBy(pe1,e1,qualifier(role="end"))</span> and <span class="name">wasControlledBy(pe2,e2,qualifier(role="start"))</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
</div>
-<p>This definition assumes that the activities represented by process execution records identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering. </p>
+<p>This definition assumes that the activities represented by activity records identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering. </p>
<p>
-In the following assertions, we find two process execution records, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, representing two activities, which took place on two separate hosts.</p>
+In the following assertions, we find two activity records, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, representing two activities, which took place on two separate hosts.</p>
<pre class="example">
-processExecution(pe1,long-workflow,t1,t2,[host="server1.example.org"])
-processExecution(pe2,long-workflow,t3,t4,[host="server2.example.org"])
+activity(pe1,long-workflow,t1,t2,[host="server1.example.org"])
+activity(pe2,long-workflow,t3,t4,[host="server2.example.org"])
entity(e1,[type="scheduler",state=1])
entity(e2,[type="scheduler",state=2])
wasControlledBy(pe1,e1,qualifier(role="end"))
@@ -1630,8 +1629,7 @@
</pre>
<p>The one identified by <span class="name">pe2</span> is said to be
scheduled after the one identified by <span class="name">pe1</span>
-because the scheduler terminated the activity (represented by process
-execution identified by <span class="name">pe1</span>) to relocate it
+because the scheduler terminated the activity (represented by activity identified by <span class="name">pe1</span>) to relocate it
to the new host.
</p>
@@ -1662,7 +1660,7 @@
-<p>An instance of a revision record, written <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
+<p> A revision record, written <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e2</span> identifying an entity that represents a newer version of an entity;
<li> contains an identifier <span class="name">e1</span> identifying an entity that represents an older version of an entity;
@@ -1725,10 +1723,10 @@
-<p>An instance of a participation record,
+<p> A participation record,
written <span class="name">hadParticipant(pe,e)</span> in PROV-ASN:
<ul>
-<li> contains to identifier <span class="name">pe</span> identifying a process execution record representing an activity;
+<li> contains to identifier <span class="name">pe</span> identifying an activity record representing an activity;
<li> contains an identifier <span class="name">e</span> identifying an entity record, which is
a representation of an entity involved in this activity.
</ul>
@@ -1736,12 +1734,12 @@
<p>An entity's participation in an activity can be by direct use or direct control. But also, if an entity and situation are characterized in two complementary manners (and are represented by two entity records related by <span class="name">isComplementOf</span>), if one of them participates in an activity, so does the other. The following captures the definition of participation.</p>
<div class='constraint' id='participation'>
-Given two identifiers <span class="name">pe</span> and <span class="name">e</span>, respectively identifying a process execution record and an entity record, the record <span class="name">hadParticipant(pe,e)</span> holds <span class='conditional'>if and only if</span>:
+Given two identifiers <span class="name">pe</span> and <span class="name">e</span>, respectively identifying an activity record and an entity record, the record <span class="name">hadParticipant(pe,e)</span> holds <span class='conditional'>if and only if</span>:
<ul>
<li> <span class="name">used(pe,e)</span> holds, or</li>
<li> <span class="name">wasControlledBy(pe,e)</span> holds, or</li>
<li> <span class="name">wasComplementOf(e1,e)</span> holds for some entity record identified by <span class="name">e1</span>, and
- <span class="name">hadParticipant(pe,e1)</span> holds some process execution record identified by <span class="name">pe</span>.</li>
+ <span class="name">hadParticipant(pe,e1)</span> holds some activity record identified by <span class="name">pe</span>.</li>
</ul>
</div>
@@ -1797,7 +1795,7 @@
<pre class="example">
entity(e1,[type="document"])
entity(e2,[type="document"])
-processExecution(pe,transform,t1,t2,[])
+activity(pe,transform,t1,t2,[])
used(pe,e1,qualifier(file="stdin"))
wasGeneratedBy(e2, pe, qualifier(file="stdout"))
@@ -1808,7 +1806,7 @@
annotation(ann2,[style="dotted"])
hasAnnotation(relation(pe,e1,qualifier(file="stdin")),ann2)
</pre>
-<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these records with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also asserts a process execution, its use of the first entity, and its generation of the second entity. The <span class="name">used</span> relation is annotated with a style (an application specific way of rendering this edge graphically).
+<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these records with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also asserts an activity, its use of the first entity, and its generation of the second entity. The <span class="name">used</span> relation is annotated with a style (an application specific way of rendering this edge graphically).
</p>
@@ -1851,7 +1849,7 @@
<span class="name">)</span>
</div>
-<p>An instance of an account record, written <span class="name">account(id, uri, exprs)</span> in PROV-ASN:</p>
+<p>An account record, written <span class="name">account(id, uri, exprs)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span> to identify this account;</li>
<li> contains an asserter identified by URI denoted by <span class="name">uri</span>;</li>
@@ -1871,7 +1869,7 @@
...
wasDerivedFrom(e2,e1)
...
- processExecution(pe0,create-file,t)
+ activity(pe0,create-file,t)
...
wasGeneratedBy(e0,pe0,qualifier())
...
@@ -1924,12 +1922,12 @@
http://example.org/asserter2,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
...
- processExecution(pe1,create-file,t1)
+ activity(pe1,create-file,t1)
...
wasGeneratedBy(e0,pe1,qualifier(fct="create"))
... )
</pre>
-<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that the entity represented by entity record identified by <span class="name">e0</span> was generated by an activity represented by process execution record identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of records violates <a href="#generation-unicity">generation-unicity</a>.</p>
+<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that the entity represented by entity record identified by <span class="name">e0</span> was generated by an activity represented by activity record identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of records violates <a href="#generation-unicity">generation-unicity</a>.</p>
<p>Account records constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes. When an record with an identifier occurs directly within an account, then its identifier denotes this record in the scope of this account, except in sub-accounts where records with the same identifier occur. </p>
@@ -1939,16 +1937,16 @@
account(acc3,
http://example.org/asserter1,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
- processExecution(pe0,create-file,t)
+ activity(pe0,create-file,t)
wasGeneratedBy(e0,pe0,qualifier())
account(acc4,
http://example.org/asserter2,
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
- processExecution(pe0,copy-file,t)
+ activity(pe0,copy-file,t)
wasGeneratedBy(e1,pe0,qualifier(fct="create"))
isComplement(e1,e0)))
</pre>
-<p>Alternatively, a process execution record identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each process execution record is asserted in a separate scope, and therefore may represent different activities in the world.
+<p>Alternatively, an activity record identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each activity record is asserted in a separate scope, and therefore may represent different activities in the world.
</p>
<p>The account record is the hook by which further meta information can be expressed about provenance, such as asserter, time of creation, signatures. How general meta-information is expressed is beyond the scope of this specification, except for asserters.</p>
@@ -1979,7 +1977,7 @@
<span class="name">)</span>
</div>
-<p>An instance of a provenance container, written <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
+<p>A provenance container, written <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
<ul>
<li> contains a set of namespace declarations <span class="name">decls</span>, declaring namespaces and associated prefixes, which can be used in attributes (conformant to production <span class="nonterminal">attribute</span>) and in names (conformant to production <span class="nonterminal">name</span>) in <span class="name">exprs</span>;</li>
<li> contains a set of identifiers <span class="name">ids</span> naming all accounts occurring (at any nesting level) in <span class="name">exprs</span>;</li>
@@ -2049,7 +2047,7 @@
<div class="note">aren't these two sentences contradictory></div>
-<p>The interpretation of a qualifier is specific to the process execution record it occurs in, which means that a same qualifier may appear in two different process execution records with different interpretations.
+<p>The interpretation of a qualifier is specific to the activity record it occurs in, which means that a same qualifier may appear in two different activity records with different interpretations.
From this specification's viewpoint, a qualifier's interpretation is out of
scope.</p>
@@ -2059,17 +2057,17 @@
By definition, a use (resp. generation, control) record does not contain an identifier.
If one wants to annotate a use (resp. generation, control) record, this record MUST be identifiable from its constituents, i.e. its source's identifier, its destination's identifier, and its qualifier.</p>
-<p> To be able to annotate use (resp. generation, control) records that refer to a given process execution identifier,
+<p> To be able to annotate use (resp. generation, control) records that refer to a given activity identifier,
any qualifier occuring in use records (resp. generation, control) with this identifier and a given entity record identifier MUST be unique.</p>
<div class='note'>It may seem strange that we do not require use records to have an identifier. Mandating the presence of identifiers in use records would facilitate their annotation. However, this would make it difficult for use records to be encoded as properties in OWL2.
</div>
<p>Qualifiers are used in determining the exact source and destination of a <span class="nonterminal">pe-linked-derivationRecord</span>. Hence,
-if one wants to express a <span class="nonterminal">pe-linked-derivationRecord</span> referring to an entity record and a process execution record, then:</p>
+if one wants to express a <span class="nonterminal">pe-linked-derivationRecord</span> referring to an entity record and an activity record, then:</p>
<ul>
-<li>the useQualifier MUST be unique among the qualifiers occuring in use records for this process execution record;
-<li>the generationQualifier MUST be unique among the qualifiers occuring in generation records for this process execution record.
+<li>the useQualifier MUST be unique among the qualifiers occuring in use records for this activity record;
+<li>the generationQualifier MUST be unique among the qualifiers occuring in generation records for this activity record.
</ul>
@@ -2159,7 +2157,7 @@
-<p>It is OPTIONAL to assert time in use, generation, and process execution records.</p>
+<p>It is OPTIONAL to assert time in use, generation, and activity records.</p>
<section>
@@ -2168,8 +2166,8 @@
<ol>
<li>Generation of an entity by an activity: identifies the final instant of an entity's creation timespan, after which it becomes available for use.</li>
<li>Use of an entity by an activity: identifies the first instant of an entity's consumption timespan.</li>
-<li>Start of an activity: identifies the instant an activity, represented by a process execution, starts;</li>
-<li>End of an activity: identifies the instant an activity, represented by a process execution, ends.</li>
+<li>Start of an activity: identifies the instant an activity, represented by an activity, starts;</li>
+<li>End of an activity: identifies the instant an activity, represented by an activity, ends.</li>
</ol>
</section>
@@ -2214,7 +2212,7 @@
<h3>Recipe Link</h3>
-<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between a process execution record and a process specification that underpins the represented activity.
+<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between an activity record and a process specification that underpins the represented activity.
</p>
<div class='grammar'>
@@ -2222,7 +2220,7 @@
</div>
<p>
-It is OPTIONAL to assert recipe links in process executions.
+It is OPTIONAL to assert recipe links in activities.
</p>
@@ -2243,7 +2241,7 @@
<p>
-Location is an OPTIONAL attribute of entity records and process execution records. The value associated with a attribute <span class="name">location</span> MUST be a <span class="nonterminal">Literal</span>, expected to denote a location.
+Location is an OPTIONAL attribute of entity records and activity records. The value associated with a attribute <span class="name">location</span> MUST be a <span class="nonterminal">Literal</span>, expected to denote a location.
</p>
@@ -2423,21 +2421,21 @@
<span class="name">)</span>
</div>
-<p> An instance of an attribution record, written <span class="name"> wasAttributedTo(e,ag)</span>:</p>
+<p> An attribution record, written <span class="name"> wasAttributedTo(e,ag)</span>:</p>
<ul>
<li>contains an identifer <span class="name">e</span>, identifying an entity record;
<li>contains an identifer <span class="name">ag</span>, identifying the agent whom the entity is attributed to.
</ul>
-<p>Attribution models the notion of a process execution generating an entity identified by <span class="name">e</span> being controlled by an agent <span class="name">ag</span>, which takes responsibility for generating <span class="name">e</span>. Formally, this is expressed as the following necessary condition.</p>
+<p>Attribution models the notion of an activity generating an entity identified by <span class="name">e</span> being controlled by an agent <span class="name">ag</span>, which takes responsibility for generating <span class="name">e</span>. Formally, this is expressed as the following necessary condition.</p>
<div class='constraint' id='attribution-implication'>
<span class='conditional'>If</span>
<span class="name">wasAttributedTo(e,ag)</span> holds for some identifiers
<span class="name">e</span> and <span class="name">ag</span>,
-<span class='conditional'>then</span> there exists a process execution identified by <span class="name">pe</span> such that the following statements hold:
+<span class='conditional'>then</span> there exists an activity identified by <span class="name">pe</span> such that the following statements hold:
<pre>
-processExecution(pe,recipe,t1,t2,attr)
+activity(pe,recipe,t1,t2,attr)
wasGenerateBy(e,pe)
wasControlledBy(pe,ag,q)
</pre>
@@ -2469,7 +2467,7 @@
</div>
-<p> An instance of a quotation record, written <span class="name"> wasQuoteOf(e2,e1,ag2,ag1)</span>:</p>
+<p> A quotation record, written <span class="name"> wasQuoteOf(e2,e1,ag2,ag1)</span>:</p>
<ul>
<li>contains an identifier <span class="name">e2</span>, identifying an entity record that represents the quote;
<li>contains an identifier <span class="name">e1</span>, identifying an entity record representing what is being quoted;
@@ -2633,7 +2631,7 @@
<li>The graphical illustration is a graph. </li>
-<li>entities, process executions and agents are represented as nodes, with oval, rectangular, and half-hexagonal shapes, respectively. </li>
+<li>Entities, activities and agents are represented as nodes, with oval, rectangular, and half-hexagonal shapes, respectively. </li>
<li>Use, Generation, Derivation, IVPof are represented as directed edges.</li>
@@ -2653,6 +2651,7 @@
<section class="appendix">
<h2>Changes Since Previous Version</h2>
<ul>
+<li>11/07/11: Aligned terminology 'activity' and 'process execution record'.</li>
<li>11/07/11: Renamed 'xxx Expression' into 'xxx Record' to avoid the language connotation.</li>
<li>11/07/11: Defined entity as identifiable characterized thing, and updated text accordingly.</li>
<li>10/08/11: Made explicit the term expression wherever was appropriate, including section titles.</li>