Skip to content

Commit

Permalink
replacing DCAT 2014 by DCAT 1
Browse files Browse the repository at this point in the history
  • Loading branch information
@riccardoAlbertoni
riccardoAlbertoni committed Oct 9, 2020
1 parent 2a73b16 commit e818f8d
Showing 1 changed file with 27 additions and 27 deletions.
54 changes: 27 additions & 27 deletions dcat/index.html
View file
Expand Up @@ -13,9 +13,9 @@

<!-- Disclaimer -->
<aside class="note">
<p>DCAT 2 supersedes DCAT [[?VOCAB-DCAT-20140116]], but it does not make it obsolete. DCAT 2 maintains the DCAT namespace as its terms preserve backward compatibility with DCAT [[?VOCAB-DCAT-20140116]]. DCAT 2 relaxes constraints and adds new classes and properties, but these changes do not break the definition of previous terms.</p>
<p>DCAT 2 supersedes DCAT [[?VOCAB-DCAT-20140116]] (hereafter named DCAT 1), but it does not make it obsolete. DCAT 2 maintains the DCAT namespace as its terms preserve backward compatibility with DCAT [[?VOCAB-DCAT-20140116]]. DCAT 2 relaxes constraints and adds new classes and properties, but these changes do not break the definition of previous terms.</p>

<p>Any new implementation is expected to adopt DCAT 2, while the existing implementations do not need to upgrade to it, unless they want to use the new features. In particular, current DCAT deployments that do not overlap with the DCAT 2 new features (e.g., data services, time and space properties qualified relations, packaging) don't need to change anything to remain in conformance with DCAT 2.
<p>Any new implementation is expected to adopt DCAT 2, while the existing implementations do not need to upgrade to it, unless they want to use the new features. In particular, current DCAT 1 deployments that do not overlap with the DCAT 2 new features (e.g., data services, time and space properties qualified relations, packaging) don't need to change anything to remain in conformance with DCAT 2.
</p>
</aside>
<section id="abstract">
Expand Down Expand Up @@ -309,7 +309,7 @@ <h3>DCAT scope</h3>

<aside class="note">
<p>
The scope of DCAT 2014 [[?VOCAB-DCAT-20140116]] was limited to catalogs of datasets.
The scope of DCAT 1 [[?VOCAB-DCAT-20140116]] was limited to catalogs of datasets.
A number of use cases for the revision [[?DCAT-UCR]] involve <b>data services</b> as members of a catalog - see <a data-cite="DCAT-UCR#ID6">&sect;&nbsp;<span class="secno">5.16 </span>DCAT Distribution to describe Web services</a> and
<a data-cite="DCAT-UCR#ID18">&sect;&nbsp;<span class="secno">5.18 </span>Modeling service-based data access</a>.
Hence, the scope of this revision of DCAT includes both datasets and data services to enable these to be part of a DCAT conformant catalog.
Expand Down Expand Up @@ -675,7 +675,7 @@ <h3>RDF representation</h3>
</p-->

<!--NoBacklogNorCR p class="issue" data-number="110">
The axiomatization of DCAT 2014 used global domain and range constraints for many of the properties defined in the DCAT namespace [[?VOCAB-DCAT-20140116]]. This makes quite strong ontological commitments, some of which are now being reconsidered - see individual issues noted inline below.
The axiomatization of DCAT 1 used global domain and range constraints for many of the properties defined in the DCAT namespace [[?VOCAB-DCAT-20140116]]. This makes quite strong ontological commitments, some of which are now being reconsidered - see individual issues noted inline below.
</p-->

<p>The (revised) DCAT vocabulary is <a href="https://www.w3.org/ns/dcat#">available in RDF</a>.
Expand All @@ -694,7 +694,7 @@ <h3>RDF representation</h3>
</ol>

<!--NoBacklogNorCR p class="issue" data-number="144">
The implementation of a DCAT 2014 profile of the revised DCAT is being considered.
The implementation of a DCAT 1 profile of the revised DCAT is being considered.
</p -->


Expand Down Expand Up @@ -731,7 +731,7 @@ <h4>Element definitions</h4>
<h3>Class: Catalog</h3>

