rfc9676v6.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
April 2025 May 2025
LEX: A Uniform Resource Name (URN) Namespace for Sources of Law LEX: A Uniform Resource Name (URN) Namespace for Sources of Law
Abstract Abstract
This document describes LEX, a Uniform Resource Name (URN) namespace This document describes LEX, a Uniform Resource Name (URN) namespace
identifier that identifies, names, assigns, and manages persistent identifier that identifies, names, assigns, and manages persistent
resources in the legal domain. This specification allows adoption of resources in the legal domain. This specification allows adoption of
a common convention by multiple jurisdictions to facilitate ease of a common convention by multiple jurisdictions to facilitate ease of
reference and access to resources in the legal domain. reference and access to resources in the legal domain.
skipping to change at line 797 skipping to change at line 797
systems and there are several programs for mapping other formats to systems and there are several programs for mapping other formats to
this one. However, to make reading and understanding such other this one. However, to make reading and understanding such other
formats (e.g., Jewish calendar), the LEX URN scheme provides that the 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 date can be added in the jurisdiction's own format. The date in the
previous example (1999-09-02) would be as follows: previous example (1999-09-02) would be as follows:
* in Hebrew characters (21 Elul 5759): * in Hebrew characters (21 Elul 5759):
כ״א-בֶּאֱלוּל-תשנ״ט כ״א-בֶּאֱלוּל-תשנ״ט
where in direction of reading, the sequence of characters is "כ"
(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).
Note that the example above uses right-to-left (RTL) script, which Note that the example above uses right-to-left (RTL) script, which
in the context of this specification may be displayed differently in the context of this specification may be displayed differently
by different document presentation environments. The descriptive by different document presentation environments. The descriptive
text may be more reliable to follow than the necessarily device- text may be more reliable to follow than the necessarily device-
and application-specific rendering. and application-specific rendering.
* in U+ notation: * in U+ notation:
U+05D8U+05F4U+05E0U+05E9U+05EAU+002DU+05DCU+05D5U+05BCU+05DC U+05D8U+05F4U+05E0U+05E9U+05EAU+002DU+05DCU+05D5U+05BCU+05DC
U+05D0U+05B1U+05D1U+05B6U+05BCU+002DU+05D0U+05F4U+05DB U+05D0U+05B1U+05D1U+05B6U+05BCU+002DU+05D0U+05F4U+05DB
skipping to change at line 843 skipping to change at line 830
1999-09-02|כ״א-בֶּאֱלוּל-תשנ״ט 1999-09-02|כ״א-בֶּאֱלוּל-תשנ״ט
which is to be converted into UTF-8 for network protocols and for which is to be converted into UTF-8 for network protocols and for
resolution (see Section 3.4). The characters that are not allowed resolution (see Section 3.4). The characters that are not allowed
(e.g., "/") or reserved (e.g., ",") cannot exist inside the date-loc (e.g., "/") or reserved (e.g., ",") cannot exist inside the date-loc
and therefore MUST be turned into ".". To be aligned with ISO and therefore MUST be turned into ".". To be aligned with ISO
format, any blank between day, month, and year MUST be converted into 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.,
apostrophes, dashes, etc.) are eliminated (no transformation occurs apostrophes, dashes, etc.) are eliminated (no transformation occurs
 End of changes. 3 change blocks. 
14 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48.