This property has never been used. The controlled vocabulary for dcat:theme does not change from repository to repository. Component Documentation Category improvement Report abusive content Share Comments Stefanos Kotoglou Tue, 05/01/2016 - 15:12 Permalink 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. Thibaut Knop Wed, 06/01/2016 - 18:04 Permalink 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. Makx DEKKERS Sun, 07/02/2016 - 12:46 Permalink We will make no change. If you don't have the information, it's OK not to provide it. Nikos Loutas Mon, 08/02/2016 - 10:25 Permalink Makx, I think that the resolution of this issue depends also on the discussion for CR20 Makx DEKKERS Wed, 10/02/2016 - 20:48 Permalink As CR20 has been resolved to keep theme, the property themeTaxonomy should also stay. Zakaria Arrassi Mon, 15/02/2016 - 15:31 Permalink Closed, themeTaxonomy becomes recommended.