Serving society Stimulating innovation Supporting legislation Update of Discovery MS MD Schemas and Tools – MIWP-8 Tim Duffy, James Reid, Paul Hasenohr and Angelo Quaglia

A number of issues has been raised for the Metadata TG (e.g. issues concerning the metadata element useLimitation) that have not been fixed with the last update of the Metadata TG. The guidelines for metadata for interoperability (aka metadata for evaluation and use) are currently contained in the data specifications rather than integrated in the Metadata TG. The quality of the metadata harvested by the INSPIRE geoportal from the national discovery services is often quite poor, even if they are formally meeting the requirements of the metadata IRs. It should be analysed how metadata, that are created now with large effort, can be used for more use cases, such as monitoring statistics, than just the search for geodata and the allocation of information.

Fix the remaining issues that has been raised. Update the Metadata TG accordingly. Integrate metadata for interoperability into the Metadata TG. Explain in the Metadata TG whether/how to take into account the revised versions of the ISO standards on metadata. MIWP-16: Improve usefulness and reliability of monitoring information Form a MIG sub-group based on pool of experts to define whether/how the TG need to be updated, e.g. to improve metadata quality and/or to facilitate metadata creation. There is a link to MIWP-16. Lead EEA (Paul Hasenohr) as follow-up from MIWP-16, SE (Michael Östling,

Participants AT, BE (Vincent Bombaerts, NL, ES, SE, DE (Martin Seiler), UK (James Reid), FR, EEA (Darja Lihteneger, Christian Ansorge), BG Experts from PoE Outcomes Updated metadata TG (if deemed appropriate) Timeline This action should start after input from MIWP-16 and from the INSPIRE mid- term evaluation are available (i.e. towards the end of 2014). Required Resources TG editor Possible fundingIn-kind contributions (PoE, MIG)

Date of last revision Subject INSPIRE Implementing Rules for Metadata Status V. 1.3 Publisher European Commission Joint Research Centre NOTE 1 The metadata elements defined in the Implementing Rules for Metadata are usually called discovery metadata. In addition to these requirements, Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services (OJ L 323, 08/12/2010, p. 11–102) and its sub-sequent amendments1,2 define six additional metadata elements for interoperability as well as some theme-specific requirements for the discovery metadata elements. Any reference in this document to “Implementing Rules for interoperability of spatial data sets and services” refers to the above-mentioned Regulation. NOTE 2 The metadata elements defined in the Implementing Rules for interoperability of spatial data sets and services are also sometimes referred to as evaluation and use metadata. The aim of this document is to define how the requirements of the Implementing Rules for Metadata can be implemented using EN ISO and EN ISO The following subsections describe for each element of the Implementing Rules its relation with the mentioned European standards. Furthermore, Annex B provides an overview of the additional metadata elements and requirements defined in the Implementing Rules for interoperability of spatial data sets and services as well as pointers to the INSPIRE Data Specifications, which provide guidance and recommendations for their implementation.

Changes from Version 1.2 of This document is Version 1.3. The changes introduced since Version 1.2 includes rewording to make the text clearer, inclusion of examples of good practice, recommendations on Conformity to include also conformity to INSPIRE Network Service, and an overview table of the elements of metadata for evaluation and use defined in the INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services…. (e.g. the recommendation for encoding conformity “not evaluated” has changed from omitting the element to encoding the element with a nilReason).

B.1. Metadata elements required by the INSPIRE Implementing Rules on the Interoperability of Spatial Datasets and Services The following metadata elements are defined as “metadata required for interoperability” in Article 13 of the Implementing Rules on the Interoperability of Spatial Datasets and Services. They are applicable to all Spatial Data Themes from Annexes I, II and III. Metadata element Coordinate reference system Temporal reference System Encoding Character encoding Spatial representation type Data Quality – Logical consistency – Topological consistency

Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked Drafting Team “Network Services” Title Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked Creator Network Services Drafting Team Date And Feasibility Testing Report by Angelo for the INSPIRE Spatial Data Services service metadata QOS extended ISO metadata elements i.e. successful test implementation of validation and uptake ‘into the geoportal’ of such SDS service records where servicetype=‘invoke’.

SUMMARY: - Integration in the TG of the evaluation and use discovery metadata elements (6 common MD elements included in the IR on data interoperability) - Possible integration in the TG of the evaluation and use discovery metadata (additional theme-specific 'recommended' elements included in the data specifications TG) - new SDS discovery service metadata profile (19119 etc.) extensions

Discussion: Action list? (small one paragraph remit):  Set up ‘now’ (because the results feed into near future work of MIWP-5 and MIWP-8 other aspects, and ‘legally’ we should be providing where relevant from now on),  A ‘Task and Finish Working sub-Group’ to:  decide on which new metadata elements/corrections to add to the next, ‘second’ and ‘final’ version of the INSPIRE Discovery Metadata profile of ISO metadata xml schema for Datasets and Services so that MS can implement providing such metadata for interoperable datasets and for future SDS services and so that JRC (and others) can validate and accept such metadata for the portal/MS monitoring returns.  Improve the TG and guidance to help MS provide better populated metadata records going forward.