The implementation of INSPIRE is perceived as complex by many stakeholders and existing software tools do not always fit to the implementer and user needs. During the implementation, there are multiple bugs discovered in existing TGs, UML models, XML schemas that are at present not addressed in a systematic way and with a low level of engagement of the community. In addition, the current approach for data-service linking in the TGs (metadata and network services) is complex and provides room for different interpretations of the requirements. All of this, combined, reduces the overall benefit and limits the uptake of the INSPIRE infrastructure.
The action will put a strong emphasis on ensuring that off the shelf software tools and libraries can be used for implementing INSPIRE requirements (as defined in Action 2019.2). An expert group under the governance of the MIG-T will be established to review and revise the existing technical guidelines, UML models and application schemas without introducing changes that not aligned with the INSPIRE IRs. In doing so, emphasis would be put on (i) minimising INSPIRE-specific extensions, and (ii) leveraging on solutions that are proven to work in practice. Where applicable, issues that would have impact on the IRs will also be captured and documented.
The action is led by the JRC, with contribution by the MIG-T, European Commission DGs and the EEA. Temporary sub-groups and networks of experts will be established, and where necessary, procurements for ad-hoc tasks will be prepared.
Task 1. Develop a procedure and prioritisation for updates of INSPIRE artefacts, e.g. Technical Guidelines, UML models, XML schemas
Task 2. Review and amendment of selected artefacts. Priority would be given to TGs that have the highest impact on the implementation
|Task 3. Agree on a simplification approach for data-service linking and update the existing metadata TG accordingly||December 2021|
Simplified, flexible and transparent approach for the update of the technical artefacts in INSPIRE that also considers the support by software tools for both implementers and users.