--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Thu Apr 18 18:05:22 2013 +0200
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Thu Apr 18 18:51:21 2013 +0200
@@ -1467,22 +1467,16 @@
</section>
<section id="dct-datecopyrighted">
<h5><span class="secno">3.3.2.6 </span>dct:dateCopyrighted</h5>
+ By creating a resource we gain automatic copyright over it, so <code>_:usedEntity</code> is not required in this complex mapping.
<p></p><pre class="code">CONSTRUCT{
?document a prov:Entity .
- _:activity a prov:Activity, prov:Copyright ;
- prov:used _:usedEntity .
-
- # The “input”
- _:usedEntity a prov:Entity .
- prov:specializationOf ?document .
-
+ _:activity a prov:Activity, prov:Copyright ;
# The “output”
_:copyrightedEntity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:usedEntity ;
prov:qualifiedGeneration [
a prov:Generation ;
prov:atTime ?date ;
@@ -1490,8 +1484,7 @@
] .
} WHERE {
?document dct:dateCopyrighted ?date.
- }
- </pre><p></p>
+ }</pre>
</section>
<section id="dct-datesubmitted">
<h5><span class="secno">3.3.2.7 </span>dct:dateSubmitted</h5>
@@ -1536,12 +1529,13 @@
<section id="dct-replaces">
<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 "replace" Activity, which used a specialization of the replaced entity (<code>_:oldEntity</code>) and
- generated a specialization of the replacement (<code>_:newEntity</code>). Thus, <code>_:newEntity</code> was derived from
- <code>_:oldEntity</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).
+ There is a relation between two resources when the former replaces or displaces the latter.
+ However, we can't always assume the replacement is derived from the former resource, because the
+ replacement could have existed and been generated independently from the original (for instance if a
+ "Introduction to provenance" book replaces the "Provenance in a nutshell" book in a catalog).
+ Therefore the "replace" Activity uses a specialization of the replaced entity (<code>_:oldEntity</code>) and generated
+ a specialization of the replacement (<code>_:newEntity</code>). These specializations model the aspect of the resource
+ which is the subject of replacement, thus, <code>_:newEntity</code> was derived from <code>_:oldEntity</code>.
</p>
<p>
</p><pre class="code">CONSTRUCT{
@@ -1560,7 +1554,7 @@
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity;
prov:wasDerivedFrom _:oldEntity ;
- prov:alternateOf _oldEntity.
+ prov:alternateOf _:oldEntity.
} WHERE {
?document dct:replaces ?document2.
@@ -1916,7 +1910,7 @@
</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>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-DCTERMS">[DCTERMS]</dt><dd><a href="http://dublincore.org/documents/dcmi-terms/"><cite>DCMI Metadata Terms</cite></a>. 14 June 2012. URL: <a href="http://dublincore.org/documents/2012/06/14/dcmi-terms/">http://dublincore.org/documents/2012/06/14/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/2012/REC-owl2-overview-20121211/"><cite>OWL 2 Web Ontology Language: Overview</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-owl2-overview-20121211/">http://www.w3.org/TR/2012/REC-owl2-overview-20121211/</a>