--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 09 15:18:58 2013 +0200
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 09 18:51:53 2013 +0200
@@ -305,12 +305,12 @@
<p>
This document describes a partial mapping from Dublin Core Terms [<cite><a href="#bib-DCTERMS" class="bibref">DCTERMS</a></cite>] to the PROV-O OWL2 ontology [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>]. A substantial number of
terms in the Dublin Core vocabulary provide information about the provenance of a resource. The mapping is expressed partly by direct RDFS/OWL mappings between
- properties and classes, which can be found <a href="http://www.w3.org/ns/prov-dc-directmappings.ttl">here</a>.
+ properties and classes, which can be found here [<cite><a href="#bib-mapping" class="bibref">PROV-DC-DIRECT-MAPPINGS</a></cite>].
</p>
<p>
Some of the direct mappings can be refined, translating single Dublin Core Terms into an extended
representation of the provenance. Therefore, refinements of classes defined in PROV are needed to represent specific Dublin Core activities and roles.
- This set of PROV refinements can be accessed <a href="http://www.w3.org/ns/prov-dc-refinements.ttl">here</a>.
+ This set of PROV refinements can be accessed here [<cite><a href="#bib-refinements" class="bibref">PROV-DC-REFINEMENTS</a></cite>].
</p>
<p>
The PROV Document Overview [<cite><a href="#bib-PROV-OVERVIEW" class="bibref">PROV-OVERVIEW</a></cite>] describes the overall state of PROV, and should be read before other PROV documents.
@@ -410,12 +410,39 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#namespaces-1"><span class="secno">1.1 </span>Namespaces</a></li><li class="tocline"><a class="tocxref" href="#structure-of-this-document"><span class="secno">1.2 </span>Structure of this document</a></li></ul></li><li class="tocline"><a class="tocxref" href="#preliminaries"><span class="secno">2. </span>Preliminaries</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#provenance-in-dublin-core"><span class="secno">2.1 </span>Provenance in Dublin Core</a></li><li class="tocline"><a class="tocxref" href="#entities-in-dublin-core"><span class="secno">2.2 </span>Entities in Dublin Core</a></li></ul></li><li class="tocline"><a class="tocxref" href="#mapping-from-dublin-core-to-prov"><span class="secno">3. </span>Mapping from Dublin Core to PROV</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#direct-mappings"><span class="secno">3.1 </span>Direct mappings</a></li><li class="tocline"><a class="tocxref" href="#prov-refinements"><span class="secno">3.2 </span>PROV refinements</a></li><li class="tocline"><a class="tocxref" href="#complex-mappings"><span class="secno">3.3 </span>Complex Mappings</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#entity-agent-mappings-who"><span class="secno">3.3.1 </span>Entity-Agent mappings (Who)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-creator"><span class="secno">3.3.1.1 </span> dct:creator</a></li><li class="tocline"><a class="tocxref" href="#dct-contributor"><span class="secno">3.3.1.2 </span>dct:contributor</a></li><li class="tocline"><a class="tocxref" href="#dct-publisher"><span class="secno">3.3.1.3 </span>dct:publisher</a></li></ul></li><li class="tocline"><a class="tocxref" href="#entity-date-mappings-when"><span class="secno">3.3.2 </span>Entity-Date mappings (When)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-created"><span class="secno">3.3.2.1 </span> dct:created</a></li><li class="tocline"><a class="tocxref" href="#dct-issued"><span class="secno">3.3.2.2 </span>dct:issued</a></li><li class="tocline"><a class="tocxref" href="#dct-modified"><span class="secno">3.3.2.3 </span>dct:modified</a></li><li class="tocline"><a class="tocxref" href="#dct-dateaccepted"><span class="secno">3.3.2.4 </span>dct:dateAccepted</a></li><li class="tocline"><a class="tocxref" href="#dct-datecopyrighted"><span class="secno">3.3.2.5 </span>dct:dateCopyrighted</a></li><li class="tocline"><a class="tocxref" href="#dct-datesubmitted"><span class="secno">3.3.2.6 </span>dct:dateSubmitted</a></li></ul></li><li class="tocline"><a class="tocxref" href="#entity-entity-mappings-how"><span class="secno">3.3.3 </span>Entity-Entity mappings (How)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-replaces"><span class="secno">3.3.3.1 </span>dct:replaces</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#cleanup"><span class="secno">3.4 </span>Cleanup</a></li><li class="tocline"><a class="tocxref" href="#list-of-terms-excluded-from-the-mapping"><span class="secno">3.5 </span>List of terms excluded from the mapping</a></li><li class="tocline"><a class="tocxref" href="#mapping-from-prov-to-dc"><span class="secno">3.6 </span>Mapping from PROV to DC</a></li></ul></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#changes-since-second-public-working-draft"><span class="secno">B. </span>Changes Since Second Public Working Draft</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#namespaces-1"><span class="secno">1.1 </span>Namespaces URIs</a></li><li class="tocline"><a class="tocxref" href="#structure-of-this-document"><span class="secno">1.2 </span>Structure of this document</a></li></ul></li><li class="tocline"><a class="tocxref" href="#preliminaries"><span class="secno">2. </span>Preliminaries</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#provenance-in-dublin-core"><span class="secno">2.1 </span>Provenance in Dublin Core</a></li><li class="tocline"><a class="tocxref" href="#entities-in-dublin-core"><span class="secno">2.2 </span>Entities in Dublin Core</a></li></ul></li><li class="tocline"><a class="tocxref" href="#mapping-from-dublin-core-to-prov"><span class="secno">3. </span>Mapping from Dublin Core to PROV</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#direct-mappings"><span class="secno">3.1 </span>Direct mappings</a></li><li class="tocline"><a class="tocxref" href="#prov-refinements"><span class="secno">3.2 </span>PROV refinements</a></li><li class="tocline"><a class="tocxref" href="#complex-mappings"><span class="secno">3.3 </span>Complex Mappings</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#entity-agent-mappings-who"><span class="secno">3.3.1 </span>Entity-Agent mappings (Who)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-creator"><span class="secno">3.3.1.1 </span> dct:creator</a></li><li class="tocline"><a class="tocxref" href="#dct-contributor"><span class="secno">3.3.1.2 </span>dct:contributor</a></li><li class="tocline"><a class="tocxref" href="#dct-publisher"><span class="secno">3.3.1.3 </span>dct:publisher</a></li></ul></li><li class="tocline"><a class="tocxref" href="#entity-date-mappings-when"><span class="secno">3.3.2 </span>Entity-Date mappings (When)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-created"><span class="secno">3.3.2.1 </span> dct:created</a></li><li class="tocline"><a class="tocxref" href="#dct-issued"><span class="secno">3.3.2.2 </span>dct:issued</a></li><li class="tocline"><a class="tocxref" href="#dct-modified"><span class="secno">3.3.2.3 </span>dct:modified</a></li><li class="tocline"><a class="tocxref" href="#dct-dateaccepted"><span class="secno">3.3.2.4 </span>dct:dateAccepted</a></li><li class="tocline"><a class="tocxref" href="#dct-datecopyrighted"><span class="secno">3.3.2.5 </span>dct:dateCopyrighted</a></li><li class="tocline"><a class="tocxref" href="#dct-datesubmitted"><span class="secno">3.3.2.6 </span>dct:dateSubmitted</a></li></ul></li><li class="tocline"><a class="tocxref" href="#entity-entity-mappings-how"><span class="secno">3.3.3 </span>Entity-Entity mappings (How)</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dct-replaces"><span class="secno">3.3.3.1 </span>dct:replaces</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#cleanup"><span class="secno">3.4 </span>Cleanup</a></li><li class="tocline"><a class="tocxref" href="#list-of-terms-excluded-from-the-mapping"><span class="secno">3.5 </span>List of terms excluded from the mapping</a></li><li class="tocline"><a class="tocxref" href="#mapping-from-prov-to-dc"><span class="secno">3.6 </span>Mapping from PROV to DC</a></li></ul></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#changes-since-second-public-working-draft"><span class="secno">B. </span>Changes Since Second Public Working Draft</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
<section id="introduction">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p>
+ The Dublin Core Metadata Initiative (DCMI) [<cite><a href="#bib-DCMI" class="bibref">DCMI</a></cite>] provides a core
+ metadata vocabulary (commonly referred to as Dublin Core) for simple
+ and generic resource descriptions[<cite><a href="#bib-DCTERMS" class="bibref">DCTERMS</a></cite>]. The original Dublin Core Metadata
+ Element Set was created in 1995 and contains fifteen broadly defined
+ properties that are still in use. Properties identified using the
+ original namespace URI <a href="http://purl.org/dc/elements/1.1/">http://purl.org/dc/elements/1.1/</a> have no
+ specified ranges, meaning that arbitrary values can be used as
+ objects. In order to assign ranges, DCMI replicated the fifteen
+ properties using the namespace URI <a href="http://purl.org/dc/terms/">http://purl.org/dc/terms/</a>. Additional
+ properties and classes beyond the original fifteen were coined using
+ this namespace URI. In this document, properties and classes using the
+ /terms/ namespace URI are referred to, simply, as DC Terms.
+ </p>
+<p>
+ This document defines a mapping between the DC Terms and the PROV
+ Ontology (PROV-O) [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>], which defines an OWL2 Ontology encoding the
+ PROV Data Model [<cite><a href="#bib-PROV-DM" class="bibref">PROV-DM</a></cite>]. The PROV vocabulary and data model are focused on expressing actions
+ and resource states in a provenance chain rather than on describing
+ resources in a general sense. The Dublin Core vocabulary is focused on
+ describing resources in a general sense, but a substantial number of
+ terms in the vocabulary provide information related to the provenance
+ of the resource. Mapping statements using Dublin Core into statements
+ using PROV makes the contained provenance information explicit. This mapping has been
+ designed for several purposes:
+ </p>
+ <!--
+ <p>
The Dublin Core Metadata Initiative (DCMI) [<cite><a href="#bib-DCMI" class="bibref">DCMI</a></cite>] provides a core metadata vocabulary (commonly referred to as Dublin Core) for simple and generic resource descriptions.
The original element set (DC elements) was created in 1995 and contains 15 broadly-defined elements still in use.
The core elements have no range specification, and arbitrary values can be used as objects. The core elements have been
@@ -430,7 +457,8 @@
<p>
This document defines a mapping between the DC Terms and the PROV Ontology (PROV-O) [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>], which defines an OWL2 Ontology encoding
the PROV Data Model [<cite><a href="#bib-PROV-DM" class="bibref">PROV-DM</a></cite>]. The mapping has been designed for several purposes:
- </p><ol>
+ </p>-->
+ <ol>
<li><b>Bridge the gap between the DC and PROV communities</b>, in order to provide valuable insights
into the different characteristics of both data models.</li>
<li>Help developers to <b>derive PROV data from the large amount of Dublin Core data</b> available on the web, improving interoperability between DC and PROV
@@ -441,17 +469,17 @@
<p>
</p><section id="namespaces-1">
- <h3 id="namespaces"><span class="secno">1.1 </span>Namespaces</h3>
- <p>The namespaces used through the document can be seen in <a href="#ns"> Table 2</a> below:
+ <h3 id="namespaces"><span class="secno">1.1 </span>Namespaces URIs</h3>
+ <p>The namespace URIs used in this document can be seen in <a href="#ns"> Table 2</a>:
</p><div id="ns" >
<table style="margin-left: auto; margin-right: auto;">
- <caption> <a href="#ns"> Table 2</a>: Namespaces used in the document </caption>
+ <caption> <a href="#ns"> Table 2</a>: Namespaces URIs used in the document </caption>
<tbody>
- <tr><td><b>prefix</b></td><td><b>Namespace IRI</b></td><td><b>Definition</b></td></tr>
- <tr><td>owl</td><td><http://www.w3.org/2002/07/owl#></td><td>The OWL namespace [<cite><a href="#bib-OWL2-OVERVIEW" class="bibref">OWL2-OVERVIEW</a></cite>].</td></tr>
- <tr><td>rdfs</td><td><http://www.w3.org/2000/01/rdf-schema#></td><td>The RDFS namespace[<cite><a href="#bib-RDFS" class="bibref">RDFS</a></cite>].</td></tr>
- <tr><td>prov</td><td><http://www.w3.org/ns/prov#></td><td>The PROV namespace [<cite><a href="#bib-PROV-DM" class="bibref">PROV-DM</a></cite>].</td></tr>
- <tr><td>dct</td><td><http://purl.org/dc/terms/></td><td>Dublin Core Terms namespace [<cite><a href="#bib-DCTERMS" class="bibref">DCTERMS</a></cite>].</td></tr>
+ <tr><td><b>prefix</b></td><td><b>Namespace IRI</b></td><td><b>Used for</b></td></tr>
+ <tr><td>owl</td><td><http://www.w3.org/2002/07/owl#></td><td>The OWL vocabulary [<cite><a href="#bib-OWL2-OVERVIEW" class="bibref">OWL2-OVERVIEW</a></cite>].</td></tr>
+ <tr><td>rdfs</td><td><http://www.w3.org/2000/01/rdf-schema#></td><td>The RDFS vocabulary[<cite><a href="#bib-RDFS" class="bibref">RDFS</a></cite>].</td></tr>
+ <tr><td>prov</td><td><http://www.w3.org/ns/prov#></td><td>The PROV vocabulary [<cite><a href="#bib-PROV-DM" class="bibref">PROV-DM</a></cite>].</td></tr>
+ <tr><td>dct</td><td><http://purl.org/dc/terms/></td><td>The DCMI /terms/ vocabulary [<cite><a href="#bib-DCTERMS" class="bibref">DCTERMS</a></cite>].</td></tr>
<!--<tr><td>dc</td><td><http://purl.org/dc/elements/1.1/></td><td>Dublin Core elements namespace [[DCTERMS]]</td></tr>-->
<tr><td>ex</td><td><http://example.org></td><td>Application-dependent URIs. Used in the examples of the document.</td></tr>
</tbody>
@@ -481,7 +509,7 @@
</li>
<li><a href="#complex-mappings">Section 3.3</a> defines <b>complex mappings</b>. These mappings make use of the refinements introduced in <a href="#prov-refinements">Section 3.2</a> and combine them
in order to derive an enhanced provenance chain.
- <!--Since the mapping produces blank nodes for each DC statement, a clean-up phase with strategies for reducing the blank nodes is also necessary.-->
+ <!--Since the mapping produces blank nodes for each DC statement, a cleanup phase with strategies for reducing the blank nodes is also necessary.-->
</li>
<li>Due to the way in which the complex mappings are defined, blank nodes are produced for each DC statement. <a href="#cleanup">Section 3.4 </a>
introduces some strategies on how to reduce the amount of blank nodes.
@@ -520,8 +548,8 @@
</p>
<!-- A total of 25 out of 55 terms can be considered provenance related.-->
<p>
- <b> Descriptive Terms (What?):</b> This category contains all the terms describing a resource without refering to its provenance (a total of 30 out of 55 terms).
- Some examples are the <code>dct:title</code>, <code> dct:abstract</code> or <code>dct:description</code> of a resource, the <code>dct:format</code> in which the resource can be found, etc.
+ <b> Descriptive Terms (What?):</b> This category contains all the terms describing a resource without referring to its provenance (a total of 30 out of 55 terms).
+ Some examples are the <code>dct:title</code>, <code> dct:abstract</code>, the <code>dct:description</code> of a resource or the <code>dct:format</code> in which the resource can be found.
</p>
<p>
<b>Agency Terms (Who?):</b> This category contains agent related terms. All properties have <code>dct:Agent</code> as range,
@@ -692,7 +720,7 @@
<p></p><p>
Since the first option provides a correct interpretation of the DC statements, it has been chosen as the approach for the complex mapping defined in this document..
Blank nodes are used for the mapping, although any naming mechanism could be provided if necessary,
- leaving the conflating of nodes to the clean-up phase.
+ leaving the conflating of nodes to the cleanup phase.
</p>
</section>
</section>
@@ -713,7 +741,7 @@
<section id="direct-mappings">
<h3><span class="secno">3.1 </span>Direct mappings</h3>
<p>
- The direct mappings relate the DC Terms to the PROV binary relationships by using the integration mechanisms of RDF.
+ The direct mappings [<cite><a href="#bib-mapping" class="bibref">PROV-DC-DIRECT-MAPPINGS</a></cite>] relate the DC Terms to the PROV binary relationships by using the integration mechanisms of RDF.
PROV applications will be able to interoperate with these DC statements by applying means of OWL 2 RL reasoning, (i.e.,
they will be able to understand DC statements). <!--The direct mappings also
contribute to the formal definition of the vocabularies by translating them to PROV.--></p>
@@ -919,7 +947,7 @@
</div>
<p>
<a href="#list_of_direct_mappings_no_prov_core">Table 5</a> enumerates the mapping of the DC terms 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.
+ have been separated in a different table because they do not belong to the core of PROV.
</p>
<div id="list_of_direct_mappings_no_prov_core">
<table style="margin-left: auto; margin-right: auto;">
@@ -951,7 +979,8 @@
<section id="prov-refinements">
<h3><span class="secno">3.2 </span>PROV refinements</h3>
<p>
- In order to produce complex mappings for the DC terms, we need specific subclasses extending the PROV ontology. These subclases
+ In order to produce complex mappings for the DC terms, we need specific subclasses extending the PROV ontology [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>].
+ These subclases [<cite><a href="#bib-refinements" class="bibref">PROV-DC-REFINEMENTS</a></cite>]
are designed to qualify the DC properties in the complex mappings. For example, a <code>dc:publisher</code> relationship implies a "Publish"
activity which used some entity to be published, produced a published entity and was associated with a publisher.
The PROV extensions for Dublin Core can be seen below:
@@ -980,7 +1009,7 @@
always needed, and it is the choice of the implementer whether to use them or not depending on the use case. It is also important to note that not all the
direct mappings have a complex mapping associated, just those which imply a specific activity: creation, publication, etc.
The complex mappings are provided in form of SPARQL CONSTRUCT queries, i.e., queries that describe a
- resulting RDF graph based on another RDF graph found in the original data. We divide the queries in different categories:
+ resulting RDF graph based on another RDF graph found in the original data. We divide the queries into different categories:
</p>
<section id="entity-agent-mappings-who">
<h4><span class="secno">3.3.1 </span>Entity-Agent mappings (Who)</h4>
@@ -995,7 +1024,7 @@
where the variables are placeholders that are filled with the values found in the data.
The mapping corresponds to the graph in <a href="#figure_mapping_example">Figure 1</a> (with small changes
for creator and rightsHolder). With this mapping,
- the difference in the complexity becomes obvious. Many blank nodes are created, so a subsequent clean-up phase that relates them and provides stable
+ the difference in the complexity becomes obvious. Many blank nodes are created, so a subsequent cleanup phase that relates them and provides stable
URIs for the entities is required. Depending on the implementation, URIs can also be coined here for every specialization.
<!--Sometimes URIs for the specializations are also available and simply not exposed to the Dublin Core record.-->
The implementation proposed in this document is an example that works conservatively. The assumption is that no further
@@ -1096,9 +1125,11 @@
Dates often correspond with a who-property, e.g., creator and created or publisher and issued.
Therefore, they lead to similar complex patterns (associating a date to each activity instead of an agent).
When using Dublin Core terms, it is usual to see that a resource is annotated with several <code>dct</code> assertions like creator, publisher,
- issued, date, etc. In this section each term is treated independently. It is important to note that since the range for dates in Dublin Core is a
- <code>rdfs:Literal</code> and <code>xsd:dateTime</code> for the <code>prov:atTime</code> property, the mapping is only valid for those literals
- that are <code>xsd:dateTime</code>.
+ issued, date, etc. In this section each term is treated independently.
+ It is important to note that since the range for DC date properties is
+ <code>rdfs:Literal</code>, and the range of the <code>prov:atTime</code> property is the class
+ of literals with the datatype <code>xsd:dateTime</code>, the mapping is only valid
+ for those literals that have the datatype <code>xsd:dateTime</code>.
</p>
<section id="dct-created">
@@ -1278,7 +1309,7 @@
<section id="entity-entity-mappings-how">
<h4><span class="secno">3.3.3 </span>Entity-Entity mappings (How)</h4>
<p>
- In Dublin Core, most of the properties relating entities to other entities don't describe the involvement of a specific activity
+ In Dublin Core, most of the properties relating entities to other entities do not imply activities related to provenance
(e.g., <code>dct:format</code>, <code>dct:source</code> or <code>isVersionOf</code>).
The only exception is <code>dct:replaces</code>, further explained below.
@@ -1287,9 +1318,9 @@
<h5 id="term_replaces"><span class="secno">3.3.3.1 </span>dct:replaces</h5>
<p>
There is a relation between two resources when the former replaces or displaces the latter. The replacement is
- the result of a "search and replace" Activity, which used a specialization of the replaced entity (<code>_:old_entity</code>) and
- produced a specialization of the replacement (<code>_:new_entity</code>). Thus, <code>_:new_entity</code> was derived from
- <code>_:old_entity</code>, as it couldn't have existed without it. However, the derivation relationship cannot always be applied between the original entities, because they
+ the result of a "replace" Activity, which used a specialization of the replaced entity (<code>_:old_entity</code>) and
+ generated a specialization of the replacement (<code>_:new_entity</code>). Thus, <code>_:new_entity</code> was derived from
+ <code>_:old_entity</code>, as it could not have existed without it. However, the derivation relationship cannot always be applied between the original entities, because they
could have existed before the replacement took place (for example, if a book replaces another in a catalog we cannot say that it was
derived from it).
</p>
@@ -1324,8 +1355,8 @@
<section id="cleanup">
<h3><span class="secno">3.4 </span>Cleanup</h3>
<p>
- The clean-up phase depends on how implementers interpret the described resources. The approach presented in this document
- leads to the proliferation of blank nodes. Blank nodes could be renamed to specific identifiers
+ The cleanup phase aims to reduce the number of blank nodes produced by the complex mappings. This depends on how implementers interpret the
+ described resources. Blank nodes could be renamed to specific identifiers
by the implementer, in order to avoid obtaining additional blank nodes when reapplying the construct queries presented
in the previous section.</p>
<p> Providing a set of rules to conflate the blank nodes is not in the scope of this document. However, the group has
@@ -1386,7 +1417,7 @@
<section id="list-of-terms-excluded-from-the-mapping">
<h3><span class="secno">3.5 </span>List of terms excluded from the mapping</h3>
<a href="#list-of-terms-excluded-from-the-mapping"> Table 6</a> lists the terms excluded from the mapping,
- either because thay are not suitable or because they don't represent provenance information.
+ either because thay are not suitable or because they do not represent provenance information.
<p>
</p><table>
@@ -1403,7 +1434,7 @@
</tr><tr>
<td><b id="term_accrualMethod"><a href="http://purl.org/dc/terms/accrualMethod">dct:accrualMethod</a></b></td>
<td>Descriptive Metadata</td>
- <td>Method by which items are added to a collection. It doesn't describe the action itself, so it is out of the scope of the mapping.</td>
+ <td>Method by which items are added to a collection. It does not describe the action itself, so it is out of the scope of the mapping.</td>
</tr><tr>
<td><b id="term_accrualPeriodicity"><a href="http://purl.org/dc/terms/accrualPeriodicity">dct:accrualPeriodicity</a></b></td>
<td>Descriptive metadata</td>
@@ -1548,8 +1579,7 @@
The mapping from PROV to Dublin Core is not part of this note. If the refinements proposed in this document are used, then the inverse of the complex mapping
patterns can be applied.
However, if the refinements are not used then only a few Dublin Core statements can be inferred from plain PROV statements.
- For example, when mapping dates only unqualified properties can be extracted,
- as there is no information if an activity with an associated date is a creation or a modification or a publication. Likewise, the agents
+ For example, when mapping dates there is no information to guess whether an activity with an associated date is a creation, a modification or a publication. Likewise, the agents
involved cannot be mapped to creators, contributors, or publishers. While Dublin Core includes provenance information, its focus
lies on the broader description of resources. PROV models a provenance chain, but it provides almost no information about the involved
resources themselves.
@@ -1561,7 +1591,7 @@
<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
This document is the result of a collaboration between the Provenance Working Group and the Dublin Core Metadata Initiative.
- The editors extend special thanks to Antoine Isaac, Ivan Herman, Timothy Lebo, Luc Moreau, Paul Groth and Satya Sahoo for their feedback; and María Poveda and Idafen Santana for their help with the HTML generation.
+ The editors extend special thanks to Antoine Isaac, Ivan Herman, Timothy Lebo, Luc Moreau, Paul Groth, Satya Sahoo and Tom Baker for their feedback; and María Poveda and Idafen Santana for their help with the HTML generation.
</p>
<p>
Members of the Provenance Working Group at the time of publication of this document were: Ilkay Altintas (Invited expert), Reza B'Far (Oracle Corporation), Khalid Belhajjame (University of Manchester), James Cheney (University of Edinburgh, School of Informatics), Sam Coppens (iMinds - Ghent University), David Corsar (University of Aberdeen, Computing Science), Stephen Cresswell (The National Archives), Tom De Nies (iMinds - Ghent University), Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland), Simon Dobson (Invited expert), Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)), Kai Eckert (Invited expert), Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER), James Frew (Invited expert), Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)), Daniel Garijo (Ontology Engineering Group, Universidad Politécnica de Madrid), Yolanda Gil (Invited expert), Ryan Golden (Oracle Corporation), Paul Groth (Vrije Universiteit), Olaf Hartig (Invited expert), David Hau (National Cancer Institute, NCI), Sandro Hawke (W3C/MIT), Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh), Ivan Herman, (W3C/ERCIM), Ralph Hodgson (TopQuadrant), Hook Hua (Invited expert), Trung Dong Huynh (University of Southampton), Graham Klyne (University of Oxford), Michael Lang (Revelytix, Inc.), Timothy Lebo (Rensselaer Polytechnic Institute), James McCusker (Rensselaer Polytechnic Institute), Deborah McGuinness (Rensselaer Polytechnic Institute), Simon Miles (Invited expert), Paolo Missier (School of Computing Science, Newcastle university), Luc Moreau (University of Southampton), James Myers (Rensselaer Polytechnic Institute), Vinh Nguyen (Wright State University), Edoardo Pignotti (University of Aberdeen, Computing Science), Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute), Carl Reed (Open Geospatial Consortium), Adam Retter (Invited Expert), Christine Runnegar (Invited expert), Satya Sahoo (Invited expert), David Schaengold (Revelytix, Inc.), Daniel Schutzer (FSTC, Financial Services Technology Consortium), Yogesh Simmhan (Invited expert), Stian Soiland-Reyes (University of Manchester), Eric Stephan (Pacific Northwest National Laboratory), Linda Stewart (The National Archives), Ed Summers (Library of Congress), Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)), Ted Thibodeau (OpenLink Software Inc.), Curt Tilmes (National Aeronautics and Space Administration), Craig Trim (IBM Corporation), Stephan Zednik (Rensselaer Polytechnic Institute), Jun Zhao (University of Oxford), Yuting Zhao (University of Aberdeen, Computing Science).
@@ -1577,18 +1607,20 @@
</section>
<section class="appendix" id="references"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-DCMI">[DCMI]</dt><dd><a href="http://dublincore.org/"><cite>Dublin Core Metadata Initiative</cite></a>. URL: <a href="http://dublincore.org/">http://dublincore.org/</a>
-</dd><dt id="bib-DCTERMS">[DCTERMS]</dt><dd><a href="http://dublincore.org/documents/dcmi-terms/"><cite>Dublin Core Terms Vocabulary</cite></a>. 8 December 2010. URL: <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+</dd><dt id="bib-DCTERMS">[DCTERMS]</dt><dd><a href="http://dublincore.org/documents/dcmi-terms/"><cite>DCMI Metadata Terms</cite></a>. 8 December 2010. URL: <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+</dd><dt id="bib-refinements">[PROV-DC-REFINEMENTS]</dt><dd><a href="http://www.w3.org/ns/prov-dc-refinements.ttl"><cite>PROV-O refinements for Dublin Core file</cite></a>. 30 April 2013. URL: <a href="http://www.w3.org/ns/prov-dc-refinements.ttl">http://www.w3.org/ns/prov-dc-refinements.ttl</a>
+</dd><dt id="bib-mapping">[PROV-DC-DIRECT-MAPPINGS]</dt><dd><a href="http://www.w3.org/ns/prov-dc-directmappings.ttl"><cite>Dublin Core to PROV mapping file</cite></a>. 30 April 2013. URL: <a href="http://www.w3.org/ns/prov-dc-directmappings.ttl">http://www.w3.org/ns/prov-dc-directmappings.ttl</a>
</dd><dt id="bib-OWL2-OVERVIEW">[OWL2-OVERVIEW]</dt><dd>W3C OWL Working Group. <a href="http://www.w3.org/TR/2009/REC-owl2-overview-20091027/"><cite>OWL 2 Web Ontology Language: Overview</cite></a>. 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-overview-20091027/">http://www.w3.org/TR/2009/REC-owl2-overview-20091027/</a>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
-</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
+</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
+</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
</dd><dt id="bib-RDFS">[RDFS]</dt><dd>Dan Brickley; Ramanathan V. Guha. RDF Vocabulary Description Language 1.0: RDF Schema. 10 February 2004. W3C Recommendation.URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file