Advanced search
ELI ontology translations
Provides the translations of the official ELI ontology. The translations are contributed by volunteer Member States are not part of the official ELI release. The translations will follow the updated…
SOLUTIONCreated: 09/04/2019Updated Date: 24/08/2021
ELI annotation tool
The ELI annotation tool is a tool for building notices describing legal resources using the European Legislation Identifier (http://www.eurlex.europa.eu/eli/) (ELI) standard. The notices describe…
SOLUTIONCreated: 08/02/2019Updated Date: 24/08/2021
ELI legislation extension for schema.org
This project aims at proposing an extension to the schema.org vocabulary to describe legislation documents, along with use-cases and markup examples. Schema.org is a vocabulary endorsed by major web…
SOLUTIONCreated: 08/02/2019Updated Date: 24/08/2021
ELI ontology
The European Legislation Identifier (ELI) is a framework to make legislation metadata available online in a standardised format, so that it can be accessed, exchanged and reused across borders. For…
SOLUTIONCreated: 07/02/2019Updated Date: 10/01/2022
ELI ontology for draft legislation (ELI-DL)
If you have any comments or feedbacks on the beta version of ELI-DL, please share them in this discussion topic. The ELI (European Legislation Identifier) ontology for draft legislation (abbreviated…
SOLUTIONCreated: 07/02/2019Updated Date: 10/01/2022
Chatbots & Dialogue Systems
Find the official event page here: https://joinup.ec.europa.eu/collection/innovative-public-services/event/chatbots-dialogue-systems This workshop explains how public organisations can facilitate…
EVENTCreated: 02/06/2020Updated Date: 02/06/2020
Feedback on the ELI extension for draft legislation
(CLOSED : for feedback, open a new discussion instead at https://joinup.ec.europa.eu/solution/eli-ontology-draft-legislation-eli-dl) The ELI extension for draft legislation has been publicly released. It is in "draft"/"alpha" version and has been made public to receive feedback. So please post your…
DISCUSSIONCreated: 07/02/2019Updated Date: 21/07/2020
Comments to the final draft of CPSV-AP v2.1
Description This issue was shared by Nicola Guarino via the mailing list: 1. Definition of public service and service identifier I raised this issue in the past, but it was never discussed in the WG, until the WG Governance Committee "decided to close this issue as there is no general need in the WG…
DISCUSSIONCreated: 31/10/2017Updated Date: 31/10/2017
Public service categories
Description This issue was raised by Alexandros Gerontas during the final CPSV-AP v2.0 revision webinar. He asked to include categories to classify public services, in addition to the events classification. Proposed solution As it implies bigger changes, we would propose to keep the model as it is…
DISCUSSIONCreated: 05/10/2017Updated Date: 05/10/2017
Service user and provider properties
Description This issue was raised by Nicola Guarino during the final CPSV-AP v2.0 revision webinar. He asked to include the service user to the specifications, and change the cardinality of the service provider property from 0..n to 1..n. In addition, he added that there are constraints concerning…
DISCUSSIONCreated: 05/10/2017Updated Date: 05/10/2017
Addition of properties to Contact Point class
Description This issue was raised by Alexandros Gerontas through the mailing list: I think the following properties might be added to the Contact Point class: Name, address, fax Proposed solution The properties name and fax already exist in the schema.org description of Contact Point - schema…
DISCUSSIONCreated: 18/09/2017Updated Date: 18/09/2017
Cardinality of the Has Contact Point property
Description This comment was made by Alexandros Gerontas through the mailing list: I think the cardinality of the property Has Contact Point should be 0..n. For example, a public service (PS) described once in a regional PS catalogue could have a different contact point at every regional unit…
DISCUSSIONCreated: 18/09/2017Updated Date: 18/09/2017