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
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: