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

Transformation: namespaces and standards #5

Open
hallinpihlatie opened this issue Jan 22, 2025 · 0 comments
Open

Transformation: namespaces and standards #5

hallinpihlatie opened this issue Jan 22, 2025 · 0 comments

Comments

@hallinpihlatie
Copy link

All HVD metadata example files that I can find for example on the European Data Portal contain the dcatap namespace (xmlns:dcatap="http://data.europa.eu/r5r/") to refer to hvdCategory and applicativeLegislation.

Namespace xmlns:geodcatap="http://data.europa.eu/930/" and xmlns:dcat="http://www.w3.org/ns/dcat#" are added by the transformation when using the "extended" alternative. The http://data.europa.eu/930/ also becomes the standard.

When using the "core" alternative of the transformation for example for service metadata, then the http://data.europa.eu/r5r/ is added as a namespace and standard.

Does the # in the end of http://www.w3.org/ns/dcat# mean that the dcatap http://data.europa.eu/r5r/ also is supported/included? Or is the intention to use and finetune the "core" only for HVD-reporting purposes in the pilot?

If not, would it make sense to alter the transformation so that it always adds both xmlns:geodcatap="http://data.europa.eu/930/" and xmlns:dcatap="http://data.europa.eu/r5r/ at least as namespaces but perhaps also as a standard as references to dcatap seems might be needed when adding elements required for HVD-reporting.

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

1 participant