Distinguish controlled vocabularies for dcat:theme and dcat:themeTaxonomy

29/08/2015

For the properties “themes” (dcat:themeTaxonomy), used for the Catalogue Class, and “theme/category” (dcat:theme), used for the Dataset Class, DCAT-AP requires the use of the same vocabulary; that is, the vocabulary under construction proposed in Annex II. Since the range for the two properties is different (skos:conceptScheme for the first property and skos:concept for the second one) and the classes in which they are used are different too, we believe the classifications to be used for the Catalogue and Dataset have to be different, in particular more generic for Catalogue and more detailed for Dataset. Thus, we think a more detailed controlled vocabulary, in addition to the one included in Annex II, must be defined.

 

This issue has been reported by Gabriele Ciasullo, Giorgia Lodi and Antonio Rotundo:

http://joinup.ec.europa.eu/mailman/archives/dcat_application_profile/2015-August/000297.html

Component

Documentation

Category

bug

Comments

Thu, 24/09/2015 - 09:26

 

Analysis: The object of the property dcat:themeTaxonomy should be the URI of the vocabulary, while the object of the property dcat:theme should be the URI of one of the terms in the vocabulary. The current draft does not make this distinction clear.

Proposal: URI of the codelist to be included in the specification.

Tue, 03/05/2016 - 09:24

The content of this field is kept private and will not be shown publicly.