You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a EU recommendation for using DCAT-AP as a schema to describe the metadata for data repositories, as to provide interoperability (alignment) across data repositories. This might be a direction that DANS will itself take. Currently, it appears that the biggest push towards DCAT-AP is coming from the medical sciences community (Cees Hof is most informed about it)
In this landscape analysis it is important that we understand,
General questions
a) what we are dealing with?
b) what is the recommendation from EU. And is it a recommendation or mandate?
c) what and how are other data repositories using DCAT-AP
There is a EU recommendation for using DCAT-AP as a schema to describe the metadata for data repositories, as to provide interoperability (alignment) across data repositories. This might be a direction that DANS will itself take. Currently, it appears that the biggest push towards DCAT-AP is coming from the medical sciences community (Cees Hof is most informed about it)
In this landscape analysis it is important that we understand,
General questions
a) what we are dealing with?
b) what is the recommendation from EU. And is it a recommendation or mandate?
c) what and how are other data repositories using DCAT-AP
Elements (Building blocks)
=
definition of terms (classes and propretries)see Brainstorm on SuperCatalog and CKAN DCAT-ext and examples (ask @andrecastro0o more about this)
The text was updated successfully, but these errors were encountered: