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
We fully support having a Good practise for HVD tagging as having a common approach is the best possible solution. Any kind of joint solution is better than having no common solution. We'd any way like to raise two things for discussion:
Present HVD tagging Good Practice proposal suggests to use a standalone descriptive keyword to indicate the ELI-legislation URL and related High value dataset keyword. I wonder could the the ELI-codes of High Value Dataset/ODD legislation and the INSPIRE Directive be added to the list of this metadata code list https://inspire.ec.europa.eu/metadata-codelist/PriorityDataset or to another code list in order to refer to it as a thesaurus in GeoNetwork? In this way all relevant legislations could be added to the applicableLegislation element, not only INSPIRE and HDV, but also others for example https://inspire.ec.europa.eu/metadata-codelist/PriorityDataset/dir-1999-31.
Could the XSL transformation be altered so that it automatically puts the key words in the right spots of the RDF-file for HVD-reporting. We propose that XLS would allow to have the Eli-code added EITHER as a separate descriptive keyword OR from a thesaurus, that is that they would both result in the following encoding recommended by the DCAT-AP-HVD 3.0.0 specification
dcatap:applicableLegislation http://data.europa.eu/eli/reg_impl/2023/138/oj, http://data.europa.eu/eli/dir/2007/2/2019-06-26;
dcatap:hvdCategory http://data.europa.eu/bna/c_b7f6a4f3;
We fully support having a Good practise for HVD tagging as having a common approach is the best possible solution. Any kind of joint solution is better than having no common solution. We'd any way like to raise two things for discussion:
Present HVD tagging Good Practice proposal suggests to use a standalone descriptive keyword to indicate the ELI-legislation URL and related High value dataset keyword. I wonder could the the ELI-codes of High Value Dataset/ODD legislation and the INSPIRE Directive be added to the list of this metadata code list https://inspire.ec.europa.eu/metadata-codelist/PriorityDataset or to another code list in order to refer to it as a thesaurus in GeoNetwork? In this way all relevant legislations could be added to the applicableLegislation element, not only INSPIRE and HDV, but also others for example https://inspire.ec.europa.eu/metadata-codelist/PriorityDataset/dir-1999-31.
Could the XSL transformation be altered so that it automatically puts the key words in the right spots of the RDF-file for HVD-reporting. We propose that XLS would allow to have the Eli-code added EITHER as a separate descriptive keyword OR from a thesaurus, that is that they would both result in the following encoding recommended by the DCAT-AP-HVD 3.0.0 specification
dcatap:applicableLegislation http://data.europa.eu/eli/reg_impl/2023/138/oj,
http://data.europa.eu/eli/dir/2007/2/2019-06-26;
dcatap:hvdCategory http://data.europa.eu/bna/c_b7f6a4f3;
Presently, the transformation encode these key words like this
<dcat:theme rdf:resource="https://eur-lex.europa.eu/eli/reg_impl/2023/138/oj"/>
<dcat:theme rdf:resource="https://eur-lex.europa.eu/eli/dir/2007/2/2019-06-26"/>
<dcat:theme rdf:resource="http://data.europa.eu/bna/c_ac64a52d"/>
FYI, this GitHub issue:
Little information rethrieved by XSLT from keywords in Anchor form · Issue #134 · SEMICeu/GeoDCAT-AP (the issue was closed waiting for a common way in INSPIRE XML to tag HVDs)
The text was updated successfully, but these errors were encountered: