--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Thu Apr 18 11:10:37 2013 +0200
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Thu Apr 18 11:36:06 2013 +0200
@@ -658,34 +658,35 @@
<section id="entities-in-dublin-core">
<h3><span class="secno">2.2 </span>Entities in Dublin Core</h3>
<p>
- Consider the example metadata record below (<a href="#example1">Example 1</a>), where a document (<code>ex:doc1</code>) is described
+ Consider the example metadata record below (<a href="#example1">Example 1</a>), where a document (<code>ex:prov-dc-20130312</code>) is described
with several DC statements:
</p>
<p>
<a href="#example1">Example 1</a>: a simple metadata record in Turtle format [<cite><a href="#bib-TURTLE" class="bibref">Turtle</a></cite>]:
</p><div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example" id="example1">
-ex:doc1 dct:title "A mapping from Dublin Core..." ;
- dct:creator ex:kai, ex:daniel, ex:simon, ex:michael ;
- dct:created "2012-02-28" ;
- dct:publisher ex:w3c ;
- dct:issued "2012-02-29" ;
- dct:subject ex:dublincore ;
- dct:replaces ex:doc2 ;
- dct:format "HTML" .</pre></div>
+ex:prov-dc-20130312 dct:title "A mapping from Dublin Core..." ;
+ dct:creator ex:kai, ex:daniel, ex:simon, ex:michael ;
+ dct:created "2012-02-28" ;
+ dct:publisher ex:w3c ;
+ dct:issued "2012-02-29" ;
+ dct:subject ex:dublincore ;
+ dct:replaces ex:prov-dc-20121211 ;
+ dct:format "HTML" .
+</pre></div>
In <a href="#example1">Example 1</a>, <code>dct:title</code>, <code>dct:subject</code> and <code>dct:format</code>
- are <i>descriptions</i> of the resource <code>ex:doc1</code>.
+ are <i>descriptions</i> of the resource <code>ex:prov-dc-20130312</code>.
They do not provide any information on how the resource was created or modified in the past.
On the other hand, some statements imply provenance-related information. For example <code>dct:creator</code>
implies that the document has been created and refers to an author. Similarly, the existence
of the <code>dct:issued</code> date implies that the document has been published. This information is redundantly
implied by the <code>dct:publisher</code> statement as well. Finally, <code>dct:replaces</code> relates
- <code>ex:doc1</code> to the document <code>ex:doc2</code>, a previous resource representing the mapping.<!-- which probably had some kind of influence on <code>ex:doc1</code>.-->
+ <code>ex:prov-dc-20130312</code> to the document <code>ex:prov-dc-20121211</code>, a previous resource representing the mapping.<!-- which probably had some kind of influence on <code>ex:doc1</code>.-->
<p></p>
As a DC metadata record describes the document as a whole,
- it is not clear how this document relates to the different states that the document had until it reached its final state.
+ it is not clear how this document relates to the different stages the document underwent until it reached its final state.
For example, a document may have a <code>dct:created</code> date and a <code>dct:issued</code> date. According to
- the PROV ontology, the activity of issuing a document involves two different states of the document: the document before it was issued
- and the issued document. Each of these states correspond to a different <code>prov:specializationOf</code> of the document. Generally,
+ the PROV ontology, the activity of issuing a document involves two different states of the document: <i>before</i> and <i>after</i> publication.
+ Each of these states correspond to a different <code>prov:specializationOf</code> of the document. Generally,
there are two approaches to deal with this issue:<p></p>
<p></p>
<p>
@@ -695,7 +696,7 @@
having a publisher implies a "Publish" activity (represented with a blank node), which is related to the <code>ex:publisher</code> agent. The
activity must have taken as input the document to be published (<code>:_usedEntity</code>, which is a <code>prov:specializationOf</code> the
resource we are describing), and generated the published resource (<code>:_resultingEntity</code>). <code>:_resultingEntity</code> is also a
- <code>prov:specializationOf</code> the resource <code>ex:doc1</code>, as it describes the document after a particular publication.
+ <code>prov:specializationOf</code> the resource <code>ex:prov-dc-20130312</code>, as it describes the document after a particular publication.
</p><p>
</p><div id="figure_mapping_example" style="text-align: center;">
<img src="img/example1.svg" alt="A mapping example creating blank nodes for each state of the resource">
@@ -706,9 +707,9 @@
</div>
</div>
<p></p><p>
- 2) Adopt the original resource (<code>ex:doc1</code>) as the <code>prov:Entity</code> used and then generated by the Publish activity
+ 2) Adopt the original resource (<code>ex:prov-dc-20130312</code>) as the <code>prov:Entity</code> used and then generated by the Publish activity
(<code>:_activity</code>). However, this representation leads to a misinterpretation of the DC statement, as shown in the example of
- <a href="#figure_mapping_example_conflating">Figure 2</a>. The representation implies that <code>ex:doc1</code>
+ <a href="#figure_mapping_example_conflating">Figure 2</a>. The representation implies that <code>ex:prov-dc-20130312</code>
was generated by <code>_:activity</code> and then used by <code>_:activity</code> afterwards, instead of being used and then being generated by
<code>_:activity</code> (PROV entities must exist before being used).
@@ -718,7 +719,7 @@
<div style="text-align: center;">
<a href="#figure_mapping_example_conflating">Figure 2</a>. A mapping example conflating blank nodes within the same resource.
The used and generated resources have the same identifier. This example is an <b>invalid translation</b> of the <code>dct:publisher</code>
- statement (as it implies that <code>ex:doc1</code> was generated by <code>_:activity</code> and then used by the same activity).
+ statement. <!--(as it implies that <code>ex:prov-dc-20130312</code> was generated by <code>_:activity</code> and then used by the same activity).-->
</div>
</div>
<p></p><p>
@@ -1004,9 +1005,9 @@
</table>
</div>
It is worth mentioning that applying the direct mappings to a metadata record such as <a href="#example1">example 1</a> will infer that
- the resource (<code>ex:doc1</code>) was <code>prov:generatedAtTime</code> at two different times (two generation dates are associated to the document:
+ the resource (<code>ex:prov-dc-20130312</code>) was <code>prov:generatedAtTime</code> at two different times (two generation dates are associated to the document:
<code>dct:created</code> and <code>dct:issued</code>). This is valid, since from the PROV
- point of view the "creation" and "issue" activities generate new entities. DC, on the other hand, groups those two intermediate entities under the same resource (<code>ex:doc1</code>), creating the record exposed
+ point of view the "creation" and "issue" activities generate new entities. DC, on the other hand, groups those two intermediate entities under the same resource (<code>ex:prov-dc-20130312</code>), creating the record exposed
in <a href="#example1">Example 1</a>. This approach is supported by PROV but it does not comply with all the PROV
constraints [<cite><a href="#bib-PROV-CONSTRAINTS" class="bibref">PROV-CONSTRAINTS</a></cite>].
<p></p>
@@ -1602,8 +1603,8 @@
list the classes and properties excluded from the mapping,
either because thay are not suitable or because they do not represent provenance information.
- <table>
- <caption> <a href="#list-of-terms-excluded-from-the-mapping"> Table 8:</a> List of classes excluded from the mapping </caption>
+ <table id="list-of-terms-excluded-from-the-mapping-classes">
+ <caption> <a href="#list-of-terms-excluded-from-the-mapping-classes"> Table 8:</a> List of classes excluded from the mapping </caption>
<tbody>
<tr>
<th>DC Term</th>
@@ -1669,8 +1670,8 @@
</tbody>
</table>
- <table id="list-of-terms-excluded-from-the-mapping-props">
- <caption> <a href="#list-of-terms-excluded-from-the-mapping-props"> Table 9:</a> List of properties excluded from the mapping </caption>
+ <table id="list-of-terms-excluded-from-the-mapping-properties">
+ <caption> <a href="#list-of-terms-excluded-from-the-mapping-properties"> Table 9:</a> List of properties excluded from the mapping </caption>
<tbody>
<tr>
<td><b id="term_abstract"><a href="http://purl.org/dc/terms/abstract">dct:abstract</a></b></td>