Advanced search
LIFO - Location Interoperability Framework Observatory
What is LIFO? The Location Interoperability Framework Observatory (LIFO) monitors the implementation of location interoperability good practices in European public administrations, based on the level…
SOLUTIONCreated: 06/04/2021Updated Date: 10/03/2023
ELISE Action semantic resources
What are semantic resources? Why are they useful? How is the ELISE Action contributing? Check out our semantic resources Semantic Assets Semantic assets or semantic resources is a collection of highly…
SOLUTIONCreated: 08/03/2021Updated Date: 17/06/2022
EULF Blueprint
The European Union Location Framework (EULF) Blueprint is a guidance framework for optimising the use of location information in policy and digital public services. It is fully aligned with the…
SOLUTIONCreated: 26/10/2020Updated Date: 01/06/2022
INSPIRE Reference Validator
Back to ELISE Frameworks and Solutions landing page INSPIRE Reference Validator features When is this solution for you? What the INSPIRE Reference Validator offers you? Some reusers of the software…
SOLUTIONCreated: 20/11/2019Updated Date: 17/03/2023
LIFO | Best Practice collection page
Coming soon
DISCUSSIONCreated: 23/07/2020Updated Date: 29/07/2020
6.1.1 Prepare test data
The use and reuse of any data exchange model is greatly eased by providing adequate test data. This test data should also be made a part of the final asset uploaded to SEMIC. Thus users of your asset will be better able to understand your asset and implement it correctly. This is an auto-generated…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
6.1.2 Set quality criteria
As the owner and developer of the asset, you should define criteria against which your solution can be proofed (using the test data). This is an auto-generated Asset Development Assistant. Please refer to the library item Asset Development Assistant for further information. Category Asset…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
6.2.1 Document your Implement
For an asset to enter the clearing process on SEMIC, a comprehensive documentation is required. As described above, this will make your solution easier to maintain and extend. This is an auto-generated Asset Development Assistant. Please refer to the library item Asset Development Assistant for…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
6.2.2 Pack and upload your asset to SEMIC
Pack a zip file containing: * all artefacts relevant to your asset (e.g. XML schema, UML-models, etc.) * documentation, preferably in English * test cases and test data (if available) * the licence file This is an auto-generated Asset Development Assistant. Please refer to the library item Asset…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
6.2.3 Leave your feedback for the SEMIC community
Especially if you have reused an asset from SEMIC your feedback will be useful for any future user of this asset. So please leave your feedback detailing how you were able to use the asset, what challenges you met and what problems had to be solved. You are also welcome to suggest improvements to…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
5.1.17 Default values: Identify conflicts
Default values are often used in data sources, e.g. to signify unknown data elements. Using a date like 01/01/1970 is an example. If these default values are not adequately documented and/or different this can lead to misinterpreted data. It is therefore important to identify any default values used…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016
5.1.18 Integrity constraints: Find common semantics
This type of conflict is closely related to data base design. It occurs when data from two different sources is to be integrated but is subject to different integrity constraints. Using different values as identifier keys is one example. Such conflicts usually point to a problem with semantic…
DISCUSSIONCreated: 21/03/2016Updated Date: 21/03/2016