--- a/dc-note/dc-note.html Fri Nov 30 13:04:11 2012 +0100
+++ b/dc-note/dc-note.html Fri Nov 30 14:59:29 2012 +0100
@@ -37,7 +37,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
//specStatus: "WD-NOTE",
- specStatus: "ED",
+ specStatus: "FPWD-NOTE",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "prov-dc",
@@ -60,6 +60,7 @@
// 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",
+ //http://www.w3.org/TR/2012/NOTE-prov-dc-20121211/
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -675,7 +676,7 @@
</div>
<p>
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" [[DC-TERMS]],
+ 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
specify concrete aspects of provenance of a resource.
@@ -684,14 +685,14 @@
</p><p>
<a href="#example1">Example 1</a>: a simple metadata record:
<pre class="example" id="example1">
- ex:doc1 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:doc2 ;
- dct:format "HTML" .
+ex:doc1 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:doc2 ;
+ dct:format "HTML" .
</pre>
In <a href="#example1">Example 1</a>, <code>dct:title</code>, <code>dct:subject</code> and <code>dct:format</code>
are descriptions of the resource <code>ex:doc1</code>.
@@ -798,7 +799,11 @@
<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.
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>
+ </p>
+ <div class="note">
+ <p>Some of the terms of the list are still under discussion: <code>dct:replaces</code> and <code>dct:isVersionOf</code>.</p>
+ </div>
+ <p>
<div id="list_of_direct_terms" ALIGN="center">
<table>
<caption> <a href="#list_of_direct_terms"> Table 3:</a> Direct mappings </caption>
@@ -927,7 +932,7 @@
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 [[PROV_CONSTRAINTS]]</a>.
+ it does not comply with all the PROV constraints [[PROV-CONSTRAINTS]]</a>.
</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>:
@@ -1398,6 +1403,9 @@
</section>
<section>
<h2>List of terms excluded from the mapping</h2>
+ <div class="note">
+ <p>Some of the terms of the list are still under discussion: <code>dct:alternative</code> and <code>dct:references</code>.</p>
+ </div>
<p>
<table>
<caption> <a href="#list_of_excluded_terms"> Table 6:</a> List of terms excluded from the mapping </caption>
@@ -1583,7 +1591,7 @@
<section class="appendix">
<h2>Acknowledgements</h2>
<p>
- We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo and Satya Sahoo for their comments and feedback, and María Poveda and Idafen Santana Pérez for his help with the HTML generation.
+ 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>
</body>