Seitenhistorie

10:00 - 10:10

• Repository auf Github (https://github.com/INSPIRE-MIF) wird noch eingerichtet
• Erweiterung der PDS-Liste soll Anfang 2024 starten
• Outcome Metadata: Mapping zwischen ISO und DCAT-AP
• Session auf der INSPIRE Conference "High-value datasets: Unlocking accessibility of Environmental data"

• work in progress: detailed mapping for each requirement in the HVD regulation with the exact metadata element
• reporting should be based entirely on existing metadata fields according to the once-only principle (→ Art. 3, 4, 5)
• licences: suggest to DG to create a list of expected equally seen licences → machine readable and human readable, e. g. codelist
• indication high-value datasets (to discuss): tagging hvd needed as top-level concept to filter, monitor and report (not yet clear how to do that in DCAT) OR tagging "hvd-annex" like INSPIRE themes or PDS
• compliance to hvd specification → self-declaration like INSPIRE approach for TG

BE will share the analysis when ready 

 Are you working on a detailed mapping from ISO to DCAT-AP to DCAT-AP for HVD?

BE/Flanders: mapping in both ways ISO to DCAT-AP & DCAT-AP to ISO

The ISO mapping is part of the discussion in GeoDCAT-AP. That is specific for the INSPIRE geo community. And thus if there is interest in active maintenance by the community on a common XSLT/ISO mapping, let us know. 

How do you handle the requirement from DCAT-AP for HVD: "In the context of DCAT-AP, a HVD Dataset is mapped on a Dataset, Bulk Download on a Distribution and API on a Data Service. To be conformant with the use of DCAT-AP in the context of the HVD regulation, this mapping MUST be followed."  

Indeed that statement is an important constraint on the mapping. Note that this constraint is actually present in DCAT-AP 2.x: that means also discussion on detecting an API or a (bulk) file distribution in ISO metadata. Regulation is not clear on how this should be handled in the metadata.

Is the file identifier analysed in DCAT? I think, in ISO 19139 the file identifier is unique and in DCAT the identifier depends on the catalogue where the metadata file is published and this results in the file metadata in DCAT being repeated.

When is the work on updating geoDCAT starting?

We will start the work on GeoDCAT-AP next year (see issue: GeoDCAT-AP update for DCAT-AP 3.0). The intention is to first release DCAT-AP for HVDs and DCAT-AP 3.0.0.

next steps

1. DCAT-AP 3.0 (January 2024)
2. xslt for mapping ISO to DCAT-AP (February 2024)

• next meeting of the sub-group: end of january 2024 (focus on metadata)

Proposal for the next meeting: The versions of DCAT in America, Asia... are you being taken into account? ISO 19139 and ISO 19115-3 allow the integration of metadata in all catalogues outside Europe. How is DCAT metadata exported to an America catalogue for example and vice versa?

DCAT-AP is the European Profile of DCAT. Any system that understands DCAT will be able to understand DCAT-AP profiles.