Diff: rfc9676v4.txt - rfc9676.txt

	rfc9676v4.txt	rfc9676.txt

	skipping to change at line 749 ¶	skipping to change at line 749 ¶
	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 "München" (MU+00FCnchen)):	der Stadt "München" (MU+00FCnchen)):

	- ASCII: urn:lex:de:stadt.munchen:rundschreiben:...;	- ASCII: urn:lex:de:stadt.munchen:rundschreiben:...;
	- Unicode: urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...;	- Unicode: urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...;

	- UTF-8: urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben:...;	- UTF-8: urn:lex:de:stadt.m%C3%BCnchen:rundschreiben:...;
	- PUNYCODE: urn:lex:de:stadt.xn--mnchen-3ya: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: "состояние закон"	Cyrillic: "состояние закон"
	(U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435	(U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435
	U+0437U+0430U+043AU+043EU+043D)), assuming that the Russia	U+0437U+0430U+043AU+043EU+043D)), assuming that the Russia
	jurisdiction-code is expressed in ASCII ("ru") (while the Cyrillic	jurisdiction-code is expressed in ASCII ("ru") (while the Cyrillic
	version would be "рф" (U+0440U+0444)):	version would be "рф" (U+0440U+0444)):

	- ASCII: urn:lex:ru:gosudarstvo:zakon:...	- ASCII: urn:lex:ru:gosudarstvo:zakon:...
	- Unicode: urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D	- Unicode: urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D
	U+0438U+0435:U+0437U+0430U+043AU+043EU+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	- UTF-8: urn:lex:ru:%D1%81%D0%BE%D1%81%D1%82%D0%BE%D1
	%x8F%xD0%xBD%xD0%xB8%xD0%xB5:%xD0%xB7%xD0%xB0%xD0%xBA	%8F%D0%BD%D0%B8%D0%B5:%D0%B7%D0%B0%D0%BA
	%xD0%xBE%xD0%xBD:...	%D0%BE%D0%BD:...
	- PUNYCODE: urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme:...	- 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 = year "-" month "-" day	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. 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 ".". To be aligned with ISO
		format, any blank between day, month, and year MUST be converted 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.

	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 1179 ¶	skipping to change at line 1201 ¶
	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$parlamento.it:	urn:lex:it:stato:legge:2000-04-03;56$parlamento.it:

	application-pdf;1.7:	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$senato.it:text-xml;	urn:lex:it:stato:legge:2000-04-03;56$senato.it:text-xml;
	dtd-nir-2.2:testo	dtd-nir-2.2:testo
	urn:lex:it:stato:legge:2000-04-03;56$senato.it:	urn:lex:it:stato:legge:2000-04-03;56$senato.it:
	application-pdf;1.7:figura.1	application-pdf;1.7:figura.1


	skipping to change at line 2149 ¶	skipping to change at line 2171 ¶
	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>.

End of changes. 11 change blocks.
	17 lines changed or deleted	45 lines changed or added
This html diff was produced by rfcdiff 1.48.