--- a/dc-note/dc-note.html Mon Feb 04 14:05:43 2013 +0000
+++ b/dc-note/dc-note.html Tue Feb 05 10:44:50 2013 +0100
@@ -57,6 +57,8 @@
// and its maturity status
//previousPublishDate: "2012-07-24",
//previousMaturity: "WD-NOTE",
+ previousPublishDate: "2012-12-11",
+ previousMaturity: "WD-NOTE",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/dc-note/dc-note.html",
@@ -541,10 +543,10 @@
the Dublin Core Terms Vocabulary [[DCTERMS]].
</p>
<p style="text-align: center;">
- The direct mappings are available <a href="http://www.w3.org/ns/prov-dc-directmappings.ttl">here</a>.
+ The mapping between Dublin Core and PROV is available <a href="http://www.w3.org/ns/prov-dc-directmappings.ttl">here</a>.
</p>
<p style="text-align: center;">
- The prov refinements for Dublin Core can be accessed here <a href="http://www.w3.org/ns/prov-dc-refinements.ttl">here</a>.
+ A set of PROV refinements for representing Dublin Core activities and roles can be accessed <a href="http://www.w3.org/ns/prov-dc-refinements.ttl">here</a>.
</p>
<p>
The PROV Document Overview [<cite><a href="#bib-PROV-OVERVIEW" class="bibref">PROV-OVERVIEW</a></cite>] describes the overall state of PROV, and should be read before other PROV documents.
@@ -579,55 +581,63 @@
<h2>Introduction</h2>
<p>
- The Dublin Core Metadata Initiative (DCMI) [[DCMI]] provides a core metadata vocabulary,
- commonly referred to as Dublin Core. The original element set, from 1995, contains 15 broadly-defined elements still in use.
+ The Dublin Core Metadata Initiative (DCMI, commonly referred to as Dublin Core) [[DCMI]] provides a core metadata vocabulary for simple and generic resource descriptions.
+ The original element set was created in 1995 and contains 15 broadly-defined elements still in use.
The core elements have no range specification, and arbitrary values can be used as objects. The core elements have been
expanded beyond the original fifteen. Existing elements have been refined and new elements have been added. This expanded vocabulary is
referred to as "DCMI Terms" and currently consists of 55 properties [[DCTERMS]].
</p>
+ <p>
The use of DCMI terms is preferred and the Dublin Core element set has been depecreated.
Both element sets have different namespaces. The original element set is typically referred with the
<code>dc</code> prefix, while <code>dct</code> (or <code>dcterms</code>) is used as prefix for the newer DCMI element set.
</p>
<p>
- DCMI terms hold a lot of provenance information and tell us about a resource, <i>when</i> it was affected in the past,
- <i>who</i> affected it and <i>how</i> it was affected. The rest of the DCMI terms (description metadata), tell us <i>what</i> was affected.
+ DCMI terms hold a lot of provenance information about a resource: <i>when</i> it was affected in the past,
+ <i>who</i> affected it and <i>how</i> it was affected. The rest of the DCMI terms (description metadata), tell us <i>what</i> was affected.
There is no direct information in Dublin Core describing <i>where</i> a resource was affected. Such information is usually
- only available for the publication of a resource (i.e., an action located at the address of the publisher).
+ only available for the publication of a resource.
</p>
<p>
- A classification of the <code>dct</code> terms is provided in <a href="#categories">Table 1</a>. This classification is by necessity
- somewhat conservative, as it can be argued that elements placed in the description metadata terms contain
- provenance information as well, depending on their usage. Based on this, 25 (out of 55) terms can be considered as
- provenance related. These terms can be further categorized according to the question they answer regarding the
- provenance of a resource:
- </p><p>
-
- <b>Dates and Time terms (When?):</b>This category contains date and time related terms.
- Dates typically belong to the provenance record of a resource. It can be questioned whether a resource changes by
- being published or not. Depending on the application, however, the publication can be seen as an action that changes
- the state of the resource. Two dates can be considered special regarding their relevance for
+ <a href="#categories">Table 1</a> classifies the <code>dct</code> terms in these four categories: <i>what?</i>, <i>who?</i>, <i>when?</i> and <i>how?</i>.
+ Each category corresponds to the question it answers regarding the description or provenance of a given resource.
+ The classification is by necessity somewhat conservative, as it can be argued that some elements placed in the description metadata terms contain
+ provenance information as well, depending on their usage. The categories are further explained below:
+ </p>
+ <!-- A total of 25 out of 55 terms can be considered provenance related.-->
+ <p>
+ <b> Descriptive Terms (What?):</b> This category contains all the terms describing a resource without refering to its provenance.
+ Some examples are the <code> dct:title</code>, <code> dct:abstract</code> or <code>dct:description</code> of a resource, the <code>dct:accessRights</code> that other agents have to
+ access the resource, the <code>dct:format</code> in which the resource can be found, etc.
+ </p>
+ <p>
+ <b>Agency Terms (Who?):</b> This category contains agent related terms. All properties have <code>dct:Agent</code> as range,
+ i.e., a resource that acts or has the power to act. The <code>dct:contributor</code>, <code>dct:creator</code>,
+ and <code>dct:publisher</code> clearly influence
+ the resource and therefore are important for its origin. This is not immediately clear for the <code>dct:rightsHolder</code>,
+ but as ownership is considered the important provenance information for many resources, like artworks, it is included in this category.
+ </p>
+ <p>
+ <b>Date and Time Terms (When?):</b>This category contains date and time related terms.
+ Dates belong to the provenance record of a resource, as they track when something was created (<code>dct:created</code>), modified
+ (<code>dct:modified</code>), published (<code>dct:issued</code>), etc. Two dates can be considered special regarding their relevance for
provenance: <code>dct:available</code> and <code>dct:valid</code>. They are different from the other dates as by definition they can represent a
date range. Often, the range of availability or validity of a resource is inherent to the resource and known
beforehand – consider the validity of a passport or the availability of a limited special offer published on the web.
In these cases, there is no action involved that makes the resource invalid or unavailable, it is simply determined
by the validity range. On the other hand, if an action is involved, e.g., a resource is declared invalid because
a mistake has been found, then it is relevant for its provenance.
- </p><p>
-
- <b>Agency Terms (Who?):</b> This category contains agent related terms. All properties that have <code>dct:Agent</code> as range,
- i.e., a resource that acts or has the power to act. The <code>dct:contributor</code>, <code>dct:creator</code>,
- and <code>dct:publisher</code> clearly influence
- the resource and therefore are important for its origin. This is not immediately clear for the <code>dct:rightsHolder</code>,
- but as ownership is considered the important provenance information for many resources, like artworks, it is included in this category.
- </p><p>
+ </p>
+ <!--
+ It can be questioned whether a resource changes by
+ being published or not. Depending on the application, however, the publication can be seen as an action that changes
+ the state of the resource.
+ -->
+ <p>
<b>Derivation Terms (How?):</b> This category contains derivation related terms.
Resources are often derived from other resources. In this case, the original resource becomes part of the provenance
- record of the derived resource. Derivations can be further
- classified as <code>dct:isVersionOf, dct:isFormatOf, dct:replaces,
- dct:source</code>. On the other hand, <code>dct:references</code>
- is a weaker relation, but it can be assumed that a referenced
- resource influenced the described resource
+ record of the derived resource. Derivations can be further classified as <code>dct:isVersionOf, dct:isFormatOf, dct:replaces and dct:source</code>.
+ <code>dct:references</code> is a weaker relation, but it can be assumed that a referenced resource influenced the described resource
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 – at most indirectly, as the validity state can change if a resource is replaced by a new
@@ -661,27 +671,27 @@
<tr>
<td><b>Provenance</b></td>
<td>Who</td>
- <td><a href="#term_contributor">contributor</a>, <a href="#term_creator">creator</a>, <a href="#term_publisher">publisher</a>, <a href="#term_rights_holder">rightsHolder</a></td>
+ <td><a href="#term_contributor">contributor</a>, <a href="#term_creator">creator</a>, <a href="#term_publisher">publisher</a>, <a href="#term_rightsHolder">rightsHolder</a></td>
</tr>
<tr>
<td><b>Provenance</b></td>
<td>When</td>
<td><a href="#term_available">available</a>, <a href="#term_created">created</a>, <a href="#term_date">date</a>, <a href="#term_dateAccepted">dateAccepted</a>,
- <a href="#term_dateCopyRighted">dateCopyrighted</a>, <a href="#term_dateSubmitted">dateSubmitted</a>, <a href="#term_issued">issued</a>,
+ <a href="#term_dateCopyrighted">dateCopyrighted</a>, <a href="#term_dateSubmitted">dateSubmitted</a>, <a href="#term_issued">issued</a>,
<a href="#term_modified">modified</a>, <a href="#term_valid">valid</a></td>
</tr>
<tr>
<td><b>Provenance</b></td>
<td>How</td>
- <td><a href="#term_has_Version">isVersionOf</a>, <a href="#term_has_Version">hasVersion</a>, <a href="#term_has_Format">isFormatOf</a>, <a href="#term_has_Format">hasFormat</a>, <a href="#term_license">license</a>,
- <a href="#term_references">references</a>, <a href="#term_isReferencedBy">isReferencedBy</a>, <a href="#term_replaces">replaces</a>, <a href="#term_replaces">isReplacedBy</a>, <a href="#term_rights">rights</a>,
+ <td><a href="#term_isVersionOf">isVersionOf</a>, <a href="#term_hasVersion">"hasVersion</a>, <a href="#term_isFormatOf">isFormatOf</a>, <a href="#term_has_Format">hasFormat</a>, <a href="#term_license">license</a>,
+ <a href="#term_references">references</a>, <a href="#term_isReferencedBy">isReferencedBy</a>, <a href="#term_replaces">replaces</a>, <a href="#term_isReplacedBy">isReplacedBy</a>, <a href="#term_rights">rights</a>,
<a href="#term_source">source</a></td>
</tr>
</tbody>
</table>
</div>
<p>
- This leaves one very special term: <code>dct:provenance</code>. This term is defined as a "statement of any changes in ownership and
+ This leaves one very special term: <i>provenance</i>. This term is defined as a "statement of any changes in ownership and
custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation" [[DCTERMS]],
which corresponds to the traditional definition of provenance for artworks. Despite being relevant for provenance,
this definition may overlap partially with almost half of the DCMI terms, which
@@ -753,9 +763,8 @@
<section>
<h3>What is ex:doc1? Entities in Dublin Core</h3>
<p>
- Consider the example metadata record shown at the beginning of
- this document (in <a href="#example1">example 1</a>). As a
- Dublin Core metadata record describes the resulting document as a whole,
+ Consider the example metadata record shown at the beginning of this document (in <a href="#example1">example 1</a>). As a <code>dc</code>
+ metadata record describes the resulting document as a whole,
it is not clear how this document relates to the different states that the document had until it reached its final state.
For example, a document may have a <code>dct:created</code> date and a <code>dct:issued</code> date. According to
the PROV ontology, the activity of issuing a document involves two different states of the document: the document before it was issued
@@ -763,10 +772,8 @@
has not changed. Generally, there are two approaches to deal with this issue:</p>
</p><p>
1) To create new instances of entities, typically as blank nodes, that are all related to the original
- document by means of <code>prov:specializationOf</code>.
- This leads to verbose and not very intuitive data models, e.g. think
- about the translation of a single <code>dct:publisher</code>
- statement, where one would expect to somehow find some activity and
+ document by means of <code>prov:specializationOf</code>. This leads to bloated and not very intuitive data models, e.g. think
+ about the translation of a single <code>dct:publisher</code> statement, where anyone would expect to somehow find some activity and
agent that are directly related to the document (as in <a href="#figure_mapping_example">Figure 1</a>).
</p><p>
<div id = "figure_mapping_example" class="figure" style="text-align: center;">
@@ -781,7 +788,7 @@
(<code>:_activity</code>). However, this representation leads to a misinterpretation of the <code>dct</code> statement, as shown in the example of
<a href="#figure_mapping_example_conflating">Figure 2</a>. The representation implies that <code>ex:doc1</code>
was generated by <code>_:activity</code> and then used by <code>_:activity</code> afterwards, instead of being used and then being generated by
- <code>_:activity</code> (PROV entities must be generated before being used).
+ <code>_:activity</code> (<code>prov:Entities</code> must exist before being used).
</p><p>
<div id = "figure_mapping_example_conflating" class="figure" style="text-align: center;">
@@ -822,69 +829,73 @@
<tr>
<th>DC Term</th>
<th>Relation</th>
- <th>PROV-O Term</th>
+ <th>PROV Term</th>
<th>Rationale</th>
</tr>
<tr>
<td><b>dct:Agent</b></td>
<td>owl:equivalentClass</td>
- <td> prov:Agent</td>
+ <td> prov:Agent.</td>
<td>Both <code>dct:Agent</code> and <code>prov:Agent</code> refer to the same concept: a resource that has the power to act (which then has responsibility for an activity).</td>
</tr>
<tr>
- <td><b>dct:rightsHolder</b></td>
+ <td><b id="term_rightsHolder">dct:rightsHolder</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
<td>The rights holder has the attribution of the activity that created the licensed resource.</td>
</tr>
<tr>
- <td><b>dct:creator</b></td>
+ <td><b id="term_creator">dct:creator</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
<td>A creator is the agent who created the resource. He is the one involved in the creation activity that led to the resource.
He has the attribution for that activity</td>
</tr>
<tr>
- <td><b>dct:publisher</b></td>
+ <td><b id="term_publisher">dct:publisher</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
<td>A publisher has the attribution of the publishing activity that led to the published resource.</td>
</tr>
<tr>
- <td><b>dct:contributor</b></td>
+ <td><b id="term_contributor">dct:contributor</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
- <td>A contributor is involved either in the creation activity or in the updating of the resource. Therefore he/she is attributed to take
+ <td>A contributor is involved either in the creation activity or in
+the updating of the resource. Therefore he/she is attributed to take
part in those activities.</td>
</tr>
<tr>
- <td><b>dct:isVersionOf</b></td>
+ <td><b id="term_isVersionOf">dct:isVersionOf</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasDerivedFrom</td>
<td><code>dct:isVersionOf</code> refers to "a related resource to which the current resource is a version, edition or adaptation".
Hence the current resource has been derived from the original one.</td>
</tr>
<tr>
- <td><b>dct:isFormatOf</b></td>
+ <td><b id="term_isFormatOf">dct:isFormatOf</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:alternateOf</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>
</tr>
<tr>
- <td><b>dct:hasFormat</b></td>
+ <td><b id="term_has_Format">dct:hasFormat</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:alternateOf</td>
<td> See rationale for <code>dct:isFormatOf</code></td>
</tr>
<tr>
- <td><b>dct:replaces</b></td>
+ <td><b id="term_replaces">dct:replaces</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasInfluencedBy</td>
- <td>This mapping is not straightforward. There is a relation between two resources when the former replaces the latter, but it is not necessarily
- derivation, revision, specification or alternate. Thus, the term is mapped to <code>prov:wasInfluencedBy</code></td>
+ <td>This mapping is not straightforward. There is a relation between
+ two resources when the former replaces the latter, but it is not
+necessarily
+ derivation, revision, specification or alternate. Thus, the term is
+mapped to <code>prov:wasInfluencedBy</code></td>
</tr>
<tr>
- <td><b>dct:source </b></td>
+ <td><b id="term_source">dct:source </b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasDerivedFrom</td>
<td>In Dublin Core, <code>dct:source</code> is defined as a "related resource from which the described resource is derived", which matches the notion of derivation
@@ -893,47 +904,51 @@
<tr>
<td><b>dct:type</b></td>
<td>owl:equivalentProperty</td>
- <td>rdf:type</td>
- <td>Both properties relate two resources in a similar
- way: the nature of the resource (or genre). Mapping to
- PROV-DM should use <code>prov:type<code>.</td>
+ <td>prov:type</td>
+ <td>Both properties relate two resources in a similar way: the nature of the resource (or genre).</td>
</tr>
<tr>
- <td><b>dct:created</b></td>
+ <td><b id="term_created">dct:created</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td><code>dct:created</code> is a property used to describe the time of creation of an entity, which corresponds to the time of its generation.
- The rationale to map this property as a subclass of <code>prov:generatedAtTime</code> is that resources in Dublin Core may have
- many dates associated to them (creation, modification, issue, etc.), each of which could correspond to a different version of the document.
- In this case, the creation is the first date asserted to the document, but doesn't necessarily correspond to the current version of the resource.</td>
+ The rationale to map this property as a subclass of <code>prov:generatedAtTime</code>
+ is that resources in Dublin Core may have
+ many dates associated to them (creation, modification, issue, etc.),
+ each of which could correspond to a different version of the document.
+ In this case, the creation is the first date asserted to the
+document, but doesn't necessarily correspond to the current version of
+the resource.</td>
</tr>
<tr>
- <td><b>dct:issued</b></td>
+ <td><b id="term_issued">dct:issued</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td>Date when the resource was issued. It is mapped as a subproperty of <code>prov:generatedAtTime</code> because the issued resource is an entity itself,
which has been generated at a certain time.</td>
</tr>
<tr>
- <td><b>dct:dateAccepted</b></td>
+ <td><b id="term_dateAccepted">dct:dateAccepted</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
- <td>The rationale is similar to the previous two properties: the version of the resource which was accepted could be different from the created or issued one.</td>
+ <td>The rationale is similar to the previous two properties: the
+version of the resource which was accepted could be different from the
+created or issued one.</td>
</tr>
<tr>
- <td><b>dct:dateCopyrighted</b></td>
+ <td><b id="term_dateCopyrighted">dct:dateCopyrighted</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td>See <code>dct:dateAccepted</code></td>
</tr>
<tr>
- <td><b>dct:dateSubmitted</b></td>
+ <td><b id="term_dateSubmitted">dct:dateSubmitted</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td>See <code>dct:dateAccepted</code></td>
</tr>
<tr>
- <td><b>dct:modified</b></td>
+ <td><b id="term_modified">dct:modified</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td>See <code>dct:dateAccepted</code></td>
@@ -942,6 +957,81 @@
</table>
</div>
With the direct mapping, a metadata record such as <a href="#example1">example 1</a> will infer that
+ the resource was <code>prov:generatedAtTime</code> at two different
+times. Although this may seem inconsistent, it is supported by PROV and
+it is due to the difference
+ between Dublin Core and PROV resources: while the former conflates
+more than one version or "state" of the resource in a single entity, the
+ latter
+ proposes to separate all of them. Thus, the mapping produces
+provenance that complies with the current definition of entity but
+ it does not comply with all the PROV constraints [<cite><a href="#bib-PROV-CONSTRAINTS" class="bibref">PROV-CONSTRAINTS</a></cite>].
+ <p></p>
+ <p>
+ Some properties have been found to be superproperties of certain prov concepts. These can be seen below in <a href="#list_of_direct_mappings2">Table 4</a>:
+ <!-- SHOULD ADD THIS FOR EACH
+ <pre rel="prov:wasQuotedFrom" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_qualifiedAttribution.ttl"
+ -->
+ </p>
+
+ <div id="list_of_direct_mappings2">
+ <table>
+ <caption> <a href="#list_of_direct_mappings2"> Table 4:</a> Direct mappings (2) </caption>
+ <tbody>
+ <tr>
+ <th>PROV Term</th>
+ <th>Relation</th>
+ <th>DC Term</th>
+ <th>Rationale</th>
+ </tr>
+ <tr>
+ <td>prov:hadPrimarySource</td>
+ <td>rdfs:subPropertyOf</td>
+ <td><b>dct:source</b></td>
+ <td>The definition of <code>prov:hadPrimarySource</code> ("something produced by some agent with direct experience
+ and knowledge about the topic") is more restrictive than <code>dct:source</code> ( "A related resource from which the
+ described resource is derived").</td>
+ </tr>
+ <tr>
+ <td>prov:wasRevisionOf</td>
+ <td>rdfs:subPropertyOf</td>
+ <td><b>dct:isVersionOf</b></td>
+ <td>Similar to the previous property, <code>prov:wasRevisionOf</code> is more restrictive in the sense that it refers to revised version of a resource, while
+ <code>dct:isVersionOf</code> involves versions, editions or adaptations of the original resource.</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <p>
+ <a href="#list_of_direct_mappings_no_prov_core">Table 5</a> enumerates the mapping of the <code>dct</code> properties that map to inverse relationships in PROV. These
+ have been separated in a different table because they don't belong to the core of PROV.
+ </p>
+ <div id="list_of_direct_mappings_no_prov_core" >
+ <table>
+ <caption> <a href="#list_of_direct_mappings_no_prov_core"> Table 5:</a> Direct mappings to the PROV terms not included in the core </caption>
+ <tbody>
+ <tr>
+ <th>PROV Term</th>
+ <th>Relation</th>
+ <th>DC Term</th>
+ <th>Rationale</th>
+ </tr>
+ <tr>
+ <td><b id="term_hasVersion">dct:hasVersion</b></td>
+ <td>rdfs:subPropertyOf</td>
+ <td>prov:hadDerivation</td>
+ <td>Inverse property of <code>dct:isVersionOf</code>.</td>
+ </tr>
+ <tr>
+ <td><b id="term_isReplacedBy">dct:isReplacedBy</b></td>
+ <td>rdfs:subPropertyOf</td>
+ <td>prov:influenced</td>
+ <td>Inverse property of <code>dct:replaces</code></td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ With the direct mapping, a metadata record such as <a href="#example1">example 1</a> will infer that
the resource was <code>prov:generatedAtTime</code> at two different times. Although this may seem inconsistent, it is supported by PROV and it is due to the difference
between Dublin Core and PROV resources: while the former conflates more than one version or "state" of the resource in a single entity, the latter
proposes to separate all of them. Thus, the mapping produces provenance that complies with the current definition of entity but
@@ -959,7 +1049,7 @@
<caption> <a href="#list_of_direct_mappings2"> Table 4:</a> Direct mappings (2) </caption>
<tbody>
<tr>
- <th>PROV-O Term</th>
+ <th>PROV Term</th>
<th>Relation</th>
<th>DC Term</th>
<th>Rationale</th>
@@ -988,13 +1078,12 @@
</p>
<div id="list_of_direct_mappings_no_prov_core" ALIGN="center">
<table>
- <caption> <a
- href="#list_of_direct_mappings_no_prov_core"> Table 5:</a> Direct mappings to the inverse PROV terms not included in the core </caption>
+ <caption> <a href="#list_of_direct_mappings_no_prov_core"> Table 5:</a> Direct mappings to the PROV terms not included in the core </caption>
<tbody>
<tr>
+ <th>PROV Term</th>
+ <th>Relation</th>
<th>DC Term</th>
- <th>Relation</th>
- <th>PROV-O Term</th>
<th>Rationale</th>
</tr>
<tr>
@@ -1071,26 +1160,26 @@
A creator is the agent associated with role CreatorRole in the CreationActivity that created a specialization of the entity (?document).
<pre class="code">
CONSTRUCT {
- ?document a prov:Entity ;
- prov:wasAttributedTo ?agent .
-
- ?agent a prov:Agent .
-
- _:activity a prov:Activity, prov:CreationActivity ;
- prov:wasAssociatedWith ?agent ;
- prov:qualifiedAssociation [
- a prov:Association ;
- prov:agent ?agent ;
- prov:hadRole prov:CreatorRole .
- ].
-
- _:resulting_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasAttributedTo ?agent .
-
+ ?document a prov:Entity ;
+ prov:wasAttributedTo ?agent.
+
+ ?agent a prov:Agent .
+
+ _:activity a prov:Activity, prov:CreationActivity ;
+ prov:wasAssociatedWith ?agent;
+ prov:qualifiedAssociation [
+ a prov:Association;
+ prov:agent ?agent;
+ prov:hadRole prov:CreatorRole .
+ ].
+
+ _:resulting_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasAttributedTo ?agent.
+
} WHERE {
- ?document dct:creator ?agent .
+ ?document dct:creator ?agent.
}
</pre>
</section>
@@ -1179,7 +1268,7 @@
_:created_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:qualifiedGeneration [
a prov:Generation ;
prov:atTime ?date ;
@@ -1209,7 +1298,7 @@
_:iss_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1239,7 +1328,7 @@
_:modified_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1269,7 +1358,7 @@
_:accepted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1299,7 +1388,7 @@
_:copyrighted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1328,7 +1417,7 @@
_:submitted_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:wasDerivedFrom _:used_entity ;
prov:qualifiedGeneration [
a prov:Generation ;
@@ -1373,7 +1462,7 @@
_:created_entity a prov:Entity ;
prov:specializationOf ?document ;
prov:wasGeneratedBy _:activity ;
- prov:generatedAtTime ?date;
+ prov:wasGeneratedAtTime ?date;
prov:qualifiedGeneration [
a prov:Generation ;
prov:atTime ?date ;
@@ -1608,15 +1697,5 @@
We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo and Satya Sahoo for their feedback; and María Poveda and Idafen Santana Pérez for his help with the HTML generation.
</p>
</section>
- <section class="appendix">
- <h2>Changes since First Working Draft</h2>
- <ul>
- <li>Corrected table headers</li>
- <li>dct:type mapped to rdf:type, not prov:type (which is not in PROV-O)</li>
- <li>Minor indenting correction on SPARQL statements</li>
- <li>Corrected prov:wasGeneratedAtTime to prov:generatedAtTime</li>
- <li>Minor typesetting to highlight DC Terms more intuitively</li>
- </ul>
- </section>
</body>
-</html>
+</html>
\ No newline at end of file