--- a/dc-note/Overview.html Wed Oct 24 14:27:23 2012 -0400
+++ b/dc-note/Overview.html Thu Oct 25 13:00:32 2012 +0200
@@ -509,7 +509,9 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
-</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" /></head>
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" />
+<script src="http://www.w3.org/2007/OWL/toggles.js"></script>
+</head>
<body style="display: inherit; ">
<div class="head"><p><a href="http://www.w3.org/">
<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a></p>
@@ -870,7 +872,7 @@
</div>
</div>
</p><p>
-Since the first option is the most conservative with respect to the underlying semantics, it has been chosen as guideline in the context-free mapping.
+Since the first option is the most conservative with respect to the underlying semantics, it has been chosen as guideline in the complex mapping.
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.
<!-- I comment this because it repeats what it has already been stated
@@ -900,7 +902,7 @@
</p>
<p>
<a href="#list_of_direct_terms">Table 3</a> and <a href="#list_of_direct_mappings2">Table 4</a> provide the detailed mapping plus the rationale for each term.
- For more information see the
+ The rest of the terms can be found in the
<a href="#list_of_excluded_terms">list of terms left out of the mapping</a>.
</p><p>
<div id="list_of_direct_terms" ALIGN="center">
@@ -1140,15 +1142,17 @@
<div id="complex_mappings" class="section">
<h3><span class="secno">2.5 </span>Complex Mappings</h3>
<p>
+The complex mappings consist on a set of patterns defined to generate qualified PROV statements from Dublin Core statements. This type of qualification may not be
+always needed, and it is the choice of the implementor 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:
</p>
<div id="entity_agent_mappings">
<h4><span class="secno">2.5.1 </span>Entity-Agent mappings (Who)</h4>
<p>
-In this category, we have four terms: <code>dct:contributor</code>, <code>dct:creator</code>, <code>dct:publisher</code>, and <code>dct:rightsHolder</code>.
-The former three
- can be mapped with the same pattern, similar to the one presented in <a href="#figure_mapping_example">Figure 1</a>.
+In this category, we have three terms: <code>dct:contributor</code>, <code>dct:creator</code> and <code>dct:publisher</code>.
+The three of them can be mapped with the same pattern, similar to the one presented in <a href="#figure_mapping_example">Figure 1</a>.
The only changes required are the roles and activities involved for each term.
<p>
@@ -1269,15 +1273,30 @@
<div id="entity_date_mappings">
<h4><span class="secno">2.5.2 </span>Entity-Date mappings (When)</h4>
<p>
-The dates often correspond with a who-property, e.g., creator and created or publisher and issued.
- Therefore, they lead to similar statements, only providing a date instead of an agent associated with the activity.
+Dates often correspond with a who-property, e.g., creator and created or publisher and issued.
+ Therefore, they lead to similar complex patterns (providing a date instead of an agent associated with the corresponding activity).
+ 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., but in this phase of the mapping each term is treated independently.
+ <form action="#"><p>
+ <input id="hide-dates" type="button" value="Hide date patterns"
+ style="display:none"
+ onclick="
+ set_display_by_class('div','date pattern','none');
+ set_display_by_id('hide-dates','none');
+ set_display_by_id('show-dates','');" />
+ <input id="show-dates" type="button" value="Show date patterns"
+ onclick="
+ set_display_by_class('div','date pattern','');
+ set_display_by_id('hide-dates','');
+ set_display_by_id('show-dates','none');" />
+ </p>
+ </form>
</p>
-<p>
-When using Dublin Core terms, it is usual to see that a resource is annotated with several dc assertions like creator, publisher,
- issued, date, etc. In this phase of the mapping each term is treated independently.
+
+<h5 id="term_created"><span class="secno">2.5.2.1 </span>dct:created</h5>
</p>
-<h5 id="term_created"><span class="secno">2.5.2.1 </span>dct:created</h5>
-</p><p><pre class="code">
+<div class="date pattern" style="display:none">
+<pre class="code">
CONSTRUCT{
?document a prov:Entity .
@@ -1297,8 +1316,12 @@
?document dct:created ?date.
}
</pre>
+ </div>
+
<h5 id="term_issued"><span class="secno">2.5.2.2 </span>dct:issued</h5>
-<p><pre class="code">
+<p>
+<div class="date pattern" style="display:none">
+<pre class="code">
CONSTRUCT{
?document a prov:Entity .
@@ -1325,7 +1348,10 @@
}
</pre>
</p>
+</div>
+
<h5 id="term_modified"><span class="secno">2.5.2.3 </span>dct:modified</h5>
+<div class="date pattern" style="display:none">
<p>
As seen with the previous terms, most entity/date properties will have a similar structure.
</p><p><pre class="code">
@@ -1354,9 +1380,12 @@
?document dct:modified ?date.
}
</pre>
-</p><p>
+</p>
+</div>
+
<h5 id="term_dateAccepted"><span class="secno">2.5.2.4 </span>dct:dateAccepted</h5>
-</p><p><pre class="code">
+<div class="date pattern" style="display:none">
+<p><pre class="code">
CONSTRUCT{
?document a prov:Entity .
@@ -1383,7 +1412,9 @@
}
</pre>
</p>
+</div>
<h5 id="term_dateCopyRighted"><span class="secno">2.5.2.5 </span>dct:dateCopyrighted</h5>
+<div class="date pattern" style="display:none">
<p><pre class="code">
CONSTRUCT{
?document a prov:Entity .
@@ -1410,7 +1441,9 @@
?document dct:dateCopyrighted ?date.
}
</pre></p>
+</div>
<h5 id="term_dateSubmitted"><span class="secno">2.5.2.6 </span>dct:dateSubmitted</h5>
+<div class="date pattern" style="display:none">
<p><pre class="code">
CONSTRUCT{
?document a prov:Entity .
@@ -1439,6 +1472,7 @@
</pre>
</p>
</div>
+</div>
<!--
<div id="entity_entity_mappings">
<h4><span class="secno">2.5.3 </span>Entity-Entity mappings (How)</h4>
@@ -1788,7 +1822,7 @@
<!-- OddPage -->
<h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
- We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo, Simon Miles and Satya Sahoo for their feedback.
+ We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo, Simon Miles and Satya Sahoo for their comments and feedback, and Idafen Santana Pérez for his help with the HTML generation.
</p>
</div>