Q: Question about dcat:theme and dcat:themeTaxonomy

[svituz]

The Question
Checking the FDP's specs at https://specs.fairdatapoint.org/ I saw that the Catalog scheme has the dcat:themeTaxonomy but doesn't have a dcat:theme property, contrary to DCAT2 model.
Using this implementation, I notice that the dcat:themeTaxonomy of a Catalog is the list of the its Datasets' dcat:theme.

I would like to have a hierarchy where the Catalog has a generic theme and its Datasets a more specific one.
For example, the Catalog with Datasets regarding nervous system diseases (theme ICD-10:G00-G99.9, and a dataset about Epilepsy (theme http://purl.bioontology.org/ontology/ICD10/G40.1).

My question is, why the Catalog doesn't have a dcat:theme property? Is it "legal" that in my implementation I add the property to represent scenarios similar to the one described?

Extension part
FDP Schema

[luizbonino]

Hi @svituz, the FDP reference implementation is deployed with a number of default metadata schemas, including catalog, dataset, etc. Indeed, in these default schemas, the dcat:Catalog has only dcat:themTaxonomy and not dcat:theme. This happened because an oversight. When we started the development of the FDP, only DCAT version 1 existed and there Catalog only had the property themeTaxonomy and only Dataset had the property theme. With DCAT v2, they included the abstract class Resource and made Catalog a subclass of Dataset. Since dcat:Resource has the property dcat:theme, all its subclasses, including dcat:Dataset and dcat:Catalog inherit this property. THe oversight was that we didn't update this part of the schemas for compliance with DCAT v2. In an upcoming version of the FDP we will fix this oversight.
You can definitely edit the schemas adding/deleting the properties you would like.

[markwilkinson]

In addition to the solution above, it is possible to create a "correct" DCAT1 record, with a themeTaxonomy on the catalog and a theme on the dataset, but you have to HTTP PUT the corrected record(s) into the FDP. It does happily accept it, though!