From c0a72fd0a3bf997340af60cea0ecb87951b09e5e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Kl=C3=ADmek?= Date: Tue, 9 Jul 2024 16:14:02 +0200 Subject: [PATCH] Prepare for public review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Jakub Klímek --- 930/releases/3.0.0/index.html | 446 +++++++++++++++++++++------ drafts/3.0.0/index.html | 555 +++++++++++++++++++++++++--------- releases/3.0.0/index.html | 555 +++++++++++++++++++++++++--------- 3 files changed, 1171 insertions(+), 385 deletions(-) diff --git a/930/releases/3.0.0/index.html b/930/releases/3.0.0/index.html index 96c9083..5b727f9 100644 --- a/930/releases/3.0.0/index.html +++ b/930/releases/3.0.0/index.html @@ -22,9 +22,21 @@ { - name: "Makx Dekkers", + name: "Jitse De Cock", + company: "PwC EU Services", + + + } + , + + { + name: "Jordi Escriu", + + + company: "JRC", + } , @@ -33,18 +45,52 @@ name: "Pavlina Fragkou", - company: "SEMIC EU", + company: "DIGIT", } , { - name: "Natasa Sofou", + name: "Andrea Perego", + + company: "European Parliament", } + , + + { + name: "Joeri Robberecht", + + + company: "DG ENV", + + + } + , + + { + name: "Arthur Schiltz", + + + company: "PwC EU Services", + + + } + , + + { + name: "Bert Van Nuffelen", + + + company: "Digitaal Vlaanderen", + + + mailto: "bert.vannuffelen@vlaanderen.be" + + } @@ -70,18 +116,6 @@ mailto: "jakub@cuit.cz" } - , - - { - name: "Bert Van Nuffelen", - - - company: "Digitaal Vlaanderen", - - - mailto: "bert.vannuffelen@vlaanderen.be" - - } @@ -95,11 +129,11 @@ var myowners = [ { - value: "SEMIC", - href: "https://joinup.ec.europa.eu/collection/semic-support-centre", + value: "Pavlina Fragkou (DIGIT)", }, { - value: "Pavlina Fragkou (DG DIGIT)", + value: "SEMIC", + href: "https://joinup.ec.europa.eu/collection/semic-support-centre", }, ] @@ -107,10 +141,12 @@ var respecConfig = { - edDraftURI: "https://semiceu.github.ioGeoDCAT-AP/930/releases/3.0.0", - latestVersion: "https://semiceu.github.io/GeoDCAT-AP/releases/2.0.0/", + prevRecURI: "https://semiceu.github.io/GeoDCAT-AP/930/releases/2.0.0/", + thisVersionURI: "https://semiceu.github.io/GeoDCAT-AP/930/releases/3.0.0", + edDraftURI: "https://semiceu.github.io/GeoDCAT-AP/930/releases/3.0.0/", + latestVersion: "https://semiceu.github.io/GeoDCAT-AP/930/releases/3.0.0", specStatus: "base", - publishDate: "2024-06-26", + publishDate: "2024-07-09", editors: myeditors, authors: myauthors, otherLinks: [ @@ -302,7 +338,7 @@

Abstract

Status

- This vocabulary has the status Candidate Recommendation published at 2024-06-26. + This vocabulary has the status Candidate Recommendation published on 2024-07-09.

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

Conformance Statement

When reusing the terms, the reuse principles of the SEMIC styleguide SHOULD be followed.

-To make the properties widely reuseable the domain and ranges are usually very open. For any kind of entity, the class rdfs:Resource is used. +To make the properties widely reuseable the domain and ranges are in most cases very open. For any kind of entity, the class rdfs:Resource is used. For any kind of value, rdfs:Literal is used. In the RDF ecosystem these are the universal denominators. @@ -396,10 +432,13 @@

Vocabulary Overview

- - - +
+ + + +
UML diagram overview of the terms defined in the 930 namespace
+
@@ -415,6 +454,10 @@

This section lists the properties matching the base namespace of this vocabulary. +
+ ISO 19115:2003 [[ISO-19115]] is currently withdrawn. + However, it is pragmatically considered as a reference standard since most geospatial metadata implementations and software tools are still using it as such, instead of ISO 19115-1:2014 [[ISO-19115-1]]. +
@@ -628,7 +671,7 @@

originator

definition - + Party who created the resource [[ISO-19115]]. @@ -793,7 +836,7 @@

processor

definition - + Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]]. @@ -968,7 +1011,7 @@

resource provider

definition - + Party that supplies the resource [[ISO-19115]]. @@ -1646,15 +1689,14 @@

-
+

Controlled Vocabularies

- The shared use of Controlled Vocabularie is an important aspect in data harmonisation. + The shared use of Controlled Vocabularies is an important aspect in data harmonisation. This section contains information on the controlled vocabularies (or data instances) that are defined in the namespace http://data.europa.eu/930. And additionally it connects properties that are defined in this namespace with external Controlled Vocabularies to improve the semantical interoperability. - - -

Instances of Metric

+
+

Instances of Metric

For the class Metric the following instances are defined in the namespace http://data.europa.eu/930. @@ -1765,7 +1807,11 @@

Instances of Metric

+ +
+
+

Suggested Controlled Vocabularies

Imposing the use of a controlled vocabulary for a property in the vocabulary is restricting severely its reusability. The table below is added to increase the insight in the preferred way how to use these properties. @@ -1907,6 +1953,8 @@

Suggested Controlled Vocabularies

+
+
@@ -1918,12 +1966,12 @@

Suggested Controlled Vocabularies

Acknowledgments

The editors gratefully acknowledge the contributions made to this document by all members of the working group. -Especially we would like to express our gratetude for the former editor and author Andrea Perego. +Especially we would like to express our gratitude for the former editor and author Andrea Perego.

This work was elaborated by a Working Group under SEMIC by Interoperable Europe in collaboration with DG Environment and JRC. Interoperable Europe of the European Commission was represented by Pavlina Fragkou. -DG Environment was represented by Joeri Robbrecht and JRC by Jordi Escrui. -Jakub Klimek and Bert Van Nuffelen are the authors of this specification. +DG Environment was represented by Joeri Robbrecht and JRC by Jordi Escriu. +Jakub Klímek and Bert Van Nuffelen are the authors of this specification.

Past and current contributors are : @@ -1936,190 +1984,391 @@

Acknowledgments

- Ludger A. Rinsche + Paloma Abad + , + + Anssi Ahlberg + , + + Riccardo Albertoni + , + + Martin Alvarez + , + + Laima Amatniece + , + + Darius Amilevicius + , + + Inga Andriuskeviciute + , + + Raphaelle Arnaud + , + + Lars-Inge Arnevik + , + + Claudia Attard + , + + Teresa Barrueco + , + + Julius Belickas + , + + Laura Bolocan + , + + Peter Bruhn Andersen + , + + Dominique Buffet + , + + Petr Bures + , + + Mathieu Chaussier + , + + Radoslav Chudy + , + + Byron Cochrane + , + + Eugeniu Costetchi , - Kuldar Aasaga + Bart Cosyn , - Anssi Ahlberg + Franck Cotton , - Matej Alic + Simon Cox , - Miguel Alvarez + Rodolfo Da Silva , - Martin Alvarez-Espinar + Vendula Dastychova , - Stefano Ambrogio + Ine de Visser , - Oystein Asnes + Pascal Derycke , - Peter Burian + Loes Deventer , - Luis Daniel Ibáñez + Ilias Dimopoulos , - Jitse De Cock + Ulrika Domellof Mattsson , - Ine De Visser + Erik Edberg , - Makx Dekkers + August Edstrom , - Jean Delahousse + Jitka Faugnerova , - Ulrika Domellöf Mattsson + Benoit Fricheteau , - Adina Dragan + Aniko Gerencser , - Pavlina Fragkou + Kety Giuliacci , - Dietmar Gattwinkel + Daniel Gomez , - Stijn Goedertier + Jonas Gottschlich , - Casper Gras + Elena Grigoriou , - Bart Hanssens + Matthias Gronewald , - Bart Hanssens + Bjorn Hagstrom , - Agnieszka Jasiczek + Lena Hallin-Pihlatie + , + + Gerald Henskens + , + + Kim Hoang + , + + Jana Hojsakova + , + + Martin Hons + , + + Hanna Horppila + , + + Antoine Jacques + , + + Markus Jobst + , + + Stepan Kafka + , + + Juliana Karciauskiene + , + + Svetlogor Kirov , Fabian Kirstein , - Jakub Klímek + Ouns Kissiyar + , + + Peter Kochmann , - Nataliia Kovalchuk + Jiri Kocourek + , + + Jeff Konnen + , + + Martin Koska + , + + Lenka Kovacova + , + + Pavla Kramolisova + , + + Michal Kuban , Andreas Kuckartz , - Christine Laaboudi-Spoiden + Veronika Kusova + , + + Kim Lan Vu + , + + Frithjof Lemmel + , + + Darja Lihteneger + , + + Anja Litka + , + + Anja Loddenkemper + , + + Emilio Lopez + , + + Tamas Lorincz , - Christoph Lange + Marceau Louis , - Petros Likidis + Peter Lubrich , - Anja Loddenkemper + Kate Lyndegaard , - Giorgia Lodi + Christoph Mikula , - Peter Lubrich + Martynas Mockus , - Lina Molinas Comet + Olga Moravcova , - Anastasija Nikiforova + Stefanie Nadler , - Geraldine Nolf + Gery Nicolay , - Frederik Nordlander + Joachim Nielandt + , + + Geraldine Nolf + , + + Erik Obersteiner + , + + Rossana Paciello , Matthias Palmer , - Andrea Perego + Tamas Palya + , + + James Passmore + , + + Mihai Paunescu + , + + Barbara Phiesel + , + + Joel Plana + , + + Francois Prunayre + , + + Ines Quintanilha + , + + Mart Randmae + , + + Athina Rapsomaniki + , + + Lenka Rejentova + , + + Riikka Repo + , + + Hannes Reuter + , + + Ludger Rinsche + , + + David Robberechts + , + + Maik Roth + , + + Antonio Rotundo + , + + Thomas Ruhl + , + + Danica Saponja + , + + Giampaolo Sellitto + , + + Silvie Semeradova + , + + Age Sild + , + + Jan Skornsek , - Taavi Ploompuu + Pawel Soczewski , - Ludger Rinsche + Petr Soucek , - Daniele Rizzi + Michele Spichtig , - Maik Roth + Simon Steuer , - Fabian Santi + Corinne Straub , - Giampaolo Sellitto + Aurelija Sturaite , - Maxime Servais + Ivana Svata , - Sebastian Sklarß + Stijn Tallir , - Michele Spichtig + Naomi Thiru , - Emidio Stani + Michal Tichy , - Igor Stefelin + Mayte Toscano , - Kees Trautwein + Martin Tuchyna , - Thomas Tursics + Thomas Tursics , - Kristine Ulander + Floor Van Damme , - Joeri van der Velde + Danny Vandenbroucke , - Sander Van Dooren + Kusova Veronika , - Bert Van Nuffelen + Jose Vicente Calle , - William Verbeeck + Fabio Vinci , - Thomas Weber + Uwe Voges , - Suzanne Wigard + Klaus-Peter Wenz , - Christian Wittig + Melissa Wittens , - Agnieszka Zajac + Jim Yang , - Øystein Åsnes + Jesper Zedlitz + , + + Mantas Zimnickas @@ -2265,5 +2514,8 @@

Acknowledgments

body.darkmode img { background: none; } + body.darkmode section#references :target { + background: #04162d; + } diff --git a/drafts/3.0.0/index.html b/drafts/3.0.0/index.html index a358323..52433a8 100644 --- a/drafts/3.0.0/index.html +++ b/drafts/3.0.0/index.html @@ -28,6 +28,16 @@ company: "PwC EU Services", + } + , + + { + name: "Jordi Escriu", + + + company: "JRC", + + } , @@ -35,7 +45,7 @@ name: "Pavlina Fragkou", - company: "DG DIGIT", + company: "DIGIT", } @@ -108,12 +118,19 @@ ] var myowners = [ + { - value: "SEMIC", - href: "https://joinup.ec.europa.eu/collection/semic-support-centre", + value: "Jordi Escriu (JRC)", }, { - value: "Pavlina Fragkou (DG DIGIT)", + value: "Joeri Robberecht (DG ENV)", + }, + { + value: "Pavlina Fragkou (DIGIT)", + }, + { + value: "SEMIC", + href: "https://joinup.ec.europa.eu/collection/semic-support-centre", }, ] @@ -126,9 +143,11 @@ var respecConfig = { postProcess: [quickreference], edDraftURI: "https://semiceu.github.io/GeoDCAT-AP/drafts/3.0.0/", - latestVersion: "https://semiceu.github.io/GeoDCAT-AP/releases/2.0.0/", + thisVersionURI: "https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0", + 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-06-25", + publishDate: "2024-07-09", editors: myeditors, authors: myauthors, otherLinks: [ @@ -428,12 +447,6 @@ "publisher":"European Commission", "date":"31 January 2024" }, - "INSPIRE-MD-20240131": { - "href":"https://inspire-mif.github.io/technical-guidelines/metadata/", - "title":"Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007. Version 2.2.0", - "publisher":"European Commission", - "date":"31 January 2024" - }, "INSPIRE-MD-REG": { "href":"http://data.europa.eu/eli/reg/2008/1205", "title":"Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata", @@ -941,7 +954,27 @@ "publisher": "European Commission, Joint Research Centre (JRC)", "date": "2019", "id": "locn-mapping" - } + }, + "AGRI-POLICY" : { + "href":" https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:32013R1306", + "title":"Regulation (EU) No 1306/2013 of the European Parliament and of the Council of 17 December 2013 on the financing, management and monitoring of the common agricultural policy and repealing Council Regulations (EEC) No 352/78, (EC) No 165/94, (EC) No 2799/98, (EC) No 814/2000, (EC) No 1290/2005 and (EC) No 485/2008", + "publisher":"European Union" + }, + "AGRI-POLICY-FARMERS" : { + "href":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32013R1307", + "title":"Regulation (EU) No 1307/2013 of the European Parliament and of the Council of 17 December 2013 establishing rules for direct payments to farmers under support schemes within the framework of the common agricultural policy and repealing Council Regulation (EC) No 637/2008 and Council Regulation (EC) No 73/2009", + "publisher":"European Union" + }, + "IACS" : { + "href":"https://publications.jrc.ec.europa.eu/repository/handle/JRC121450", + "title":"Technical guidelines on IACS spatial data sharing. Part 1 - Data discovery", + "publisher":"JRC" + }, + "A2.5" : { + "href":"https://wikis.ec.europa.eu/display/InspireMIG/Action+2.5+Alignment+of+INSPIRE+and+high-value+dataset+implementation", + "title":"Action 2.5 Alignment of INSPIRE and high-value dataset implementation", + "publisher":"European Commission - INSPIRE Maintenance and Implementation Group (MIG)" + } } }; @@ -976,7 +1009,7 @@

Abstract

