CR7 Repository. Remove the property dcat:themeTaxonomy

05/01/2016

This property has never been used. The controlled vocabulary for dcat:theme does not change from repository to repository.

Component

Documentation

Category

improvement

Comments

Tue, 05/01/2016 - 14:12

Proposed resolution: In the future, there may be more than one theme vocabularies in use: (a) the Eurovoc domains and (b) the MDR Dataset Themes vocabulary. Removing the property makes it impossible to identify the theme vocabulary used. In DCAT-AP this property is recommended.

Wed, 06/01/2016 - 17:04

Theoretically, I do fully agree. However, having two vocabularies in use will never be the case on Joinup. We already hesitate with one. Two would make the property even less relevant as it is now. But I guess that we could leave it and not use it.

Sun, 07/02/2016 - 11:46

We will make no change. If you don't have the information, it's OK not to provide it.

Mon, 08/02/2016 - 09:25

Makx, I think that the resolution of this issue depends also on the discussion for CR20

 

Wed, 10/02/2016 - 19:48

As CR20 has been resolved to keep theme, the property themeTaxonomy should also stay.

Mon, 15/02/2016 - 14:31

Closed, themeTaxonomy becomes recommended.

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