<aside class="note">
<p>The scope of DCAT 2014 was catalogs of datasets [[?VOCAB-DCAT-20140116]]. This has been generalized, and properties common to all cataloged resources are now associated with a super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>.</p>
<p>The scope of DCAT 1 was catalogs of datasets [[?VOCAB-DCAT-20140116]]. This has been generalized, and properties common to all cataloged resources are now associated with a super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>.</p>
<p>Moreover, an explicit class for <a href="#Class:Data_Service">data services</a> has been added in this revision of DCAT, to enable these to be part of a catalog.</p>
<p>Finally, <code>dcat:Catalog</code> has been made a sub-class of <code>dcat:Dataset</code>, and provision for catalogs to be composed of other catalogs is also enabled.</p>
<p>See <a href="https://github.com/w3c/dxwg/issues/116">Issue #116</a> and <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a>.</p>
Expand Down Expand Up @@ -1023,7 +1023,7 @@ <h4>Property: contact point</h4>

<aside class="note">
<p>
In DCAT 2014 [[VOCAB-DCAT-20140116]] the domain of <code>dcat:contactPoint</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision. See <a href="https://github.com/w3c/dxwg/issues/95">Issue #95</a>.
In DCAT 1 [[VOCAB-DCAT-20140116]] the domain of <code>dcat:contactPoint</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision. See <a href="https://github.com/w3c/dxwg/issues/95">Issue #95</a>.
</p>
</aside>

Expand Down Expand Up @@ -1177,7 +1177,7 @@ <h4>Property: theme/category</h4>

<aside class="note">
<p>
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:theme</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:theme</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
See <a href="https://github.com/w3c/dxwg/issues/123">Issue #123</a>.
</p>
</aside>
Expand Down Expand Up @@ -1331,7 +1331,7 @@ <h4>Property: keyword/tag</h4>

<aside class="note">
<p>
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:keyword</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision - see <a href="https://github.com/w3c/dxwg/issues/121">Issue #121</a>.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:keyword</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision - see <a href="https://github.com/w3c/dxwg/issues/121">Issue #121</a>.
</p>
</aside>

Expand All @@ -1350,7 +1350,7 @@ <h4>Property: landing page</h4>

<aside class="note">
<p>
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:landingPage</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision - see <a href="https://github.com/w3c/dxwg/issues/122">Issue #122</a>.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:landingPage</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision - see <a href="https://github.com/w3c/dxwg/issues/122">Issue #122</a>.
</p>
</aside>

Expand Down Expand Up @@ -1622,8 +1622,8 @@ <h3>Class: Dataset</h3>

<aside class="note">
<p>
In DCAT 2014 [[?VOCAB-DCAT-20140116]] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a member of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> [[?DCTERMS]].
The scope of <a href="#Class:Dataset"><code>dcat:Dataset</code></a> also includes other members of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a>, such as various multimedia (imagery, sound, video) and text, so the sub-class relationship from DCAT 2014 [[?VOCAB-DCAT-20140116]] has been removed in this revised DCAT vocabulary - see <a href="https://github.com/w3c/dxwg/issues/98">Issue #98</a>.
In DCAT 1 [[?VOCAB-DCAT-20140116]] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a member of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> [[?DCTERMS]].
The scope of <a href="#Class:Dataset"><code>dcat:Dataset</code></a> also includes other members of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a>, such as various multimedia (imagery, sound, video) and text, so the sub-class relationship from DCAT 1 [[?VOCAB-DCAT-20140116]] has been removed in this revised DCAT vocabulary - see <a href="https://github.com/w3c/dxwg/issues/98">Issue #98</a>.
</p>
<p>
Note that members of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> may appear as the value of the <a href="#Property:resource_type"><code>dct:type</code></a> property, as shown in <a href="#classifying-dataset-types"></a>.
Expand Down Expand Up @@ -2941,7 +2941,7 @@ <h2>License and rights statements</h2>

