usually a Legally Mandated Organisation with the task to implement the Directive. They provide details about their approach and the use of a collection of tools.
Implementers are encouraged to share existing documentation describing implementations, as well as links to other documents, such as input data, output data and configuration files. This information can help other implementers and help build a common picture of INSPIRE between organisations.
usually a private company but sometimes a research group or a Legally Mandated Organisation.
They provide details about their software packages (or other tools that aid implementation) and which INSPIRE implementation tasks their software can potentially support. They may also work with INSPIRE implementers to provide examples of implementations.
the software packages (whole or partial), libraries or other specific technical items that aid INSPIRE implementation helping people to share INSPIRE data, metadata and services.
|Implementation||how things were actually done to implement INSPIRE|
|App||end-user web applications and mobile apps that showcase the power of Spatial Data Infrastructures, especially those using INSPIRE data and services|
|INSPIRE in Practice||a collaborative platform that brings together different players involved in INSPIRE in a single place, facilitating the exchange of geospatial know-how and expertise|
|Asset||These stand for artefacts required or generated by the execution of Tasks.|
represent the activities that need to be fulfilled in order to implement INSPIRE obligations.
Tasks are structured into a multi-level hierarchy, i.e. every task can be split into a number of sub-tasks. An example is “provide and operate discovery services”, which contains as one of its sub-tasks “validate metadata”.
Closely connected with Tasks are Assets.
|Actor||stand for knowledge profiles required for executing Tasks|
Individual step in an implementation is represented by an Implementation Step.
If the implementation follows the recipe in the Workflow, the Implementation Step will usually exemplify one or more Tasks of the Workflow.
The link between Tasks and Implementation Steps enables the user to inspect how others have implemented particular Tasks in their implementation.
Unlike a Task, an Implementation Step is elementary and does not decompose into “Sub-Steps”.
|LMO||Legally Mandated Organisation|
|Workflow||represents a schema describing in which sequence and under which conditions the recipe’s steps can be executed. It is a collection of ordered implementation steps.|