-GeoDCAT-AP is an extension of the DCAT application profile for data portals in Europe ([[[DCAT-AP-3]]]) for describing geospatial datasets, dataset series, and services. Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [[ISO-19115]] and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]] of the European Union. +GeoDCAT-AP is an extension of the DCAT application profile for data portals in Europe ([[[DCAT-AP-3]]]) for describing geospatial datasets, dataset series, and services. Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [[ISO-19115]], those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]] of the European Union and those defined in the Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 [[INSPIRE-MD]].
@@ -987,9 +1020,9 @@

This document contains version 3.0.0 of the specification for GeoDCAT-AP, an extension of the DCAT application profile for data portals in Europe [[DCAT-AP-3]] for describing geospatial datasets, dataset series, and services.

-

Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [[ISO-19115]] and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]].

+

Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [[ISO-19115]], its XML metadata encoding standard, ISO/TS 19139:2007 [[ISO-19139]], and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]].

-

The GeoDCAT-AP specification does not replace the INSPIRE Metadata Regulation [[?INSPIRE-MD-REG]] nor the INSPIRE Metadata technical guidelines [[INSPIRE-MD]] based on ISO 19115 and ISO 19119. Its purpose is to give owners of geospatial metadata the possibility to achieve more by providing the means of an additional implementation through harmonised RDF syntax bindings. Conversion rules to RDF syntax would allow Member States to maintain their collections of INSPIRE-relevant datasets following the INSPIRE Metadata technical guidelines based on [[ISO-19115]] and [[ISO-19119]], while at the same time publishing these collections on [[DCAT-AP-3]]-conformant data portals. A conversion to an RDF representation allows additional metadata elements to be displayed on general-purposed data portals, provided that such data portals are capable of displaying additional metadata elements. Additionally, data portals may be capable of providing machine-to-machine interfaces where additional metadata could be provided.

+

The GeoDCAT-AP specification does not replace the INSPIRE Metadata Regulation [[?INSPIRE-MD-REG]] nor the INSPIRE Metadata technical guidelines [[INSPIRE-MD]] based on ISO 19115 and ISO 19119. Its purpose is to give producers and maintainers of geospatial metadata the possibility to achieve more by providing the means of an additional implementation through harmonised RDF syntax bindings used in the Open Data community. Conversion rules to RDF syntax would allow Member States to maintain their collections of INSPIRE-relevant datasets following the INSPIRE Metadata technical guidelines based on [[ISO-19115]] and [[ISO-19119]], while at the same time publishing these collections on [[DCAT-AP-3]]-conformant data portals. A conversion to an RDF representation allows additional metadata elements to be displayed on general-purposed open data portals, provided that such data portals are capable of displaying additional metadata elements. Additionally, data portals may be capable of providing machine-to-machine interfaces where additional metadata could be provided.

@@ -1003,9 +1036,9 @@

Context

With this regard, the wide range of (open) data portals developed by European public administrations is the result of this mission. These Web-based interfaces allow access to data by providing users means to explore a catalogue of datasets. To facilitate the sharing, discovery and re-use of the data beyond the (open) data portal, common agreements for the exchange of catalogues of datasets are needed. These interoperability agreements enable to connect (open) data catalogues into a pan-european catalogue of datasets.

-

The DCAT Application Profile specifies the generic agreements for (open) data portals operated by public administrations in Europe. This specification extends DCAT-AP with additional requirements for geospatial data.

+

The DCAT Application Profile specifies the generic agreements for (open) data portals operated by public administrations in Europe. This specification extends DCAT-AP with additional requirements for describing geospatial data.

-

The current document is the result of the major semantic change release process described in the Change and Release Management Policy for DCAT-AP [[DCAT-AP-CRMP]] and was built starting from GeoDCAT-AP version 2.0.0 [[GeoDCAT-AP-20201223]], with the purpose of aligning it with DCAT-AP version 3.x.x [[DCAT-AP-3]] and with version 2.1.3 of the INSPIRE Metadata Technical Guidelines [[INSPIRE-MD-20230731]].

