1. MIG temporary sub-group on Persistent Identifier (PID) DRAFT Terms of Reference Part II Christian Ansorge European Environment Agency MIG-T meeting, 18/12/2014

2. Background MIWP-4a MIWP-4: Managing and using http URIs for INSPIRE identifiers (not endorsed by MIG-P, Sept. 2014) Persistent Identifiers RDF representation of INSPIRE Datamodels MIG-T discussed in London, 1/10/2014, the role of PID (especially INSPIRE Identifier) as obstacle for INSPIRE implementation EEA volunteered to prepare draft ToR for this sub-part of MIWP-4 After MIG-T discussion on 27/11/2014 establishment of small WG to specify issues and task of ToR Special thanks to Morten Borrebæk, Chris Schubert, Markus Seifert and Andrea Perego

3. MIG-T meeting, 18/12/2014 Draft ToR for MIWP-4a Work related to Persistent Identifiers is ongoing in: MIWP-8 (MD) MIWP-6 (R&R) MIWP-5 (V&T) … ?

4. MIG-T meeting, 18/12/2014 IssuePriorityType APackage: scope and role of PID in INSPIRE A1Use case for PIDs within the INSPIRE framework unclear High (precondition) Conceptual A2 INSPIRE related documents addressing PIDs aren’t clearly identified MediumResearch A3INSPIRE documents might contain inconsistencies HighGovernance; Conceptual BPackage: INSPIRE object identifier B1 Guidelines for the implementation of the INSPIRE Spatial Object Identifier not identified or missing HighConceptual B2INSPIRE Spatial Object Identifier management rules are missing HighGovernance; Conceptual B3 No mechanism for uniqueness of the attributes of the INSPIRE Spatial Object Identifier in place High Conceptual; Implementation; Governance CPackage: Operational systems and tools C1 Operational systems and their processes related to PID management not specified MediumImplementation; Governance

5. MIG-T meeting, 18/12/2014 MIWP-4a Tasks Copied from Article 2 of the ToR :  Develop an agreed work-plan to achieve the main objectives A. Based on an overview of the identifiers within INSPIRE, define the scope and role of selected groups of identifiers (e.g. identifiers used for the interoperability of spatial data sets and services). Specify the use case and derive functional requirements for the usage of identifiers within the INSPIRE technical framework. Identify and list documents or other resources addressing the creation, design and management of PIDs related to the legal and technical framework of INSPIRE including countries best practices. Identify inconsistencies between INSPIRE documentation and legal or technical implementation. B. Solve issues related to INSPIRE spatial object identifier as a main focus Evaluate existing best practices from the implementing countries Develop common guidelines for the creation of INSPIRE Identifier considering  Governance rules  Different technologies  Uniqueness, persistency and further functional requirements. C. Elaborate operational systems and tools to support identifiers use cases Overview of existing tools to support creation and management of identifiers Specify requirements for register, validation procedures and redirection use cases