Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

develop a landscape analysis on DCAT, DCAT-AP and friends #1

Open
andrecastro0o opened this issue Nov 4, 2024 · 1 comment
Open
Assignees

Comments

@andrecastro0o
Copy link
Contributor

andrecastro0o commented Nov 4, 2024

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)

see Brainstorm on SuperCatalog and CKAN DCAT-ext and examples (ask @andrecastro0o more about this)

@andrecastro0o
Copy link
Contributor Author

@aapolimeno a few more references that might help in understanding the current context and user requirements for DCAT-AP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants