This document is an excerpt from the EUR-Lex website
The 3 features outlined below can be implemented independently. To benefit fully from Linked Data, however, all 3 should be used.
ELI's HTTP URIs enable users to access legislation in a persistent way. The URIs are formally described by machine-readable templates, using semantic components from a legal and an end-user point of view.
ELI metadata describes legal information in a standardised way. Publishers of legal information are free to use their own metadata schemas, but are encouraged to implement the ELI metadata schema as well.
ELI metadata elements can be serialised in accordance with the W3C Recommendation, 'RDFa in XHTML: Syntax and Processing', following the ELI ontology.
You can download the latest version of the ELI ontology from the Metadata Registry website.
As ELI progresses toward making legal metadata more reusable, it should lower the barrier for data consumers to retrieve the ELI metadata from an ELI provider. A way of achieving this is by legislation publishers describing and publishing ELI datasets. The following document explains how to best describe and disseminate in view of making legal data more reusable.
CELLAR stores and disseminates all content and metadata created or disseminated by the Publications Office. It also drives the Publications Office's major portals, including EUR-Lex and OP Portal.
CELLAR resources are semantically described by the CDM (Common Data Model), an FRBR-compliant OWL ontology, which also serves as the basis for the Publication Office's ELI implementation. It is publicly accessible and allows all interested parties to retrieve content and its RDF structured metadata for reuse. A public SPARQL endpoint is made available to query its metadata store.
RDFEdit allows users to search, display and edit the metadata of legal resources in the Publications Office's Cellar database (an RDF triplestore database).
While RDFEdit contains some coding specific to the Cellar API (to load RDF data and generate update instructions, for instance), its architecture is entirely generic and relies on OWL ontology parameters and additional annotations to display and edit templates.
Last update: 07/11/2018