--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Mon Apr 22 08:39:23 2013 -0400
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 23 00:03:30 2013 +0200
@@ -255,7 +255,7 @@
<dt>Contributors:</dt>
<dd><span><a href="http://www.inf.kcl.ac.uk/staff/simonm">Simon Miles</a></span>, King's College London, UK</dd>
<dd><span><a href="http://www.linkedin.com/in/craigtrim">Craig M. Trim</a></span>, IBM, USA</dd>
-<dd><span><a href="http://staff.oclc.org/~dewey/michael.htm">Michael Panzer</a></span>, OCLC Online Computer Library center, USA</dd>
+<dd><span><a href="http://staff.oclc.org/~dewey/michael.htm">Michael Panzer</a></span>, OCLC Online Computer Library Center, USA</dd>
</dl>
@@ -510,7 +510,7 @@
in order to derive an enhanced provenance chain.
<!--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>
+ <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.
</li>
<li><a href="#list-of-terms-excluded-from-the-mapping">Section 3.5</a>, on the other hand, describes the rationale for the terms left out of the mapping.
@@ -530,7 +530,7 @@
<p>
This section explains two main particular considerations that should be taken into account regarding the mapping:
</p><ul>
- <li><a href="#provenance-in-dublin-core">Section 2.1</a>: The relation of the DC terms with provenance.</li>
+ <li><a href="#provenance-in-dublin-core">Section 2.1</a>: The relation of the DC terms to provenance.</li>
<li><a href="#entities-in-dublin-core">Section 2.2</a>: The definition of entities in DC.</li>
</ul>
<p></p>
@@ -577,7 +577,7 @@
version
-->
<p>
- <b>Derivation and licensing Terms (How?):</b> This category contains derivation related terms.
+ <b>Derivation and Licensing Terms (How?):</b> This category contains derivation related terms.
When a resource is derived from other resources, the original resource becomes part of the provenance
chain of the derived resource. In DC, derivations can be further classified as versions (<code>dct:isVersionOf</code>),
format serializations (<code>dct:isFormatOf</code>), replacements (<code>dct:replaces</code>) and sources of information (<code>dct:source</code>).
@@ -586,7 +586,7 @@
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. However, inverse properties belong to the provenance related terms as they can be used to describe the relations
- between the resources involved. Finally, licensing (<code>dct:license</code>), rights (<code>dct:rights</code>) and their access (<code>accessRights</code>)
+ between the resources involved. Finally, licensing (<code>dct:license</code>), rights (<code>dct:rights</code>) and their access (<code>dct:accessRights</code>)
are considered part of the provenance of the resource as well, since they restrict and explain how the resource can be used for further derivation.
</p>
<div id="categories-props" >
@@ -663,7 +663,7 @@
<td><b>Descriptive metadata</b></td>
<td>
<a href="#term_AgentClass">AgentClass</a>, <a href="#term_BibliographicResource">BibliographicResource</a>,
- <a href="#term_FileFormat">FileFormat</a>, <a href="#term_Frequency">,Frequency</a>, <a href="#term_Jurisdiction">Jurisdiction</a>,
+ <a href="#term_FileFormat">FileFormat</a>, <a href="#term_Frequency">Frequency</a>, <a href="#term_Jurisdiction">Jurisdiction</a>,
<a href="#term_LicenseDocument">LicenseDocument</a>, <a href="#term_LinguisticSystem">LinguisticSystem</a>,
<a href="#term_Location">Location</a>, <a href="#term_LocationPeriodOrJurisdiction">LocationPeriodOrJurisdiction</a>,
<a href="#term_MediaType">MediaType</a>, <a href="#term_MediaTypeOrExtent">MediaTypeOrExtent</a>,
@@ -695,8 +695,8 @@
with several DC statements:
</p>
<p>
- <a href="#example1">Example 1</a>: a simple metadata record in Turtle format [<cite><a href="#bib-TURTLE" class="bibref">Turtle</a></cite>]:
- </p><div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example" id="example1">
+ <a href="#example1" id="example1">Example 1</a>: a simple metadata record in Turtle format [<cite><a href="#bib-TURTLE" class="bibref">Turtle</a></cite>]:
+ </p><div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">
ex:prov-dc-20130312 dct:title "A mapping from Dublin Core..." ;
dct:creator ex:kai, ex:daniel, ex:simon, ex:michael ;
dct:created "2012-02-28" ;
@@ -756,9 +756,9 @@
</div>
</div>
<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..
+ 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 cleanup phase.
+ leaving the conflating of nodes to the <a href="#cleanup">cleanup phase</a>.
</p>
</section>
</section>
@@ -837,7 +837,7 @@
<td><b id="term_dateCopyrighted"><a href="http://purl.org/dc/terms/dateCopyRighted">dct:dateCopyrighted</a></b></td>
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#generatedAtTime">prov:generatedAtTime</a></td>
- <td>Property used to describe the date when the resource was copy righted. <code>dct:dateCopyrighted</code> is mapped as a subproperty of <code>prov:generatedAtTime</code>
+ <td>Property used to describe the date when the resource was copyrighted. <code>dct:dateCopyrighted</code> is mapped as a subproperty of <code>prov:generatedAtTime</code>
because the copyrighted resource was generated by a "CopyRight" activity which may have changed it from its previous state.</td>
</tr>
<tr>
@@ -851,19 +851,19 @@
<td><b id="term_has_Format"><a href="http://purl.org/dc/terms/hasFormat">dct:hasFormat</a></b></td>
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#alternateOf">prov:alternateOf</a></td>
- <td> See rationale for <code>dct:isFormatOf</code> (as <code>prov:alternateOf</code>).</td>
+ <td> See rationale for <a href="#term_isFormatOf"><code>dct:isFormatOf</code></a> (as <code>prov:alternateOf</code>).</td>
</tr>
<tr>
<td><b id="term_isFormatOf"><a href="http://purl.org/dc/terms/isFormatOf">dct:isFormatOf</a></b></td>
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#alternateOf">prov:alternateOf</a></td>
- <td><code>dct:isFormatOf</code> refers to another resource which is the same but in another format. Thus, the mapping is straightforward to <code>prov:alternateOf</code>.</td>
+ <td><code>dct:isFormatOf</code> refers to another resource which is the same but in another format. Thus, the term is mapped to <code>prov:alternateOf</code>.</td>
</tr>
<tr>
<td><b id="term_isFormatOf"><a href="http://purl.org/dc/terms/isFormatOf">dct:isFormatOf</a></b></td>
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a></td>
- <td><code>dct:isFormatOf</code> refers to another pre-existing resource which is the same but in another format,
+ <td><code>dct:isFormatOf</code> refers to another "pre-existing" resource which is the same but in another format (according to <a href="http://purl.org/dc/terms/hasFormat"><code>cdt:hasFormat</code></a>),
implying that the new resource is based on the former.</td>
</tr>
<tr>
@@ -916,8 +916,8 @@
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a></td>
<td><code>dct:source</code> is defined as a "related resource from which the described resource is derived", which matches the notion of derivation
- in PROV-DM ("a transformation of an entity in another"). However, prov:wasDerivedFrom also covers broader derivations such as "an update of an entity
- resulting in a new one" which is not covered by dct:source</td>
+ in PROV-DM ("a transformation of an entity in another"). However, <code>prov:wasDerivedFrom</code> also covers broader derivations such as "an update of an entity
+ resulting in a new one" which is not covered by dct:source.</td>
</tr>
@@ -946,7 +946,7 @@
</td>
<td>rdfs:subClassOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#Entity">prov:Entity</a></td>
- <td>A bibliographic resource refers to books, articles, etc., which are concrete PROV entities</td>
+ <td>A bibliographic resource refers to books, articles, etc., which are concrete PROV entities.</td>
</tr>
<tr>
<td>
@@ -960,7 +960,7 @@
<td><b id="term_LinguisticSystem"><a href="http://purl.org/dc/terms/LinguisticSystem">dct:LinguisticSystem</a></b></td>
<td>rdfs:subClassOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#Plan">prov:Plan</a></td>
- <td>A <code>dct:LinguisticSystem</code> is a system od symbols, sounds, gestures, etc. used in communication. Therefore, the linguistic system
+ <td>A <code>dct:LinguisticSystem</code> is a system of symbols, sounds, gestures, etc. used in communication. Therefore, the linguistic system
defines the plan to follow in order to learn a certain language.
</td>
</tr>
@@ -969,7 +969,7 @@
<td><b id="term_Location"><a href="http://purl.org/dc/terms/Location">dct:Location</a></b></td>
<td>owl:equivalentClass</td>
<td><a href="http://www.w3.org/TR/prov-o/#Location">prov:Location</a></td>
- <td>Both <code>dct:Location</code> and <code>prov:Location</code> define locations as "spatian regions or named places".</td>
+ <td>Both <code>dct:Location</code> and <code>prov:Location</code> define locations as "spatial regions or named places".</td>
</tr>
<tr>
<td>
@@ -997,7 +997,7 @@
</td>
<td>rdfs:subClassOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#Entity">prov:Entity</a></td>
- <td>Statement about the intelectual rights of a resource (e.g., a Document). Thus, it is mapped as a type of <code>prov:Entity</code>. </td>
+ <td>Statement about the intellectual rights of a resource (e.g., a Document). Thus, it is mapped as a type of <code>prov:Entity</code>. </td>
</tr>
<tr>
<td>
@@ -1013,7 +1013,7 @@
</td>
<td>rdfs:subClassOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#Entity">prov:Entity</a></td>
- <td>A material thing, which is a concrete type of <code>prov:Entity</code></td>
+ <td>A material thing, which is a concrete type of <code>prov:Entity</code>.</td>
</tr>
<tr>
<td>
@@ -1021,7 +1021,7 @@
</td>
<td>rdfs:subClassOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#Plan">prov:Plan</a></td>
- <td><code>dct:Policy</code> is defined as "a plan or course of action by an authority, intended to influence and determine decisions, actions, and other matters.". This is a
+ <td><code>dct:Policy</code> is defined as "a plan or course of action by an authority, intended to influence and determine decisions, actions, and other matters." This is a
specialization of <code>prov:Plan</code>.
</td>
</tr>
@@ -1035,7 +1035,7 @@
</tbody>
</table>
</div>
- It is worth mentioning that applying the direct mappings to a metadata record such as <a href="#example1">example 1</a> will infer that
+ It is worth mentioning that applying the direct mappings to a metadata record such as <a href="#example1">Example 1</a> will infer that
the resource (<code>ex:prov-dc-20130312</code>) was <code>prov:generatedAtTime</code> at two different times (two generation dates are associated to the document:
<code>dct:created</code> and <code>dct:issued</code>). This is valid, since from the PROV
point of view the "creation" and "issue" activities generate new entities. DC, on the other hand, groups those two intermediate entities under the same resource (<code>ex:prov-dc-20130312</code>), creating the record exposed
@@ -1058,7 +1058,7 @@
-->
<div id="list_of_direct_mappings2_props">
<table>
- <caption> <a href="#list_of_direct_mappings2_props"> Table 6:</a> Direct mappings (Properties) (2) </caption>
+ <caption> <a href="#list_of_direct_mappings2_props"> Table 6:</a> Direct mappings (Properties generalizing PROV terms)</caption>
<tbody>
<tr>
<th>PROV Term</th>
@@ -1087,7 +1087,7 @@
</div>
<div id="list_of_direct_mappings2_classes">
<table>
- <caption> <a href="#list_of_direct_mappings2_classes"> Table 7:</a> Direct mappings (Classes) (2) </caption>
+ <caption> <a href="#list_of_direct_mappings2_classes"> Table 7:</a> Direct mappings (Classes generalizing PROV terms)</caption>
<tbody>
<tr>
<th>PROV Term</th>