--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 23 01:05:06 2013 +0200
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Tue Apr 23 02:19:18 2013 +0200
@@ -21,15 +21,15 @@
div.illegal-example { color: red }
div.illegal-example p { color: black }
aside.example, div.example {
- padding: .5em;
- border-left-width: .5em;
+ padding:.5em;
+ border-left-width:.5em;
border-left-style: solid;
border-color: #e0cb52;
background: #fcfaee;
}
aside.example div.example {
- border-left-width: .1em;
+ border-left-width:.1em;
border-color: #999;
background: #fff;
}
@@ -60,7 +60,7 @@
table th {
background-color: LightGoldenRodYellow;
}
-.parameters th, .exceptions th {
+.parameters th,.exceptions th {
color: #fff;
padding: 3px 5px;
text-align: left;
@@ -71,17 +71,17 @@
.parameters th { background: #90b8de; }
.exceptions th { background: #deb890; }
-.parameters td, .exceptions td {
+.parameters td,.exceptions td {
padding: 3px 10px;
border-top: 1px solid #ddd;
vertical-align: top;
}
-.parameters tr:first-child td, .exceptions tr:first-child td {
+.parameters tr:first-child td,.exceptions tr:first-child td {
border-top: none;
}
-.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+.parameters td.prmName,.exceptions td.excName,.exceptions td.excCodeName {
width: 100px;
}
@@ -141,7 +141,7 @@
text-decoration: none;
}
-cite .bibref {
+cite.bibref {
font-style: normal;
}
@@ -156,11 +156,11 @@
ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
/* --- TOC --- */
-.toc a, .tof a {
+.toc a,.tof a {
text-decoration: none;
}
-a .secno, a .figno {
+a.secno, a.figno {
color: #000;
}
@@ -215,7 +215,7 @@
margin-bottom: 1em;
}
-.section dl.attrs dd, .section dl.eldef dd {
+.section dl.attrs dd,.section dl.eldef dd {
margin-bottom: 0;
}
@@ -285,9 +285,9 @@
#add other authors/editors here
prov:wasAttributedTo <http://www.w3.org/2011/prov>;
prov:wasInfluencedBy <http://www.w3.org/TR/2013/WD-prov-dc-20130430/#acknowledgements>.
-<http://delicias.dia.fi.upm.es/members/DGarijo/#me> a prov:Person .
-<http://www.kaiec.org/#me> a prov:Person .
-<http://www.w3.org/2011/prov> a prov:Organization .
+<http://delicias.dia.fi.upm.es/members/DGarijo/#me> a prov:Person.
+<http://www.kaiec.org/#me> a prov:Person.
+<http://www.w3.org/2011/prov> a prov:Organization.
-->
<b resource="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/" typeof="foaf:Document prov:Entity">
<b property="prov:wasRevisionOf" resource="http://www.w3.org/TR/2012/WD-prov-dc-20130312/"></b>
@@ -697,14 +697,14 @@
<p>
<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" ;
- dct:publisher ex:w3c ;
- dct:issued "2012-02-29" ;
- dct:subject ex:dublincore ;
- dct:replaces ex:prov-dc-20121211 ;
- dct:format "HTML" .
+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";
+ dct:publisher ex:w3c;
+ dct:issued "2012-02-29";
+ dct:subject ex:dublincore;
+ dct:replaces ex:prov-dc-20121211;
+ dct:format "HTML".
</pre></div>
In <a href="#example1">Example 1</a>, <code>dct:title</code>, <code>dct:subject</code> and <code>dct:format</code>
are <i>descriptions</i> of the resource <code>ex:prov-dc-20130312</code>.
@@ -1156,19 +1156,19 @@
activity which used some entity to be published, produced a published entity and was associated with a publisher.
The PROV extensions for DC can be seen below:
</p><pre class="code">
- prov:Publish rdfs:subClassOf prov:Activity .
- prov:Contribute rdfs:subClassOf prov:Activity .
- prov:Create rdfs:subClassOf prov:Activity, prov:Contribute .
- prov:RightsAssignment rdfs:subClassOf prov:Activity .
- prov:Modify rdfs:subClassOf prov:Activity .
- prov:Accept rdfs:subClassOf prov:Activity .
- prov:Copyright rdfs:subClassOf prov:Activity .
- prov:Submit rdfs:subClassOf prov:Activity .
- prov:Replace rdfs:subClassOf prov:Activity .
- prov:Publisher rdfs:subClassOf prov:Role .
- prov:Contributor rdfs:subClassOf prov:Role .
- prov:Creator rdfs:subClassOf prov:Role, prov:Contributor .
- prov:RightsHolder rdfs:subClassOf prov:Role .
+ prov:Publish rdfs:subClassOf prov:Activity.
+ prov:Contribute rdfs:subClassOf prov:Activity.
+ prov:Create rdfs:subClassOf prov:Activity, prov:Contribute.
+ prov:RightsAssignment rdfs:subClassOf prov:Activity.
+ prov:Modify rdfs:subClassOf prov:Activity.
+ prov:Accept rdfs:subClassOf prov:Activity.
+ prov:Copyright rdfs:subClassOf prov:Activity.
+ prov:Submit rdfs:subClassOf prov:Activity.
+ prov:Replace rdfs:subClassOf prov:Activity.
+ prov:Publisher rdfs:subClassOf prov:Role.
+ prov:Contributor rdfs:subClassOf prov:Role.
+ prov:Creator rdfs:subClassOf prov:Role, prov:Contributor.
+ prov:RightsHolder rdfs:subClassOf prov:Role.
</pre>
<!--<p>
Additional refinements of the PROV properties have been ommitted, since the direct mappings presented in <a href="#direct-mappings">Section 3.1</a>
@@ -1209,12 +1209,12 @@
A creator is the agent in charge of the <code>prov:Create</code> activity that generated a specialization of the entity <code>?document</code>. The agent is assigned the role <code>prov:Creator</code>.
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
+ ?document a prov:Entity;
prov:wasAttributedTo ?agent.
- ?agent a prov:Agent .
+ ?agent a prov:Agent.
- _:activity a prov:Activity, prov:Create ;
+ _:activity a prov:Activity, prov:Create;
prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
a prov:Association;
@@ -1222,9 +1222,9 @@
prov:hadRole [a prov:Creator].
].
- _:resultingEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:resultingEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasAttributedTo ?agent.
} WHERE {
@@ -1237,26 +1237,26 @@
Contributor is mapped following the previous pattern. Only the roles and activities change:
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
- prov:wasAttributedTo ?agent .
+ ?document a prov:Entity;
+ prov:wasAttributedTo ?agent.
- ?agent a prov:Agent .
+ ?agent a prov:Agent.
- _:activity a prov:Activity, prov:Contribute ;
- prov:wasAssociatedWith ?agent ;
+ _:activity a prov:Activity, prov:Contribute;
+ prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
- a prov:Association ;
- prov:agent ?agent ;
+ a prov:Association;
+ prov:agent ?agent;
prov:hadRole [a prov:Contributor].
].
- _:resultingEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasAttributedTo ?agent .
+ _:resultingEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
+ prov:wasAttributedTo ?agent.
} WHERE {
- ?document dct:contributor ?agent .
+ ?document dct:contributor ?agent.
}
</pre>
</section>
@@ -1265,31 +1265,31 @@
In case of publication, a second specialization representing the entity before the publication is necessary:
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
- prov:wasAttributedTo ?agent .
+ ?document a prov:Entity;
+ prov:wasAttributedTo ?agent.
- ?agent a prov:Agent .
+ ?agent a prov:Agent.
_:usedEntity a prov:Entity;
prov:specializationOf ?document.
- _:activity a prov:Activity, prov:Publish ;
+ _:activity a prov:Activity, prov:Publish;
prov:used _:usedEntity;
- prov:wasAssociatedWith ?agent ;
+ prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
- a prov:Association ;
- prov:agent ?agent ;
- prov:hadRole [a prov:Publisher] .
+ a prov:Association;
+ prov:agent ?agent;
+ prov:hadRole [a prov:Publisher].
].
- _:resultingEntity a prov:Entity ;
- prov:specializationOf ?document ;
+ _:resultingEntity a prov:Entity;
+ prov:specializationOf ?document;
prov:wasDerivedFrom _:usedEntity
- prov:wasGeneratedBy _:activity ;
- prov:wasAttributedTo ?agent .
+ prov:wasGeneratedBy _:activity;
+ prov:wasAttributedTo ?agent.
} WHERE {
- ?document dct:publisher ?agent .
+ ?document dct:publisher ?agent.
}
</pre>
<p></p>
@@ -1299,31 +1299,31 @@
The rightsHolder manages the rights of a resource, getting some attribution for the ownership by being ascribed to it:
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
- prov:wasAttributedTo ?agent .
+ ?document a prov:Entity;
+ prov:wasAttributedTo ?agent.
- ?agent a prov:Agent .
+ ?agent a prov:Agent.
_:oldRightsEntity a prov:Entity;
prov:specializationOf ?document.
- _:activity a prov:Activity, prov:RightsAssignment ;
+ _:activity a prov:Activity, prov:RightsAssignment;
prov:used _:oldRightsEntity;
- prov:wasAssociatedWith ?agent ;
+ prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
- a prov:Association ;
- prov:agent ?agent ;
- prov:hadRole [a prov:RightsHolder] .
+ a prov:Association;
+ prov:agent ?agent;
+ prov:hadRole [a prov:RightsHolder].
].
- _:newRightsEntity a prov:Entity ;
- prov:specializationOf ?document ;
+ _:newRightsEntity a prov:Entity;
+ prov:specializationOf ?document;
prov:wasDerivedFrom _:oldRightsEntity
- prov:wasGeneratedBy _:activity ;
- prov:wasAttributedTo ?agent .
+ prov:wasGeneratedBy _:activity;
+ prov:wasAttributedTo ?agent.
} WHERE {
- ?document dct:rightsHolder ?agent .
+ ?document dct:rightsHolder ?agent.
}
</pre>
<p></p>
@@ -1332,7 +1332,7 @@
<section id="entity-date-mappings-when">
<h4><span class="secno">3.3.2 </span>Entity-Date mappings (When)</h4>
<p>
- Dates often correspond with a who-property, e.g., creator and created or publisher and issued.
+ Dates often correspond with a who-property. For example, date created implies a creator and date issued implies a publisher.
Therefore, they lead to similar complex patterns (associating a date to each activity instead of an agent).
When using DC 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.
@@ -1344,11 +1344,11 @@
<section id="term_date">
<h5><span class="secno">3.3.2.1 </span> dct:date</h5>
- <p>Term defined as a point or period of time associated with an event in the lifecycle of the resource.</p>
+ <p><code>dct:date</code> is a term defined as a point or period of time associated with an event in the lifecycle of the resource.</p>
<pre class="code">
CONSTRUCT{
- _:event a prov:InstantaneousEvent ;
- prov:atTime ?date .
+ _:event a prov:InstantaneousEvent;
+ prov:atTime ?date.
} WHERE {
?document dct:date ?date.
}
@@ -1358,23 +1358,23 @@
</section>
<section id="dct-created">
<h5><span class="secno">3.3.2.2 </span> dct:created</h5>
- <p></p>
+ <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:created</code> is mapped to PROV thusly:</p>
<pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Create ;
+ _:activity a prov:Activity, prov:Create;
# The “output”
- _:createdEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:createdEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:created ?date.
}
@@ -1384,28 +1384,29 @@
<section id="dct-issued">
<h5><span class="secno">3.3.2.3 </span>dct:issued</h5>
<p>
+ <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:issued</code> is mapped to PROV thusly:</p>
</p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Publish ;
- prov:used _:usedEntity .
+ _:activity a prov:Activity, prov:Publish;
+ prov:used _:usedEntity.
# The “input”
- _:usedEntity a prov:Entity .
- prov:specializationOf ?document .
+ _:usedEntity a prov:Entity.
+ prov:specializationOf ?document.
# The “output”
- _:issEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:issEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:usedEntity ;
+ prov:wasDerivedFrom _:usedEntity;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:issued ?date.
}
@@ -1414,28 +1415,30 @@
</section>
<section id="dct-modified">
<h5><span class="secno">3.3.2.4 </span>dct:modified</h5>
- <p></p><pre class="code">
+ <p>
+ <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:modified</code> is mapped to PROV thusly:</p>
+ </p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Modify ;
- prov:used _:usedEntity .
+ _:activity a prov:Activity, prov:Modify;
+ prov:used _:usedEntity.
# The “input”
- _:usedEntity a prov:Entity .
- prov:specializationOf ?document .
+ _:usedEntity a prov:Entity.
+ prov:specializationOf ?document.
# The “output”
- _:modifiedEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:modifiedEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:usedEntity ;
+ prov:wasDerivedFrom _:usedEntity;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:modified ?date.
}
@@ -1444,28 +1447,30 @@
</section>
<section id="dct-dateaccepted">
<h5><span class="secno">3.3.2.5 </span>dct:dateAccepted</h5>
- <p></p><pre class="code">
+ <p>
+ <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateAccepted</code> is mapped to PROV thusly:</p>
+ </p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Accept ;
- prov:used _:usedEntity .
+ _:activity a prov:Activity, prov:Accept;
+ prov:used _:usedEntity.
# The “input”
- _:usedEntity a prov:Entity .
- prov:specializationOf ?document .
+ _:usedEntity a prov:Entity.
+ prov:specializationOf ?document.
# The “output”
- _:acceptedEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:acceptedEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:usedEntity ;
+ prov:wasDerivedFrom _:usedEntity;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:dateAccepted ?date.
}
@@ -1477,47 +1482,49 @@
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 .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Copyright ;
+ _:activity a prov:Activity, prov:Copyright;
# The “output”
- _:copyrightedEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:copyrightedEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:dateCopyrighted ?date.
}</pre>
</section>
<section id="dct-datesubmitted">
<h5><span class="secno">3.3.2.7 </span>dct:dateSubmitted</h5>
- <p></p><pre class="code">
+ <p>
+ <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateSubmitted</code> is mapped to PROV thusly:</p>
+ </p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
- _:activity a prov:Activity, prov:Submit ;
- prov:used _:usedEntity .
+ _:activity a prov:Activity, prov:Submit;
+ prov:used _:usedEntity.
# The “input”
- _:usedEntity a prov:Entity .
- prov:specializationOf ?document .
+ _:usedEntity a prov:Entity.
+ prov:specializationOf ?document.
# The “output”
- _:submittedEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:submittedEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:usedEntity ;
+ prov:wasDerivedFrom _:usedEntity;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:dateSubmitted ?date.
}
@@ -1540,8 +1547,8 @@
<p>
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).
+ replacement could have existed and been generated independently from the original (for example, if a catalog replaces a book entitled
+ "Introduction to provenance" with one entitled "Provenance in a nutshell).
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>.
@@ -1549,21 +1556,21 @@
<p>
</p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
?document2 a prov:Entity.
- _:activity a prov:Activity, prov:Replace ;
+ _:activity a prov:Activity, prov:Replace;
prov:used _:oldEntity.
# The “input”
_:oldEntity a prov:Entity;
- prov:specializationOf ?document2 ;
+ prov:specializationOf ?document2;
# The “output”
- _:newEntity a prov:Entity ;
- prov:specializationOf ?document ;
+ _:newEntity a prov:Entity;
+ prov:specializationOf ?document;
prov:wasGeneratedBy _:activity;
- prov:wasDerivedFrom _:oldEntity ;
+ prov:wasDerivedFrom _:oldEntity;
prov:alternateOf _:oldEntity.
} WHERE {
@@ -1591,26 +1598,26 @@
<p>The example below shows how to conflate the blank nodes for <code>dct:creator</code> and <code>dct:created</code> properties:
</p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity.
_:activity a prov:Activity, prov:Create.
prov:wasAssociatedWith ?agent
prov:qualifiedAssociation [
a prov:Association;
prov:agent ?agent;
- prov:hadRole [a prov:Creator] .
- ] .
+ prov:hadRole [a prov:Creator].
+ ].
# The “output”
- _:createdEntity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
+ _:createdEntity a prov:Entity;
+ prov:specializationOf ?document;
+ prov:wasGeneratedBy _:activity;
prov:wasGeneratedAtTime ?date;
prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ a prov:Generation;
+ prov:atTime ?date;
+ prov:activity _:activity.
+ ].
} WHERE {
?document dct:creator ?agent;
dct:created ?date.
@@ -1625,8 +1632,8 @@
</div>
</div>
<p></p>
- <p>2) Another solution is to <b>sort all the activities according to their logical order</b>, if known, and conflate the blank
- nodes result of one activity with the input of the subsequent activity. <!-- in case they are both specializations of the same entity -->
+ <p>2) Another solution is to <b>sort all the activities according to their logical order</b>, if known, and conflate the specialized entity (blank
+ node) result of one activity with the specialized entity (blank node) input of the subsequent activity. <!-- in case they are both specializations of the same entity -->
<a href="#figure_cleanup2">Figure 4</a> shows a graphical example with two different activities (creation and publication) that happened at different
points in time. Creation precedes publication, so instead of creating different blank nodes for their respective usage and generation, both activities share the same
blank node (<code>_:createdEntity</code>).
@@ -1643,7 +1650,7 @@
<h3><span class="secno">3.5 </span>List of terms excluded from the mapping</h3>
<a href="#list-of-terms-excluded-from-the-mapping-properties"> Table 9</a> and <a href="#list-of-terms-excluded-from-the-mapping-classes"> Table 10</a>
list the properties and classes excluded from the mapping,
- either because thay are not suitable or because they do not represent provenance information.
+ either because they are not suitable or because they do not represent provenance information.
<table id="list-of-terms-excluded-from-the-mapping-properties">
<caption> <a href="#list-of-terms-excluded-from-the-mapping-properties"> Table 9:</a> List of properties excluded from the mapping </caption>
@@ -1662,7 +1669,8 @@
<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 does not 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. Since this term does not describe the activity or the entities
+ participating on the activity (just the plan followed), 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>
@@ -1685,7 +1693,7 @@
<tr>
<td><b id="term_available"><a href="http://purl.org/dc/terms/available">dct:available</a></b></td>
<td>Provenance: When</td>
- <td>Property that states when a resource is available. There is no direct mapping between this property and the notion of invalidation in PROV.</td>
+ <td>Property that states when a resource is available. There is no direct mapping between this property and the PROV notions of generation and invalidation.</td>
</tr>
<tr>
<td><b id="term_bibliographicCitation"><a href="http://purl.org/dc/terms/bibliographicCitation">dct:bibliographicCitation</a></b></td>
@@ -1708,7 +1716,7 @@
</tr><tr>
<td><b id="term_educationLevel"><a href="http://purl.org/dc/terms/educationLevel">dct:educationLevel</a></b></td>
<td>Descriptive metadata</td>
- <td>The educational level of the audience for which the resource is intended to.</td>
+ <td>The educational level of the audience for which the resource is intended.</td>
</tr><tr>
<td><b id="term_extent"><a href="http://purl.org/dc/terms/extent">dct:extent</a></b></td>
<td>Descriptive metadata</td>
@@ -1727,11 +1735,11 @@
<tr>
<td><b id="term_identifier"><a href="http://purl.org/dc/terms/identifier">dct:identifier</a></b></td>
<td>Descriptive metadata</td>
- <td>An unambiguous reference on a given context. </td>
+ <td>"An unambiguous reference to the resource within a given context." </td>
</tr><tr>
<td><b id="term_instructionalMethod"><a href="http://purl.org/dc/terms/instructionalMethod">dct:instructionalMethod</a></b></td>
<td>Descriptive metadata</td>
- <td>Method used to create the knowledge that the resource is supposed to support.</td>
+ <td>"A process, used to engender knowledge, attitudes and skills, that the described resource is designed to support".</td>
</tr><tr>
<td><b id="term_isPartOf"><a href="http://purl.org/dc/terms/isPartOf">dct:isPartOf</a></b></td>
<td>Descriptive metadata</td>
@@ -1739,8 +1747,8 @@
</tr><tr>
<td><b id="term_isRequiredBy"><a href="http://purl.org/dc/terms/isRequiredBy">dct:isRequiredBy</a></b></td>
<td>Descriptive metadata</td>
- <td>Property used to describe that the current resource is required for supporting the function of another resource. This is not related
- the provenance of the resource, since it refers to something that may not have happened yet (e.g., a library dependency in script program).</td>
+ <td>Property used to describe that the current resource is required for supporting the function of another resource. This is not related to
+ the provenance of the resource, since it refers to something that may not have happened yet (e.g., a programming scripts' dependency on another dependency).</td>
</tr><tr>
<td><b id="term_language"><a href="http://purl.org/dc/terms/language">dct:language</a></b></td>
<td>Descriptive metadata</td>
@@ -1808,7 +1816,9 @@
<tr>
<td><b id="term_valid"><a href="http://purl.org/dc/terms/valid">dct:valid</a></b></td>
<td>Provenance: When</td>
- <td>Property that states when a resource is valid. The notion of invalidation is defined in PROV-DM, but not the notion of validation. Thus this property is left out of the mapping.</td>
+ <td>"Date (often a range) of validity of a resource." This property could correspond to PROV's generation and invalidation of the resource
+ or one of its specializations. However, <code>dct:valid</code> can be used to set expiry dates (e.g., resource valid until 2015), which is not
+ provenance (it is not about past events). Thus this property is left out of the mapping.</td>
</tr>
</tbody></table>
@@ -1823,7 +1833,8 @@
<tr>
<td><b id="term_AgentClass"><a href="http://purl.org/dc/terms/AgentClass">dct:AgentClass</a></b></td>
<td>Descriptive metadata</td>
- <td>Specialization of <code>rdf:Class</code> to define classes or groups of Agents. None of the PROV classes are defined similarly, so it is our of the scope of the mapping.</td>
+ <td>Specialization of <code>rdfs:Class</code> to define classes or groups of Agents (like <code>dct:Agent</code>. None of the PROV classes
+ are defined similarly, so it is our of the scope of the mapping.</td>
</tr>
<tr>
<td><b id="term_FileFormat"><a href="http://purl.org/dc/terms/FileFormat">dct:FileFormat</a></b></td>
@@ -1839,7 +1850,7 @@
<tr>
<td><b id="term_Jurisdiction"><a href="http://purl.org/dc/terms/Jurisdiction">dct:Jurisdiction</a></b></td>
<td>Descriptive metadata</td>
- <td>Defined as "The extent or range of judicial, law enforcement, or other authority". This class is not described by any of the DC properties
+ <td>Defined as "The extent or range of judicial, law enforcement, or other authority." This class is not described by any of the DC properties
and is used to describe a particular aspect of the resource for which the provenance is not further described. Therefore it is not part of this mapping. </td>
</tr>
<tr>
@@ -1857,7 +1868,8 @@
<tr>
<td><b id="term_PeriodOfTime"><a href="http://purl.org/dc/terms/PeriodOfTime">dct:PeriodOfTime</a></b></td>
<td>Descriptive metadata</td>
- <td>Interval of time (start and end dates). </td>
+ <td>Interval of time (start and end dates). Although PROV models instantaneous events, and entities and activities can be seen as
+ occupying intervals of time, there is no clear mapping to any of the PROV terms.</td>
</tr>
<tr>
<td><b id="term_PhysicalMedium"><a href="http://purl.org/dc/terms/PhysicalMedium">dct:PhysicalMedium</a></b></td>