MIWP 2014-16: Deliverables for approval Michael Lutz 5th MIG meeting, Brussels 30 November – 1 December 2016

Status legacy MIWP actions Nov 2016 5 Validation Draft ATS for NS, SDS and MD; 1st release Testing framework and ETS 6/2017 6 Registers Completed 7a SOS 7b WCS 8 Metadata 10 Data specs 14 Thematic Clusters platform operational, TG change proposals and IR issues endorsed by MIG-P on-going 16 Monitoring 18a xsds sds SDS ext Extensions Study & inventory completed

Endorsement procedure As far as possible, the MIG shall adopt these documents by consensus at the 5th Meeting of the MIG. In case issues are identified that impede adoption and need further clarification or investigation, the group’s opinion will be requested via a written procedure. The documents under the MIWP 2014-2016 legacy actions ([DOC15]-[DOC19]) have been developed in collaboration between Member States, EFTA Countries, Commission and EEA in subgroups of the permanent technical subgroup of the MIG. These documents have been approved by the Member States delegates in the permanent technical subgroup and are now presented for adoption by the MIG. Upon approval of these MIWP 2014-2016 deliverables, the MIG also decides to close the associated actions.

Endorsement procedure COM will present the documents After discussion the documents will be put forward for adoption in batch. In case of objection to the batch adoption, the MIG can adopt a subset of the documents and mandate the permanent technical subgroup to address the remaining issues in the non-adopted documents. Adoption for the non-adopted documents in the 5th meeting of the MIG will be requested via written procedure.

Registries and registers – Why? MS need to build registries and use the central INSPIRE registers Guidelines needed for extending central INSPIRE registers  register federation Priorities for the further development (functionality and content) of the central INSPIRE registry to be discussed between EC and MS Procedures and decision-making rules needed for a control body for the central INSPIRE registers

Registries and registers – Deliverables Guidance / best practices document Best practices for setting up registers / registries for register managers & users INSPIRE Register Federation – Overview How to join the INSPIRE register federation for register managers How to use the INSPIRE register federation for register users Annexes (examples of descriptors, validation stylesheet) Terms of reference for control body and submitting organisations for central INSPIRE registry and register federation formalise maintenance process (based on ISO 19135) as light-weight as possible

Registries and registers – Deliverables Tested and supported by implementation Register of Registers (RoR) prototype Support of Register federation exchange format in central INSPIRE registry service and Re3gistry software (developed under ARE3NA ISA action) http://inspire-regadmin.jrc.ec.europa.eu/ror

Registries and registers – Process MIG sub-group Dec 2014 – Nov 2016 DE, AT, SE, UK, SK, ES, EE, FR, FI, EEA, OP, JRC 16 virtual meetings (plus one informal face-to- face) Strongly supported by JRC registry team and ARE3NA ISA action (development) MIG-T review of TG & BP document Oct 2016 Unanimously endorsed by 18 countries (MT, BG, CH, SE, ES, CZ, IT, AT, EE, HU, DK, PL, LV, NL, FR, DE, RO, UK) Comments from SE, IT, DK, NL, FR, DE, UK Comment resolution and final draft almost completed Terms of reference drafted by JRC and updated based on MIG-T discussion

TGs & tools for observation & coverage data – Why? Many Annex II+III data sets are based on observations or coverages Available solutions in TGs for Download services (WFS and Atom) not suited for providing direct access to observation or coverage data Additional opportunities by sharing data using SOS/WCS

TGs & tools for observation & coverage data – Deliverables Technical Guidelines for Download Services based on SOS (INSPIRE SOS profile) WCS (INSPIRE WCS profiles) Update of D2.9 Guidelines for the use of O&M and SWE Focus on implementers Guidance tailored to INSPIRE Previously existing content as Annexes Simpler and shorter document Alignment with TG for download services SOS Open Source Implementation (52North) with support for additional observation types (e.g. PointObservation, ProfileObservation, TrajectoryObservation, …)

TGs & tools for observation & coverage data – Process 2 MIG sub-groups MIWP-7a Dec 2014 – summer 2016 MIWP-7b Jun 2016 – summer 2016 ~10 virtual meetings each (plus face-to-face meetings and workshops at the INSPIRE Conference) Supported by 2 TG editors and 1 OS development contract MIG-T review of 2 SOS/O&M/SWE TGs Aug-Sep 2016 Unanimously endorsed by 16 countries (BG, CZ, MT, NO, LV, DK, HU, CY, NL, FR, SE, EE, ES, PT, DE, PL) Comments from SE, DK, NL, FR MIG-T review of WCS TG Mar-Apr 2016 Unanimously endorsed by 19 countries (SE, BG, CY, MT, UK, CZ, LV, EE, DK, DE, FR, BE, HU, FI, NL, IT, PL, RO, CH) Comments from UK, CZ, DE, FR, NL, CH, JRC

Updated Metadata TG – Why? Implementation experience since 2009 Address identified issues: Metadata for SDS Integrate metadata for interoperability Language neutral identifiers Unique Resource Identifier Coupled resources Conditions applying to access and use Harmonized restrictions/licenses Integrate Theme specific metadata Relation to ISO19115-1:2014 Conformance classes in registry Metadata for monitoring Add Abstract Test suite

Updated Metadata TG – Deliverable TG for metadata v2.0 Including all requirements on metadata from different legal acts  Conformance classes for Data sets Network services Spatial data services TG re-structured following ISO 19139 Requirements language improved based on MIWP-5 feedback Transition period (1.3  2.0) of 3 years from agreed date

Updated Metadata TG – Process MIG sub-group Nov 2014 – Dec 2015 (Nov 2016) ~20 virtual and 2 face-to-face meetings Supported by TG editor MIG-T review of updated TG Apr-May 2016 Unanimously endorsed by 22 countries (DE, SE, BG, CZ, DK, UK, FR, IT, NO, FI, EE, HU, LV, CH, BE, MT, PL, NL, PT, AT, RO, ES) Comments from DE, SE, CZ, DK, UK, FR, IT, CH, NL, AT, ES Final comment resolution web-conference to resolve remaining 5 open issues on 21 November Final editorial check still to be done