-
Notifications
You must be signed in to change notification settings - Fork 171
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
DKAN supporting DCAT-AP.de #2595
Comments
A few hints:
|
Thanks @akuckartz! We've found it challenging to understand exactly how to comply with the DCAT-AP standard, as there are many different implementations, country-specific standards, conflicting examples and different validators. The DCAT-AP endpoint that ships with DKAN was passing a generic European Commission-supported validator when it was released. It looks like this validator now lives at http://dcat-ap.semic.eu/dcat-ap_validator.html but is broken :\ Most people were requesting XML/RDF so that's what we focused on providing. If you have a current version of DKAN you should have a /catalog.xml that conforms to DCAT-AP. |
The source code of that validator is available here: https://github.com/SEMICeu/dcat-ap_validator but it does not seem to be maintained. |
DKAN 2 release will be coming up before long, and will probably be where we'll want to address this sort of enhancement. |
#868 unfortunately was closed without resolving it. |
We have reopened #868 and will work on the user story for it. |
I think we can close this in favor of #868, we just need a basic pattern for supporting additional DCAT profiles/variants. |
As a german national data-catalogue harverster (govdata.de) , I want to access a municipal dcat-ap catalogue, so that I can pull data from cities that use dkan.
All german municipal data providers are obliged to provide a data catalog following a new european/national standard called DCAT-AP.de. When comparing the example file (see this gist) with the dkan dcat-catalogue there seem to be some differences.
Could you please take a look at the specification and provide some guidance on how to adapt/expand/configure the DKAN api to provide a national endpoint following the standard? Thanks!
The text was updated successfully, but these errors were encountered: