rfc9676v4.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		February 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 794 ¶		skipping to change at line 794 ¶
	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. 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
			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 U+ notation:		* in U+ notation:
	U+05D8U+05F4U+05E0U+05E9U+05EAU+0020U+05DCU+05D5U+05BCU+05DC		U+05D8U+05F4U+05E0U+05E9U+05EAU+002DU+05DCU+05D5U+05BCU+05DC
	U+05D0U+05B1U+05D1U+05B6U+05BCU+0020U+05D0U+05F4U+05DB		U+05D0U+05B1U+05D1U+05B6U+05BCU+002DU+05D0U+05F4U+05DB
	* in UTF-8 code:		* in UTF-8 code:
	%d7%98%d7%b4%d7%a0%d7%a9%d7%aa%20%d7%9c%d7%95%d6%bc%d7%9c%d7		%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%20%d7%90%d7%b4%d7%9b		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		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, 1999-09-02 will be written in ISO plus Hebrew format as:		For example, 1999-09-02 will be written in ISO plus Hebrew format as:
	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 ".".		and therefore MUST be turned into ".".
	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.
End of changes. 5 change blocks.
	7 lines changed or deleted		26 lines changed or added
This html diff was produced by rfcdiff 1.48.