--- a/dc-note/dc-note.html Tue Dec 11 10:35:15 2012 +0000
+++ b/dc-note/dc-note.html Tue Dec 11 11:01:08 2012 +0000
@@ -623,8 +623,11 @@
</p><p>
<b>Derivation Terms (How?):</b> This category contains derivation related terms.
Resources are often derived from other resources. In this case, the original resource becomes part of the provenance
- record of the derived resource. Derivations can be further classified as <code>dct:isVersionOf, dct:isFormatOf, dct:replaces, dct:source</code>.
- <code>dct:references</code> is a weaker relation, but it can be assumed that a referenced resource influenced the described resource
+ record of the derived resource. Derivations can be further
+ classified as <code>dct:isVersionOf, dct:isFormatOf, dct:replaces,
+ dct:source</code>. On the other hand, <code>dct:references</code>
+ is a weaker relation, but it can be assumed that a referenced
+ resource influenced the described resource
and therefore it is relevant for its provenance. The respective inverse properties do not necessarily contribute to
the provenance of the described resource, e.g., a resource is usually not directly affected by being referenced or
by being used as a source – at most indirectly, as the validity state can change if a resource is replaced by a new
@@ -678,7 +681,7 @@
</table>
</div>
<p>
- This leaves one very special term: <i>provenance</i>. This term is defined as a "statement of any changes in ownership and
+ This leaves one very special term: <code>dct:provenance</code>. This term is defined as a "statement of any changes in ownership and
custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation" [[DCTERMS]],
which corresponds to the traditional definition of provenance for artworks. Despite being relevant for provenance,
this definition may overlap partially with almost half of the DCMI terms, which
@@ -750,8 +753,9 @@
<section>
<h3>What is ex:doc1? Entities in Dublin Core</h3>
<p>
- Consider the example metadata record shown at the beginning of this document (in <a href="#example1">example 1</a>). As a <code>dc</code>
- metadata record describes the resulting document as a whole,
+ Consider the example metadata record shown at the beginning of
+ this document (in <a href="#example1">example 1</a>). As a
+ Dublin Core metadata record describes the resulting 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.
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
@@ -759,8 +763,10 @@
has not changed. Generally, there are two approaches to deal with this issue:</p>
</p><p>
1) To create new instances of entities, typically as blank nodes, that are all related to the original
- document by means of <code>prov:specializationOf</code>. This leads to bloated and not very intuitive data models, e.g. think
- about the translation of a single <code>dct:publisher</code> statement, where anyone would expect to somehow find some activity and
+ document by means of <code>prov:specializationOf</code>.
+ This leads to verbose and not very intuitive data models, e.g. think
+ about the translation of a single <code>dct:publisher</code>
+ statement, where one would expect to somehow find some activity and
agent that are directly related to the document (as in <a href="#figure_mapping_example">Figure 1</a>).
</p><p>
<div id = "figure_mapping_example" class="figure" style="text-align: center;">
@@ -775,7 +781,7 @@
(<code>:_activity</code>). However, this representation leads to a misinterpretation of the <code>dct</code> statement, as shown in the example of
<a href="#figure_mapping_example_conflating">Figure 2</a>. The representation implies that <code>ex:doc1</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> (<code>prov:Entities</code> must exist before being used).
+ <code>_:activity</code> (PROV entities must be generated before being used).
</p><p>
<div id = "figure_mapping_example_conflating" class="figure" style="text-align: center;">
@@ -816,13 +822,13 @@
<tr>
<th>DC Term</th>
<th>Relation</th>
- <th>PROV Term</th>
+ <th>PROV-O Term</th>
<th>Rationale</th>
</tr>
<tr>
<td><b>dct:Agent</b></td>
<td>owl:equivalentClass</td>
- <td> prov:Agent.</td>
+ <td> prov:Agent</td>
<td>Both <code>dct:Agent</code> and <code>prov:Agent</code> refer to the same concept: a resource that has the power to act (which then has responsibility for an activity).</td>
</tr>
<tr>
@@ -887,8 +893,10 @@
<tr>
<td><b>dct:type</b></td>
<td>owl:equivalentProperty</td>
- <td>prov:type</td>
- <td>Both properties relate two resources in a similar way: the nature of the resource (or genre).</td>
+ <td>rdf:type</td>
+ <td>Both properties relate two resources in a similar
+ way: the nature of the resource (or genre). Mapping to
+ PROV-DM should use <code>prov:type<code>.</td>
</tr>
<tr>
<td><b>dct:created</b></td>
@@ -951,7 +959,7 @@
<caption> <a href="#list_of_direct_mappings2"> Table 4:</a> Direct mappings (2) </caption>
<tbody>
<tr>
- <th>PROV Term</th>
+ <th>PROV-O Term</th>
<th>Relation</th>
<th>DC Term</th>
<th>Rationale</th>
@@ -980,12 +988,13 @@
</p>
<div id="list_of_direct_mappings_no_prov_core" ALIGN="center">
<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>
+ <caption> <a
+ href="#list_of_direct_mappings_no_prov_core"> Table 5:</a> Direct mappings to the inverse PROV terms not included in the core </caption>
<tbody>
<tr>
- <th>PROV Term</th>
+ <th>DC Term</th>
<th>Relation</th>
- <th>DC Term</th>
+ <th>PROV-O Term</th>
<th>Rationale</th>
</tr>
<tr>
@@ -1062,26 +1071,26 @@
A creator is the agent associated with role CreatorRole in the CreationActivity that created a specialization of the entity (?document).
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
- prov:wasAttributedTo ?agent.
-
- ?agent a prov:Agent .
-
- _:activity a prov:Activity, prov:CreationActivity ;
- prov:wasAssociatedWith ?agent;
- prov:qualifiedAssociation [
- a prov:Association;
- prov:agent ?agent;
- prov:hadRole prov:CreatorRole .
- ].
-
- _:resulting_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasAttributedTo ?agent.
-
+ ?document a prov:Entity ;
+ prov:wasAttributedTo ?agent .
+
+ ?agent a prov:Agent .
+
+ _:activity a prov:Activity, prov:CreationActivity ;
+ prov:wasAssociatedWith ?agent ;
+ prov:qualifiedAssociation [
+ a prov:Association ;
+ prov:agent ?agent ;
+ prov:hadRole prov:CreatorRole .
+ ].
+
+ _:resulting_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasAttributedTo ?agent .
+
} WHERE {
- ?document dct:creator ?agent.
+ ?document dct:creator ?agent .
}
</pre>
</section>
@@ -1170,7 +1179,7 @@
_:created_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:qualifiedGeneration [
a prov:Generation ;
prov:atTime ?date ;
@@ -1200,7 +1209,7 @@
_:iss_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1230,7 +1239,7 @@
_:modified_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1260,7 +1269,7 @@
_:accepted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1290,7 +1299,7 @@
_:copyrighted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1319,7 +1328,7 @@
_:submitted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1364,7 +1373,7 @@
_:created_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
+ prov:generatedAtTime ?date;
prov:qualifiedGeneration [
a prov:Generation ;
prov:atTime ?date ;
@@ -1599,5 +1608,15 @@
We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo and Satya Sahoo for their feedback; and María Poveda and Idafen Santana Pérez for his help with the HTML generation.
</p>
</section>
+ <section class="appendix">
+ <h2>Changes since First Working Draft</h2>
+ <ul>
+ <li>Corrected table headers</li>
+ <li>dct:type mapped to rdf:type, not prov:type (which is not in PROV-O)</li>
+ <li>Minor indenting correction on SPARQL statements</li>
+ <li>Corrected prov:wasGeneratedAtTime to prov:generatedAtTime</li>
+ <li>Minor typesetting to highlight DC Terms more intuitively</li>
+ </ul>
+ </section>
</body>
-</html>
\ No newline at end of file
+</html>