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/2021
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/2021
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/2020
ICT standardisation in eGovernmentFree and open source software in Public AdministrationsEnvironment+4 topics
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/2019
Many associations defined for PublicOrganization should actually be moved to Organisation
The practical relevance of CPOV with respect to the W3C ontology of organizations is that it introduces some useful attributes and associations, such as hasContactPoint, logo, and address. However, in the present CPOV version, these associations are attached to cpov:PublicOrganization, while they…
DISCUSSIONCreated: 15/03/2017
cpov:PublicOrganization not a subclass of org:Organization in the RDF encoding
In the documentation of CPOV V1.0.0 and in the UML diagram, cpov:PublicOrganization is defined as a subclass of org:Organization. However, in the associated RDF file (cpov_rdf_schema_turtle_v0.03.ttl) cpov:PublicOrganization is just defined as a subclass of dct:Agent. Suggested fix: change the rdf…
DISCUSSIONCreated: 15/03/2017
Misleading description of org:OrganizationalUnit
We have described the class org:OrganizationalUnit as a subclass of cpov:PublicOrganization. We have done so implicitly in the text and declaratively in the diagram. In the text we write: "An Organizational Unit is a sub class of Public Organization [...]" ..which of course can be true and does not…
DISCUSSIONCreated: 16/11/2016
Why are schema.org properties recommended as RDF terms?
Dear all, I find it worrying that terms specifically selected/optimized for annotating web pages for SEO and SERP are recommended in a core vocabulary. A core vocabulary by its definition should be broadly applicable... Understandably, the schema.org specification has a broad coverage, is made very…
DISCUSSIONCreated: 07/11/2016
Range of contactPoint is not VCard
Section 4.1.13 and 4.1.14 mention that the range of contactPoint is a VCard. They also mention that the rdf binding of contactPoint is schema:contactPoint. However, schema.org defines contactPoint as having range schema:ContactPoint. The semantics of both seem different enough to say that they…
DISCUSSIONCreated: 04/11/2016
Temporal availability can vary with channel.
Moreover (continuing on issue "CPOV: Property CPOV:Temporal missing."): temporal availability can vary according through which channel the PublicOrganisation is contacted (eg from 8-19u by telephone, from 9-17u on-site). This is independent of the specific PublicServices that the PublicOrganisation…
DISCUSSIONCreated: 03/11/2016
Property CPOV:Temporal missing.
A property CPOV:PublicOrganisation:Temporal comparable to CPSVAP: PublicService:Temporal or CPSVAP: PublicService:Channel:Availability should be added. Useful where the availability of the PublicService is not specific for the service but for the PublicOrganisation that provides it. Eg a…
DISCUSSIONCreated: 03/11/2016