Skip to content
Permalink
Browse files

Merge pull request #818 from w3c/dcat-purge-closed-issues-daveb

Purge closed issue notes  - thanks for reviewing, @dr-shorthair
  • Loading branch information...
davebrowning committed Mar 15, 2019
2 parents 0b72304 + aa32793 commit 4a85130d54ca004c6d1e4c294a7c07af6f4fb1f5
Showing with 11 additions and 36 deletions.
  1. +11 −36 dcat/index.html
@@ -136,7 +136,7 @@ <h2>Introduction</h2>

<section id="motivation" class="informative"><h2>Motivation for change</h2>
<p>The original Recommendation [[?VOCAB-DCAT-20140116]], published in January 2014, provided the basic framework for describing datasets. Importantly, it made the distinction between a dataset as an abstract idea and a distribution as a manifestation of the dataset. Although DCAT has been widely adopted, it has become clear that the original specification lacked a number of essential features that were added either through application profiles, such as the European Commission's DCAT-AP [[?DCAT-AP]], or the development of larger vocabularies that, to a greater or lesser extent, built upon the base standard, such as the Healthcare and Life Sciences Community Profile [[?HCLS-Dataset]], the Data Tag Suite [[?DATS]] and more. This version of DCAT has been developed to address the specific shortcomings that have come to light through the experiences of different communities, the aim being, of course, to improve interoperability between the outputs of these larger vocabularies.
For example, in this new DCAT version, we provide classes, properties and guidance to address <a href="Dereferenceable-identifiers">identifiers</a>, <a href="#quality-information">quality information</a>, <a href="#data-citation">data citation</a> issues.</p>
For example, in this new DCAT version, we provide classes, properties and guidance to address <a href="#Dereferenceable-identifiers">identifiers</a>, <a href="#quality-information">quality information</a>, <a href="#data-citation">data citation</a> issues.</p>
<p>This draft includes re-writing of the specification throughout. Significant changes from the 2014 Recommendation are marked within the text using "Note" sections, as well as being described in the <a href="#changes">Change History</a>.</p>

</section>
@@ -953,16 +953,18 @@ <h4>Property: contact point</h4>
<section id="Property:resource_creator">
<h4>Property: resource creator</h4>

<p class="note">
<div class="note">
<p>
New property added in this revision of DCAT, specifically added when considering the data citation requirement and
added to the <a href="#Class:Resource"><code>dcat:Resource</code></a> class, as the Dataset superclass. For more details, see
the <a href="data-citation">data citation</a> section.
</p>
the <a href="#data-citation">data citation</a> section.
</p>

<p class="issue" data-number="80">
<p>
The use of the [[?PROV-O]] qualified-attribution pattern is <a href="#qualified-attribution">described below</a>.
`dct:creator` corresponds with a general attribution with the role 'creator'.
</p>
</p>
</div>

<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/creator">dct:creator</a></th></tr></thead>
@@ -1053,7 +1055,7 @@ <h4>Property: language</h4>
<section id="Property:resource_publisher">
<h4>Property: publisher</h4>

<p class="issue" data-number="80">
<p class="note">
The use of the [[?PROV-O]] qualified-attribution pattern is <a href="#qualified-attribution">described below</a>.
`dct:publisher` corresponds with a general attribution with the role 'publisher'.
</p>
@@ -1169,11 +1171,6 @@ <h4>Property: resource relation</h4>
<a href="http://purl.org/dc/terms/relation"><code>dct:relation</code></a> is a super-property of a number of more specific properties which express more precise relationships, so use of <code>dct:relation</code> is not inconsistent with a subsequent reclassification with more specific semantics, though the more specialized sub-properties <em title="SHOULD" class="rfc2119">SHOULD</em> be used to link a dataset to component and supplementary resources if possible.
</p>

<p class="issue" data-number="81">
The general need to describe relationships between datasets has been identified as a requirement to be satisfied in the revision of DCAT.
Guidance on the use of more specific relationship predicates is required, particularly in the context of the <code>dcat:Dataset</code> sub-class.
</p>

<p class="note">
Use of this Dublin Core Terms property in this context added in this revision of DCAT.
</p>
@@ -1487,10 +1484,6 @@ <h3>Class: Dataset</h3>
</p>


<p class="issue" data-number="59">
The need to more formally encode access restrictions for both datasets and distributions has been identified as a requirement to be satisfied in the revision of DCAT.
</p>

<p class="issue" data-number="60">
The need to provide richer descriptions of dataset aspects (e.g. instrument/sensor used, spatial feature, observable property, quantity kind) has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
@@ -1511,9 +1504,6 @@ <h3>Class: Dataset</h3>
<p class="issue" data-number="86">
The need to be able to provide usage notes for a dataset or distribution has been identified as a requirement to be satisfied in the revision of DCAT.
</p>
<p class="issue" data-number="433">
The need to be able to provide citations for a distribution has been identified as a potential requirement to be satisfied in the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></th></tr></thead>
@@ -1550,11 +1540,6 @@ <h4>Property: dataset distribution</h4>
</table>
</section>

<p class="issue" data-number="81">
<a href="https://github.com/w3c/dxwg/issues/81">Issue #81</a> concerns the general need to describe relationships between datasets.
Guidance on the use of specializations of <code>dct:relation</code> is required in the context of <code>dcat:Dataset</code>.
</p>

<section id="Property:dataset_frequency">
<h4>Property: frequency</h4>
<table class="definition">
@@ -1731,14 +1716,6 @@ <h3>Class: Distribution</h3>
<a href="#Property:distribution_update_date">update/modification date</a>,
</p>

<p class="issue" data-number="54">
The packaging of files in a <code>dcat:Distribution</code> is being considered as part of the revision of DCAT.
</p>

<p class="issue" data-number="59">
The need to more formally encode access restrictions for both datasets and distributions has been identified as a requirement to be satisfied in the revision of DCAT.
</p>

<table class="definition">
<thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/dcat#Distribution">dcat:Distribution</a></th></tr></thead>
<tbody>
@@ -1984,10 +1961,8 @@ <h4>Property: spatial resolution</h4>
<p class="note">
New property in this context in this revision of DCAT.
</p>
</tbody>
</table>

</section>
</section>

<section id="Property:distribution_temporalresolution">
<h4>Property: temporal resolution</h4>
@@ -4241,7 +4216,7 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>
</li>

<li>
<a href="#Property:resource_relation">Property: resource relation</a>: The property <code>dct:relation</code> is recommended for use in the context of a catalogued resource to capture general relationships, including the case where the package of resources associated with a catalogued item includes a mixture of representations, parts, documentation and other elements which are not strictly 'distributions' of a dataset - see <a href="https://github.com/w3c/dxwg/issues/253">Issue #253</a>.
<a href="#Property:resource_relation">Property: resource relation</a>: The property <code>dct:relation</code> is recommended for use in the context of a catalogued resource to capture general relationships, including the case where the package of resources associated with a catalogued item includes a mixture of representations, parts, documentation and other elements which are not strictly 'distributions' of a dataset - see <a href="https://github.com/w3c/dxwg/issues/253">Issue #253</a>. The more general use of <code>dct:relation</code> is driven by the requirement documented in <a href="https://github.com/w3c/dxwg/issues/81">Issue #81</a>.
</li>


0 comments on commit 4a85130

Please sign in to comment.
You can’t perform that action at this time.