<aside class="note">
<p>
DCAT 2014 handling of license and rights do not appear to satisfy all requirements [[?VOCAB-DCAT-20140116]].
DCAT 1 handling of license and rights do not appear to satisfy all requirements [[?VOCAB-DCAT-20140116]].
The recently completed W3C ODRL model [[?ODRL-MODEL]] and vocabulary [[?ODRL-VOCAB]] provide a rich language for describing many kinds of rights and obligations.
In this section, we describe some patterns for linking DCAT Datasets and/or Distributions to suitable license and rights expressions.
</p>
Expand Down Expand Up @@ -3407,7 +3407,7 @@ <h2>Data citation</h2>

<p>
In order to support data citation, this DCAT revision has added the consideration of <a href="#dereferenceable-identifiers">dereferenceable identifiers</a> and support for indicating
<a href="#Property:resource_creator">the creators of the cataloged resources</a>. The remaining properties necessary for data citation were already available in DCAT 2014 [[?VOCAB-DCAT-20140116]].
<a href="#Property:resource_creator">the creators of the cataloged resources</a>. The remaining properties necessary for data citation were already available in DCAT 1 [[?VOCAB-DCAT-20140116]].
</p>

<p>
Expand Down Expand Up @@ -3992,8 +3992,8 @@ <h2>Alignment with Schema.org</h2>
General purpose Web search services that use metadata at all rely primarily on [[?SCHEMA-ORG]], so the relationship of DCAT to [[?SCHEMA-ORG]] is of interest for data providers and catalog publishers who wish their datasets and services to be exposed through those indexes.
</p>
<p>
A <a href="https://www.w3.org/wiki/WebSchemas/Datasets">mapping between DCAT 2014 and schema.org</a> was discussed on the original proposal to extend [[?SCHEMA-ORG]] for describing datasets and data catalogs.
Partial mappings between DCAT 2014 [[?VOCAB-DCAT-20140116]] and [[?SCHEMA-ORG]] were provided earlier by the
A <a href="https://www.w3.org/wiki/WebSchemas/Datasets">mapping between DCAT 1 and schema.org</a> was discussed on the original proposal to extend [[?SCHEMA-ORG]] for describing datasets and data catalogs.
Partial mappings between DCAT 1 [[?VOCAB-DCAT-20140116]] and [[?SCHEMA-ORG]] were provided earlier by the
<a href="https://www.w3.org/2015/spatial/wiki/ISO_19115_-_DCAT_-_Schema.org_mapping">Spatial Data on the Web Working Group</a>, building upon previous work.
</p>
<p>
Expand Down Expand Up @@ -4644,7 +4644,7 @@ <h3>Changes since the W3C Recommendation of 4 February 2020</h3>
</section>
<section id="changes-since-20140116">
<h3>Changes since the W3C Recommendation of 16 January 2014</h3>
<p>The document has undergone the following changes since the DCAT 2014 W3C Recommendation of 16 January 2014 [[?VOCAB-DCAT-20140116]]:</p>
<p>The document has undergone the following changes since the DCAT 1 W3C Recommendation of 16 January 2014 [[?VOCAB-DCAT-20140116]]:</p>

<ul>

Expand Down Expand Up @@ -4756,7 +4756,7 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>

<li>
<a href="#Class:Resource">Class: Cataloged resource</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to datasets. This has been generalized, and properties common to all cataloged resources are now associated with a super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to datasets. This has been generalized, and properties common to all cataloged resources are now associated with a super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>.
See <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a> and <a href="https://github.com/w3c/dxwg/issues/116">Issue #116</a>.
<!--
The wiki page on <a href="https://github.com/w3c/dxwg/wiki/Cataloguing-data-services">Cataloguing data services</a> describes some proposals related to this requirement.
Expand All @@ -4765,23 +4765,23 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>

<li>
<a href="#Class:Data_Service">Class: Data service</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to datasets. The new class <code>dcat:DataService</code> has been added to support cataloging of various kinds of data services.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to datasets. The new class <code>dcat:DataService</code> has been added to support cataloging of various kinds of data services.
See <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a>, <a href="https://github.com/w3c/dxwg/issues/56">Issue #56</a>, <a href="https://github.com/w3c/dxwg/issues/432">Issue #432</a>, <a href="https://github.com/w3c/dxwg/issues/821">Issue #821</a>.
</li>

