diff --git a/drafts/3.0.0/index.html b/drafts/3.0.0/index.html index 2ce99d5..eae2125 100644 --- a/drafts/3.0.0/index.html +++ b/drafts/3.0.0/index.html @@ -147,7 +147,7 @@ prevVersionURI: "https://semiceu.github.io/GeoDCAT-AP/releases/2.0.0/", latestVersion: "https://semiceu.github.io/GeoDCAT-AP/drafts/3.0.0/", specStatus: "base", - publishDate: "2024-09-16", + publishDate: "2024-09-23", editors: myeditors, authors: myauthors, otherLinks: [ @@ -1160,9 +1160,9 @@

Meeting minutes

Status

- This application profile has the status Candidate Recommendation published at 2024-09-16. + This application profile has the status Candidate Recommendation published at 2024-09-23.

Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog. @@ -23099,7 +23099,26 @@

Motivation and use cases

Supported tooling

-

To support the transformation from INSPIRE metadata to GeoDCAT-AP compliant metadata an XSLT tool was developed. This tool has been updated to transform data to be compliant with GeoDCAT-AP 3.0.0. The GeoDCAT-AP XSLT can be found on the dev branch of the GitHub repository. The XSLT can be run directly on the output of a CSW or on single metadata records, by using any of the programming languages supporting XSLT conversion. Additionally, a proof-of-concept API has been developed to facilitate the testing of the XSLT on single metadata records or on top of a CSW endpoint.

+

+ To support the transformation from INSPIRE metadata to GeoDCAT-AP compliant metadata, a reference XSLT transformation was developed, and is being maintained. + This transformation has been updated to transform data to be compliant with GeoDCAT-AP 3.0.0. + The reference XSLT can be found in a GitHub repository. + The XSLT can be run directly on the output of a CSW or on single metadata records, by using any of the programming languages supporting XSLT conversion. +

+ +
+

+ The reference XSLT is not meant to be used in production directly. + It serves as a reference which needs to be adjusted according to the specific needs and practice of the individual metadata publishers, as the practice is currently not coherent across publishers in certain aspects. + These aspects include: +

+ +