--- a/model/ProvenanceModel.html Thu Dec 08 21:31:54 2011 +0000
+++ b/model/ProvenanceModel.html Thu Dec 08 21:44:06 2011 +0000
@@ -12,6 +12,7 @@
<style type="text/css">
.note { font-size:small; margin-left:50px }
table { text-align: center; vertical-align: middle }
+ center { text-align: center; }
</style>
<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
@@ -571,7 +572,9 @@
<p>
The following ER diagram provides a high level overview of the <strong>structure of PROV-DM records</strong>. Examples of provenance assertions that conform to this schema are provided in the next section.</p>
+<div style="text-align: center;">
<img src="overview.png" alt="PROV-DM overview"/>
+</div>
<div class="note"> Overview diagram does not represent the sub-relations -- proposal to use a UML notation instead of ER.</div>
@@ -807,9 +810,13 @@
<p>Entities are layed out according to the ordering of their generation event. We endeavor to show time progressing from left to right. This means that edges for Usage, Generation and Derivation typically point from right to left.</p>
+<div style="text-align: center;">
<img src="example-graphical.png" alt="example"/>
+</div>
<br/>
+<div style="text-align: center;">
<img src="timeline.png" alt="example"/>
+</div>
</section>
</section>
@@ -1167,8 +1174,8 @@
<p>This section describes all the PROV-DM records representing relations between the elements introduced in <a href="#record-element">Section Element</a>. While these relations are not binary, they all involve two primary elements. They can be summarized as follows. </p>
-<div class="table">
-<table border="1" align="center">
+<div style="text-align: center;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
<caption>PROV-DM Core Relation Summary</caption>
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
<tr><td>Entity</td><td><a title="derivation record">wasDerivedFrom</a><br><a title="complementarity record">wasComplementOf</a></td><td><a title="generation record">wasGeneratedBy</a></td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
@@ -1638,8 +1645,9 @@
<p>Hence, given a precision axis, with values <em>precise</em> and <em>imprecise</em>, and an activity axis, with values <em>one activity</em> and <em>n activities</em>, we can then form a matrix of possible derivations, precise or imprecise, or corresponding to one activity or n activities.
Out of the four possibilities, PROV-DM offers three forms of derivation, while the fourth one is not meaningful. The following table summarises names for the three kinds of derivation, which we then explain.</p>
-<div class="table">
-<table border="1" align="center">
+
+<div style="text-align: center;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
<caption>PROV-DM Derivation Type Summary</caption>
<tr><td colspan=2 rowspan=2></td><td colspan=2>precision axis</td></tr>
<tr><td>precise</td><td>imprecise</td></tr>
@@ -1892,7 +1900,9 @@
An entity record represents, by means of attribute-value pairs, a thing and its situation in the world, which remain constant over a characterization interval.
As soon as the thing's situation changes, this marks the end of the characterization interval for the entity record representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity record, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two entities, we can hope to establish correspondences amongst the entity records that represent them at various points along that events line. The figure below illustrates this intuition.</p>
+<div style="text-align: center;">
<img src="complement-of.png" alt="illustration complementOf"/>
+</div>
<p>
Relation <em>complement-of</em> between two entity records is intended to capture these correspondences, as follows. Suppose entity records A and B share a set P of attributes, and each of them has other attributes in addition to P. If the values assigned to each attribute in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of attributes of B is a strict superset of A's attributes, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
@@ -2576,7 +2586,9 @@
<p>The following figure summarizes the additional relations described in subsections 6.2 onwards.</p>
+<div style="text-align: center;">
<img src="sec6-summary.png" alt="common relations"/>
+</div>
<section id="record-Collection">
@@ -2670,7 +2682,9 @@
</pre>
<p>The corresponding graphical representation is shown below.</p>
+<div style="text-align: center;">
<img src="collections.png" alt="collections"/>
+</div>
<p> With these assertions:</p>
@@ -2832,8 +2846,7 @@
from
<span class="name">wasInformedBy(a2,a1)</span>, we know that there exists <span class="name">e1</span> such that <span class="name">e1</span> was generated by <span class="name">a1</span> and used by <span class="name">a2</span>. Likewise, from <span class="name">wasInformedBy(a3,a2)</span>, we know that there exists <span class="name">e2</span> such that <span class="name">e2</span> was generated by <span class="name">a2</span> and used by <span class="name">a3</span>. The following illustration shows a case where transitivity cannot hold. The horizontal axis represents time. We see that <span class="name">e1</span> was generated after <span class="name">e2</span> was used. Furthermore, the illustration also shows that <span class="name">a3</span> completes before <span class="name">a1</span>. So it is impossible for <span class="name">a3</span> to have used an entity generated by <span class="name">a1</span>.</p>
-
-<div align="center">
+<div style="text-align: center;">
<img src="informedByNonTransitive.png" alt="non transitivity of wasInformedBy" />
</div>