So far we have not yet added all mandatory vocabularies that are to be used as ranges for certain DCAT-AP properties.
Here's the list of these: https://semiceu.github.io/DCAT-AP/releases/3.0.1/#controlled-vocabularies-to-be-used
We implemented the needed vocs for the theme and media_type slots already, since these are small enough to be provided as enums directly in dcat_ap_plus.yaml.
I believe, the best option would be to do the others with dynamic enums. I was wondering if we could have a cron job that uses OAK to periadically expend these dynamic enums into their own schemas, which we would then import into dcat_ap_plus.yaml.
Any thoughts @dalito, @HendrikBorgelt & @markdoerr?
So far we have not yet added all mandatory vocabularies that are to be used as ranges for certain DCAT-AP properties.
Here's the list of these: https://semiceu.github.io/DCAT-AP/releases/3.0.1/#controlled-vocabularies-to-be-used
We implemented the needed vocs for the
themeandmedia_typeslots already, since these are small enough to be provided as enums directly in dcat_ap_plus.yaml.I believe, the best option would be to do the others with dynamic enums. I was wondering if we could have a cron job that uses OAK to periadically expend these dynamic enums into their own schemas, which we would then import into dcat_ap_plus.yaml.
Any thoughts @dalito, @HendrikBorgelt & @markdoerr?