Ihre Favoritenliste enthält derzeit keine Seiten. Sie fügen dieser Liste Seiten hinzu, indem Sie im Menü Extras der angezeigten Seite Favorit selektieren.
SK: Despite the next INSPIRE monitoring will remain "business as usual" some basic guidance from EC level towards the MS would help a lot. E.g. how to label HVD themes in Metadata, how properly define and encode relevant CC licences to ensure synergy with HVD reporting and tangible visibility of INSPIRE in HVD reporting outcomes
HVD reporting for INSPIRE - scenarios (poll via chat)
data.europa.eu harvests all national, regional portals (geo and non-geo) (mapping based on GeoDCAT-AP for geoportals)
data.europa.eu harvests national open data portal (incl. data from geoportal) - most preferred
data.europa.eu harvests EU INSPIRE Geoportal
Don't know
formal call in the open data committee soon
11:20 – 11:50
State of play (metadata - GeoDCAT-AP, accessibility, licensing …)
How would we use GeoDCAT-AP? (poll via chat)
Strategy 1: GeoDCAT-AP is derived from INSPIRE metadata - short-term
Strategy 2: Use GeoDCAT-AP natively for INSPIRE metadata - needs more time → long-term
Don't know
11:45 – 11:55
Other issues & Next steps
Requirements: Accessibility (ATOM feeds accepted as API?)
From Poland prespective ATOM service isn't usefull for user and isn't popular among data users.
NL don't see INSPIRE ATOM as API, but as bulk download.
We had the same discussion in the Czech Republic for the data/Atom of the Czech Office for Surveying, Mapping and Cadastre with czech open data community and we agreed that Atom with Open search description is API...so we have the same "issue" as Germany
IT considers ATOM Feed as Bulk download
Same for LU
Identification - How should HVD datasets be identified?
INSPIRE PDS approach (given that all PDS are considered HVD)
HVD approach: use HVD categories, encode PDS info as second level information
Both
Don't know
We were planning only to use HVD categories (FI)
IT: Solution 2 is preferable because in our national INSPIRE catalog there may be datasets especially for the Geospatial category which are not of national interest as required by Reg. 138/2023.
FI: There is a risk that it is indicated in different ways if a code list isn't used. Therefore I'm in favor of using the HVD category thesaurus available in all European languages.
Licensing
11:55 – 12:00
Conclusions and closing of the meeting
Next steps
4th GeoDCAT SEMIC webinar on , 10-12 : relationship with INSPIRE
Written feedback following todays meeting by 10 May. For possible discussion in the 4th SEMIC webinar and MIG-T.
MIG-T meeting 17 May, proposals for common approaches
MIG meeting in June with participation of SEMIC, CNECT to present state of play and confirm proposals for common approaches
SEMIC recommendation of DCAT-AP for HVD will be presented to the PSI Expert Group on → first stable version at the end of the year, improvements afterwards (as part of new version 3.0 of DCAT-AP)
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
10:45 – 10:55
Discussion & next steps (All)
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
DCAT-AP 3.0 (January 2024)
xslt for mapping ISO to DCAT-AP (February 2024)
10:55 – 11:00
Conclusions and closing of the meeting (ENV)
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.
Kick-Off Meeting
Following the discussion in the 17th meeting of the MIG on the new action mandate 2.5 to align INSPIRE and High Value Dataset rules, and the written procedure on the proposed mandate, the action mandate was approved by consensus. Actions 2.1 and 2.2 are abandoned and replaced by Action 2.5. This meeting kicks off the subgroup for Action 2.5. All MIG and MIG-T members are invited to join for this first meeting.
Vision der europ. Kommission: "Streamlining" und Integration der europäischen Portale (INSPIRE, Open Data, ...) sowie der Codelisten auf VocBench (DCAT-AP) and INSPIRE registry
Lizenzen
bei der Fortschreibung der INSPIRE-Richtlinie könnte die Verpflichtung zur Verwendung von offenen Lizenzen aufgegriffen werden (GreenData4All)
Zugänglichkeit
die Europäische Kommission ist nachwievor der Auffassung, dass Atom Feeds den Anforderungen an APIs gemäß HVD-DVO nicht genügen
Monitoring & Reporting
die HVD-DVO sieht einen 2-jährigen Reporting-Zyklus vor
die Europäische Kommission hat einen Vorschlag für ein Amendment der INSPIRE-Richtlinie vorgelegt, um den Reporting-Zyklus von INSPIRE an die HVD-DVO anzupassen (INSPIRE Monitoring & Reporting nur noch alle zwei Jahre)
erstes (gemeinsames) Reporting 2025
10:30
Organisation of work - Proposal for dedicated workgroups under the 2.5 Action subgroup
keine Bildung von Unter-Arbeitsgruppen, sondern verschiedene Meetings → Kreis der Teilnehmenden richtet sich an jeweiligem Fokus des Meetings aus
10:50
Any other business
IT: At the national level we are preparing operational guidelines on HVDs in Italy with a focus on INSPIRE themes, we have prepared comparison tables between the environmental directives and the INSPIRE priority datasets.
Litauen: At national level we consider that HVD to be only "picked up" from the public datasets as defined under the INSPIRE themes. In case new dataset to assigned to HVD, this dataset first to be amended to the list of INSPIRE datasets. Do you support this approach?
BE: we are all doing the same exercises... We are trying to map as much as possible out of the metadata elements (ISO/INSPIRE + DCAT). So that we can feed this (like INSPIRE) the much possible through metadata itself. => anybody who is doing that same excercise as well?
11:05
Conclusions and next steps
DG ENV richtet für die Action 2.5 ein neues Repository auf GitHub ein
die Präsentation wird in dem neuen Repository geteilt
der "Call for experts" wird Anfang nächster Woche gestartet (für die Dauer von zwei Wochen)
11:15
End of meeting
die Änderung der Interoperabilitätsverordnung wird in Kürze veröffentlicht
SK: Despite the next INSPIRE monitoring will remain "business as usual" some basic guidance from EC level towards the MS would help a lot. E.g. how to label HVD themes in Metadata, how properly define and encode relevant CC licences to ensure synergy with HVD reporting and tangible visibility of INSPIRE in HVD reporting outcomes
formal call in the open data committee soon