+

The current document is the result of the major semantic change release process described in the Change and Release Management Policy for DCAT-AP [[DCAT-AP-CRMP]] and was built starting from GeoDCAT-AP version 2.0.0 [[GeoDCAT-AP-20201223]], with the purpose of aligning it with DCAT-AP version 3.x.x [[DCAT-AP-3]] and with version 2.2.0 of the INSPIRE Metadata Technical Guidelines for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 [[INSPIRE-MD]].

This work has been carried out in the context of the European Commission’s Interoperable Europe initiative [[INTEROPERABLE-EUROPE]].

@@ -1015,12 +1048,12 @@

Context

Scope of the Application Profile

-

The objective of this work is to produce an updated release of GeoDCAT-AP based on requests for change coming from real-world implementations of the specification and an alignment with [[DCAT-AP-3]] and [[INSPIRE-MD-20230731]].

+

The objective of this work is to produce an updated release of GeoDCAT-AP based on requests for change coming from real-world implementations of the specification and an alignment with [[DCAT-AP-3]] and [[INSPIRE-MD]].

As [[[DCAT-AP-3]]], the Application Profile specified in this document is based on the specification of the Data Catalog Vocabulary (DCAT). DCAT is originally developed under the responsibility of the Government Linked Data Working Group [[GLD]] at W3C, and was significantly revised in 2020 by the W3C Dataset Exchange Working Group [[DXWG]]. DCAT is an RDF [[RDF11-CONCEPTS]] vocabulary designed to facilitate interoperability between data catalogues published on the Web.

-

The objective of this work is to produce an extension of [[DCAT-AP-3]] based on numerous requests for change coming from real-world implementations of the specification listed on the GitHub issues section since the previous release [[GeoDCAT-AP-20201223]]. For that purpose the [[DCAT-AP-3]] specification is extended with improved definitions, usage notes and usages constraints such as cardinalities for properties and the usage of controlled vocabularies. Additional classes and properties are re-used or introduced where necessary. +

The objective of this work is to produce an extension of [[DCAT-AP-3]] based on numerous requests for change coming from real-world implementations of the specification listed on the GitHub issues section since the previous release [[GeoDCAT-AP-20201223]]. For that purpose the [[DCAT-AP-3]] specification is extended with improved definitions, usage notes and usage constraints such as cardinalities for properties and the usage of controlled vocabularies. Additional classes and properties are re-used or introduced where necessary.

