Annex 1: Summary of issues
The tasks summarized below are a list of issues related to Persistent Identifiers within the framework of INSPIRE identified by MIG representatives.
These are the currently identified issues as of the beginning of December 2014. Additional issues identified can be proposed to the MIG-T; these issues shall be outside the scope of this ToR unless the MIG-T specifically instructs the group to take account of the issue within the original timescales.
Priority
This is a classification in priority levels of the issues.
Type
Each issue can be of different types. The list of types shall be extended during the process of issue identification, following the needs.
Implementation: Issues directly relevant for the provision of spatial data
Governance: Issue regarding management and procedure
INSPIRE Architecture: …[CS1]
Issue / Priority / TypeA / Use case for PIDs within the INSPIRE framework unclear / High (precondition) / Conceptual
B1 / INSPIRE Identifier management rules / High / Governance
B2 / Ensure uniqueness of the attributes of the INSPIRE Identifier / Medium / Conceptual; Implementation; Governance
B3 / Guidelines for the implementation of the INSPIRE Identifier not identified or missing / High / Implementation
Activities
The following issues are planned to be processed within the work of this work package.
A –Use case for PIDs within the INSPIRE framework unclear[CS2]
Description:The use case of PIDs within the framework of INSPIRE is inconsistent between the INSPIRE Generic Conceptual Model,INSPIRE specifications [CS3]and its actual implementation.This leads to unclear requirements towards the design (e.g. persistency and uniqueness) and governance of identifiers. The use case of PIDs and functional requirements have to be developed in order to derive consistent requirements for all further activities.
Action: Specify the use case and derive functional requirements for the usage of PIDs within INSPIRE.
B -This package contains several sub issues related to the INSPIRE Identifier
B1 - INSPIRE Identifier management rules
Description: Processes and procedures regarding the management of INSPIRE Identifier are needed to ensure and maintain persistency of the identifiers (e.g. in case of renaming of a Public Authority or transfer of a dataset to another Public Authority). Those rules and procedures are currently missing.
Action:Specify case based procedures and management rules for the INSPIRE identifier, taking results of Issue A into account.
B2 – Ensure uniqueness of the attributes of the INSPIRE Identifier
Description: TheCommission Regulation (EU) No 1089/2010 demands uniqueness localId and namespace of the INSPIRE Identifier. According tothe INSPIRE Generic Conceptual Model, v. 3.4, a data provider shall register it’s namespace in the INSPIRE External Object Identifier Namespaces Register[CA4][CS5], which is currently not existing. Without registration of namespaces it is impossible for data providers to ensure and prove that they provide a unique namespace.
Action:Specify requirements for INSPIRE Namespace registry, taking results of Issue A into account.
B3- Guidelines for the implementation of the INSPIRE Identifier missing or not identified yet.
Description: INSPIRE data providersoften lacking common guidelines and best practices on the creation of the INSPIRE Identifier. Some guidelines are existing on national or community level, while the INSPIRE Generic Conceptual Model, 3.4, has to be updated.
Action: Evaluate existing best practices from the implementing countries and develop common guidelines for the creation of INSPIRE Identifier.
C – Operational systems and tools for linking and managing INSPIRE Identifier
C1 – Operational systems and their processes
Description: The given concept for INSPIRE id’s (including local id, namespaces and versionId) plus the INSPIRE thematic identifier needs ‘common’ processes and operations for using efficient function for linking, curate and redirection of implemented spatial objects.
Action: Specify requirements in use casesfor a register, for validation procedures and redirection use cases. and Elaborate existing technical infrastructure in Member states.
(e.g. linking E-PRTR, information about industrial facilities and pollutants, with the same industrial object which has to be reported under SEVESO Directive and Industrial Emission reports).
C2 – Inspire thematic identifier, the right function to link?
Description: The unique INSPIRE id should be linked with related spatial objects information by the thematic identifier. Are there any prototypical solution around the INSPIRE world for technical solutions and implementation. How individual thematic identifier should be, will be a register necessary?
Action: Short analyses how can the ‘INSPIRE thematic Identifier’ used as a clutch between spatial objects. Are there any alternatives?
[CS1]Should we add the structure and components of identifiers within INSPIRE here?
[CS2]Rewording: ‘Use case for elaborating PID’s within the INSPIRE framework”
[CS3]Do we have some examples for inconsistency? I don’t know all Data spec’s in detail but why I realised that the given examples in the Data spec’s are quite poor and in many cases the ‘thematic identifier’ is not mention at all. Do you mean this?
[CA4]Please correct me if I am wrong.
[CS5]This namespace register is still mentioned few times in the GCM. That’s why the following action is needed.