<li><a href="#Class:Dataset">Class: Dataset</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a term of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> [[!DCTERMS]]. This relationship has been removed in the revised DCAT vocabulary.
In DCAT 1 [[?VOCAB-DCAT-20140116]] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a term of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> [[!DCTERMS]]. This relationship has been removed in the revised DCAT vocabulary.
See <a href="https://github.com/w3c/dxwg/issues/98">Issue #98</a>.
</li>

<li>
<a href="#Class:Distribution">Class: Distribution</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the definition of a <a href="#Class:Distribution"><code>dcat:Distribution</code></a> allowed a number of alternative interpretations. The definition has been rephrased to clarify that distributions are primarily <i>representations</i> of datasets.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the definition of a <a href="#Class:Distribution"><code>dcat:Distribution</code></a> allowed a number of alternative interpretations. The definition has been rephrased to clarify that distributions are primarily <i>representations</i> of datasets.
See <a href="https://github.com/w3c/dxwg/issues/172">Issue #52</a> and related use cases.
</li>

<li><a href="#Property:resource_theme">Property: theme/category</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:theme</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:theme</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
See <a href="https://github.com/w3c/dxwg/issues/123">Issue #123</a>.
</li>

Expand All @@ -4791,27 +4791,27 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>
</li>

<li><a href="#Property:resource_keyword">Property: keyword/tag</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:keyword</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:keyword</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
See <a href="https://github.com/w3c/dxwg/issues/121">Issue #121</a>.
</li>

<li><a href="#Property:resource_contact_point">Property: contact point</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:contactPoint</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:contactPoint</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
See <a href="https://github.com/w3c/dxwg/issues/95">Issue #95</a>.
</li>

<li><a href="#Property:resource_landing_page">Property: landing page</a>:
In DCAT 2014 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:landingPage</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
In DCAT 1 [[?VOCAB-DCAT-20140116]] the domain of <code>dcat:landingPage</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain has been relaxed in this revision.
See <a href="https://github.com/w3c/dxwg/issues/122">Issue #122</a>.
</li>

<li><a href="http://vocab.org/vann/#usageNote">Property: <code>vann:usageNote</code></a>:
DCAT 2014 [[?VOCAB-DCAT-20140116]] included documentation captured as text using <a href="http://vocab.org/vann/#usageNote"><code>vann:usageNote</code></a> elements, which is a sub-property of <code>rdfs:seeAlso</code> - an <code>owl:ObjectProperty</code> that cannot have a Literal value. This revision of DCAT has fixed these issues and replaced the use of <code>vann:usageNote</code> with <a href="https://www.w3.org/TR/skos-primer/#secdocumentation"><code>skos:scopeNote</code></a>.
DCAT 1 [[?VOCAB-DCAT-20140116]] included documentation captured as text using <a href="http://vocab.org/vann/#usageNote"><code>vann:usageNote</code></a> elements, which is a sub-property of <code>rdfs:seeAlso</code> - an <code>owl:ObjectProperty</code> that cannot have a Literal value. This revision of DCAT has fixed these issues and replaced the use of <code>vann:usageNote</code> with <a href="https://www.w3.org/TR/skos-primer/#secdocumentation"><code>skos:scopeNote</code></a>.
See <a href="https://github.com/w3c/dxwg/issues/233">Issue #233</a>.
</li>

<li><a href="#Property:record_conforms_to">Property: conforms to</a>:
DCAT 2014 [[?VOCAB-DCAT-20140116]] had no way of representing the conformance of a record metadata with a metadata standard. This revision has added the property <code>dct:conformsTo</code> for <code>dcat:CatalogRecord</code> to cover this requirement.
DCAT 1 [[?VOCAB-DCAT-20140116]] had no way of representing the conformance of a record metadata with a metadata standard. This revision has added the property <code>dct:conformsTo</code> for <code>dcat:CatalogRecord</code> to cover this requirement.
See <a href="https://github.com/w3c/dxwg/issues/502">Issue #502</a>.
</li>

Expand Down

0 comments on commit e818f8d

Please sign in to comment.