The work does not cover implementation issues like mechanisms for exchange of data and expected behaviour of systems implementing the Application Profile other than what is defined in the Conformance Statement in section [[[#conformance]]]. @@ -1030,9 +1063,6 @@

Scope of the Application Profile

The Application Profile is intended to facilitate data exchange and therefore the classes and properties defined in this document are only relevant for the data to be exchanged; there are no requirements for communicating systems to implement specific technical environments. The only requirement is that the systems can export and import data in RDF in conformance with this Application Profile.

-

The work does not cover implementation issues like mechanisms for exchange of data and expected behaviour of systems implementing the Application Profile other than what is defined in the Conformance Statement in . -

-

The Application Profile is intended to facilitate data exchange and therefore the classes and properties defined in this document are only relevant for the data to be exchanged; there are no requirements for communicating systems to implement specific technical environments. The only requirement is that the systems can export and import data in RDF in conformance with this Application Profile.

@@ -1060,8 +1090,8 @@

DCAT-AP Context

Interoperable Europe, within its mission to stimulate the data interoperability in Europe, manages this specification on the metadata agreements for sharing dataset descriptions between data portals. The governance is taken care by the SEMIC action within Interoperable Europe. -Initially, the scope of the specification was the exchange between Open Data Portals in Europa. -Although this is still at the core of the specification, DCAT-AP is not limited to public accessible Open Data, but can be applied to any kind of datasets. +Initially, the scope of the specification was the exchange between Open Data Portals in Europe. +Although this is still at the core of the specification, DCAT-AP is not limited to publicly accessible Open Data, but can be applied to any kind of datasets. In the past decade, DCAT-AP has grown from a single specification to a whole ecosystem of related and interconnected specifications.

@@ -1071,16 +1101,16 @@

DCAT-AP Context

Revision history

The first GeoDCAT-AP specification was released in December 2015. The subsequent release 1.0.1 improved the specification. These specifications are aligned with the core profile of ISO 19115:2003 [[ISO-19115]] and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]]. Five years later in December 2020 the second version of GeoDCAT-AP was released. W3C DCAT 2 restructured DCAT by introducing the notions of a generic Catalogued Resource of which Datasets and Data Services are special cases. As a consequence both DCAT-AP and GeoDCAT-AP required a major revision ensuring alignment between the different specifications. -In 2023, the adoption of W3C DCAT 3 [[vocab-dcat-3]] triggered a new alignment for DCAT-AP, and consquently for GeoDCAT-AP. +In 2023, the adoption of W3C DCAT 3 [[vocab-dcat-3]] triggered a new alignment for DCAT-AP, and consequently for GeoDCAT-AP. W3C DCAT 3 extends the profile with the Dataset Series notion. -This document is the combination of addressing issues raised by the community and this alignment. +This document is the combination of this alignment and addressing issues raised by the community.

Notes on alignment with DCAT 3

Being an extension of [[DCAT-AP-3]], GeoDCAT-AP inherits the changes that were introduced in [[[DCAT-AP-3]]] due to the aligment with [[[vocab-dcat-3]]]. The introduction of Dataset Series in DCAT is an additive operation from semantical, data modeling perspective. Therefore the impact on existing GeoDCAT-AP 2.x, exchanges is limited. Nevertheless, publishers may face substantial impact on the existing catalogues as the new terminology for Dataset Series may require to revisit the publisher's metadata guidelines. For instance, if the publisher had chosen to document a Dataset Series as a Dataset with multiple Distributions, then the alignment with Dataset Series as expressed in this specification will require a substantial effort. -This impact goes beyond the specification and dependent on the usage of the shared information. +This impact goes beyond the specification and is dependent on the usage of the shared information. In the context of GeoDCAT-AP and in line with the conformance expectations and [[DCAT-AP-3]], the term Dataset Series will be solely used for resources that are explicitly identified by the class Dataset Series. The situation, as mentioned, where a Dataset has multiple Distributions, will be considered as a Dataset with multiple Distributions and not as a Dataset Series. This way, receivers of GeoDCAT-AP metadata can rely on the classes to process the metadata. @@ -1111,7 +1141,7 @@

Meeting minutes

  • Webinar 20 February 2024 (Meeting Minutes, recording, slides)
  • Webinar 12 March 2024 (Meeting Minutes, recording, slides)
  • Webinar 23 April 2024 (Meeting Minutes, recording, slides)
    • -
  • Webinar 14 May 2024 (Meeting Minutes, recording, slides)
    • +
  • Webinar 14 May 2024 (Meeting Minutes, recording, slides)
    • @@ -1130,9 +1160,9 @@

    Meeting minutes

    Status

    - This application profile has the status Candidate Recommendation published at 2024-06-25. + This application profile has the status Candidate Recommendation published at 2024-07-09.

    Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog. @@ -1254,12 +1284,15 @@

    Application profile diagram

    An overview of GeoDCAT-AP is shown by the UML diagram below. The UML diagram illustrates the specification described in this document. For readability purposes, the representation has been condensed as follows:
      -
    • no ranges for data properties are shown, because some of them are expressed as unions of XSD types
      • -
    • The figure contain the key classes with some important supporting classes. Other object properties (relationships) are listed as properties on the UML class with their target range.
      • -
    • The class dcat:Resource has been included to ease to see the connection with W3C DCAT. GeoDCAT-AP treats it as an abstract notion.
      • + +
    • The figure contains the key classes with some important supporting classes. Other object properties (relationships) are listed as properties on the UML class with their target range.
      • +
    • The class dcat:Resource has been included to ease to see the connection with W3C DCAT. GeoDCAT-AP treats it as an abstract notion.
    The cardinalities and qualifications are included in the figure. +This specification distinguishes between main entities, i.e. classes in the core of the application profile, supporting entities, i.e. classes used for representation of less crucial aspects of the application profile, and datatypes used for typing literal values. + +

    @@ -1324,10 +1357,13 @@

    Application profile diagram

    - - - +
    + + + +
    UML diagram overview of the GeoDCAT-AP 3.0.0 Application profile
    +
    @@ -1397,7 +1433,7 @@

    Usage Note
    - If the Agent is an organisation, the use of the Organization Ontology [[ORG]] is recommended. + If the Agent is an organisation, the use of the Organization Ontology [[ORG]] is recommended. For the purpose of this application profile, Agent from the FOAF Vocabulary [[FOAF]] is used as a unifying class, also representing Agent from Dublin Core [[DC-TERMS]] and Agent from the W3C Provenance Ontology (PROV-O) [[PROV-O]].
    @@ -4969,8 +5005,8 @@

    0..* - - + + Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]]. @@ -5130,8 +5166,8 @@

    0..* - - + + Party that supplies the resource [[ISO-19115]]. @@ -5967,8 +6003,8 @@

    An established (technical) standard to which the Data Service conforms. - The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected. - + The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected. + For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the INSPIRE Address data model. - This application profile has the status Candidate Recommendation published at 2024-06-25. + This application profile has the status Candidate Recommendation published at 2024-07-09.

    Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog. @@ -1254,12 +1284,15 @@

    Application profile diagram

    An overview of GeoDCAT-AP is shown by the UML diagram below. The UML diagram illustrates the specification described in this document. For readability purposes, the representation has been condensed as follows:
      -
    • no ranges for data properties are shown, because some of them are expressed as unions of XSD types
      • -
    • The figure contain the key classes with some important supporting classes. Other object properties (relationships) are listed as properties on the UML class with their target range.
      • -
    • The class dcat:Resource has been included to ease to see the connection with W3C DCAT. GeoDCAT-AP treats it as an abstract notion.
      • + +
    • The figure contains the key classes with some important supporting classes. Other object properties (relationships) are listed as properties on the UML class with their target range.
      • +
    • The class dcat:Resource has been included to ease to see the connection with W3C DCAT. GeoDCAT-AP treats it as an abstract notion.
    The cardinalities and qualifications are included in the figure. +This specification distinguishes between main entities, i.e. classes in the core of the application profile, supporting entities, i.e. classes used for representation of less crucial aspects of the application profile, and datatypes used for typing literal values. + +

    @@ -1324,10 +1357,13 @@

    Application profile diagram

    - - - +
    + + + +
    UML diagram overview of the GeoDCAT-AP 3.0.0 Application profile
    +
    @@ -1397,7 +1433,7 @@

    Usage Note
    - If the Agent is an organisation, the use of the Organization Ontology [[ORG]] is recommended. + If the Agent is an organisation, the use of the Organization Ontology [[ORG]] is recommended. For the purpose of this application profile, Agent from the FOAF Vocabulary [[FOAF]] is used as a unifying class, also representing Agent from Dublin Core [[DC-TERMS]] and Agent from the W3C Provenance Ontology (PROV-O) [[PROV-O]].
    @@ -4969,8 +5005,8 @@

    0..* - - + + Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]]. @@ -5130,8 +5166,8 @@

    0..* - - + + Party that supplies the resource [[ISO-19115]]. @@ -5967,8 +6003,8 @@

    An established (technical) standard to which the Data Service conforms. - The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected. - + The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected. + For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the INSPIRE Address data model.