--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 23 02:19:18 2013 +0200
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 23 02:36:07 2013 +0200
@@ -1227,9 +1227,9 @@
prov:wasGeneratedBy _:activity;
prov:wasAttributedTo ?agent.
- } WHERE {
- ?document dct:creator ?agent.
- }
+} WHERE {
+ ?document dct:creator ?agent.
+}
</pre>
</section>
<section id="dct-contributor">
@@ -1255,9 +1255,9 @@
prov:wasGeneratedBy _:activity;
prov:wasAttributedTo ?agent.
- } WHERE {
- ?document dct:contributor ?agent.
- }
+} WHERE {
+ ?document dct:contributor ?agent.
+}
</pre>
</section>
<section id="dct-publisher">
@@ -1288,9 +1288,9 @@
prov:wasGeneratedBy _:activity;
prov:wasAttributedTo ?agent.
- } WHERE {
- ?document dct:publisher ?agent.
- }
+} WHERE {
+ ?document dct:publisher ?agent.
+}
</pre>
<p></p>
</section>
@@ -1322,9 +1322,9 @@
prov:wasGeneratedBy _:activity;
prov:wasAttributedTo ?agent.
- } WHERE {
- ?document dct:rightsHolder ?agent.
- }
+} WHERE {
+ ?document dct:rightsHolder ?agent.
+}
</pre>
<p></p>
</section>
@@ -1349,9 +1349,9 @@
CONSTRUCT{
_:event a prov:InstantaneousEvent;
prov:atTime ?date.
- } WHERE {
- ?document dct:date ?date.
- }
+} WHERE {
+ ?document dct:date ?date.
+}
</pre>
Note that the above inference would not generally be considered useful due to the ambiguity of <code>dct:date</code> (we don't know how the entity is
related to the event), however the above mapping is included here for completeness.
@@ -1375,9 +1375,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:created ?date.
- }
+} WHERE {
+ ?document dct:created ?date.
+}
</pre>
</section>
@@ -1407,9 +1407,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:issued ?date.
- }
+} WHERE {
+ ?document dct:issued ?date.
+}
</pre>
<p></p>
</section>
@@ -1439,9 +1439,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:modified ?date.
- }
+} WHERE {
+ ?document dct:modified ?date.
+}
</pre>
<p></p>
</section>
@@ -1471,9 +1471,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:dateAccepted ?date.
- }
+} WHERE {
+ ?document dct:dateAccepted ?date.
+}
</pre>
<p></p>
</section>
@@ -1495,9 +1495,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:dateCopyrighted ?date.
- }</pre>
+} WHERE {
+ ?document dct:dateCopyrighted ?date.
+}</pre>
</section>
<section id="dct-datesubmitted">
<h5><span class="secno">3.3.2.7 </span>dct:dateSubmitted</h5>
@@ -1525,9 +1525,9 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:dateSubmitted ?date.
- }
+} WHERE {
+ ?document dct:dateSubmitted ?date.
+}
</pre>
<p></p>
</section>
@@ -1573,9 +1573,9 @@
prov:wasDerivedFrom _:oldEntity;
prov:alternateOf _:oldEntity.
- } WHERE {
- ?document dct:replaces ?document2.
- }
+} WHERE {
+ ?document dct:replaces ?document2.
+}
</pre><p></p>
</section>
<p>
@@ -1618,10 +1618,10 @@
prov:atTime ?date;
prov:activity _:activity.
].
- } WHERE {
- ?document dct:creator ?agent;
- dct:created ?date.
- }
+} WHERE {
+ ?document dct:creator ?agent;
+ dct:created ?date.
+}
</pre>
<a href="#figure_cleanup1">Figure 3</a> shows a graphical representation of the pattern (considering <code>?date</code> as <code>ex:dateCreation</code> and <code>?agent</code> as <code>ex:creator</code>):
@@ -1880,7 +1880,8 @@
<tr>
<td><b id="term_SizeOrDuration"><a href="http://purl.org/dc/terms/SizeOrDuration">dct:SizeOrDuration</a></b></td>
<td>Descriptive metadata</td>
- <td>Dimension or time taken to execute something.</td>
+ <td>Dimension or time taken to execute something (e.g., the minutes for a cooking recipe). The "duration" aspect of the size is prospective,
+ while PROV just covers retrospective durations.</td>
</tr>
<tr>
<td><b id="term_Standard"><a href="http://purl.org/dc/terms/Standard">dct:Standard</a></b></td>
@@ -1894,13 +1895,14 @@
<section id="mapping-from-prov-to-dc">
<h3><span class="secno">3.6 </span>Mapping from PROV to DC</h3>
<p>
- The mapping from PROV to DC is not part of this note. If the refinements proposed in this document are used, then the inverse of the complex mapping
+ The mapping from PROV to DC is not part of this note. If the refinements proposed in <a href="#prov-refinements">Section 3.2</a> are used, then the inverse of the complex mapping
patterns can be applied.
However, if the refinements are not used then only a few DC statements can be inferred from plain PROV statements.
- 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 activity. Likewise, the agents
- involved cannot be mapped to creators, contributors, or publishers. While DC 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.
+ 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 activity.
+ This is because DC provides more specific classes of activities. Likewise, the agents involved cannot be mapped to creators, contributors, or publishers.
+ This is because DC provides more specific classes of agency. While DC includes provenance information, its focus
+ lies on the broader description of resources. Because PROV is focused on modeling provenance chains, it does not
+ provide ways to describe the resources being chained together.
</p>
</section>
</section>