EUR-Lex Access to European Union law
This document is an excerpt from the EUR-Lex website
Document 52019XG1024(01)
Council Conclusions on the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law 2019/C 360/01
Council Conclusions on the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law 2019/C 360/01
Council Conclusions on the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law 2019/C 360/01
ST/12087/2019/REV/1
OJ C 360, 24.10.2019, p. 1–22
(BG, ES, CS, DA, DE, ET, EL, EN, FR, HR, IT, LV, LT, HU, MT, NL, PL, PT, RO, SK, SL, FI, SV)
24.10.2019 |
EN |
Official Journal of the European Union |
C 360/1 |
Council Conclusions on the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law
(2019/C 360/01)
I. INTRODUCTION
1. |
Article 67(1) of the Treaty on the Functioning of the European Union provides for the constitution of an area of freedom, security and justice with respect for fundamental rights and the different legal systems and traditions of the Member States. |
2. |
The multi-annual European e-Justice action plans 2009-2013, 2014-2018 and 2019-2023 of the Council of the European Union stress the importance of access to national case law, the need for standardisation and a decentralised technical architecture. |
3. |
The European Parliament Resolution of 9 July 2008 on the role of the national judge in the European judicial system stresses the need for cross-border access to national case law to enable the national judges to fulfil their role in the European legal order. |
II. IDENTIFICATION OF NEEDS
4. |
A European area of freedom, security and justice in which judicial cooperation can take place requires not only knowledge of European law, but in particular mutual knowledge of the legal systems of other Member States. |
5. |
The European e-Justice Portal should fulfil the objective of disseminating information about the EU and Member States’ legal systems and should serve as a useful tool for citizens, legal professionals as well as Member States’ authorities. |
6. |
Knowledge on the substance and application of European Union law cannot be solely acquired from EU legal sources, but also the case law of national courts has to be taken into account, with respect to decisions asking for a preliminary ruling, decisions following a preliminary ruling as well as those applying EU law on their own. |
7. |
With financial support or direct involvement from the European Union recent years have witnessed initiatives that support the above-mentioned goals, such as the metasearch engine of the Network of the Presidents of the Supreme Judicial Courts of the European Union, the Dec.Nat and Jurifast databases of the Association of Councils of State and Supreme Administrative Jurisdictions of the European Union, the JURE (Jurisdiction Recognition Enforcement) database of the European Commission, EUR-Lex, and the case law database of the European Union Agency for Fundamental Rights. |
8. |
The use and support of these initiatives have underlined the need for such databases but experience has shown that searching these databases is often very complex and not user-friendly. |
9. |
A study performed by a task group of the Working Group on e-Law made it clear that apart from problems with multilingualism, these problems are mostly due to the lack of uniform identifiers for case law. At the national level various identification systems exist, some of them court-designated, others vendor-specific. Databases designed to query case law from various Member States — of which the abovementioned are just a few examples — sometimes invent their own identification system, and sometimes re-use one or more of the national numbering systems. Search and citation of case law in the cross-border context is therefore extremely difficult: identifiers which are issued by one system might not be compatible with other systems. |
10. |
The abovementioned study made it clear that comparable problems exist with metadata used for describing case law. The fact that nearly all national and European databases use different naming and design rules for metadata jeopardises the possibilities for effective and user-friendly cross-border case law search for judges, legal professionals and citizens. |
III. IDENTIFICATION OF SOLUTIONS
11. |
In line with the principle of proportionality, the principle of decentralisation endorsed by the European e-Justice Action Plans and the principles of the European Interoperability Framework a single centralised European database of case law should not replace national solutions. Moreover, specific user needs that arise for specific fields of law call for different databases with different functionalities, be they of public or of commercial nature. |
12. |
In order to both […] facilitate the further development of European case law databases and […] serve legal professionals and citizens in their use of these databases, a common system for the identification, citation and metadata of case law is therefore indispensable. Such a common standard would be compatible with the principles outlined in the previous paragraph. |
13. |
For the identification of judicial decisions a standard identifier should be used which is recognisable, readable and understandable by both humans and computers, and which is compatible with technological standards. At the same time it is desirable that national identification systems can work in parallel with such a European standard, but also that a European standard can serve as the sole national standard for those countries that so wish. |
14. |
Because the organisation of courts and IT-applications used by courts vary not only between Member States, but also within a Member State, it should be possible to implement an identification and metadata system court by court. |
15. |
In line with the stated principles on proportionality and decentralisation, decisions on the courts and tribunals to participate in this case law identification and metadata system have to be taken at the national level. |
16. |
As acceptance by the courts and governments of the Member States is of utmost importance for the implementation and use of an identification and metadata system for case law, consultations on this recommendation have taken place with the Network of Presidents of the Supreme Judicial Courts of the European Union, the Association of the Councils of State and Supreme Administrative Jurisdictions of the European Union, the European Network of Councils for the Judiciary, the LEX-initiative, the CEN/Metalex workshop, Semic.EU, the European Commission, the Court of Justice of the European Union and the Publications Office of the European Union. Also the European Legislation Identifier and Akoma Ntoso have been taken into account, as to optimise interoperability with those standards. |
17. |
The identification and metadata system should be made well-known to citizens and legal professionals. Furthermore, to improve the chances of finding case law which is provided with an identifier and metadata as described in Annex I, these judicial decisions should be searchable — by identifier and a minimum set of metadata — via a common search engine. The architecture of this common search engine should be decentralised and embedded within the European e-Justice Portal. Although a common search engine reinforces the usability of an identification and metadata system, it should not be a prerequisite for the introduction of the identification and metadata at the national level. |
18. |
The common search engine should not only have the possibility to index decisions from judiciary websites but also from other websites that disseminate case law, e.g. in summarised or translated versions. |
IV. ON ECLI EXTENSIONS AND IMPROVEMENTS
19. |
Eight years after the adoption of the first version of these Council Conclusions, ECLI has been implemented in public databases with court decisions by seventeen Member States, the Court of Justice of the European Union, the European Court of Human Rights and the Boards of Appeal of the European Patent Organisation. Many of these databases have been indexed by the ECLI Search Engine, which has been developed by the European Commission in accordance with paragraph 27-f. |
20. |
ECLI is being used as the sole or as an additional way of citation in many jurisdictions. In the ‘Conclusions of the Council and the representatives of the Governments of the Member States meeting within the Council on Best Practices regarding the On-line Publication of Court Decisions’ (1) the use of ECLI and interconnection of national case law databases with the ECLI Search Engine have been identified as a best practice. |
21. |
Notwithstanding the fact that ECLI can be considered to have contributed towards increased accessibility to and the quality of legal information to the benefit of the legal community, some shortcomings of the ECLI framework have surfaced. At the same time, technological developments and new insights offer opportunities for enhancements that could benefit the legal community. Therefore, some improvements and extensions of the standard would be advantageous. |
22. |
However, given the number of ECLI implementations, technical changes in or extensions of the standard should not jeopardise the investments made in the current and ongoing implementations. In this context, jurisdictions that have implemented ECLI:
|
23. |
The improvements and extensions of the original ECLI standard can be summarised as follows:
|
24. |
The specifications for ECLI-XL are described in Part II of Annex I, while the additional metadata have been added to part III of Annex I. |
25. |
A guide for the legal community on the use of ECLI and ECLI-XL is included in Annex II. |
V. INTRODUCTION OF ECLI
26. |
Member States are invited to introduce, on a voluntary basis at the national level, the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law. |
27. |
The following recommendations would apply to the Member States who decide to introduce ECLI and a minimum set of uniform metadata for case law:
|
ANNEX I
On technical specifications, organisation and implementation
I. THE FORMAT OF THE EUROPEAN CASE LAW IDENTIFIER
1. |
A European Case Law Identifier (ECLI) must consist of the following five components, which must appear in the listed order:
|
2. |
The five components of the ECLI, as defined in the previous section, can be formatted in one of two syntaxes, which are fully equivalent and can be used interchangeably.
|
3. |
An ECLI must not contain any interspacing or punctuation marks, neither within the constituent components, nor between them — except for those mentioned under (1-e) and (2). |
4. |
Letters in all of the components must be Latin alphanumerical characters only. |
5. |
In case the elements of ECLI are separated by colons, the letters in the components described in (1a), (1b), (1c) and (1e) are preferably written in capitals; but there must be no difference in meaning as to their capitalisation. In case the elements are separated by a slash, all letters must be in lowercase. |
6. |
So as not to compromise its use or comprehensibility an ECLI must not be extended with any other components, apart from those described in section II. |
7. |
The namespace of ECLI must be registered at the address: https://e-justice.europa.eu/ecli |
II. ECLI EXTENSION LANGUAGE
8. |
The ECLI framework is constructed on the principles of the Functional Requirements for Bibliographical Records (FRBR), on which other standards in the domain of legal informatics — like CEN-Metalex, URN:LEX and Legal DocML (Akoma Ntoso) — are also based. |
9. |
The term ‘ECLI’ is reserved for the identifier at the work level and the document level only. |
10. |
To identify or to refer to the expression or manifestation level, and/or to specific parts of a court decision, the ECLI Extension Language (ECLI-XL) should be used, as described in this section. |
A. Expression Level Identifier
11. |
An expression is any temporal, linguistic and/or edited version of a court decision at the work level. Different expressions can be uniquely identified by using the syntax described in this section. |
12. |
The elements identifying a specific expression:
|
13. |
The temporal variant element:
|
14. |
The compiler element:
|
15. |
The language element:
|
16. |
The comprehensiveness element:
|
17. |
Compiler specific expression element:
|
B. Manifestation Level Identifier
18. |
A manifestation is the physical embodiment of an expression. There is only one element to express the manifestation. The manifestation element:
|
C. Fragments
19. |
It is recommended to structure and mark-up court decisions in such a way that specific parts thereof (‘fragments’) can be identified unequivocally. It is recommended to use the syntax described in this section. Alternatively, if other fragments identifiers are used, it is advisable to cater for a mapping mechanism and to publish this mapping mechanism on the ECLI website. Even if court decisions are not available with identifiable fragments, the syntax in this section can be used to create URIs to refer to specific fragments of court decisions. |
20. |
The fragment identifier can be used at the work level, at the expression level and at the manifestation level. |
21. |
If used, the fragment identifier must be placed directly after the last element identifying the full court decision identifier, which can be the ECLI, or the ECLI-XL expression or ECLI-XL manifestation element. |
22. |
The fragment is always preceded by ‘#’. |
23. |
When used as an identifier, the fragment is used to identify a single part. |
24. |
When used as a reference, the fragment can also refer to more fragments. |
25. |
The singular fragment consists of a label followed by a numbering element. |
26. |
The label element is mandatory, and must be an (English) abbreviation from the following list (the full term/explanation is added between brackets):
|
27. |
The numbering element immediately follows the label element, without interpunction or white space. |
28. |
The numbering element:
|
29. |
A singular fragment can have a hierarchical structure, with the highest fragment mentioned first. The nested elements are separated by a hyphen. There are no prescriptions on the possible hierarchy, except for that hierarchical elements with the same labels cannot be combined in one hierarchy. |
30. |
A plural fragment:
|
D. Resolution
31. |
Any application that cannot interpret ECLI-XL should see to it that those extensions are ignored. This can be accomplished by truncating everything from (and including) an opening bracket (‘(’), or — if not HTTP is used — a hash (‘#’), whichever one comes first. |
32. |
Websites that develop a mechanism to direct an ECLI-XL URI to the correct expression, manifestation or fragment, should cater for a method to handle ECLI-XL URIs that do not exist on that specific website. This could be e.g. implemented by redirecting to an overview of versions of the ECLI that are available instead, or to decide on which ‘best match’ should be presented. |
III. METADATA
A. Introduction
33. |
Section B contains the metadata scheme from the original version of these Council Conclusions. Section C contains an updated and extended overview of the metadata. Not to complicate the datamodels and functioning of national databases and their connections with the ECLI search interface, the new metadata scheme fully includes and builds on the original metadata scheme, although from a technical perspective another naming convention might have been chosen. By way of exception, adaptations to the original scheme that have been implemented in the XML schema used for the interconnection between Member States’ repositories and the ECLI search interface, have been implemented in Section C as well. |
B. Original Metadata Scheme
34. |
To further the understandability and findability of case law, each document containing a judicial decision should have a set of metadata as described in this paragraph. These metadata should be described as much as possible according to the standards set by the Dublin Core Metadata Initiative (hereafter: DCMI), and as further specified in this paragraph. |
35. |
Each document which is an instance of a judgment or a description thereof should, and in case it has to be searchable by the interface as described in part VI, must contain the following metadata:
|
36. |
Each document which is an instance of judgment may also contain the following metadata:
|
37. |
All metadata in this paragraph which do not have a fixed format or which are not based on a scheme must have a language attribute. |
C. Revised Metadata Scheme
38. |
Metadata can exist at the different levels of the FRBR domain. In this section they are specified for the levels of work, expression and manifestation. Metadata are classified to their FRBR level based on the target of the metadata statement, not based on the FRBR level on which the author of the metadata operates (‘creator’ for the work, ‘compiler’ for the expression or ‘editor’ for the manifestation). Hence, every compiler can make metadata statements about the work level and about its own expression, not about the expressions of another compiler. |
39. |
The revised and extended metadata scheme can be used independently from the use of ECLI-XL. |
40. |
The metadata are formulated in a functional specification. There is no prescribed technical framework to express the metadata, as not to impose any technical solution. In cooperation with the ECLI Expert Group, the Commission should develop a technical standard to standardise the exchange of metadata between the ECLI Search Engine and national repositories. |
41. |
The tables in the following sections, specifying the metadata for work, expression and manifestation, contain the following columns:
|
42. |
Work level metadata
|
43. |
Expression level metadata
|
44. |
Manifestation level metadata
|
IV. ON NATIONAL IMPLEMENTATION
A. The National ECLI-Coordinator
45. |
Each Member State using the ECLI must appoint a governmental or judicial organisation as the national ECLI-coordinator. One country must not have more than one ECLI-coordinator. |
46. |
The national ECLI-coordinator is responsible for:
|
47. |
The national ECLI-coordinator should publish on the ECLI-website, as defined in part V, information describing the way the ordinal number is composed and other information regarding the way in which ECLI is being implemented. |
48. |
If within a Member State, the use of XX as a court code is allowed for decisions from other jurisdictions, the national ECLI coordinator should, if and when within the other jurisdiction native ECLIs are being assigned to those decisions, take appropriate action to replace these XX-ECLIs by the native ECLIs, using the <ReplacedBy/>-element. There is no obligation for any ECLI coordinator to populate the <Replaces/>-element with ECLIs with an XX-court code that might have been assigned by other Member States. |
B. Implementation
49. |
National implementation of ECLI is a national responsibility, notwithstanding the possible availability of European funding. |
50. |
Courts and tribunals within one country may join the ECLI-system at different moments in time. |
51. |
To facilitate easy referral, ECLI should also be used within physical embodiments of the judgment itself. |
52. |
It is advised to assign ECLI to all judgments which are rendered, and not only for those which are published on judiciary websites. |
53. |
The ECLI may be assigned to historical judgments. Such an approach is encouraged. |
54. |
At the national level the assignment of the ECLI should be organised as a separate service, in accordance with the guidelines of the European Interoperability Framework. |
55. |
When included in, or printed on a court decision, it is advised not only to display the ECLI in colon based syntax, but also an HTTP URI of the manifestation. The latter could be labelled as ‘this document’, ‘this version’ or a comparable label. |
V. THE ECLI-WEBSITE
56. |
An ECLI website should be established; this website should be part of the European e-Justice Portal. |
57. |
The website should contain:
|
VI. THE ECLI SEARCH ENGINE
58. |
There should be an ECLI Search Engine for searching court decisions by ECLI, metadata and text. |
59. |
In accordance with the European e-Justice action plan the ECLI Search Engine should be decentralised in nature: a database at European level should not be aimed at replacing national solutions. |
60. |
The European Commission is responsible for the technical functioning of the ECLI Search Engine. |
61. |
The register of expression compilers must be maintained by the Commission and should be accessible via the ECLI Search Engine. |
62. |
The ECLI Search Engine should have a RESTful API. |
63. |
For end-users the ECLI Search Engine must be available via the ECLI-website, although it does not have to be an integral technical part of it. |
64. |
The European Commission must make available a well-described interface for indexation of databases with court decisions by the ECLI Search Engine. |
65. |
In case of abuse or misbehaviour the Commission reserves the right to deny an organisation the right to be connected to the ECLI Search Engine, or disconnect an organisation in case of systematic violations. |
66. |
A resolver must be available at https://e-justice.europa.eu/ecli/ meaning that an ECLI typed after this address will show the available data on this ECLI via the search interface. In addition, https://ecli.eu can also be used. |
VII. ECLI WITHIN THE EU
67. |
The ECLI coordinator for the EU jurisdictions is the Court of Justice of the European Union. |
68. |
Where appropriate in the Annex I ‘country’ or ‘Member State’ should be read ‘EU.’ |
ANNEX II
On the use of ECLI and ECLI-XL in legal texts
1. |
The name‘ECLI’should only be used to indicate a court decision at the work level. |
2. |
It is advised to use ECLI for citing court decisions, as a preferred or additional way of citing. |
3. |
When used for citation, an ECLI should always be written in full. No elements should be left out. |
4. |
When ECLIs are being cited in texts which are meant for human reading, it is strongly advised to use the colon-based syntax with the preferred casing. |
5. |
When, in legal documents, references are made to court decisions, in a majority of cases the reference is meant to be made to the work level, independent from a specific linguistic, temporal, editorial or other variant. Therefore, the ECLI should be used to make such a reference, without any indication of a specific variant. |
6. |
Exceptions to this rule can exist if — for legal or documentary reasons — explicit reference has to be made to a specific variant, e.g. when two linguistic variants are compared. |
7. |
ECLI-XL is designed to distinguish between such variants in a technical way; however, it is strongly recommended not to display ECLI-XL in texts which are meant for human reading, but only to display the full ECLI-XL reference in a footnote or as technical code in a hyperlink. |
8. |
If information systems prefer to guide the user to a specific expression or manifestation of a court decision, although such variants are not of legal relevance, the linking should be set up in such a way (e.g. by the use of stylesheets) that users are shielded from any information that might create misunderstanding about the intended level of reference. |
9. |
Contrary to the specific expression or manifestation of a court decision, references in legal texts to specific parts of a judgment are made explicitly and intentionally. Since ECLI-XL is error-prone when references to fragments would be constructed or read by humans, it is strongly advised to use ECLI-XL references to fragments only in hyperlinks and other machine readable code, or as additional information in footnotes, while the fragments should be described in text according to local habits or citation guides. |