rfc9676v1.txt   rfc9676.txt 
Independent Submission P. Spinosa Independent Submission P. Spinosa
Request for Comments: 9676 Request for Comments: 9676
Category: Informational E. Francesconi Category: Informational E. Francesconi
ISSN: 2070-1721 National Research Council of Italy (CNR) ISSN: 2070-1721 National Research Council of Italy (CNR)
C. Lupo C. Lupo
November 2024 May 2025
A Uniform Resource Name (URN) Namespace for Sources of Law (LEX) LEX: A Uniform Resource Name (URN) Namespace for Sources of Law
Abstract Abstract
This document describes a Uniform Resource Name (URN) namespace This document describes LEX, a Uniform Resource Name (URN) namespace
identifier for identifying, naming, assigning, and managing identifier that identifies, names, assigns, and manages persistent
persistent resources in the legal domain. This specification allows resources in the legal domain. This specification allows adoption of
adoption of a common convention by multiple jurisdictions to a common convention by multiple jurisdictions to facilitate ease of
facilitate ease of reference and access to resources in the legal reference and access to resources in the legal domain.
domain.
This specification is an Independent Submission to the RFC Series. This specification is an Independent Submission to the RFC Series.
It is not a standard and does not have the consensus of the IETF. It is not a standard and does not have the consensus of the IETF.
Status of This Memo Status of This Memo
This document is not an Internet Standards Track specification; it is This document is not an Internet Standards Track specification; it is
published for informational purposes. published for informational purposes.
This is a contribution to the RFC Series, independently of any other This is a contribution to the RFC Series, independently of any other
skipping to change at line 41 skipping to change at line 40
implementation or deployment. Documents approved for publication by implementation or deployment. Documents approved for publication by
the RFC Editor are not candidates for any level of Internet Standard; the RFC Editor are not candidates for any level of Internet Standard;
see Section 2 of RFC 7841. see Section 2 of RFC 7841.
Information about the current status of this document, any errata, Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9676. https://www.rfc-editor.org/info/rfc9676.
Copyright Notice Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. to this document.
Table of Contents Table of Contents
1. Introduction 1. Introduction
1.1. Purpose of the "lex" Namespace 1.1. The Purpose of Namespace LEX
1.2. Background 1.2. Background
1.3. General Characteristics of the System 1.3. General Characteristics of the System
1.4. Linking a LEX Name to a Document 1.4. Linking a LEX Name to a Document
1.5. Use of LEX Names in References 1.5. Use of LEX Names in References
1.6. Definitions 1.6. Definitions
1.7. Terminology 1.7. Terminology
1.8. Syntax Used in This Document 1.8. Syntax Used in This Document
1.9. Namespace Registration 1.9. Namespace Registration
2. Registration of LEX 2. Registration of LEX
2.1. Identifier Structure 2.1. Identifier Structure
2.2. Jurisdiction-Code Register 2.2. Jurisdiction-Code Registry
2.3. Conformance with URN Syntax 2.3. Conformance with URN Syntax
2.4. Validation Mechanism 2.4. Validation Mechanism
2.5. Scope 2.5. Scope
3. General Syntax and Features of the LEX Identifier 3. General Syntax and Features of the LEX Identifier
3.1. Allowed and Not Allowed Characters 3.1. Allowed and Not Allowed Characters
3.2. Reserved Characters 3.2. Reserved Characters
3.3. Case Sensitivity 3.3. Case Sensitivity
3.4. Unicode Characters Outside the ASCII Range 3.4. Unicode Characters Outside the ASCII Range
3.5. Abbreviations 3.5. Abbreviations
3.6. Date Format 3.6. Date Format
4. Specific Syntax and Features of the LEX Identifier 4. Specific Syntax and Features of the LEX Identifier
4.1. Spaces, Connectives, and Punctuation Marks 4.1. Spaces, Connectives, and Punctuation Marks
4.2. Acronyms 4.2. Acronyms
4.3. Ordinal Numbers 4.3. Ordinal Numbers
5. Creation of the Source of Law LEX Identifier: Baseline 5. Creation of the Source of Law LEX Identifier: Baseline
Structure Structure
5.1. Basic Principles 5.1. Basic Principles
5.2. Model of Sources of Law Representation 5.2. Model of Sources of Law Representation
5.3. Structure of the Local Name 5.3. Structure of the Local-Name
5.4. Structure of the Document Identifier at "Work" Level 5.4. Structure of the Document Identifier at "Work" Level
5.5. Aliases 5.5. Aliases
5.6. Structure of the Document Identifier at "Expression" Level 5.6. Structure of the Document Identifier at "Expression" Level
5.7. Structure of the Document Identifier at "Manifestation" 5.7. Structure of the Document Identifier at "Manifestation"
Level Level
5.8. Sources of Law References 5.8. Sources of Law References
6. Specific Syntax of the Identifier at "Work" Level 6. Specific Syntax of the Identifier at "Work" Level
6.1. The Authority Element 6.1. The Authority Element
6.1.1. Indication of the Authority 6.1.1. Indication of the Authority
6.1.2. Multiple Issuers 6.1.2. Multiple Issuers
skipping to change at line 117 skipping to change at line 116
6.3.2. Multiple Dates 6.3.2. Multiple Dates
6.3.3. Unnumbered Measures 6.3.3. Unnumbered Measures
6.3.4. Multiple Numbers 6.3.4. Multiple Numbers
6.4. The Annex Element 6.4. The Annex Element
6.4.1. Formal Annexes 6.4.1. Formal Annexes
6.4.2. Annexes of Annexes 6.4.2. Annexes of Annexes
7. Specific Syntax of the Version Element of the "Expression" 7. Specific Syntax of the Version Element of the "Expression"
7.1. The Version Element 7.1. The Version Element
7.1.1. Different Versions of a Legislative Document 7.1.1. Different Versions of a Legislative Document
7.1.2. Identification of the Version 7.1.2. Identification of the Version
8. Summary of the Syntax of the Uniform Names of the "lex" 8. Summary of the Syntax of the Uniform Names of the LEX Namespace
Namespace
9. Procedure of Uniform Names Assignment 9. Procedure of Uniform Names Assignment
9.1. Specifying the Jurisdiction Element of the LEX Identifier 9.1. Specifying the Jurisdiction Element of the LEX Identifier
9.2. Jurisdictional Registrar for Names Assignment 9.2. Jurisdictional Registrar for Names Assignment
9.3. Identifier Uniqueness 9.3. Identifier Uniqueness
9.4. Identifier Persistence Considerations 9.4. Identifier Persistence Considerations
10. Recommendations for the Resolution Process 10. Recommendations for the Resolution Process
10.1. General Architecture of the System 10.1. General Architecture of the System
10.2. Catalogues for Resolution 10.2. Catalogues for Resolution
10.3. Suggested Resolver Behavior 10.3. Suggested Resolver Behavior
11. Security Considerations 11. Security Considerations
12. IANA Considerations 12. IANA Considerations
13. References 13. References
13.1. Normative References 13.1. Normative References
13.2. Informative References 13.2. Informative References
Acknowledgements Acknowledgements
Authors' Addresses Authors' Addresses
1. Introduction 1. Introduction
1.1. Purpose of the "lex" Namespace 1.1. The Purpose of Namespace LEX
The purpose of the "lex" namespace is to assign a unique identifier The purpose of the LEX namespace is to assign a unique identifier in
in a well-defined format to documents that are sources of law. In a well-defined format to documents that are sources of law. In this
this context, "sources of law" include any legal document within the context, "sources of law" include any legal document within the
domain of legislation, case law, administrative acts, or regulations. domain of legislation, case law, administrative acts, or regulations.
Potential sources of law (acts under the process of law formation, Potential sources of law (acts under the process of law formation,
such as bills) are included as well. "Legal doctrine", that is, the such as bills) are included as well. "Legal doctrine", that is, the
body of knowledge and theoretical speculation typical of legal body of knowledge and theoretical speculation typical of legal
scholars (e.g., commentary on judgment, jurisprudence review, scholars (e.g., commentary on judgment, jurisprudence review,
commentary on legislation, encyclopedic entries, monographs, articles commentary on legislation, encyclopedic entries, monographs, articles
in magazines, manuals, etc.) is explicitly not covered. in magazines, manuals, etc.) is explicitly not covered.
The identifier is conceived so that its construction depends only on The identifier is conceived so that its construction depends only on
the content of the document itself and not its online availability, the content of the document itself and not its online availability,
physical location, and access mode. The identifier itself is physical location, and access mode. The identifier itself is
assigned by the jurisdiction of the identified document. A document assigned by the jurisdiction of the identified document. A document
that is not available online may, nevertheless, have a LEX URN that is not available online may, nevertheless, have a LEX URN
identifier. identifier.
The lex URN may be used as a way to represent references (and more The LEX URN may be used as a way to represent references (and more
generally, any type of relation) among various sources of law. In an generally, any type of relation) among various sources of law. In an
online environment with resources distributed among different web online environment with resources distributed among different web
publishers, lex URNs allow a simplified global interconnection of publishers, LEX URNs allow a simplified global interconnection of
legal documents by means of automated resolution. LEX URNs consist legal documents by means of automated resolution. LEX URNs consist
of persistent and location-independent identifiers and are of persistent and location-independent identifiers and are
particularly useful when they can be mapped into or associated with particularly useful when they can be mapped into or associated with
locators such as HTTP URLs. Moreover, LEX URN details can be used as locators such as HTTP URLs. Moreover, LEX URN details can be used as
a reference to create persistent and location-independent identifiers a reference to create persistent and location-independent identifiers
that are HTTP-based [RFC3986]. that are HTTP-based [RFC3986].
1.2. Background 1.2. Background
This specification of a unique identifier for legal documents follows This specification of a unique identifier for legal documents follows
skipping to change at line 190 skipping to change at line 188
Other national initiatives in Europe introduced standards for the Other national initiatives in Europe introduced standards for the
description of legal sources [FRAN]. Collaborations between description of legal sources [FRAN]. Collaborations between
government, national research institutes, and universities have government, national research institutes, and universities have
defined national XML standards for legal document management, as well defined national XML standards for legal document management, as well
as schemes for legal document identification. Outside of Europe, as schemes for legal document identification. Outside of Europe,
similar initiatives have addressed similar problems [FRAN]. Several similar initiatives have addressed similar problems [FRAN]. Several
of these identifiers are based on a URN schema. of these identifiers are based on a URN schema.
In today's information society, the processes of political, social, In today's information society, the processes of political, social,
and economic integration of European Union (EU) member states, as and economic integration of European Union (EU) Member States, as
well as the increasing integration of the worldwide legal and well as the increasing integration of the worldwide legal and
economic processes, are causing a growing interest in the exchange of economic processes, are causing a growing interest in the exchange of
legal information knowledge at national and transnational levels. legal information at national and transnational levels. The growing
The growing desire for improved quality and accessibility of legal desire for improved quality and accessibility of legal information
information amplifies the need for interoperability among legal amplifies the need for interoperability among legal information
information systems across national boundaries. A common, well- systems across national boundaries. A common, well-defined schema
defined schema used to identify sources of law at an international used to identify sources of law at an international level is an
level is an essential prerequisite for interoperability. essential prerequisite for interoperability.
Interest groups within several countries have already expressed their Interest groups within several countries have already expressed their
intention to adopt a shared solution based on a URN technique. In intention to adopt a shared solution based on a URN technique. In
several conferences (such as [LVI]), representatives of the several conferences (such as [LVI]), representatives of the
Publications Office of the European Union (OP) have expressed the Publications Office of the European Union (OP) have expressed the
need for a unique identifier for sources of law, based on open need for a unique identifier for sources of law, based on open
standards and able to provide advanced modalities of document standards and able to provide advanced modalities of document
hyperlinking, with the aim of promoting interoperability among hyperlinking, with the aim of promoting interoperability among
national and European institution information systems. Similar national and European institution information systems. Similar
concerns have been raised by international groups concerned with free concerns have been raised by international groups concerned with free
access to legal information, and the Permanent Bureau of the Hague access to legal information, and the Permanent Bureau of the Hague
Conference on Private International Law [HCPIL] encourages State Conference on Private International Law [HCPIL] encourages State
Parties to "adopt neutral methods of citation of their legal Parties to "adopt neutral methods of citation of their legal
materials, including methods that are medium-neutral, provider- materials, including methods that are medium-neutral, provider-
neutral and internationally consistent". In a similar direction, the neutral and internationally consistent". In a similar direction, the
CEN Metalex initiative is moving, at the European level, towards the CEN Metalex initiative is moving, at the European level, towards the
definition of a standard interchange format for sources of law, definition of a standard interchange format for sources of law,
including recommendations for defining naming conventions for them. including recommendations for defining naming conventions for them.
Additionally, the need for unique identifiers for sources of law is Additionally, the need for unique identifiers for sources of law is
of particular interest in the domain of case law. This is acutely of particular interest in the domain of case law. This need is
felt within both common law systems, where cases are the main law acutely felt within both common law systems (where cases are the main
sources, and civil law systems, in order to provide an integrated law sources) and civil law systems, because unique identifiers can
access to cases and legislation, as well as to track the provide integrated access to cases and legislation, as well as the
relationships between them. This domain is characterized by a high ability to track the relationships between them. This domain is
degree of fragmentation in case law information systems, which characterized by a high degree of fragmentation in case law
usually lack interoperability. information systems, which usually lack interoperability.
In the European Union, the community institutions have stressed the In the European Union, the community institutions have stressed the
need for citizens, businesses, lawyers, prosecutors, and judges to need for citizens, businesses, lawyers, prosecutors, and judges to
become more aware of (directly applicable) EU laws and also the become more aware of (directly applicable) EU laws and also the
various national legal systems. The growing importance of national various national legal systems. The growing importance of national
judiciaries for the application of community law was stressed in the judiciaries for the application of community law was stressed in the
resolution of the European Parliament of 9 July 2008 on the role of resolution of the European Parliament of 9 July 2008 on the role of
the national judge in the European judicial system. Similarly, the the national judge in the European judicial system. Similarly, the
Council of the European Union has underlined the importance of cross- Council of the European Union has underlined the importance of cross-
border access to national case law, as well as the need for its border access to national case law, as well as the need for its
standardization, in view of an integrated access in a decentralized standardization, with a vision of a decentralized architecture with
architecture. In this view, the Working Party on Legal Data integrated access. The Working Party on Legal Data Processing
Processing (e-Law) of the Council of the European Union formed a task (e-Law) of the Council of the European Union formed a task group to
group to study the possibilities for improving cross-border access to study the possibilities for improving cross-border access to national
national case law. Taking notice of the report of the Working case law. Taking notice of the report of the Working Party's task
Party's task group, in 2009, the Council of the European Union group, in 2009, the Council of the European Union decided to
decided to elaborate on a uniform European system for the elaborate on a uniform European system for the identification of case
identification of case law (i.e., the European Case-Law Identifier law (i.e., the European Case-Law Identifier (ECLI)) and a uniform set
(ECLI)) and a uniform set of metadata based on the Dublin Core. of metadata based on the Dublin Core.
The Council of the European Union invited the Member States to The Council of the European Union invited the Member States to
introduce the European Legislation Identifier (ELI) in the legal introduce the European Legislation Identifier (ELI) in the legal
information systems, which is an http-based, Semantic Web-oriented information systems, which is an HTTP-based, Semantic Web-oriented
identification system for legislation of the European Union and identification system for legislation of the European Union and
Member States. Member States.
The LEX identifier (also referred to in this text as "LEX name") is The LEX identifier (also referred to in this text as "LEX name") is
conceived to be general enough to provide guidance at the core of the conceived to be general enough to provide guidance at the core of the
standard and offer sufficient flexibility to cover a wide variety of standard and offer sufficient flexibility to cover a wide variety of
needs for identifying legal documents of different types, namely, needs for identifying legal documents of different types, namely,
legislative, case law, and administrative acts. Moreover, it can be legislative, case law, and administrative acts. Moreover, it can be
effectively used within a federative environment where different effectively used within a federative environment where different
publishers (public and private) can provide their own items of a publishers (public and private) can provide their own items, in
legal document (that is, there is more than one manifestation of the [FRBR] sense (see Section 5.2), of a legal document (that is, there
same legal document). is more than one manifestation (see Section 5.2) of the same legal
document).
Specifications and syntax rules for the LEX identifier can also be Specifications and syntax rules for the LEX identifier can also be
used for http-based naming conventions to cope with different used for HTTP-based naming conventions to cope with different
requirements in legal information management, for example, the need requirements in legal information management, for example, the need
to have an identifier that is compliant with the Linked Open Data to have an identifier that is compliant with the Linked Open Data
principles. principles.
This document supplements the required name syntax with a naming This document supplements the required name syntax with a naming
convention that interprets all these recommendations into an original convention that interprets all these recommendations into an original
solution for sources of law identification. solution for sources of law identification.
1.3. General Characteristics of the System 1.3. General Characteristics of the System
skipping to change at line 316 skipping to change at line 315
preserving sufficient flexibility to allow for diverse document types preserving sufficient flexibility to allow for diverse document types
and to respect the need for local control of collections by an and to respect the need for local control of collections by an
equally diverse assortment of administrative entities. equally diverse assortment of administrative entities.
The challenge is to provide the right amount guidance at the core of The challenge is to provide the right amount guidance at the core of
the specification while providing sufficient flexibility to cover a the specification while providing sufficient flexibility to cover a
wide variety of needs. LEX does this by splitting the identifier wide variety of needs. LEX does this by splitting the identifier
into parts. The first part uses a preexisting standard specification into parts. The first part uses a preexisting standard specification
("country/jurisdiction name standard") to indicate the country (or ("country/jurisdiction name standard") to indicate the country (or
more generally, the jurisdiction) of origin for the legal document more generally, the jurisdiction) of origin for the legal document
being identified; the remainder ("local name") is intended for local being identified; the remainder ("local-name") is intended for local
use in identifying documents issued in that country or jurisdiction. use in identifying documents issued in that country or jurisdiction.
The second part depends only on the identification system for sources The second part depends only on the identification system for sources
of law operating in that nation, and it is mainly composed by of law operating in that nation, and it is mainly composed by
formalized information related to the enacting authority, the type of formalized information related to the enacting authority, the type of
measure, the details, and possibly the annex. measure, the details, and possibly the annex.
The identification system based on uniform names includes: The identification system based on uniform names includes:
* A schema for assigning names capable of unambiguously representing * A schema for assigning names capable of unambiguously representing
skipping to change at line 342 skipping to change at line 341
* A resolution mechanism -- in a distributed environment -- that * A resolution mechanism -- in a distributed environment -- that
ties a uniform name to the online location of the corresponding ties a uniform name to the online location of the corresponding
resource(s). resource(s).
This document considers the first of these requirements. It also This document considers the first of these requirements. It also
contains a few references to the architecture of the resolution contains a few references to the architecture of the resolution
service and to the corresponding software. service and to the corresponding software.
1.4. Linking a LEX Name to a Document 1.4. Linking a LEX Name to a Document
The LEX name is linked to the document through meta-information, The LEX name is linked to the document through metadata, which may be
which may be specified as follows: specified as follows:
* Within the document itself through a specific element within an * Within the document itself through a specific element within an
XML schema or by a meta tag [W3C.HTML]. XML schema or by a meta tag [W3C.HTML].
* Externally by means of a Resource Description Framework * Externally by means of a Resource Description Framework
[W3C.RDF-SCHEMA] triple, a specific attribute in a database, etc. [W3C.RDF-SCHEMA] triple, a specific attribute in a database, etc.
At least one of these references is necessary to enable automated At least one of these references is necessary to enable automated
construction, an update of catalogues (distributed and centralized), construction, an update of catalogues (distributed and centralized),
and the implementation of resolvers that associate the uniform name and the implementation of resolvers that associate the uniform name
skipping to change at line 369 skipping to change at line 368
LEX names can be used in references as an HREF attribute value of the LEX names can be used in references as an HREF attribute value of the
hypertext link to the referred document. This link can be created in hypertext link to the referred document. This link can be created in
two ways: two ways:
* Manually inserting the link with the uniform name in the referring * Manually inserting the link with the uniform name in the referring
document. This is a burdensome procedure, especially for document. This is a burdensome procedure, especially for
documents that are already online. documents that are already online.
* Automatically constructing (either permanently or temporarily) the * Automatically constructing (either permanently or temporarily) the
link with the uniform name through reference parsers of a text. link with the uniform name from references in the text using a
This procedure offers more time savings, even if it is subject to parser. This procedure offers more time savings, even if it is
a certain percentage of errors, since references are not always subject to a certain percentage of errors, since references are
accurate or complete. Nevertheless, this solution could be not always accurate or complete. This solution could nevertheless
acceptable for already-published documents. be acceptable for documents that are already published.
No matter which method is adopted, new documents produced in a No matter which method is adopted, new documents produced in a
certain format (for example, XML, XHTML, etc.) should express certain format (for example, XML, XHTML, etc.) should express
references through the uniform name of the document referred to. references through the uniform name of the document referred to.
1.6. Definitions 1.6. Definitions
The following terms are used in this document: The following terms are used in this document:
Source of Law: A general concept that refers to legislation, case Source of Law: A general concept that refers to legislation, case
skipping to change at line 410 skipping to change at line 409
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.8. Syntax Used in This Document 1.8. Syntax Used in This Document
This document uses a syntax that is based on the Augmented Backus- This document uses a syntax that is based on the Augmented Backus-
Naur Form (ABNF) [RFC5234] meta-language, which is used in many RFCs. Naur Form (ABNF) [RFC5234] meta-language, which is used in many RFCs.
1.9. Namespace Registration 1.9. Namespace Registration
The "lex" namespace has been registered in the "Formal URN The LEX namespace has been registered in the "Formal URN Namespaces"
Namespaces" registry. See Section 12. registry. See Section 12.
2. Registration of LEX 2. Registration of LEX
2.1. Identifier Structure 2.1. Identifier Structure
The identifier has the following hierarchical structure: The identifier has the following hierarchical structure:
"urn:lex:" NSS "urn:lex:" NSS
where NSS is the Namespace Specific String composed as follows: where NSS is the Namespace Specific String composed as follows:
skipping to change at line 455 skipping to change at line 454
jurisdiction-code: Usually the identification code of the country jurisdiction-code: Usually the identification code of the country
where the source of law is issued. To facilitate the transparency where the source of law is issued. To facilitate the transparency
of the name, the jurisdiction-code usually follows the rules of of the name, the jurisdiction-code usually follows the rules of
identification of other Internet applications, based on domain identification of other Internet applications, based on domain
name (for details and special cases, see Section 2.2). name (for details and special cases, see Section 2.2).
Due to the differences in representation in the various languages Due to the differences in representation in the various languages
of a country, the use of the standard [ISO.3166-1] is strongly of a country, the use of the standard [ISO.3166-1] is strongly
RECOMMENDED for easier identification of the country. Therefore, RECOMMENDED for easier identification of the country. Therefore,
a urn-lex ID always begins with a sequence of ASCII characters: a LEX URN ID always begins with a sequence of ASCII characters:
"urn:lex:ccTLD". For all the other components that follow the "urn:lex:ccTLD". For all the other components that follow the
jurisdiction-code, the Jurisdictional Registrar decides the mode jurisdiction-code, the Jurisdictional Registrar decides the mode
of representation (ASCII or UTF-8 percent-encoding; see of representation (ASCII or UTF-8 percent-encoding; see
Section 3.4). Section 3.4).
Where applicable, the domain name of the country or multinational Where applicable, the domain name of the country or multinational
or international organization is used. If such information is not or international organization is used. If such information is not
available for a particular institution, a specific code will be available for a particular institution, a specific code will be
defined (see Section 2.2). Examples reported in this document are defined (see Section 2.2). Examples reported in this document are
hypothetical and assume that the corresponding domain name is used hypothetical and assume that the corresponding domain name is used
for the jurisdiction-code. for the jurisdiction-code.
jurisdiction-unit The possible administrative hierarchical sub- jurisdiction-unit: The possible administrative hierarchical sub-
structures defined by each country or organization within their structures defined by each country or organization within their
specific legal system. This additional information can be used specific legal system. This additional information can be used
when two or more levels of legislative or judicial production when two or more levels of legislative or judicial production
exist (e.g., federal, state, and municipality level) and the same exist (e.g., federal, state, and municipality level) and the same
bodies may be present in each jurisdiction. Therefore, acts of bodies may be present in each jurisdiction. Therefore, the
the same type issued by similar authorities in different areas jurisdiction-unit differs for acts of the same type issued by
differ for the jurisdiction-unit specification. similar authorities but pertain to different jurisdictions related
to different geographical areas.
The following is an example: An example can be the following:
"br:governo:decreto" (decree of federal government),
"br:governo:decreto" (decree of federal government) "br;sao.paulo:governo:decreto" (decree of São (SU+00E3o) Paulo
"br;sao.paulo:governo:decreto" (decree of SU+00E3o Paulo state) state)
"br;sao.paulo;campinas:governo:decreto" (decree of Campinas "br;sao.paulo;campinas:governo:decreto" (decree of Campinas
municipality) municipality).
The following are fictitious examples of sources of law identifiers: The following are fictitious examples of sources of law identifiers:
urn:lex:it:stato:legge:2003-09-21;456 urn:lex:it:stato:legge:2003-09-21;456
(Italian act) (Italian act)
urn:lex:fr:etat:loi:2004-12-06;321 urn:lex:fr:etat:loi:2004-12-06;321
(French act) (French act)
urn:lex:es:estado:ley:2002-07-12;123 urn:lex:es:estado:ley:2002-07-12;123
(Spanish act) (Spanish act)
urn:lex:ch;glarus:regiere:erlass:2007-10-15;963 urn:lex:ch;glarus:regiere:erlass:2007-10-15;963
(Glarus Swiss Canton decree) (Glarus Swiss Canton decree)
urn:lex:eu:commission:directive:2010-03-09;2010-19-EU urn:lex:eu:commission:directive:2010-03-09;2010-19-EU
(EU Commission Directive) (EU Commission Directive)
urn:lex:us:supreme.court:decision:1978-04-28;77-5953 urn:lex:us:supreme.court:decision:1978-04-28;77-5953
(US SC decision: Riley vs Illinois) (US SC decision: Riley vs Illinois)
urn:lex:be:conseil.etat:decision:2008-07-09;185.273 urn:lex:be:conseil.etat:decision:2008-07-09;185.273
(Decision of the Belgian Council of State) (Decision of the Belgian Council of State)
2.2. Jurisdiction-Code Register 2.2. Jurisdiction-Code Registry
A new jurisdiction-code registry has been created. Note that this is A new jurisdiction-code registry has been created. Note that this is
a CNR registry and *not* an IANA registry. a CNR registry and *not* an IANA registry.
Each entry contains the following elements: Each entry contains the following elements:
jurisdiction-code: The identifier of jurisdiction assigned to the jurisdiction-code: The identifier assigned to the jurisdiction
country or organization. (i.e., to the country or organization).
jurisdiction: The official name of the jurisdiction, country or jurisdiction: The official name of the jurisdiction (i.e., the
organization. country or organization).
registrant: Essential information that identifies the organization registrant: Essential information that identifies the organization
that requested the registration of the code. The registrant will that requested the registration of the code. The registrant will
be responsible for its DNS zone, the attribution of sub-zone be responsible for its DNS zone, the attribution of sub-zone
delegations, and so on. It is RECOMMENDED that each jurisdiction delegations, and so on. It is RECOMMENDED that each jurisdiction
create a registry of all delegated levels so that the organization create a registry of all delegated levels so that the organization
responsible for each sub-zone can easily be identified. responsible for each sub-zone can easily be identified.
reference: A reference to the defining document (if any). reference: A reference to the defining document (if any).
The registry is initially empty. The following are possible example The table, available at the address lex-urn.nic.it, is initially
entries: empty. The registry is initially empty. The following are possible
example entries:
"br"; "Brazil"; "Prodasen, Federal Senate, address, contact"; "br"; "Brazil"; "Prodasen, Federal Senate, address, contact";
\[reference\] \[reference\]
"eu"; "European Union"; "DG Digit, European Commission, address, "eu"; "European Union"; "DG Digit, European Commission, address,
contact"; \[reference\] contact"; \[reference\]
"un.org"; "United Nations"; "DPI, United Nations, address, "un.org"; "United Nations"; "DPI, United Nations, address,
contact"; \[reference\] contact"; \[reference\]
CNR is responsible for the jurisdiction-code and the root lex- CNR is responsible for the jurisdiction-code and the root lex-
nameserver.nic.it registries of the resolution routing. nameserver.nic.it registries of the resolution routing.
skipping to change at line 547 skipping to change at line 547
expert(s) according to the established rules of governance (published expert(s) according to the established rules of governance (published
on the CNR website dedicated to LEX governance). The application on the CNR website dedicated to LEX governance). The application
will be evaluated according to the Jurisdictional Registrar will be evaluated according to the Jurisdictional Registrar
authoritativeness and the offered guarantees. The designated authoritativeness and the offered guarantees. The designated
expert(s) will evaluate such applications with a similar approach as expert(s) will evaluate such applications with a similar approach as
evaluations of the DNS. Typically, such applications should come evaluations of the DNS. Typically, such applications should come
from public administrations, as authorities enacting sources of law. from public administrations, as authorities enacting sources of law.
The adopted registration policy is similar to that of the "Expert The adopted registration policy is similar to that of the "Expert
Review" policy specified in [RFC8126]. The designated expert(s) will Review" policy specified in [RFC8126]. The designated expert(s) will
assign jurisdiction codes based on the following principles: assign jurisdiction-codes based on the following principles:
* If a request comes from a jurisdiction that corresponds to a * If a request comes from a jurisdiction that corresponds to a
country and the jurisdiction code is the same as a top-level country and the jurisdiction-code is the same as a top-level
Country Code Top-Level Domain (ccTLD), then the top-level ccTLD Country Code Top-Level Domain (ccTLD), then the top-level ccTLD
should be used as the jurisdiction code. should be used as the jurisdiction-code.
* If a request comes from a jurisdiction that corresponds to a * If a request comes from a jurisdiction that corresponds to a
multi-national organization (e.g., European Union) or multi-national organization (e.g., European Union) or
international organization (e.g., United Nations and World Trade international organization (e.g., United Nations and World Trade
Organization), the Top-Level Domain Name (e.g., "eu") or the Organization), the Top-Level Domain Name (e.g., "eu") or the
Domain Name (e.g., "un.org" and "wto.org") of the organization Domain Name (e.g., "un.org" and "wto.org") of the organization
should be used as the jurisdiction code. should be used as the jurisdiction-code.
* If a multi-national or international organization does not have a * If a multi-national or international organization does not have a
registered domain, the designated expert(s) should assign registered domain, the designated expert(s) should assign
something like "name.lex.arpa", where the name will be the acronym something like "name.lex.arpa", where the name will be the acronym
of the organization name in the language chosen by the of the organization name in the language chosen by the
organization itself. For example, the jurisdiction code of the organization itself. For example, the jurisdiction-code of the
European Economic Community could be "eec.lex.arpa". The alias European Economic Community could be "eec.lex.arpa". The alias
mechanism allows for acronyms in different languages. mechanism allows for acronyms in different languages.
Jurisdiction codes MUST NOT be renamed, because that would violate Jurisdiction-codes MUST NOT be renamed, because that would violate
the rule that URN assignments be persistent. the rule that URN assignments be persistent.
Jurisdiction codes MUST NOT ever be deleted. They can only be marked Jurisdiction-codes MUST NOT ever be deleted. They can only be marked
as "obsolete", i.e., closed for new assignments within the as "obsolete", i.e., closed for new assignments within the
jurisdiction. Requests to obsolete a jurisdiction code are also jurisdiction. Requests to obsolete a jurisdiction-code are also
processed by the designated expert(s). processed by the designated expert(s).
Designated expert(s) can unilaterally initiate allocation or Designated expert(s) can unilaterally initiate allocation or
obsolescence of a jurisdiction code. obsolescence of a jurisdiction-code.
Requests for new jurisdiction code assignments must include the Requests for new jurisdiction-code assignments must include the
organization or country requesting it and contact information (email) organization or country requesting it and contact information (email)
of who requested the assignment. of who requested the assignment.
2.3. Conformance with URN Syntax 2.3. Conformance with URN Syntax
The "lex" namespace identifier (NID) syntax conforms to [RFC8141]. The LEX namespace identifier (NID) syntax conforms to [RFC8141].
However, a series of characters are reserved for identifying elements However, a series of characters are reserved for identifying elements
or sub-elements, or for future extensions of the LEX naming or sub-elements, or for future extensions of the LEX naming
convention (see Section 3.2). convention (see Section 3.2).
2.4. Validation Mechanism 2.4. Validation Mechanism
The Jurisdictional Registrar (or those it delegates) of each adhering The Jurisdictional Registrar (or those it delegates) of each adhering
country or organization is responsible for the definition or country or organization is responsible for the definition or
acceptance of the uniform name's primary elements (issuing authority acceptance of the uniform name's primary elements (issuing authority
and type of legal measure). and type of legal measure).
2.5. Scope 2.5. Scope
Global interest. In fact, each body that enacts sources of law can The scope is global. In fact, each Body that enacts sources of law
identify them by this scheme. Furthermore, other bodies (even non- can identify them by this scheme. Furthermore, other bodies (even
enacting sources of law, such as newspapers, magazine publishers, non-enacting sources of law, such as newspapers, magazine publishers,
etc.) that aim to reference legal documents can unequivocally etc.) that aim to reference legal documents can unequivocally
identify them by this scheme. identify them by this scheme.
3. General Syntax and Features of the LEX Identifier 3. General Syntax and Features of the LEX Identifier
This section lists the general features applicable to all This section lists the general features applicable to all
jurisdictions. jurisdictions.
3.1. Allowed and Not Allowed Characters 3.1. Allowed and Not Allowed Characters
The characters are defined in accordance with [RFC8141]. For various The characters are defined in accordance with [RFC8141]. For various
reasons that are explained later, only a subset of characters is reasons that are explained later, only a subset of characters is
allowed in the "lex" NSS. All other characters are either eliminated allowed in the LEX NSS. All other characters are either eliminated
or converted. or converted.
For the full syntax of the uniform names in the "lex" space, please For the full syntax of the uniform names in the LEX space, please see
see Section 8. Section 8.
3.2. Reserved Characters 3.2. Reserved Characters
The following characters are reserved in the specific "lex" The following characters are reserved in the specific LEX namespace:
namespace:
"@" Separator of the expression that contains information on "@" Separator of the expression that contains information on
version and language. version and language.
"$" Separator of the manifestation that contains information on "$" Separator of the manifestation that contains information on
format, editor, etc. format, editor, etc.
":" Separator of the main elements of the name at any entity. ":" Separator of the main elements of the name at any entity.
";" Separator of the level. It identifies the introduction of an ";" Separator of the level. It identifies the introduction of an
skipping to change at line 656 skipping to change at line 655
(e.g., multiple numbers). (e.g., multiple numbers).
"~" Separator of the partition identifier in references (e.g., "~" Separator of the partition identifier in references (e.g.,
paragraph of an article). paragraph of an article).
"*" Reserved for future expansions. "*" Reserved for future expansions.
"!" Reserved for future expansions. "!" Reserved for future expansions.
To keep backward compatibility with existing applications in some To keep backward compatibility with existing applications in some
jurisdictions, the "lex" NID syntax does not include the use of the jurisdictions, the LEX NID syntax does not include the use of the
character "/" in this version. This character is always converted character "/" in this version. This character is always converted
into "-", except in the formal annexes (see Section 6.4.1). into "-", except in the formal annexes (see Section 6.4.1).
3.3. Case Sensitivity 3.3. Case Sensitivity
For all the languages where different cases (uppercase or lowercase) For all the languages where different cases (uppercase or lowercase)
or different spellings of the same word are possible, names belonging or different spellings of the same word are possible, names belonging
to "lex" namespace are case-insensitive. For the Latin alphabet, it to LEX namespace are case-insensitive. For the Latin alphabet, it is
is RECOMMENDED that names be created in lower case, but names that RECOMMENDED that names be created in lower case, but names that
differ only in case or in the spelling of the same word MUST be differ only in case or in the spelling of the same word MUST be
considered equivalent (e.g., "Ministry" will be recorded as considered equivalent (e.g., "Ministry" will be recorded as
"ministry"). "ministry").
3.4. Unicode Characters Outside the ASCII Range 3.4. Unicode Characters Outside the ASCII Range
In order to exploit the DNS as a routing tool towards the proper In order to exploit the DNS as a routing tool towards the proper
resolution system, keep editing and communication more simple, and resolution system, keep editing and communication more simple, and
avoid character percent-encoding, it is RECOMMENDED that characters avoid character percent-encoding, it is RECOMMENDED that characters
outside the ASCII range (e.g., national characters, diacritic signs, outside the ASCII range (e.g., national characters, diacritic signs,
etc.) be replaced by base ASCII characters. For example, the Italian etc.) are turned into base ASCII characters (e.g., the Italian term
term "sanitU+00E0" can be replaced by "sanita", the French term "sanità" (sanitU+00E0)" replaced into "sanita", the French term
"ministU+00E8re" can be replaced by "ministere", and "MU+00FCnchen" "ministère" (ministU+00E8re) replaced into "ministere", in case by
can be replaced by "muenchen" (transliteration). transliteration (e.g., "München" (MU+00FCnchen) replaced into
"muenchen").
This mapping consists of: This mapping consists of:
* Transcription from non-Latin alphabets * Transcription from non-Latin alphabets
* Transliteration of some signs (e.g., diaeresis and eszett) * Transliteration of some signs (e.g., diaeresis and eszett)
* Preservation of only the basic characters, eliminating the signs * Preservation of only the basic characters, eliminating the signs
placed above (e.g., accents and tilde), below (e.g., cedilla and placed above (e.g., accents and tilde), below (e.g., cedilla and
little tail), or on (e.g., oblique cut) little tail), or on (e.g., oblique cut)
The most suitable, well-known, and widespread mapping system for a The most suitable, well-known, and widespread mapping system for a
given language MUST be chosen by the jurisdiction, or in agreement given language MUST be chosen by the jurisdiction or by the
with this one, by the jurisdiction-unit in case of different jurisdiction-unit (in agreement with the jurisdiction) in the case of
languages in various regions, also taking into account the choices different languages in various regions, also taking into account the
made for the same language by other jurisdictions. This mapping is choices made for the same language by other jurisdictions. This
simpler and more feasible for languages that use the Latin alphabet mapping is simpler and more feasible for languages that use the Latin
and gradually becomes more complex for other alphabets and for alphabet and gradually becomes more complex for other alphabets and
writing systems that use opposite orientation (from right to left) or for writing systems that use opposite orientation (from right to
are based on ideographic symbols. left) or are based on ideographic symbols.
If this conversion is not acceptable by a specific jurisdiction or it If this conversion is not acceptable by a specific jurisdiction or it
is not available in a given language, Unicode MUST be used, and for is not available in a given language, Unicode MUST be used, and for
accessing network protocols, any Unicode code points outside the accessing network protocols, any Unicode code points outside the
ASCII range MUST be converted to UTF-8 percent-encoding according to ASCII range MUST be converted to UTF-8 percent-encoding according to
[RFC3986] and [RFC3629] . [RFC3986] and [RFC3629] .
In this case, it should be noted that the generated URN (as some of In this case, it should be noted that the generated URN (as well as
its parts) cannot be used directly for routing through the DNS. some of its parts) cannot be used directly for routing through the
Therefore, the jurisdiction must adopt one of the following DNS. Therefore, the jurisdiction must adopt one of the following
strategies: strategies:
* Convert non-ASCII characters within the DNS into IDN encoding * Convert non-ASCII characters within the DNS into IDN encoding
using Punycode translation [RFC5894] (e.g., mU+00FCnchen in xn-- using Punycode translation [RFC5894] (e.g., "münchen"
mnchen-3ya) and develop a software interface that converts the URN (mU+00FCnchen) in xn--mnchen-3ya) and develop a software interface
before the navigation in the DNS. that converts the URN before the navigation in the DNS.
* Create a routing service relying on a software, outside of the * Create a routing service relying on a software, outside of the
DNS, that addresses a proper resolution service. DNS, that addresses a proper resolution service.
Note that the urn:lex ID could contain groups of characters (UTF-8 Note that the LEX URN ID could contain groups of characters (UTF-8
percent-encoded) of some languages with different orientations. In percent-encoded) of some languages with different orientations. In
this case, the BiDi rules apply [RFC5893]. this case, the BiDi rules apply [RFC5893].
The preferred order is summarized as follows: The preferred order is summarized as follows:
* Conversion into basic ASCII is the RECOMMENDED solution (for not * Conversion into basic ASCII is the RECOMMENDED solution (because
having to make conversions for network protocols and the DNS). conversions for network protocols and the DNS are not needed).
* Using Unicode and converting to UTF-8 percent-encoding [RFC3629] * Using Unicode and converting to UTF-8 percent-encoding [RFC3629]
for accessing network protocols and to Punycode [RFC5894] only for for accessing network protocols and to Punycode [RFC5894] only for
navigation in DNS via software interface. navigation in DNS via software interface.
* Creation of a routing service relying on a software outside of DNS * Creation of a routing service relying on a software outside of DNS
and addressing a proper resolution service. and addressing a proper resolution service.
The first solution allows native DNS routing while the other two The first solution allows native DNS routing while the other two
solutions require software development for the interface or the solutions require software development for the interface or the
routing. However, it is up to the specific jurisdiction to choose routing. However, it is up to the specific jurisdiction to choose
the preferred solution. the preferred solution.
The following are two examples (Latin and Cyrillic alphabets) The following are two examples (Latin and Cyrillic alphabets)
relating to the different solutions adopted: relating to the different solutions adopted:
* A circular adopted by the Municipality of Munich (Rundschreiben * A circular adopted by the Municipality of Munich (Rundschreiben
der Stadt MU+00FCnchen): der Stadt "München" (MU+00FCnchen)):
- ASCII:
urn:lex:de:stadt.munchen:rundschreiben: ...
- Unicode:
urn:lex:de:stadt.mU+00FCnchen:rundschreiben: ...
- UTF-8:
urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben: ...
- Punycode:
urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben: ... - ASCII: urn:lex:de:stadt.munchen:rundschreiben:...;
- Unicode: urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...;
- UTF-8: urn:lex:de:stadt.m%C3%BCnchen:rundschreiben:...;
- PUNYCODE: urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben:...
* A state law of the Russian Federation (Latin: gosudarstvo zakon; * A state law of the Russian Federation (Latin: gosudarstvo zakon;
Cyrillic: U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435 Cyrillic: "состояние закон"
U+0437U+0430U+043AU+043EU+043D): (U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435
U+0437U+0430U+043AU+043EU+043D)), assuming that the Russia
- ASCII: jurisdiction-code is expressed in ASCII ("ru") (while the Cyrillic
version would be "рф" (U+0440U+0444)):
urn:lex:ru:gosudarstvo:zakon: ...
- Unicode:
urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D
U+0438U+0435:U+0437U+0430U+043AU+043EU+043D: ...
- UTF-8:
urn:lex:ru:%xD1%x81%xD0%xBE%xD1%x81%xD1%x82%xD0%xBE%xD1
%x8F%xD0%xBD%xD0%xB8%xD0%xB5:%xD0%xB7%xD0%xB0%xD0%xBA
%xD0%xBE%xD0%xBD: ...
- Punycode:
urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme: ...
| Note: The above assumes that the Russia jurisdiction-code is - ASCII: urn:lex:ru:gosudarstvo:zakon:...
| expressed in ASCII ("ru"), while the Cyrillic version - Unicode: urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D
| ("U+0440U+0444") has the Punycode "xn--p1ai". U+0438U+0435:U+0437U+0430U+043AU+043EU+043D:...
- UTF-8: urn:lex:ru:%D1%81%D0%BE%D1%81%D1%82%D0%BE%D1
%8F%D0%BD%D0%B8%D0%B5:%D0%B7%D0%B0%D0%BA
%D0%BE%D0%BD:...
- PUNYCODE: urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme:...
3.5. Abbreviations 3.5. Abbreviations
Abbreviations are often used in law for indicating institutions Abbreviations are often used in law for indicating institutions
(e.g., Min.), structures (e.g., Dept.), or legal measures (e.g., (e.g., Min.), structures (e.g., Dept.), or legal measures (e.g.,
Reg.), but they are not used in a uniform way. Therefore, their Reg.), but they are not used in a uniform way. Therefore, their
expansion is highly RECOMMENDED (e.g., "Min." is expanded as expansion is highly RECOMMENDED (e.g., "Min." is expanded as
"ministry"). "ministry").
3.6. Date Format 3.6. Date Format
[ISO.8601.1988] describes the international format for representing [ISO.8601-1.2019] and [ISO.8601-2.2019] describe the international
dates. Dates MUST always be represented in this format (4 digits for format for representing dates. Dates MUST always be represented in
the year, 2 digits for the month, and 2 digits for the day): this format (4 digits for the year, 2 digits for the month, and 2
digits for the day):
date-iso = yyyy-mm-dd date-iso = year "-" month "-" day
For example, "September 2, 99" will be written as "1999-09-02". For example, "September 2, 99" will be written as "1999-09-02".
This format ensures interoperability between different representation This format ensures interoperability between different representation
systems, and there are several programs for mapping other formats to systems and there are several programs for mapping other formats to
this one. this one. However, to make reading and understanding such other
formats (e.g., Jewish calendar), the LEX URN scheme provides that the
date can be added in the jurisdiction's own format. The date in the
previous example (1999-09-02) would be as follows:
However, to facilitate reading and understanding other formats (e.g., * in Hebrew characters (21 Elul 5759):
Jewish calendar), the urn:lex scheme allows for the date to be added
in the jurisdiction's own format. For example, the date in the
previous example would be 21.Elul,5759, that is:
* In Hebrew characters: כ״א-בֶּאֱלוּל-תשנ״ט
U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.U+05EA Note that the example above uses right-to-left (RTL) script, which
U+05E9U+05E0U+05F4U+05D8 in the context of this specification may be displayed differently
by different document presentation environments. The descriptive
text may be more reliable to follow than the necessarily device-
and application-specific rendering.
* In UTF-8: * in U+ notation:
%x5c%x75%x30%x35%x44%x42%x5c%x75%x30%x35%x46%x34%x5c%x75%x30%x35 U+05D8U+05F4U+05E0U+05E9U+05EAU+002DU+05DCU+05D5U+05BCU+05DC
%x44%x30%x2e%x5c%x75%x30%x35%x44%x30%x5c%x75%x30%x35%x42%x31%x5c U+05D0U+05B1U+05D1U+05B6U+05BCU+002DU+05D0U+05F4U+05DB
%x75%x30%x35%x44%x43%x5c%x75%x30%x35%x44%x35%x5c%x75%x30%x35%x42
%x43%x5c%x75%x30%x35%x44%x43%x2e%x5c%x75%x30%x35%x45%x41%x5c%x75
%x30%x35%x45%x39%x5c%x75%x30%x35%x45%x30%x5c%x75%x30%x35%x46%x34
%x5c%x75%x30%x35%x44%x38
Therefore, for all the dates in the urn:lex identifier (see Sections * in UTF-8 code:
%d7%98%d7%b4%d7%a0%d7%a9%d7%aa-%d7%9c%d7%95%d6%bc%d7%9c%d7%
90%d6%b1%d7%91%d6%b6%d6%bc-%d7%90%d7%b4%d7%9b
Therefore, for all the dates in the LEX URN identifier (see Sections
6.3 and 7.1.2), it is possible to indicate the date in the local 6.3 and 7.1.2), it is possible to indicate the date in the local
format: format:
date = date-iso [ "|" date-loc ] date = date-iso ["|" date-loc]
For example, "September 2, 99" will be written in ISO format and For example, 1999-09-02 will be written in ISO plus Hebrew format as:
Hebrew format as follows:
1999-09-02|U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC. 1999-09-02|כ״א-בֶּאֱלוּל-תשנ״ט
U+05EAU+05E9U+05E0U+05F4U+05D8
The characters that are not allowed (e.g., "/") or reserved (e.g., which is to be converted into UTF-8 for network protocols and for
",") cannot exist inside the date-loc and therefore MUST be turned resolution (see Section 3.4). The characters that are not allowed
into ".". (e.g., "/") or reserved (e.g., ",") cannot exist inside the date-loc
and therefore MUST be turned into ".". To be aligned with ISO
format, any blank between day, month, and year MUST be converted into
"-".
In the above Hebrew character examples, the sequence of characters is
as follows: "כ" (HEBREW LETTER KAF, U+05DB), "״" (HEBREW PUNCTUATION
GERSHAYIM, U+05F4), "א" (HEBREW LETTER ALEF, U+05D0), "-" (HYPHEN-
MINUS, U+002D), "בֶּ" (HEBREW LETTER BET, HEBREW POINT SEGOL, HEBREW
POINT DAGESH OR MAPIQ, U+05D1 U+05B6 U+05BC), "אֱ" (HEBREW LETTER
ALEF, HEBREW POINT HATAF SEGOL, U+05D0 U+05B1), "ל" (HEBREW LETTER
LAMED, U+05DC), "וּ" (HEBREW LETTER VAV, HEBREW POINT DAGESH OR
MAPIQ, U+05D5 U+05BC), "ל" (HEBREW LETTER LAMED, U+05DC), "-"
(HYPHEN-MINUS, U+002D), "ת" (HEBREW LETTER TAV, U+05EA), "ש" (HEBREW
LETTER SHIN, U+05E9), "נ" (HEBREW LETTER NUN, U+05E0), "״" (HEBREW
PUNCTUATION GERSHAYIM, U+05F4), and "ט" (HEBREW LETTER TET, U+05D8).
4. Specific Syntax and Features of the LEX Identifier 4. Specific Syntax and Features of the LEX Identifier
This section discusses features related to specific jurisdictions. This section discusses features related to specific jurisdictions.
The implementation of these features is RECOMMENDED. The implementation of these features is RECOMMENDED.
4.1. Spaces, Connectives, and Punctuation Marks 4.1. Spaces, Connectives, and Punctuation Marks
When explicitly present, all language connectives (e.g., articles, When explicitly present, all language connectives (e.g., articles,
prepositions, etc.), punctuation marks, and special characters (e.g., prepositions, etc.), punctuation marks, and special characters (e.g.,
skipping to change at line 874 skipping to change at line 869
4.2. Acronyms 4.2. Acronyms
The use of acronyms might be confusing and encourage ambiguity in The use of acronyms might be confusing and encourage ambiguity in
uniform names (the same acronym may indicate two different uniform names (the same acronym may indicate two different
institutions or structures); therefore, their expansion is highly institutions or structures); therefore, their expansion is highly
RECOMMENDED (e.g., "FAO" is expanded as RECOMMENDED (e.g., "FAO" is expanded as
"food.agriculture.organization"). "food.agriculture.organization").
4.3. Ordinal Numbers 4.3. Ordinal Numbers
To even the representation, it is highly RECOMMENDED that any ordinal To standardise the representation, it is highly RECOMMENDED that any
number included in a component of a document name (e.g., in the ordinal number included in a component of a document name (e.g., in
description of an institution body) is indicated in Western Arabic the description of an institution Body) is indicated in Western
numerals, regardless to the original expression, whether Roman Arabic numerals, regardless to the original expression, whether Roman
numerals, an adjective, Arabic numerals with an apex, etc. (such as numerals, an adjective, Arabic numerals with an apex, etc. (such as
IV, third, 1U+00B0, and 2^). For example, "Department IV" becomes IV, third, 1° (1U+00B0), and 2^). For example, "Department IV"
"department.4". becomes "department.4".
5. Creation of the Source of Law LEX Identifier: Baseline Structure 5. Creation of the Source of Law LEX Identifier: Baseline Structure
5.1. Basic Principles 5.1. Basic Principles
The uniform name must identify one and only one document (more The uniform name must identify one and only one document (more
precisely a "bibliographic resource" [ISBD]; see also Section 5.2) precisely a "bibliographic resource" [ISBD]; see also Section 5.2)
and is created in such a way that it is: and is created in such a way that it is:
* self-explanatory, * self-explanatory,
skipping to change at line 912 skipping to change at line 907
5.2. Model of Sources of Law Representation 5.2. Model of Sources of Law Representation
According to the Functional Requirements for Bibliographic Records According to the Functional Requirements for Bibliographic Records
(FRBR) [FRBR] model developed by IFLA (International Federation of (FRBR) [FRBR] model developed by IFLA (International Federation of
Library Associations and Institutions), four fundamental entities (or Library Associations and Institutions), four fundamental entities (or
aspects) can be specified in a source of law, as in any intellectual aspects) can be specified in a source of law, as in any intellectual
production. production.
The first two entities reflect its contents: The first two entities reflect its contents:
work: Identifies a distinct intellectual creation; in our case, it work: Identifies a distinct intellectual creation; in this document,
identifies a source of law both in its original form as amended it identifies a source of law in both its original form and its
over time. amended form over time.
expression: Identifies a specific intellectual realization of a expression: Identifies a specific intellectual realization of a
work; in our case, it identifies every different (original or up- work; in this document, it identifies every different (original or
to-date) version of the source of law over time and/or language in up-to-date) version of the source of law over time and/or language
which the text is expressed. in which the text is expressed.
The other two entities relate to its form: The other two entities relate to its form:
manifestation: Identifies a physical embodiment of an expression of manifestation: Identifies a physical embodiment of an expression of
a work; in our case, it identifies embodiments in different media a work; in this document, it identifies embodiments in different
(printing, digital, etc.), encoding formats (XML, PDF, etc.), or media (printing, digital, etc.), encoding formats (XML, PDF,
other publishing characteristics. etc.), or other publishing characteristics.
item: Identifies a specific copy of a manifestation; in our case, it item: Identifies a specific copy of a manifestation; in this
identifies individual physical copies as they are found in document, it identifies individual physical copies as they are
particular physical locations. found in particular physical locations.
In this document, the [FRBR] model has been interpreted for the In this document, the [FRBR] model has been interpreted for the
specific characteristics of the legal domain. In particular, apart specific characteristics of the legal domain. In particular, apart
from the language that does produce a specific expression, the from the language that does produce a specific expression, the
discriminative criterion between expression and manifestation is discriminative criterion between expression and manifestation is
based on the difference of the juridical effects that a variation can based on the difference of the juridical effects that a variation can
provide with respect to the involved actors (citizens, parties, and provide with respect to the involved actors (citizens, parties, and
institutions). In this scenario, the main characteristic of the institutions). In this scenario, the main characteristic of the
expression of an act is represented by its validity over the time expression of an act is represented by its validity over the time
during which it provides the same juridical effects. These effects during which it provides the same juridical effects. These effects
may change as a result of amendments or annulments of other may change as a result of amendments or annulments of other
legislative or jurisprudential acts. Therefore, notes, summaries, legislative or jurisprudential acts. Therefore, notes, summaries,
comments, anonymizations, and other editorial activities over the comments, anonymizations, and other editorial activities over the
same text do not produce different expressions. Instead, they same text do not produce different expressions. Instead, they
produce different manifestations. produce different manifestations.
5.3. Structure of the Local Name 5.3. Structure of the Local-Name
The local-name within the "lex" namespace MUST contain all the The local-name within the LEX namespace MUST contain all the
necessary pieces of information enabling the unequivocal necessary pieces of information enabling the unequivocal
identification of a legal document. If the local-name violates this identification of a legal document. If the local-name violates this
requirement, the related URN is not a valid one within the "lex" requirement, the related URN is not a valid one within the LEX
namespace. namespace.
In the legal domain, three components are always present at the In the legal domain, three components are always present at the
"work" level: the enacting authority, the type of provision, and the "work" level: the enacting authority, the measure type, and the
details. A fourth component, the annex, can also be added. It is details. A fourth component, the annex, is added if any. It is
often necessary to differentiate various expressions, that is: often necessary to differentiate various expressions, that is:
* the original version and all the amended versions of the same * the original version and all the amended versions of the same
document, and document, and
* the versions of the text expressed in the different official * the versions of the text expressed in the different official
languages of the state or organization. languages of the state or organization.
Finally, the uniform name allows a distinction among diverse Finally, the uniform name allows a distinction among diverse
manifestations that may be produced by multiple publishers using manifestations that may be produced by multiple publishers using
skipping to change at line 983 skipping to change at line 978
added to the expression for representing the characteristics of the added to the expression for representing the characteristics of the
publication (manifestation). publication (manifestation).
Information that forms a uniform name for a source of law at each Information that forms a uniform name for a source of law at each
level (work, expression, and manifestation) is expressed in the level (work, expression, and manifestation) is expressed in the
official language of the relevant jurisdiction. More language- official language of the relevant jurisdiction. More language-
dependent names (aliases) are created in cases where there are dependent names (aliases) are created in cases where there are
multiple official languages (as in Switzerland) or more involved multiple official languages (as in Switzerland) or more involved
jurisdictions (as in international treaties). jurisdictions (as in international treaties).
Therefore, the more general structure of the local name appears as Therefore, the more general structure of the local-name appears as
follows: follows:
local-name = work ["@" expression] ["$" manifestation] local-name = work ["@" expression] ["$" manifestation]
However, consistent with legislative practice, the uniform name of However, consistent with legislative practice, the uniform name of
the main original provision (work) becomes the identifier of an the main original provision (work) becomes the identifier of an
entire class of documents that includes the following: the original entire class of documents that includes the following: the original
main document, the annexes, and all the versions, languages, and main document, the annexes, and all the versions, languages, and
formats that are subsequently generated. formats that are subsequently generated.
skipping to change at line 1042 skipping to change at line 1037
urn:lex:es:tribunal.supremo:decision:2001-09-28;68 urn:lex:es:tribunal.supremo:decision:2001-09-28;68
urn:lex:fr:assemblee.nationale:proposition.loi:13.legislature;1762 urn:lex:fr:assemblee.nationale:proposition.loi:13.legislature;1762
urn:lex:br:estado:constituicao:1988-10-05;lex-1 urn:lex:br:estado:constituicao:1988-10-05;lex-1
urn:lex:un.org:united.nations;general.assembly:resolution: urn:lex:un.org:united.nations;general.assembly:resolution:
1961-11-28;a-res-1661 1961-11-28;a-res-1661
urn:lex:nl:hoge.raad:besluit:2008-04-01;bc8581 urn:lex:nl:hoge.raad:besluit:2008-04-01;bc8581
The type of measure is important to identify case law and The type of measure is important to identify case law and
legislation, especially within legal systems where cases are legislation, especially within legal systems where cases are
traditionally identified only through the year of release and a traditionally identified only through the year of release and a
number. Since the aim of the lex schema is to identify specific number. Since the aim of the LEX schema is to identify specific
materials, the type of measure or the full date are able to materials, the type of measure or the full date are able to
differentiate between materials belonging to a specific case. differentiate between materials belonging to a specific case.
The following is an example where the type of measure or the full The following is an example where the type of measure or the full
date are essential for identify specific materials of a case: date are essential for identify specific materials of a case:
* 4/59 Judgment of the EEC Court of Justice 04/04/1960, Mannesmann * 4/59 Judgment of the EEC Court of Justice 04/04/1960, Mannesmann
AG and others / ECSC High Authority AG and others / ECSC High Authority
urn:lex:eec.lex.arpa:court.justice:judgement:1960-04-04;4-59 urn:lex:eec.lex.arpa:court.justice:judgement:1960-04-04;4-59
skipping to change at line 1157 skipping to change at line 1152
To identify a specific manifestation, the uniform name of the To identify a specific manifestation, the uniform name of the
expression is followed by a suitable suffix containing the following expression is followed by a suitable suffix containing the following
main elements: main elements:
editor: Editorial staff who produced it, expressed according to the editor: Editorial staff who produced it, expressed according to the
publisher's Internet domain name. Since publishers' domain names publisher's Internet domain name. Since publishers' domain names
may vary over time, manifestations already assigned by a publisher may vary over time, manifestations already assigned by a publisher
remain unchanged, even if the identified object is no longer remain unchanged, even if the identified object is no longer
accessible. In this case, in order to make its materials accessible. In this case, in order to make its materials
accessible, the publisher will have to create a new manifestation accessible, the publisher will have to create a new manifestation
with a new domain name for each of them. with a new domain name for each object.
format: The digital format (e.g., XML, HTML, PDF, etc.) expressed format: The digital format (e.g., XML, HTML, PDF, etc.) expressed
according to the MIME Content-Type standard [RFC2045], where the according to the MIME Content-Type standard [RFC2045], where the
"/" character is to be substituted with the "-" sign. "/" character is to be substituted with the "-" sign.
component: Possible components of the expressions contained in the component: Possible components of the expressions contained in the
manifestation. Such components are expressed by language- manifestation. Such components are expressed by language-
dependent labels representing the whole document (in English dependent labels representing the whole document (in English
"all"), the main part of the document (in English "body"), or the "all"), the main part of the document (in English "body"), or the
caption label of the component itself (e.g., Table 1, Figure 2, caption label of the component itself (e.g., Table 1, Figure 2,
skipping to change at line 1180 skipping to change at line 1175
feature: Other features of the document (e.g., anonymized decision feature: Other features of the document (e.g., anonymized decision
text). text).
Thus, the manifestation suffix reads: Thus, the manifestation suffix reads:
manifestation = editor ":" format manifestation = editor ":" format
[":" component [":" feature]] [":" component [":" feature]]
To indicate possible features or peculiarities, each main element of To indicate possible features or peculiarities, each main element of
the manifestation MAY be followed by further specifications the manifestation MAY be followed by further specifications
(separated by ";"), for example as regards editor the archive name (separated by ";"), for example, the archive name and electronic
and the electronic publisher, for format the version, etc. publisher for the editor and the version for format. Therefore, the
Therefore, the main elements of the manifestation will assume the main elements of the manifestation will assume the following forms:
following forms:
editor = publisher *(";" specification) editor = publisher *(";" specification)
format = mime *(";" specification) format = mime *(";" specification)
component = part *(";" specification) component = part *(";" specification)
feature = attribute *(";" specification) feature = attribute *(";" specification)
The syntax details of the manifestation element are shown in The syntax details of the manifestation element are shown in
Section 8 in the related part. Section 8 in the related part.
The following are hypothetical examples: The following are hypothetical examples:
* The original version of the Italian act 3 April 2000, n. 56 might * The original version of the Italian act 3 April 2000, n. 56 might
have the following manifestations with their relative uniform have the following manifestations with their relative uniform
names: names:
- PDF format (vers. 1.7) of the whole act edited by the Italian - PDF format (vers. 1.7) of the whole act edited by the Italian
Parliament: Parliament:
urn:lex:it:stato:legge:2000-04-03;56$application-pdf; urn:lex:it:stato:legge:2000-04-03;56$parlamento.it:
1.7:parlamento.it application-pdf;1.7
- XML format (version 2.2 DTD NIR) of the text of the act and PDF - XML format (version 2.2 DTD NIR) of the text of the act and PDF
format (version 1.7) of the "Figura 1" (figure 1) contained in format (version 1.7) of the "Figura 1" (figure 1) contained in
the body, edited by the Italian Senate: the body, edited by the Italian Senate:
urn:lex:it:stato:legge:2000-04-03;56$text-xml;dtd-nir-2.2: urn:lex:it:stato:legge:2000-04-03;56$senato.it:text-xml;
senato.it:testo dtd-nir-2.2:testo
urn:lex:it:stato:legge:2000-04-03;56$application-pdf;1.7: urn:lex:it:stato:legge:2000-04-03;56$senato.it:
senato.it:figura.1 application-pdf;1.7:figura.1
* The Spanish URN of the HTML format of the whole Judgment of the * The Spanish URN of the HTML format of the whole Judgment of the
European Court of Justice n. 33/08 of 11/06/2009, in Spanish European Court of Justice n. 33/08 of 11/06/2009, in Spanish
version, published in the Jurifast database in anonymized form: version, published in the Jurifast database in anonymized form:
urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08 urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
@original:es$text-html:juradmin.eu;jurifast:todo:anonimo @original:es$juradmin.eu;jurifast:text-html:todo:anonimo
It is useful to be able to assign a uniform name to a manifestation It is useful to be able to assign a uniform name to a manifestation
(or to a part of it) in case non-textual objects are involved. These (or to a part of it) in case non-textual objects are involved. These
may be multimedia objects that are non-textual in their own right may be multimedia objects that are non-textual in their own right
(e.g., geographic maps, photographs, etc.) or texts recorded in non- (e.g., geographic maps, photographs, etc.) or texts recorded in non-
textual formats (e.g., image scans of documents). textual formats (e.g., image scans of documents).
5.8. Sources of Law References 5.8. Sources of Law References
References to sources of law often refer to specific partitions of References to sources of law often refer to specific partitions of
skipping to change at line 1277 skipping to change at line 1274
character of URI fragment, which is not transmitted to the server. character of URI fragment, which is not transmitted to the server.
According to these requirements, the syntax of a reference is: According to these requirements, the syntax of a reference is:
URN-reference = URN-document ["~" partition-id] URN-reference = URN-document ["~" partition-id]
For example, referring to paragraph 3 of article 15 of the French Act For example, referring to paragraph 3 of article 15 of the French Act
of 15 May 2004, n. 106, the reference can be of 15 May 2004, n. 106, the reference can be
"urn:lex:fr:etat:loi:2004-05-15;106~art15;par3". "urn:lex:fr:etat:loi:2004-05-15;106~art15;par3".
Using a different separator ("~") from the document name, the If a different separator ("~") is used after the document name, the
partition ID is not withheld by the browser but is transmitted to the partition ID is not withheld by the browser but is transmitted to the
resolution process. If the partition syntax is compatible with the resolution process. If the partition syntax is compatible with the
media type used, this enables the resolver to retrieve (for example, media type used, this enables the resolver to retrieve (for example,
out of a database) only the referred partition; otherwise, the whole out of a database) only the referred partition; otherwise, the whole
act is returned. act is returned.
When resolving to HTTP, the resolver SHALL transform the partition ID When resolving to HTTP, the resolver SHALL transform the partition ID
to an appropriate internal reference (#) on the page or at the to an appropriate internal reference (#) on the page or at the
beginning if that point cannot be found. The transformation in the beginning if that point cannot be found. The transformation in the
URI fragment is obtained by appending the "#" character followed by URI fragment is obtained by appending the "#" character followed by
skipping to change at line 1360 skipping to change at line 1357
Depending on the kind of measure, the body within the issuing Depending on the kind of measure, the body within the issuing
authority is unambiguously determined (e.g., the Council for Regional authority is unambiguously determined (e.g., the Council for Regional
Acts), and it is not normally indicated in the references. Just like Acts), and it is not normally indicated in the references. Just like
in practice, the indication of the enacting authority is limited to in practice, the indication of the enacting authority is limited to
the minimum in relation to the type of measure (e.g., the minimum in relation to the type of measure (e.g.,
"region.tuscany:act" and not "region.tuscany;council:act"). "region.tuscany:act" and not "region.tuscany;council:act").
6.1.5. Indication of the Function 6.1.5. Indication of the Function
Generally, the function is indicated, sometimes instead of the body Generally, the function is indicated, sometimes instead of the Body
itself: itself:
* In the case of political, representative, or elective offices * In the case of political, representative, or elective offices
(e.g., "university.oxford;rector:decree" instead of (e.g., "university.oxford;rector:decree" instead of
"university.oxford;rectorship:decree"). "university.oxford;rectorship:decree").
* When referring to a top officer in the institution (e.g., general * When referring to a top officer in the institution (e.g., general
manager, general secretary, etc.), which is not always possible to manager, general secretary, etc.), which is not always possible to
associate a specific internal institutional structure to (e.g., associate a specific internal institutional structure to (e.g.,
"national.council.research;general.manager"). "national.council.research;general.manager").
skipping to change at line 1470 skipping to change at line 1467
competence. In this case, the authority element is the same competence. In this case, the authority element is the same
(e.g., "ministry.justice:regulation;use.information.tools. (e.g., "ministry.justice:regulation;use.information.tools.
telematic.process" and "ministry.justice:decree"). telematic.process" and "ministry.justice:decree").
6.3. The Details Element 6.3. The Details Element
6.3.1. Indication of the Details 6.3.1. Indication of the Details
The details of a source of law usually include the date of the The details of a source of law usually include the date of the
enactment and the identification number (inclusion in the body of enactment and the identification number (inclusion in the body of
laws, register, protocol, etc.). laws, registry, protocol, etc.).
Some measures can have multiple dates. There are also cases in which Some measures can have multiple dates. There are also cases in which
the number of the measure does not exist (unnumbered measures) or a the number of the measure does not exist (unnumbered measures) or a
measure has multiple numbers (e.g., unified cases). For these measure has multiple numbers (e.g., unified cases). For these
reasons, the setup of both elements (date and number) includes reasons, the setup of both elements (date and number) includes
multiple values. multiple values.
Some institutions (e.g., the Parliaments) usually identify documents Some institutions (e.g., the Parliaments) usually identify documents
through their period of reference (e.g., the legislature number) through their period of reference (e.g., the legislature number)
rather than through a date, which would be much less meaningful and rather than through a date, which would be much less meaningful and
never used in references (e.g., Senate bill S.2544 of the XIV never used in references (e.g., Senate bill S.2544 of the XIV
legislature). In these cases, the component period is substitued for legislature). In these cases, the component period is substitued for
the component dates. the component dates.
Usually, details of a measure are not reported according to a Usually, details of a measure are not reported according to a
specific sequence. In accordance with the global structure of the specific sequence. In accordance with the global structure of the
uniform name, which goes from general to specific, the sequence date- uniform name, which goes from general to specific, the sequence date-
number has the following form: number has the following form:
details = (dates / period) ";" numbers details = (dates / period) ";" numbers
The following are examples: "2000-12-06;126" and The following are examples: "2000-12-06;126" and
"14.legislature;s.2544". "14.legislature;s.2544".
6.3.2. Multiple Dates 6.3.2. Multiple Dates
Some sources of law, even if unique, are identified by more than one Some sources of law, even if unique, are identified by more than one
date. In this case, all the given dates are to be reported and date. In this case, all the given dates are to be reported and
indicated as follows: indicated as follows:
dates = date *("," date) dates = date *("," date)
For example, the measure of the Data Protection Authority of December For example, the measure of the Data Protection Authority of December
30, 1999-January 13, 2000, No. 1/P/2000 has the following uniform 30, 1999-January 13, 2000, No. 1/P/2000 has the following uniform
name: name:
personal.data.protection.authority:measure:1999-12-30,2000-01- personal.data.protection.authority:measure:1999-12-30,2000-01-
13;1-p-2000 13;1-p-2000
As specified in Section 3.6, all the dates can have the date typical As specified in Section 3.6, all the dates can have the date typical
of the jurisdiction in addition to the ISO format. of the jurisdiction in addition to the ISO format.
skipping to change at line 1551 skipping to change at line 1548
an official publication, is preferred because it has the clear an official publication, is preferred because it has the clear
advantage of being public and is therefore easier to find. advantage of being public and is therefore easier to find.
6.3.4. Multiple Numbers 6.3.4. Multiple Numbers
Some legal documents (e.g., bills), even if unique, are identified by Some legal documents (e.g., bills), even if unique, are identified by
a set of numbers (e.g., the unification of cases or bills). In this a set of numbers (e.g., the unification of cases or bills). In this
case, in the numbers field, all the identifiers are reported, case, in the numbers field, all the identifiers are reported,
according to the following structure: according to the following structure:
numbers = document-id *("," document-id) number = document-id *("," document-id)
The following is an example: "2000-06-12;c-10-97,c-11-97,c-12-97". The following is an example: "2000-06-12;c-10-97,c-11-97,c-12-97".
The characters that are not allowed (e.g., "/") or reserved (e.g., The characters that are not allowed (e.g., "/") or reserved (e.g.,
":"), including the comma, cannot exist inside the document-id and ":"), including the comma, cannot exist inside the document-id and
therefore MUST be turned into "-". therefore MUST be turned into "-".
When special characters contained in the number of the act are When special characters contained in the number of the act are
distinctive of the act itself (e.g., bill n. 123-bis (removal of 123) distinctive of the act itself (e.g., bill n. 123-bis (removal of 123)
and n. 123/bis (return of 123)) and would disappear with the and n. 123/bis (return of 123)) and would disappear with the
skipping to change at line 1678 skipping to change at line 1675
* The date that the communication of the rectification or errata * The date that the communication of the rectification or errata
corrige was published. corrige was published.
* A specification that must identify the reason concerning the * A specification that must identify the reason concerning the
amendment (e.g., the specific phase of the legislative process), amendment (e.g., the specific phase of the legislative process),
for the cases in which the date is not usually used (e.g., bills). for the cases in which the date is not usually used (e.g., bills).
It is possible to add further specifications that will distinguish It is possible to add further specifications that will distinguish
each of the different versions of the text to guarantee identifier each of the different versions of the text to guarantee identifier
unequivocalness. For example with regard to changes of the in-force unequivocalness. Examples include changes of the in-force or
or effectiveness of any partition or portion of the text itself effectiveness of a formal partition or portion of the text itself
(e.g., when the amendments introduced by an act are applied at (e.g., when the amendments introduced by an act are applied at
different times) or different events occurring on the same date. different times) or different events occurring on the same date.
version = (amendment-date / specification) version = (amendment-date / specification)
*(";" (event-date / event)) *(";" (event-date / event))
where: where:
amendment-date: Contains the issuing date of the last considered amendment-date: Contains the issuing date of the last considered
amendment or of the last communication of amendment. If the amendment or of the last communication of amendment. If the
skipping to change at line 1714 skipping to change at line 1711
The issuing date of an amending act was chosen as the identifier of a The issuing date of an amending act was chosen as the identifier of a
version because it can be obtained from the heading (formal data). version because it can be obtained from the heading (formal data).
For example, the name "state:royal.decree:1941-01-30;12@1998-02-19" For example, the name "state:royal.decree:1941-01-30;12@1998-02-19"
identifies the updated text of the "Royal Decree of 30/1/1941, No. identifies the updated text of the "Royal Decree of 30/1/1941, No.
12" with the amendments introduced by the "Law Decree of 19/2/1998, 12" with the amendments introduced by the "Law Decree of 19/2/1998,
No. 51" without any indication of its actual entry into force. The No. 51" without any indication of its actual entry into force. The
same uniform name with the additional ending ";1999-01-01" indicates same uniform name with the additional ending ";1999-01-01" indicates
the in-force or effective version starting on a different date the in-force or effective version starting on a different date
(1/1/99). (1/1/99).
For full compatibility, every update of text or of the effectiveness For full compatibility, every update of text, or of the
of a "multi-version" document implies the creation of a new uniform effectiveness, of a "multi-version" document implies the creation of
name, even if the object remains only one, containing the identifier a new uniform name, even if the object remains single, containing the
of the virtually generated version, exactly as in the case of a identifier of the virtually generated version, as in the case of a
"single-version" document. Specific metadata will associate every "single-version" document. Specific metadata will associate every
uniform name with the period of time during which such a name, uniform name with the period of time during which such a name,
together with its corresponding text, is to be considered valid together with its corresponding text, is to be considered valid
(e.g., the "multi-version" document containing "R.D. of 01/30/1941, (e.g., the "multi-version" document containing "R.D. of 01/30/1941,
no. 12", updated by the amendments introduced by the "D.Lgs. of no. 12", updated by the amendments introduced by the "D.Lgs. of
02/19/1998, no. 51", contains the name of the original version 02/19/1998, no. 51", contains the name of the original version
"state:royal.decree:1941-01-30;12" as well as the name of the updated "state:royal.decree:1941-01-30;12" as well as the name of the updated
version "state:royal.decree:1941-01-30;12@1998-02-19"). version "state:royal.decree:1941-01-30;12@1998-02-19").
Note that if there are attachments or annexes, the creation of a new Note that if there are attachments or annexes, the creation of a new
version (even in the case of only one component) would imply the version (even in the case of only one component) would imply the
creation of a new uniform name for all the connected objects in order creation of a new uniform name for all the connected objects in order
to guarantee their alignment (i.e., the main document, attachments, to guarantee their alignment (i.e., the main document, attachments,
and annexes). and annexes).
As specified in Section 3.6, all the dates can have the date typical As specified in Section 3.6, all the dates can have the date typical
of the jurisdiction in addition to the date in ISO format. of the jurisdiction in addition to the date in ISO format.
8. Summary of the Syntax of the Uniform Names of the "lex" Namespace 8. Summary of the Syntax of the Uniform Names of the LEX Namespace
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of a Uniform Resource Name (URN) of the "lex" namespace ; Structure of a Uniform Resource Name (URN) of the LEX namespace
; - NID-lex = namespace ; - NID = LEX namespace identifier
; - NSS-lex = specific name ; - NSS = LEX Namespace Specific String
;------------------------------------------------------------------- ;-------------------------------------------------------------------
URN-lex = "urn:" NID-lex ":" NSS-lex URN = "urn:" NID ":" NSS
NID-lex = "lex" NID = "lex"
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of a "lex" specific name ; Structure of a LEX specific name
;------------------------------------------------------------------- ;-------------------------------------------------------------------
NSS-lex = jurisdiction ":" local-name NSS = jurisdiction ":" local-name
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the jurisdiction element ; Structure of the jurisdiction element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
jurisdiction = jurisdiction-code *(";" jurisdiction-unit) jurisdiction = jurisdiction-code *(";" jurisdiction-unit)
jurisdiction-code = 2*alf-dot jurisdiction-code = 2*alf-dot
jurisdiction-unit = alf-dot jurisdiction-unit = alf-dot
skipping to change at line 1810 skipping to change at line 1807
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the details element ; Structure of the details element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
details = (dates / period) ";" numbers details = (dates / period) ";" numbers
dates = date *("," date) dates = date *("," date)
period = alf-dot period = alf-dot
numbers = (document-id *("," document-id)) / number-lex numbers = number / number-lex
number = (document-id *("," document-id))
document-id = alf-dot-oth document-id = alf-dot-oth
number-lex = "lex-" 1*DIGIT number-lex = "lex-" 1*DIGIT
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the annex element ; Structure of the annex element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
annex = annex-id *(";" specification) annex = annex-id *(";" specification)
skipping to change at line 1835 skipping to change at line 1834
; Structure of the expression element ; Structure of the expression element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
expression = version [":" language] expression = version [":" language]
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the version element ; Structure of the version element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
version = (amendment-date / specification) version = (amendment-date / specification)
*(";" (event-date / event)) *(";" (event-date / event))
amendment-date = date amendment-date = date
event-date = date event-date = date
event = alf-dot event = alf-dot
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the language element ; Structure of the language element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
language = 2*3alfa *["-" extlang] / 4*8alfa language = 2*3alfa *["-" extlang] / 4*8alfa
extlang = 3alfa *2("-" 3alfa) extlang = 3alfa *2("-" 3alfa)
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the manifestation element ; Structure of the manifestation element
;------------------------------------------------------------------- ;-------------------------------------------------------------------
manifestation = format ":" editor manifestation = editor ":" format
[":" component [":" feature]] [":" component [":" feature]]
format = mime *(";" specification)
mime = alf-dot-hyp
editor = publisher *(";" specification) editor = publisher *(";" specification)
publisher = alf-dot-hyp publisher = alf-dot-hyp
format = mime *(";" specification)
mime = alf-dot-hyp
component = part *(";" specification) component = part *(";" specification)
part = alf-dot-hyp part = alf-dot-hyp
feature = attribute *(";" specification) feature = attribute *(";" specification)
attribute = alf-dot-hyp attribute = alf-dot-hyp
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Structure of the date ; Structure of the date
;------------------------------------------------------------------- ;-------------------------------------------------------------------
date = date-iso ["|" date-loc] date = date-iso ["|" date-loc]
date-iso = year "-" month "-" day date-iso = year "-" month "-" day
year = 4DIGIT year = 4DIGIT
month = 2DIGIT month = 2DIGIT
day = 2DIGIT
day = 2DIGIT
date-loc = *(alfadot / other) date-loc = *(alfadot / other)
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; Allowed, reserved, and future characters ; Allowed, reserved and future characters
;------------------------------------------------------------------- ;-------------------------------------------------------------------
; - allowed = alfadot / other / reserved ; - allowed = alfadot / other / reserved
; - reserved = ":" / "@" / "$" / "+" / "|" / ";" / "," / "~" ; - reserved = ":" / "@" / "$" / "+" / "|" / ";" / "," / "~"
; - future = "*" / "!" ; - future = "*" / "!"
alf-dot = alfanum *alfadot alf-dot = alfanum *alfadot
alf-dot-hyp = alfanum *(alfadot / "-") alf-dot-hyp = alfanum *(alfadot / "-")
alf-dot-oth = alfanum *(alfadot / other) alf-dot-oth = alfanum *(alfadot / other)
alfadot = alfanum / "." alfadot = alfanum / "."
alfa = lowercase / uppercase alfa = lowercase / uppercase
alfanum = alfa / DIGIT / encoded alfanum = alfa / DIGIT / encoded
skipping to change at line 1922 skipping to change at line 1924
encoded = "%" 2HEXDIG encoded = "%" 2HEXDIG
HEXDIG = DIGIT / %x41-46 / %x61-66 ; hex digits (0-9,A-F,a-f) HEXDIG = DIGIT / %x41-46 / %x61-66 ; hex digits (0-9,A-F,a-f)
other = "-" / "_" / "'" / "=" / "(" / ")" other = "-" / "_" / "'" / "=" / "(" / ")"
9. Procedure of Uniform Names Assignment 9. Procedure of Uniform Names Assignment
9.1. Specifying the Jurisdiction Element of the LEX Identifier 9.1. Specifying the Jurisdiction Element of the LEX Identifier
Under the "lex" namespace, each country or international organization Under the LEX namespace, each country or international organization
is assigned a jurisdiction code, which characterizes the URNs of the is assigned a jurisdiction-code, which characterizes the URNs of the
source of law of that country or jurisdiction. This code is assigned source of law of that country or jurisdiction. This code is assigned
according to ccTLD (as well as TLDN (Top-Level Domain Name) or DN according to ccTLD (as well as TLDN (Top-Level Domain Name) or DN
(Domain Name) for organizations) representation, and it is the value (Domain Name) for organizations) representation, and it is the value
of the jurisdiction-code element, which preserves cross-country of the jurisdiction-code element, which preserves cross-country
uniqueness of the identifiers. uniqueness of the identifiers.
9.2. Jurisdictional Registrar for Names Assignment 9.2. Jurisdictional Registrar for Names Assignment
Any country or jurisdiction that intends to adopt this schema MUST Any country or jurisdiction that intends to adopt this schema MUST
identify a Jurisdictional Registrar, an organization that shares and identify a Jurisdictional Registrar, an organization that shares and
defines the structure of the optional part (jurisdiction-unit) of the defines the structure of the optional part (jurisdiction-unit) of the
name, according to the organization of the state or institution (for name, according to the organization of the state or institution (for
details, see Section 2.2). It must appoint a Jurisdictional details, see Section 2.2). It must appoint a Jurisdictional
Registrar and inform the Designed Experts, together with the Registrar and must apply the Designated Experts to register the new
registration of a jurisdiction code. For example, in a federal jurisdiction-code.
state, a jurisdiction-unit corresponding to the name of each member
state (e.g., "br;sao.paulo", "br;minas.gerais", etc.) may be defined. For example, in a federal state, a jurisdiction-unit corresponding to
the name of each Member State (e.g., "br;sao.paulo",
"br;minas.gerais", etc.) may be defined.
The process of assigning the local-name is managed by each specific The process of assigning the local-name is managed by each specific
country or jurisdiction under the related jurisdiction element. country or jurisdiction under the related jurisdiction element.
In any country, the Jurisdictional Registrar shares and defines the In any country, the Jurisdictional Registrar shares and defines the
assignment of the primary elements (issuing authority and type of assignment of the primary elements (issuing authority and type of
legal measure) of the local names considering the characteristics of legal measure) of the local-names considering the characteristics of
its own state or institution organization. its own state or institution organization.
The Jurisdictional Registrar MUST establish, according to the The Jurisdictional Registrar MUST establish, according to the
guidelines indicated in this document, a uniform procedure within the guidelines indicated in this document, a uniform procedure within the
country or organization to define local-name elements, make decisions country or organization to define local-name elements, make decisions
about normalizations, solve and avoid possible name collisions, and about normalizations, solve and avoid possible name collisions, and
maintain authoritative registries of various kinds (e.g., for maintain authoritative registries of various kinds (e.g., for
authorities, types of measures, etc.). In particular, accurate authorities, types of measures, etc.). In particular, accurate
point-in-time representations of the structure and naming of point-in-time representations of the structure and naming of
government entities are important to semantically aware applications government entities are important to semantically aware applications
in this domain. in this domain.
Moreover, the Jurisdictional Registrar shares and defines the rules Moreover, the Jurisdictional Registrar shares and defines the rules
to construct partition IDs for each document type, possibly in to construct partition IDs for each document type, possibly in
accordance with those already defined in other jurisdictions. accordance with those already defined in other jurisdictions.
Finally, the Jurisdictional Registrar will develop and publish the Finally, the Jurisdictional Registrar will develop and publish the
rules and guidelines for the local-name construction as well as the rules and guidelines for the local-name construction as well as the
predefined values and codes. The Jurisdictional Registrar should predefined values and codes. The Jurisdictional Registrar should
also promote the urn:lex identifier for the sources of law of its also promote the LEX URN identifier for the sources of law of its
jurisdiction. jurisdiction.
Such a set of rules will have to be followed by all institutional Such a set of rules will have to be followed by all institutional
bodies adopting the URN LEX identification system in a country or bodies adopting the LEX URN identification system in a country or
jurisdiction, as well as by private publishers. Each of them will be jurisdiction, as well as by private publishers. Each of them will be
responsible for assigning names to their domains. responsible for assigning names to their domains.
9.3. Identifier Uniqueness 9.3. Identifier Uniqueness
Identifiers in the "lex" namespace are defined through a jurisdiction Identifiers in the LEX namespace are defined through a jurisdiction
element assigned to the sources of law of a specific country or element assigned to the sources of law of a specific country or
organization, and a local-name is assigned by the issuing authority organization, and a local-name is assigned by the issuing authority
in conformance with the syntax defined in Section 5. The main in conformance with the syntax defined in Section 5. The main
elements (authority and type of measure) of the local-name are elements (authority and type of measure) of the local-name are
defined by the Jurisdictional Registrar, so that it is ensured that defined by the Jurisdictional Registrar, so that it is ensured that
the constructed URNs are unique. The Jurisdictional Registrar MUST the constructed URNs are unique. The Jurisdictional Registrar MUST
provide clear documentation of rules by which names are to be provide clear documentation of rules by which names are to be
constructed and MUST update its registries and make them accessible. constructed and MUST update its registries and make them accessible.
Any enacting authority is responsible for defining formal parameters Any enacting authority is responsible for defining formal parameters
to guarantee local name uniqueness by attributing, if necessary, a to guarantee local-name uniqueness by attributing, if necessary, a
conventional internal number, which when combined with the other conventional internal number, which when combined with the other
local-name components (authority, measure, and date), builds a unique local-name components (authority, measure, and date), builds a unique
identifier. Uniqueness is achieved by checking against the catalogue identifier. Uniqueness is achieved by checking against the catalogue
of previously assigned names. of previously assigned names.
9.4. Identifier Persistence Considerations 9.4. Identifier Persistence Considerations
The persistence of identifiers depends on the durability of the The persistence of identifiers depends on the durability of the
institutions that assign and administer them. The goal of the LEX institutions that assign and administer them. The goal of the LEX
schema is to maintain uniqueness and persistence of all resources schema is to maintain uniqueness and persistence of all resources
skipping to change at line 2036 skipping to change at line 2040
from national scope down to very local scope, MUST equally take from national scope down to very local scope, MUST equally take
responsibility for the persistence of identifiers within their scope. responsibility for the persistence of identifiers within their scope.
10. Recommendations for the Resolution Process 10. Recommendations for the Resolution Process
10.1. General Architecture of the System 10.1. General Architecture of the System
The task of the resolution service is to associate a LEX identifier The task of the resolution service is to associate a LEX identifier
with a specific document address on the Internet. In contrast with with a specific document address on the Internet. In contrast with
systems that can be constructed around rigorous and enforceable systems that can be constructed around rigorous and enforceable
engineering premises, such as DNS, the "lex" namespace resolver will engineering premises, such as DNS, the LEX namespace resolver will be
be expected to cope with a wide variety of inputs that are incomplete expected to cope with a wide variety of inputs that are incomplete or
or partially incorrect, particularly those created by the automated partially incorrect, particularly those created by the automated
extraction of references from texts. In this document, the result is extraction of references from texts. In this document, the result is
a particular emphasis on a flexible and robust resolver design. a particular emphasis on a flexible and robust resolver design.
The system has a distributed architecture based on two fundamental The system has a distributed architecture based on two fundamental
components: a chain of information in the DNS and a series of components: a chain of information in the DNS and a series of
resolution services from URNs to URLs, each competent within a resolution services from URNs to URLs, each competent within a
specific domain of the namespace. specific domain of the namespace.
The client retrieves the document associated with this URN using the The client retrieves the document associated with this URN using the
procedure described in [RFC3404], which starts with a DNS NAPTR procedure described in [RFC3404], which starts with a DNS NAPTR
query. query.
A resolution service can delegate the resolution and management of A resolution service can delegate the resolution and management of
hierarchically dependent portions of the name. Delegation of this hierarchically dependent portions of the name. Delegation of this
responsibility will not be unreasonably withheld provided that the responsibility will not be unreasonably withheld provided that the
processes for their resolution and management are robust and processes for their resolution and management are robust and
followed. followed.
For the "lex" namespace, CNR will 1) maintain the root zone of the For the LEX namespace, CNR will 1) maintain the root zone of the
chain resolution, equivalent to "lex.urn.arpa" (see [RFC3405]), in chain resolution, equivalent to "lex.urn.arpa" (see [RFC3405]), in
the lex-nameserver.nic.it (see Section 12) and 2) update the DNS the lex-nameserver.nic.it (see Section 12) and 2) update the DNS
information with a new record to delegate the relative resolution in information with a new record to delegate the relative resolution
correspondence with the adhesion (see Section 2.2) of a new country when a new country (e.g., "br") or organization is added (see
(e.g., "br") or organization. This may be obtained by a regular Section 2.2). This delegation may be obtained by a regular
expression that matches the initial part of the URN (e.g., expression that matches the initial part of the URN (e.g.,
"urn:lex:br") and redirects towards the proper zone (e.g., "urn:lex:br") and redirects towards the proper zone (e.g.,
"lex.senado.gov.br"). "lex.senado.gov.br").
Likewise, the institution responsible for the jurisdiction uniform Likewise, the institution responsible for the jurisdiction uniform
names (e.g., "urn:lex:br") has the task of managing the relative root names (e.g., "urn:lex:br") has the task of managing the relative root
in the DNS system (e.g., "lex.senado.gov.br" zone) and routing the in the DNS system (e.g., "lex.senado.gov.br" zone) and routing the
resolution towards its resolvers on the basis of parts of the uniform resolution towards its resolvers on the basis of parts of the uniform
names. In a similar way, it can delegate the resolution of country/ names. In a similar way, it can delegate the resolution of country/
organization sub-levels (e.g., "urn:lex:br;sao.paolo") towards the organization sub-levels (e.g., "urn:lex:br;sao.paolo") towards the
relative zone (e.g., "lex.sao-paolo.gov.br"). relative zone (e.g., "lex.sao-paolo.gov.br").
Such a DNS routing chain does not work for all the URN components Such a DNS routing chain does not work for all the URN components
containing percent-encoded characters. Therefore, when converting a containing percent-encoded characters. Therefore, when converting a
"lex" URN in UTF-8 code to a DNS query, clients MUST perform any LEX URN in UTF-8 code to a DNS query, clients MUST perform any
necessary punycode conversion [RFC5891] before sending the query. necessary punycode conversion [RFC5891] before sending the query.
The resolution service is made up of two elements: a knowledge base The resolution service is made up of two elements: a knowledge base
(consisting in a catalogue or a set of transformation rules) and (consisting in a catalogue or a set of transformation rules) and
software to query the knowledge base. software to query the knowledge base.
10.2. Catalogues for Resolution 10.2. Catalogues for Resolution
Incompleteness and inaccuracy are rather frequent in legal citations; Incompleteness and inaccuracy are rather frequent in legal citations;
thus, incomplete or inaccurate uniform names of the referred document thus, incomplete or inaccurate uniform names of the referred document
skipping to change at line 2112 skipping to change at line 2116
10.3. Suggested Resolver Behavior 10.3. Suggested Resolver Behavior
First, the resolver SHOULD separate the part corresponding to the First, the resolver SHOULD separate the part corresponding to the
partition ID from the document name, with the "~" separator. partition ID from the document name, with the "~" separator.
The resolution process SHOULD implement a normalization of the The resolution process SHOULD implement a normalization of the
uniform name to be resolved. This may involve transforming some uniform name to be resolved. This may involve transforming some
components to the canonical form (e.g., filling out the acronyms, components to the canonical form (e.g., filling out the acronyms,
expanding the abbreviations, unifying the institution names, expanding the abbreviations, unifying the institution names,
standardizing the type of measures, etc.). For this function, standardizing the type of measures, etc.). For this function,
authorities and types of measure registers are useful. authorities and types of measure registries are useful.
The resolver SHOULD then query the catalogue searching for the URN The resolver SHOULD then query the catalogue searching for the URN
that corresponds exactly to the given one (normalized if necessary). that corresponds exactly to the given one (normalized if necessary).
Since the names coming from the references may be inaccurate or Since the names coming from the references may be inaccurate or
incomplete, an iterative and heuristic approach (based on partial incomplete, an iterative and heuristic approach (based on partial
matches) is indicated. Incomplete references (not including all the matches) is indicated. Incomplete references (not including all the
elements to create the canonical uniform name) are normal and elements to create the canonical uniform name) are normal and
natural; for a human reader, the reference would be "completed" by natural; for a human reader, the reference would be "completed" by
contextual understanding of the reference in the document in which it contextual understanding of the reference in the document in which it
occurs. occurs.
skipping to change at line 2149 skipping to change at line 2153
Security considerations are those normally associated with the use Security considerations are those normally associated with the use
and resolution URNs in general. Additional security considerations and resolution URNs in general. Additional security considerations
concerning the authenticity of a document do not pertain to the LEX concerning the authenticity of a document do not pertain to the LEX
specifications, but they pertain to security and trust issues that specifications, but they pertain to security and trust issues that
can be addressed with other means, like digital signatures, data can be addressed with other means, like digital signatures, data
encryption, etc. encryption, etc.
12. IANA Considerations 12. IANA Considerations
IANA has registered "lex" namespace in the "Formal URN Namespaces" IANA has registered LEX namespace in the "Formal URN Namespaces"
registry [RFC8141]. registry [RFC8141].
In addition, to activate a distributed resolution system, IANA has In addition, to activate a distributed resolution system, IANA has
registered the following NAPTR record in the URN.ARPA domain: registered the following NAPTR record in the URN.ARPA domain:
lex.urn.arpa. lex.urn.arpa.
IN NAPTR 100 10 "" "" "" lex-nameserver.nic.it. IN NAPTR 100 10 "" "" "" lex-nameserver.nic.it.
Note that lex-nameserver.nic.it indicates the CNR server (see Note that lex-nameserver.nic.it indicates the CNR server (see
Section 2.2) that is responsible for the resolution of the "lex" Section 2.2) that is responsible for the resolution of the LEX
namespace at the time of this writing. namespace at the time of this writing.
13. References 13. References
13.1. Normative References 13.1. Normative References
[ISO.8601.1988] [ISO.8601-1.2019]
ISO, "Date and time - Representations for information
interchange", ISO 8601-1:2019, February 2019,
<https://www.iso.org/standard/70907.html>.
[ISO.8601-2.2019]
ISO, "Data elements and interchange formats - Information ISO, "Data elements and interchange formats - Information
interchange - Representation of dates and times", interchange - Representation of dates and times",
ISO 8601:1988, June 1988. ISO 8601-2:2019, February 2019,
<https://www.iso.org/standard/70908.html>.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996,
<https://www.rfc-editor.org/info/rfc2045>. <https://www.rfc-editor.org/info/rfc2045>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at line 2269 skipping to change at line 2279
<https://assets.hcch.net/docs/b093f152-a4b3-4530-949e- <https://assets.hcch.net/docs/b093f152-a4b3-4530-949e-
65c1bfc9cda1.pdf>. 65c1bfc9cda1.pdf>.
[ISBD] The Standing Committee of the IFLA Cataloguing Section [ISBD] The Standing Committee of the IFLA Cataloguing Section
Berlin/Munich: De Gruyter Saur, "ISBD: International Berlin/Munich: De Gruyter Saur, "ISBD: International
Standard Bibliographic Description – Consolidated Standard Bibliographic Description – Consolidated
Edition", ISBN 978-3-11-026379-4, 2011. Edition", ISBN 978-3-11-026379-4, 2011.
[ISO.3166-1] [ISO.3166-1]
ISO, "Codes for the representation of names of countries ISO, "Codes for the representation of names of countries
and their subdivisions - Part 1: Country codes". and their subdivisions - Part 1: Country codes, ISO
3166-1:2020, 2020.", 2020.
[LVI] Peruginelli, G., Ed. and M. Ragona, Ed., "Law via the [LVI] Peruginelli, G., Ed. and M. Ragona, Ed., "Law via the
Internet. Free Access, Quality of Information, Internet. Free Access, Quality of Information,
Effectiveness of Rights", ISBN 9788883980589, April 2009. Effectiveness of Rights", ISBN 9788883980589, April 2009.
[SART] Sartor, G., Palmirani, M., Francesconi, E., and M. [SART] Sartor, G., Palmirani, M., Francesconi, E., and M.
Biasiotti, "Legislative XML for the Semantic Web: Biasiotti, "Legislative XML for the Semantic Web:
Principles, Models, Standards for Document Management", Principles, Models, Standards for Document Management",
ISBN 978-94-007-1887-6, 2011. ISBN 978-94-007-1887-6, 2011.
[SPIN] Spinosa, P., "The Assignment of Uniform Names to Italian [SPIN] Spinosa, P., "Identification of Legal Documents through
Legal Documents, URN-NIR 1.4", ITTIG technical Report n. URNs (Uniform Resource Names)", Proceedings of the EuroWeb
8/2010, June 2020. 2001, The Web in Public Administration , 2001.
[W3C.RDF-SCHEMA] [W3C.RDF-SCHEMA]
Brickley, D., Ed. and R. Guha, Ed., "RDF Schema 1.1", W3C Brickley, D., Ed. and R. Guha, Ed., "RDF Schema 1.1", W3C
REC rdf-schema, W3C rdf-schema, February 2014, REC rdf-schema, W3C rdf-schema, February 2014,
<https://www.w3.org/TR/rdf-schema/>. <https://www.w3.org/TR/rdf-schema/>.
Acknowledgements Acknowledgements
The authors wish to thank all those who provided suggestions and The authors wish to thank all those who provided suggestions and
comments. comments.
 End of changes. 132 change blocks. 
285 lines changed or deleted 296 lines changed or added

This html diff was produced by rfcdiff 1.48.