--- a/model/ProvenanceModel.html Fri Nov 11 09:37:20 2011 +0000
+++ b/model/ProvenanceModel.html Fri Nov 11 09:59:04 2011 +0000
@@ -566,7 +566,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 activity underpinning the derivation, and relevant attribute describing the use and generation of entities.</p>
+Derivation Records (described in <a href="#Derivation-Relation">Section Derivation Relation</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 attribute describing the use and generation of entities.</p>
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -956,6 +956,8 @@
<p>This section describes all the PROV-ASN records conformant to the <span class='nonterminal'>relationRecord</span> production of the grammar.</p>
+<section id="activity-entity-relation">
+<h3>Activity-Entity Relation</h3>
<section id="record-Generation">
<h4>Generation Record</h4>
@@ -1120,11 +1122,11 @@
<div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
</section>
-
-
-
-<section id="record-Derivation">
-<h3>Derivation Record</h3>
+</section>
+
+
+<section id="Derivation-Relation">
+<h3>Derivation Relation</h3>
<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>
@@ -1403,9 +1405,11 @@
+<section id="activity-agent-relation">
+<h3>Activity-Agent Relation</h3>
<section id="record-Control">
-<h3>Control Record</h3>
+<h4>Control Record</h4>
<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; attributes describe this involvement.</p>
@@ -1442,6 +1446,52 @@
</section>
+<section id="record-Participation">
+<h4>Participation Record</h4>
+
+<p>A <dfn id="dfn-Participation">participation record</dfn> is a representation of the involvement of an entity in an activity. A participation record can be asserted or inferred.</p>
+
+
+<p>In PROV-ASN, a participation record's text matches the <span class="nonterminal">participationRecord</span> production of the grammar defined in this specification document.</p>
+
+
+<div class='grammar'>
+<span class="nonterminal">participationRecord</span> :=
+<span class="name">hadParticipant</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+<span class="name">)</span>
+</div>
+
+
+
+<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 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>
+
+<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 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 activity record identified by <span class="name">pe</span>.</li>
+</ul>
+</div>
+
+
+<div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
+
+</section>
+</section>
<section id="record-complement-of">
@@ -1544,229 +1594,6 @@
</section>
-<section id="record-OrderingOfActivities">
-<h3>Activity Ordering Record</h3>
-</section>
-
-<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.
-A <dfn id="ControlOrdering">control ordering record</dfn> is a representation that the end of
-an activity precedes the start of another activity.
-</p>
-
-<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'>
-<span class="nonterminal">peOrderingRecord</span> :=
-<span class="nonterminal">informationFlowOrderingRecord</span> |
-<span class="nonterminal">controlOrderingRecord</span>
-<br/>
-
-<span class="nonterminal">informationFlowOrderingRecord</span> :=
-<span class="name">wasInformedBy</span>
-<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
-<span class="name">)</span>
-<br/>
-
-<span class="nonterminal">controlOrderingRecord</span> :=
-<span class="name">wasScheduledAfter</span>
-<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
-<span class="name">)</span>
-<br/>
-</div>
-
-
-<p>
-A information flow ordering record, written as
-<span class="name">wasInformedBy(pe2,pe1)</span> in PROV-ASN:
-<ul>
-<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 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 sets of attribute-value pairs <span class="name">attrs1</span> and <span class="name">attrs2</span>,
-such that <span class="name">wasGeneratedBy(e,pe1,attrs1)</span> and <span class="name">used(pe2,e,attrs2)</span> hold.
-</div>
-
-<p>The relationship <span class="name">wasInformedBy</span> is not transitive. Indeed, consider the records <span class="name">wasInformedBy(pe2,pe1)</span> and <span class="name">wasInformedBy(pe3,pe2)</span>, the record
-<span class="name">wasInformedBy(pe3,pe1)</span>, may not necessarily hold, as illustrated by the following event line.
-<pre>
- ------ pe1
- |
- e1
- |
- ------- pe2
- |
- e2
- |
- ----- pe3
-</pre>
-<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>
-A control ordering record, written as
-<span class="name">wasScheduledAfter(pe2,pe1)</span> in PROV-ASN: </p>
-<ul>
-<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 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,[prov:role="end"])</span> and <span class="name">wasControlledBy(pe2,e2,[prov:role="start"])</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
-</div>
-<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 attribute <span class="name">[prov:role="end")</span>) the first activity, and the second agents initiates (control attribute <span class="name">[prov: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 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">
-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,[prov:role="end"])
-wasControlledBy(pe2,e2,[prov:role="start"])
-wasDerivedFrom(e2,e1)
-wasScheduledAfter(pe2,pe1)
-</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 activity identified by <span class="name">pe1</span>) to relocate it
-to the new host.
-</p>
-
-
-<div class='pending'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</div>
-
-
-
-<section id="record-Revision">
-<h3>Revision Record</h3>
-
-<p> A <dfn id="dfn-Revision">revision record</dfn> is a representation of the creation of an entity considered to be a variant of another. Deciding whether something is made available as a revision of something else usually involves an agent who represents someone in the world who takes responsibility for declaring that the former is variant of the latter. </p>
-
-<p>In PROV-ASN, a revision record's text matches the <span class="nonterminal">revisionRecord</span> production of the grammar defined in this specification document.
-</p>
-
-<div class='grammar'>
-<span class="nonterminal">revisionRecord</span> :=
-<span class="name">wasRevisionOf</span>
-<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
-[<span class="name">,</span>
-<span class="nonterminal">identifier</span>]
-<span class="name">)</span>
-</div>
-
-
-
-<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;
-<li> MAY refer to a responsible agent with identifier <span class="name">ag</span>.
-</ul>
-
-
-<p>A revision record can only be asserted, since it needs to include a reference to an agent who represents someone in the real world who bears responsibility for declaring a variant of an entity. However, it needs to satisfy the following constraint, linking the two entity records by a derivation, and stating them to be a complement of a third entity record.</p>
-
-<div class='constraint' id='wasRevision'>
-Given two identifiers <span class="name">old</span> and <span class="name">new</span> identifying two entities, and an identifier <span class="name">ag</span> identifying an agent,
-<span class='conditional'>if</span> a record <span class="name">wasRevisionOf(new,old,ag)</span> is asserted, <span class='conditional'>then</span>
-there exists an entity record identifier <span class="name">e</span> and attribute-values <span class="name">av</span>, such that the following records hold:
-<ul>
-<li> <span class="name">wasEventuallyDerivedFrom(new,old)</span>;
-<li> <span class="name">entity(e,av)</span>;
-<li> <span class="name">wasComplementOf(new,e)</span>;
-<li> <span class="name">wasComplementOf(old,e)</span>.
-</ul>
-</div>
-
-<p><span class="name">wasRevisionOf</span> is a strict sub-relation
- of <span class="name">wasEventuallyDerivedDerivedFrom</span> since two entities <span class="name">e2</span> and <span class="name">e1</span>
- may satisfy <span class="name">wasEventuallyDerivedDerivedFrom(e2,e1)</span> without being a variant of
- each other.
-</p>
-
-<p>
-The following revision assertion</p>
-<pre class="example">
-wasRevisionOf(e3,e2,a4)
-</pre>
-<p>states that the document represented by entity record identified by <span class="name">e3</span> is declared to be revision of document represented by entity record identified by <span class="name">e2</span> by agent representy by entity record denoted by <span class="name">a4</span>.
-</p>
-
-
-<div class='pending'>Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
-
-
-</section>
-
-<section id="record-Participation">
-<h3>Participation Record</h3>
-
-<p>A <dfn id="dfn-Participation">participation record</dfn> is a representation of the involvement of an entity in an activity. A participation record can be asserted or inferred.</p>
-
-
-<p>In PROV-ASN, a participation record's text matches the <span class="nonterminal">participationRecord</span> production of the grammar defined in this specification document.</p>
-
-
-<div class='grammar'>
-<span class="nonterminal">participationRecord</span> :=
-<span class="name">hadParticipant</span>
-<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
-<span class="name">)</span>
-</div>
-
-
-
-<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 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>
-
-<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 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 activity record identified by <span class="name">pe</span>.</li>
-</ul>
-</div>
-
-
-<div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
-
-</section>
<section id="record-annotationAssociation">
<h4>Annotation Association Record</h4>
@@ -2385,6 +2212,184 @@
<div class='note'>The types of these relations need to be made explicit.</div>
+<section id="record-OrderingOfActivities">
+<h3>Activity Ordering Record</h3>
+</section>
+
+<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.
+A <dfn id="ControlOrdering">control ordering record</dfn> is a representation that the end of
+an activity precedes the start of another activity.
+</p>
+
+<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'>
+<span class="nonterminal">peOrderingRecord</span> :=
+<span class="nonterminal">informationFlowOrderingRecord</span> |
+<span class="nonterminal">controlOrderingRecord</span>
+<br/>
+
+<span class="nonterminal">informationFlowOrderingRecord</span> :=
+<span class="name">wasInformedBy</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+<span class="name">)</span>
+<br/>
+
+<span class="nonterminal">controlOrderingRecord</span> :=
+<span class="name">wasScheduledAfter</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+<span class="name">)</span>
+<br/>
+</div>
+
+
+<p>
+A information flow ordering record, written as
+<span class="name">wasInformedBy(pe2,pe1)</span> in PROV-ASN:
+<ul>
+<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 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 sets of attribute-value pairs <span class="name">attrs1</span> and <span class="name">attrs2</span>,
+such that <span class="name">wasGeneratedBy(e,pe1,attrs1)</span> and <span class="name">used(pe2,e,attrs2)</span> hold.
+</div>
+
+<p>The relationship <span class="name">wasInformedBy</span> is not transitive. Indeed, consider the records <span class="name">wasInformedBy(pe2,pe1)</span> and <span class="name">wasInformedBy(pe3,pe2)</span>, the record
+<span class="name">wasInformedBy(pe3,pe1)</span>, may not necessarily hold, as illustrated by the following event line.
+<pre>
+ ------ pe1
+ |
+ e1
+ |
+ ------- pe2
+ |
+ e2
+ |
+ ----- pe3
+</pre>
+<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>
+A control ordering record, written as
+<span class="name">wasScheduledAfter(pe2,pe1)</span> in PROV-ASN: </p>
+<ul>
+<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 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,[prov:role="end"])</span> and <span class="name">wasControlledBy(pe2,e2,[prov:role="start"])</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
+</div>
+<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 attribute <span class="name">[prov:role="end")</span>) the first activity, and the second agents initiates (control attribute <span class="name">[prov: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 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">
+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,[prov:role="end"])
+wasControlledBy(pe2,e2,[prov:role="start"])
+wasDerivedFrom(e2,e1)
+wasScheduledAfter(pe2,pe1)
+</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 activity identified by <span class="name">pe1</span>) to relocate it
+to the new host.
+</p>
+
+
+<div class='pending'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</div>
+
+
+
+<section id="record-Revision">
+<h3>Revision Record</h3>
+
+<p> A <dfn id="dfn-Revision">revision record</dfn> is a representation of the creation of an entity considered to be a variant of another. Deciding whether something is made available as a revision of something else usually involves an agent who represents someone in the world who takes responsibility for declaring that the former is variant of the latter. </p>
+
+<p>In PROV-ASN, a revision record's text matches the <span class="nonterminal">revisionRecord</span> production of the grammar defined in this specification document.
+</p>
+
+<div class='grammar'>
+<span class="nonterminal">revisionRecord</span> :=
+<span class="name">wasRevisionOf</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+[<span class="name">,</span>
+<span class="nonterminal">identifier</span>]
+<span class="name">)</span>
+</div>
+
+
+
+<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;
+<li> MAY refer to a responsible agent with identifier <span class="name">ag</span>.
+</ul>
+
+
+<p>A revision record can only be asserted, since it needs to include a reference to an agent who represents someone in the real world who bears responsibility for declaring a variant of an entity. However, it needs to satisfy the following constraint, linking the two entity records by a derivation, and stating them to be a complement of a third entity record.</p>
+
+<div class='constraint' id='wasRevision'>
+Given two identifiers <span class="name">old</span> and <span class="name">new</span> identifying two entities, and an identifier <span class="name">ag</span> identifying an agent,
+<span class='conditional'>if</span> a record <span class="name">wasRevisionOf(new,old,ag)</span> is asserted, <span class='conditional'>then</span>
+there exists an entity record identifier <span class="name">e</span> and attribute-values <span class="name">av</span>, such that the following records hold:
+<ul>
+<li> <span class="name">wasEventuallyDerivedFrom(new,old)</span>;
+<li> <span class="name">entity(e,av)</span>;
+<li> <span class="name">wasComplementOf(new,e)</span>;
+<li> <span class="name">wasComplementOf(old,e)</span>.
+</ul>
+</div>
+
+<p><span class="name">wasRevisionOf</span> is a strict sub-relation
+ of <span class="name">wasEventuallyDerivedDerivedFrom</span> since two entities <span class="name">e2</span> and <span class="name">e1</span>
+ may satisfy <span class="name">wasEventuallyDerivedDerivedFrom(e2,e1)</span> without being a variant of
+ each other.
+</p>
+
+<p>
+The following revision assertion</p>
+<pre class="example">
+wasRevisionOf(e3,e2,a4)
+</pre>
+<p>states that the document represented by entity record identified by <span class="name">e3</span> is declared to be revision of document represented by entity record identified by <span class="name">e2</span> by agent representy by entity record denoted by <span class="name">a4</span>.
+</p>
+
+
+<div class='pending'>Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
+
+
+</section>
+
<section>
<h3>Attribution Record</h3>