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
As explained in the section B.6.8.1 in the draft of GeoDCAT-AP v. 2.0.0, for conformance with DCAT-AP, GeoDCAT-AP records MUST also include keywords from the EU Vocabularies Data Theme Named Authority List.
@andrea-perego I performed some tests and the implementation seems work.
The transformation could be also extended to cover the INSPIRE themes encoded with gco:CharacterString element at least in English language, leaving to the reusers to further include additional extensions to take into account the themes expressed in other MS languages.
The question is whether this feature should be part of the reference GeoDCAT-AP XSLT, or it is rather more in scope with customised versions of the XSLT used in production environments (as the EDP one).
For instance, applying this extension will significantly increase the complexity of the XSLT with a possible impact on its efficiency. By contrast, the URI-based mapping has not these issue, and it is designed for metadata records following the INSPIRE recommendations of using URIs for the themes.
As explained in the section B.6.8.1 in the draft of GeoDCAT-AP v. 2.0.0, for conformance with DCAT-AP, GeoDCAT-AP records MUST also include keywords from the EU Vocabularies Data Theme Named Authority List.
An improvement of the XSLT could be adding the transformation from INSPIRE themes, included in the INSPIRE XML record, to DCAT-AP themes, based on the alignments between the related controlled vocabularies.
The text was updated successfully, but these errors were encountered: