Align XSLT with working draft of GeoDCAT-AP 2.0.0 #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This version includes revisions needed to ensure compliance with DCAT 2 and DCAT-AP 2.0, and reflecting the first working draft of GeoDCAT-AP 2.0.0:
https://semiceu.github.io/GeoDCAT-AP/drafts/2.0.0-draft-0.1/
Such revisions are implemented in a conservative way - i.e., by adding new mappings without removing the original ones, but flagging them as deprecated, thus ensuring backward compatibility.
Another main change concerns having moved to the core profile some mappings which were originally part of the extended profile only, and concerning metadata elements supported in DCAT-AP 2.
Finally, this new version includes revisions to ensure compliance with the 2017 edition of the INSPIRE Metadata Implementation Guidelines. Also in this case, revisions have been implemented in a conservative way, to ensure backward compatibility with metadata records following previous versions of the INSPIRE Metadata Technical Guidelines.
More precisely:
dcat:DataService
.dcat:endpointURL
.dcat:endpointDescription
.dcat:accessService
.dcat:servesDataset
.dcat:bbox
.dcat:startDate
.dcat:endDate
.dcat:spatialResolutionInMeters
dcat:hadRole
.dcat:theme
.dcat:keyword
.dcat:contactPoint
.gmd:useConstraints
is now used to map use conditions. The previous versions of the mappings used instead elementgmd:useLimitation
, which has been kept for backward compatibility, but flagged as deprecated.gmx:Anchor
.gmd:MD_RestrictionCode
andgmx:Anchor
.dcat:accessService
. One major difference with respect to the previous versions of the mapping is that resource locators are considered as distributions of datasets and series whenever they point to a service / API.gml:
namespaces.