Methodology

We followed the steps described below to collect evidence for the revisions proposed in [[VOCAB-DCAT-3]]:

1. Identify the actual list of revisions proposed in [[VOCAB-DCAT-3]] for which implementation evidence should be collected (see for more details).
2. Review some existing vocabularies based on [[VOCAB-DCAT]] or [[VOCAB-DCAT-2]], and identify if they include already the changes proposed in [[VOCAB-DCAT-3]], and/or their alignment with [[VOCAB-DCAT-3]] is planned. The rationale for including also planned implementations is that these vocabularies are not likely to adopt the revisions proposed in [[VOCAB-DCAT-3]] until it becomes a W3C Recommendation.
3. Check existing datasets to verify if the changes proposed [[VOCAB-DCAT-3]] are implemented.
4. Develop an Implementation Report with details of the steps above.

As noted, to have a broader coverage of [[VOCAB-DCAT-3]] adoption we considered different types of evidence:

1. DCAT-based vocabularies
2. Existing datasets metadata

This report includes only a representative subset, providing nonetheless enough implementation evidence of the revisions proposed in [[VOCAB-DCAT-3]]. Our perspective only aims to review some of the existing vocabularies to find proof that each feature is implemented at least once.

Meeting the exit criteria

As described in the DXWG charter, to advance to Proposed Recommendation, evidence will be adduced in order to demonstrate that each of the changes made to the original DCAT Recommendation [[VOCAB-DCAT]] has been published and consumed independently in catalogs and related systems at least once, although a higher number is expected for the majority of terms.

Evidence of implementation was gathered from existing datasets, which already implement the proposed changes, as well as from existing application profiles of [[VOCAB-DCAT]].

DCAT-based vocabularies and datasets

The following table shows DCAT-based vocabularies providing implementation evidence of the revisions proposed in [[VOCAB-DCAT-3]].

The criteria used to select the relevant vocabularies are the following ones:

1. They are based on [[VOCAB-DCAT-3]] or they extend [[VOCAB-DCAT]] with properties and classes included in [[VOCAB-DCAT-3]].
2. Preferably, they are used across multiple data catalogs and/or domains/disciplines.

The vocabularies listed earlier in this section have been chosen for the following reasons:

• [[DCAT-AP]] is a profile of [[VOCAB-DCAT]] used across Europe since 2014 as a metadata interchange format, primarily for catalogs of government data, and, to some extent, for scientific data. As such, it has a broad geographic coverage, and it is supported in data catalogs (e.g., the European Data Portal) and catalog platforms (e.g., CKAN). This report considers [[DCAT-AP-3]] that is the latest editor's draft release.
• [[DCAT-EP]] is an extension of the DCAT Application Profile for European data portals (DCAT-AP), designed and used for documenting datasets and data services of the European Parliament.
• [[GeoDCAT-AP-2]] is domain-specific extension of [[DCAT-AP]] for geospatial and statistical data, respectively, and they share the same geographic coverage of [[VOCAB-DCAT]].

Furthermore, the [[DataEuropaPortal]] serves as a pivotal hub for accessing European open data across a spectrum of sources, including international, European Union, national, regional, local, and geodata portals. It amalgamates the former EU Open Data Portal and the European Data Portal into a cohesive platform. Datasets available through the portal are considered as proof of implementation for a DCAT 3 features.

[[DCAT-AP]] has also been used as a basis for the development of country-specific extensions (see [[DCAT-AP-EXT]]). Such extensions have not been included in this report, but they provide additional support to the implementation evidence for the revisions proposed in [[VOCAB-DCAT-3]] already included in [[DCAT-AP-3]].

Implementation Evidence

The table below shows the evidence collected for each one of the revisions proposed in [[VOCAB-DCAT-3]], including, for each revision, the existing implementations - flagged with "✔" -, as well as the planned implementations - flagged with "(✔)". The vocabularies and data catalogs/data services/datasets corresponding to columns in this table are listed in subsequent sections.

The reported planned implementations reflect the following (not mutually exclusive) scenarios:

• The vocabulary or the metadata schema of the data catalog is being aligned with [[VOCAB-DCAT-3]] (or this alignment is planned).
• The vocabulary or data catalog supports equivalent or similar properties and classes, that may be eventually replaced by those defined in [[VOCAB-DCAT-3]].