--- a/dc-note/releases/NOTE-prov-dc-20121211/Overview.html Mon Dec 03 12:13:40 2012 +0100
+++ b/dc-note/releases/NOTE-prov-dc-20121211/Overview.html Mon Dec 03 12:26:47 2012 +0100
@@ -714,7 +714,7 @@
agent that are directly related to the document (as in <a href="#figure_mapping_example">Figure 1</a>).
</p><p>
</p><div id="figure_mapping_example" class="figure" style="text-align: center;">
- <img src="img/example1.png">
+ <img src="img/example1.png" alt="A mapping example illustrating the first approach">
<div style="text-align: center;">
<a href="#figure_mapping_example">Figure 1</a>. A mapping example creating blank nodes for each state of the resource. In PROV entities are represented
with ellipses, activities with rectangles and agents with pentagons.
@@ -729,7 +729,7 @@
</p><p>
</p><div id="figure_mapping_example_conflating" class="figure" style="text-align: center;">
- <img src="img/mapping-example%2520-%2520conflating.png">
+ <img src="img/mapping-example%2520-%2520conflating.png" alt="A mapping example illustrating the second approach">
<div style="text-align: center;">
<a href="#figure_mapping_example_conflating">Figure 2</a>. A mapping example conflating blank nodes in the same resource. The used and generated resources have the same identifier.
</div>
@@ -761,7 +761,7 @@
<p>Some of the terms of the list are still under discussion: <code>dct:replaces</code> and <code>dct:isVersionOf</code>.</p>
</div>
<p>
- </p><div id="list_of_direct_terms" align="center">
+ </p><div id="list_of_direct_terms">
<table>
<caption> <a href="#list_of_direct_terms"> Table 3:</a> Direct mappings </caption>
<tbody>
@@ -904,7 +904,7 @@
latter
proposes to separate all of them. Thus, the mapping produces
provenance that complies with the current definition of entity but
- it does not comply with all the PROV constraints [<cite><a href="#bib-PROV-CONSTRAINTS" rel="biblioentry" class="bibref">PROV-CONSTRAINTS</a></cite>].
+ it does not comply with all the PROV constraints [<cite><a href="#bib-PROV-CONSTRAINTS" class="bibref">PROV-CONSTRAINTS</a></cite>].
<p></p>
<p>
Some properties have been found to be superproperties of certain prov concepts. These can be seen below in <a href="#list_of_direct_mappings2">Table 4</a>:
@@ -913,7 +913,7 @@
-->
</p>
- <div id="list_of_direct_mappings2" align="center">
+ <div id="list_of_direct_mappings2">
<table>
<caption> <a href="#list_of_direct_mappings2"> Table 4:</a> Direct mappings (2) </caption>
<tbody>
@@ -945,7 +945,7 @@
<a href="#list_of_direct_mappings_no_prov_core">Table 5</a> enumerates the mapping of the <code>dct</code> properties that map to inverse relationships in PROV. These
have been separated in a different table because they don't belong to the core of PROV.
</p>
- <div id="list_of_direct_mappings_no_prov_core" align="center">
+ <div id="list_of_direct_mappings_no_prov_core" >
<table>
<caption> <a href="#list_of_direct_mappings_no_prov_core"> Table 5:</a> Direct mappings to the PROV terms not included in the core </caption>
<tbody>
@@ -1356,7 +1356,7 @@
<a href="#figure_cleanup1">Figure 3</a> shows a graphical representation of the pattern:
<div id="figure_cleanup1" class="figure" style="text-align: center;">
- <img src="img/cleanup1.png">
+ <img src="img/cleanup1.png" alt="Gathering complementing properties to conflate blank nodes">
<div style="text-align: center;">
<a href="#figure_cleanup1">Figure 3</a>. Gathering complementing properties to conflate blank nodes.
</div>
@@ -1374,7 +1374,7 @@
respective usage and generation, both activities share the same
blank node (<code>_:created_entity</code>).
</p><div id="figure_cleanup2" class="figure" style="text-align: center;">
- <img src="img/cleanup2.png">
+ <img src="img/cleanup2.png" alt="Sorting the activities by date to conflate blank nodes">
<div style="text-align: center;">
<a href="#figure_cleanup2">Figure 4</a>. Sorting the activities by date to conflate blank nodes.
</div>
@@ -1564,8 +1564,8 @@
<td><b id="term_relation">dct:relation</b></td>
<td>Provenance </td>
<td>A related resource. This relationship is very broad and could relate either provenance resources or not.
- Therefore it could be seen as a superproperty of <code>prov:wasDerivedFrom</code>, <code>prov:wasInfluencedBy</code>, <code>prov:alternateOf</code>, <code>prov:specializationOf</code>, etc. Thus there is no direct mapping.</td><td>
- </td></tr>
+ Therefore it could be seen as a superproperty of <code>prov:wasDerivedFrom</code>, <code>prov:wasInfluencedBy</code>, <code>prov:alternateOf</code>, <code>prov:specializationOf</code>, etc. Thus there is no direct mapping.</td>
+ </tr>
</tbody></table>
<p></p>
</div>