European Case Law Identifier¶
Assign a jurisdiction-spanning, human-readable identifier to a judicial decision by composing scheme, country or organization, court, decision year, and locally governed ordinal components, then pair it with interoperable metadata for distributed discovery.
Core Idea¶
The European Case Law Identifier (ECLI) is a standardized identifier and metadata framework for judicial decisions published by participating European jurisdictions and institutions. It gives a decision a recognizable cross-system name with five mandatory colon-separated components:
ECLI:<country-or-organization>:<court>:<decision-year>:<ordinal>
The European e-Justice Portal states the purpose as correct and unequivocal citation of judgments from European and national courts, coupled with uniform metadata that improves case-law search.[1] The first four components create a shared namespace: the literal ECLI, a jurisdiction or organization code, a court code, and the four-digit year of decision. A national or institutional coordinator governs the final ordinal within the declared local rules. The format thus combines European interoperability with local issuance authority.
ECLI identifies the judicial decision, while documents that embody or publish the decision may exist at multiple locations and in different versions or languages. Metadata links those manifestations to the decision identity and supports distributed retrieval. The ECLI search interface does not require all case law to be copied into one central database; participating publishers expose indexed records while retaining their own repositories.[2]
Its invariant is federated decision identity under delegated namespace governance: every identifier parses into a common jurisdiction–court–year scaffold, while the participating authority guarantees local uniqueness and supplies compatible metadata.
Structural Signature¶
The structure has nine roles:
- A judicial decision as the identified legal object.
- A scheme marker, the literal
ECLI, that makes the identifier recognizable. - A country or organization namespace distinguishing participating legal orders or European bodies.
- A court code identifying the issuing tribunal within that namespace.
- A decision year preserving a stable temporal partition.
- A locally constructed ordinal that completes uniqueness under published national or institutional rules.
- A coordinator that governs court codes, ordinal construction, and implementation information.[1]
- Uniform metadata describing the decision and the published document according to common terms, including Dublin Core-derived fields.[3]
- Discovery infrastructure—publisher indexes, a search engine, and resolver behavior—that uses the identifier without becoming its identity authority.
The assignment flow is:
qualifying court decision → coordinator-approved jurisdiction and court codes → decision year → locally unique ordinal → syntactic validation → attachment to document metadata → publication in one or more repositories → cross-repository discovery or resolution.
The syntax is visible and partially meaningful, but human readability is not the source of uniqueness. The namespace rules and issuing authorities are.
What It Is Not¶
It is not a case number. A docket or file number organizes proceedings within one court and can recur across courts or years. ECLI identifies the judicial decision across publishing and citation systems; a national file reference may be incorporated into the ordinal but does not become equivalent to the whole ECLI.
It is not a URL. A URL locates a particular web resource and may change. An ECLI names the decision and can be used by a resolver or search service to find available records.
It is not the text of a judgment. The identified decision can have multiple language versions, redactions, summaries, or publisher manifestations. The metadata distinguishes the decision identity from the document instance.
It is not CELEX. CELEX numbers identify documents in EUR-Lex, including legislation and EU case-law publications, under a separate scheme. EUR-Lex explicitly distinguishes an ECLI's fifth component from the CELEX number.[4]
It is not the European Legislation Identifier (ELI), which addresses legislation through a URI and metadata pattern. Similar interoperability goals do not erase the case-law versus legislation object boundary.
It is not a universal citation style. ECLI supplies a stable identifier that citations can include, but it does not replace jurisdiction-specific rules for case names, reporters, pinpoints, dates, or procedural descriptions.
It is not a centralized European case-law database. The portal searches indexed records exposed by participating publishers; participation and retrospective coverage are jurisdiction-dependent.[1][2]
Scope of Application¶
ECLI applies to judicial decisions for which a participating Member State, EU institution, or eligible organization has implemented the scheme. Each participant decides the breadth and timing of adoption: all courts or selected courts, prospective assignment or retrospective coverage, and the local design of the ordinal within the shared constraints.[1]
The system supports citation, legal research, cross-border judicial work, publisher interoperability, database linking, legal knowledge graphs, and public access to case law. It is particularly useful where the same judgment appears in a court database, a national legal portal, a European index, a translated or summarized collection, and private legal-information services.
Council Conclusions published in 2011 established the identifier and minimum uniform metadata framework.[3] The Council adopted updated conclusions including ECLI 2.0 in 2019 to improve the scheme and cross-border access.[5] Version-specific technical details should be read from the applicable conclusions; the stable abstraction here is the common composite identity plus delegated coordination and interoperable metadata.
Clarity¶
A string counts as an ECLI only if all five required components are present in the declared order, separated by colons, and issued under the participant's rules. A look-alike string invented by a database user is not an ECLI merely because it matches the grammar; assignment authority and local uniqueness matter.
Parsing supports immediate diagnostics. In ECLI:EU:C:1998:27, EU denotes the European Union, C the Court of Justice, 1998 the decision year, and 27 the locally assigned unique component.[4] If a purported identifier changes court or year while referring to the same decision, either the string is wrong or a replacement/migration issue must be documented.
Metadata and identifier should be evaluated separately. A syntactically valid ECLI can be attached to incomplete metadata, impairing discovery without destroying the identifier's identity claim. Conversely, rich case metadata without an ECLI may support local search but fail to provide the shared reference handle.
Manages Complexity¶
European case law is distributed across jurisdictions, court hierarchies, languages, publishers, document formats, and citation traditions. A query based only on party names, national docket syntax, or reporter citation can miss the same decision as represented elsewhere. ECLI compresses the minimum routing coordinates into one stable surface that both people and machines can recognize.
The design avoids forcing every jurisdiction into one local identifier policy. The common prefix, jurisdiction, court, and year components establish cross-system structure; the delegated ordinal lets participants reuse legacy identifiers or local sequences. Coordination information makes the delegation auditable.
Uniform metadata reduces another layer of heterogeneity. A search service can interpret creator court, decision date, language, subject, identifier, and document relationships across repositories instead of learning every publisher's proprietary fields. The identifier anchors deduplication: records with the same ECLI presumptively concern the same decision even if their URLs, language, or editorial packaging differ.
Abstract Reasoning¶
ECLI realizes a hierarchical namespace. Uniqueness is compositional: the scheme marker separates ECLI from other identifier families; country or organization separates participating authorities; court separates issuing bodies; year partitions the court's output; and the ordinal distinguishes decisions within that partition. Global coordination is obtained without a single central allocator issuing every final number.
This licenses fault localization. A collision between two decisions with the same full ECLI lies in the issuing participant's court or ordinal governance, not in the search engine. A missing search result can arise from absent or invalid metadata, publisher indexing, or implementation coverage even when the ECLI itself is valid. A dead URL is a location failure, not necessarily an identifier failure.
The decision-versus-document distinction also supports one-to-many reasoning. One ECLI can anchor several document instances; each instance can carry its own publisher, language, access rights, summary, or issue date while remaining isVersionOf the same decision identity under the metadata model.[3]
Knowledge Transfer¶
The exact framework transfers across participating European courts because each maps the same roles: decision, jurisdiction, court, year, ordinal, coordinator, metadata, and publisher. A German Federal Constitutional Court ECLI may encode a detailed national reference in the ordinal, while an EU court may use an annual sequence; both remain interoperable through the fixed outer grammar.[6][4]
The architectural lesson transfers to other federated identifiers: reserve shared components centrally, delegate a collision-free local component, publish authority rules, distinguish identity from location, and attach compatible metadata. That generic structure belongs to Identifier Assignment and Authority Record. Calling another federated identifier “ECLI” is incorrect unless it participates in the European case-law scheme.
Examples¶
EU Court of Justice. ECLI:EU:C:1998:27 parses into scheme ECLI, organization EU, court C, decision year 1998, and ordinal 27.[4]
National court with local ordinal policy. ECLI:NL:HR:2016:764 identifies a Netherlands Supreme Court decision. The European e-Justice resolver can surface available metadata by appending the ECLI to its resolver path.[1]
Multiple manifestations. A national court publishes the authentic-language judgment; a second service publishes a translated summary. Both records cite the same ECLI, while their document-level language, publisher, and type metadata differ.
Coverage failure. A valid ECLI produces no portal result because the publisher has not exposed the record to the index. The correct diagnosis is discovery-layer incompleteness, not reassignment of a new identifier.
Collision failure. A coordinator-approved ordinal rule fails to distinguish two decisions by the same court in the same year. Repair occurs within the local ordinal namespace and must preserve replacement history, rather than adding ad hoc punctuation outside the standard.
Structural Tensions¶
Uniform grammar versus national autonomy. More prescribed structure improves interoperability; more local freedom eases adoption and legacy integration. ECLI fixes four routing components while delegating the ordinal.
Human meaning versus opaque persistence. Readable components help citation and debugging, but embedding court and year can complicate institutional reorganization or correction. Governance must prevent semantic readability from becoming identifier instability.
Identity versus location. A persistent decision name should survive changing URLs, yet users often expect an identifier to resolve directly. Resolver infrastructure bridges the expectations without turning the URL into the identity.
Voluntary adoption versus network value. Jurisdictions retain implementation control, but every coverage gap reduces cross-border search completeness.
Decision identity versus document variation. Collapsing all manifestations improves deduplication; preserving language, redaction, publisher, and version distinctions is necessary for evidential and research use.
Structural–Framed Character¶
ECLI is strongly structured but institutionally framed. Its grammar, namespace partition, delegation, uniqueness, and metadata relations are formally recognizable. Yet judicial decisions, courts, Member States, Council Conclusions, coordinators, and European legal-information infrastructure are constitutive rather than replaceable examples.
It is therefore a clear domain-specific abstraction. Its identifier architecture travels, but that portable architecture is already represented by primes; the name ECLI remains bound to European case law.
Structural Core vs. Domain Accent¶
The structural core is a composite federated identifier with globally fixed routing fields, locally governed uniqueness, separation of identity from location, and interoperable metadata.
The domain accent supplies European jurisdiction codes, courts, decision years, judicial ordinals, Council governance, Dublin Core case-law profiles, and the e-Justice discovery layer. Removing these leaves Identifier Assignment; retaining them yields ECLI.
Instantiates / Related Primes¶
ECLI strictly instantiates Identifier Assignment by assigning one governed, parseable handle to a judicial decision within a federated namespace.
It relates to Canonical Label, because the ECLI becomes a preferred stable surface among local references; Authority Record, because coordinators maintain court codes and rules; Record Reconciliation, because common identifiers merge manifestations; and Federated Search, because distributed repositories remain locally held while metadata is searched across them.
The minimal prospective DAG parent is prime:identifier_assignment.
Relationships to Other Abstractions¶
Current abstraction European Case Law Identifier Domain-specific
Parents (1) — more general patterns this builds on
-
European Case Law Identifier is a kind of Identifier Assignment Prime
ECLI strictly instantiates Identifier Assignment by assigning one governed, parseable handle to a judicial decision within a federated namespace.It relates to Canonical Label, because the ECLI becomes a preferred stable surface among local references; Authority Record, because coordinators maintain court codes and rules; Record Reconciliation, because common identifiers merge manifestations; and Federated Search, because distributed repositories remain locally held while metadata is searched across them. The minimal prospective DAG parent is
prime:identifier_assignment.
Hierarchy paths (4) — routes to 4 parentless roots
- European Case Law Identifier → Identifier Assignment → Appellation
- European Case Law Identifier → Identifier Assignment → Indirection → Abstraction
- European Case Law Identifier → Identifier Assignment → Indirection → Function (Mapping)
- European Case Law Identifier → Identifier Assignment → Indirection → Layering
Neighborhood in Abstraction Space¶
European Case Law Identifier sits in a sparse region of the domain-specific corpus (96th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Underdeterminacy (Law) — 0.79
- Constitutionalism — 0.78
- Machine-Readable Document — 0.77
- RDA: Resource Description and Access — 0.77
- Web of Trust — 0.75
Computed from structural-signature embeddings · 2026-09-08
Not to Be Confused With¶
Do not confuse the European Case Law Identifier with a docket number, case number, neutral citation, reporter citation, URL, DOI, URN, CELEX number, European Legislation Identifier, court-code registry, metadata record, legal citation style, or the ECLI Search Engine.
ECLI is the supported acronym alias. ECLI 2.0 denotes a revision of the framework rather than an unrestricted synonym for every version. National ECLI formats are implementations or recognized variants, not separate abstractions.
The frozen semantic leader prime:record_reconciliation is related but not coverage: ECLI makes reconciliation possible by supplying a common identity; it is not the later act of matching records.
References¶
[1] European Commission, “European Case Law Identifier (ECLI)”, European e-Justice Portal. registry ↩a ↩b ↩c ↩d ↩e
[2] Publications Office of the European Union, “European Case Law Identifier”, EUR-Lex summary. registry ↩a ↩b
[3] Council of the European Union, “Council conclusions inviting the introduction of the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law”, 2011/C 127/01. registry ↩a ↩b ↩c
[4] Publications Office of the European Union, “ECLI—European Case Law Identifier”, EUR-Lex Help. registry ↩a ↩b ↩c ↩d
[5] Council of the European Union, “Council conclusions on the European case law identifier (ECLI) and a minimum set of uniform metadata for case law—including ECLI 2.0”, 2019. registry ↩
[6] European Commission, “European Case Law Identifier—Germany”, European e-Justice Portal. registry ↩