--- a/model/prov-constraints.html Wed Aug 08 11:49:50 2012 +0100
+++ b/model/prov-constraints.html Wed Aug 08 12:08:22 2012 +0100
@@ -1548,14 +1548,14 @@
class="name">a1</span> started. So in this example (with no other
information) it is impossible for <span class="name">a3</span> to have used an entity generated by <span
class="name">a1</span>. This is illustrated in <a
-href="#counterexample-wasInformedBy">Figure 1</a>.</p>
+href="#counterexample-wasInformedBy">Figure 2</a>.</p>
<div style="text-align: center;">
<figure>
<img src="images/constraints/informedByNonTransitive.png" alt="non transitivity of wasInformedBy" />
<br>
<figcaption id="counterexample-wasInformedBy">Counter-example for transitivity of wasInformedBy</figcaption>
-</figure> <!-- <b>Figure 1:</b> -->
+</figure> <!-- <b>Figure 2:</b> -->
</div>
</div>
@@ -2508,7 +2508,7 @@
start and endpoints of its lifetime.
</p>
-<p><a href="#ordering-activity">Figure 2</a> summarizes the ordering
+<p><a href="#ordering-activity">Figure 3</a> summarizes the ordering
constraints on activities in a
graphical manner. For this and subsequent figures, an event time line points to the
right. Activities are represented by rectangles, whereas entities are
@@ -2531,7 +2531,7 @@
<figure id="ordering-activity">
<img src="images/constraints/ordering-activity.png" alt="constraints between events" />
<br>
-<figcaption id="ordering-activity-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for activities</figcaption> <!-- <b>Figure 2:</b> -->
+<figcaption id="ordering-activity-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for activities</figcaption> <!-- <b>Figure 3:</b> -->
</figure>
</div>
@@ -2544,7 +2544,7 @@
The existence of an activity implies that the <a>activity start
event</a> always <a>precedes</a> the corresponding <a>activity end
event</a>. This is illustrated by
-<a href="#ordering-activity">Figure 2</a>
+<a href="#ordering-activity">Figure 3</a>
(a) and expressed by <a class="rule-ref"
href="#start-precedes-end"><span>TBD</span></a>.</p>
@@ -2564,7 +2564,7 @@
<hr />
<p id='usage-within-activity_text'>A usage implies ordering of <a title="instantaneous event">events</a>, since the <a title="entity usage event">usage event</a> had to occur during the associated activity. This is
-illustrated by <a href="#ordering-activity">Figure 2</a> (b) and expressed by <a class="rule-ref" href="#usage-within-activity"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-activity">Figure 3</a> (b) and expressed by <a class="rule-ref" href="#usage-within-activity"><span>TBD</span></a>.</p>
<div class='constraint' id='usage-within-activity'>
<ol>
@@ -2597,7 +2597,7 @@
<p id='generation-within-activity_text'>A generation implies ordering of <a title="instantaneous event">events</a>, since the <a title="entity generation event">generation event</a> had to occur during the associated activity. This is
-illustrated by <a href="#ordering-activity">Figure 2</a> (c) and expressed by <a class="rule-ref" href="#generation-within-activity"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-activity">Figure 3</a> (c) and expressed by <a class="rule-ref" href="#generation-within-activity"><span>TBD</span></a>.</p>
<div class='constraint' id='generation-within-activity'>
<ol>
@@ -2635,7 +2635,7 @@
implies that the start event of <span class="name">a1</span> cannot
follow the end event of <span class="name">a2</span>. This is
illustrated by
-<a href="#ordering-activity">Figure 2</a>
+<a href="#ordering-activity">Figure 3</a>
(d) and expressed by <a class="rule-ref"
href="#wasInformedBy-ordering"><span>TBD</span></a>.</p>
@@ -2664,7 +2664,7 @@
of <a title="instantaneous event">events</a>,
since <span class="name">a1</span> must have been active
before <span class="name">a2</span> started. This is illustrated by
-<a href="#ordering-activity">Figure 2</a>
+<a href="#ordering-activity">Figure 3</a>
(e) and expressed by <a class="rule-ref"
href="#wasStartedByActivity-ordering"><span>TBD</span></a>.</p>
@@ -2693,8 +2693,8 @@
As with activities, entities have lifetimes: they are generated, then
can be used, other entities can be derived from them, and finally they
can be invalidated. The constraints on these events are
-illustrated graphically in <a href="#ordering-entity">Figure 3</a> and
-<a href="#ordering-entity-trigger">Figure 4</a>.
+illustrated graphically in <a href="#ordering-entity">Figure 4</a> and
+<a href="#ordering-entity-trigger">Figure 5</a>.
</p>
@@ -2703,7 +2703,7 @@
<figure id="ordering-entity">
<img src="images/constraints/ordering-entity.png" alt="ordering constraints for entities" />
<br>
-<figcaption id="ordering-entity-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for entities</figcaption></figure> <!-- <b>Figure 3:</b> -->
+<figcaption id="ordering-entity-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for entities</figcaption></figure> <!-- <b>Figure 4:</b> -->
</div>
<p>
@@ -2737,7 +2737,7 @@
<p id='generation-precedes-usage_text'>
A usage and a generation for a given entity implies ordering of <a title="instantaneous event">events</a>, since the <a title="entity generation
event">generation event</a> had to precede the <a title="entity usage event">usage event</a>. This is
-illustrated by <a href="#ordering-entity">Figure 3</a>(a) and expressed by <a class="rule-ref" href="#generation-precedes-usage"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-entity">Figure 4</a>(a) and expressed by <a class="rule-ref" href="#generation-precedes-usage"><span>TBD</span></a>.</p>
<div class='constraint' id='generation-precedes-usage'>
<p> <span class="conditional">IF</span>
@@ -2781,7 +2781,7 @@
First, we consider derivations, where the activity and usage are known. In that case, the <a title="entity usage event">usage</a> of <span class="name">e1</span> has to precede the <a title="entity generation
event">generation</a> of <span class="name">e2</span>.
This is
-illustrated by <a href="#ordering-entity-fig">Figure 3</a> (b) and expressed by <a
+illustrated by <a href="#ordering-entity-fig">Figure 4</a> (b) and expressed by <a
class="rule-ref" href="#derivation-usage-generation-ordering"><span>TBD</span></a>.</p>
@@ -2801,7 +2801,7 @@
<p id='derivation-generation-generation-ordering_text'>
When the activity, generation or usage is unknown, a similar constraint exists, except that the constraint refers to its
generation event, as
-illustrated by <a href="#ordering-entity-fig">Figure 3</a> (c) and expressed by <a
+illustrated by <a href="#ordering-entity-fig">Figure 4</a> (c) and expressed by <a
class="rule-ref" href="#derivation-generation-generation-ordering"><span>TBD</span></a>.</p>
<div class='constraint'
@@ -2838,7 +2838,7 @@
<p id='wasStartedBy-ordering_text'>
The entity that triggered the start of an activity must exist before the activity starts.
This is
-illustrated by <a href="#ordering-entity-trigger">Figure 4</a>(a) and expressed by <a class="rule-ref" href="#wasStartedBy-ordering"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-entity-trigger">Figure 5</a>(a) and expressed by <a class="rule-ref" href="#wasStartedBy-ordering"><span>TBD</span></a>.</p>
<div class='constraint' id='wasStartedBy-ordering'>
@@ -2870,7 +2870,7 @@
<p id='wasEndedBy-ordering_text'> Similarly, the entity that triggered
the end of an activity must exist before the activity ends, as
illustrated by
-<a href="#ordering-entity-trigger">Figure 4</a>(b).</p>
+<a href="#ordering-entity-trigger">Figure 5</a>(b).</p>
<div class='constraint' id='wasEndedBy-ordering'>
@@ -2901,7 +2901,7 @@
<figure id="ordering-entity-trigger">
<img src="images/constraints/ordering-entity-trigger.png" alt="ordering constraints for trigger entities" />
<br>
-<figcaption id="ordering-entity-trigger-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for trigger entities</figcaption> <!-- <b>Figure 4:</b> -->
+<figcaption id="ordering-entity-trigger-fig">Summary of <a title="instantaneous event">instantaneous event</a> ordering constraints for trigger entities</figcaption> <!-- <b>Figure 5:</b> -->
</figure>
</div>
@@ -2951,7 +2951,7 @@
activity, attribution, or delegation.
</p> <p>Further constraints associated with agents appear in <a
- href="#ordering-agents">Figure 5</a> and are discussed below.</p>
+ href="#ordering-agents">Figure 6</a> and are discussed below.</p>
<div style="text-align: center;">
<figure id="ordering-agents-fig">
@@ -2959,7 +2959,7 @@
<br>
<figcaption id="ordering-agents">Summary of <a
title="instantaneous event">instantaneous event</a> ordering
- constraints for agents</figcaption> <!--<b>Figure 5:</b> -->
+ constraints for agents</figcaption> <!--<b>Figure 6:</b> -->
</figure>
</div>
@@ -2971,7 +2971,7 @@
agent MUST have been generated, or MUST have become
associated with the activity, after the activity start: so, the agent MUST exist before the activity end. Likewise, the agent may be destructed, or may terminate its association with the activity, before the activity end: hence, the agent invalidation is required to happen after the activity start.
This is
-illustrated by <a href="#ordering-agents">Figure 5</a> (a) and expressed by <a class="rule-ref" href="#wasAssociatedWith-ordering"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-agents">Figure 6</a> (a) and expressed by <a class="rule-ref" href="#wasAssociatedWith-ordering"><span>TBD</span></a>.</p>
<div class='constraint' id='wasAssociatedWith-ordering'>
@@ -3013,7 +3013,7 @@
with the agent. The agent MUST exist before the entity
invalidation. Likewise, the entity generation must precede the agent destruction.
This is
-illustrated by <a href="#ordering-agents">Figure 5</a> (b) and expressed by <a class="rule-ref" href="#wasAttributedTo-ordering"><span>TBD</span></a>.</p>
+illustrated by <a href="#ordering-agents">Figure 6</a> (b) and expressed by <a class="rule-ref" href="#wasAttributedTo-ordering"><span>TBD</span></a>.</p>