rfc9676.original.xml   rfc9676.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [ <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" do
<!ENTITY nbsp "&#160;"> cName="draft-spinosa-urn-lex-24" number="9676" updates="" obsoletes="" category=
<!ENTITY zwsp "&#8203;"> "info" submissionType="independent" tocInclude="true" xml:lang="en" symRefs="tru
<!ENTITY nbhy "&#8209;"> e" sortRefs="true" prepTime="2025-05-05T12:52:05" indexInclude="true" scripts="C
<!ENTITY wj "&#8288;"> ommon,Cyrillic,Hebrew,Latin" tocDepth="3">
]> <link href="https://datatracker.ietf.org/doc/draft-spinosa-urn-lex-24" rel="pr
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> ev"/>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.18 (Ruby 3.0. <link href="https://dx.doi.org/10.17487/rfc9676" rel="alternate"/>
2) --> <link href="urn:issn:2070-1721" rel="alternate"/>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-spinosa-urn-lex-24" category="info" submissionType="independent" version="3">
<!-- xml2rfc v2v3 conversion 3.22.0 -->
<front> <front>
<title abbrev="URN LEX Namespace for Sources of Law">A Uniform Resource Name <title abbrev="LEX: URN Namespace for Sources of Law">LEX: A Uniform Resourc
(URN) Namespace for Sources of Law (LEX)</title> e Name (URN) Namespace for Sources of Law</title>
<seriesInfo name="Internet-Draft" value="draft-spinosa-urn-lex-24"/> <seriesInfo name="RFC" value="9676" stream="independent"/>
<author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa"> <author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa">
<organization/>
<address> <address>
<postal> <postal>
<street>Via Zanardelli, 15</street> <street>Via Zanardelli, 15</street>
<city>Firenze</city> <city>Firenze</city>
<code>50136</code> <code>50136</code>
<country>Italy</country> <country>Italy</country>
</postal> </postal>
<phone>+39 339 5614056</phone> <phone>+39 339 5614056</phone>
<email>pierluigi.spinosa@gmail.com</email> <email>pierluigi.spinosa@gmail.com</email>
</address> </address>
</author> </author>
<author initials="E." surname="Francesconi" fullname="Enrico Franceseconi"> <author initials="E." surname="Francesconi" fullname="Enrico Franceseconi">
<organization>National Research Council of Italy (CNR)</organization> <organization showOnFrontPage="true">National Research Council of Italy (C NR)</organization>
<address> <address>
<postal> <postal>
<street>Via de' Barucci, 20</street> <street>Via de' Barucci, 20</street>
<city>Firenze</city> <city>Firenze</city>
<code>50127</code> <code>50127</code>
<country>Italy</country> <country>Italy</country>
</postal> </postal>
<phone>+39 055 43995</phone> <phone>+39 055 43995</phone>
<email>enrico.francesconi@cnr.it</email> <email>enrico.francesconi@cnr.it</email>
</address> </address>
</author> </author>
<author initials="C." surname="Lupo" fullname="Caterina Lupo"> <author initials="C." surname="Lupo" fullname="Caterina Lupo">
<organization/>
<address> <address>
<postal> <postal>
<street>Via San Fabiano, 25</street> <street>Via San Fabiano, 25</street>
<city>Roma</city> <city>Roma</city>
<code>117</code> <code>117</code>
<country>Italy</country> <country>Italy</country>
</postal> </postal>
<phone>+39 3382632348</phone> <phone>+39 3382632348</phone>
<email>caterina.lupo@gmail.com</email> <email>caterina.lupo@gmail.com</email>
</address> </address>
</author> </author>
<date year="2024" month="August" day="17"/> <date month="04" year="2025"/>
<abstract> <keyword>identifier for legal documents</keyword>
<?line 154?> <keyword>legislation</keyword>
<keyword>case law</keyword>
<t>This document describes a Uniform Resource Name (URN) Namespace <keyword>administrative acts</keyword>
Identifier for identifying, naming, assigning, <abstract pn="section-abstract">
and managing persistent resources in the legal domain. This <t indent="0" pn="section-abstract-1">This document describes LEX, a Unifo
specification is published to allow adoption of a common convention rm Resource Name (URN) namespace identifier
by multiple jurisdictions to facilitate ease of reference and access that identifies, names, assigns, and manages persistent resources in the
to resources in the legal domain.<br/> legal domain. This specification allows adoption of a common
This specification is an independent submission to the RFC series. convention by multiple jurisdictions to facilitate ease of reference and
It is not a standard, and does not have the consensus of the IETF.</t> access to resources in the legal domain.</t>
<t indent="0" pn="section-abstract-2">This specification is an Independent
Submission to the RFC Series. It is not a standard and does not have the
consensus of the IETF.</t>
</abstract> </abstract>
<boilerplate>
<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
"exclude" pn="section-boilerplate.1">
<name slugifiedName="name-status-of-this-memo">Status of This Memo</name
>
<t indent="0" pn="section-boilerplate.1-1">
This document is not an Internet Standards Track specification; it i
s
published for informational purposes.
</t>
<t indent="0" pn="section-boilerplate.1-2">
This is a contribution to the RFC Series, independently of any
other RFC stream. The RFC Editor has chosen to publish this
document at its discretion and makes no statement about its value
for implementation or deployment. Documents approved for
publication by the RFC Editor are not candidates for any level of
Internet Standard; see Section 2 of RFC 7841.
</t>
<t indent="0" pn="section-boilerplate.1-3">
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
<eref target="https://www.rfc-editor.org/info/rfc9676" brackets="non
e"/>.
</t>
</section>
<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
ude" pn="section-boilerplate.2">
<name slugifiedName="name-copyright-notice">Copyright Notice</name>
<t indent="0" pn="section-boilerplate.2-1">
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
</t>
<t indent="0" pn="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<eref target="https://trustee.ietf.org/license-info" brackets="none
"/>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document.
</t>
</section>
</boilerplate>
<toc>
<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" p
n="section-toc.1">
<name slugifiedName="name-table-of-contents">Table of Contents</name>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
c.1-1">
<li pn="section-toc.1-1.1">
<t indent="0" pn="section-toc.1-1.1.1"><xref derivedContent="1" form
at="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-introduction">Introduction</xref><
/t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.1.2">
<li pn="section-toc.1-1.1.2.1">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><
xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.
1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-th
e-purpose-of-namespace-le">The Purpose of Namespace LEX</xref></t>
</li>
<li pn="section-toc.1-1.1.2.2">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.1"><
xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.
2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ba
ckground">Background</xref></t>
</li>
<li pn="section-toc.1-1.1.2.3">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.3.1"><
xref derivedContent="1.3" format="counter" sectionFormat="of" target="section-1.
3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ge
neral-characteristics-of-">General Characteristics of the System</xref></t>
</li>
<li pn="section-toc.1-1.1.2.4">
<t indent="0" pn="section-toc.1-1.1.2.4.1"><xref derivedContent=
"1.4" format="counter" sectionFormat="of" target="section-1.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-linking-a-lex-name-to-
a-doc">Linking a LEX Name to a Document</xref></t>
</li>
<li pn="section-toc.1-1.1.2.5">
<t indent="0" pn="section-toc.1-1.1.2.5.1"><xref derivedContent=
"1.5" format="counter" sectionFormat="of" target="section-1.5"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-use-of-lex-names-in-re
feren">Use of LEX Names in References</xref></t>
</li>
<li pn="section-toc.1-1.1.2.6">
<t indent="0" pn="section-toc.1-1.1.2.6.1"><xref derivedContent=
"1.6" format="counter" sectionFormat="of" target="section-1.6"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-definitions">Definitio
ns</xref></t>
</li>
<li pn="section-toc.1-1.1.2.7">
<t indent="0" pn="section-toc.1-1.1.2.7.1"><xref derivedContent=
"1.7" format="counter" sectionFormat="of" target="section-1.7"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-terminology">Terminolo
gy</xref></t>
</li>
<li pn="section-toc.1-1.1.2.8">
<t indent="0" pn="section-toc.1-1.1.2.8.1"><xref derivedContent=
"1.8" format="counter" sectionFormat="of" target="section-1.8"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-syntax-used-in-this-do
cumen">Syntax Used in This Document</xref></t>
</li>
<li pn="section-toc.1-1.1.2.9">
<t indent="0" pn="section-toc.1-1.1.2.9.1"><xref derivedContent=
"1.9" format="counter" sectionFormat="of" target="section-1.9"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-namespace-registration
">Namespace Registration</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.2">
<t indent="0" pn="section-toc.1-1.2.1"><xref derivedContent="2" form
at="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-registration-of-lex">Registration
of LEX</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.2.2">
<li pn="section-toc.1-1.2.2.1">
<t indent="0" pn="section-toc.1-1.2.2.1.1"><xref derivedContent=
"2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-identifier-structure">
Identifier Structure</xref></t>
</li>
<li pn="section-toc.1-1.2.2.2">
<t indent="0" pn="section-toc.1-1.2.2.2.1"><xref derivedContent=
"2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-jurisdiction-code-regi
stry">Jurisdiction-Code Registry</xref></t>
</li>
<li pn="section-toc.1-1.2.2.3">
<t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent=
"2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-conformance-with-urn-s
yntax">Conformance with URN Syntax</xref></t>
</li>
<li pn="section-toc.1-1.2.2.4">
<t indent="0" pn="section-toc.1-1.2.2.4.1"><xref derivedContent=
"2.4" format="counter" sectionFormat="of" target="section-2.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-validation-mechanism">
Validation Mechanism</xref></t>
</li>
<li pn="section-toc.1-1.2.2.5">
<t indent="0" pn="section-toc.1-1.2.2.5.1"><xref derivedContent=
"2.5" format="counter" sectionFormat="of" target="section-2.5"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-scope">Scope</xref></t
>
</li>
</ul>
</li>
<li pn="section-toc.1-1.3">
<t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" form
at="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-general-syntax-and-features">Gener
al Syntax and Features of the LEX Identifier</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.3.2">
<li pn="section-toc.1-1.3.2.1">
<t indent="0" pn="section-toc.1-1.3.2.1.1"><xref derivedContent=
"3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-allowed-and-not-allowe
d-cha">Allowed and Not Allowed Characters</xref></t>
</li>
<li pn="section-toc.1-1.3.2.2">
<t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent=
"3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-reserved-characters">R
eserved Characters</xref></t>
</li>
<li pn="section-toc.1-1.3.2.3">
<t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent=
"3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-case-sensitivity">Case
Sensitivity</xref></t>
</li>
<li pn="section-toc.1-1.3.2.4">
<t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent=
"3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-unicode-characters-out
side-">Unicode Characters Outside the ASCII Range</xref></t>
</li>
<li pn="section-toc.1-1.3.2.5">
<t indent="0" pn="section-toc.1-1.3.2.5.1"><xref derivedContent=
"3.5" format="counter" sectionFormat="of" target="section-3.5"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-abbreviations">Abbrevi
ations</xref></t>
</li>
<li pn="section-toc.1-1.3.2.6">
<t indent="0" pn="section-toc.1-1.3.2.6.1"><xref derivedContent=
"3.6" format="counter" sectionFormat="of" target="section-3.6"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-date-format">Date Form
at</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.4">
<t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" form
at="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-specific-syntax-and-feature">Speci
fic Syntax and Features of the LEX Identifier</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.4.2">
<li pn="section-toc.1-1.4.2.1">
<t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent=
"4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-spaces-connectives-and
-punc">Spaces, Connectives, and Punctuation Marks</xref></t>
</li>
<li pn="section-toc.1-1.4.2.2">
<t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent=
"4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-acronyms">Acronyms</xr
ef></t>
</li>
<li pn="section-toc.1-1.4.2.3">
<t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent=
"4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-ordinal-numbers">Ordin
al Numbers</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.5">
<t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" form
at="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-creation-of-the-source-of-l">Creat
ion of the Source of Law LEX Identifier: Baseline Structure</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.5.2">
<li pn="section-toc.1-1.5.2.1">
<t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent=
"5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-basic-principles">Basi
c Principles</xref></t>
</li>
<li pn="section-toc.1-1.5.2.2">
<t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent=
"5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-model-of-sources-of-la
w-rep">Model of Sources of Law Representation</xref></t>
</li>
<li pn="section-toc.1-1.5.2.3">
<t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent=
"5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-structure-of-the-local
-name">Structure of the Local-Name</xref></t>
</li>
<li pn="section-toc.1-1.5.2.4">
<t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent=
"5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-structure-of-the-docum
ent-i">Structure of the Document Identifier at "Work" Level</xref></t>
</li>
<li pn="section-toc.1-1.5.2.5">
<t indent="0" pn="section-toc.1-1.5.2.5.1"><xref derivedContent=
"5.5" format="counter" sectionFormat="of" target="section-5.5"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-aliases">Aliases</xref
></t>
</li>
<li pn="section-toc.1-1.5.2.6">
<t indent="0" pn="section-toc.1-1.5.2.6.1"><xref derivedContent=
"5.6" format="counter" sectionFormat="of" target="section-5.6"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-structure-of-the-docum
ent-id">Structure of the Document Identifier at "Expression" Level</xref></t>
</li>
<li pn="section-toc.1-1.5.2.7">
<t indent="0" pn="section-toc.1-1.5.2.7.1"><xref derivedContent=
"5.7" format="counter" sectionFormat="of" target="section-5.7"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-structure-of-the-docum
ent-ide">Structure of the Document Identifier at "Manifestation" Level</xref></t
>
</li>
<li pn="section-toc.1-1.5.2.8">
<t indent="0" pn="section-toc.1-1.5.2.8.1"><xref derivedContent=
"5.8" format="counter" sectionFormat="of" target="section-5.8"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-sources-of-law-referen
ces">Sources of Law References</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.6">
<t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" form
at="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-specific-syntax-of-the-iden">Speci
fic Syntax of the Identifier at "Work" Level</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.6.2">
<li pn="section-toc.1-1.6.2.1">
<t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent=
"6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-the-authority-element"
>The Authority Element</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.6.2.1.2">
<li pn="section-toc.1-1.6.2.1.2.1">
<t indent="0" pn="section-toc.1-1.6.2.1.2.1.1"><xref derived
Content="6.1.1" format="counter" sectionFormat="of" target="section-6.1.1"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-indication
-of-the-authority">Indication of the Authority</xref></t>
</li>
<li pn="section-toc.1-1.6.2.1.2.2">
<t indent="0" pn="section-toc.1-1.6.2.1.2.2.1"><xref derived
Content="6.1.2" format="counter" sectionFormat="of" target="section-6.1.2"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-multiple-i
ssuers">Multiple Issuers</xref></t>
</li>
<li pn="section-toc.1-1.6.2.1.2.3">
<t indent="0" pn="section-toc.1-1.6.2.1.2.3.1"><xref derived
Content="6.1.3" format="counter" sectionFormat="of" target="section-6.1.3"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-indication
-of-the-issuer">Indication of the Issuer</xref></t>
</li>
<li pn="section-toc.1-1.6.2.1.2.4">
<t indent="0" pn="section-toc.1-1.6.2.1.2.4.1"><xref derived
Content="6.1.4" format="counter" sectionFormat="of" target="section-6.1.4"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-indication
-of-the-body">Indication of the Body</xref></t>
</li>
<li pn="section-toc.1-1.6.2.1.2.5">
<t indent="0" pn="section-toc.1-1.6.2.1.2.5.1"><xref derived
Content="6.1.5" format="counter" sectionFormat="of" target="section-6.1.5"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-indication
-of-the-function">Indication of the Function</xref></t>
</li>
<li pn="section-toc.1-1.6.2.1.2.6">
<t indent="0" pn="section-toc.1-1.6.2.1.2.6.1"><xref derived
Content="6.1.6" format="counter" sectionFormat="of" target="section-6.1.6"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-convention
s-for-the-authori">Conventions for the Authority</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.6.2.2">
<t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent=
"6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-the-measure-element">T
he Measure Element</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.6.2.2.2">
<li pn="section-toc.1-1.6.2.2.2.1">
<t indent="0" pn="section-toc.1-1.6.2.2.2.1.1"><xref derived
Content="6.2.1" format="counter" sectionFormat="of" target="section-6.2.1"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-criteria-f
or-the-indication">Criteria for the Indication of the Type of Measure</xref></t>
</li>
<li pn="section-toc.1-1.6.2.2.2.2">
<t indent="0" pn="section-toc.1-1.6.2.2.2.2.1"><xref derived
Content="6.2.2" format="counter" sectionFormat="of" target="section-6.2.2"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-further-sp
ecification-to-th">Further Specification to the Type of Measure</xref></t>
</li>
<li pn="section-toc.1-1.6.2.2.2.3">
<t indent="0" pn="section-toc.1-1.6.2.2.2.3.1"><xref derived
Content="6.2.3" format="counter" sectionFormat="of" target="section-6.2.3"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-aliases-fo
r-sources-of-law-">Aliases for Sources of Law with Different Normative Reference
s</xref></t>
</li>
<li pn="section-toc.1-1.6.2.2.2.4">
<t indent="0" pn="section-toc.1-1.6.2.2.2.4.1"><xref derived
Content="6.2.4" format="counter" sectionFormat="of" target="section-6.2.4"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-relations-
between-measure-a">Relations Between Measure and Authority in the Aliases</xref>
</t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.6.2.3">
<t indent="0" pn="section-toc.1-1.6.2.3.1"><xref derivedContent=
"6.3" format="counter" sectionFormat="of" target="section-6.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-the-details-element">T
he Details Element</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.6.2.3.2">
<li pn="section-toc.1-1.6.2.3.2.1">
<t indent="0" pn="section-toc.1-1.6.2.3.2.1.1"><xref derived
Content="6.3.1" format="counter" sectionFormat="of" target="section-6.3.1"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-indication
-of-the-details">Indication of the Details</xref></t>
</li>
<li pn="section-toc.1-1.6.2.3.2.2">
<t indent="0" pn="section-toc.1-1.6.2.3.2.2.1"><xref derived
Content="6.3.2" format="counter" sectionFormat="of" target="section-6.3.2"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-multiple-d
ates">Multiple Dates</xref></t>
</li>
<li pn="section-toc.1-1.6.2.3.2.3">
<t indent="0" pn="section-toc.1-1.6.2.3.2.3.1"><xref derived
Content="6.3.3" format="counter" sectionFormat="of" target="section-6.3.3"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-unnumbered
-measures">Unnumbered Measures</xref></t>
</li>
<li pn="section-toc.1-1.6.2.3.2.4">
<t indent="0" pn="section-toc.1-1.6.2.3.2.4.1"><xref derived
Content="6.3.4" format="counter" sectionFormat="of" target="section-6.3.4"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-multiple-n
umbers">Multiple Numbers</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.6.2.4">
<t indent="0" pn="section-toc.1-1.6.2.4.1"><xref derivedContent=
"6.4" format="counter" sectionFormat="of" target="section-6.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-the-annex-element">The
Annex Element</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.6.2.4.2">
<li pn="section-toc.1-1.6.2.4.2.1">
<t indent="0" pn="section-toc.1-1.6.2.4.2.1.1"><xref derived
Content="6.4.1" format="counter" sectionFormat="of" target="section-6.4.1"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-formal-ann
exes">Formal Annexes</xref></t>
</li>
<li pn="section-toc.1-1.6.2.4.2.2">
<t indent="0" pn="section-toc.1-1.6.2.4.2.2.1"><xref derived
Content="6.4.2" format="counter" sectionFormat="of" target="section-6.4.2"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-annexes-of
-annexes">Annexes of Annexes</xref></t>
</li>
</ul>
</li>
</ul>
</li>
<li pn="section-toc.1-1.7">
<t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" form
at="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-specific-syntax-of-the-vers">Speci
fic Syntax of the Version Element of the "Expression"</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.7.2">
<li pn="section-toc.1-1.7.2.1">
<t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent=
"7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-the-version-element">T
he Version Element</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.7.2.1.2">
<li pn="section-toc.1-1.7.2.1.2.1">
<t indent="0" pn="section-toc.1-1.7.2.1.2.1.1"><xref derived
Content="7.1.1" format="counter" sectionFormat="of" target="section-7.1.1"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-different-
versions-of-a-leg">Different Versions of a Legislative Document</xref></t>
</li>
<li pn="section-toc.1-1.7.2.1.2.2">
<t indent="0" pn="section-toc.1-1.7.2.1.2.2.1"><xref derived
Content="7.1.2" format="counter" sectionFormat="of" target="section-7.1.2"/>.  <
xref derivedContent="" format="title" sectionFormat="of" target="name-identifica
tion-of-the-versi">Identification of the Version</xref></t>
</li>
</ul>
</li>
</ul>
</li>
<li pn="section-toc.1-1.8">
<t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" form
at="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-summary-of-the-syntax-of-th">Summa
ry of the Syntax of the Uniform Names of the LEX Namespace</xref></t>
</li>
<li pn="section-toc.1-1.9">
<t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" form
at="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-procedure-of-uniform-names-">Proce
dure of Uniform Names Assignment</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.9.2">
<li pn="section-toc.1-1.9.2.1">
<t indent="0" pn="section-toc.1-1.9.2.1.1"><xref derivedContent=
"9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-specifying-the-jurisdi
ction">Specifying the Jurisdiction Element of the LEX Identifier</xref></t>
</li>
<li pn="section-toc.1-1.9.2.2">
<t indent="0" pn="section-toc.1-1.9.2.2.1"><xref derivedContent=
"9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-jurisdictional-registr
ar-fo">Jurisdictional Registrar for Names Assignment</xref></t>
</li>
<li pn="section-toc.1-1.9.2.3">
<t indent="0" pn="section-toc.1-1.9.2.3.1"><xref derivedContent=
"9.3" format="counter" sectionFormat="of" target="section-9.3"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-identifier-uniqueness"
>Identifier Uniqueness</xref></t>
</li>
<li pn="section-toc.1-1.9.2.4">
<t indent="0" pn="section-toc.1-1.9.2.4.1"><xref derivedContent=
"9.4" format="counter" sectionFormat="of" target="section-9.4"/>.  <xref derived
Content="" format="title" sectionFormat="of" target="name-identifier-persistence
-cons">Identifier Persistence Considerations</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.10">
<t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" fo
rmat="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-recommendations-for-the-res">Rec
ommendations for the Resolution Process</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.10.2">
<li pn="section-toc.1-1.10.2.1">
<t indent="0" pn="section-toc.1-1.10.2.1.1"><xref derivedContent
="10.1" format="counter" sectionFormat="of" target="section-10.1"/>.  <xref deri
vedContent="" format="title" sectionFormat="of" target="name-general-architectur
e-of-the">General Architecture of the System</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2">
<t indent="0" pn="section-toc.1-1.10.2.2.1"><xref derivedContent
="10.2" format="counter" sectionFormat="of" target="section-10.2"/>.  <xref deri
vedContent="" format="title" sectionFormat="of" target="name-catalogues-for-reso
lution">Catalogues for Resolution</xref></t>
</li>
<li pn="section-toc.1-1.10.2.3">
<t indent="0" pn="section-toc.1-1.10.2.3.1"><xref derivedContent
="10.3" format="counter" sectionFormat="of" target="section-10.3"/>.  <xref deri
vedContent="" format="title" sectionFormat="of" target="name-suggested-resolver-
behavior">Suggested Resolver Behavior</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.11">
<t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="11" fo
rmat="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-security-considerations">Securit
y Considerations</xref></t>
</li>
<li pn="section-toc.1-1.12">
<t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="12" fo
rmat="counter" sectionFormat="of" target="section-12"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-iana-considerations">IANA Consid
erations</xref></t>
</li>
<li pn="section-toc.1-1.13">
<t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="13" fo
rmat="counter" sectionFormat="of" target="section-13"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-references">References</xref></t
>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.13.2">
<li pn="section-toc.1-1.13.2.1">
<t indent="0" pn="section-toc.1-1.13.2.1.1"><xref derivedContent
="13.1" format="counter" sectionFormat="of" target="section-13.1"/>.  <xref deri
vedContent="" format="title" sectionFormat="of" target="name-normative-reference
s">Normative References</xref></t>
</li>
<li pn="section-toc.1-1.13.2.2">
<t indent="0" pn="section-toc.1-1.13.2.2.1"><xref derivedContent
="13.2" format="counter" sectionFormat="of" target="section-13.2"/>.  <xref deri
vedContent="" format="title" sectionFormat="of" target="name-informative-referen
ces">Informative References</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.14">
<t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="" form
at="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="
" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgeme
nts</xref></t>
</li>
<li pn="section-toc.1-1.15">
<t indent="0" pn="section-toc.1-1.15.1"><xref derivedContent="" form
at="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="
" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Add
resses</xref></t>
</li>
</ul>
</section>
</toc>
</front> </front>
<middle> <middle>
<?line 165?> <section anchor="introduction" numbered="true" removeInRFC="false" toc="incl
ude" pn="section-1">
<section anchor="introduction"> <name slugifiedName="name-introduction">Introduction</name>
<name>Introduction</name> <section anchor="the-purpose-of-namespace-lex" numbered="true" removeInRFC
<section anchor="the-purpose-of-namespace-lex"> ="false" toc="include" pn="section-1.1">
<name>The Purpose of Namespace "lex"</name> <name slugifiedName="name-the-purpose-of-namespace-le">The Purpose of Na
<t>The purpose of the "lex" namespace is to assign a unique mespace LEX</name>
identifier in a well-defined format to documents that are sources of <t indent="0" pn="section-1.1-1">The purpose of the LEX namespace is to
law. In this context, "sources of law" include any assign a unique identifier
legal document within the domain of legislation, case law and in a well-defined format to documents that are sources of law.
administrative acts or regulations. Potential sources of In this context, "sources of law" include any legal document within the domain
law (acts under the process of law formation, as bills) are included of legislation, case law, administrative acts, or regulations. Potential
as well. "Legal doctrine", that is the body of knowledge and theoretical sources of law (acts under the process of law formation, such as bills) are
speculation typical of legal scholars (e.g. commentary on judgment,<br/> included as well. "Legal doctrine", that is, the body of knowledge and
jurisprudence review, commentary on legislation, encyclopedic entries, theoretical speculation typical of legal scholars (e.g., commentary on
monographs, articles in magazines, manuals, etc.) is explicitly not covered.</t> judgment, jurisprudence review, commentary on legislation, encyclopedic
<t>The identifier is conceived so that its construction depends only on entries, monographs, articles in magazines, manuals, etc.) is explicitly not
the content of the document itself and not its on-line availability, its covered.</t>
physical location, and access mode. The identifier itself is assigned <t indent="0" pn="section-1.1-2">The identifier is conceived so that its
by the jurisdiction of the identified document. Even a document that construction depends only on
the content of the document itself and not its online availability, physical loc
ation, and access mode. The identifier itself is assigned
by the jurisdiction of the identified document. A document that
is not available online may, nevertheless, have a LEX URN identifier.</t> is not available online may, nevertheless, have a LEX URN identifier.</t>
<t>The lex URN may be used as a way to represent references (and <t indent="0" pn="section-1.1-3">The LEX URN may be used as a way to rep resent references (and
more generally, any type of relation) among various sources of law. more generally, any type of relation) among various sources of law.
In an on-line environment with resources distributed among different In an online environment with resources distributed among different
web publishers, lex URNs web publishers, LEX URNs
allow a simplified global interconnection of legal documents by means allow a simplified global interconnection of legal documents by means
of automated resoluton. LEX URNs consist of persistent and of automated resolution.
LEX URNs consist of persistent and
location-independent identifiers and are particularly location-independent identifiers and are particularly
useful when they can be mapped into or associated with locators such useful when they can be mapped into or associated with locators such
as HTTP URLs. Moreover, LEX URNs details can be used as a reference as HTTP URLs. Moreover, LEX URN details can be used as a reference
to create HTTP-based persistent and location-independent identifiers to create persistent and location-independent identifiers that are HTTP-based
<xref target="RFC3986"/>.</t> <xref target="RFC3986" format="default" sectionFormat="of" derivedContent="RFC39
86"/>.</t>
</section> </section>
<section anchor="background"> <section anchor="background" numbered="true" removeInRFC="false" toc="incl
<name>Background</name> ude" pn="section-1.2">
<t>This specification of a unique identifier for legal documents <name slugifiedName="name-background">Background</name>
<t indent="0" pn="section-1.2-1">This specification of a unique identifi
er for legal documents
follows a number of initiatives in the field of legal document follows a number of initiatives in the field of legal document
management.</t> management.</t>
<t>Since 2001 the Italian Government, through the National Center for <t indent="0" pn="section-1.2-2">Since 2001, the Italian Government prom
Information Technology in the Public Administration, the Ministry of oted the NormeInRete project
Justice and CNR (the National Research Council of Italy) promoted through the National Center for Information Technology in the Public
the NormeInRete project. It was aimed at introducing standards for Administration, the Ministry of Justice, and the National Research
sources of law description and identification using XML and URN Council of Italy (CNR). The NormeInRete project was aimed at introducing
techniques.</t> standards for describing and identifying sources
<t>Other national initiatives in Europe introduced standards for the of law using XML and URN
description of legal sources <xref target="FRAN"/>. Collaborations techniques.</t>
<t indent="0" pn="section-1.2-3">Other national initiatives in Europe in
troduced standards for the
description of legal sources <xref target="FRAN" format="default" sectionFormat=
"of" derivedContent="FRAN"/>. Collaborations
between government, national research institutes, and between government, national research institutes, and
universities, have defined national XML standards for legal document universities have defined national XML standards for legal document
management, as well as schemes for legal document identification. management, as well as schemes for legal document identification.
Outside of Europe, similar initiatives have addressed similar problems Outside of Europe, similar initiatives have addressed similar problems
<xref target="FRAN"/>. Several of these identifiers are based on a URN schema.< <xref target="FRAN" format="default" sectionFormat="of" derivedContent="FRAN"/>.
/t> Several of these identifiers are based on a URN schema.</t>
<t>In today's information society the processes of political, social and <t indent="0" pn="section-1.2-4">In today's information society, the pro
economic integration of European Union member states as well as the cesses of political, social, and
increasing integration of the world-wide legal and economic processes economic integration of European Union (EU) Member States, as well as the
are causing a growing interest in exchanging legal information increasing integration of the worldwide legal and economic processes,
knowledge at national and trans-national levels. are causing a growing interest in the exchange of legal information
at national and transnational levels.
The growing desire for improved quality and accessibility of legal The growing desire for improved quality and accessibility of legal
information amplifies the need for interoperability among legal information amplifies the need for interoperability among legal
information systems across national boundaries. A common well-defined information systems across national boundaries. A common, well-defined
schema used to identify sources of law at international level is an schema used to identify sources of law at an international level is an
essential prerequisite for interoperability.</t> essential prerequisite for interoperability.</t>
<t>Interest groups within several countries have already expressed their <t indent="0" pn="section-1.2-5">Interest groups within several countrie
intention to adopt a shared solution based on a URN technique.<br/> s have already expressed
The need for a unique identifier of sources of law in different their intention to adopt a shared solution based on a URN technique.
EU Member States, based on open standards and able to provide In several conferences (such as <xref target="LVI" format="default" secti
advanced modalities of document hyper-linking, has been expressed in onFormat="of" derivedContent="LVI"/>), representatives
several conferences (as <xref target="LVI"/>) by representatives of the Publicat of the Publications Office of the European Union (OP) have expressed
ions the need for a unique identifier for sources of law,
Office of the European Union (OP), with the aim of promoting based on open standards and able to provide advanced
interoperability among national and European institution information modalities of document hyperlinking, with the aim of promoting
systems. Similar concerns have been raised by international groups interoperability among national and European institution information
concerned with free access to legal information, and the Permanent systems.
Bureau of the Hague Conference on Private International Law <xref target="HCPIL"
/> Similar concerns have been raised by
that encourage State Parties to "adopt neutral methods of citation of international groups concerned with free access to legal information,
their legal materials, including methods that are medium-neutral, and the Permanent Bureau of the Hague Conference on Private
provider-neutral and internationally consistent.". In a similar International Law <xref target="HCPIL" format="default" sectionFormat="o
direction the CEN Metalex initiative is moving, at European level, f" derivedContent="HCPIL"/> encourages State Parties
towards the definition of a standard interchange format for sources to "adopt neutral methods of citation of their legal materials,
of law, including recommendations for defining naming conventions to including methods that are medium-neutral, provider-neutral and
them.</t> internationally consistent".
<t>The need of unique identifiers for sources of law is of In a similar direction, the CEN Metalex
particular interest also in the domain of case law. This is initiative is moving, at the European level, towards the definition of a
acutely felt within both common law systems, where cases are the standard interchange format for sources of law, including
main law sources, and civil law systems, in order to recommendations for defining naming conventions for them.</t>
provide an integrated access to cases and legislation, as well as <t indent="0" pn="section-1.2-6">Additionally, the need for unique ident
to track the relationships between them. This domain is characterized ifiers for sources of law is of
particular interest in the domain of case law.
This need is acutely felt within both common law systems (where cases are
the main law sources) and civil law systems, because unique identifiers can prov
ide
integrated access to cases and legislation, as well as the ability to track the
relationships between them. This domain is characterized
by a high degree of fragmentation in case law information systems, by a high degree of fragmentation in case law information systems,
which usually lack interoperability.</t> which usually lack interoperability.</t>
<t>In the European Union, the community institutions have stressed the <t indent="0" pn="section-1.2-7">In the European Union, the community in
need for citizens, businesses, lawyers, prosecutors and judges to stitutions have stressed the
become more aware not only of (directly applicable) EU law, but also need for citizens, businesses, lawyers, prosecutors, and judges to
of the various national legal systems. The growing importance of become more aware of (directly applicable) EU laws and also
national judiciaries for the application of Community law was the various national legal systems.
The growing importance of
national judiciaries for the application of community law was
stressed in the resolution of the European Parliament of 9 July 2008 stressed in the resolution of the European Parliament of 9 July 2008
on the role of the national judge in the European judicial system.<br/> on the role of the national judge in the European judicial system.
Similarly the Council of the European Union has underlined the Similarly, the Council of the European Union has underlined the
importance of cross-border access to national case law, as well as importance of cross-border access to national case law, as well as
the need for its standardisation, in view of an integrated access in the need for its standardization, with a vision of a decentralized
a decentralized architecture. In this view the Working Party on Legal architecture with integrated access. The Working Party on Legal Data
Data Processing (e-Law) of the Council of the European Union formed a Processing (e-Law) of the Council of the European Union formed a
task group to study the possibilities for improving cross-border task group to study the possibilities for improving cross-border
access to national case law. Taking notice of the report of the access to national case law.
Working Party's task group, the Council of the EU decided in 2009 to Taking notice of the report of the
elaborate on a uniform, European system for the identification of Working Party's task group, in 2009, the Council of the European Union decided t
case law (ECLI: European Case-Law Identifier) and uniform Dublin o
Core-based set of metadata.</t> elaborate on a uniform European system for the identification of
<t>The Council of the European Union invited the Member States to case law (i.e., the European Case-Law Identifier (ECLI)) and a uniform set of me
introduce in the legal information systems the European Legislation tadata based on the Dublin Core.</t>
Identifier (ELI), an http-based Semantic Web oriented identification <t indent="0" pn="section-1.2-8">The Council of the European Union invit
system for European Union and Member States legislation.</t> ed the Member States to
<t>The LEX identifier (also referred in this text as "LEX name") is introduce the European Legislation Identifier (ELI) in the legal
conceived to be general enough so as to provide guidance at the core information systems, which is an HTTP-based, Semantic Web-oriented
of the standard and sufficient flexibility to cover a wide variety of identification system for legislation of the European Union and Member S
needs for identifying all the legal documents of different nature, tates.</t>
namely legislative, case-law and administrative acts. Moreover, it <t indent="0" pn="section-1.2-9">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 standard and offer sufficient flexibility to cover a wide variety of
needs for identifying legal documents of different types,
namely, legislative, case law, and administrative acts.
Moreover, it
can be effectively used within a federative environment where can be effectively used within a federative environment where
different publishers (public and private) can provide their own items different publishers (public and private) can provide their own items,
of a legal document (that is there is more than one manifestation of in <xref target="FRBR" format="default" sectionFormat="of" derivedContent="FRBR"
/> sense (see <xref target="src-law" format="default" sectionFormat="of" derived
Content="Section 5.2"/>),
of a legal document (that is, there is more than one manifestation (see <xref ta
rget="src-law" format="default" sectionFormat="of" derivedContent="Section 5.2"/
>) of
the same legal document).</t> the same legal document).</t>
<t>Specifications and syntax rules of LEX identifier can be used <t indent="0" pn="section-1.2-10">Specifications and syntax rules for th
also for http-based naming convention to cope with e LEX identifier can also be used
different requirements in legal information management, for example for HTTP-based naming conventions to cope with
the need of having an identifier compliant with the Linked Open Data different requirements in legal information management, for example,
the need to have an identifier that is compliant with the Linked Open Data
principles.</t> principles.</t>
<t>This document supplements the required name syntax with a naming <t indent="0" pn="section-1.2-11">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.</t> solution for sources of law identification.</t>
</section> </section>
<section anchor="general-characteristics-of-the-system"> <section anchor="general-characteristics-of-the-system" numbered="true" re
<name>General Characteristics of the System</name> moveInRFC="false" toc="include" pn="section-1.3">
<t>The specifications in this document promote interoperability <name slugifiedName="name-general-characteristics-of-">General Character
istics of the System</name>
<t indent="0" pn="section-1.3-1">The specifications in this document pro
mote interoperability
among legal information systems by defining a namespace among legal information systems by defining a namespace
convention and structure that will create and manage identifiers for convention and structure that will create and manage identifiers for
legal documents. The identifiers are intended to be:</t> legal documents. The identifiers are intended to have the following qualities:</
<ul spacing="normal"> t>
<li> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1
<t>globally unique</t> .3-2">
<li pn="section-1.3-2.1">
<t indent="0" pn="section-1.3-2.1.1">globally unique</t>
</li> </li>
<li> <li pn="section-1.3-2.2">
<t>transparent</t> <t indent="0" pn="section-1.3-2.2.1">transparent</t>
</li> </li>
<li> <li pn="section-1.3-2.3">
<t>reversible</t> <t indent="0" pn="section-1.3-2.3.1">reversible</t>
</li> </li>
<li> <li pn="section-1.3-2.4">
<t>persistent</t> <t indent="0" pn="section-1.3-2.4.1">persistent</t>
</li> </li>
<li> <li pn="section-1.3-2.5">
<t>location-independent, and</t> <t indent="0" pn="section-1.3-2.5.1">location-independent</t>
</li> </li>
<li> <li pn="section-1.3-2.6">
<t>language-neutral.</t> <t indent="0" pn="section-1.3-2.6.1">language-neutral</t>
</li> </li>
</ul> </ul>
<t>These qualities facilitate legal document management and <t indent="0" pn="section-1.3-3">These qualities facilitate management o
a mechanism of stable cross-collections and cross-country f legal documents and
a mechanism for stable cross-collection and cross-country
references.</t> references.</t>
<t>Transparency means that given an act and its relevant metadata <t indent="0" pn="section-1.3-4">Transparency means that, for a given ac t and its relevant metadata
(issuing authority, type of measure, etc.), it is possible to create (issuing authority, type of measure, etc.), it is possible to create
the related URN able to a related URN that is able to
uniquely identify the act in a way that is reversible uniquely identify the act in a way that is reversible
(from an act to its URN and from a (from an act to its URN and from a
URN to the act).</t> URN to the act).</t>
<t>Language-neutrality, in particular, is an important feature that <t indent="0" pn="section-1.3-5">Language neutrality, in particular, is an important feature that
promotes adoption of the standard by organizations that must adhere to promotes adoption of the standard by organizations that must adhere to
official-language requirements. This specification provides official language requirements. This specification provides
guidance to both public and private groups that create, promulgate, guidance to both public and private groups that create, promulgate,
and publish legal documents. Registrants wish to minimize the and publish legal documents. Registrants wish to minimize the
potential for creating conflicting proprietary schemes, while potential for creating conflicting proprietary schemes, while
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.</t> equally diverse assortment of administrative entities.</t>
<t>The challenge is to provide the right amount guidance at the <t indent="0" pn="section-1.3-6">The challenge is to provide the right a mount guidance at the
core of the specification while providing sufficient flexibility to core of the specification while providing sufficient flexibility to
cover a wide variety of needs. LEX does this by cover a wide variety of needs. LEX does this by
splitting the identifier into parts. The first part uses a splitting the identifier into parts. The first part uses a
pre-existing standard specification ("country/jurisdiction name preexisting standard specification ("country/jurisdiction name
standard") to indicate the country (or more generally the standard") to indicate the country (or more generally, the
jurisdiction) of origin for the legal document being identified; the jurisdiction) of origin for the legal document being identified; the
remainder ("local name") is intended for local use in identifying remainder ("local-name") is intended for local use in identifying
documents issued in that country or jurisdiction.</t> documents issued in that country or jurisdiction.</t>
<t>The second part <t indent="0" pn="section-1.3-7">The second part depends only on the ide
depends only on the sources of law identification system operating ntification
in that nation and it is mainly composed by formalized information system for sources of law operating in that nation, and it is mainly com
related to the enacting authority, the type of measure, the details posed by
and possibly the annex.</t> formalized information related to the enacting authority, the type of
<t>The identification system based on uniform names includes:</t> measure, the details, and possibly the annex.</t>
<ul spacing="normal"> <t indent="0" pn="section-1.3-8">The identification system based on unif
<li> orm names includes:</t>
<t>a schema for assigning names capable of representing unambiguousl <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1
y .3-9">
any addressed source of law (namely legislation, case law and <li pn="section-1.3-9.1">
administrative acts), issued by any authority (intergovernmental, <t indent="0" pn="section-1.3-9.1.1">A schema for assigning names ca
supranational, national, regional and local) at any time (past, pable of unambiguously
present and future);</t> representing any addressed source of law (namely legislation, case
law, and administrative acts) issued by any authority
(intergovernmental, supranational, national, regional, and local)
at any time (past, present, and future).</t>
</li> </li>
<li> <li pn="section-1.3-9.2">
<t>a resolution mechanism - in a distributed environment - that ties <t indent="0" pn="section-1.3-9.2.1">A resolution mechanism -- in a
a distributed environment -- that ties a
uniform name to the on-line location of the corresponding uniform name to the online location of the corresponding
resource(s).</t> resource(s).</t>
</li> </li>
</ul> </ul>
<t>This document considers the first of these requirements. It also <t indent="0" pn="section-1.3-10">This document considers the first of t hese 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.</t> service and to the corresponding software.</t>
</section> </section>
<section anchor="linking-a-lex-name-to-a-document"> <section anchor="linking-a-lex-name-to-a-document" numbered="true" removeI
<name>Linking a LEX Name to a Document</name> nRFC="false" toc="include" pn="section-1.4">
<t>The LEX name is linked to the document through meta-information which <name slugifiedName="name-linking-a-lex-name-to-a-doc">Linking a LEX Nam
e to a Document</name>
<t indent="0" pn="section-1.4-1">The LEX name is linked to the document
through metadata, which
may be specified as follows:</t> may be specified as follows:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1
<li> .4-2">
<t>within the document itself through a specific element within <li pn="section-1.4-2.1">
an XML schema or by an <xref target="W3C.HTML"/> META tag;</t> <t indent="0" pn="section-1.4-2.1.1">Within the document itself thro
ugh a specific element within
an XML schema or by a meta tag <xref target="W3C.HTML" format="default" sectionF
ormat="of" derivedContent="W3C.HTML"/>.</t>
</li> </li>
<li> <li pn="section-1.4-2.2">
<t>externally by means of a Resource Description Framework <xref tar <t indent="0" pn="section-1.4-2.2.1">Externally by means of a Resour
get="W3C.rdf-schema"/> ce Description Framework <xref target="W3C.RDF-SCHEMA" format="default" sectionF
ormat="of" derivedContent="W3C.RDF-SCHEMA"/>
triple, a specific attribute in a database, etc.</t> triple, a specific attribute in a database, etc.</t>
</li> </li>
</ul> </ul>
<t>At least one of these references is necessary to enable automated <t indent="0" pn="section-1.4-3">At least one of these references is nec
construction and update of catalogues (distributed and centralized) essary to enable automated
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
of a document with its physical location(s). LEX assumes no of a document with its physical location. LEX assumes no
particular relationship between the originator of the document, its particular relationship between the originator of the document, its
publisher, and the implementer of catalogues or resolution services.</t> publisher, the implementer of catalogues, or resolution services.</t>
</section> </section>
<section anchor="use-of-lex-names-in-references"> <section anchor="use-of-lex-names-in-references" numbered="true" removeInR
<name>Use of LEX Names in References</name> FC="false" toc="include" pn="section-1.5">
<t>LEX names can be used in references as an HREF attribute value of the <name slugifiedName="name-use-of-lex-names-in-referen">Use of LEX Names
in References</name>
<t indent="0" pn="section-1.5-1">LEX names can be used in references as
an HREF attribute value of the
hypertext link to the referred document. hypertext link to the referred document.
This link can be created in two ways:</t> This link can be created in two ways:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1
<li> .5-2">
<t>by manually inserting in the referring document the link with the <li pn="section-1.5-2.1">
uniform name: this is a burdensome procedure, especially for <t indent="0" pn="section-1.5-2.1.1">Manually inserting the link wit
documents that are already on-line;</t> h the
uniform name in the referring document. This is a burdensome procedure, especial
ly for
documents that are already online.</t>
</li> </li>
<li> <li pn="section-1.5-2.2">
<t>by automatically constructing (either permanently or temporarily) <t indent="0" pn="section-1.5-2.2.1">Automatically constructing (eit
the link with the uniform name, through reference parsers of a her permanently or temporarily)
text: this is a more time-saving procedure even if subject to a the link with the uniform name from references in the text using
a parser. This procedure offers more time savings, even if it is subject to a
certain percentage of errors, since references are not always certain percentage of errors, since references are not always
accurate or complete. This solution could nevertheless be accurate or complete. This solution could nevertheless be
acceptable for already published documents.</t> acceptable for documents that are already published.</t>
</li> </li>
</ul> </ul>
<t>Whatever method is adopted, new documents produced <t indent="0" pn="section-1.5-3">No matter which method is adopted, new
in whatever format (for example XML, XHTML, etc) documents produced
in a certain format (for example, XML, XHTML, etc.)
should express references through the uniform name should express references through the uniform name
of the document referred to.</t> of the document referred to.</t>
</section> </section>
<section anchor="definitions"> <section anchor="definitions" numbered="true" removeInRFC="false" toc="inc
<name>Definitions</name> lude" pn="section-1.6">
<t>The following terms are used in <name slugifiedName="name-definitions">Definitions</name>
these specifications:</t> <t indent="0" pn="section-1.6-1">The following terms are used in this do
<ul spacing="normal"> cument:
<li> </t>
<t>Source of Law: <dl spacing="normal" indent="3" newline="false" pn="section-1.6-2">
a general concept to refer to legislation, case <dt pn="section-1.6-2.1">Source of Law:</dt>
law, regulations and administrative acts. In its broadest sense, <dd pn="section-1.6-2.2">
A general concept that refers to legislation, case
law, regulations, and administrative acts. In its broadest sense,
the source of law is anything that can be conceived as the the source of law is anything that can be conceived as the
originator of 'erga omnes' legal rules. In this document "Source of originator of 'erga omnes' legal rules. In this document, "source of
Law" refers also to acts during their making such as bills that law" also refers to acts during their creation, such as bills, that
might or might not become laws;</t> might or might not become laws.</dd>
</li> <dt pn="section-1.6-2.3">Jurisdictional Registrar:</dt>
<li> <dd pn="section-1.6-2.4">
<t>Jurisdictional Registrar: An organization in any
an organization that shares and defines in any jurisdiction that shares and defines the assignment of the main components of th
jurisdiction the assignment of the main components of the resource e resource
identifier through which the identifier uniqueness is guaranteed.</t> identifier through which the identifier uniqueness is guaranteed.</dd>
</li> </dl>
</ul>
</section> </section>
<section anchor="terminology"> <section anchor="terminology" numbered="true" removeInRFC="false" toc="inc
<name>Terminology</name> lude" pn="section-1.7">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <name slugifiedName="name-terminology">Terminology</name>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and <t indent="0" pn="section-1.7-1">
"OPTIONAL" in this document are to be interpreted as described in BCP The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they a "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
ppear in all ",
capitals, as shown here.</t> "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be
interpreted as described in BCP 14 <xref target="RFC2119" format="default" s
ectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="defa
ult" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they app
ear in all capitals, as
shown here.
</t>
</section> </section>
<section anchor="syntax-used-in-this-document"> <section anchor="syntax-used-in-this-document" numbered="true" removeInRFC
<name>Syntax Used in this Document</name> ="false" toc="include" pn="section-1.8">
<t>This document uses the syntax common to many Internet RFCs, which is <name slugifiedName="name-syntax-used-in-this-documen">Syntax Used in Th
based on the ABNF (Augmented Backus-Naur Form) <xref target="RFC5234"/> meta- is Document</name>
language.</t> <t indent="0" pn="section-1.8-1">This document uses a syntax that is bas
ed on the Augmented
Backus-Naur Form (ABNF) <xref target="RFC5234" format="default" sectionF
ormat="of" derivedContent="RFC5234"/> meta-language, which
is used in many RFCs.</t>
</section> </section>
<section anchor="namespace-registration"> <section anchor="namespace-registration" numbered="true" removeInRFC="fals
<name>Namespace Registration</name> e" toc="include" pn="section-1.9">
<t>The "lex" namespace has already been registered in the "Formal URN <name slugifiedName="name-namespace-registration">Namespace Registration
Namespaces" registry.</t> </name>
<t indent="0" pn="section-1.9-1">The LEX namespace has been registered i
n the "Formal URN
Namespaces" registry. See <xref target="iana" format="default" sectionFormat="of
" derivedContent="Section 12"/>.</t>
</section> </section>
</section> </section>
<section anchor="registration-of-lex"> <section anchor="registration-of-lex" numbered="true" removeInRFC="false" to
<name>Registration of LEX</name> c="include" pn="section-2">
<section anchor="identifier-structure"> <name slugifiedName="name-registration-of-lex">Registration of LEX</name>
<name>Identifier Structure</name> <section anchor="identifier-structure" numbered="true" removeInRFC="false"
<t>The identifier has a hierarchical structure as follows:</t> toc="include" pn="section-2.1">
<artwork><![CDATA[ <name slugifiedName="name-identifier-structure">Identifier Structure</na
me>
<t indent="0" pn="section-2.1-1">The identifier has the following hierar
chical structure:</t>
<sourcecode type="abnf" markers="false" pn="section-2.1-2">
"urn:lex:" NSS "urn:lex:" NSS
]]></artwork> </sourcecode>
<t>where NSS is the Namespace Specific String composed as follows:</t> <t indent="0" pn="section-2.1-3">where NSS is the Namespace Specific Str
<artwork><![CDATA[ ing composed as follows:</t>
<sourcecode type="abnf" markers="false" pn="section-2.1-4">
NSS = jurisdiction ":" local-name NSS = jurisdiction ":" local-name
]]></artwork> </sourcecode>
<t>where:</t> <t indent="0" pn="section-2.1-5">where:</t>
<ul spacing="normal"> <dl newline="false" spacing="normal" indent="3" pn="section-2.1-6">
<li> <dt pn="section-2.1-6.1">jurisdiction:</dt>
<t>jurisdiction <dd pn="section-2.1-6.2">
identifies the scope (state, regional, Identifies the scope (state, regional,
municipal, supranational or of an organization) where a set of municipal, supranational, or organizational) where a set of
sources of law have validity. It is also possible to represent sources of law have validity. It is also possible to represent
international organizations (either states or public international organizations (either states, public
administrations or private entities);</t> administrations, or private entities).</dd>
</li> <dt pn="section-2.1-6.3">local-name:</dt>
<li> <dd pn="section-2.1-6.4">The uniform name of the source of law in the
<t>local-name is the uniform name of the source of law in the country or jurisdiction where it is issued; its internal structure
country or jurisdiction where it is issued; its internal is common to the already-adopted schemas.
structure is common to the already adopted schemas. It It
represents all aspects of an intellectual production, represents all aspects of an intellectual production,
from its initial idea, through its from its initial idea, through its
evolution during the time, to its realisation by different evolution during the time, to its realization by different
means (paper, digital, etc.).</t> means (paper, digital, etc.).</dd>
</li> </dl>
</ul> <t indent="0" pn="section-2.1-7">The jurisdiction element is composed of
<t>The jurisdiction element is composed of two specific fields:</t> two specific fields:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-2.1-8">
jurisdiction = jurisdiction-code *(";" jurisdiction-unit) jurisdiction = jurisdiction-code *(";" jurisdiction-unit)
]]></artwork> </sourcecode>
<t>where:</t> <t indent="0" pn="section-2.1-9">where:</t>
<ul spacing="normal"> <dl newline="false" spacing="normal" indent="3" pn="section-2.1-10">
<li> <dt pn="section-2.1-10.1">jurisdiction-code:</dt>
<t>jurisdiction-code is usually the identification code of the count <dd pn="section-2.1-10.2">
ry <t indent="0" pn="section-2.1-10.2.1">Usually the identification cod
where the source of law is issued.<br/> e of the
To facilitate the transparency of the name, the jurisdiction-code country where the source of law is issued. To facilitate the
follows usually the rules of identification of other Internet transparency of the name, the jurisdiction-code usually follows
applications, based on domain name (for details and special cases see the rules of identification of other Internet applications, based
<xref target="jur-cod-regist"/>).<br/> on domain name (for details and special cases, see <xref target="jur
Due to the differences in representation in the various languages of a country, -cod-regist" format="default" sectionFormat="of" derivedContent="Section 2.2"/>)
for an easier identification of the country the use the .</t>
standard <xref target="ISO3166-1"/> is strongly RECOMMENDED.<br/> <t indent="0" pn="section-2.1-10.2.2">Due to the differences in repr
Therefore a urn-lex ID always begins with a sequence of ASCII characters: esentation in the various
"urn:lex:ccTLD". For all the other components that follow the jurisdiction-code, languages of a country, the use of the standard <xref target="ISO.316
the Jurisdictional Registrar decides the mode of representation (ASCII or 6-1" format="default" sectionFormat="of" derivedContent="ISO.3166-1"/> is
UTF-8 %-encoding) (see <xref target="non-ascii-char"/>).<br/> strongly <bcp14>RECOMMENDED</bcp14> for easier identification
Where applicable, the domain name of the of the country. Therefore, a LEX URN ID always begins with a
country or multinational or international organisation is used.<br/> sequence of ASCII characters: "urn:lex:ccTLD". For all the other
If such information is not available for a particular institution, a components that follow the jurisdiction-code, the Jurisdictional
specific code will be defined (see <xref target="jur-cod-regist"/>). Registrar decides the mode of representation (ASCII or UTF-8
Examples reported in this document are hypothetical and assume that percent-encoding; see <xref target="non-ascii-char" format="default"
the corresponding domain name is used for the jurisdiction-code.</t> sectionFormat="of" derivedContent="Section 3.4"/>).</t>
</li> <t indent="0" pn="section-2.1-10.2.3">Where applicable, the domain n
<li> ame of the country or multinational or
<t>jurisdiction-unit are the possible administrative hierarchical international organization is used. If such information is not available for
sub-structures defined by each country or organisation within their a particular institution, a specific code will be defined (see <xref target="jur
specific legal system. This additional information can be used in -cod-regist" format="default" sectionFormat="of" derivedContent="Section 2.2"/>)
case two or more levels of legislative or judicial production exist . Examples reported in this document are
(e.g., federal, state and municipality level) and the same bodies may hypothetical and assume that the corresponding domain name is used for the
be present in each jurisdiction. Therefore acts of the same type jurisdiction-code.</t>
issued by similar authorities in different areas differ for the </dd>
jurisdiction-unit specification.<br/> <dt pn="section-2.1-10.3">jurisdiction-unit</dt>
<dd pn="section-2.1-10.4">
<t indent="0" pn="section-2.1-10.4.1">The possible administrative hi
erarchical
sub-structures defined by each country or organization within their
specific legal system.
This additional information can be used when two or more levels of legislative o
r judicial production exist
(e.g., federal, state, and municipality level) and the same bodies may
be present in each jurisdiction.
Therefore, the jurisdiction-unit differs for acts of the same type issued by sim
ilar authorities but pertain to different jurisdictions related to different geo
graphical areas.<br/>
An example can be the following:<br/> An example can be the following:<br/>
"br:governo:decreto" (decree of federal government),<br/> "br:governo:decreto" (decree of federal government),<br/>
"br;sao.paulo:governo:decreto" (decree of SU+00E3o Paulo state) <br/> "br;sao.paulo:governo:decreto" (decree of São (SU+00E3o) Paulo state) <br/>
"br;sao.paulo;campinas:governo:decreto" (decree of Campinas <br/> "br;sao.paulo;campinas:governo:decreto" (decree of Campinas <br/>
municipality).</t> municipality).</t>
</li> </dd>
</ul> </dl>
<t>Fictitious examples of sources of law identifiers are:</t> <t indent="0" pn="section-2.1-11">The following are fictitious examples
<artwork><![CDATA[ of sources of law identifiers:</t>
<artwork align="left" pn="section-2.1-12">
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)
]]></artwork> </artwork>
</section> </section>
<section anchor="jur-cod-regist"> <section anchor="jur-cod-regist" numbered="true" removeInRFC="false" toc="
<name>Jurisdiction-code Register</name> include" pn="section-2.2">
<t>A new jurisdiction-code registry has been created. Each entry <name slugifiedName="name-jurisdiction-code-registry">Jurisdiction-Code
contains the following elements:</t> Registry</name>
<ul spacing="normal"> <t indent="0" pn="section-2.2-1">A new jurisdiction-code registry has be
<li> en created. Note that this
<t>jurisdiction-code: the identifier of jurisdiction, assigned is a CNR registry and <strong>not</strong> an IANA registry.</t>
to the country or organisation;</t> <t indent="0" pn="section-2.2-2">Each
</li> entry contains the following elements:</t>
<li> <dl spacing="normal" indent="3" newline="false" pn="section-2.2-3">
<t>jurisdiction: the official name of the jurisdiction, <dt pn="section-2.2-3.1">jurisdiction-code:</dt>
country or organisation;</t> <dd pn="section-2.2-3.2">The identifier assigned to the jurisdiction
</li> (i.e., to the country or organization).</dd>
<li> <dt pn="section-2.2-3.3">jurisdiction:</dt>
<t>registrant: essential information to identify the organization <dd pn="section-2.2-3.4">The official name of the jurisdiction (i.e.,
the country or organization).</dd>
<dt pn="section-2.2-3.5">registrant:</dt>
<dd pn="section-2.2-3.6">Essential information that identifies the org
anization
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 and for 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 <bcp14>RECOMMENDED</bcp14> 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 of each sub-zone can easily be identified;</t> responsible for each sub-zone can easily be identified.</dd>
</li> <dt pn="section-2.2-3.7">reference:</dt>
<li> <dd pn="section-2.2-3.8">A reference to the defining document (if any)
<t>reference: a reference to the defining document (if any).</t> .</dd>
</li> </dl>
</ul> <t indent="0" pn="section-2.2-4">The table, available at the address lex
<t>The table is initially empty. Possible example entries are:</t> -urn.nic.it, is initially empty. The registry is initially empty. The following
<artwork><![CDATA[ are possible example entries:</t>
<artwork align="left" pn="section-2.2-5">
"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\]
]]></artwork> </artwork>
<t>Note that this is a CNR registry and <strong>not</strong> an IANA reg <t indent="0" pn="section-2.2-6">CNR is responsible for the
istry.</t>
<t>CNR is responsible for the
jurisdiction-code and the root lex-nameserver.nic.it registries of the resolutio n jurisdiction-code and the root lex-nameserver.nic.it registries of the resolutio n
routing.</t> routing.</t>
<t>A new Jurisdictional Registrar will contact CNR or the Designated <t indent="0" pn="section-2.2-7">A new Jurisdictional Registrar will con
Expert(s) according to the established rules of governance (published tact CNR or the designated
in the CNR website dedicated to the LEX governance). The application expert(s) according to the established rules of governance (published
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
of the DNS. Typically such applications should come from public evaluations of the DNS. Typically, such applications should come from public
administrations, as authorities enacting sources of law.</t> administrations, as authorities enacting sources of law.</t>
<t>The adopted registration policy is similar to that of the "Expert Rev <t indent="0" pn="section-2.2-8">The adopted registration policy is simi
iew" lar to that of the "Expert Review"
as specified in <xref target="RFC8126"/>. Designated Experts will assign policy specified in <xref target="RFC8126" format="default" sectionFormat="of" d
jurisdiction codes based on the following principles:</t> erivedContent="RFC8126"/>. The designated expert(s) will assign
<ul spacing="normal"> jurisdiction-codes based on the following principles:</t>
<li> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2
<t>If a request comes from a jurisdiction that corresponds to a .2-9">
country and the jurisdiction code is the same as a top level ccTLD, <li pn="section-2.2-9.1">
then the top level ccTLD should be <t indent="0" pn="section-2.2-9.1.1">If a request comes from a juris
used as the jurisdiction code;</t> diction that corresponds to a
country and the jurisdiction-code is the same as a top-level Country Code Top-Le
vel Domain (ccTLD),
then the top-level ccTLD should be
used as the jurisdiction-code.</t>
</li> </li>
<li> <li pn="section-2.2-9.2">
<t>If a request comes from a jurisdiction that corresponds to a <t indent="0" pn="section-2.2-9.2.1">If a request comes from a juris
multi-national (e.g., European Union) or international (e.g., United diction that corresponds to a
Nations, World Trade Organization) organizations the Top Level multi-national organization (e.g., European Union) or international
Domain Name (e.g., "eu") or the Domain Name (e.g., "un.org", organization (e.g.,
"wto.org") of the organization should be used as the jurisdiction United Nations and World Trade Organization), the
code;</t> Top-Level Domain Name (e.g., "eu") or the Domain Name (e.g.,
"un.org" and "wto.org") of the organization should be used as the
jurisdiction-code.</t>
</li> </li>
<li> <li pn="section-2.2-9.3">
<t>in case when such multi-national or international organization do <t indent="0" pn="section-2.2-9.3.1">If a multi-national or internat
es ional organization does
not have a registered domain, Designated Expert(s) should assign not have a registered domain, the designated expert(s) should assign
something like name.lex.arpa, where name will be the something like "name.lex.arpa", where the name will be the
acronym of the organization name, in the language chosen by the organization its acronym of the organization name in the language chosen by the organization itse
elf. lf.
For example, the jurisdiction code of the European Economic Community For example, the jurisdiction-code of the European Economic Community
could be "eec.lex.arpa". could be "eec.lex.arpa". The alias mechanism allows for acronyms in different la
Anyway the alias mechanism allows to have acronyms in different languages.</t> nguages.</t>
</li> </li>
</ul> </ul>
<t>Jurisdiction codes MUST NOT be renamed, because that <t indent="0" pn="section-2.2-10">Jurisdiction-codes <bcp14>MUST NOT</bc
would violate rules that URN assignments are persistent.</t> p14> be renamed, because that
<t>Jurisdiction codes MUST NOT ever be deleted. They can only be marked would violate the rule that URN assignments be persistent.</t>
as <t indent="0" pn="section-2.2-11">Jurisdiction-codes <bcp14>MUST NOT</bc
"obsolete", i.e. closed for new assignments within the jurisdiction. p14> ever be deleted. They can only be marked as
Requests to obsolete a jurisdiction code are also processed by "obsolete", i.e., closed for new assignments within the jurisdiction.
Designated Expert(s).</t> Requests to obsolete a jurisdiction-code are also processed by
<t>Designated Expert(s) can unilaterally initiate allocation or the designated expert(s).</t>
obsolescence of a jurisdiction code.</t> <t indent="0" pn="section-2.2-12">Designated expert(s) can unilaterally
<t>Request for new jurisdiction code assignment must include initiate allocation or
the organization or country requesting it and Contact information (email) obsolescence of a jurisdiction-code.</t>
<t indent="0" pn="section-2.2-13">Requests for new jurisdiction-code ass
ignments must include
the organization or country requesting it and contact information (email)
of who requested the assignment.</t> of who requested the assignment.</t>
</section> </section>
<section anchor="conformance-with-urn-syntax"> <section anchor="conformance-with-urn-syntax" numbered="true" removeInRFC=
<name>Conformance with URN Syntax</name> "false" toc="include" pn="section-2.3">
<t>The "lex" namespace identifier (NID) syntax conforms to <name slugifiedName="name-conformance-with-urn-syntax">Conformance with
<xref target="RFC8141"/>. However, a series of characters are reserved to identi URN Syntax</name>
fy <t indent="0" pn="section-2.3-1">The LEX namespace identifier (NID) synt
ax conforms to
<xref target="RFC8141" format="default" sectionFormat="of" derivedContent="RFC81
41"/>. However, a series of characters are reserved for identifying
elements or sub-elements, or for future extensions of the LEX naming elements or sub-elements, or for future extensions of the LEX naming
convention (see <xref target="res-chars"/>).</t> convention (see <xref target="res-chars" format="default" sectionFormat="of" der ivedContent="Section 3.2"/>).</t>
</section> </section>
<section anchor="validation-mechanism"> <section anchor="validation-mechanism" numbered="true" removeInRFC="false"
<name>Validation Mechanism</name> toc="include" pn="section-2.4">
<t>The Jurisdictional Registrar (or those it delegates) of each adhering <name slugifiedName="name-validation-mechanism">Validation Mechanism</na
me>
<t indent="0" pn="section-2.4-1">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).</t> and type of legal measure).</t>
</section> </section>
<section anchor="scope"> <section anchor="scope" numbered="true" removeInRFC="false" toc="include"
<name>Scope</name> pn="section-2.5">
<t>Global interest. In fact each body that enacts sources of law can <name slugifiedName="name-scope">Scope</name>
identify them by this scheme. Furthermore, other bodies (even not <t indent="0" pn="section-2.5-1">The scope is global. In fact, each Bod
enacting sources of law, such as newspaper or magazine publishers, y that enacts sources of law can
etc.) aiming to refer legal documents, can unequivocally identify identify them by this scheme. Furthermore, other bodies (even non-enact
them by this scheme.</t> ing sources of law, such as newspapers, magazine publishers, etc.) that aim to r
eference legal documents can unequivocally identify them
by this scheme.</t>
</section> </section>
</section> </section>
<section anchor="general-syntax-and-features-of-the-lex-identifier"> <section anchor="general-syntax-and-features-of-the-lex-identifier" numbered
<name>General Syntax and Features of the LEX Identifier</name> ="true" removeInRFC="false" toc="include" pn="section-3">
<t>This section lists the general features applicable to all <name slugifiedName="name-general-syntax-and-features">General Syntax and
Features of the LEX Identifier</name>
<t indent="0" pn="section-3-1">This section lists the general features app
licable to all
jurisdictions.</t> jurisdictions.</t>
<section anchor="allowed-and-not-allowed-characters"> <section anchor="allowed-and-not-allowed-characters" numbered="true" remov
<name>Allowed and Not Allowed Characters</name> eInRFC="false" toc="include" pn="section-3.1">
<t>These characters are defined in accordance with the <xref target="RFC <name slugifiedName="name-allowed-and-not-allowed-cha">Allowed and Not A
8141"/> llowed Characters</name>
"Uniform Resource Names (URNs)". For various reasons, later <t indent="0" pn="section-3.1-1">The characters are defined in accordanc
explained, in the "lex" NSS only a subset of characters is e with <xref target="RFC8141" format="default" sectionFormat="of" derivedContent
allowed. All other characters are either eliminated or converted.</t> ="RFC8141"/>.
<t>For the full syntax of the uniform names in the "lex" space, please For various reasons that are
see <xref target="urn-lex-syn"/>.</t> explained later, only a subset of characters is
allowed in the LEX NSS. All other characters are either eliminated or converted.
</t>
<t indent="0" pn="section-3.1-2">For the full syntax of the uniform name
s in the LEX space, please
see <xref target="urn-lex-syn" format="default" sectionFormat="of" derivedConten
t="Section 8"/>.</t>
</section> </section>
<section anchor="res-chars"> <section anchor="res-chars" numbered="true" removeInRFC="false" toc="inclu
<name>Reserved Characters</name> de" pn="section-3.2">
<t>The following characters are reserved in the specific "lex" <name slugifiedName="name-reserved-characters">Reserved Characters</name
>
<t indent="0" pn="section-3.2-1">The following characters are reserved i
n the specific LEX
namespace:</t> namespace:</t>
<artwork><![CDATA[ <dl indent="6" newline="false" spacing="normal" pn="section-3.2-2">
"@" separator of the expression, that contains information on <dt pn="section-3.2-2.1">"@"</dt>
version and language; <dd pn="section-3.2-2.2">Separator of the expression that contains inf
"$" separator of the manifestation, that contains information on ormation on
format, editor, etc.; version and language.</dd>
":" separator of the main elements of the name at any entity; <dt pn="section-3.2-2.3">"$"</dt>
";" separator of level. It identifies the introduction of an element <dd pn="section-3.2-2.4">Separator of the manifestation that contains
at a hierarchically lower level, or the introduction of a information on
specification; format, editor, etc.</dd>
"+" separator of the repetitions of an entire main element (e.g., <dt pn="section-3.2-2.5">":"</dt>
multiple authorities); <dd pn="section-3.2-2.6">Separator of the main elements of the name at
"|" separator between different formats of the same element (e.g., any entity.</dd>
date); <dt pn="section-3.2-2.7">";"</dt>
"," separator of the repetitions of individual components in the main <dd pn="section-3.2-2.8">Separator of the level. It identifies the int
roduction of an element
at a hierarchically lower level or the introduction of a
specification.</dd>
<dt pn="section-3.2-2.9">"+"</dt>
<dd pn="section-3.2-2.10">Separator of the repetitions of an entire ma
in element (e.g.,
multiple authorities).</dd>
<dt pn="section-3.2-2.11">"|"</dt>
<dd pn="section-3.2-2.12">Separator between different formats of the s
ame element (e.g.,
date).</dd>
<dt pn="section-3.2-2.13">","</dt>
<dd pn="section-3.2-2.14">Separator of the repetitions of individual c
omponents in the main
elements, each bearing the same level of specificity (e.g., elements, each bearing the same level of specificity (e.g.,
multiple numbers); multiple numbers).</dd>
"~" separator of the partition identifier in references (e.g., <dt pn="section-3.2-2.15">"~"</dt>
paragraph of an article); <dd pn="section-3.2-2.16">Separator of the partition identifier in ref
"*" and "!" are reserved for future expansions. erences (e.g.,
]]></artwork> paragraph of an article).</dd>
<t>To keep backward compatibility with existing applications in some <dt pn="section-3.2-2.17">"*"</dt>
jurisdictions, the "lex" NID syntax does not include the use of the <dd pn="section-3.2-2.18">Reserved for future expansions.</dd>
character "/" in this version.<br/> <dt pn="section-3.2-2.19">"!"</dt>
This character is always converted into <dd pn="section-3.2-2.20">Reserved for future expansions.</dd>
"-", except in the formal annexes (see <xref target="annex-formal"/>).</t> </dl>
<t indent="0" pn="section-3.2-3">To keep backward compatibility with exi
sting applications in some
jurisdictions, the LEX NID syntax does not include the use of the
character "/" in this version. This character is always converted into
"-", except in the formal annexes (see <xref target="annex-formal" format="defau
lt" sectionFormat="of" derivedContent="Section 6.4.1"/>).</t>
</section> </section>
<section anchor="case-sensitivity"> <section anchor="case-sensitivity" numbered="true" removeInRFC="false" toc
<name>Case Sensitivity</name> ="include" pn="section-3.3">
<t>For all the languages where different cases (upper or lower cases) <name slugifiedName="name-case-sensitivity">Case Sensitivity</name>
or different spelling of the same word are possible, <t indent="0" pn="section-3.3-1">For all the languages where different c
names belonging to "lex" namespace are case-insensitive. ases (uppercase or lowercase)
It is RECOMMENDED that, in latin alphabet, they be created in lower case, but na or different spellings of the same word are possible, names belonging
mes that differ to LEX namespace are case-insensitive. For the Latin alphabet, it is
only in case, or in the spelling, of the same word <bcp14>RECOMMENDED</bcp14> that names be created in
MUST be considered to be equivalent<br/> lower case, but names that differ only in case or in the spelling of
(e.g., "Ministry" will be recorded as "ministry").</t> the same word <bcp14>MUST</bcp14> be considered equivalent
(e.g., "Ministry" will be recorded as "ministry").</t>
</section> </section>
<section anchor="non-ascii-char"> <section anchor="non-ascii-char" numbered="true" removeInRFC="false" toc="
<name>Unicode Characters outside the ASCII Range</name> include" pn="section-3.4">
<t>In order to exploit DNS as a routing tool towards the proper <name slugifiedName="name-unicode-characters-outside-">Unicode Character
resolution system, to keep editing and communication more simple and s Outside the ASCII Range</name>
to avoid character percent-encoding, it is RECOMMENDED that the characters outsi <t indent="0" pn="section-3.4-1">In order to exploit the DNS as a routin
de the ASCII range g tool towards the proper
(e.g. national characters, diacritic signs, ...) are turned into base ASCII resolution system, keep editing and communication more simple, and avoid charact
characters (e.g., the Italian term "sanitU+00E0" replaced into er percent-encoding, it is <bcp14>RECOMMENDED</bcp14> that characters outside th
"sanita", the French term "ministU+00E8re" replaced into e ASCII range
"ministere"), in case by transliteration (e.g. "MU+00FCnchen" (e.g., national characters, diacritic signs, etc.) are turned into base ASCII
characters (e.g., the Italian term "sanità" (sanitU+00E0)" replaced into
"sanita", the French term "ministère" (ministU+00E8re) replaced into
"ministere", in case by transliteration (e.g., "München" (MU+00FCnchen)
replaced into "muenchen").</t> replaced into "muenchen").</t>
<t>This mapping consists of:</t> <t indent="0" pn="section-3.4-2">This mapping consists of:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3
<li> .4-3">
<t>transcription from non-Latin alphabets;</t> <li pn="section-3.4-3.1">
<t indent="0" pn="section-3.4-3.1.1">Transcription from non-Latin al
phabets</t>
</li> </li>
<li> <li pn="section-3.4-3.2">
<t>transliteration of some signs (diaeresis, eszett, ...);</t> <t indent="0" pn="section-3.4-3.2.1">Transliteration of some signs (
e.g., diaeresis and eszett)</t>
</li> </li>
<li> <li pn="section-3.4-3.3">
<t>preservation of the only basic characters, eliminating the signs <t indent="0" pn="section-3.4-3.3.1">Preservation of only the basic
placed above (accents, tilde, ...), below (cedilla, little tail, characters, eliminating the signs
...) or on (oblique cut, ...).</t> placed above (e.g., accents and tilde), below (e.g., cedilla and little tail), o
r on (e.g., oblique cut)</t>
</li> </li>
</ul> </ul>
<t>The most suitable, well-known and widespread mapping system for a giv <t indent="0" pn="section-3.4-4">The most suitable, well-known, and wide
en language MUST be chosen by the spread mapping system for a given
jurisdiction, or, in agreement with this one, by the jurisdiction-unit in language <bcp14>MUST</bcp14> be chosen by the jurisdiction or by the
case of different languages in the various regions, jurisdiction-unit (in agreement with the jurisdiction) in the case of
also taking into account the choices made for the same language by other jurisdi different languages in various regions, also taking into account the choices
ctions.<br/> made for the same language by other jurisdictions. This mapping is simpler
Certainly this mapping is simpler and more feasible for languages that and more feasible for languages that use the Latin alphabet and gradually
use the Latin alphabet and gradually becomes more complex both for becomes more complex for other alphabets and for writing systems that use
other alphabets and for writing systems with opposite orientation opposite orientation (from right to left) or are based on ideographic
(from right to left) or based on ideographic symbols.</t> symbols.</t>
<t>If this conversion is not acceptable by a specific jurisdiction or it <t indent="0" pn="section-3.4-5">If this conversion is not acceptable by
is a specific jurisdiction or
not available in a given language, UNICODE MUST be used and, for accessing it is not available in a given language, Unicode <bcp14>MUST</bcp14>
network protocols, any UNICODE code points outside the ASCII range MUST be be used, and for accessing network protocols, any Unicode code points
converted in UTF-8 %-encoding according to <xref target="RFC3986"/> and <xref ta outside the ASCII range <bcp14>MUST</bcp14> be converted to UTF-8
rget="RFC3629"/>.<br/> percent-encoding according to <xref target="RFC3986" format="default" se
In this case it should be noted that the generated URN (as some ctionFormat="of" derivedContent="RFC3986"/> and <xref target="RFC3629" format="d
of its parts) cannot be used directly for routing through DNS, and efault" sectionFormat="of" derivedContent="RFC3629"/> .</t>
therefore the jurisdiction must adopt one of the following <t indent="0" pn="section-3.4-6">In this case, it should be noted that t
strategies:</t> he
<ul spacing="normal"> generated URN (as well as some of its parts) cannot be used directly for
<li> routing through the DNS. Therefore, the jurisdiction must adopt one of
<t>to convert non-ASCII characters within the DNS into the IDN the following strategies:</t>
encoding, using the <xref target="RFC5894"/> punycode translation (e.g. <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3
mU+00FCnchen in xn--mnchen-3ya), and to develop a .4-7">
software interface that converts the URN before the navigation in DNS, or</t> <li pn="section-3.4-7.1">
<t indent="0" pn="section-3.4-7.1.1">Convert non-ASCII characters wi
thin the DNS into IDN
encoding using Punycode translation <xref target="RFC5894" format="default" sect
ionFormat="of" derivedContent="RFC5894"/> (e.g.,
"münchen" (mU+00FCnchen) in xn--mnchen-3ya) and develop a
software interface that converts the URN before the navigation in the DNS.</t>
</li> </li>
<li> <li pn="section-3.4-7.2">
<t>to create a routing service relying on a software, out of DNS, <t indent="0" pn="section-3.4-7.2.1">Create a routing service relyin
addressing a proper resolution service.</t> g on a software, outside of the DNS,
that addresses a proper resolution service.</t>
</li> </li>
</ul> </ul>
<t>Note that the urn:lex ID, could contain groups of characters (UTF-8 % <t indent="0" pn="section-3.4-8">Note that the LEX URN ID could contain
-encoded) groups of characters (UTF-8 percent-encoded)
of some languages with different orientations: in this case the BiDi rules apply of some languages with different orientations. In this case, the BiDi rules appl
<xref target="RFC5893"/>.</t> y <xref target="RFC5893" format="default" sectionFormat="of" derivedContent="RFC
<t>Summarizing, the preference order is the following:</t> 5893"/>.</t>
<ul spacing="normal"> <t indent="0" pn="section-3.4-9">The preferred order is summarized as fo
<li> llows:</t>
<t>Conversion into basic ASCII, RECOMMENDED solution (for not having <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3
to make conversions .4-10">
for network protocols and DNS);</t> <li pn="section-3.4-10.1">
<t indent="0" pn="section-3.4-10.1.1">Conversion into basic ASCII is
the <bcp14>RECOMMENDED</bcp14> solution (because
conversions for network protocols and the DNS are not needed).</t>
</li> </li>
<li> <li pn="section-3.4-10.2">
<t>Using UNICODE, and convert into UTF-8 %-encoding <xref target="RF <t indent="0" pn="section-3.4-10.2.1">Using Unicode and converting t
C3629"/>, for accessing network protocols, o UTF-8 percent-encoding <xref target="RFC3629" format="default" sectionFormat="
and to punycode <xref target="RFC5894"/>, only for navigation in DNS, via softwa of" derivedContent="RFC3629"/> for accessing network protocols
re interface;</t> and to Punycode <xref target="RFC5894" format="default" sectionFormat="of" deriv
edContent="RFC5894"/> only for navigation in DNS via software interface.</t>
</li> </li>
<li> <li pn="section-3.4-10.3">
<t>Creation of a routing service relying on a software, out of DNS, <t indent="0" pn="section-3.4-10.3.1">Creation of a routing service
addressing a proper resolution service.</t> relying on a software outside of DNS
and addressing a proper resolution service.</t>
</li> </li>
</ul> </ul>
<t>The first solution allows native DNS routing, while the other two <t indent="0" pn="section-3.4-11">The first solution allows native DNS r
require software development for the interface or the routing. outing while the other two
However it is up to the specific jurisdiction to choose the preferred solutions require software development for the interface or the routing.
However, it is up to the specific jurisdiction to choose the preferred
solution.</t> solution.</t>
<t>Two examples (Latin and Cyrillic alphabet) relating to the different <t indent="0" pn="section-3.4-12">The following are two examples (Latin
solutions adopted are here reported:</t> and Cyrillic alphabets) relating to the different
<artwork><![CDATA[ solutions adopted:</t>
a circular adopted by the Municipality of Munich (Rundschreiben der <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3
Stadt MU+00FCnchen): .4-13">
- ascii = urn:lex:de:stadt.munchen:rundschreiben:... <li pn="section-3.4-13.1">
- unicode = urn:lex:de:stadt.mU+00FCnchen:rundschreiben:... <t indent="0" pn="section-3.4-13.1.1">A circular adopted by the Muni
- utf-8 = urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben:... cipality of Munich (Rundschreiben der
- punycode = urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben:... Stadt "München" (MU+00FCnchen)):</t>
]]></artwork> <artwork align="left" pn="section-3.4-13.1.2">
<artwork><![CDATA[ - ASCII: urn:lex:de:stadt.munchen:rundschreiben:...;
a state law of the Russian Federation (latin: gosudarstvo zakon; - Unicode: urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...;
cyrillic: U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435 - UTF-8: urn:lex:de:stadt.m%C3%BCnchen:rundschreiben:...;
U+0437U+0430U+043AU+043EU+043D): - PUNYCODE: urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben:...
- ascii = urn:lex:ru:gosudarstvo:zakon:... </artwork>
- unicode = urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D </li>
U+0438U+0435:U+0437U+0430U+043AU+043EU+043D:... <li pn="section-3.4-13.2">
- utf-8 = urn:lex:ru:%xD1%x81%xD0%xBE%xD1%x81%xD1%x82%xD0%xBE%xD1 <t indent="0" pn="section-3.4-13.2.1">A state law of the Russian Fed
%x8F%xD0%xBD%xD0%xB8%xD0%xB5:%xD0%xB7%xD0%xB0%xD0%xBA eration (Latin: gosudarstvo zakon;
%xD0%xBE%xD0%xBD:... Cyrillic: "состояние закон" (U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0
- punycode = urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme:... 435
U+0437U+0430U+043AU+043EU+043D)), assuming that
assuming that the Russia jurisdiction-code is expressed the Russia jurisdiction-code is expressed in ASCII ("ru")
in ASCII ("ru"), (while the Cyrillic version would be "рф" (U+0440U+0444)):</t>
while the Cyrillic version ("U+0440U+0444") has the <artwork align="left" pn="section-3.4-13.2.2">
puny-code "xn--p1ai". - ASCII: urn:lex:ru:gosudarstvo:zakon:...
]]></artwork> - 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:%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:...
</artwork>
</li>
</ul>
</section> </section>
<section anchor="abbreviations"> <section anchor="abbreviations" numbered="true" removeInRFC="false" toc="i
<name>Abbreviations</name> nclude" pn="section-3.5">
<t>Abbreviations are often used in law for indicating institutions (e.g. <name slugifiedName="name-abbreviations">Abbreviations</name>
Min.), structures (e.g. Dept.), or legal measures (e.g. Reg.) but not <t indent="0" pn="section-3.5-1">Abbreviations are often used in law for
in a uniform way, therefore their expansion is highly RECOMMENDED<br/> indicating institutions (e.g.,
(e.g., "Min." is reported as "ministry").</t> Min.), structures (e.g., Dept.), or legal measures (e.g., Reg.), but they are no
t
used in a uniform way. Therefore, their expansion is highly <bcp14>RECOMMENDED</
bcp14>
(e.g., "Min." is expanded as "ministry").</t>
</section> </section>
<section anchor="dat-form"> <section anchor="dat-form" numbered="true" removeInRFC="false" toc="includ
<name>Date Format</name> e" pn="section-3.6">
<t>The <xref target="ISO.8601.1988"/> is the international format for re <name slugifiedName="name-date-format">Date Format</name>
presenting dates: <t indent="0" pn="section-3.6-1"><xref target="ISO.8601-1.2019" format="
therefore dates MUST always be represented in this format (4 digits for the year default" sectionFormat="of" derivedContent="ISO.8601-1.2019"/> and <xref target=
, "ISO.8601-2.2019" format="default" sectionFormat="of" derivedContent="ISO.8601-2
2 digits for the month, 2 digits for the day):</t> .2019"/> describe the international format for representing dates. Dates <bcp14>
<artwork><![CDATA[ MUST</bcp14> always be represented in this format (4 digits for the year,
date-iso = yyyy-mm-dd 2 digits for the month, and 2 digits for the day):</t>
]]></artwork> <sourcecode type="abnf" markers="false" pn="section-3.6-2">
<t>(e.g., "September 2, 99" will be written as "1999-09-02").</t> date-iso = year "-" month "-" day
<t>This format ensures interoperability between different representation </sourcecode>
systems and <t indent="0" pn="section-3.6-3">For example, "September 2, 99" will be
there are several programs for mapping other formats to this one.<br/> written as "1999-09-02".</t>
However, to make reading and understanding such other formats (e.g. Jewish calen <t indent="0" pn="section-3.6-4">This format ensures interoperability be
dar), tween different
the urn:lex scheme provides that the date can be added in the jurisdiction's own representation systems and there are several programs for mapping
format<br/> other formats to this one. However, to make reading and understanding
(e.g. the date in the previous example would be 21.Elul,5759, that is:</t> such other formats (e.g., Jewish calendar), the LEX URN scheme
<artwork><![CDATA[ provides that the date can be added in the jurisdiction's own format.
- in Hebrew characters: The date in the previous example (1999-09-02) would be as follows:</t>
"U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.U+05EA <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3
U+05E9U+05E0U+05F4U+05D8"; .6-5">
- in UTF-8 code: <li pn="section-3.6-5.1">
"%x5c%x75%x30%x35%x44%x42%x5c%x75%x30%x35%x46%x34%x5c%x75%x30%x35 <t indent="0" pn="section-3.6-5.1.1">in Hebrew characters (21 Elul 5
%x44%x30%x2e%x5c%x75%x30%x35%x44%x30%x5c%x75%x30%x35%x42%x31%x5c 759):</t>
%x75%x30%x35%x44%x43%x5c%x75%x30%x35%x44%x35%x5c%x75%x30%x35%x42 <artwork align="left" pn="section-3.6-5.1.2">כ״א-בֶּאֱלוּל-תשנ״ט
%x43%x5c%x75%x30%x35%x44%x43%x2e%x5c%x75%x30%x35%x45%x41%x5c%x75 </artwork>
%x30%x35%x45%x39%x5c%x75%x30%x35%x45%x30%x5c%x75%x30%x35%x46%x34 <t indent="0" pn="section-3.6-5.1.3">Note that the example above use
%x5c%x75%x30%x35%x44%x38"). s right-to-left (RTL) script, which in the context of this specification may be
]]></artwork> displayed differently by different document presentation environments. The descr
<t>Therefore, for all the dates in the urn:lex identifier iptive text may be more reliable to follow than the necessarily device- and appl
(see <xref target="det-elem"/> and <xref target="ide-vers"/>), ication-specific rendering.</t>
it is also possible to indicate the one in the local format:</t> </li>
<artwork><![CDATA[ <li pn="section-3.6-5.2">
date = date-iso [ "|" date-loc ] <t indent="0" pn="section-3.6-5.2.1">in U+ notation:</t>
]]></artwork> <artwork align="left" pn="section-3.6-5.2.2">
<t>(e.g., "September 2, 99" will be written in ISO plus Hebrew format as U+05D8U+05F4U+05E0U+05E9U+05EAU+002DU+05DCU+05D5U+05BCU+05DC
<br/> U+05D0U+05B1U+05D1U+05B6U+05BCU+002DU+05D0U+05F4U+05DB
"1999-09-02|U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC. </artwork>
U+05EAU+05E9U+05E0U+05F4U+05D8").</t> </li>
<t>The characters which are not allowed (e.g. "/") or which are reserved <li pn="section-3.6-5.3">
(e.g. ",") cannot exist <t indent="0" pn="section-3.6-5.3.1">in UTF-8 code:</t>
inside the date-loc and therefore MUST be turned into ".".</t> <artwork align="left" pn="section-3.6-5.3.2">
%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
</artwork>
</li>
</ul>
<t indent="0" pn="section-3.6-6">Therefore, for all the dates in the LEX
URN identifier
(see Sections <xref target="det-elem" format="counter" sectionFormat="of" derive
dContent="6.3"/> and <xref target="ide-vers" format="counter" sectionFormat="of"
derivedContent="7.1.2"/>),
it is possible to indicate the date in the local format:</t>
<sourcecode type="abnf" markers="false" pn="section-3.6-7">
date = date-iso ["|" date-loc]
</sourcecode>
<t indent="0" pn="section-3.6-8">For example, 1999-09-02 will be written
in ISO plus Hebrew format as:</t>
<artwork align="left" pn="section-3.6-9">1999-09-02|כ״א-בֶּאֱלוּל-תשנ״ט<
/artwork>
<t indent="0" pn="section-3.6-10">which is to be converted into UTF-8 fo
r network protocols and for resolution (see <xref target="non-ascii-char" format
="default" sectionFormat="of" derivedContent="Section 3.4"/>). The characters th
at are not allowed (e.g., "/") or reserved (e.g., ",") cannot exist
inside the date-loc and therefore <bcp14>MUST</bcp14> be turned into ".". To be
aligned with ISO format, any blank between day, month, and year <bcp14>MUST</bcp
14> be converted into "-".</t>
<t indent="0" pn="section-3.6-11">In the above Hebrew character examples
, the sequence of characters is
<u format="lit-name-num" pn="u-1">כ</u>,
<u format="lit-name-num" pn="u-2">״</u>,
<u format="lit-name-num" pn="u-3">א</u>,
<u format="lit-name-num" pn="u-4">-</u>,
<u format="lit-name-num" pn="u-5">בֶּ</u>,
<u format="lit-name-num" pn="u-6">אֱ</u>,
<u format="lit-name-num" pn="u-7">ל</u>,
<u format="lit-name-num" pn="u-8">וּ</u>,
<u format="lit-name-num" pn="u-9">ל</u>,
<u format="lit-name-num" pn="u-10">-</u>,
<u format="lit-name-num" pn="u-11">ת</u>,
<u format="lit-name-num" pn="u-12">ש</u>,
<u format="lit-name-num" pn="u-13">נ</u>,
<u format="lit-name-num" pn="u-14">״</u>,
and <u format="lit-name-num" pn="u-15">ט</u>.</t>
</section> </section>
</section> </section>
<section anchor="specific-syntax-and-features-of-the-lex-identifier"> <section anchor="specific-syntax-and-features-of-the-lex-identifier" numbere
<name>Specific Syntax and Features of the LEX Identifier</name> d="true" removeInRFC="false" toc="include" pn="section-4">
<t>In this section there are other features related to specific <name slugifiedName="name-specific-syntax-and-feature">Specific Syntax and
jurisdictions and the implementation of which is RECOMMENDED.</t> Features of the LEX Identifier</name>
<section anchor="spaces-connectives-and-punctuation-marks"> <t indent="0" pn="section-4-1"> This section discusses features related to
<name>Spaces, Connectives and Punctuation Marks</name> specific
<t>All the language connectives (e.g., articles, prepositions, etc.), jurisdictions. The implementation of these features is
the punctuation marks and all the special characters (as apostrophes, <bcp14>RECOMMENDED</bcp14>.</t>
dashes, etc.), when explicitly present, are eliminated (no <section anchor="spaces-connectives-and-punctuation-marks" numbered="true"
transformation occurs in cases of languages with declensions or removeInRFC="false" toc="include" pn="section-4.1">
agglutinating languages). The words left are connected to each other <name slugifiedName="name-spaces-connectives-and-punc">Spaces, Connectiv
by a dot (".") which substitutes the "space".<br/> es, and Punctuation Marks</name>
(e.g., "Ministry of Finances, Budget and of Economic Planning" <t indent="0" pn="section-4.1-1">When explicitly present, all language c
becomes "ministry.finances.budget.economic.planning";<br/> onnectives (e.g., articles, prepositions, etc.), punctuation marks, and special
"Ministerstvo Finansov" becomes "ministerstvo.finansov")</t> characters (e.g., apostrophes, dashes, etc.) are eliminated (no
transformation occurs in cases of languages with declensions or
agglutinating languages). The words that are left are connected to
each other by a dot ("."), which substitutes for the space (e.g.,
"Ministry of Finances, Budget, and Economic Planning" becomes
"ministry.finances.budget.economic.planning" and "Ministerstvo Finansov"
becomes "ministerstvo.finansov").</t>
</section> </section>
<section anchor="acronyms"> <section anchor="acronyms" numbered="true" removeInRFC="false" toc="includ
<name>Acronyms</name> e" pn="section-4.2">
<t>The use of acronyms might be confusing and encourage ambiguity in <name slugifiedName="name-acronyms">Acronyms</name>
<t indent="0" pn="section-4.2-1">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<br/> <bcp14>RECOMMENDED</bcp14>
(e.g., "FAO" is expanded as "food.agriculture.organization").</t> (e.g., "FAO" is expanded as "food.agriculture.organization").</t>
</section> </section>
<section anchor="ordinal-numbers"> <section anchor="ordinal-numbers" numbered="true" removeInRFC="false" toc=
<name>Ordinal Numbers</name> "include" pn="section-4.3">
<t>To even the representation, it is highly RECOMMENDED that any ordinal <name slugifiedName="name-ordinal-numbers">Ordinal Numbers</name>
number included in a component of a document name (e.g., in the <t indent="0" pn="section-4.3-1">To standardise the representation, it i
description of an institution body) is indicated in Western Arabic s highly <bcp14>RECOMMENDED</bcp14> that any ordinal
numerals, regardless to the original expression: whether in Roman number included in a component of a document name (e.g., in the
numerals, or with an adjective, or in Arabic numeral with apex, etc. description of an institution Body) is indicated in Western Arabic
(IV, third, 1U+00B0, 2^, etc.)<br/> numerals, regardless to the original expression, whether Roman
(e.g., "Department IV" becomes "department.4").</t> numerals, an adjective, Arabic numerals with an apex, etc.
(such as IV, third, 1° (1U+00B0), and 2^). For example, "Department IV" becomes
"department.4".</t>
</section> </section>
</section> </section>
<section anchor="creation"> <section anchor="creation" numbered="true" removeInRFC="false" toc="include"
<name>Creation of the Source of Law LEX Identifier - Baseline structure</n pn="section-5">
ame> <name slugifiedName="name-creation-of-the-source-of-l">Creation of the Sou
<section anchor="basic-principles"> rce of Law LEX Identifier: Baseline Structure</name>
<name>Basic Principles</name> <section anchor="basic-principles" numbered="true" removeInRFC="false" toc
<t>The uniform name must identify one and only one document (more ="include" pn="section-5.1">
precisely a "bibliographic resource" <xref target="ISBD"/>, see also <xref targe <name slugifiedName="name-basic-principles">Basic Principles</name>
t="src-law"/>) <t indent="0" pn="section-5.1-1">The uniform name must identify one and
only one document (more
precisely a "bibliographic resource" <xref target="ISBD" format="default" sectio
nFormat="of" derivedContent="ISBD"/>; see also <xref target="src-law" format="de
fault" sectionFormat="of" derivedContent="Section 5.2"/>)
and is created in such a way that it is:</t> and is created in such a way that it is:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<li> .1-2">
<t>self-explanatory;</t> <li pn="section-5.1-2.1">
<t indent="0" pn="section-5.1-2.1.1">self-explanatory,</t>
</li> </li>
<li> <li pn="section-5.1-2.2">
<t>identifiable through simple and clear rules;</t> <t indent="0" pn="section-5.1-2.2.1">identifiable through simple and
clear rules,</t>
</li> </li>
<li> <li pn="section-5.1-2.3">
<t>compatible with the practice commonly used for references;</t> <t indent="0" pn="section-5.1-2.3.1">compatible with the practice co
mmonly used for references,</t>
</li> </li>
<li> <li pn="section-5.1-2.4">
<t>able to be created from references in the text, automatically (by <t indent="0" pn="section-5.1-2.4.1">able to be created from referen
parser) or manually;</t> ces in the text, automatically (by
parser) or manually, and</t>
</li> </li>
<li> <li pn="section-5.1-2.5">
<t>representative of both the formal and the substantive aspects of <t indent="0" pn="section-5.1-2.5.1">representative of both the form
al and the substantive aspects of
the document.</t> the document.</t>
</li> </li>
</ul> </ul>
</section> </section>
<section anchor="src-law"> <section anchor="src-law" numbered="true" removeInRFC="false" toc="include
<name>Model of Sources of Law Representation</name> " pn="section-5.2">
<t>According to the <xref target="FRBR"/> (Functional Requirements for B <name slugifiedName="name-model-of-sources-of-law-rep">Model of Sources
ibliographic of Law Representation</name>
Records) model developed by IFLA (International Federation of Library <t indent="0" pn="section-5.2-1">According to the Functional Requirement
Associations and Institutions), in a source of law, as in any s for Bibliographic Records
intellectual production, four fundamental entities (or aspects) can be (FRBR) <xref target="FRBR" format="default" sectionFormat="of" derivedCo
specified.</t> ntent="FRBR"/> model developed by IFLA (International
<t>The first two entities reflect its contents:</t> Federation of Library Associations and Institutions), four
<ul spacing="normal"> fundamental entities (or aspects) can be specified in a source of law,
<li> as in any intellectual production.</t>
<t>work: identifies a distinct intellectual creation; in our case, i <t indent="0" pn="section-5.2-2">The first two entities reflect its cont
t ents:</t>
identifies a source of law both in its original form <dl spacing="normal" indent="3" newline="false" pn="section-5.2-3">
as amended over time;</t> <dt pn="section-5.2-3.1">work:</dt>
</li> <dd pn="section-5.2-3.2">Identifies a distinct intellectual creation;
<li> in this document, it
<t>expression: identifies a specific intellectual realisation of a identifies a source of law in both its original form and its amended
work; in our case it identifies every different (original or form over time.</dd>
<dt pn="section-5.2-3.3">expression:</dt>
<dd pn="section-5.2-3.4">Identifies a specific intellectual realizatio
n of a
work; in this document, it identifies every different (original or
up-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 in
which the text is expressed.</t> which the text is expressed.</dd>
</li> </dl>
</ul> <t indent="0" pn="section-5.2-4">The other two entities relate to its fo
<t>The other two entities relate to its form:</t> rm:</t>
<ul spacing="normal"> <dl spacing="normal" indent="3" newline="false" pn="section-5.2-5">
<li> <dt pn="section-5.2-5.1">manifestation:</dt>
<t>manifestation: identifies a physical embodiment of an expression <dd pn="section-5.2-5.2">Identifies a physical embodiment of an expres
of a work; sion of a work;
in our case it identifies embodiments in different media in this document, it identifies embodiments in different media
(printing, digital, etc.), encoding formats (XML, PDF, etc.), (printing, digital, etc.), encoding formats (XML, PDF, etc.),
or other publishing characteristics;</t> or other publishing characteristics.</dd>
</li> <dt pn="section-5.2-5.3">item:</dt>
<li> <dd pn="section-5.2-5.4">Identifies a specific copy of a manifestation
<t>item: identifies a specific copy of a manifestation; in our case ; in this document, it
it
identifies individual physical copies as they are found in identifies individual physical copies as they are found in
particular physical locations.</t> particular physical locations.</dd>
</li> </dl>
</ul> <t indent="0" pn="section-5.2-6">In this document, the <xref target="FRB
<t>In this document the <xref target="FRBR"/> model has been interpreted R" format="default" sectionFormat="of" derivedContent="FRBR"/> model has been in
for the terpreted 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, provide with respect to the involved actors (citizens, parties,
institutions). In this scenario the main characteristic of the and 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 may during which it provides the same juridical effects. These effects may
change as a result of amendments or annulments of other legislative or change as a result of amendments or annulments of other legislative or
jurisprudential acts. Therefore notes, summarizations, comments, jurisprudential acts. Therefore, notes, summaries, comments,
anonymizations and other editorial activities over the same text do anonymizations, and other editorial activities over the same text do
not produce different expressions, but different manifestations.</t> not produce different expressions. Instead, they produce different manifestation
s.</t>
</section> </section>
<section anchor="the-structure-of-the-local-name"> <section anchor="the-structure-of-the-local-name" numbered="true" removeIn
<name>The Structure of the Local Name</name> RFC="false" toc="include" pn="section-5.3">
<t>The local-name within the "lex" namespace MUST contain all the <name slugifiedName="name-structure-of-the-local-name">Structure of the
Local-Name</name>
<t indent="0" pn="section-5.3-1">The local-name within the LEX namespace
<bcp14>MUST</bcp14> 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 identification of a legal document. If the local-name violates
this requirement, the related URN is not a valid one within the "lex" this requirement, the related URN is not a valid one within the LEX
namespace.</t> namespace.</t>
<t>In the legal domain, at "work" level, three components are always <t indent="0" pn="section-5.3-2">In the legal domain, three components a
present: the enacting authority, the type of provision and the re always
details. A fourth component, the annex, can be added if any. present at the "work" level: the enacting authority, the measure type, and the
details. A fourth component, the annex, is added if any.
It is often necessary to differentiate various expressions, that is:</t> It is often necessary to differentiate various expressions, that is:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<li> .3-3">
<t>the original version and all the amended versions of the same <li pn="section-5.3-3.1">
document;</t> <t indent="0" pn="section-5.3-3.1.1">the original version and all th
e amended versions of the same
document, and</t>
</li> </li>
<li> <li pn="section-5.3-3.2">
<t>the versions of the text expressed in the different official <t indent="0" pn="section-5.3-3.2.1">the versions of the text expres
sed in the different official
languages of the state or organization.</t> languages of the state or organization.</t>
</li> </li>
</ul> </ul>
<t>Finally the uniform name allows a distinction among diverse <t indent="0" pn="section-5.3-4">Finally, the uniform name allows a dist
manifestations, which may be produced by multiple publishers using inction among diverse
manifestations that may be produced by multiple publishers using
different means and formats.</t> different means and formats.</t>
<t>In every case, the basic identifier of the source of law (work) <t indent="0" pn="section-5.3-5">In every case, the basic identifier of the source of law (work)
remains the same, but information is added regarding the specific remains the same, but information is added regarding the specific
version under consideration (expression); similarly a suffix is added version under consideration (expression). Similarly, a suffix is added
to the expression for representing the characteristics of the to the expression for representing the characteristics of the
publication (manifestation).</t> publication (manifestation).</t>
<t>Information that forms a source of law uniform name at each level <t indent="0" pn="section-5.3-6">Information that forms a uniform name f
(work, expression, manifestation) is expressed in the official or a source of law at each level
language of the relevant jurisdiction; in case of multiple official (work, expression, and manifestation) is expressed in the official
language of the relevant jurisdiction. More language-dependent names (aliases) a
re
created in cases where there are multiple official
languages (as in Switzerland) or more involved jurisdictions (as in languages (as in Switzerland) or more involved jurisdictions (as in
international treaties), more language-dependent names (aliases) are international treaties).</t>
created.</t> <t indent="0" pn="section-5.3-7">Therefore, the more general structure o
<t>Therefore, the more general structure of the local name appears as f the local-name appears as
follows:</t> follows:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-5.3-8">
local-name = work ["@" expression] ["$" manifestation] local-name = work ["@" expression] ["$" manifestation]
]]></artwork> </sourcecode>
<t>However, consistent with legislative practice, the uniform name of <t indent="0" pn="section-5.3-9">However, consistent with legislative pr
actice, 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 which includes: the original main document, entire class of documents that includes the following: the original main documen
the annexes, and all their versions, languages and formats t,
subsequently generated.</t> the annexes, and all the versions, languages, and formats
that are subsequently generated.</t>
</section> </section>
<section anchor="structure-of-the-document-identifier-at-work-level"> <section anchor="structure-of-the-document-identifier-at-work-level" numbe
<name>Structure of the Document Identifier at "Work" Level</name> red="true" removeInRFC="false" toc="include" pn="section-5.4">
<t>The structure of the document identifier is comprised of the four <name slugifiedName="name-structure-of-the-document-i">Structure of the
Document Identifier at "Work" Level</name>
<t indent="0" pn="section-5.4-1">The structure of the document identifie
r is comprised of the four
fundamental elements mentioned above, distinguished one from fundamental elements mentioned above, distinguished one from
the other, ordered by increasingly narrow the other and ordered by increasingly narrow
domains and competencies:</t> domains and competencies:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-5.4-2">
work = authority ":" measure ":" details *(":" annex) work = authority ":" measure ":" details *(":" annex)
]]></artwork> </sourcecode>
<t>where:</t> <t indent="0" pn="section-5.4-3">where:</t>
<ul spacing="normal"> <dl newline="false" spacing="normal" indent="3" pn="section-5.4-4">
<li> <dt pn="section-5.4-4.1">authority:</dt>
<t>authority is the issuing or proposing authority of the measure <dd pn="section-5.4-4.2">The issuing or proposing authority of the mea
(e.g., State, Ministry, Municipality, Court, etc.);</t> sure
</li> (e.g., state, ministry, municipality, court, etc.).</dd>
<li> <dt pn="section-5.4-4.3">measure:</dt>
<t>measure is the type of the measure, both public nature (e.g., <dd pn="section-5.4-4.4">The type of the measure, both public (e.g.,
constitution, act, treaty, regulation, decree, decision, etc.) as constitution, act, treaty, regulation, decree, decision, etc.) and
well as private one (e.g., license, agreement, etc);</t> private (e.g., license, agreement, etc.).</dd>
</li> <dt pn="section-5.4-4.5">details:</dt>
<li> <dd pn="section-5.4-4.6">The terms associated with the measure, typica
<t>details are the terms associated to the measure, typically the da lly the date
te
(usually the signature date) and the number included in the heading (usually the signature date) and the number included in the heading
of the act;</t> of the act.</dd>
</li> <dt pn="section-5.4-4.7">annex:</dt>
<li> <dd pn="section-5.4-4.8">The identifier of the annex, if any (e.g., An
<t>annex is the identifier of the annex, if any (e.g., Annex 1).</t> nex 1).</dd>
</li> </dl>
</ul> <t indent="0" pn="section-5.4-5">Both the main document and its annexes
<t>In case of annexes, both the main document and its annexes have their have their
own uniform name so that they can individually be referenced; the own uniform names so that they can be referenced individually; the
identifier of the annex adds a suffix to that of the main document. identifier of the annex adds a suffix to that of the main document.
In similar way the identifier of an annex of an annex adds an ending In a similar way, the identifier of an annex of an annex adds an ending
to that of the annex which it is attached to.</t> to that of the annex that it is attached to.
<t>The main elements of the work name are generally divided into several </t>
<t indent="0" pn="section-5.4-6">The main elements of the work name are
generally divided into several
elementary components, and for each component, specific rules of elementary components, and for each component, specific rules of
representation are established (criteria, modalities, syntax and representation are established (criteria, modalities, syntax, and
order). order).
For the details regarding each element, please see the <xref target="syn-work"/> For the details regarding each element, see <xref target="syn-work" format="defa
. ult" sectionFormat="of" derivedContent="Section 6"/>.
Examples (hypothetical) of work identifiers are:</t> The following are hypothetical examples of work identifiers:</t>
<artwork><![CDATA[ <artwork align="left" pn="section-5.4-7">
urn:lex:it:stato:legge:2006-05-14;22 urn:lex:it:stato:legge:2006-05-14;22
urn:lex:uk:ministry.justice:decree:1999-10-07;45 urn:lex:uk:ministry.justice:decree:1999-10-07;45
urn:lex:ch;glarus:regiere:erlass:2007-10-15;963 urn:lex:ch;glarus:regiere:erlass:2007-10-15;963
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
]]></artwork> </artwork>
<t>The type of measure is important to identify <t indent="0" pn="section-5.4-8">The type of measure is important to ide
case law, as well as legislation, especially within the legal systems ntify
where cases are identified traditionally only through the year of case law and legislation, especially within legal systems
release and a number. Since the aim of the lex schema is to where cases are traditionally identified only through the year of
release and a number. Since the aim of the LEX schema is to
identify specific materials, the type of measure or the full date are identify specific materials, the type of measure or the full date are
able to differentiate between materials belonging to a able to differentiate between materials belonging to a
specific case.</t> specific case.</t>
<t>Here below is an example where the type of measure or the full date <t indent="0" pn="section-5.4-9">The following is an example where the t ype of measure or the full date
are essential for identify specific materials of a case:</t> are essential for identify specific materials of a case:</t>
<artwork><![CDATA[ <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
- 4/59 Judgment of the EEC Court of Justice 04/04/1960, Mannesmann .4-10">
AG and others / ECSC High Authority <li pn="section-5.4-10.1">
<t indent="0" pn="section-5.4-10.1.1">4/59 Judgment of the EEC Court
of Justice 04/04/1960, Mannesmann AG and others / ECSC High Authority</t>
<artwork align="left" pn="section-5.4-10.1.2">
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
- 4/59 Order of the EEC Court of Justice 18/05/1960, Mannesmann AG </artwork>
and others / ECSC High Authority </li>
<li pn="section-5.4-10.2">
<t indent="0" pn="section-5.4-10.2.1">4/59 Order of the EEC Court of
Justice 18/05/1960, Mannesmann AG and others / ECSC High Authority</t>
<artwork align="left" pn="section-5.4-10.2.2">
urn:lex:eec.lex.arpa:court.justice:order:1960-05-18;4-59 urn:lex:eec.lex.arpa:court.justice:order:1960-05-18;4-59
]]></artwork> </artwork>
</li>
</ul>
</section> </section>
<section anchor="aliases"> <section anchor="aliases" numbered="true" removeInRFC="false" toc="include
<name>Aliases</name> " pn="section-5.5">
<t>International treaties involve multiple signatory jurisdictions, <name slugifiedName="name-aliases">Aliases</name>
<t indent="0" pn="section-5.5-1">International treaties involve multiple
signatory jurisdictions
and are therefore represented through multiple identifiers, each of them related and are therefore represented through multiple identifiers, each of them related
to a signatory. For example, a bilateral France and to a signatory. For example, a bilateral France and
Germany treaty is identified through two URNs (aliases) belonging to Germany treaty is identified through two URNs (aliases) belonging to
either "fr" or "de" jurisdiction<br/> either the "fr" or "de" jurisdiction
(e.g., "urn:lex:fr:etat:traite:..." and "urn:lex:de:staat:vertrag:..." (e.g., "urn:lex:fr:etat:traite:..." and "urn:lex:de:staat:vertrag:..."
since it pertains to both the French and the German jurisdiction).</t> since it pertains to both the French and German jurisdictions).</t>
<t>In the states or organisations that have multiple official <t indent="0" pn="section-5.5-2">In the states or organizations that hav
languages, a document has multiple identifiers, each of them expressed in e multiple official
a different official language, basically a set of equivalent aliases. languages, a document has multiple identifiers. Each identifier is expressed in
a different official language and is basically a set of equivalent aliases.
This system permits manual or automated construction of the uniform This system permits manual or automated construction of the uniform
name of the referred source of law in the same language used in the name of the referred source of law in the same language used in the
document itself<br/> document itself
(e.g., "urn:lex:eu:council:directive:2004-12-07;31", (e.g., "urn:lex:eu:council:directive:2004-12-07;31" and
"urn:lex:eu:consiglio:direttiva:2004-12-07;31", etc.).</t> "urn:lex:eu:consiglio:direttiva:2004-12-07;31").</t>
<t>Moreover, a document can be assigned more than one uniform name in <t indent="0" pn="section-5.5-3">Moreover, a document can be assigned mo
re than one uniform name in
order to facilitate its linking from other documents. This option can order to facilitate its linking from other documents. This option can
be used for documents that, although unique, are commonly referenced be used for documents that, although unique, are commonly referenced
from different perspectives. For example, the form of a document's from different perspectives, for example, the form of a document's
promulgation and its specific content (e.g., a Regulation promulgated promulgation and its specific content (e.g., a Regulation promulgated
through a Decree of the President of the Republic).</t> through a Decree of the President of the Republic).</t>
</section> </section>
<section anchor="structure-of-the-document-identifier-at-expression-level" <section anchor="structure-of-the-document-identifier-at-expression-level"
> numbered="true" removeInRFC="false" toc="include" pn="section-5.6">
<name>Structure of the Document Identifier at "Expression" Level</name> <name slugifiedName="name-structure-of-the-document-id">Structure of the
<t>There may be several expressions of a legal text, connected to Document Identifier at "Expression" Level</name>
<t indent="0" pn="section-5.6-1">There may be several expressions of a l
egal text connected to
specific versions or languages.</t> specific versions or languages.</t>
<t>Each version is characterized by the period of time during which that <t indent="0" pn="section-5.6-2">Each version is characterized by the pe riod of time during which that
text is to be considered to be in force or effective. text is to be considered to be in force or effective.
The lifetime of a version ends with the issuing of the subsequent The lifetime of a version ends with the issuing of the subsequent
version. New versions of a text may be brought into existence by:</t> version. New versions of a text may be brought into existence by:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<li> .6-3">
<t>amendments due to the issuing of other legal <li pn="section-5.6-3.1">
<t indent="0" pn="section-5.6-3.1.1">amendments due to the issuing o
f other legal
acts and to the subsequent production of updated or consolidated acts and to the subsequent production of updated or consolidated
texts;</t> texts,</t>
</li> </li>
<li> <li pn="section-5.6-3.2">
<t>correction of publication errors (rectification or errata corrige <t indent="0" pn="section-5.6-3.2.1">correction of publication error
);</t> s (rectification or errata corrige), and</t>
</li> </li>
<li> <li pn="section-5.6-3.3">
<t>entry into or departure from a particular time span, depending on <t indent="0" pn="section-5.6-3.3.1">entry into or departure from a
particular time span, depending on
the specific date in which different partitions of a text come into the specific date in which different partitions of a text come into
force.</t> force.</t>
</li> </li>
</ul> </ul>
<t>Each such version may be expressed in more than one language, <t indent="0" pn="section-5.6-4">Each version may be expressed in more t
with each language-version having its own specific identifier. han one language,
with each language version having its own specific identifier.
The identifier of a source of law expression adds such information to The identifier of a source of law expression adds such information to
the work identifier, using the following main structure:</t> the work identifier using the following main structure:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-5.6-5">
expression = version [":" language] expression = version [":" language]
]]></artwork> </sourcecode>
<t>where:</t> <t indent="0" pn="section-5.6-6">where:</t>
<ul spacing="normal"> <dl newline="false" spacing="normal" indent="3" pn="section-5.6-7">
<li> <dt pn="section-5.6-7.1">version:</dt>
<t>version is the identifier of the version of the original or <dd pn="section-5.6-7.2">The identifier of the version of the original
amended source of law. In general it is expressed by the or
amended source of law. In general, it is expressed by the
promulgation date of the amending act; other specific promulgation date of the amending act; other specific
information can be used for particular documents. If necessary, the information can be used for particular documents. If necessary, the
original version is specified by the string "original", expressed in original version is specified by the string "original" and is expressed in
the language of the act or version (for the details regarding this the language of the act or version (for the details regarding this
element, please see the <xref target="syn-ver"/>);</t> element, please see <xref target="syn-ver" format="default" sectionFormat="of" d
</li> erivedContent="Section 7"/>).</dd>
<li> <dt pn="section-5.6-7.3">language:</dt>
<t>language is the identification code of the language in which the <dd pn="section-5.6-7.4">The identification code of the language in wh
document is expressed, according to <xref target="RFC5646"/> (it=Italian, fr=Fre ich the
nch, document is expressed, according to <xref target="RFC5646" format="default" sect
de=German, etc.). The granularity level of the language (for example ionFormat="of" derivedContent="RFC5646"/> (it=Italian, fr=French,
de=German, etc.). The granularity level of the language (for example,
the specification of the German language as used in Switzerland the specification of the German language as used in Switzerland
rather than the standard German) is left to each specific rather than standard German) is left to each specific
jurisdiction. The information is not necessary when the text is jurisdiction. The information is not necessary when the text is
expressed in the sole official language of the country or expressed in the sole official language of the country or
jurisdiction.</t> jurisdiction.</dd>
</li> </dl>
</ul> <t indent="0" pn="section-5.6-8">The following are hypothetical examples
<t>Hypothetical examples of document identifiers for expressions are:</t of document identifiers for expressions:</t>
> <artwork align="left" pn="section-5.6-9">
<artwork><![CDATA[
urn:lex:ch:etat:loi:2006-05-14;22@originel:fr urn:lex:ch:etat:loi:2006-05-14;22@originel:fr
(original version in French) (original version in French)
urn:lex:ch:staat:gesetz:2006-05-14;22@original:de urn:lex:ch:staat:gesetz:2006-05-14;22@original:de
(original version in German) (original version in German)
urn:lex:ch:etat:loi:2006-05-14;22@2008-03-12:fr urn:lex:ch:etat:loi:2006-05-14;22@2008-03-12:fr
(amended version in French) (amended version in French)
urn:lex:ch:staat:gesetz:2006-05-14;22@2008-03-12:de urn:lex:ch:staat:gesetz:2006-05-14;22@2008-03-12:de
(amended version in German) (amended version in German)
urn:lex:be:conseil.etat:decision:2008-07-09;185.273@originel:fr urn:lex:be:conseil.etat:decision:2008-07-09;185.273@originel:fr
(original version in French of a Belgian decision) (original version in French of a Belgian decision)
]]></artwork> </artwork>
</section> </section>
<section anchor="struct-manif"> <section anchor="struct-manif" numbered="true" removeInRFC="false" toc="in
<name>Structure of the Document Identifier at "Manifestation" Level</nam clude" pn="section-5.7">
e> <name slugifiedName="name-structure-of-the-document-ide">Structure of th
<t>To identify a specific manifestation, the uniform name of the e Document Identifier at "Manifestation" Level</name>
<t indent="0" pn="section-5.7-1">To identify a specific manifestation, t
he 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:</t> main elements:</t>
<ul spacing="normal"> <dl spacing="normal" indent="3" newline="false" pn="section-5.7-2">
<li> <dt pn="section-5.7-2.1">editor:</dt>
<t>editor: editorial staff who produced it, expressed according to <dd pn="section-5.7-2.2">Editorial staff who produced it, expressed ac
its Internet domain name. Since publishers' domain names may vary cording to
the publisher's Internet domain name. Since publishers' domain names may vary
over time, manifestations already assigned by a publisher remain over time, manifestations already assigned by a publisher remain
unchanged even if the identified object is no longer accessible. In unchanged, even if the identified object is no longer accessible. In
this case, in order to make its materials accessible, the publisher this case, in order to make its materials accessible, the publisher
will have to create for each of them a new manifestation with the will have to create a new manifestation with a
new domain name;</t> new domain name for each object.</dd>
</li> <dt pn="section-5.7-2.3">format:</dt>
<li> <dd pn="section-5.7-2.4">The digital format (e.g., XML, HTML, PDF, etc
<t>format: the digital format (e.g., XML, HTML, PDF, etc.) expressed .) expressed
according to the MIME Content-Type standard <xref target="RFC2045"/>, where the according to the MIME Content-Type standard <xref target="RFC2045" format="defau
"/" character is to be substituted by the "-" sign;</t> lt" sectionFormat="of" derivedContent="RFC2045"/>, where the
</li> "/" character is to be substituted with the "-" sign.</dd>
<li> <dt pn="section-5.7-2.5">component:</dt>
<t>component: possible components of the expressions contained in <dd pn="section-5.7-2.6">Possible components of the expressions
the manifestation. Such components are expressed by language- contained in the manifestation. Such components are expressed by
dependent labels representing the whole document (in English "all") language-dependent labels representing the whole document (in
or the main part of the document (in English "body") or the caption English "all"), the main part of the document (in English "body"),
label of the component itself (e.g. Table 1, Figure 2, etc.);</t> or the caption label of the component itself (e.g., Table 1,
</li> Figure 2, etc.).</dd>
<li> <dt pn="section-5.7-2.7">feature:</dt>
<t>feature: other features of the document (e.g., anonymized <dd pn="section-5.7-2.8">Other features of the document (e.g., anonymi
decision text).</t> zed
</li> decision text).</dd>
</ul> </dl>
<t>The manifestation suffix thus reads:</t> <t indent="0" pn="section-5.7-3">Thus, the manifestation suffix reads:</
<artwork><![CDATA[ t>
<sourcecode type="abnf" markers="false" pn="section-5.7-4">
manifestation = editor ":" format manifestation = editor ":" format
[":" component [":" feature]] [":" component [":" feature]]
]]></artwork> </sourcecode>
<t>To indicate possible features or peculiarities, each main element of <t indent="0" pn="section-5.7-5">To indicate possible features or peculi
the manifestation MAY be followed by further specifications arities, each main element of
(separated by ";"), for example as regards editor the archive name the manifestation <bcp14>MAY</bcp14> be followed by further specifications
and the electronic publisher, for format the version, etc. (separated by ";"), for example, the archive name and electronic publisher
Therefore the main elements of the manifestation will assume the for the editor and the version for format.
forms:</t> Therefore, the main elements of the manifestation will assume the
<artwork><![CDATA[ following forms:</t>
<sourcecode type="abnf" markers="false" pn="section-5.7-6">
editor = publisher *(";" specification) editor = publisher *(";" specification)
format = mime *(";" specification) format = mime *(";" specification)
component = part *(";" specification) component = part *(";" specification)
feature = attribute *(";" specification) feature = attribute *(";" specification)
]]></artwork> </sourcecode>
<t>The syntax details of the manifestation element is shown in <t indent="0" pn="section-5.7-7">The syntax details of the manifestation
<xref target="urn-lex-syn"/>, in the related part.</t> element are shown in
<t>(examples (hypothetical):</t> <xref target="urn-lex-syn" format="default" sectionFormat="of" derivedContent="S
<t>the original version of the Italian act 3 April 2000, n. 56 might hav ection 8"/> in the related part.</t>
e <t indent="0" pn="section-5.7-8">The following are hypothetical examples
:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
.7-9">
<li pn="section-5.7-9.1">
<t indent="0" pn="section-5.7-9.1.1">The original version of the Ita
lian act 3 April 2000, n. 56 might have
the following manifestations with their relative uniform names:</t> the following manifestations with their relative uniform names:</t>
<artwork><![CDATA[ <ul spacing="normal" bare="false" empty="false" indent="3" pn="secti
- PDF format (vers. 1.7) of the whole act edited by the Italian on-5.7-9.1.2">
Parliament: <li pn="section-5.7-9.1.2.1">
"urn:lex:it:stato:legge:2000-04-03;56$application-pdf; <t indent="0" pn="section-5.7-9.1.2.1.1">PDF format (vers. 1.7)
1.7:parlamento.it" of the whole act edited by the Italian Parliament:</t>
- XML format (version 2.2 DTD NIR) of the text of the act and PDF <artwork align="left" pn="section-5.7-9.1.2.1.2">
format (version 1.7) of the "Figura 1" (figure 1) contained in the urn:lex:it:stato:legge:2000-04-03;56$parlamento.it:
body, edited by the Italian Senate: application-pdf;1.7
"urn:lex:it:stato:legge:2000-04-03;56$text-xml;dtd-nir-2.2: </artwork>
senato.it:testo" </li>
"urn:lex:it:stato:legge:2000-04-03;56$application-pdf;1.7: <li pn="section-5.7-9.1.2.2">
senato.it:figura.1" <t indent="0" pn="section-5.7-9.1.2.2.1">XML format (version 2.2
]]></artwork> DTD NIR) of the text of the act and PDF format
<t>the Spanish URN of the html format of the whole Judgment of the (version 1.7) of the "Figura 1" (figure 1) contained in the body, edited by
the Italian Senate:</t>
<artwork align="left" pn="section-5.7-9.1.2.2.2">
urn:lex:it:stato:legge:2000-04-03;56$senato.it:text-xml;
dtd-nir-2.2:testo
urn:lex:it:stato:legge:2000-04-03;56$senato.it:
application-pdf;1.7:figura.1
</artwork>
</li>
</ul>
</li>
<li pn="section-5.7-9.2">
<t indent="0" pn="section-5.7-9.2.1">The Spanish URN of the HTML for
mat of the whole Judgment of the
European Court of Justice n. 33/08 of 11/06/2009, in Spanish version, European Court of Justice n. 33/08 of 11/06/2009, in Spanish version,
published in the Jurifast database in anonymized form:</t> published in the Jurifast database in anonymized form:</t>
<artwork><![CDATA[ <artwork align="left" pn="section-5.7-9.2.2">
"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
]]></artwork> </artwork>
<t>It is useful to be able to assign a uniform name to a </li>
</ul>
<t indent="0" pn="section-5.7-10">It is useful to be able to assign a un
iform name to a
manifestation (or to a part of it) in case non-textual objects are manifestation (or to a part of it) in case non-textual objects are
involved. These may be multimedia objects that are non-textual in involved. These may be multimedia objects that are non-textual in
their own right (e.g. geographic maps, photographs, etc.), or texts their own right (e.g., geographic maps, photographs, etc.) or texts
recorded in non-textual formats, such as image scans of documents.</t> recorded in non-textual formats (e.g., image scans of documents).</t>
</section> </section>
<section anchor="sources-of-law-references"> <section anchor="sources-of-law-references" numbered="true" removeInRFC="f
<name>Sources of Law References</name> alse" toc="include" pn="section-5.8">
<t>References to sources of law often refer to specific partitions of <name slugifiedName="name-sources-of-law-references">Sources of Law Refe
rences</name>
<t indent="0" pn="section-5.8-1">References to sources of law often refe
r to specific partitions of
the act (article, paragraph, etc.) and not to the entire document.</t> the act (article, paragraph, etc.) and not to the entire document.</t>
<t>From a legal point of view, a partition is always a text block, that <t indent="0" pn="section-5.8-2">From a legal point of view, a partition is always a text block that
represents a logical subdivision of an act.</t> represents a logical subdivision of an act.</t>
<t>As regards the digital representation, <t indent="0" pn="section-5.8-3">In the digital representation, a partit
a partition is ion is represented
represented by an element (a block of text) with its own ID; this ID by an element (a block of text) with its own ID; this ID aims to
aims to identify the related element and to locate it. In this case, identify the related element and locate it. Therefore,
therefore, it is possible either to extract or to point to a it is possible to either extract or point to a
partition.</t> partition.</t>
<t>In a mark-up not fitting the logical structure of the text (as HTML), <t indent="0" pn="section-5.8-4">For markup that does not fit the logica
l structure of the text (like HTML),
generally only the starting point of the partition, rather than the generally only the starting point of the partition, rather than the
whole block of text or element, is identified through a label (a &lt;a whole block of text or element, is identified through a label (e.g., &lt;a
id=partitionID&gt;&lt;/a&gt; tag in Html Markup Language <xref target="W3C.HTML" id=partitionID&gt;&lt;/a&gt; tag in the HTML markup language <xref target="W3C.H
/>). In this case TML" format="default" sectionFormat="of" derivedContent="W3C.HTML"/>). In this c
therefore it is not possible to extract a partition but only to point ase, it is only possible to point to a partition but not extract it.</t>
to it.</t> <t indent="0" pn="section-5.8-5">Partitions should be assigned unique la
<t>Partitions should be assigned unique labels or bels or
IDs within the including document and their value should be the same IDs within the including document, and their value should be the same
regardless of document format.</t> regardless of document format.</t>
<t>For enabling the construction of the partition identifier between <t indent="0" pn="section-5.8-6">To enable the construction of the parti
different collections of documents, specific construction rules for tion identifier between
IDs or labels will be defined and shared, within each country or different collections of documents, specific construction rules for
jurisdiction, for any document type<br/> IDs or labels will be defined and shared within each country or
(e.g., for legislation, the jurisdiction for any document type. For example, in legislation, paragra
paragraph 2 of the article 3 might have as label or ID the value ph 2 of
"art3;par2", similarly for case-law, paragraph 22 of the judgment in article 3 might have the value "art3;par2" as the label or ID;
Case 46/76 Bauhuis v Netherlands, might have as label or ID the value similarly, for case law, paragraph 22 of the judgment in
"par22").</t> Case 46/76 Bauhuis v Netherlands might have the value "par22" as the lab
<t>Furthermore, it is useful to foresee the compatibility with el or ID.</t>
applications able to manage this information (e.g., returning the <t indent="0" pn="section-5.8-7">Furthermore, it is useful to foresee th
e compatibility with
applications that are able to manage this information (e.g., returning the
proper element); these procedures are particularly useful in the case proper element); these procedures are particularly useful in the case
of rather long acts, such as codes, constitutions, regulations, etc. of rather long acts, such as codes, constitutions, regulations, etc.
For this purpose it is necessary that the partition identifier is For this purpose, it is necessary that the partition identifier be
transmitted to the servers (resolution and application) and therefore transmitted to the servers (resolution and application). Therefore,
it cannot be separated by the typical "#" character of URI fragment, it cannot be separated by the typical "#" character of URI fragment,
which is not transmitted to the server.</t> which is not transmitted to the server.</t>
<t>According to these requirements, the syntax of a reference is:</t> <t indent="0" pn="section-5.8-8">According to these requirements, the sy
<artwork><![CDATA[ ntax of a reference is:</t>
<sourcecode type="abnf" markers="false" pn="section-5.8-9">
URN-reference = URN-document ["~" partition-id] URN-reference = URN-document ["~" partition-id]
]]></artwork> </sourcecode>
<t>(e.g., to refer to the paragraph 3 of the article 15 of the French <t indent="0" pn="section-5.8-10">For example, referring to paragraph 3
of article 15 of the French
Act of 15 May 2004, n. 106, the reference can be Act of 15 May 2004, n. 106, the reference can be
"urn:lex:fr:etat:loi:2004-05-15;106~art15;par3").</t> "urn:lex:fr:etat:loi:2004-05-15;106~art15;par3".</t>
<t>Using a different separator ("~") from the document name, the <t indent="0" pn="section-5.8-11">If a different separator ("~") is used
partition ID is not withheld by the browser but it is transmitted to after the document name, the
the resolution process. This enables the resolver to retrieve (for partition ID is not withheld by the browser but is transmitted to
example, out of a database) only the referred partition, if the the resolution process.
partition syntax is compatible with the media type used, otherwise to If the
return the whole act.</t> partition syntax is compatible with the media type used, this enables the resolv
<t>When resolving to HTTP, er to retrieve (for
the resolver SHALL transform the partition ID example, out of a database) only the referred partition; otherwise, the whole ac
to an appropriate internal reference (#) in the page, t is returned.
</t>
<t indent="0" pn="section-5.8-12">When resolving to HTTP,
the resolver <bcp14>SHALL</bcp14> transform the partition ID
to an appropriate internal reference (#) on the page
or at the beginning if that point cannot be found. or at the beginning if that point cannot be found.
The transformation in URI fragment is obtained appending to The transformation in the URI fragment is obtained by appending the "#" characte
the URL the "#" character followed by the partition ID (in the r followed by the partition ID to
the URL (in the
example above, the returned URL will be &lt;URL-document&gt;#art15;par3). example above, the returned URL will be &lt;URL-document&gt;#art15;par3).
Doing this, knowing the granularity of the act markup, the resolver Doing this, knowing the granularity of the act markup, the resolver
could exploit the hierarchical structure of the ID, eliminating could exploit the hierarchical structure of the ID by eliminating
sub-partitions not addressed. If only the article was identified in the sub-partitions that are not addressed. In the previous example, if only the arti
act, in the previous example it could return &lt;URL-document&gt;#art15 cle was identified in the
act, it could return &lt;URL-document&gt;#art15
only.</t> only.</t>
<t>It is possible to use the general syntax (with "#"); in this <t indent="0" pn="section-5.8-13">It is possible to use the general synt
case only the URN document component of the reference is transmitted ax (with "#"); in this
to the resolver, therefore the whole document will always be case, only the URN document component of the reference is transmitted
to the resolver; therefore, the whole document will always be
retrieved.</t> retrieved.</t>
</section> </section>
</section> </section>
<section anchor="syn-work"> <section anchor="syn-work" numbered="true" removeInRFC="false" toc="include"
<name>Specific Syntax of the Identifier at "Work" Level</name> pn="section-6">
<section anchor="the-authority-element"> <name slugifiedName="name-specific-syntax-of-the-iden">Specific Syntax of
<name>The authority Element</name> the Identifier at "Work" Level</name>
<section anchor="indication-of-the-authority"> <section anchor="the-authority-element" numbered="true" removeInRFC="false
<name>Indication of the Authority</name> " toc="include" pn="section-6.1">
<t>The authority element of a uniform name may indicate, in the <name slugifiedName="name-the-authority-element">The Authority Element</
name>
<section anchor="indication-of-the-authority" numbered="true" removeInRF
C="false" toc="include" pn="section-6.1.1">
<name slugifiedName="name-indication-of-the-authority">Indication of t
he Authority</name>
<t indent="0" pn="section-6.1.1-1">The authority element of a uniform
name may indicate the following in the
various cases:</t> various cases:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section
<li> -6.1.1-2">
<t>the actual authority issuing the legal provision. More <li pn="section-6.1.1-2.1">
specifically, the authority adopting the provision or enacting it;</t> <t indent="0" pn="section-6.1.1-2.1.1">The actual authority issuin
g the legal provision. More
specifically, the authority adopting the provision or enacting it.</t>
</li> </li>
<li> <li pn="section-6.1.1-2.2">
<t>the institution where the provision is registered, known and <t indent="0" pn="section-6.1.1-2.2.1">The institution where the p
rovision is registered, known, and
referenced to, even if produced by others (e.g., the bills referenced to, even if produced by others (e.g., the bills
identified through the reference to the Chamber where they are identified through the reference to the Chamber where they are
presented);</t> presented).</t>
</li> </li>
<li> <li pn="section-6.1.1-2.3">
<t>the institution regulated (and referred to in citations) by the <t indent="0" pn="section-6.1.1-2.3.1">The institution regulated (
and referred to in citations) by the
legal provision even when this is issued by another authority legal provision even when this is issued by another authority
(e.g., the statute of a Body);</t> (e.g., the statute of a Body).</t>
</li> </li>
<li> <li pn="section-6.1.1-2.4">
<t>the entity that proposed the legal material not yet included in <t indent="0" pn="section-6.1.1-2.4.1">The entity that proposed th
the e legal material not yet included in the
institutional process (e.g. a proposed bill written by a institutional process (e.g., a proposed bill written by a
political party).</t> political party).</t>
</li> </li>
</ul> </ul>
</section> </section>
<section anchor="multiple-issuers"> <section anchor="multiple-issuers" numbered="true" removeInRFC="false" t
<name>Multiple Issuers</name> oc="include" pn="section-6.1.2">
<t>Some sources of law are enacted by a number of issuing parties (e.g <name slugifiedName="name-multiple-issuers">Multiple Issuers</name>
., <t indent="0" pn="section-6.1.2-1">Some sources of law are enacted by
a number of issuing parties (e.g.,
inter-ministerial decrees, agreements, etc.). In this case, the inter-ministerial decrees, agreements, etc.). In this case, the
authority element contains all the issuing parties (properly authority element contains all the issuing parties (properly
separated), as follows:</t> separated) as follows:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.1.2-2">
authority = issuer *("+" issuer) authority = issuer *("+" issuer)
]]></artwork> </sourcecode>
<t>(e.g., "ministry.justice+ministry.finances").</t> <t indent="0" pn="section-6.1.2-3">This is an example: "ministry.justi
ce+ministry.finances".</t>
</section> </section>
<section anchor="indication-of-the-issuer"> <section anchor="indication-of-the-issuer" numbered="true" removeInRFC="
<name>Indication of the Issuer</name> false" toc="include" pn="section-6.1.3">
<t>Each issuing authority is essentially represented by either an <name slugifiedName="name-indication-of-the-issuer">Indication of the
Issuer</name>
<t indent="0" pn="section-6.1.3-1">Each issuing authority is essential
ly represented by either an
institutional office (e.g., Prime Minister) or an institution (e.g., institutional office (e.g., Prime Minister) or an institution (e.g.,
Ministry); in the last case, the authority is indicated in accordance Ministry); in the last case, the authority is indicated in accordance
with the institution's hierarchical structure, from the more general with the institution's hierarchical structure, from more general
to more specific (Council, Department, etc.), ending with the to more specific (Council, Department, etc.), ending with the
relative office (President, Director, etc.). relative office (President, Director, etc.).
Therefore, the structure of the issuer is as follows:</t> Therefore, the structure of the issuer is as follows:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.1.3-2">
issuer = (institution *(";" body-function)) / office issuer = (institution *(";" body-function)) / office
]]></artwork> </sourcecode>
<t>(e.g., "ministry.finances;department.revenues;manager")</t> <t indent="0" pn="section-6.1.3-3">This is an example: "ministry.finan
ces;department.revenues;manager".</t>
</section> </section>
<section anchor="indication-of-the-body"> <section anchor="indication-of-the-body" numbered="true" removeInRFC="fa
<name>Indication of the Body</name> lse" toc="include" pn="section-6.1.4">
<t>Depending on the kind of measure, the body within the issuing <name slugifiedName="name-indication-of-the-body">Indication of the Bo
dy</name>
<t indent="0" pn="section-6.1.4-1">Depending on the kind of measure, t
he 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 normally it is not indicated in the references. Acts), and it is not normally indicated in the references.
Just like in practice, the indication of the enacting authority is Just like in practice, the indication of the enacting authority is
limited to the minimum in relation to the type of measure<br/> limited to the minimum in relation to the type of measure
(e.g., "region.tuscany:act" and not "region.tuscany;council:act").</t> (e.g., "region.tuscany:act" and not "region.tuscany;council:act").</t>
</section> </section>
<section anchor="indication-of-the-function"> <section anchor="indication-of-the-function" numbered="true" removeInRFC
<name>Indication of the Function</name> ="false" toc="include" pn="section-6.1.5">
<t>Generally, the function is indicated, sometimes instead of the body <name slugifiedName="name-indication-of-the-function">Indication of th
e Function</name>
<t indent="0" pn="section-6.1.5-1">Generally, the function is indicate
d, sometimes instead of the Body
itself:</t> itself:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section
<li> -6.1.5-2">
<t>in case of political, representative or elective offices<br/> <li pn="section-6.1.5-2.1">
<t indent="0" pn="section-6.1.5-2.1.1">In the case of political, r
epresentative, or elective offices
(e.g., "university.oxford;rector:decree" instead of (e.g., "university.oxford;rector:decree" instead of
"university.oxford;rectorship:decree");</t> "university.oxford;rectorship:decree").</t>
</li> </li>
<li> <li pn="section-6.1.5-2.2">
<t>when it refers to a top officer in the institution (e.g., gener <t indent="0" pn="section-6.1.5-2.2.1">When referring to a top off
al icer 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<br/> associate a specific internal institutional structure to
(e.g., "national.council.research;general.manager").</t> (e.g., "national.council.research;general.manager").</t>
</li> </li>
</ul> </ul>
<t>It is not indicated when it clearly corresponds to the person in <t indent="0" pn="section-6.1.5-3">It is not indicated when it clearly corresponds to the person in
charge of an institution (typically, a general director); in this charge of an institution (typically, a general director); in this
case, only the structure and not the person in charge is indicated<br/> case, only the structure and not the person in charge is indicated
(e.g., "ministry.justice;department.penitentiary.administration").</t> (e.g., "ministry.justice;department.penitentiary.administration").</t>
<t>The function MUST be indicated when:</t> <t indent="0" pn="section-6.1.5-4">The function <bcp14>MUST</bcp14> be
<ul spacing="normal"> indicated when:</t>
<li> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section
<t>it is not the same of the director or the person in charge of t -6.1.5-5">
he <li pn="section-6.1.5-5.1">
structure (for example, in case of an undersecretary, a deputy <t indent="0" pn="section-6.1.5-5.1.1">It is not the same as the d
director, etc.);</t> irector or the person in charge of the
structure (for example, an undersecretary, a deputy
director, etc.). </t>
</li> </li>
<li> <li pn="section-6.1.5-5.2">
<t>the type of measure may be both monocratic or collegial: the <t indent="0" pn="section-6.1.5-5.2.1">The type of measure may be
both monocratic or collegial; the
indication of the office eliminates the ambiguity.</t> indication of the office eliminates the ambiguity.</t>
</li> </li>
</ul> </ul>
</section> </section>
<section anchor="conventions-for-the-authority"> <section anchor="conventions-for-the-authority" numbered="true" removeIn
<name>Conventions for the Authority</name> RFC="false" toc="include" pn="section-6.1.6">
<t>Acts and measures bearing the same relevance as an act, issued or <name slugifiedName="name-conventions-for-the-authori">Conventions for
the Authority</name>
<t indent="0" pn="section-6.1.6-1">Acts and measures bearing the same
relevance as an act, issued or
enacted since the foundation of the State, have conventionally enacted since the foundation of the State, have conventionally
indicated "state" (expressed in each country official language) as indicated "state" (expressed in each country's official language) as
authority; the same convention is used for constitutions, codes the authority. The same convention is used for constitutions, codes
(civil, criminal, civil procedure, criminal procedure, etc) and (civil, criminal, civil procedure, criminal procedure, etc.), and
international treaties.</t> international treaties.</t>
</section> </section>
</section> </section>
<section anchor="the-measure-element"> <section anchor="the-measure-element" numbered="true" removeInRFC="false"
<name>The measure Element</name> toc="include" pn="section-6.2">
<section anchor="criteria-for-the-indication-of-the-type-of-measure"> <name slugifiedName="name-the-measure-element">The Measure Element</name
<name>Criteria for the Indication of the Type of Measure</name> >
<t>In uniform names the issuing authority of a document is mandatory. <section anchor="criteria-for-the-indication-of-the-type-of-measure" num
This makes unnecessary to indicate any further qualification of the bered="true" removeInRFC="false" toc="include" pn="section-6.2.1">
<name slugifiedName="name-criteria-for-the-indication">Criteria for th
e Indication of the Type of Measure</name>
<t indent="0" pn="section-6.2.1-1">In uniform names, the issuing autho
rity of a document is mandatory.
This makes it unnecessary to indicate any further qualification of the
measure (e.g., ministerial decree, directorial ordinance, etc.), even measure (e.g., ministerial decree, directorial ordinance, etc.), even
if it is widely used. if it is widely used.
When the authority-measure combination clearly identifies a specific When the authority-measure combination clearly identifies a specific
document, the type of measure is not defined through attributes document, the type of measure is not defined through attributes
referring to the enacting authority<br/> referring to the enacting authority
(e.g., "region.tuscany:act" and not "region.tuscany:regional.act").</t> (e.g., "region.tuscany:act" and not "region.tuscany:regional.act").</t>
</section> </section>
<section anchor="further-specification-to-the-type-of-measure"> <section anchor="further-specification-to-the-type-of-measure" numbered=
<name>Further Specification to the Type of Measure</name> "true" removeInRFC="false" toc="include" pn="section-6.2.2">
<t>In the measure element, it is usually sufficient to indicate the <name slugifiedName="name-further-specification-to-th">Further Specifi
type of a measure. As usual, references to sources of law, rather cation to the Type of Measure</name>
than through the formal details (date and number), may be made <t indent="0" pn="section-6.2.2-1">In the measure element, it is usual
through some of their characteristics such as the subject-matter ly sufficient to indicate the
covered (e.g., accounting regulations), nicknames referring to the type of a measure. As usual, rather than through the formal details
promoter (e.g., Bolkestein directive) or to the topic of the act (e.g., (date and number), references to sources of law may be made through
Bankruptcy Law), etc.. some of their characteristics, such as the subject matter covered
In these cases, the type of measure MAY be followed by further (e.g., accounting regulations), nicknames referring to the promoter
specifications useful in referencing even if the details are lacking:</t> (e.g., Bolkestein directive), or the topic of the act (e.g.,
<artwork><![CDATA[ Bankruptcy Law), etc. In these cases, the type of measure
<bcp14>MAY</bcp14> be followed by further specifications that are
useful in referencing, even if the details are lacking:</t>
<sourcecode type="abnf" markers="false" pn="section-6.2.2-2">
measure = measure-type *(";" specification) measure = measure-type *(";" specification)
]]></artwork> </sourcecode>
<t>(e.g., "regulations;accounting" or "act;bankruptcy").</t> <t indent="0" pn="section-6.2.2-3">These are examples: "regulations;ac
counting" or "act;bankruptcy".</t>
</section> </section>
<section anchor="aliases-for-sources-of-law-with-different-normative-ref <section anchor="aliases-for-sources-of-law-with-different-normative-ref
erences"> erences" numbered="true" removeInRFC="false" toc="include" pn="section-6.2.3">
<name>Aliases for Sources of Law with Different Normative References</ <name slugifiedName="name-aliases-for-sources-of-law-">Aliases for Sou
name> rces of Law with Different Normative References</name>
<t>There are legislative measures that, although unique, are usually <t indent="0" pn="section-6.2.3-1">There are legislative measures that
cited in different ways, for example through the legislative act , although unique, are usually
introducing them into the legal order (President's decree, cited in different ways, for example, introducing them into the
legislative decree, etc.) or through their legislative category legal order through a legislative act (President's decree,
(regulations, consolidation, etc.). legislative decree, etc.) or through their legislative category
In order to ensure, in all the cases, the validity of the references, (regulations, consolidation, etc.). In order to ensure the validity o
an alias (additional URN LEX identifier), that takes into account the f the references in all cases, an alias (an additional URN LEX
measure category, is added to what represents the legislative form of identifier) that takes into account the measure category is added
the same act<br/> to what represents the legislative form of the same act (e.g.,
(e.g., "state:decree.legislative:1992-07-24;358" and "state:decree.legislative:1992-07-24;358" and
"state:consolidation;public.contracts:1992-07-24;358").</t> "state:consolidation;public.contracts:1992-07-24;358").</t>
</section> </section>
<section anchor="relations-between-measure-and-authority-in-the-aliases" <section anchor="relations-between-measure-and-authority-in-the-aliases"
> numbered="true" removeInRFC="false" toc="include" pn="section-6.2.4">
<name>Relations between Measure and Authority in the Aliases</name> <name slugifiedName="name-relations-between-measure-a">Relations Betwe
<t>The sources of law including different normative references are en Measure and Authority in the Aliases</name>
<t indent="0" pn="section-6.2.4-1">The sources of law including differ
ent normative references are
usually introduced in legislation through the adoption or the issuing usually introduced in legislation through the adoption or the issuing
of an act, which they are either included or attached to. It is, of an act, which they are either included or attached to. Therefore, it is
therefore, necessary to create an alias linking the two aspects of necessary to create an alias linking the two aspects of
the same document. Specifically, the different measures can be:</t> the same document. Specifically, the different measures can be:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section
<li> -6.2.4-2">
<t>adopted/issued by an authority different from the one regulated <li pn="section-6.2.4-2.1">
by <t indent="0" pn="section-6.2.4-2.1.1">Adopted/issued by an author
the provision (e.g., the statute of a Body); in this case, the ity different from the one regulated by
correlation is established between two uniform names each featuring the provision (e.g., the statute of a Body). In this case, the
a completely different authority element<br/> correlation is established between two uniform names, each featuring
a completely different authority element
(e.g., "italian.society.authors.publishers:statute" and (e.g., "italian.society.authors.publishers:statute" and
"ministry.cultural.activities+ministry.finances.budget.economic. "ministry.cultural.activities+ministry.finances.budget.economic.
planning:decree");</t> planning:decree").</t>
</li> </li>
<li> <li pn="section-6.2.4-2.2">
<t>issued by the institution itself either because it has issuing <t indent="0" pn="section-6.2.4-2.2.1">Issued by the institution i
tself either because it has issuing
authority or by virtue of a proxy (e.g., a provision that refers to authority or by virtue of a proxy (e.g., a provision that refers to
the functioning of the Body itself); in this case, the two aliases the functioning of the Body itself). In this case, the two aliases
share the first part of the authority<br/> share the first part of the authority
(e.g., "municipality.firenze:statute" and (e.g., "municipality.firenze:statute" and
"municipality.firenze;council:deliberation");</t> "municipality.firenze;council:deliberation").</t>
</li> </li>
<li> <li pn="section-6.2.4-2.3">
<t>issued by the same Body to regulate a particular sector of its <t indent="0" pn="section-6.2.4-2.3.1">Issued by the same Body to
own regulate a particular sector of its own
competence; in this case the authority element is the same<br/> 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").</t> telematic.process" and "ministry.justice:decree").</t>
</li> </li>
</ul> </ul>
</section> </section>
</section> </section>
<section anchor="det-elem"> <section anchor="det-elem" numbered="true" removeInRFC="false" toc="includ
<name>The Details Element</name> e" pn="section-6.3">
<section anchor="indication-of-the-details"> <name slugifiedName="name-the-details-element">The Details Element</name
<name>Indication of the Details</name> >
<t>The details of a source of law usually include the date of the <section anchor="indication-of-the-details" numbered="true" removeInRFC=
"false" toc="include" pn="section-6.3.1">
<name slugifiedName="name-indication-of-the-details">Indication of the
Details</name>
<t indent="0" pn="section-6.3.1-1">The details of a source of law usua
lly 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.).</t> laws, registry, protocol, etc.).</t>
<t>Some measures can have multiple dates; there are also cases in whic <t indent="0" pn="section-6.3.1-2">Some measures can have multiple dat
h es. 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 set up of both elements (date and number) includes reasons, the setup of both elements (date and number) includes
multiple values.</t> multiple values.</t>
<t>Some institutions (e.g., the Parliaments) usually identify document s <t indent="0" pn="section-6.3.1-3">Some institutions (e.g., the Parlia ments) 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 used in legislature). In these cases, the component period is
substitution of the component dates.</t> substitued for the component dates.</t>
<t>Usually details of a measure are not reported according to a specif <t indent="0" pn="section-6.3.1-4">Usually, details of a measure are n
ic ot reported according to a specific
sequence; in accordance with the global structure of the uniform sequence. In accordance with the global structure of the uniform
name, which goes from the general to the specific, the sequence name, which goes from general to specific, the sequence
date-number has the following form:</t> date-number has the following form:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.3.1-5">
details = (dates / period) ";" numbers details = (dates / period) ";" numbers
]]></artwork> </sourcecode>
<t>(e.g., "2000-12-06;126", "14.legislature;s.2544").</t> <t indent="0" pn="section-6.3.1-6">The following are examples: "2000-1
2-06;126" and "14.legislature;s.2544".</t>
</section> </section>
<section anchor="multiple-dates"> <section anchor="multiple-dates" numbered="true" removeInRFC="false" toc
<name>Multiple Dates</name> ="include" pn="section-6.3.2">
<t>Some sources of law, even if unique, are identified by more than on <name slugifiedName="name-multiple-dates">Multiple Dates</name>
e <t indent="0" pn="section-6.3.2-1">Some sources of law, even if unique
date; in this case, in the field dates all the given dates are to , are identified by more than one
date. In this case, all the given dates are to
be reported and indicated as follows:</t> be reported and indicated as follows:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.3.2-2">
dates = date *("," date) dates = date *("," date)
]]></artwork> </sourcecode>
<t>(e.g., the measure of the Data Protection Authority of December 30, <t indent="0" pn="section-6.3.2-3">For example, the measure of the Dat
1999-January 13, 2000, No. 1/P/2000 has the following uniform name:<br/> a Protection Authority of
"personal.data.protection.authority:measure:1999-12-30,2000-01-13; December 30, 1999-January 13, 2000, No. 1/P/2000 has the following
1-p-2000").</t> uniform name:</t>
<t>As specified in <xref target="dat-form"/>, all the dates can have, <artwork align="left" pn="section-6.3.2-4">
in addition to the ISO format, personal.data.protection.authority:measure:1999-12-30,2000-01-
also the date typical of the jurisdiction.</t> 13;1-p-2000
</artwork>
<t indent="0" pn="section-6.3.2-5">As specified in <xref target="dat-f
orm" format="default" sectionFormat="of" derivedContent="Section 3.6"/>, all the
dates can have
the date typical of the jurisdiction in addition to the ISO
format.</t>
</section> </section>
<section anchor="unnumbered-measures"> <section anchor="unnumbered-measures" numbered="true" removeInRFC="false
<name>Unnumbered Measures</name> " toc="include" pn="section-6.3.3">
<t>Measures not officially numbered in the publications may have a <name slugifiedName="name-unnumbered-measures">Unnumbered Measures</na
me>
<t indent="0" pn="section-6.3.3-1">Measures not officially numbered in
the publications may have a
non-unequivocal identifier, because several measures of the same type non-unequivocal identifier, because several measures of the same type
can exist, issued on the same day by the same authority. can exist and can be issued on the same day by the same authority.
To ensure that the uniform name is unambiguous, the numbers field To ensure that the uniform name is unambiguous, the numbers field
MUST, in any case, contain a discriminating element, which can be any <bcp14>MUST</bcp14>, in any case, contain a discriminating element, which can be
identifier used internally, and not published, by the authority any
identifier used internally and not published by the authority
(e.g., protocol).</t> (e.g., protocol).</t>
<t>If the authority does not have its own identifier, one identifier <t indent="0" pn="section-6.3.3-2">If the authority does not have its
MUST be created for the name system. In order to easily differentiate own identifier, one identifier
<bcp14>MUST</bcp14> be created for the name system. In order to easily different
iate
it, such number is preceded by the string "lex-":</t> it, such number is preceded by the string "lex-":</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.3.3-3">
number-lex = "lex-" 1*DIGIT number-lex = "lex-" 1*DIGIT
]]></artwork> </sourcecode>
<t>(e.g., "ministry.finances:decree:1999-12-20;lex-3").</t> <t indent="0" pn="section-6.3.3-4">The following is an example: "minis
<t>It is responsibility of the authority issuing a document to assign try.finances:decree:1999-12-20;lex-3".</t>
a <t indent="0" pn="section-6.3.3-5">It is the responsibility of the aut
discriminating specification to it; in case of multiple authorities, hority issuing a document to assign a
discriminating specification to it. When there are multiple authorities,
only one of them is responsible for the assignment of the number to only one of them is responsible for the assignment of the number to
the document (e.g., the proponent).</t> the document (e.g., the proponent).</t>
<t>The unnumbered measures published on an official publication (e.g., <t indent="0" pn="section-6.3.3-6">The unnumbered measures published o
the Official Gazette), instead of by a progressive number are n an official publication (e.g.,
recognized by the univocal identifying label printed on the paper. the Official Gazette), are
Such an identifier, even if unofficial but assigned to a document in recognized by the univocal identifying label printed on the paper instead of by
an official publication, is to be preferred because it has the clear a progressive number.
advantage to be public and therefore easier to be found.</t> Such an identifier, even if it is unofficial but assigned to a document in
an official publication, is preferred because it has the clear
advantage of being public and is therefore easier to find.</t>
</section> </section>
<section anchor="mult-num"> <section anchor="mult-num" numbered="true" removeInRFC="false" toc="incl
<name>Multiple Numbers</name> ude" pn="section-6.3.4">
<t>Some legal documents (e.g., bills), even if unique, are identified <name slugifiedName="name-multiple-numbers">Multiple Numbers</name>
by <t indent="0" pn="section-6.3.4-1">Some legal documents (e.g., bills),
even if unique, are identified by
a set of numbers (e.g., the unification of cases or bills). a set of numbers (e.g., the unification of cases or bills).
In this case, in the numbers field, all the identifiers are In this case, in the numbers field, all the identifiers are
reported, according to the following structure:</t> reported, according to the following structure:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.3.4-2">
numbers = document-id *("," document-id) number = document-id *("," document-id)
]]></artwork> </sourcecode>
<t>(e.g., "2000-06-12;c-10-97,c-11-97,c-12-97").</t> <t indent="0" pn="section-6.3.4-3">The following is an example: "2000-
<t>The characters which are not allowed (e.g., "/") or reserved (e.g., 06-12;c-10-97,c-11-97,c-12-97".</t>
":"), including the comma, cannot exist inside the document-id, and <t indent="0" pn="section-6.3.4-4">The characters that are not allowed
therefore MUST be turned into "-".</t> (e.g., "/") or reserved (e.g.,
<t>Where special characters contained in the number of the act are ":"), including the comma, cannot exist inside the document-id and
distinctive of the act itself (e.g. bill n. 123-bis (removal of 123) therefore <bcp14>MUST</bcp14> be turned into "-".</t>
<t indent="0" pn="section-6.3.4-5">When special characters contained i
n the number of the act are
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
conversion to "-", a further ending must be added, allowing to conversion to "-", a further ending must be added to
distinguish the acts (e.g. bill n.123-bis-removal and 123-bis- distinguish the acts (e.g., bill n.123-bis-removal and 123-bis-return).</t>
return).</t>
</section> </section>
</section> </section>
<section anchor="the-annex-element"> <section anchor="the-annex-element" numbered="true" removeInRFC="false" to
<name>The annex Element</name> c="include" pn="section-6.4">
<section anchor="annex-formal"> <name slugifiedName="name-the-annex-element">The Annex Element</name>
<name>Formal Annexes</name> <section anchor="annex-formal" numbered="true" removeInRFC="false" toc="
<t>Although annexes are an integral part of the legal document, they m include" pn="section-6.4.1">
ay <name slugifiedName="name-formal-annexes">Formal Annexes</name>
be referred to and undergo amendments separately from the act to <t indent="0" pn="section-6.4.1-1">Although annexes are an integral pa
which they are annexed. It is, therefore, necessary that both the rt of a legal document, they
main document as well as each formal individual annex is may be referred to and undergo amendments separately from the act to
unequivocally identified.</t> which they are annexed. Therefore, it is necessary that both the
<t>Formal annexes may be registered as separate parts or together with main document as well as each formal individual annex is
a unequivocally identified.</t>
legal provision; they may also be autonomous in nature or not. In any <t indent="0" pn="section-6.4.1-2">Formal annexes may be registered as
case, they MUST be given a uniform name, which includes the uniform separate parts or together
name of the source of law to which they are attached, and a suffix with a legal provision; they may or may not be autonomous in nature. I
which identifies the annex itself.</t> n
<t>The suffix of formal annexes includes the official heading of the any case, they <bcp14>MUST</bcp14> be given a uniform name that
annex and, possibly, further specifications (e.g., the title) which includes the uniform name of the source of law to which they are
attached and a suffix that identifies the annex itself.</t>
<t indent="0" pn="section-6.4.1-3">The suffix of formal annexes includ
es the official heading of the
annex and, possibly, further specifications (e.g., the title) that
will facilitate the retrieval of the annex in case the identifier is will facilitate the retrieval of the annex in case the identifier is
missing:</t> missing:</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-6.4.1-4">
annex = annex-id *(";" specification) annex = annex-id *(";" specification)
]]></artwork> </sourcecode>
<t>(e.g., "region.sicily;council:deliberation:1998-02-12;14:annex.a; <t indent="0" pn="section-6.4.1-5">The following is an example:</t>
borders.park").</t> <artwork align="left" pn="section-6.4.1-6">
<t>The characters which are not allowed (e.g. "/") or which are reserv region.sicily;council:deliberation:1998-02-12;14:annex.a;
ed borders.park
(e.g. ":") must not be featured in the annex-id and therefore MUST </artwork>
be turned into ".".</t> <t indent="0" pn="section-6.4.1-7">The characters that are not allowed
(e.g., "/") or that are
reserved (e.g., ":") must not be featured in the annex-id and
therefore <bcp14>MUST</bcp14> be turned into ".".</t>
</section> </section>
<section anchor="annex-annex"> <section anchor="annex-annex" numbered="true" removeInRFC="false" toc="i
<name>Annexes of Annexes</name> nclude" pn="section-6.4.2">
<t>When there are annexes to an annex, their corresponding identifiers <name slugifiedName="name-annexes-of-annexes">Annexes of Annexes</name
are created by adding to the identifier of the original annex those >
of the annexes that are connected with it (that is, attached to it)<br/> <t indent="0" pn="section-6.4.2-1">When there are annexes to an annex,
(e.g., Table 1 attached to the Annex A of the preceding legal act their corresponding identifiers are
has the following uniform name:<br/> created by adding to the identifier of the original annex those of the
"region.sicily;council:deliberation:1998-02-12;14:annex.a; annexes that are connected with it (that is, attached to it). For example,
borders.park:table.1;municipality.territories").</t> Table 1 attached to the Annex A of the preceding legal act has the
following uniform name:</t>
<artwork align="left" pn="section-6.4.2-2">
region.sicily;council:deliberation:1998-02-12;14:annex.a;
borders.park:table.1;municipality.territories
</artwork>
</section> </section>
</section> </section>
</section> </section>
<section anchor="syn-ver"> <section anchor="syn-ver" numbered="true" removeInRFC="false" toc="include"
<name>Specific Syntax of the Version Element of the "Expression"</name> pn="section-7">
<section anchor="the-version-element"> <name slugifiedName="name-specific-syntax-of-the-vers">Specific Syntax of
<name>The version Element</name> the Version Element of the "Expression"</name>
<section anchor="different-versions-of-a-legislative-document"> <section anchor="the-version-element" numbered="true" removeInRFC="false"
<name>Different Versions of a Legislative Document</name> toc="include" pn="section-7.1">
<t>The creation of an updated text of a document may have one of the <name slugifiedName="name-the-version-element">The Version Element</name
>
<section anchor="different-versions-of-a-legislative-document" numbered=
"true" removeInRFC="false" toc="include" pn="section-7.1.1">
<name slugifiedName="name-different-versions-of-a-leg">Different Versi
ons of a Legislative Document</name>
<t indent="0" pn="section-7.1.1-1">The creation of an updated text of
a document may have one of the
following forms:</t> following forms:</t>
<ul spacing="normal"> <dl spacing="normal" indent="3" newline="false" pn="section-7.1.1-2">
<li> <dt pn="section-7.1.1-2.1">"multi-version":</dt>
<t>"multi-version": when specific mark-ups which identify the modi <dd pn="section-7.1.1-2.2">Specific markups that identify the modifi
fied ed
parts of a document (added, substituted or deleted parts) and their parts of a document (added, substituted, or deleted parts) and their
related periods of effectiveness are indicated inside one single related periods of effectiveness are indicated inside a single
object (e.g., an xml file). Such a document will be able, in a object (e.g., an XML file). Such a document will be able, in a
dynamic way, to appear in different forms according to the dynamic way, to appear in different forms according to the
requested date of effectiveness. requested date of effectiveness.
In this document type, usually a set of metadata contains the In this document type, a set of metadata usually contains the
lifecycle of the document (from the original to the last life cycle of the document (from the original to the last
modification), including the validity time interval of each version modification), including the validity time interval of each version
and of each related text portion;</t> and of each related text portion.</dd>
</li> <dt pn="section-7.1.1-2.3">"single-version":</dt>
<li> <dd pn="section-7.1.1-2.4">A new and distinct object
<t>"single-version": when, on the contrary, a new and distinct obj
ect
is created for each amendment to the text at a given time. Each is created for each amendment to the text at a given time. Each
object is, therefore, characterized by its own period of validity. object is, therefore, characterized by its own period of validity.
In any case all the versions SHOULD be linked one another and In any case, all the versions <bcp14>SHOULD</bcp14> be linked to one another and
immediately navigable.</t> immediately navigable.</dd>
</li> </dl>
</ul> <t indent="0" pn="section-7.1.1-3">In a "multi-version" document, each
<t>In a "multi-version" document, each time interval should have a lin time interval should have a link
k to the related in-force document version that can be
to the related in-force document version which can be therefore
displayed. displayed.
In a "single-version" document, the metadata should contain links to In a "single-version" document, the metadata should contain links to
all the previous modifications and a link only to the following all the previous modifications and a link only to the following
version, if any.</t> version, if any.</t>
<t><xref target="RFC8288"/> can be used as reference to establish link s between <t indent="0" pn="section-7.1.1-4"><xref target="RFC8288" format="defa ult" sectionFormat="of" derivedContent="RFC8288"/> can be used as a reference to establish links between
different document versions, either in the "multi-version" or in the different document versions, either in the "multi-version" or in the
"single-version" document. According to <xref target="RFC8288"/> the following "single-version" document. According to <xref target="RFC8288" format="default" sectionFormat="of" derivedContent="RFC8288"/>, the following
relations are useful:</t> relations are useful:</t>
<ul spacing="normal"> <dl spacing="normal" indent="3" newline="false" pn="section-7.1.1-5">
<li> <dt pn="section-7.1.1-5.1">current (or last or last-version):</dt>
<t>current (or last or last-version): in-force version</t> <dd pn="section-7.1.1-5.2">in-force version</dd>
</li> <dt pn="section-7.1.1-5.3">self:</dt>
<li> <dd pn="section-7.1.1-5.4">this version</dd>
<t>self: this version</t> <dt pn="section-7.1.1-5.5">next:</dt>
</li> <dd pn="section-7.1.1-5.6">next version</dd>
<li> <dt pn="section-7.1.1-5.7">previous:</dt>
<t>next: next version</t> <dd pn="section-7.1.1-5.8">previous version</dd>
</li> <dt pn="section-7.1.1-5.9">first:</dt>
<li> <dd pn="section-7.1.1-5.10">original version</dd>
<t>previous: previous version</t> </dl>
</li> <t indent="0" pn="section-7.1.1-6">It is <bcp14>RECOMMENDED</bcp14> th
<li> at these relations be inserted in the header of
<t>first: original version</t>
</li>
</ul>
<t>It is RECOMMENDED that these relations are inserted in the header o
f
each version (if "single-version") or associated to each entry each version (if "single-version") or associated to each entry
containing a single URN (if "multi-version").</t> containing a single URN (if "multi-version").</t>
</section> </section>
<section anchor="ide-vers"> <section anchor="ide-vers" numbered="true" removeInRFC="false" toc="incl
<name>Identification of the Version</name> ude" pn="section-7.1.2">
<t>In order to identify the different time versions of the same act, t <name slugifiedName="name-identification-of-the-versi">Identification
o of the Version</name>
the uniform name of the original document has to be added a specific <t indent="0" pn="section-7.1.2-1">In order to identify the different
suffix.</t> time versions of the same act, a specific suffix has to be added to
<t>Such a suffix identifies each version of a legal provision and the uniform name of the original document.</t>
<t indent="0" pn="section-7.1.2-2">Such a suffix identifies each versi
on of a legal provision and
includes, first and foremost, one of the following elements:</t> includes, first and foremost, one of the following elements:</t>
<ul spacing="normal"> <ul spacing="normal" bare="false" empty="false" indent="3" pn="section
<li> -7.1.2-3">
<t>the issuing date of the last amending measure taken into accoun <li pn="section-7.1.2-3.1">
t;</t> <t indent="0" pn="section-7.1.2-3.1.1">The issuing date of the las
t amending measure taken into account.</t>
</li> </li>
<li> <li pn="section-7.1.2-3.2">
<t>the date in which the communication of the rectification or of <t indent="0" pn="section-7.1.2-3.2.1">The date that the communica
the tion of the rectification or
errata corrige, is published;</t> errata corrige was published.</t>
</li> </li>
<li> <li pn="section-7.1.2-3.3">
<t>a specification which must identify the reason concerning the <t indent="0" pn="section-7.1.2-3.3.1">A specification that must i
dentify 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).</t> for the cases in which the date is not usually used (e.g., bills).</t>
</li> </li>
</ul> </ul>
<t>It is possible to add further specifications that will <t indent="0" pn="section-7.1.2-4">It is possible to add further speci fications that will
distinguish each of the different versions of the text to guarantee distinguish each of the different versions of the text to guarantee
identifier unequivocalness. For example with regard to changes of the identifier unequivocalness. Examples include changes of the
in-force or effectiveness of any partition or portion of the text in-force or effectiveness of a formal partition or portion of the text
itself (e.g., when the amendments introduced by an act are applied at itself (e.g., when the amendments introduced by an act are applied at
different times) or different events occurring on the same date.</t> different times) or different events occurring on the same date.</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-7.1.2-5">
version = (amendment-date / specification) version = (amendment-date / specification)
*(";" (event-date / event)) *(";" (event-date / event))
]]></artwork> </sourcecode>
<t>where:</t> <t indent="0" pn="section-7.1.2-6">where:</t>
<ul spacing="normal"> <dl newline="false" spacing="normal" indent="3" pn="section-7.1.2-7">
<li> <dt pn="section-7.1.2-7.1">amendment-date:</dt>
<t>amendment-date contains the issuing date of the last considered <dd pn="section-7.1.2-7.2">Contains the issuing date of the last con
amendment or of the last communication of amendment. In case the sidered
amendment or of the last communication of amendment. If the
original text introduces differentiated periods in which an act is original text introduces differentiated periods in which an act is
effective and the information system produces one version for each effective and the information system produces one version for each
of them, such element contains the string "original" expressed in of them, such element contains the string "original" expressed in
the language of the act or version;</t> the language of the act or version.</dd>
</li> <dt pn="section-7.1.2-7.3">specification:</dt>
<li> <dd pn="section-7.1.2-7.4">Contains any information that is useful t
<t>specification contains any information useful to identify unamb o identify the version unambiguously
iguously and univocally.</dd>
and univocally the version;</t> <dt pn="section-7.1.2-7.5">event-date:</dt>
</li> <dd pn="section-7.1.2-7.6">Contains the date in which a version is p
<li> ut into
<t>event-date contains the date in which a version is put into force, is effective, or is published.</dd>
force, is effective or is published;</t> <dt pn="section-7.1.2-7.7">event:</dt>
</li> <dd pn="section-7.1.2-7.8">A name assigned to the event producing a
<li> further version
<t>event is a name assigned to the event producing a further versi (e.g., amendment, decision, etc.).</dd>
on </dl>
(e.g., amendment, decision, etc.).</t> <t indent="0" pn="section-7.1.2-8">The issuing date of an amending act
</li> was chosen as the identifier of a
</ul> version because it can be obtained from the heading (formal data). For example,
<t>The issuing date of an amending act was chosen as identifier of a the name "state:royal.decree:1941-01-30;12@1998-02-19"
version because it can be obtained from the heading (formal data)<br/>
(e.g., 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.<br/> No. 51" without any indication of its actual entry into force.
The same uniform name with the additional ending ";1999-01-01" indicates The same uniform name with the additional ending ";1999-01-01" indicates
the in-force or effective version starting in a different date (from the in-force or effective version starting on a different date (1/1/99).</t>
1/1/99).</t> <t indent="0" pn="section-7.1.2-9">For full compatibility, every updat
<t>For a full compatibility, every updating of a text or of the e of text, or of the
effectiveness of a "multi-version" document implies the creation of a effectiveness, of a "multi-version" document implies the creation of a
new uniform name, even if the object remains only one, containing the new uniform name, even if the object remains single, containing the
identifier of the virtually generated version, exactly as in the case identifier of the virtually generated version, as in the case
of a "single-version" document. A specific meta-data will associate of a "single-version" document.
every uniform name with the period of time during which such a name Specific metadata will associate
together with its corresponding text is to be considered valid<br/> every uniform name with the period of time during which such a name,
(e.g., the multi-version document containing the "R.D. of 01/30/1941, together with its corresponding text, is to be considered valid
(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 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").</t> version "state:royal.decree:1941-01-30;12@1998-02-19").</t>
<t>Please note that in case of attachments or annexes, the creation of a <t indent="0" pn="section-7.1.2-10">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 new 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, the to guarantee their alignment (i.e., the main document,
attachments and annexes).</t> attachments, and annexes).</t>
<t>As specified in <xref target="dat-form"/>, all the dates can have, <t indent="0" pn="section-7.1.2-11">As specified in <xref target="dat-
in addition to the ISO format, form" format="default" sectionFormat="of" derivedContent="Section 3.6"/>, all th
also the date typical of the jurisdiction.</t> e dates can have the date typical of the jurisdiction in addition to the date in
ISO format.</t>
</section> </section>
</section> </section>
</section> </section>
<section anchor="urn-lex-syn"> <section anchor="urn-lex-syn" numbered="true" removeInRFC="false" toc="inclu
<name>Summary of the Syntax of the Uniform Names of the "lex" Namespace</n de" pn="section-8">
ame> <name slugifiedName="name-summary-of-the-syntax-of-th">Summary of the Synt
<t>;-------------------------------------------------------------------<br ax of the Uniform Names of the LEX Namespace</name>
/> <t indent="0" pn="section-8-1">;------------------------------------------
; Structure of a Uniform Resource Name (URN) of the "lex" namespace<br/> -------------------------<br/>
; - NID-lex = namespace<br/> ; Structure of a Uniform Resource Name (URN) of the LEX namespace<br/>
; - NSS-lex = specific name<br/> ; - NID = LEX namespace identifier<br/>
; - NSS = LEX Namespace Specific String<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-2">
URN-lex = "urn:" NID-lex ":" NSS-lex URN = "urn:" NID ":" NSS
NID-lex = "lex" NID = "lex"
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-3">;------------------------------------------
/> -------------------------<br/>
; Structure of a "lex" specific name<br/> ; Structure of a LEX specific name<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-4">
NSS-lex = jurisdiction ":" local-name NSS = jurisdiction ":" local-name
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-5">;------------------------------------------
/> -------------------------<br/>
; Structure of the jurisdiction element<br/> ; Structure of the jurisdiction element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-6">
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
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-7">;------------------------------------------
/> -------------------------<br/>
; Structure of the local-name element<br/> ; Structure of the local-name element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-8">
local-name = work ["@" expression] ["$" manifestation] local-name = work ["@" expression] ["$" manifestation]
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-9">;------------------------------------------
/> -------------------------<br/>
; Structure of the work element<br/> ; Structure of the work element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-10">
work = authority ":" measure ":" details *(":" annex) work = authority ":" measure ":" details *(":" annex)
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-11">;-----------------------------------------
/> --------------------------<br/>
; Structure of the authority element<br/> ; Structure of the authority element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-12">
authority = issuer *("+" issuer) authority = issuer *("+" issuer)
issuer = (institution *(";" body-function)) / office issuer = (institution *(";" body-function)) / office
institution = alf-dot institution = alf-dot
body-function = alf-dot body-function = alf-dot
office = alf-dot office = alf-dot
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-13">;-----------------------------------------
/> --------------------------<br/>
; Structure of the measure element<br/> ; Structure of the measure element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-14">
measure = measure-type *(";" specification) measure = measure-type *(";" specification)
measure-type = alf-dot measure-type = alf-dot
specification = alf-dot specification = alf-dot
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-15">;-----------------------------------------
/> --------------------------<br/>
; Structure of the details element<br/> ; Structure of the details element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-16">
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
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-17">;-----------------------------------------
/> --------------------------<br/>
; Structure of the annex element<br/> ; Structure of the annex element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-18">
annex = annex-id *(";" specification) annex = annex-id *(";" specification)
annex-id = alf-dot annex-id = alf-dot
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-19">;-----------------------------------------
/> --------------------------<br/>
; Structure of the expression element<br/> ; Structure of the expression element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-20">
expression = version [":" language] expression = version [":" language]
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-21">;-----------------------------------------
/> --------------------------<br/>
; Structure of the version element<br/> ; Structure of the version element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-22">
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
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-23">;-----------------------------------------
/> --------------------------<br/>
; Structure of the language element<br/> ; Structure of the language element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-24">
language = 2*3alfa *["-" extlang] / 4*8alfa language = 2*3alfa *["-" extlang] / 4*8alfa
extlang = 3alfa *2("-" 3alfa) extlang = 3alfa *2("-" 3alfa)
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-25">;-----------------------------------------
/> --------------------------<br/>
; Structure of the manifestation element<br/> ; Structure of the manifestation element<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-26">
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
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-27">;-----------------------------------------
/> --------------------------<br/>
; Structure of the date<br/> ; Structure of the date<br/>
;-------------------------------------------------------------------</t> ;-------------------------------------------------------------------</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-28">
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)
]]></artwork> </sourcecode>
<t>;-------------------------------------------------------------------<br <t indent="0" pn="section-8-29">;-----------------------------------------
/> --------------------------<br/>
; Allowed, reserved and future characters<br/> ; Allowed, reserved and future characters<br/>
;-------------------------------------------------------------------<br/> ;-------------------------------------------------------------------<br/>
; - allowed = alfadot / other / reserved<br/> ; - allowed = alfadot / other / reserved<br/>
; - reserved = ":" / "@" / "$" / "+" / "|" / ";" / "," / "~"<br/> ; - reserved = ":" / "@" / "$" / "+" / "|" / ";" / "," / "~"<br/>
; - future = "*" / "!"</t> ; - future = "*" / "!"</t>
<artwork><![CDATA[ <sourcecode type="abnf" markers="false" pn="section-8-30">
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 1869 skipping to change at line 2209
uppercase = %x41-5A ; upper-case ASCII letters (A-Z) uppercase = %x41-5A ; upper-case ASCII letters (A-Z)
DIGIT = %x30-39 ; decimal digits (0-9) DIGIT = %x30-39 ; decimal digits (0-9)
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 = "-" / "_" / "'" / "=" / "(" / ")"
]]></artwork> </sourcecode>
</section> </section>
<section anchor="the-procedure-of-uniform-names-assignment"> <section anchor="the-procedure-of-uniform-names-assignment" numbered="true"
<name>The Procedure of Uniform Names Assignment</name> removeInRFC="false" toc="include" pn="section-9">
<section anchor="specifying-the-jurisdiction-element-of-the-lex-identifier <name slugifiedName="name-procedure-of-uniform-names-">Procedure of Unifor
"> m Names Assignment</name>
<name>Specifying the jurisdiction Element of the LEX Identifier</name> <section anchor="specifying-the-jurisdiction-element-of-the-lex-identifier
<t>Under the "lex" namespace, each country or international organization " numbered="true" removeInRFC="false" toc="include" pn="section-9.1">
is assigned with a jurisdiction code, which characterizes the URNs of <name slugifiedName="name-specifying-the-jurisdiction">Specifying the Ju
the source of law of that country or jurisdiction. This code is risdiction Element of the LEX Identifier</name>
assigned according to ccTLD (as well as TLDN (Top Level Domain Name) <t indent="0" pn="section-9.1-1">Under the LEX namespace, each country o
or DN (Domain Name) for the organizations) representation and it is r international organization
the value of the jurisdiction-code element, which preserves cross- is assigned a jurisdiction-code, which characterizes the URNs of
country uniqueness of the identifiers.</t> the 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 (Domain Name) for organizations) representation, and it is
the value of the jurisdiction-code element, which preserves cross-country unique
ness of the identifiers.</t>
</section> </section>
<section anchor="jurisdictional-registrar-for-names-assignment"> <section anchor="jurisdictional-registrar-for-names-assignment" numbered="
<name>Jurisdictional Registrar for Names Assignment</name> true" removeInRFC="false" toc="include" pn="section-9.2">
<t>Any country or jurisdiction, who intends to adopt this schema, MUST <name slugifiedName="name-jurisdictional-registrar-fo">Jurisdictional Re
identify a Jurisdictional Registrar, an organization which shares and gistrar for Names Assignment</name>
<t indent="0" pn="section-9.2-1">Any country or jurisdiction that intend
s to adopt this schema <bcp14>MUST</bcp14>
identify a Jurisdictional Registrar, an organization that shares and
defines the structure of the optional part (jurisdiction-unit) of defines the structure of the optional part (jurisdiction-unit) of
the name, according to the organization of the state or institution the name, according to the organization of the state or institution
(for details see <xref target="jur-cod-regist"/>). It must appoint a Jurisdicti (for details, see <xref target="jur-cod-regist" format="default" sectionFormat="
onal of" derivedContent="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 jurisdiction
registration of a jurisdiction code. For example, in a federal state -code.</t>
a jurisdiction-unit corresponding to the name of each member state<br/> <t indent="0" pn="section-9.2-2">For example, in a federal state,
(e.g. "br;sao.paulo", "br;minas.gerais", etc.) may be defined.</t> a jurisdiction-unit corresponding to the name of each Member State
<t>The process of assigning the local-name is managed by each (e.g., "br;sao.paulo", "br;minas.gerais", etc.) may be defined.</t>
<t indent="0" pn="section-9.2-3">The process of assigning the local-name
is managed by each
specific country or jurisdiction under the related jurisdiction specific country or jurisdiction under the related jurisdiction
element.</t> element.</t>
<t>In any country the Jurisdictional Registrar shares and defines the <t indent="0" pn="section-9.2-4">In any country, the Jurisdictional Regi strar 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.</t> its own state or institution organization.</t>
<t>Such a Registrar MUST establish, according to the guidelines <t indent="0" pn="section-9.2-5">The Jurisdictional Registrar <bcp14>MUS T</bcp14> establish, according to the guidelines
indicated in this document, a uniform procedure within the indicated in this document, a uniform procedure within the
country or organization to define local-name elements, to take country or organization to define local-name elements, make
decisions upon normalizations and finally to solve and avoid possible decisions about normalizations, solve and avoid possible
name collisions as well as to maintain authoritative registries of name collisions, and maintain authoritative registries of
various kinds (e.g., for authorities, types of measures, etc.). In various kinds (e.g., for authorities, types of measures, etc.). In
particular, accurate point-in-time representations of the structure particular, accurate point-in-time representations of the structure
and naming of government entities are important to semantically-aware and naming of government entities are important to semantically aware
applications in this domain.</t> applications in this domain.</t>
<t>Moreover, the Registrar shares and defines the rules to construct <t indent="0" pn="section-9.2-6">Moreover, the Jurisdictional Registrar shares and defines the rules to construct
partition IDs for each document type, possibly in accordance with partition IDs for each document type, possibly in accordance with
those already defined in other jurisdictions.</t> those already defined in other jurisdictions.</t>
<t>Finally, the Registrar will develop and publish the rules and the <t indent="0" pn="section-9.2-7">Finally, the Jurisdictional Registrar w
guidelines for the local-name construction as well as the ill develop and publish the rules and
predefined values and codes. The Registrar should also promote the guidelines for the local-name construction as well as the predefined
urn:lex identifier for the sources of law of its jurisdiction.</t> values and codes. The Jurisdictional Registrar should also promote the L
<t>Such a set of rules will have to be followed by all institutional EX URN
bodies adopting the URN LEX identification system in a country or identifier for the sources of law of its jurisdiction.</t>
jurisdiction, as well as by private publishers, and each of them will <t indent="0" pn="section-9.2-8">Such a set of rules will have to be fol
lowed by all institutional
bodies adopting the LEX URN identification system in a country or
jurisdiction, as well as by private publishers. Each of them will
be responsible for assigning names to their domains.</t> be responsible for assigning names to their domains.</t>
</section> </section>
<section anchor="identifier-uniqueness"> <section anchor="identifier-uniqueness" numbered="true" removeInRFC="false
<name>Identifier Uniqueness</name> " toc="include" pn="section-9.3">
<t>Identifiers in the "lex" namespace are defined through a <name slugifiedName="name-identifier-uniqueness">Identifier Uniqueness</
name>
<t indent="0" pn="section-9.3-1">Identifiers in the LEX namespace are de
fined through a
jurisdiction element assigned to the sources of law of a specific jurisdiction element assigned to the sources of law of a specific
country or organization, and a local-name assigned by the issuing country or organization, and a local-name is assigned by the issuing
authority, in conformance with the syntax defined in <xref target="creation"/>. authority in conformance with the syntax defined in <xref target="creation" form
The at="default" sectionFormat="of" derivedContent="Section 5"/>. The
main elements (authority and type of measure) of the local-name are main 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 <bcp14>MUST</bcp14 >
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 and make accessible its registries.</t> constructed and <bcp14>MUST</bcp14> update its registries and make them accessib
<t>Any enacting authority is responsible to define formal parameters to le.</t>
guarantee local name uniqueness by attributing, if necessary, a <t indent="0" pn="section-9.3-2">Any enacting authority is responsible f
conventional internal number, which, combined with the other local- or defining formal parameters to
name components (authority, measure and date), builds a unique guarantee local-name uniqueness by attributing, if necessary, a
conventional internal number, which when combined with the other local-name comp
onents (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.</t> of previously assigned names.</t>
</section> </section>
<section anchor="identifier-persistence-considerations"> <section anchor="identifier-persistence-considerations" numbered="true" re
<name>Identifier Persistence Considerations</name> moveInRFC="false" toc="include" pn="section-9.4">
<t>The persistence of identifiers depends on the durability of the <name slugifiedName="name-identifier-persistence-cons">Identifier Persis
tence Considerations</name>
<t indent="0" pn="section-9.4-1">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
identified by the assigned URNs.</t> identified by the assigned URNs.</t>
<t>In particular, the CNR is responsible of maintaining <t indent="0" pn="section-9.4-2">In particular, CNR is responsible for m
the uniqueness of the jurisdiction element; given that the aintaining
the uniqueness of the jurisdiction element. Given that the
jurisdiction is assigned on the basis of the long-held ccTLD jurisdiction is assigned on the basis of the long-held ccTLD
representation of the country (or the TLDN or DN of the organization) representation of the country (or the TLDN or DN of the organization)
and that the country or organization associated code is expected to and that the associated code for country or organization is expected to
continue indefinitely, the URN also persists indefinitely.</t> continue indefinitely, the URN also persists indefinitely.</t>
<t>The rules for the construction of the name are conceived to delegate <t indent="0" pn="section-9.4-3">The rules for the construction of the n
the responsibility of their uniqueness to a set of authorities which ame are conceived to delegate
the responsibility of their uniqueness to a set of authorities that
is identified within each country or organization.</t> is identified within each country or organization.</t>
<t>Therefore, each authority is responsible for assigning URNs which <t indent="0" pn="section-9.4-4">Therefore, each authority is responsibl e for assigning URNs that
have a very long life expectancy and can be expected to remain unique have a very long life expectancy and can be expected to remain unique
for the foreseeable future. Practical and political considerations, for the foreseeable future. Practical and political considerations,
as well as diverse local forms of government organization, will as well as diverse local forms of government organization, will
result in different methods of assigning responsibility for different result in different methods of assigning responsibility for different
levels of the name.</t> levels of the name.</t>
<t>Where this cannot be accomplished by the implementation of an <t indent="0" pn="section-9.4-5">Where this cannot be accomplished by th e implementation of an
authoritative hierarchy, it is highly desirable that it be done by authoritative hierarchy, it is highly desirable that it be done by
creating consensus around a series of published rules for the creating consensus around a series of published rules for the
creation and administration of names by institutions and bodies that creation and administration of names by institutions and bodies that
operate by means of collaboration rather than compulsion.</t> operate by means of collaboration rather than compulsion.</t>
<t>Issuing authorities that operate in more localized scopes, ranging <t indent="0" pn="section-9.4-6">Issuing authorities that operate in mor
from the national down to the very local, MUST equally take e localized scopes, ranging
from national scope down to very local scope, <bcp14>MUST</bcp14> equally take
responsibility for the persistence of identifiers within their scope.</t> responsibility for the persistence of identifiers within their scope.</t>
</section> </section>
</section> </section>
<section anchor="recommendations-for-the-resolution-process"> <section anchor="recommendations-for-the-resolution-process" numbered="true"
<name>Recommendations for the Resolution Process</name> removeInRFC="false" toc="include" pn="section-10">
<section anchor="the-general-architecture-of-the-system"> <name slugifiedName="name-recommendations-for-the-res">Recommendations for
<name>The General Architecture of the System</name> the Resolution Process</name>
<t>The task of the resolution service is that of associating a LEX <section anchor="the-general-architecture-of-the-system" numbered="true" r
identifier with a specific document address on the Internet. By emoveInRFC="false" toc="include" pn="section-10.1">
<name slugifiedName="name-general-architecture-of-the">General Architect
ure of the System</name>
<t indent="0" pn="section-10.1-1">The task of the resolution service is
to associate a LEX
identifier with a specific document address on the Internet. In
contrast with systems that can be constructed around rigorous and contrast with systems that can be constructed around rigorous and
enforceable engineering premises, such as DNS, the "lex" namespace enforceable engineering premises, such as DNS, the LEX namespace
resolver will be expected to cope with a wide variety of inputs resolver will be expected to cope with a wide variety of inputs
incomplete or partially incorrect, particularly those that are incomplete or partially incorrect, particularly those
created by the automated extraction of created by the automated extraction of
references from texts. In this document, references from texts. In this document,
the result is a particular emphasis on a flexible and robust resolver the result is a particular emphasis on a flexible and robust resolver
design.</t> design.</t>
<t>The system has a distributed architecture based on two fundamental <t indent="0" pn="section-10.1-2">The system has a distributed architect
components: a chain of information in DNS (Domain Name System) and a ure based on two fundamental
components: a chain of information in the DNS and a
series of resolution services from URNs to URLs, each competent series of resolution services from URNs to URLs, each competent
within a specific domain of the namespace.</t> within a specific domain of the namespace.</t>
<t>The client retrieves the document associated with this URN using the <t indent="0" pn="section-10.1-3">The client retrieves the document asso
procedure described in <xref target="RFC3404"/>, which starts with a DNS NAPTR ciated with this URN using the
procedure described in <xref target="RFC3404" format="default" sectionFormat="of
" derivedContent="RFC3404"/>, which starts with a DNS NAPTR
query.</t> query.</t>
<t>A resolution service can delegate the resolution and management of <t indent="0" pn="section-10.1-4">A resolution service can delegate the
hierarchically-dependent portions of the name. resolution and management of
hierarchically dependent portions of the name.
Delegation of this responsibility will not be unreasonably withheld Delegation of this responsibility will not be unreasonably withheld
provided that the processes for their resolution and management are provided that the processes for their resolution and management are
robust and are followed.</t> robust and followed.</t>
<t>For the "lex" namespace, CNR will maintain in the lex-nameserver.nic. <t indent="0" pn="section-10.1-5">For the LEX namespace, CNR will 1) mai
it ntain the root zone of the
(see <xref target="iana"/>) the root zone of the chain resolution (equivalent chain resolution, equivalent to "lex.urn.arpa" (see <xref target="RFC3405" forma
to "lex.urn.arpa", see <xref target="RFC3405"/>) and, in correspondence with the t="default" sectionFormat="of" derivedContent="RFC3405"/>), in
adhesion (see <xref target="jur-cod-regist"/>) of a new country (e.g., "br") or the lex-nameserver.nic.it (see <xref target="iana" format="default" sectionForma
organization, will update the DNS information with a new record to t="of" derivedContent="Section 12"/>) and 2) update the DNS
delegate the relative resolution. This may be obtained by a regular information with a new record to delegate the relative resolution
when a new country (e.g., "br") or organization is added
(see <xref target="jur-cod-regist" format="default" sectionFormat="of" derivedCo
ntent="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").</t> "lex.senado.gov.br").</t>
<t>Likewise, the institution responsible for the jurisdiction uniform <t indent="0" pn="section-10.1-6">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 similar way it can delegate the resolution of names. In a similar way, it can delegate the resolution of
country/organization sub-levels (e.g., "urn:lex:br;sao.paolo") country/organization sub-levels (e.g., "urn:lex:br;sao.paolo")
towards the relative zone (e.g., "lex.sao-paolo.gov.br").</t> towards the relative zone (e.g., "lex.sao-paolo.gov.br").</t>
<t>Such DNS routing chain does not work for all the URN components <t indent="0" pn="section-10.1-7">Such a DNS routing chain does not work
containing %-encoded characters. Therefore, when converting a "lex" URN for all the URN components
in UTF-8 code to a DNS query, clients MUST perform any necessary punycode containing percent-encoded characters. Therefore, when converting a LEX URN
conversion <xref target="RFC5891"/> before sending the query.</t> in UTF-8 code to a DNS query, clients <bcp14>MUST</bcp14> perform any necessary
<t>The resolution service is made up of two elements: a knowledge base punycode
(consisting in a catalogue or a set of transformation rules) and a conversion <xref target="RFC5891" format="default" sectionFormat="of" derivedCon
software to query the knowledge base itself.</t> tent="RFC5891"/> before sending the query.</t>
<t indent="0" pn="section-10.1-8">The resolution service is made up of t
wo elements: a knowledge base
(consisting in a catalogue or a set of transformation rules) and
software to query the knowledge base.</t>
</section> </section>
<section anchor="catalogues-for-resolution"> <section anchor="catalogues-for-resolution" numbered="true" removeInRFC="f
<name>Catalogues for Resolution</name> alse" toc="include" pn="section-10.2">
<t>Incompleteness and inaccuracy are rather frequent in legal citations, <name slugifiedName="name-catalogues-for-resolution">Catalogues for Reso
and incomplete or inaccurate uniform names of the referred document lution</name>
are thus likely to be built from textual references (this is even <t indent="0" pn="section-10.2-1">Incompleteness and inaccuracy are rath
er frequent in legal citations;
thus, incomplete or inaccurate uniform names of the referred document
are likely to be built from textual references (this is even
more frequent if they are created automatically through a specific more frequent if they are created automatically through a specific
parser). For this reason, the implementation of a catalogue, based on parser). For this reason, the implementation of a catalogue, based on
a relational-database, is suggested, as it will lead to a higher a relational database, is suggested, as it will lead to higher
flexibility in the resolution process.</t> flexibility in the resolution process.</t>
<t>In addition the catalogue must manage the aliases, the various <t indent="0" pn="section-10.2-2">In addition, the catalogue must manage
versions and languages of the same source of law as well as the the aliases, the various
versions and languages of the same source of law, and the
related manifestations.</t> related manifestations.</t>
<t>It is suggested that each enacting authority implements its own <t indent="0" pn="section-10.2-3">It is suggested that each enacting aut hority implement its own
catalogue, assigning a corresponding unambiguous uniform name to each catalogue, assigning a corresponding unambiguous uniform name to each
resource.</t> resource.</t>
</section> </section>
<section anchor="suggested-resolver-behaviour"> <section anchor="suggested-resolver-behaviour" numbered="true" removeInRFC
<name>Suggested Resolver Behaviour</name> ="false" toc="include" pn="section-10.3">
<t>First, the resolver SHOULD separate the part corresponding to <name slugifiedName="name-suggested-resolver-behavior">Suggested Resolve
the partition ID, through the "~" separator, from the document name.</t> r Behavior</name>
<t>The resolution process SHOULD implement a normalization of the <t indent="0" pn="section-10.3-1">First, the resolver <bcp14>SHOULD</bcp
14> separate the part corresponding to
the partition ID from the document name, with the "~" separator.</t>
<t indent="0" pn="section-10.3-2">The resolution process <bcp14>SHOULD</
bcp14> 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.</t> authorities and types of measure registries are useful.</t>
<t>The resolver SHOULD then query the catalogue searching for the URN <t indent="0" pn="section-10.3-3">The resolver <bcp14>SHOULD</bcp14> the
which corresponds exactly to the given one (normalized if necessary). n query the catalogue searching for the URN
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, heuristic approach (based on partial incomplete, an iterative and heuristic approach (based on partial
matches) is indicated. Incomplete matches) is indicated. Incomplete
references (not including all the elements to create the canonical references (not including all the elements to create the canonical
uniform name) are normal and natural; for a human reader, the uniform name) are normal and natural; for a human reader, the
reference would be "completed" by contextual understanding of the reference would be "completed" by contextual understanding of the
reference in the document in which it occurs.</t> reference in the document in which it occurs.</t>
<t>In this phase, the resolver should use the partition ID information <t indent="0" pn="section-10.3-4">In this phase, the resolver should use
to retrieve, if it is possible, only the referred partition, the partition ID information
otherwise to return the entire document.</t> to retrieve, if it is possible, only the referred partition;
<t>Lacking more specific indications, the resolver SHOULD select the otherwise, the entire document is returned.</t>
best (most recent) version of the requested source of law, and <t indent="0" pn="section-10.3-5">Lacking more specific indications, the
resolver <bcp14>SHOULD</bcp14> select the
best (most recent) version of the requested source of law and
provide all the manifestations with their related items. provide all the manifestations with their related items.
A more specific indication in the uniform name to be resolved will, A more specific indication in the uniform name to be resolved will,
of course, result in a more selective retrieval, based on any of course, result in a more selective retrieval, based on any
suggested expression and/or manifestations components (e.g. date, suggested expression and/or manifestations components (e.g., date,
language, format, etc.).</t> language, format, etc.).</t>
<t>Finally, the resolver SHOULD append to URLs the "#" character <t indent="0" pn="section-10.3-6">Finally, the resolver <bcp14>SHOULD</b
followed by partition ID, transforming it in a URI fragment for cp14> append the "#" character
followed by the partition ID to URLs, to create URI fragments for
browser pointing.</t> browser pointing.</t>
</section> </section>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations" numbered="true" removeInRFC="false
<name>Security Considerations</name> " toc="include" pn="section-11">
<t>Security considerations are those normally associated with the use and <name slugifiedName="name-security-considerations">Security Considerations
</name>
<t indent="0" pn="section-11-1">Security considerations are those normally
associated with the use and
resolution URNs in general. Additional security considerations concerning resolution URNs in general. Additional security considerations concerning
the authenticity of a document do not pertain to the LEX specifications, the authenticity of a document do not pertain to the LEX specifications,
but they pertain security and trust issues which can be addressed with other mea but they pertain to security and trust issues that can be addressed with other m
ns, eans,
like digital signature, data encryption, etc.</t> like digital signatures, data encryption, etc.</t>
</section> </section>
<section anchor="iana"> <section anchor="iana" numbered="true" removeInRFC="false" toc="include" pn=
<name>IANA Considerations</name> "section-12">
<t>IANA has already registered the "lex" namespace, according to the <name slugifiedName="name-iana-considerations">IANA Considerations</name>
template at section 2. Registration has been accomplished as the <t indent="0" pn="section-12-1">IANA has registered LEX namespace in the
Formal URN Namespace registry described by <xref target="RFC8141"/>.</t> "Formal URN Namespaces" registry <xref target="RFC8141" format="default" section
<t>In addition, to activate a distributed resolution system, the one-off Format="of" derivedContent="RFC8141"/>.</t>
registration of the following NAPTR record is requested <t indent="0" pn="section-12-2">In addition, to activate a distributed res
in the URN.ARPA domain:</t> olution system, IANA has registered the following NAPTR record in the URN.ARPA d
<artwork><![CDATA[ omain:</t>
<sourcecode type="dns-rr" markers="false" pn="section-12-3">
lex.urn.arpa. lex.urn.arpa.
IN NAPTR 100 10 "" "" "" lex-nameserver.nic.it. IN NAPTR 100 10 "" "" "" lex-nameserver.nic.it.
]]></artwork> </sourcecode>
<t>where lex-nameserver.nic.it indicates the server of CNR (see section 2. <t indent="0" pn="section-12-4">Note that lex-nameserver.nic.it indicates
2) the CNR server (see <xref target="jur-cod-regist" format="default" sectionFormat
that is responsible for the resolution of the "lex" namespace at the time of thi ="of" derivedContent="Section 2.2"/>)
s writing.</t> that is responsible for the resolution of the LEX namespace at the time of this
</section> writing.</t>
<section anchor="acknowledgements">
<name>Acknowledgements</name>
<t>The authors of this document wish to thank all the supporters for
giving suggestions and comments.</t>
<t>They are also grateful to the Legislative XML community <xref target="S
ART"/> for the
interesting discussions on this topic and to the Working Group
"Identification of the legal resources through URNs" of Italian
NormeInRete project for the provided guidance <xref target="SPIN"/>.</t>
<t>The authors owe a debt of gratitude to Tom Bruce, former director of th
e
Legal Information Institute of the Cornell University Law School, for
his contribution in revising this document and sharing fruitful
discussions which greatly improved the final draft. The authors wish
to specially thank Marc van Opijnen (Dutch Ministry of Security and
Justice) for his valuable comments on LEX specifications which
contributed to improve the final result, as well as for the common
work aimed to harmonize ECLI and LEX specifications. Thanks also to
Joao Alberto de Oliveira Lima, legislative system analyst of the
Brazilian Federal Senate, and to Attila Torcsvari, information
management consultant, for their detailed comments on the first
drafts of this document, which provided significant hints to the
final version of the standard, and to Robert Richards of the Legal
Information Institute (Cornell University Law School), promoter and
maintainer of the Legal Informatics Research social network, as well
as to the members of this network, for their valuable comments on
this proposal.</t>
<t>Finally, many thanks go to Loriana Serrotti who significantly
contributed to the first drafting of this document.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references anchor="sec-combined-references"> <references pn="section-13">
<name>References</name> <name slugifiedName="name-references">References</name>
<references anchor="sec-normative-references"> <references anchor="sec-normative-references" pn="section-13.1">
<name>Normative References</name> <name slugifiedName="name-normative-references">Normative References</na
<reference anchor="RFC2045" target="https://www.rfc-editor.org/info/rfc2 me>
045" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2045.xml"> <reference anchor="ISO.8601-1.2019" target="https://www.iso.org/standard
/70907.html" quoteTitle="true" derivedAnchor="ISO.8601-1.2019">
<front>
<title>Date and time - Representations for information interchange</
title>
<author>
<organization showOnFrontPage="true">ISO</organization>
</author>
<date month="February" year="2019"/>
</front>
<seriesInfo name="ISO" value="8601-1:2019"/>
</reference>
<reference anchor="ISO.8601-2.2019" target="https://www.iso.org/standard
/70908.html" quoteTitle="true" derivedAnchor="ISO.8601-2.2019">
<front>
<title>Data elements and interchange formats - Information interchan
ge - Representation of dates and times</title>
<author>
<organization showOnFrontPage="true">ISO</organization>
</author>
<date month="February" year="2019"/>
</front>
<seriesInfo name="ISO" value="8601-2:2019"/>
</reference>
<reference anchor="RFC2045" target="https://www.rfc-editor.org/info/rfc2
045" quoteTitle="true" derivedAnchor="RFC2045">
<front> <front>
<title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title> <title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
<author fullname="N. Freed" initials="N." surname="Freed"/> <author fullname="N. Freed" initials="N." surname="Freed"/>
<author fullname="N. Borenstein" initials="N." surname="Borenstein"/ > <author fullname="N. Borenstein" initials="N." surname="Borenstein"/ >
<date month="November" year="1996"/> <date month="November" year="1996"/>
<abstract> <abstract>
<t>This initial document specifies the various headers used to des cribe the structure of MIME messages. [STANDARDS-TRACK]</t> <t indent="0">This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="2045"/> <seriesInfo name="RFC" value="2045"/>
<seriesInfo name="DOI" value="10.17487/RFC2045"/> <seriesInfo name="DOI" value="10.17487/RFC2045"/>
</reference> </reference>
<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2 119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2 119" quoteTitle="true" derivedAnchor="RFC2119">
<front> <front>
<title>Key words for use in RFCs to Indicate Requirement Levels</tit le> <title>Key words for use in RFCs to Indicate Requirement Levels</tit le>
<author fullname="S. Bradner" initials="S." surname="Bradner"/> <author fullname="S. Bradner" initials="S." surname="Bradner"/>
<date month="March" year="1997"/> <date month="March" year="1997"/>
<abstract> <abstract>
<t>In many standards track documents several words are used to sig nify the requirements in the specification. These words are often capitalized. T his document defines these words as they should be interpreted in IETF documents . This document specifies an Internet Best Current Practices for the Internet Co mmunity, and requests discussion and suggestions for improvements.</t> <t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often cap italized. This document defines these words as they should be interpreted in IET F documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t >
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="14"/> <seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/> <seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference> </reference>
<reference anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3 <reference anchor="RFC3404" target="https://www.rfc-editor.org/info/rfc3
629" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml"> 404" quoteTitle="true" derivedAnchor="RFC3404">
<front>
<title>UTF-8, a transformation format of ISO 10646</title>
<author fullname="F. Yergeau" initials="F." surname="Yergeau"/>
<date month="November" year="2003"/>
<abstract>
<t>ISO/IEC 10646-1 defines a large character set called the Univer
sal Character Set (UCS) which encompasses most of the world's writing systems. T
he originally proposed encodings of the UCS, however, were not compatible with m
any current applications and protocols, and this has led to the development of U
TF-8, the object of this memo. UTF-8 has the characteristic of preserving the fu
ll US-ASCII range, providing compatibility with file systems, parsers and other
software that rely on US-ASCII values but are transparent to other values. This
memo obsoletes and replaces RFC 2279.</t>
</abstract>
</front>
<seriesInfo name="STD" value="63"/>
<seriesInfo name="RFC" value="3629"/>
<seriesInfo name="DOI" value="10.17487/RFC3629"/>
</reference>
<reference anchor="RFC3404" target="https://www.rfc-editor.org/info/rfc3
404" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3404.xml">
<front> <front>
<title>Dynamic Delegation Discovery System (DDDS) Part Four: The Uni form Resource Identifiers (URI)</title> <title>Dynamic Delegation Discovery System (DDDS) Part Four: The Uni form Resource Identifiers (URI)</title>
<author fullname="M. Mealling" initials="M." surname="Mealling"/> <author fullname="M. Mealling" initials="M." surname="Mealling"/>
<date month="October" year="2002"/> <date month="October" year="2002"/>
<abstract> <abstract>
<t>This document describes a specification for taking Uniform Reso urce Identifiers (URI) and locating an authoritative server for information abou t that URI. The method used to locate that authoritative server is the Dynamic D elegation Discovery System. This document is part of a series that is specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and unde rstand any document in this series without reading the others. [STANDARDS-TRACK] </t> <t indent="0">This document describes a specification for taking U niform Resource Identifiers (URI) and locating an authoritative server for infor mation about that URI. The method used to locate that authoritative server is th e Dynamic Delegation Discovery System. This document is part of a series that is specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehe nsive DDDS" (RFC 3401). It is very important to note that it is impossible to re ad and understand any document in this series without reading the others. [STAND ARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="3404"/> <seriesInfo name="RFC" value="3404"/>
<seriesInfo name="DOI" value="10.17487/RFC3404"/> <seriesInfo name="DOI" value="10.17487/RFC3404"/>
</reference> </reference>
<reference anchor="RFC3405" target="https://www.rfc-editor.org/info/rfc3 405" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3405.xml"> <reference anchor="RFC3405" target="https://www.rfc-editor.org/info/rfc3 405" quoteTitle="true" derivedAnchor="RFC3405">
<front> <front>
<title>Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARP A Assignment Procedures</title> <title>Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARP A Assignment Procedures</title>
<author fullname="M. Mealling" initials="M." surname="Mealling"/> <author fullname="M. Mealling" initials="M." surname="Mealling"/>
<date month="October" year="2002"/> <date month="October" year="2002"/>
<abstract> <abstract>
<t>This document is fifth in a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS " (RFC 3401). It is very important to note that it is impossible to read and und erstand any document in this series without reading the others. This document sp ecifies an Internet Best Current Practices for the Internet Community, and reque sts discussion and suggestions for improvements.</t> <t indent="0">This document is fifth in a series that is completel y specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Compreh ensive DDDS" (RFC 3401). It is very important to note that it is impossible to r ead and understand any document in this series without reading the others. This document specifies an Internet Best Current Practices for the Internet Community , and requests discussion and suggestions for improvements.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="65"/> <seriesInfo name="BCP" value="65"/>
<seriesInfo name="RFC" value="3405"/> <seriesInfo name="RFC" value="3405"/>
<seriesInfo name="DOI" value="10.17487/RFC3405"/> <seriesInfo name="DOI" value="10.17487/RFC3405"/>
</reference> </reference>
<reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3 <reference anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3
986" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"> 629" quoteTitle="true" derivedAnchor="RFC3629">
<front>
<title>UTF-8, a transformation format of ISO 10646</title>
<author fullname="F. Yergeau" initials="F." surname="Yergeau"/>
<date month="November" year="2003"/>
<abstract>
<t indent="0">ISO/IEC 10646-1 defines a large character set called
the Universal Character Set (UCS) which encompasses most of the world's writing
systems. The originally proposed encodings of the UCS, however, were not compat
ible with many current applications and protocols, and this has led to the devel
opment of UTF-8, the object of this memo. UTF-8 has the characteristic of preser
ving the full US-ASCII range, providing compatibility with file systems, parsers
and other software that rely on US-ASCII values but are transparent to other va
lues. This memo obsoletes and replaces RFC 2279.</t>
</abstract>
</front>
<seriesInfo name="STD" value="63"/>
<seriesInfo name="RFC" value="3629"/>
<seriesInfo name="DOI" value="10.17487/RFC3629"/>
</reference>
<reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3
986" quoteTitle="true" derivedAnchor="RFC3986">
<front> <front>
<title>Uniform Resource Identifier (URI): Generic Syntax</title> <title>Uniform Resource Identifier (URI): Generic Syntax</title>
<author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee "/> <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee "/>
<author fullname="R. Fielding" initials="R." surname="Fielding"/> <author fullname="R. Fielding" initials="R." surname="Fielding"/>
<author fullname="L. Masinter" initials="L." surname="Masinter"/> <author fullname="L. Masinter" initials="L." surname="Masinter"/>
<date month="January" year="2005"/> <date month="January" year="2005"/>
<abstract> <abstract>
<t>A Uniform Resource Identifier (URI) is a compact sequence of ch aracters that identifies an abstract or physical resource. This specification de fines the generic URI syntax and a process for resolving URI references that mig ht be in relative form, along with guidelines and security considerations for th e use of URIs on the Internet. The URI syntax defines a grammar that is a supers et of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every pos sible identifier. This specification does not define a generative grammar for UR Is; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t> <t indent="0">A Uniform Resource Identifier (URI) is a compact seq uence of characters that identifies an abstract or physical resource. This speci fication defines the generic URI syntax and a process for resolving URI referenc es that might be in relative form, along with guidelines and security considerat ions for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements o f every possible identifier. This specification does not define a generative gra mmar for URIs; that task is performed by the individual specifications of each U RI scheme. [STANDARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="STD" value="66"/> <seriesInfo name="STD" value="66"/>
<seriesInfo name="RFC" value="3986"/> <seriesInfo name="RFC" value="3986"/>
<seriesInfo name="DOI" value="10.17487/RFC3986"/> <seriesInfo name="DOI" value="10.17487/RFC3986"/>
</reference> </reference>
<reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5 234" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"> <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5 234" quoteTitle="true" derivedAnchor="RFC5234">
<front> <front>
<title>Augmented BNF for Syntax Specifications: ABNF</title> <title>Augmented BNF for Syntax Specifications: ABNF</title>
<author fullname="D. Crocker" initials="D." role="editor" surname="C rocker"/> <author fullname="D. Crocker" initials="D." role="editor" surname="C rocker"/>
<author fullname="P. Overell" initials="P." surname="Overell"/> <author fullname="P. Overell" initials="P." surname="Overell"/>
<date month="January" year="2008"/> <date month="January" year="2008"/>
<abstract> <abstract>
<t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Au gmented BNF (ABNF), has been popular among many Internet specifications. The cur rent specification documents ABNF. It balances compactness and simplicity with r easonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ra nges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specification s. [STANDARDS-TRACK]</t> <t indent="0">Internet technical specifications often need to defi ne a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF) , called Augmented BNF (ABNF), has been popular among many Internet specificatio ns. The current specification documents ABNF. It balances compactness and simpli city with reasonable representational power. The differences between standard BN F and ABNF involve naming rules, repetition, alternatives, order-independence, a nd value ranges. This specification also supplies additional rule definitions an d encoding for a core lexical analyzer of the type common to several Internet sp ecifications. [STANDARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="STD" value="68"/> <seriesInfo name="STD" value="68"/>
<seriesInfo name="RFC" value="5234"/> <seriesInfo name="RFC" value="5234"/>
<seriesInfo name="DOI" value="10.17487/RFC5234"/> <seriesInfo name="DOI" value="10.17487/RFC5234"/>
</reference> </reference>
<reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5 646" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"> <reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5 646" quoteTitle="true" derivedAnchor="RFC5646">
<front> <front>
<title>Tags for Identifying Languages</title> <title>Tags for Identifying Languages</title>
<author fullname="A. Phillips" initials="A." role="editor" surname=" Phillips"/> <author fullname="A. Phillips" initials="A." role="editor" surname=" Phillips"/>
<author fullname="M. Davis" initials="M." role="editor" surname="Dav is"/> <author fullname="M. Davis" initials="M." role="editor" surname="Dav is"/>
<date month="September" year="2009"/> <date month="September" year="2009"/>
<abstract> <abstract>
<t>This document describes the structure, content, construction, a nd semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register v alues for use in language tags and the creation of user-defined extensions for p rivate interchange. This document specifies an Internet Best Current Practices f or the Internet Community, and requests discussion and suggestions for improveme nts.</t> <t indent="0">This document describes the structure, content, cons truction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined exten sions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions fo r improvements.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="47"/> <seriesInfo name="BCP" value="47"/>
<seriesInfo name="RFC" value="5646"/> <seriesInfo name="RFC" value="5646"/>
<seriesInfo name="DOI" value="10.17487/RFC5646"/> <seriesInfo name="DOI" value="10.17487/RFC5646"/>
</reference> </reference>
<reference anchor="RFC5891" target="https://www.rfc-editor.org/info/rfc5 891" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml"> <reference anchor="RFC5891" target="https://www.rfc-editor.org/info/rfc5 891" quoteTitle="true" derivedAnchor="RFC5891">
<front> <front>
<title>Internationalized Domain Names in Applications (IDNA): Protoc ol</title> <title>Internationalized Domain Names in Applications (IDNA): Protoc ol</title>
<author fullname="J. Klensin" initials="J." surname="Klensin"/> <author fullname="J. Klensin" initials="J." surname="Klensin"/>
<date month="August" year="2010"/> <date month="August" year="2010"/>
<abstract> <abstract>
<t>This document is the revised protocol definition for Internatio nalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing do main names, not free text. [STANDARDS-TRACK]</t> <t indent="0">This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relations hip to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationali zed Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for pr ocessing domain names, not free text. [STANDARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="5891"/> <seriesInfo name="RFC" value="5891"/>
<seriesInfo name="DOI" value="10.17487/RFC5891"/> <seriesInfo name="DOI" value="10.17487/RFC5891"/>
</reference> </reference>
<reference anchor="RFC5893" target="https://www.rfc-editor.org/info/rfc5 893" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5893.xml"> <reference anchor="RFC5893" target="https://www.rfc-editor.org/info/rfc5 893" quoteTitle="true" derivedAnchor="RFC5893">
<front> <front>
<title>Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)</title> <title>Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)</title>
<author fullname="H. Alvestrand" initials="H." role="editor" surname ="Alvestrand"/> <author fullname="H. Alvestrand" initials="H." role="editor" surname ="Alvestrand"/>
<author fullname="C. Karp" initials="C." surname="Karp"/> <author fullname="C. Karp" initials="C." surname="Karp"/>
<date month="August" year="2010"/> <date month="August" year="2010"/>
<abstract> <abstract>
<t>The use of right-to-left scripts in Internationalized Domain Na mes (IDNs) has presented several challenges. This memo provides a new Bidi rule for Internationalized Domain Names for Applications (IDNA) labels, based on the encountered problems with some scripts and some shortcomings in the 2003 IDNA Bi di criterion. [STANDARDS-TRACK]</t> <t indent="0">The use of right-to-left scripts in Internationalize d Domain Names (IDNs) has presented several challenges. This memo provides a new Bidi rule for Internationalized Domain Names for Applications (IDNA) labels, ba sed on the encountered problems with some scripts and some shortcomings in the 2 003 IDNA Bidi criterion. [STANDARDS-TRACK]</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="5893"/> <seriesInfo name="RFC" value="5893"/>
<seriesInfo name="DOI" value="10.17487/RFC5893"/> <seriesInfo name="DOI" value="10.17487/RFC5893"/>
</reference> </reference>
<reference anchor="RFC5894" target="https://www.rfc-editor.org/info/rfc5 894" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5894.xml"> <reference anchor="RFC5894" target="https://www.rfc-editor.org/info/rfc5 894" quoteTitle="true" derivedAnchor="RFC5894">
<front> <front>
<title>Internationalized Domain Names for Applications (IDNA): Backg round, Explanation, and Rationale</title> <title>Internationalized Domain Names for Applications (IDNA): Backg round, Explanation, and Rationale</title>
<author fullname="J. Klensin" initials="J." surname="Klensin"/> <author fullname="J. Klensin" initials="J." surname="Klensin"/>
<date month="August" year="2010"/> <date month="August" year="2010"/>
<abstract> <abstract>
<t>Several years have passed since the original protocol for Inter nationalized Domain Names (IDNs) was completed and deployed. During that time, a number of issues have arisen, including the need to update the system to deal w ith newer versions of Unicode. Some of these issues require tuning of the existi ng protocols and the tables on which they depend. This document provides an over view of a revised system and provides explanatory material for its components. T his document is not an Internet Standards Track specification; it is published f or informational purposes.</t> <t indent="0">Several years have passed since the original protoco l for Internationalized Domain Names (IDNs) was completed and deployed. During t hat time, a number of issues have arisen, including the need to update the syste m to deal with newer versions of Unicode. Some of these issues require tuning of the existing protocols and the tables on which they depend. This document provi des an overview of a revised system and provides explanatory material for its co mponents. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="5894"/> <seriesInfo name="RFC" value="5894"/>
<seriesInfo name="DOI" value="10.17487/RFC5894"/> <seriesInfo name="DOI" value="10.17487/RFC5894"/>
</reference> </reference>
<reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8 126" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"> <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8 126" quoteTitle="true" derivedAnchor="RFC8126">
<front> <front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs </title> <title>Guidelines for Writing an IANA Considerations Section in RFCs </title>
<author fullname="M. Cotton" initials="M." surname="Cotton"/> <author fullname="M. Cotton" initials="M." surname="Cotton"/>
<author fullname="B. Leiba" initials="B." surname="Leiba"/> <author fullname="B. Leiba" initials="B." surname="Leiba"/>
<author fullname="T. Narten" initials="T." surname="Narten"/> <author fullname="T. Narten" initials="T." surname="Narten"/>
<date month="June" year="2017"/> <date month="June" year="2017"/>
<abstract> <abstract>
<t>Many protocols make use of points of extensibility that use con <t indent="0">Many protocols make use of points of extensibility t
stants to identify various protocol parameters. To ensure that the values in the hat use constants to identify various protocol parameters. To ensure that the va
se fields do not have conflicting uses and to promote interoperability, their al lues in these fields do not have conflicting uses and to promote interoperabilit
locations are often coordinated by a central record keeper. For IETF protocols, y, their allocations are often coordinated by a central record keeper. For IETF
that role is filled by the Internet Assigned Numbers Authority (IANA).</t> protocols, that role is filled by the Internet Assigned Numbers Authority (IANA)
<t>To make assignments in a given registry prudently, guidance des .</t>
cribing the conditions under which new values should be assigned, as well as whe <t indent="0">To make assignments in a given registry prudently, g
n and how modifications to existing values can be made, is needed. This document uidance describing the conditions under which new values should be assigned, as
defines a framework for the documentation of these guidelines by specification well as when and how modifications to existing values can be made, is needed. Th
authors, in order to assure that the provided guidance for the IANA Consideratio is document defines a framework for the documentation of these guidelines by spe
ns is clear and addresses the various issues that are likely in the operation of cification authors, in order to assure that the provided guidance for the IANA C
a registry.</t> onsiderations is clear and addresses the various issues that are likely in the o
<t>This is the third edition of this document; it obsoletes RFC 52 peration of a registry.</t>
26.</t> <t indent="0">This is the third edition of this document; it obsol
etes RFC 5226.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="26"/> <seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/> <seriesInfo name="RFC" value="8126"/>
<seriesInfo name="DOI" value="10.17487/RFC8126"/> <seriesInfo name="DOI" value="10.17487/RFC8126"/>
</reference> </reference>
<reference anchor="RFC8141" target="https://www.rfc-editor.org/info/rfc8 141" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"> <reference anchor="RFC8141" target="https://www.rfc-editor.org/info/rfc8 141" quoteTitle="true" derivedAnchor="RFC8141">
<front> <front>
<title>Uniform Resource Names (URNs)</title> <title>Uniform Resource Names (URNs)</title>
<author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre "/> <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre "/>
<author fullname="J. Klensin" initials="J." surname="Klensin"/> <author fullname="J. Klensin" initials="J." surname="Klensin"/>
<date month="April" year="2017"/> <date month="April" year="2017"/>
<abstract> <abstract>
<t>A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace , with the intent that the URN will be a persistent, location-independent resour ce identifier. With regard to URN syntax, this document defines the canonical sy ntax for URNs (in a way that is consistent with URI syntax), specifies methods f or determining URN-equivalence, and discusses URI conformance. With regard to UR N namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and it describes procedures for regi stering namespace identifiers with the Internet Assigned Numbers Authority (IANA ). This document obsoletes both RFCs 2141 and 3406.</t> <t indent="0">A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular UR N namespace, with the intent that the URN will be a persistent, location-indepen dent resource identifier. With regard to URN syntax, this document defines the c anonical syntax for URNs (in a way that is consistent with URI syntax), specifie s methods for determining URN-equivalence, and discusses URI conformance. With r egard to URN namespaces, this document specifies a method for defining a URN nam espace and associating it with a namespace identifier, and it describes procedur es for registering namespace identifiers with the Internet Assigned Numbers Auth ority (IANA). This document obsoletes both RFCs 2141 and 3406.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="8141"/> <seriesInfo name="RFC" value="8141"/>
<seriesInfo name="DOI" value="10.17487/RFC8141"/> <seriesInfo name="DOI" value="10.17487/RFC8141"/>
</reference> </reference>
<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8 174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8 174" quoteTitle="true" derivedAnchor="RFC8174">
<front> <front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti tle> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti tle>
<author fullname="B. Leiba" initials="B." surname="Leiba"/> <author fullname="B. Leiba" initials="B." surname="Leiba"/>
<date month="May" year="2017"/> <date month="May" year="2017"/>
<abstract> <abstract>
<t>RFC 2119 specifies common key words that may be used in protoco l specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t> <t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clari fying that only UPPERCASE usage of the key words have the defined special meanin gs.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="14"/> <seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="8174"/> <seriesInfo name="RFC" value="8174"/>
<seriesInfo name="DOI" value="10.17487/RFC8174"/> <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference> </reference>
<reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8 288" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml"> <reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8 288" quoteTitle="true" derivedAnchor="RFC8288">
<front> <front>
<title>Web Linking</title> <title>Web Linking</title>
<author fullname="M. Nottingham" initials="M." surname="Nottingham"/ > <author fullname="M. Nottingham" initials="M." surname="Nottingham"/ >
<date month="October" year="2017"/> <date month="October" year="2017"/>
<abstract> <abstract>
<t>This specification defines a model for the relationships betwee <t indent="0">This specification defines a model for the relations
n resources on the Web ("links") and the type of those relationships ("link rela hips between resources on the Web ("links") and the type of those relationships
tion types").</t> ("link relation types").</t>
<t>It also defines the serialisation of such links in HTTP headers <t indent="0">It also defines the serialisation of such links in H
with the Link header field.</t> TTP headers with the Link header field.</t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="RFC" value="8288"/> <seriesInfo name="RFC" value="8288"/>
<seriesInfo name="DOI" value="10.17487/RFC8288"/> <seriesInfo name="DOI" value="10.17487/RFC8288"/>
</reference> </reference>
<reference anchor="ISO.8601.1988" xml:base="https://bib.ietf.org/public/ <reference anchor="W3C.HTML" target="https://www.w3.org/TR/html/" quoteT
rfc/bibxml2/reference.ISO.8601.1988.xml"> itle="true" derivedAnchor="W3C.HTML">
<front>
<title>Data elements and interchange formats - Information interchan
ge - Representation of dates and times</title>
<author>
<organization>International Organization for Standardization</orga
nization>
</author>
<date month="June" year="1988"/>
</front>
<seriesInfo name="ISO" value="Standard 8601"/>
</reference>
<reference anchor="W3C.HTML" target="https://www.w3.org/TR/html/" xml:ba
se="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.HTML.xml">
<front> <front>
<title>HTML</title> <title>HTML</title>
<author/> <author/>
</front> </front>
<seriesInfo name="W3C REC" value="html"/> <seriesInfo name="W3C REC" value="HTML"/>
<seriesInfo name="W3C" value="html"/> <seriesInfo name="W3C" value="HTML"/>
</reference> </reference>
</references> </references>
<references anchor="sec-informative-references"> <references anchor="sec-informative-references" pn="section-13.2">
<name>Informative References</name> <name slugifiedName="name-informative-references">Informative References
<reference anchor="FRAN"> </name>
<reference anchor="FRAN" quoteTitle="true" derivedAnchor="FRAN">
<front> <front>
<title>Technologies for European Integration. Standards-based Inter operability of Legal Information Systems</title> <title>Technologies for European Integration. Standards-based Inter operability of Legal Information Systems</title>
<author initials="E." surname="Francesconi" fullname="Enrico Frances coni"> <author initials="E." surname="Francesconi" fullname="Enrico Frances coni">
<organization>European Press Academic Publishing</organization> <organization showOnFrontPage="true">European Press Academic Publi shing</organization>
</author> </author>
<date year="2007"/> <date year="2007"/>
</front> </front>
<seriesInfo name="ISBN" value="978-88-8398-050-3"/> <seriesInfo name="ISBN" value="978-88-8398-050-3"/>
</reference> </reference>
<reference anchor="FRBR" target="https://www.ifla.org/files/assets/catal oguing/frbr/frbr_2008.pdf"> <reference anchor="FRBR" target="https://www.ifla.org/files/assets/catal oguing/frbr/frbr_2008.pdf" quoteTitle="true" derivedAnchor="FRBR">
<front> <front>
<title>Functional Requirements for Bibliographic Records</title> <title>Functional Requirements for Bibliographic Records</title>
<author> <author>
<organization/> <organization showOnFrontPage="true">International Federation of L ibrary Associations and Institutions</organization>
</author> </author>
<date>n.d.</date> <date month="February" year="2009"/>
</front> </front>
</reference> </reference>
<reference anchor="HCPIL" target="https://assets.hcch.net/docs/b093f152- a4b3-4530-949e-65c1bfc9cda1.pdf"> <reference anchor="HCPIL" target="https://assets.hcch.net/docs/b093f152- a4b3-4530-949e-65c1bfc9cda1.pdf" quoteTitle="true" derivedAnchor="HCPIL">
<front> <front>
<title>The Hague Conference on Private International Law "Access to Foreign Law in Civil and Commercial Matters. Conclusions and Recommendations"</t itle> <title>Access to Foreign Law in Civil and Commercial Matters</title>
<author> <author>
<organization>The European Commission</organization> <organization showOnFrontPage="true">The European Commission</orga nization>
</author> </author>
<date year="2012"/> <date month="February" year="2012"/>
</front> </front>
<refcontent>The Hague Conference on Private International Law</refcont ent>
</reference> </reference>
<reference anchor="ISBD"> <reference anchor="ISBD" quoteTitle="true" derivedAnchor="ISBD">
<front> <front>
<title>International Standard Bibliographic Description - Consolidat ed Edition.</title> <title>ISBD: International Standard Bibliographic Description – Cons olidated Edition</title>
<author> <author>
<organization>The Standing Committee of the IFLA Cataloguing Secti on Berlin/Munich\: De Gruyter Saur</organization> <organization showOnFrontPage="true">The Standing Committee of the IFLA Cataloguing Section Berlin/Munich: De Gruyter Saur</organization>
</author> </author>
<date year="2011"/> <date year="2011"/>
</front> </front>
<seriesInfo name="ISBN" value="978-3-11-026379-4"/> <seriesInfo name="ISBN" value="978-3-11-026379-4"/>
</reference> </reference>
<reference anchor="ISO3166-1"> <reference anchor="ISO.3166-1" quoteTitle="true" derivedAnchor="ISO.3166 -1">
<front> <front>
<title>Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes</title> <title>Codes for the representation of names of countries and their subdivisions - Part 1: Country codes, ISO 3166-1:2020, 2020.</title>
<author> <author>
<organization>International Organization for Standardization</orga nization> <organization showOnFrontPage="true">ISO</organization>
</author> </author>
<date/> <date year="2020"/>
</front> </front>
</reference> </reference>
<reference anchor="LVI"> <reference anchor="LVI" quoteTitle="true" derivedAnchor="LVI">
<front> <front>
<title>Law via the Internet. Free Access, Quality of Information, Ef fectiveness of Rights</title> <title>Law via the Internet. Free Access, Quality of Information, Ef fectiveness of Rights</title>
<author initials="G." surname="Peruginelli" fullname="Ginevra Perugi nelli" role="editor"> <author initials="G." surname="Peruginelli" fullname="Ginevra Perugi nelli" role="editor">
<organization>European Press Academic Publishing</organization> <organization showOnFrontPage="true">European Press Academic Publi shing</organization>
</author> </author>
<author initials="M." surname="Ragona" fullname="Mario Ragona" role= "editor"> <author initials="M." surname="Ragona" fullname="Mario Ragona" role= "editor">
<organization>European Press Academic Publishing</organization> <organization showOnFrontPage="true">European Press Academic Publi shing</organization>
</author> </author>
<date year="2008"/> <date month="April" year="2009"/>
</front> </front>
<seriesInfo name="ISBN" value="9788883980589"/> <seriesInfo name="ISBN" value="9788883980589"/>
</reference> </reference>
<reference anchor="SART"> <reference anchor="SART" quoteTitle="true" derivedAnchor="SART">
<front> <front>
<title>Legislative XML for the Semantic Web. Principles, Models, Sta ndards for Document Management, Law, Governance and Technology Series</title> <title>Legislative XML for the Semantic Web: Principles, Models, Sta ndards for Document Management</title>
<author initials="G." surname="Sartor" fullname="Giovanni Sartor"> <author initials="G." surname="Sartor" fullname="Giovanni Sartor">
<organization/> <organization showOnFrontPage="true"/>
</author> </author>
<author initials="M." surname="Palmirani" fullname="Monica Palmirani "> <author initials="M." surname="Palmirani" fullname="Monica Palmirani ">
<organization/> <organization showOnFrontPage="true"/>
</author> </author>
<author initials="E." surname="Francesconi" fullname="Enrico Frances coni"> <author initials="E." surname="Francesconi" fullname="Enrico Frances coni">
<organization/> <organization showOnFrontPage="true"/>
</author> </author>
<author initials="M." surname="Biasiotti" fullname="Maria Angela Bia sotti"> <author initials="M." surname="Biasiotti" fullname="Maria Angela Bia sotti">
<organization/> <organization showOnFrontPage="true"/>
</author> </author>
<date year="2011"/> <date year="2011"/>
</front> </front>
<seriesInfo name="ISBN" value="978-94-007-1887-6"/> <seriesInfo name="ISBN" value="978-94-007-1887-6"/>
</reference> </reference>
<reference anchor="SPIN"> <reference anchor="SPIN" quoteTitle="true" derivedAnchor="SPIN">
<front> <front>
<title>The Assignment of Uniform Names to Italian Legal Documents, U RN-NIR 1.4</title> <title>Identification of Legal Documents through URNs (Uniform Resou rce Names)</title>
<author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa" > <author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa" >
<organization/> <organization showOnFrontPage="true"/>
</author> </author>
<date year="2020" month="June"/> <date year="2001"/>
</front> </front>
<seriesInfo name="ITTIG" value="technical Report n. 8/2010."/> <seriesInfo name="Proceedings of the EuroWeb 2001, The Web in Public A dministration" value=""/>
</reference> </reference>
<reference anchor="W3C.rdf-schema" target="https://www.w3.org/TR/rdf-sch ema/" xml:base="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.rdf-schema .xml"> <reference anchor="W3C.RDF-SCHEMA" target="https://www.w3.org/TR/rdf-sch ema/" quoteTitle="true" derivedAnchor="W3C.RDF-SCHEMA">
<front> <front>
<title>RDF Schema 1.1</title> <title>RDF Schema 1.1</title>
<author/> <author fullname="Dan Brickley" role="editor"/>
<author fullname="R.V. Guha" role="editor"/>
<date year="2014" month="February"/>
</front> </front>
<seriesInfo name="W3C REC" value="rdf-schema"/> <seriesInfo name="W3C REC" value="rdf-schema"/>
<seriesInfo name="W3C" value="rdf-schema"/> <seriesInfo name="W3C" value="rdf-schema"/>
</reference> </reference>
</references> </references>
</references> </references>
<?line 2288?> <section numbered="false" anchor="acknowledgements" removeInRFC="false" toc=
"include" pn="section-appendix.a">
<name slugifiedName="name-acknowledgements">Acknowledgements</name>
<t indent="0" pn="section-appendix.a-1">The authors wish to thank all thos
e who provided
suggestions and comments.</t>
<t indent="0" pn="section-appendix.a-2">The authors are grateful to the Le
gislative XML community <xref target="SART" format="default" sectionFormat="of"
derivedContent="SART"/> for the interesting discussions on this topic and to the
Working Group "Identification of the legal resources through URNs" of the
Italian NormeInRete project for the guidance provided <xref target="SPIN"
format="default" sectionFormat="of" derivedContent="SPIN"/>.</t>
<t indent="0" pn="section-appendix.a-3">The authors owe a debt of gratitud
e to <contact fullname="Tom Bruce"/>, former director of the Legal Informa
tion Institute of the
Cornell University Law School, for his contribution in revising this
document and sharing fruitful discussions that greatly improved the
document. The authors wish to specially thank <contact fullname="Marc van
Opijnen"/> (Dutch Ministry of Security and Justice)
for his valuable comments on LEX specifications, which contributed to
improving this document, as well as for the common work aimed to
harmonize the ECLI and LEX specifications. Thanks also to <contact fullnam
e="Joao Alberto de Oliveira Lima"/>, Legislative System Analyst
of the Brazilian Federal Senate, and to <contact fullname="Attila To
rcsvari"/>, Information Management Consultant, for their detailed
comments on the first draft versions of this document, which provided
significant improvements to the final document. Thanks also to <contact fu
llname="Robert Richards"/> of the Legal Information Institute (Cornell
University Law School), promoter and maintainer of the Legal Informatics
Research social network, as well as to the members of this network, for
their valuable comments on this document.</t>
<t indent="0" pn="section-appendix.a-4">Finally, many thanks go to <contac
t fullname="Loriana Serrotti"/>, who
significantly contributed to the first draft versions of this document.</t
>
</section>
<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
="include" pn="section-appendix.b">
<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
<author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa">
<address>
<postal>
<street>Via Zanardelli, 15</street>
<city>Firenze</city>
<code>50136</code>
<country>Italy</country>
</postal>
<phone>+39 339 5614056</phone>
<email>pierluigi.spinosa@gmail.com</email>
</address>
</author>
<author initials="E." surname="Francesconi" fullname="Enrico Franceseconi"
>
<organization showOnFrontPage="true">National Research Council of Italy
(CNR)</organization>
<address>
<postal>
<street>Via de' Barucci, 20</street>
<city>Firenze</city>
<code>50127</code>
<country>Italy</country>
</postal>
<phone>+39 055 43995</phone>
<email>enrico.francesconi@cnr.it</email>
</address>
</author>
<author initials="C." surname="Lupo" fullname="Caterina Lupo">
<address>
<postal>
<street>Via San Fabiano, 25</street>
<city>Roma</city>
<code>117</code>
<country>Italy</country>
</postal>
<phone>+39 3382632348</phone>
<email>caterina.lupo@gmail.com</email>
</address>
</author>
</section>
</back> </back>
<!-- ##markdown-source:
H4sIAAAAAAAAA8y9aXMb2ZUm/P3+ihxUVxgoAxBXLeSow5QoVdEhqTSkZPeM
Xe9EEkiCaQFIODNBiqVW//Y5z1nukgBVKtvV8VbYFAnkcpdzz36eMxqNnGvL
dl4cZSfZ+2V5VdWL7LxoqnU9KbI3+aLI+u/P3wz412aV04d0SXbB3zdZdZW9
ym+z/qsX/zFw02qypKuOsmmdX7WjZlUuqyYfrevlaF58HO0duPzysi5ujjJ6
Yka3fPGhrlzVR1lbr5t2b2fnyc6em+TtUVYuryrXrC8XZdOU1bK9WxX4cFqs
CvqxbJ3L1+11VR+5LBvR/+m/ctkcZW/H2YUMSD6Ukb4ti/rVupyV6ZdNWxcF
vexPZZ79n3yZ19NiPi+H2e6hfD8p27uj7GVZF8ufC/2oWi/bmj49a/P5nX02
pXcc7uzuP5QPVtfVkj75/f6TbJ/+f/hw92DnUL8rFnk5P8pWNKI5RjTW9fvD
DF+MJ9WiM6MX4+xlnS9pxSbVsoxn9WJZl5PKvi3C11U9O6JFb2nh8jm2ucjr
yXX2nMY+KedYeB591n/+5nywuRTT4nfZs7xeTya0Fns7nUnuPfpVixOtxc7h
YXaw/+TJYbISBc9ifBXm+IfJsh6XbWcdno+zV+tVFS/A87wt6nKZR1/E87jI
l9nL/LLMlxXN4zCex87O7sNkk8+rRf5Vk9jff7z3cH9v/+BxMouJDmU8p6FE
e+mWdNJoJ24KUOr5y+d7OweH9uvu7hP9df/hnv/1YOcg/GrX7j95/FB/PaSX
268PD/ynj5/shl/3w6927ePdvYf+14Nd/+sjf8He48f49ezix/Hjhzu7490n
8sGf95+Pf3j3+tWRcziW0Xxenp+8OeJ1UOby77Io2bticr2s5tWspIOOQ/9i
XVergjbkbNkWs5ppc5xlF22+nNK5a0aXeVNM9W5cg8tr2rw5bQ+zimJGtHxm
76+W2cVd0xaLhu8JzAD/KdmEE7RxgO45Q8kFfIr8uN/WRdNkJ5N8WizKSfZ2
fTkvm+tyOePrp7T9R3RWduRwNEQLRYPFsiGdXTx7c5Q9efR49Jj+R7s52jnc
Ge3zGj47T9bwJZ1Sf3T/vqYDtiCGJ8v4rKTXVrR+q2saxDmdeVo7uTmvZyD8
67ZdNUcPHtze3o7Lq3k+pmk8uCrnRfMgb5qibR4Qqea0M2sa+4Or+rLmH/+X
xv54vJpe0cN+eP727NXWbc3eXRfZD/lsXRAzWV4VdPaJqVdYnfKGlkB2bmmc
BzKjdzKhhW3sAS2tdVUX5WzJ35bL7Hl5QzyJyIAeuVgU9aSkO1/nLT2oGdtt
9LbJfA1J0PClmDldTLSDVzW9LUTA24fx+i3E80WcbF0xWZ7x9WRyPV4W7QOS
c82Dy50n+1e7h3uj/OByf3RwuL8zenLwpBg9PJzsXl5Nnkym+a4uW6CC3T0+
Rs9Oty5iukZ2Ajpbe0rEWJcrJnQjZ1qEppqXeMs0ezEt9Qzhv/vm7zeOV4Lf
RdsuK0ErXOBktfTN2ctXJ2CnRhjZRcE06G9/RuKqXD54vV6Wk+u/HtH4su/r
9R3NhNjsuk6nv/uLh2B/tLs72iFG+ujJ6EB4zv7uw4ej3a0r9px4ttA/xloX
KzqLdCSEDdAMcJRZnxDeDZ4DIqGLy1ofQarElAhNKGg0yt7mdZvtHrFMJG7P
YmEbK+msYrp3P9azfFn+LONg1UY3Uz+LVmX3yaNHpFg8eQIG8epPZ1vniRNx
Q4KLd4TfVLSQ/rRPcoqG2f9a58YRI1441Ae8uLrCvt0USzAruua8nF23X8Ei
vx9nb4t6PSuX0IA6PPJ7+vSmzrdeUVeYQEHEWNX+w1/DOTeG8nqcneczWt/O
KF7ndVl1v/qnX+8Z9+Nfoln6j9j2DklU+ubi5Pzd9i0sZmUzZwGZ/cfrV55o
L0hPWLb0/j8Xl2OwS9LEVsSUbedeE/3NaX+9QOQ7T6vJGsyfJr/MZywHhqAS
u+v76gbkCCYMgvdS947eh4l81cZf0FGIVs/2vLrJl8sy/XZzq97m80VJwrNL
M69Jkk7yja83JPNWyfsLonlzFM/KnE52226Mgmgmz06Ws2Ke80X+ms2NjrjT
k4MRSfLR7uPHj0YPN1nbxduze7Qe2ugTEjCzJW8anT8ztdgCgvCDUkkKqaoz
tr+eDMhiGr05O892xwdb9k4tnMSG+aKFs4Wc3707+57sLVAKbRBUjFVFrJAE
yeMHNL+dcTTfP66XBSwAtgGgBdbTq1EzuSZaxvPciBhpfkkqdz4hg+zdddlk
U6PYKQuwS7DirzM43RnsuvKKJsK0X8qfd3RSh5gk/5vz6uJXB4Jf4FhAXJGu
2JSkDtKLa31JA+UCR2/OSz0lBb+EuMQwXbMqJvSqibBuGvdK2AIJVtqkfD6v
brN8Wq1MwuQZ9A36ncjwBuMi5n55ly3W8xbHOPvbui6backyk/f5Kp9AdYVO
VJBmi2fUhSlMGHouahFd+ksDloXdGDERUWQPZ8FWxuvxGFLplQDGmTtrcc+y
amkqjfKYIQ9kWhXyxXVOPAs30hxJvDbrxmsHL969HDve7kU5nc4L50g81dV0
LUrC0+g/0EFBXLZeVTLtYPz35sXHHp7yhf/k9lW4He/nG0XK84NKXmKhBZoP
6SR/XxeuDPRT4uNbElSjaXFFEmuaiajEbUah9Ixr+iSvi6zxHgk3z2/HEPP0
Jb2FVqItPhLP7YVLMrqkR28gfXSKrbxztl9K+bcl3Ss7KXvIN5lcIGFNxiLN
jR6D9Xf5lEi7xCFioUFHid5SE1XM1nI9bd/bCqQNxTgdatbny9dEAiJmVnU1
UdGPr4OCQKuVkTE1bwY8Yx0+vb3hdRpnvVc2C1KglkVvKMuDpabnXlZT1jk+
LKvbeTGdFaZgkS7fgo/widIBZ+3dinmLzBujnlxX87xusn4xno0z0d1J/76D
7fC39XQmki1zfI5WNQ0N56Qubsridti5PllKuu5uMidJT4eP/mDlb5g5Oqqi
StMfJMDKyVyO1yKf5T/T9Ohj4h2kS9EvRTsZDzDR4uNqXk6Ipd/xeZhAuBbT
sZBkTF1MGJOCtmtKG6IL1fKntI9yKDI5mrQVyzmG7fRktSoZhDyUZOjmYn7F
a4o341nVckQKN63zTV7O1Q4e4hu3ur5reHnn1cQ21zOUbEGKxDjrjlieD67B
h4Y2nrgXhhAzLhuWv3HqR0hn4gXxPTpVfsyYtTOeIoOcwxbkUS9yGixpjUVN
D5yz5srsJWd/IPyCYXS6wHTG+Qu6NbsssnVDr88hPW7pA2aTqvYHRkr0hBO0
ICLMZqTz1sS477AadyBBZbpCKUT2RBOz7AZaJHG29DyPiZ+BodqiF8ubsq6W
/jhHPHqKo1permGDySOn5RWPp3W3xaUXJDVNWafUOBUoWVMuiMR4ZWfz6pL2
sISaT2SxLPwWpOyEji3JGVJkGwc5tG6JpeDdGNGc/iIJoUsq9EfDw0MigQji
cEYro1hmhD0QgwmcYcXHhU5yPb9ztAlX63l2e10wPyMziRbpEtu7ohOHwVfg
VURUFZntGBavFr+sooc268k1WMwP7969pSG+Ilb2mjYLB2sYhj0tWiKfxh4e
dt5vNMTkpC4gTfEocRZ15/hLU3SfPqkj7fNnorln+eTDrCbzb+pS8bMhbFn+
i5CJDxWUlM5euasKO42xL9eLS7qI7iXuTqwbzN1LeLp/Pt3ca7fwaj4N8KIE
DyTTZFeEsGqOovMLw2yvaQKza/7e+3ufF6ApDM/F7rLIONBRsCk0yU4iAQRm
gq9eyyfg+e6P64YoQjj+8zfnWR8XfIV7eQBptCDJNWXe94ZGUpwtz4uWxdTf
iODHdCEdb1qucoE9b0FRrFZAp2tiU8ilB1bVS9HPMDDbF92ydYMnwADDl0Rl
TjRe2sKGlvZHGlCdeTu+s0NiOvqxgMknVhnd7OL3BzGnY/z0CY5RojK4LubE
GCtZ28ZdFu1tQYdpFm2iH0ZtK0l6PlkWxGIaZu2OaO8GtN6ycGNGanqNvxlz
TYd5L22xMgCpj39ZnS+23dFZ07H7cd029BnmK0s0BEMjxl8nKyiMfjqF3Y21
00toz0lALHAM/epcQEKIokCL2hQpRyJuJAcde8yyQWyPMdRPEgnT/O53TVZG
NA42VLR3sSokJLOqSH5CaA75mpwdjg4hkwpOgTI4pcPs6KyR4UKfLAo+yg20
+SZeOxACHVJiTExunadgELdVPZ+ObrFqsrggR/9aP0SHuU5yodo8I7Z0aw+k
VcSxIOVkcp0v2diRJ0XzdpFa1gaSYBWNrOdm5D+a04LP6QRA4NpbiJTLWkJz
JJ7qClrN39XNFBSLMrji+f0uXvdcxZooi8tCFG4Zf+zHF4G5eX8jrnx6VV2R
DuOHewn2nIsJc2ImWKzXO6EIkRkkJMxo7Mh3ZS2R644XQswohy0Q7Zo0jBou
dzpqxdYZMOnppkB4rBpT9xsl5eCClHMwJ+og3Zl0Sz0P4pUsWRFUa40tTagH
10QHUClJsOOrDvV7FiZGYbTQ28QTzbyzCDTKoKu8eJ+9Frq+YLoehrfRfJcR
L2EagG5HIwV50DvIaLmBV2YKdROUUspbPOu4JvWrhi71gc32a1gf4HthGcql
C0u2jBQ6sM9Xfzr7/HkAzSd29t4U3iIV0aVM9cerK8gn/apzePs/vh0MRS3B
tyRpmB+wZIIT8B4aTQ6Rf6QxZjbBo/On9DvOLpTZsX1QL5UIeOp1XmLel3cd
ShQycnqHqVBXcPqqSk/rvnHkh2aAwStLrB1b+mxNtLa2dfh1YZpPnzjq8/mz
Y2uGbiDaIXkh1MHu8lI8WD2h1mWxbrF5i6K9rqbifS+9S94xleuwFxwbZVtL
7E5wHbvPG+GkAZTrxUifO3RKarV9ImI+Hvj8zjReKEy9Mcz23OSNmxJTE50a
q/H8xRuid1JLSCUPwgoMYEGvYddSG/aZucOQtM5bPgFsq4HhlEEftPOhGjx4
c2FeBhxJPXtOzl488zqNXfHV8nSmOzi6IjcT1hyruVAzic88PXTjwDfxa/2R
Z09B0OmDSKHtqLINN4V5JsbsJqPbXT4hPYRW+qqYe9fGZUUUqtwYb1HyH8JQ
YEEGqYs9hYDkR/NVMjSh3AlH/ZKbMYKaHRmVbb44uUSqFtPoPOgroPXH3oAg
m2ExwC/5QUNG6kq5LlfgRKKE8apm6rbkYcKyJx6cT0CwP4uVnGfXJanYUxqE
xMuu6FwsfPiJ7vLunC0ibehur0tS6dbNmgl2jiFtlSpbmNdQ3XGLBe12exez
H+UsSHcwqeK8OKCDSKNfgqdDpWAVY4gR3rFZSovbFLStlZp9cMDw2Sb1lF5G
RxEGdX6LHYR1Lx6Mq6wvR4r+IPMP7JeEwiAjQcIETiYxE5VT/mOWdiRyWUc2
VhmrIKR3VHXLcQwiV38HDawkZa22JAJm4PJqO4jP/eJgA8iWcH5JlLjVUI6U
shAaIiO3zM1X/yT745rmxrEg5RoIL9ld8ahmhT3dP0vHahOEiFZhMBd9NDKP
togpSEh2481ZrWfNMl6UjDWj0aWckHAQ/KiMCNNDkGhjbeO5VtnoiaFpwMfG
PG3bWSMxjYSgCVxrJOh/xjfE7Ug/mrQkbsbeVcpPwfv+XNUQ+iwy2F/HjkV3
mrc5yR9WePF1vxiR3BnYcnx5dXCs8GbX5s0HkZiYfNOup6rsV6ahGq2IKsu8
NFo594WVI5LMeeRE85E+UUuARP5yyezI+ggDGm6dx3ssHnEyJkckuOGYFWoS
FqLbrSU8MgyzFhryNN8xbumIeJbTf/H81VkU7XxOX2BhsxBNGfAh15dkp9Cc
lu45HXF1ozQFz44Eck4iKVc58+UNKZc3ZSt0mqqRmJ43nNOAxjaFP3n0q8DK
42BQ/8WrswGkBmdq6KDjeCqJjRI+j64XwEXL2Bk/ViQddyRHdAXgn4r06T5L
THZJ1cZd4B0vPrY4cj1cjhBFD75kFxzERGqX3j1JihU7bJqK7UevUGezdTmV
OG6rTL8ujJN6VQOjbtbQdjHf7IqUGTPLIBPhU4C/FM8D9y3YXGOx0HRDaohx
JcEm8zZCizcjAWeEDvnQYV4QXiG4LUGMkQYxsi1BjNjVV7ZOnXuFZSjQ49ho
U5UiJwWDzqfcnrhfoVK4MKTgX836K3FgYQAr0WwH7ES0RRUltLoleuVMMVbc
Ok6OfhTmqFUhZM2F3cFwddLBKZpEs80axC/TBw3gsYvdhiJbmztSFD5m9Xqu
Ga8pUUUuT8f0hW2KyHxDHZSNXhW8btGy1HGmWLnccuRi/w/eUnyE1V4EGUGj
I52CaWOZjLGCdZ+bKxzXvyLDju74EYYiGDvpa5bQMO4Ggps1SezCIm6FjZTn
Vtj68JNzna6Lp3ttpjvZgfQEJdum2FCj2RmNTavLWblERMrE/ja9uOPact/r
+Xzu1T84Pb29KbmGvxC7TEKYTUoLxi78sqhvdEMXdJGPZCvLJJXUWwt5CIrG
i8aEx4GotZAyto4WTl3oPnK+YT50QplNN5DUaPCwhXddWduRcyONZuBMSyx2
JI4nMjxgmI4QyYMDkxRG+iP47emPbV578XrSd2RUrWmYZgIKY6a9F/cUi/oQ
Z+8c7EDvEmYlAQcrrWzYAUAHGi4N0Q0m1XxeTMKhtU85NcyFcBPe76c10bCM
rO+s5PDYEqxPLFUiVjI7ihscHJOtrl82DefXSWIHx/QsVEVPa8BtJSAJpsmJ
CazZiPdF9s95i6Zg17Y5Z5ysPW2C94KxwjxpNR6OOJoyu2g/+ldEiTZyuNBo
4PxUmoR85dj5VNnTwOledXZGgpPLKHo0tBwF1WJJXBW5p0en5N8kWRaJsCM6
r6L8Ol3nxRq265R5dQtb44q17pGRSsII1bhLozkqHBrnRS7IGBbtpjgxHx+/
WlafzafFej7D75yEohKpK0nH2TnEJc5BCy8hXUEvgphckBrNyuTKh/XZasPz
ldtfzRGSRWIL8QZIcsS+1VUPM7ukjWPHWM0M+36lQCKP7GLgGEIUdAbdNTwD
SUKhVWpT/y3OJrvnSJ+bS35lOCgwjZeu+LvYtfZ0hALr1kyqjlqAyeLUqoJF
x5EeB79JmehCTN9IXIQvjs5gVzlyUI48vSSbyyujD/riwrh7tCWefCMxVc6M
Ya59eecakoEtb0kSIq9F7oDum7FkgF2VNdEoPoFcJwrHTo3o5U0bh7U6I+/3
lN88SELy4O/ObiHVEgd0OcVNlqsj+at92q40Ds4rFT+LbS2Rjt6y6PDMy4Kt
cR//P+aH1Khx4BSTfk9Iwuu5QRYEelk3rPhHyqYL6iX4n2nPOFM6fLo5HqoS
CNe0THkpXSedQvb+S0LdjCiWrerqlZcu8xA2ZG6I6bEzcYGsI2Y9LHfF3o0d
vcZ2lRsWy1yOaczO6fMNli4eRA5zC88Qrq4cerksPnbSTNI5eNe8WXGS8axZ
PA2L4FyjYxIQsDw5vXKSryQ94yp41PHtmr6+LGfrat1wrQtSJ6LQnWTr6fL2
u1bARipTts0OgCSTTWeOcRfWKuuz8hNioXD7IlV7RTxTrfMQHh0iJSr45JnW
BuAInO5RIqFwlTctnmCJIizC1hA6g2NeocgXFLSBkYjHOLEjNkBGQjSsbSCr
Mt4CowPLGzFlxpgTMSow1oqz7uleSyPpNwPkWXY0ZXZmT6FltZ6N+MhoKtfO
1NcG3kzE27D9dBtnxpi8jpw1waNhq+BYgGhsX+9IxkwkcNXCEQiZL9EczeF5
o9PPfRLrL2rHwazmtaOpz8WO0DdHqUWS1gC1aRTrwOxLdZohpPxTkkU08YJP
QpKAl2ZY2ZNzz32zQowTvYvPgATT5TTRYWK6zT59sjqoz5+z1y/enWRtPgNZ
FR85JgGWa6k6EiLw6a5xMcfLmuZ+W9Uf9IEhpfbzZ3o5kSBZS8N4gHmrdKl0
Snok+IHoic6dtHQic5DKsojJxVMCcrQKeL2gQ9BSE9MCK/CpRC5JW2Nf0WrK
zinEA6QkBJG5JPMJWnLwCQ6cRaOQ4FQE7zjzG6K2G6FqnFbLFeLL48Mk5nmS
RsnK6Ea+G04PkxE9a73g7NU4xBE7+2Nfv1mGbVV3E/A0sc5cCyG45qcjAdVo
OThF03MTPUfQbN5L3qqve8Wunfvd+MX0VzseaToUPSPa0Zw16x/OX7yMiOMm
n6+NABzHX9k1hSNmB8w7r3xan3AgvkZfJ1quSOjbCkaDHCqQNmdMzjkOQU+X
DIXowZxMEM5wIc81p0GHdR6JZgUjIbtc1yT2GoQeOCViKmYQnwB+4RVXIGzJ
3LXwujLgYxmokjaIRmOEQt7sdi4592dlUdM5Kx8kZMlMIS1wfoeC2I3BJ0MP
eVchpZvorwGNg4bxAFr6eIbiUyIhNWrExeLnmRUwHMsrJHD/rRATDE+Y0Aoj
JEUDxUGDaUPPplWuEMJpSsmPDSShsZp8jh0DF5tM1uJiVg9O0RZmDxnVkvY1
nyZpmkQBcm+xEgOZlQld5JAjH4wc5/5Me4EnaESX5wubrpgiA/Q22rWVplNB
Ebu1uzRk2o9cUmC/w+w/wGqZyQ0y11zzUDV9IJFzUQpcl5skEsATf1vRqE99
ODc5kiKiRJiwrk9kIourx9AJe029O3xALryy9Cq/RXlE7p2+7AxetWJnXXGE
c1OLojs4fBMlft/vWj1bMmu8rKt8imgu8vWLoVJuqraxGX4H2TZTnVsPuvdQ
ayZT1mGQvyPVjOTfYlk0v1NDgd2YIebj17bnJ++4iq0n82wkygyKRpo6kbva
TyVRi8RakCHqc9PFNZCRkQzjDxYN/wK61sgkTajBIf9jZCxwDqJY2lwpwz7A
qDCPJ82pNbKgkjrEfBnZ+1maA81KU1LDg084Osz2wdK85KZJYeL0kMgiNJKU
yG/HXBQnDdfn0QrO1jn8A4WkmROxlZKiuUmTH4o7ZJORBdR7/f7iXW8o/2Zv
fuTfz1/8r/dn5y9O8fvFDyevXvlf5ApHf/z4/pV+j9/Cnc9/fP36xZtTuZk+
zTofvT753z1xyfV+fPvu7Mc3J696mw5NjvdzrMO7a4W2rBKIZcqz52/d7kHG
qbiofyddin9HHTr9jkxjkb5s58mfLTKPkXGcS2XHfO7InilbzihBCuM1XPxw
CcEHLw7l900Uo/kqDbXrt2bbnY+TPFHzHeDDgcVh9ZkosxGXDBI3G+dNNdx6
8uzNy6x/suZ8AfoYOcfrZvQmX9cog14MZPKo6KfJs7rrzJNFcwmlM0bgTKL3
TEPopFsrg8CyMXDJQ+JHFT6GRbe8ZGOX02T9K5ueXlkjPSF5v2g3SdWPL/6J
4nYX5oHeOt6NqgoeaHZNv7LNAoUv+LATDf+/8B/K1HrrenlE8z3qZW8uLvRz
J0ko9IEVr4RltAANxiaeNrX4tz8fz3iasocevYtNzxELGX+pvJUFQXx9KEpS
WuLYTZ9TSYNBO3TIYZiUK85Pjc3fTFhxh6UNNNEm19htNzmaU0NIHyynSC7J
pPaLWXHsTfaOAJcmpKVeV1OYNPuVxiNu0qRuCRfiG/Wamp+Pre6wWrYfiQVt
brxUZi3Vz7fVO6SzF9+N+BaOWRzqPOYuEA7X6tjBZd6uZ0F1FDXz2KR2fkUk
zpSzS7SJciPY+7nmRFErfhs6dpLL60t25tKe50FHhGVR3JjKFWQgq4ND87jT
oOaalMERHp+nKfZkf5WvYJdMSUDDTSIxAvUZJWtj5qxMXKgba0y6vLcoufwg
ofTkESnJj1Aan33X7x330s+RdjNIDt0G+cu9NBRLf9qSzcCXeH+JhFxkg7fq
MrLfnAGbVFnyisbBGZ+2s1D/28bAfLVGPDofqd1IusgqPgjG+F2UiRRnz2oq
GRN3X3L7pLyFo3Ji0mj+WlMU7tMnGheGMxJ2+/nzAJM7XXvnktGCVoh24A+U
h1u2lUmPxqpWeUGJSKHHL1GLyj7rjbnFvmQ+o40sqfc9k6TyIA0kq2BGtHW1
nNGyReqCZiaT9scpZJmCQmVnp2qZkAyawV+lAd+mgDIkG3xy8fzsLOTfNUeZ
8wx+MnlHussYQtNnLsh2REoZK3qyp9s3fJhx7Ow+5VFTdYRJLZQsO8vdl1HS
MNz7dy9Hj7NvR8iVha9sQHy9KGidlvS6vJmU5QiT0Q39s3BsnzinPuGIWNR0
j5gelxfHomAbo258RTBMFLzq7ErU6thztlGoJ2njSWaoTy4krcpXSMv55PDx
ZSg70Zlukq57ITZco3lTkRaWaIrXdyvsH9voYuawL0csgE03ZLxOOlMfw9jY
5vEGGwKrsoTUIAM7llWsegB6bOSlSOPnTay5yCfXcdwi2YXgeizrsIRx5qPa
4PlU8Fs6Qf7U5yNpXmDdFt2R+o2koPimEPmo6YdBMmUccnJccjvU9BroF63P
ATClg9Mn8eSBd3xxhssl0XWB8Miduyy8Vx3FKFiDJGCTRad+EgwkfgyiIS7E
AKwgyOIApfC1kMuSo6BG//YFV5v7mdjgoPuTpfcg6Dq2sTF/RJf0LusjiTdU
R3TayUapelmff5PcXlmlqD5rMJTbjpu8Gq/y9bz64gMu3v9+Z+fFfpW9xaWy
2IOs+4jjCQ2TTnbzxWc914twe7xXkPsvsRIts/zCTtyWio80c8NLfGOrZXuE
EVb0x2xWHO3t7OyPdp6M9naPDxSvrm9lhwj8+/uu6iMSau3RvCpx08Fod2+0
8/B4f0+Qf/ovIa6u03uK5ghpVFO87A530S2P6Mbj3b19uetihYPUuW1yfTwj
alk3R2AyUDKKek7MAk+g23dGu4fHTx7qE77nK7OLW6I2Wr5ly3XYWM9oHOuj
iQeCOtIqgRtMnh7G8z/mX3efjF68l8e+eB9hR2Wndkt4Jo0OajtpXmPUTbTY
TsYaOtoFnggt0N7j40ePRodPDnWk7y+yi+eZvyw7L2lVspsmO5vPy2VVNuHh
l8URIzKU8zEvur8JmcpYQxrx7uPD8d4jffapXmCH8Fkxn5WMf+VTOjnp0Stv
f9xQ2c7VSMw+fdPh8V+woZ07YY/fpgZolmQoBFI3M+rKwUsKVvt8NCs5t6bS
NtvVy6Ouh4WmF180DDXvWYhxbWXfx53ny6MtxySxV5I3uOxLT6x9GshRFkrN
Yq4fF65JoCJYYOzTyyXBj86P5tzWHXtcJmWV/+GNLLjpEZfsq1ohwGjCH1bH
6ZuL7GfEjThSahn2GlLQR0MS4ho44AtIMlV4WZ0lybQ0AzNSA2XIG1IC66Qp
aIEkoKeScqHPLqYm4wxYYcuCxFOBUxzvsWEy64eaO+cgYZTLwFuhmvRRXF3u
FW1LqwvJoSVMvzsztMQlXnpLj15RLFYwsd+aTmECqDAcsojrkgjoHWe9Z3X+
cznHb29JVpOEJxJ9qXLnoliyZ0Bj8ENOviF+2DtW/J6//sUP+68/uV6xxnPS
5GZ8cvo9sSkyFYfb0O/C4/Wh/iXdx6+XgA/EA+nJ2Bup+m74FW/Phln68caD
v/Rw5T1vqrawjbZoCarMPX2Azr77jpTX776DBXN28uYk9kzhWk5oS6l7Q2Vg
PmTaTV1ViJp+ZLcEYndFPSb5Oi5be3RZJE5eDZeTRY8o0tg43b2WhKRbysx5
Onq2TguwIo66vviIEF0fgCwTwDiyW0DTSjg7UUIt3h6dBayvvo/EODX/8Irb
4pLrVqeF5Af5uDpCiuHugfCIyHp1pt0XiCFa9Uc6pPtm6kyLyz3snC1yxfrc
NPi4LUFq6yLwGGwAGhZIDGyzGE17XJGmm3PwwEI9xM1oboI9Q0dz4xmZRpE4
ksBem+2uLHYqx9qpT/PpooYwVzBPUsKTUXA+uWMzWQfcKj/TwfZk6rSSqJzp
ASUjJDSUS/OK7wGsIlqxTG5rZL1EsiWELkiGWeKGDqI05GmzMD27Yj7IkoWX
pdGUz25MhFO1zCBrfIxShZ7t+MY4zOPHZgD7d9tqpbXXbNJryEqG2fnOtotD
kgYKsvU1x//kVACfybZ2KJRXqynlrINNG1yvEz7ossAJ/4zK/+xdndMq/Jj4
brtZrUX2jib+ChOnB5yKpSsIafJwcPmB5yBbvlc2jcXs3bYV/+Erq5JYmF/S
exfUZX5JrbSR4V/4NHUW6R6PhL4L6ZP0NA8tlsehBzHoh5uUDV6go1TqzjJk
BkgAc15+EJfemLj3OK9XuRWdsnJmjIw9VxnDCSzvFltXQvyCVqBk2cOT64rk
cXa5qYdpBhHStl6GUPWmZzHxZ3ryeWGQD75eUY6P7EWvKCZ+Qj284mR5J+na
cFiXtE0hXS0XnyXRrayqzLFjQns34DjV7pU7WORQ9EIsxXSIEGsubr+8dbc8
tpuyQr6jCiE+O5wa7uOjEhsPCf2/8DqO+LMbCekIU5ZEAirE4T5GFqo/MGG6
XnVJcpcu69E2jUmzncwrc/tA9saDiDK+0jTSc2EIvFz2vC5LEM2Ak0maymNy
wFXhtlEnJw9sIVrMgnYW61VrlgyXmRe8Y+ZprZ0Mo5mY23PLaDjgJpzMZrtl
xCFIzUnxmgzqNgiXE0CEUSt/5MydVjGXRUeJzZE+Y5oPIFZvr6uO5RFeC+Wr
ktswFZbPoA6JwH4p1ro9UhnX2r05Ox2EwCu/hEsLVSoe7EIq/lDdFlxelivO
Iadoef8x76nkyKfgIM4MSiwN7Ab7e4gPsOKSNMqZfUuBDNYDrdlZnSIl9YbS
u9jj27Aj1P0pZ6xmXPDaTu8XQqH36pJ95vyAQyxbbyY1A2/5cDWEjKhjgxrn
2qoeJ4gGUhi78tXG3TDd75C9Uy6QQegXb7OWRbIANfdZsR8kA5qr4xD7dDrj
7yP4MyIuwVy8AiXynBhvUJEo2J/YcWzRYXOxybwQll0anhE97+UaSU013KZD
jRWoP7PPKVckl9w9it3Qp6XQ0Ws49MYeWAUPjDHenKAH5uVClWVJ8OnUggyV
OyCH96YS9dRT47bhh4I0zWfAyr6UApqEGEO8fVs8/sv/GdiZwmTQlLREz/KW
ruyFIWyhNSWJygkhcwKppImhZNJl9revp/ulzEd/EJqie4bN+Y7cD7ZLAr/B
aCOe4HpboWYbxpptBhpAslgZ3MysqzHPdoB/zPEirxYIh0IWAIunHMxCq6Wj
IZaK7wd5RtO2uFQ6B42iF3MQCksOZstLpN5x8s9LPZVX6/ncON+Wg9ikY2PO
OcxWyAAunLAha8RCD2Ggu3NjgWEvsk/fBGa1bWO6eXD3cVUdjI90CMSr5+nB
9fEHGmuxoodE2beazVcK0AXr5er/i6UREl7gR+CCNU1QNvXm2PX+bcuDk5rd
Lz+bHy0fDBVHXILr9OijrY8ul4EFRjFmq0Tg3Ic7uvu4czdbNuIrS3NCyghK
V3MN9AUCAd120mJQgkHUVitKjRkGG4+RZUuiJDSs32+ZVF2sirZsTdBhADTA
Op2tWhv8UI97HFnJA3r4f8YPt9TroJXKOqfBoS1PR/I5njb85aGiFuqmnK45
ydIHgpUqMXp+YJDvIlyK3CdhaCU3jE74OnWxuDhly3QF1JGn+l9bBsfRVBG5
CRZxDFganoqbGaNW11xxavHw73pM5r3/0UuPW6KbrHLRTcbmSntXZR+KYkW2
/+QDgIt4SWjfteiNGaYvQ0scI8AvIxsr5erDmAeenRpT8njRBoFs6QIWvzZW
kfUehDRBPb0ezjpcxalJnBrg2SHX1LneiDT/4iNnzhpupiSqccEUFlMYHv85
ku9E9QIKBnypgEy8gWKyyd/iTIKQNCG2ZKBYydPor1eqAsjB408HmeOqSruU
aAehm1lC3cjYFBNJHcTDTLgjEeG8Ejg/YGp1VOFcUZRGJSNxYxaFB/Hu+tlZ
XCESjNTI1XVO505zJtN0/jB2AeuRcTBz1FirYzGnZv9QzHvj7zy34cbkHNt2
kk7MxUse8YJ1nXyOpcksCN0zXNGeN9Vr7mEjvojewr7GJpIoZ0MnEluVIlBi
CJKIcc64W5++6eRcfF2lvpLCWQCeYgzoivRsREYEg1ZcvvRdRcQSAYKtuGrf
xUUgHODnlC4+hxAnAqcwNRAnNQM5ls9gwOyTBlhVflOV0+hYaN6/zy6xevCN
KAuHfr60RDUvkWxBhHrjb0FWWT4BE59ksO3og/F4LDjhxGqWBvQLl6I80kXv
053F6yxUjKT5rNeQEG45Gr6DVFLSrSb+ZPN3eU9u02Cx3CUUwLc9rouNG+Vr
orLeYOj9U9CdkflFXK6ozYTFZHuv8aCXz+nxxbLnkmfRq5B5hC8GhlkBWGMt
wG5YGa6u2E3KT/cVXOxWBL29Ss4c56V3x8EhecBcYF1RQpXD3CkhiZqfi7aV
pcadWs2dRPTEKZI3yMKJtsuUSC/D8HCUPcrs8svqpgAy/ERkXlvOkfqEFw2Z
7dxmfbqOzl9Oqm/ZttDqyeCHVOKNh0CjJazIyAHE3GStw1R/96JCwcG6bCWN
ieE4AUAqqhnqqZsVciz9ckYwPLkCJXiHm2cfiePNpQFc6GRYaSCwhdowlisV
OlRswTKXFBG6SXJoElSbwO47yXOSjwv8eKlbkBIFARaZsHWtp61CrRfNbxqs
aVEkbFoAL2CFP7WTiBM+l7qeudp7tkYSKCB+UEtqDhjEFcKYZrGHQfOpd5ag
lxIh30xKxVQSGqVqQiFtpAroo2Ad4JFOhugJ2EeBb2thXAY5wstdrUiGlVxQ
VPp0OEWPkGp9rmq5apmAfPyByME3tWruFpcV4GeRomYNFkyvtwy1UHvE4Hve
tEiR6mthhy5NauMCyZTChtn7N2fPfzx94UlNPN/LqcDgKLrtcuaWpK+iLpMY
e1tNKi4uIIXebmdZtKpK1vvvYbL6ChdrMlk3TzANrv1FMcl/4tX/i/YC/Inz
+KwLRS6+n+C8X1bijlP2L/a6wYEAQpW1OejHKLsCNgH7J6WQRhbAY/lhEbyQ
05xlkn5S8NH6rK4NP7cicQALNFSeBpPRcSgMKTsSamLcIl4V5p3dZM/YhQvZ
y4eOhcrpG+JLQQoKRrK3+9Hg8PPnbLVe3vEGCQOOhABCO5EUwIZ8XI5GC/5r
tH+XD4ZW/TyFGVCtOLRldc/iobqCUmZm5A3H3zACrPZlWJ5lflPOfFYur2FV
69R92oOutBVe18Wc4bgYCM5eOgSBYUXxDK6q56i6FF+L3rGl+HScBtOLTBOI
aAmHGmtQI9hgTVI/Rj8h1GIKBVfFV6QggxUEVhrxgubIK/uStojMo/K01OAB
7I07pm+0p/wJ/sD1YkGM92feVtGofEaG6GNlJxOICel5xDJULQGIPehpmGhH
fn04C1vDUHrqFvmHImI+kJ7iae+wACYN2gUW0e95B5QfKIypkjSPZOOgS8MB
Os6fP3eYzeabhhywEkL01ByR+FC0AR7lJp2ha9wmyWLQzxlVxlwCvy35sc+I
YQv8lxqtWkqiKk62DkFRbETPYTlEC+IU5SDMRc/kQt0H5unQI2kdAS0tQyMC
qioLSGTin0pjwRVEeaW0urICUQ8chhndViG/sq+yFmGTu5r0JxTnq/AcaNl5
yJgIJRz2PF8YKxnQRW3gksXUO8rybFLWkpBtF6t28zrO1qXNkVaMWf98vZw2
k+u6KC/hbClQKX3R5tM2i7XfwREAMGAgZU+NMRxNC6R/TtsxmSa46KiOn3VE
Oh/dtFYzbNtt0Qu239te0YnYdue3H5/vf/vx2Rfu9Ydgy+0pB99yu3pEbE0l
5xmBAxVT52uiZ7QHVtBBcAnevqNsVjXraU5EfFNlP+cf4DTLsonu91FGUz44
2MXP/Rfh94O96JOX/Psp/3zMP9FqmH95xD93+OdJuGX/dOv+1OujaDRHPJp7
d4Uu/vqxRflZOjId6NGXh3nPvtK7v/14uvvtx8f0/9Md2tgX0d/4dy/+PHo7
ffVSvzrVfx/rv4dH+ssj/XdH/z1J7veP5WfcTzw0RpDN4528uCz2J9PF1fTD
zD5aflgUfKvjOgRfKx1oZXtdk8ezRyKW6DT9Xr0m69QF9uaZhcmtfo/3gtf3
4KA34LRY+M4wbHl2DwNb7eZlzxPzCXdVL0XYuo4PI/mS+Qtx0GLp0SO0G5iB
R4ldE6FJi670ulzCSIwKH8SQPiWVHF/4HiEa1rPvz4sZ2Y3sVKpQThhAbQEg
wdI9qJFlHZyXWEPAa6dVRKnDaNyTCKaWk2z4iU5xtl8KjMCnb6Z5y67Az5sl
1FzBFFpbSxWTFyjeMxKBuCdYSXBLoygpTIY/EaXfVzeFe6LSFwM5OJACvoBm
fVcAKc/tdT9fkKJ2Pcw2Pp/md4O4bo+HMCrJWH2a3dF/o8ViNJ0axdgiXtD2
Cdjt3jB78iQ432DogUqwprtPnjxB8v/OXo8LlsQloiNHO8C6aDbQKrc4+TsF
U761B7pQtVIEBQGvvR9InSDrcCEzNGNY9AGLFrA8FVMf4/JRf1Pj4GswNxtD
aDfW5pijuOnDhF7/WDAe3wTuSeKuAy0MM4VZgrAeKTCwAobF0doS0opCACxm
Dr9rGHJWV84cb/52vWOF4xqVb2S3Ztzt7Y5fzNfz4eGjwye+C5/fdE7L+qGg
036b1splGbjK4ekz/Hx5wL/vjOUf/Hy2y78/55+H/In8/pwvesFclX97wj93
ouc87mk+mKi4knbPXad73348nHz78dHhtx/3iQHv078HB/T/vS2fP6R/D7qf
O2biuAd/7xXbn4ffNz6nd+zv4nN5xsYY9u951uG2Z+k47rkHn28dG/6/a5/L
M+Lv9p9sv2frfHh95Blbx/0Y7M5iPcaE1LDQSIZwJCUxI+coGOU0ZDItWs56
IR6IY/PpE10zgnj6/JlEV7m9YDwBHoTNb9lzDPsn9L7BnIgxeR71lwwRQv6T
7sl++tV8il5ILDxbzenc6BnQY4YqKRfxsP/8R8+Ck8Nw70Ew3pg43QX9IWDw
SO6DOqEfSPJmuMaH8/SCYc97Zzg8l5EE9e4lv1qaZKuix5xZsYO+N+5FINS/
ZebIU+edU01osqKsXRmuvTKCTDQzLI0zboJteYPVUDWSEmNMMedGIs+1b+KN
Iru8JTOmXWvKVV5/+Jqck6BBdYKB2SR6ulKotRIFCGzB7lDxFwtiL8uQVTQG
JDMqiI8+3Nd/R24XhJnoWS3J1Ws0BJ/mDf41GGDOvo1ak6p0HUpaScgn6S8r
x96vKL0BGFCNxUk0uyn15BQ0HUtxq10+m8FU1diCv1ZLBgR+Bi5eCVDK+sjW
cmCdd156pkyJmPtEkAPdQ2TOaE87CStzoLM33hIbxDBfllyrQKvwDN02xK9N
n/s82rdzdCdfznrOfNxeKRxf6c3jS753bP3Wxiu76RjM4rXGktjS4xc21U0v
6zxPvpdn4vsBUYqm3LpAPO9CDNwn5Ap4kYRGr7S1G7q/+dZKAr0pjV1cmuTT
9yEFy2EG6GFgwLdV5F9IFHmkNHr1ffBVqrfbrnq/PPmxpzZOvrQI7VVVTcf5
rEbRODcAiTMNWR3/Ea5tIvE3kivRPYKcpsAJeJrOESmLFuPcYhEI4tsSyY38
eKf9Na2Rsbj+fQ5IlmIJcoKOHWIFF+l0cOx090ICogLcWjUN3fdn5MHWZOlB
/51gDFBiG0ZyyevpXFuLSAquwNBHWU5HOMvMHAEJWC3yZfQESAiucKF5TP8m
fMdC8PK6TC/W61bFR4WA7J/9CftcoqM3BNvOsx0yHf4/62wcdvQUCSsCznz2
p4jSp/7z8QHvYew0xGQSbLOO9MhG2TPiLox/GnBXPn0z0Wd8/gfEyxZ584zd
vG99/cp21q4nMQaYkeRoyxW1YkeFEY7w4foIkgGqeVI2BWf79S5J8yl99MrA
vnpsSD47hU8W2hTrSZ8+NfUE7TBIgeI0WLjBQ+6F5JNGEOyq048yFBWMOPWQ
gdfuWNHWxZWES43JhHSBjHg2cC7hV8flluYzj5IiVxAv8PAK+o112xCj1rKR
GBRXlbsoV0RCekUMOoJHSif0FFuxf4lCBgE/HEiOrGBESrVl3LsP1MOhxySR
R9EGIB3QzwUFDR51R+HsAlile02Gh9Qvh3xdUOR5anN++sY24ysVAPD0TsEb
upQ+Oyf9uP8SEt2SsqMuG1jLZzGFuHPOZWkGDB4yN9+1uHDPXr46yfpp473I
+4iJlJd1Xt+5E0VI9brRWcTfJe0hT3FxuGBN4ezugymi4a6RPEb2rkAte5Qm
TjDXVR+odet8LVri1ofc8bcRheA91vm89SXaCGwcxVmOAq5MJ7dNUZSMRRxj
8Bie5B2VbYyn13RnK1RUCgKiZ7OgKMQq6PKFIJIzwDtAlgSkN3Dh9NGmLicj
i+GYFNITs0oGyoc4PApOiQi4CauqQ2Pw0vVq1FYjTm30fsCt2Fd+2Nj7B1Hk
P+NsxgAqyPCusQ9St8pHU+Kt4jIexZrCUvFGJXmynXXxqLtkkFXT0iP6L6Ol
FCnLC4Mdu39p/CM6ZUro+Yi17aMuUaJCKcLV0Ed+gweH0UHfnr70anfGGSs8
a83MT1KWpZML81WyLu/b/km1klr0dFW6O55SZpR+6teLHlQKRi/n4OXcWnfN
vSuFVRrgzgaucTMOZlWCo+t5kfAVD6IQAy1a0XOY0PZONlaZgORYRvKMW3bk
DLXP/D8xhSRJEImfiuGaAGgnadzo1QTFSjKUbiBVkA7FOpX6CiMC0lY0UYel
LoRiQL+KoRemQprcTMrggDmNx8Po+BaSLBJ9e4tKHb43wKRGnTN3QeyHjokr
6XQ6TLTqQcA8ReEW0oV8hnFnoS0NtnNKpL2K+LG9exi9YGn4htSnR/9aoeGc
YsWpEdzG/kg1DjaWgg21pvArA+ge7U0q2YxFQ3o7jwhc0ldBkV20nvucdjlL
KcKQ2Oyrej1VAIvcXqfmBXJSgEysUX2rg5UmTW2DXikwZHzhK2th/CJJu9dn
Il+XS7lsLQRCCLxuWnG6j5FgYCNhrRtJbY04TExc1njEI1N6fwh7sFAq8ksK
gzwgwjSM8la6Wbzso7GUC/UAuADFTmxCVZi4JIHR2S3FJaoY8kiSAbOt28sM
RVRXwSMn49MSTvSCZOrzCsxQDbDQR8gysIQgWTvuzi6UdoSepTFH4Ta6PUiE
npUnkP5aFHF2vpRaMky1HgXBWfmlZhpM/p5riAnHyHroDQ7tRprSymvkVs4M
H3Y89gzpMdZkaomSJfj4nni4eNNyAxMaC075UWrsxUUq5vMxfcRyTeIc6gjV
/Fif1b2MST/um51mF3h4GsaPjsD/+BWtIoDHVjqjRy094GFiLGm6RlDYeDLc
kUw7/Lj0RBnyrfZkMIhvhou3qomoZR+7QVysAORLn3cI8S5kJbqUaIMYo+T4
pBg/m5pTH3Q30HY1gUsKS+iA4QktiNnu82jNPWm7yNEkn9luSWWeEAbHBu6g
xWG0Ex/9w52BeQRBsBFSbGM3ciKnpRmB9QZK1nzAaxShBwnsIQOVd1Yk3Vut
reRz6XixhonwTt+SqJZGdp7YvGrg63K01Vns2j32Kdp0lSeHjWeID5QuvSB2
8zPgvZbTgYe887I6dRrLLR3o2pYNCvZ7CVyetSnzreXMv8ZV9SjiIG7kDIwq
CatIGDZ0VIqcG1XEZXVtGZ0aWp/bgiOM/yKW/JRV5uwvKIoL6/8TffBvvXQT
fITEBz1Dw3NRbGIhbTb/cPNca99KafNtzCowVDk53iHEKlJy2NDpS0rCJgBf
43xqj+uvCoo1I0o5Ir/S99lwnitbI3DlkmXtGd8w4mMRZ3BcfAm4UHjBfcor
wgHdjTG879hLBbn0Z5ZLgrTxdY6BbcJ/gw5Ck5mo6kvgd4liFX+XnR7r2iUW
uNURLqSQ3JL3h8p+Z2vBAIIkhlIutf0tdyjhDEnVIZcgYHBWWhhSTuvq1ok4
bqz2ZEU2wnIiubieLJkKn0b9mFDxqJkd/Lsh137Xx1+8bVsAf8P9lk6hdeGM
CF0hTBILdV9JKS8y5+SFQGJbEGCY5Lsh1EPyXS2+Y7ZddZz6TlMSoicPk65+
0srW6u+4J0hAO51AXwATuIv7LwwVO3DocfrMpUrHXFtse8xr7JFOhV7H7RhC
wYK0seBxezRgTRrWDhPWFceDNoXWYR7QyMKBrh8DFgsUxVrTUQKC5xYHOT6+
lmwJw0yiqfOweHP9Bm4IWlWkRHeyeZ7wPbsijzyf96fbO/sSFuCbY1oRH6OY
MAdwSJtI2FaEAScwIcHgFrgQ76XUVnX3jBwSuQkiugPFlIxvjLkYZpNhsHSZ
oT41/l3eAP2dl7fzCrnGW3LQEdqWhLG1I3l3fU9pMZ9RETFJcz9eBgv8ajKN
4VpAjw369tCXdShyrdeQvQVvGGOuk7vDEcYIi6yvtnwO8TrVFqxDKwxFvQBz
JSIIq2Y3ag+KFg9CB2qF6+xGF0cHPWuEOaNy3UMJ92O0YAa+4GX59eimD0c7
h6Pdg+O9vQDd+eHIBw7/toYKVggYa3HE2QQABX10fHD4qwFJI9xTxlMkYTgW
kNAqgfDcZcTVx8cPH8fwqvTAYnE5L4qxKTfFkTJT1uGBvLq7PzbxT8f/ePfR
wzCty9rQVo3V0dpVR8h74ykdHgMiYDcsA0NIHa0Zx0rf2RwrvY11NHdHIe37
iBWb3ScPd0e7uxh/PgKkwO7Dh+Ghy/nRdTUrxnWeT48ui2a+pi0R1NKD0c7u
8eXk8eHj3Silpds4kQNwvoFsDOFifQfZ9W28OOmpE7WPiqzYGIq5UZx5CY5z
5rxHi0QhiSE0c6SIuW1oNYTEPTkxQsGsyijPHWcX3J6JD37p4ad8Zlku/U4D
gIk/iOjHBkdIs7WNpKW7M0QE59ZAebUATmq2mq/NPzEtOI7xvWn4xIF+wEpI
daA07vV5aR6L/5eG44RfGMJp3HF+yxTFg4G3R7ltBw8On2R/XE9ncfOdFy+e
i/zHB3+UM5rtHDyg/xH97ZCqAPbakOYMD+vJ98G11GQPshfPL55nP5S0byce
pybzWcEx8tYRY/d6LvA3ZA9gHEd4C5PswfHB6PCJjfNHLlL50iB3Hz/YOdwY
JA1Raz3++UEyw9UBEmt7LAO0jGExcqI8hbOt5pLZWMFGE6WiIkGSQgJwaFNV
F/X7xQ5N37jRnhOxaAVfkOVamOOJS5/D68YpuFqOvlACqIXGiUvpVOm+5+Zt
d6qyMZOIDq6d0tsKXq3Y1ouPgFNElt5V3QMl96ZF2t8iipt3Ya+JNxCbRL64
4jSkBQp0BYqC6nzGlzhp1gYHrtR+Nr7jNAjHsLJVbZO5JSMZBF9b6MISowyr
B5w1qS+Y2cM4JQJBhK/YptgD4PItbqeo0JK9NMwurTFNDAKgu6AtB7UmGG34
SvZTI2zMnmhrSxn17QuhMtUOXQzF7Bu7besh06nLXQdfhuv2Bt3cb4YKZ8zs
BCdc8c4fHe/vorFWcjVZ57N5WfH1LV2fd6/3nVte0+GpFL4stIBVT6UiVmvf
wGsGyOuY9LQfHrUg6oOC1Zxrp1YO5IiPPWpLzuuvTdcRKLGKUO5VkrRYpKHN
iRvhNEnbsqEmfmlKQdC+JWYUqAOIgCtNnhtvAibyLJIUnd81zvdVNwcqphLF
5zjC7DPxUHOgdlrUkZ1zzK3F66lH0sc736LwfhqJlfNCTMPBr3EhvPD+mn/G
kRC5ExhlR/rZakp85GmOvfySfhEn3QUZHnzGdQL9yNjqUYF18DX+HArLVojO
iZMCUeck6iTtODTQrFkiXaAPaScu1XgSdwJaicRJyquCH8rzsIFwH2+fqeK9
BVc+FUS8POaGHWdvitvELZ6LU1zX7ZL3W2swOYGWo4WXd+KdCHGuaeipE73U
B7vYhc5gc1E35DCcuLMG3SY9cg3Gi7Tikv/W3p+al1PXhb8hduhKG8+sz1+H
kE6NL/I25zvLmXStLhjTjyfHzYQQoAShKrptFFDmlW5WOTsuVmKIZoogH9VA
WhWC7HB0Zg29KF5jxkpm7I1MdtmoijOabEd1JxJ3ccq6vJRwAkPEjmjzztpj
tD6X8zpul1Fqhj+D427XOB5pyvjj8DKM8o1eODQZb1qHR8Wl5QH4jI1y7/FL
nLrRe576lfgLN4jTif206SyLDuN2T0snNyROIrFAUjJdjkybi7pME0L0hKec
1Vo7+9CUQBK0x3oSfBTkvr40kBMR1UWS5ewqRNIkF2AjMFbGMNfKgBppxtez
i3vDVO1o41SE4LfCcfAVdVf3OhwQ93RfdjjQUz5/FvdcSLZJN2hLs7IoLydk
5URaRbQRwxTzQcq6Hx48RHpZ2T5V4Jwhnemnog4O3bR4KqqgaQycgj0jJRir
7jv2bAwmbqTr4nOfJHSqlunvyhuvGkVBGEfMiHOJcIpV/ZRmYHI/x4g4H9wy
wLdm+MvQt3SjCmHXW48BLrLGbUSeAJq7qXTafAL0afpmsmvjRlNxq5wtXnvJ
6Yvl7za30uQ6aX4TfEp/EAIu5mQoSCeWTfJfqr4fN7hRm4FEdtH+vPWROSmg
xf2P1N34ihGK82Wf9FE/xk54+tcPMXqmDXLLM7tj/BVdbX7NuopAsI439lAf
tfhqPe91HIZTVQ95pXz/iIN0vwZkbLv2F7V9yWMPSQe9cmvHzDjBqLTupcJT
c4/OZA5vTULZEG8u8TmzgJJknKMoKYdGciVI0D66j8Yi4YTGvA35cSS+fXfc
qHGbucVCOsDv4q85WQnpFvB8+CTITlQ69LL1JhJP2D8zk+g/N5uXxKep77Ce
CFzS3KTfOvOiDI6BwgN00NJBrrLmpHgmnHfrDS4uPBXD1dxZ4VZFM7EhIWkT
dWwS6PBYMN4jb6Z2zkDfaTacacnA0ede6n65oBpqyZ0mhHDepC81FjOJcyWl
kXrImIyq1rPNTh+vz16/YFhwWqjRO7j8ohaQ6Nq8c3CI1HfvF0QV6INeiugo
lkEo+vGyvjfqsbfH8tY5FHEUygw3e2zH7FjpuNBkSgneROtFJLaOYxyKvRvr
Q17p5H5GlhUwzy+LebOZnEFUP49rBGjxXyxn2Nesl8/nvYEkn/ooEvSijbBw
chcKS0I3h0nOdjjn7lwGaR7qWNQ3IZWC7/hM7w6zl+UMPGzPB0RHVm931C2/
2xiM2s+ajMc0YGySpa+HeUsI0SJn14KbnHaP7Vz7VJkHx5CFHhO8CfuPdeUw
Vf5Tx/3TTxGoqS978lQSZgegRNJDy7zWYBQfqQS31uc+xGN8ffK/QaEx27wS
wPBUYWpQMcswr3JR7xjIg5GOBdVJlM3Gps36KcB6bwQa2Jlvr0B6eV0ticl7
7iAP01MbGQBa2/MuAeDaGiLscgzpCyPNNNHjtl6km6WjfBoxTenum0x8ECEj
07UL2Jb3XhY28akcgfsfKDuHtANtM3bPY6OgkAHPqmq/ddpR22NpB08MogOF
7WG9LecRIx2j+nh7nJEWLbHAOpZZ1Bgx289OVnU5z0h32RlmxIYOH2r5H5i+
65qUiUAzFl/WCiF000H8jsIjxMM9g8dwxtnu+JHv9CLMijH0p2XEc22ktAFv
85p+5aCGi/qnb0ZKJd6xf3z48N8ipODRanqFVH966xGt3pyfVI3LtkeDI1mT
DA5rtTfey07fnWZvzs79MFnFj8w4rtw9femyjbvjyfWY5+XZbo9MHGF/u4NE
IKgsAoMd3rMC0l7t66eOoY4+LubH03Y6Wpb1iOaDuxs8B/M+amkjq94/vJZY
yOR5PLV8vNuzA4DhW2NMJOnqcly3Cy/rk+3vBM9c1P+tE5wiMt3ff7DzGJ/t
7j7YefiAxvqET4m90HiR8w3H7AyhW8VV3rRwJ+SMDMv1RyZUrMZE0d8jF7mP
hUsEq8yPOHa0xG94/4hMi93d4/390c5jF8yfopHNwLyPyMTjll3jYn38Nx3I
UVtNqyOMoFxUPc8/JMuXbNur9Vy1Et/GgDXICKqGtWsOjqa8hRtwVOpr43zt
duAzGwFmiJFx+II1SlY6nKUtWka+usg45MJlL/5qqV6o00eJ24N4AniZwGuK
DjALcJqLfIWCheuqlY9CzTgGDC+k8+jK0Bqjx2tOXWh0US5gTTeTfJkm98E3
3q21s8LA++0fNB3w5YNIUEm7d0jStXTKiGABUg+kM/7Q16r7YUBM93lYxDrg
SLBUW0lRjAoGX4qTVDzoDN6JMaDj2tB8pz4jWBB81O95Oa8mHyTRO2TF4Nt5
NWNXAum2yMFJCzzQCCOoA7Fa3il0dunLXacqJI9Q93MZC59nqGciMMxHenZ6
LDbK2anLS26Sk/YSNWFnz1PfNtccwYQJlS1s5QR0IyvG9kqXBkzZyd7W6oAD
WiEvK58bPyeJWOaMgDBar3iTrsrW69V+Fbv2OC8+cnthtAyGLmQ8aQoGmyM1
P8jvJ5tb9uph1vFaOWGMySqyr918gtvjx7mq5LQBf/2fuSunT/0rzk7//a//
80H+71mbzxiOB8wYgBM001fmmfr06c/7z8eYBneAj1c5gpAqW3OGxUgrtsAx
lSCJXdZAl9xxOR+t9NtwbAJErLePJXJnFk5Vu7PTBG1VEgSTtqeqryInN5/T
veGpFlF1UcF77EsTvqLtTJJSlm3R3K39EjRzJSoSmFRcl2mRiairThwdDE+X
dLYrnSqHxHju3Sb23MGWrFb4Z3VBOs3dOzjUjLSzvIuK82Ae+7jxVVWnKUjs
e/ddHva80iP8jLTGoCNy+pKYgDWdZbEEsPiuR5fvH9Nj9nrDqN4AL+MWAZwE
Fb3Fv+ZvpgmQLOGGCAcPHzx6mD3L19drdGTI3jAYARy9tJRfNRSMYo8RApLu
SmVHyIKyzcO+2YPCJa0nTBqTyJVKwzJt0aJrWxdAulFicgpCqid4wLmfTSG9
26bSsaguoiCFlL9jdEr0fAppnZRVwPvDob8gELlzneTb+zLAODlYha1mOoJP
ruuVNunCiQ4VRQYetr07SCOgLQsAHIWoI7ek5QBhQFJF5k1YOZ/oK4wEmE0B
4TkxWVtJ3WJ+2/smdtTQArw/P8uuiHYkO9/j7bBQvW9c481y+aaIS8s0fS10
MYqbLZed0ghSakfh26f8tz9gf0GfFb9wo3LaxYzyHbd0hOEg7HeP2+6hfSKu
YpoESw/6/DUpZ8jTYNttd+eh1cbZqLQofiMRSB3sB+wMPzymO/+L3ka/0TD2
pYmFwuZGfUJ815g+TW6Q+WrbBK3EMw8lGTqHui04QtfF3G/tZV3dNuCba4WV
6Gyck6l4OtIGh5oHwjxaSz74ohtZSzpvdVncSDzJ+eQNBQbOvdo/CHLZ5+FE
ori86sxDaULLI7qoFaIYM1ddc9iMnVm3JSB6AQ4MHpCaurTEf75mZRJjV4L8
4d27t0OXTOnih5NXrzKPj9Q5kLS6nIi2lLbCq7qUGDkny80jQuh/M/AAfpzz
hB4wer4vifUzvJDMOm9VQQnHkuvAJYTdQWoCtF50Erky8VItW9QWLc29jhe9
P38lJnFymGNX1sbs+moee6eVlJnIEimGGB5rIvKv/5P+8sfw378JVE1EfVpZ
XHWYofGDifg4OBnZ9wtWjIYJiTnBI7duK2zRRi2uNvVCYJjHfS9QDTSK7AUu
XBWcathcZ1eBLu383+aJnqcrwrUf92EygqnyQJX0ti4Ld80Zm6kZq3HWo8FX
kAnx95neafcGx4YQql0qbMgw9ENOWAxqlPKl9LBbxaEtcgf8qevMFk+hxy11
duSnW0DkbBfuradCbMxS9/+xToRFVCL0Qvuf3WtefvPNN6RRTztR7ZA723le
cAV3zf0YVstDQ1nNLyeG+yLfXKBB4nInSSJig0YsTKuoG2dI73NR+zUyYbQm
2d/PAN/2gFCMJ5rzRLu0WllwDE4VUrLDXWUTtVeWc8k6A40hpOkRUQ59OCyu
1dVE5KiZDyls8yZGu4gyaxMaVKJ7fp1zvZEfG0NfAPHCDNvBtqmoQoXiEugz
XoYw3GQ2KdVLOrBUlqy70jIdzR+A7tjwvpgdrS1OoqTqaI5w8KxbzU57BsQv
G2LBXfyUi3PZhba/Vfhjjfox27krfC+0yA0ZTVKGC6GrPpw8PBPL7OEtMWKs
WIXKGrBBMLg7qBGg99eWrXuG+dUNPDOLoutb4YAXyMdCo1oHBreV0qtCXFgt
HIu5kaHdYVZS/9JEBWyNz0JJvAXCQTeOme+1aCXwG28WBX5+57ymOuBKji3F
s+HxT2VnOVzx+57+MeiCiHareX6/gQvYsxXd5CCytJrittHflnN6rL6B818T
r406SNCaNtl8zlrx1YFva4RSDHxwIOgbyZnQfbFSSJMSsOGbNqqKT8aV4NSF
Nqku5FmGN/yuuUfaDoM2Gpc+Q7BIyzITC/3nkheNBu6GHRdB9rC24mPXPqxh
C+FTcel2zqu2ppuDcbcCe0MRUBIom3vIRb9/CpUnLKmEmBAaGF0pnNdgkD3Q
Ed1LQkYxxxFCXg2Gs6bPxGKtgQgJYtpCTWAp6BYecjH54w+lgFmGEk/wW3Q8
jt0yQnwu2eT1UjAjSTihBrBA8SjriBFT051hB8E5N7SiDTxhbC9xlwJ5DW3+
vOcpIZ2EuTdjh2hBNi8/sIM/rTAvNya8CeEBAxdqW1zZSqu7WC/wPKEMacWh
ZmpSYRRS8qU117hdw0V9d0Sv6Xnvb+fLY8vZx0V21LfsjuG6+V7LJqGNQpJj
NeROOPDdN3yU0OBMH4StcxKoZ2UhAj3wrHy4gYZXSzg4nIuGAbV9DcKS8TZo
CcfVR9rL6bEcFC1O7EWD4OjTPZc31+XKbmHpxpKybGWPG4lrtNVKx+A7Pm7y
I88MMvXV1MOg2OIFLWd9imM+cSSojhlpxgzUphXPXQw2trhSBhqYAA03XiSr
ZBrrlo+xwmBrvnLRH1KvoKcUb8vBkIrzO8nZRq/0qUfyRC0Dm2jc9nCmRc7p
CvkibYQVbFWmyts6av4wdmXbxHwkI35hpi9M2Ht2r6SLuRSxnLJlQUXfc7CM
u8lzNptleHg6NzDpdFmElv2amevXZ5To7CyVZWPUGoDMolnGyanD+JzkCrYS
EVKO9Jw1q2zTVEiYktblFlYPgMqqRbWsJpjvRDL053DM5vMjr511uYHKJg+o
LC4RD9FrbIS7Ty3F5rSc48jsOLHyAd8gY6PZsCKlTASRayngA6qywtWiulvj
S0jZa5DCsQpWAjtrJ35AID8XtrDHtWI9D1gj7D11cHfTaRnZwPPu4zDo8Bb1
9EoaeMc7yj5T15+UN9AMFAQOv+GD4J0NX8WfASGBDZbtkC6WlaR7/UUL0fZK
q9X9Rm3KgHdKQq8VjAJRqxSJOVZfEwyLqGqL+zhij1DBaK1EPxSQ1wmylE9k
QhDB0o3+TkZlNz/b2TT1qG8q50N/KEouDpiKphJ0MNouV17p+UVTToWAHYu/
LNEfR/a6SUX0vtRUd+WIW+ESfZr79kJlZRkWaPEhNUv5QcAThl6UdrhFdfiH
pP9RrTrPOBH/Gq/ILpJseH33NipoI2ILkUINdAj+BOfETcpCS9Oj7gjOFiS3
Z4yzE71xGEPrbsTGLXrpNHoZLG6FzLUsqL4UgGMR2MAD5JGmGOTTwlfBcfs+
Iaqy3sCasmAHn/M15yOMyLZt2UF3wzVeli8o/U+xQVEMhF66LCcf5KR0t5TL
Tiq4JvUZz6r5BwBoMwSollMONIjMVFStPH6iRP7FEHqWLz/U61U7uUMCwkBo
fKyb1Gj9/nZCvD/Nz6VpflF8yLaH0Sqi1OEYuWWeTz5IQ8IY5Mne+tR+G/F4
vpTfFlG4LepxWGupTEZxzqVfg0DTWt7N7K2TpMG216mPObwRR/NNEWdvaPUh
TydCkfKS6wsVoHoC3KRUqyGEN6DqpQmSMRHHL6JpgdezF0ol5CLzfT/F0SIJ
18FgJMtV+Z+LH2U8UZRP5vb+nWWKZIkjOiM+7fpJLC/U8Pncy8E47Qy+FGMt
YDnGhBcwPDs+Wq6Zl+LnrJ9PDVOCXbwAUg+xwIHiCrYsOrpdh71IsAkMA4wd
XXmLO6NEle5ia8Wt8xId5yswWNYV1E4YR/cBAwWly6O9g+P9w8fMdZ1enSzZ
sZQ3juH6AYtpund6qj1Xm6/xGBXKdpmZnQTDUXiwYRhIJmjq64pSFzz9LT2p
R2wWnkjj2kZy2hctxOsTQhXfrHhjY3Pcp/oMQ82XgPyq98d7AjkwFDB+MrY+
kvyaRDewDrFGK1bDzVzttoph0f0eBuDPiw03c4KxKAdaophSFSu9JR/ErtJI
8oabvT8IRZzBWcuw76kD+st+VbOAIr9hJsbW3JeExVBDRhuYeqqQsQYracTY
kEzbPsyLtpjHI990S8aWYykZoWMYoQWp93J1Mw7FKUc6i5560YO5Ja0vRMNQ
uNpNJ+NG8xFp0M4BwsQgD1vQtbs1918J67KY5GvJLwB2gxFk7CBF3+277Kas
27UuPm3Px7tQMx92qxV+oT4A3UwzCKNybOyeDmTbJgpp6hHNJJtGHsV48XE5
RKzXhX1YRChvtHa0cz8Xmyu/5SLv5SHNtrwszLTdXFE+KTwNDmsLBaeF040a
sleWVueyAJpXpNPuzCXKO/cvS+bXxZYKUueYdnMcpbqM24qbo6OCnJ4K23Ws
cQOFGbkHqMob9KeqoahxhG6I1ufri4bSpl2kT5LHRon3GwCjnqky1xPOEwqM
xZqNc8q6BbUanejzA6yUz/tDidnRWyTvhg2goW+Y7AMSmcZBEjaXQqFwVzS2
ZlXf4ZYdAvtkxbvMVUOsJFb/Gfg8dOfqk1XH1xXBzBc3vpfRCbiKXOyDa+Bm
iKbx6wcCjsF6rAOIo8ILFwygsoZbTvwZvuhjQ+/3wJvOv5GztSR1d5GwlCTC
F2oBaPh+Iy131GfZuVSXCmgRUVZEeGgESGYD7FQRW3bllH0YIkR978PFmgFq
m4aRgYkPQScHF1hyX2erUY5Eu8FHcma/hNMuxnuHBwe2i/9x9icXjcpCWB3D
IQTZdYKlr4h2vowtOiDheiYuzvSRFUxOixGEtYYLXUzjBKrIrhawCWU6IYwT
UmRm8+pyW4JEjIxjyzoD4XoJbm7JTk9sIzd5b+a44ZweBO1LGxWvJHn93ONP
p/tUKBNgVrKCA9RKGfF3zR2uigAozsPj3b2HPfpk9yABs2t4D4PW6IOfpwxm
vi30GSLbsakSxa+BSR2DUvBUu0JN2Q/dQBQpMzJ1f1bi+foZO6PdZRFtKfd4
MPfbluiU3Cn9EGEUDqUXYtcWjFmPsWOAgrwlzqdwIiexI+qU1Ejerf2doWPM
wj8CTYnUyt39oZYkvSEFdPfBW1R47GzZ1VjDOkJvNHHmkoqDPC9IIX3z2Eu+
Ix2ioiTujejtUuuyO9rdP3a7o9UIf/MWnsSoD7TCnz75Nr2fh53mlca+xdJS
g8mIFt0fRWAOM8dc3EscS3H02a8JDACI6H3g22pyECHZb3w8zSEKHF271HKD
AnyLVCpLqqxDVUUE058AipjKZsg+XkQZ1g0XnNytCjdhwD2SLsEVHMFXTeHY
ibQZvwljbqbGhmnm80xTlKgkaCjEZQKJadzB+S9rvTTIdd+zIIt7ecAdYo4w
4S+GVoW2QyEzSNmmRHI4IqKeOl9ENLTZhLwMpX2T7hyu6eqNXg7z0lsFRLzg
3JQ09LW0uIZvbKXGnGDLMgIZS4Ng4+dNGRsRiE85FLuzo8wQdQH6S2duuolg
glrDXswe5RbUINK5l6+z3e9Oz74/e/eLQecUhnSPThNjdu5HsSwJVTWWXb2h
aXvHdZSyHgqfXGd3m65vtGy3I7jbC7hPiu+kZnXs8bjmhV90eWuM66jrqVmN
3QpltS5FypqGu0X1CmSVcZZ0iGokEPriSsRDf7Tvv89/Llriv8M4oCtwAuhK
jaLzGz9KuBBQTTVbxthZCLvGx/5O+mYieZ5bGoWDvMpXyJzm+vQ8pdogtvzQ
kczrKzhYQwjBhqW7Z5LDUHm/8olUHbORdRd49l0+BV4/59zLLYKTnbaZxYGQ
oxHSV9NkJG3zSLYGyAOKw2eVzmlzEq+pcWLZ4CuEtfMogh0N2phcZLNof9Na
nz72fZQSoZ4wviB3OjjCziT6cBMcIYjMbZhQ9vynftajcmqSPnyy4fwVufmQ
DvnxBOi8Tx4NJ0DVlX/36F9v4n1d0+Gh7zqc9hoeut5Rj+ndHGeqyy7yYdqC
OO5AHEbOvDyqXtrahXjUk6RsyxdK2912K3Y7NhdXPdXcREr6j9wkkE8JHAIr
+0jY39sfXZZcLbGobkQFoM+kD6N8/0C/5yxe/VryYcT0oNdJC4eQtcQhT6lD
llnBgWJBO03o4d6S1llmKHugidoRgr+NvknHrcMe2agxGvtMc91t1wU+/Asx
TzmULyVEdKLI6p++4ftGEjn6DDxY9eUb9jrbwtJHbFZrvqEtd3p8h+LoRD+p
yyJJ08SwOXY/q2KwPUvsQ6mSWSA5d+ByHcepDGZqHtLAfYbdKhrDTHUdRPmA
AC3OQVmGqDmbodu7SFOLQ5tTqVhb2KUKRsMztZxaPN4mxQvVSOhqJi1dpSmr
62SnHvtlE5/DJQtPeASRX8xQLq1CKdPZY2UE2pT3r935IybGR5q9POy03tgw
BL2imThtOFyQboE6qrUlh6J9WDlQCAC3nhblICp5KjgIPf4qXcRkYF5kaQsC
8xEpfv6S3q4pQqQzbgfjiCUAWeTzQjONHOeyRyioEoLhfPZgEujIl8GPlxZi
LUhd6gb15J6n8q9y868J5sHqaGi687utjkoodY9HO3tg+bsHR/z0cX7sLlkV
bcZEXx9+Jc//QqN5pxcQ7xeWZfUoAsbhWbGf5Gavebe117yEIXWzaZW7nId/
fnY+5cDcb3qZltxIbwlxL4X8K05/D5KZwcVNkYeSNo3l8iaOooftkB0kxicV
f36eRVR5H1BVtbgaDbhzYUdREIcL/33QTNF4kgs4YsUvPPFFrmwrsF7IvAFh
z6+wwP81NHTEMGDj3ePEhd4iTo/UEc2Fvqfa408q/l6E6gl8nGDgStkHABT/
iTbPQuY36eu+6LEOoe0/Jbiwr6KQp0G76SGKWloj20zhWw2MJFKwvXEfjBqX
OsCkJqTH9pCBl/aOJJcwgnHj0nffHikuyl9UUxY72hC06Yygr/pEjJ/F2K/z
wnBrGl//WdZc4qGQNux64+d5KN4l3KmsXUd5vqzdYYLcNgjBOIVD8/hQ2Ucg
jJRzeEzFaumUDimUhvgOkKV3R8RLE7/N77guUxWqJDtA25R11GqeABkBDcZm
4YNk/IiKbLZGvVsVQ++59tbComjzqaDoahmCvAJgxJO7yXyzb1M/RDmNa1gW
Qt4Au0r2S7l9V332oX/G32XHhwqdIoJfNsR//dQ2jOkP5gaUBRCV7EeHqoZm
RUp4XdIjAQiHR/reyrKDyG5sEpcHv9CrZj7bBm/mvqmiWmD04wyFD4EYOurY
Bny0+WBCUMAWQzfMfEre1vIwzhc//Pj+1SmICJHuYqqd2bVeh+N+5YLrQVmH
XOY35Yx5mSJLdE5fpKjydNO9UAADcdnxC0Ot3FxPxEhArD1RGDtKXF1+MaDf
r+b5HVRHGU9n41LNORClDsVcbBgLR2BtgXwNYkxzjepluNqDQCQCxHnYMOtv
6Rit7/He48efPyf4vXmTVm/5sLsOZhOAobsmqAaybAcRCZ3NqOwbd++yjLOT
DUhcHWw6sdrni0jmEdK0mP9O1rU12pbKGP3X3jU4Crtqh3CUcZa+MJLwIUnO
9oh/Rh/aThyFPQlfcnz7aAMczBxz5y+e//j69Ys3py9OvWO2KbJ0LsSaijoq
u4BezAqMixlH1qcd7S6jxBuTpmHSWAl5vS6C+8yVwXO+ET8p3apQH7HRXjZW
AT59Q/KCb/rskqyoRKwFiuHjt63hqfZaE5ffFljTsKJJpwpFbuJspzhaxoYH
NBgRUNaCM2o9Hq9kFdD0k2ayzuyUoeYtaMcsMszhkQ96QKSwJaCpbcgQSvC1
mSw9yLYFdZDgtUwSvCyjPYVmN98MVLdkVzZg432qfYofzw5B7x7FS/KOk1eb
t8Im6KAGIRQNLjUpAuxGFkmRON3H4zddq6e4vS46nSk5jYF7tZs/OA2/R9MX
H7+JdWZZietwa6k1kcZ9NiOfP2gsiU8mgl6N6HZr8116/GxNko+kSdJhLnIm
sI4S97mwtuNAyeH0Lsai9d1dPWOKeyYsFU0HQjNU7wPiUvSDeFAu9oQNA352
5IGJEt00v0t8a4IigoPUuvTEShpD1Ff7hh9UTcBqowI2DUq1EMbeVLZD9lTh
n9llyDv6YBsQpP9PDOo+v8uu5z8G23pNpk+ONbz7D2DoWJFQsD83dlXnpPkr
2S1jPgMGfDUlkcHKbZmbNG4UlHFP474LPE6q7XrIjIlQb6w9jj0ZLMgW2FQ6
jERCLhqf2ii/jUNTHlw/xdbPdAG+hK4PxpGyjVDgu7xLxh0wgDw7SWoWVQu2
sImWQUXvicggmUbKGfO4n8BqLb0/rEMFc72wvFW9wQX5JZw+q60Vo0gLXibf
r3xmcvD7BmXe7CQjko0moeq86VIlaCDqusCoFBM4J5ZZjE8hnS18J+ooiqOq
nIcH8baLudX6VilAkiByV7QW+NT03bq6Q3zfYowHu4jc7+8c7+79wTsWnvRc
x/vXtZtZ+zvHo6J2O/s7D3Yf4JGceOB293ohf+VeBsVPQu56eM7ukwd7DzCY
oUMCwyHaJ+FBQKERyovz1ripqGA0FKFnijQtoWV4Z4wr0TrCuEJqtu5O75gj
r2jQuNvzxnPj5Kxu4d+eKD1CncbQvR4NGmBj09H6PHjyZKBIabk00Uuwsoba
BZ1XXN2luQevs/y6Ddlxr2GERopz28bEG+JgSaZ+5bjuQW1Ba6tu8V6fJmDa
wZZeJshE5VPu2zVH8MYfabNgtzddUK4vGFNkNUQeFrKpRmxUGeixqMNOF27r
Pn+p25GUwwhmc+rYB22lrsl7myKxBZweu2RHYmCXBJW/dz4+HWNgO7sPcIJw
ftwSiTtAfrODZ5kTXzxGp+NXswbPcjs4QHKGsqWdoYSzblO+3S/yiF4cdek+
Rsfqudev4jg4E2+lSwvpgZrXEpeKsrtVEbDr0G54O1l7I0ooOhAaLvGpCz6b
b6DxQJwVARxJHpl1T4pAAlo5iPciG7SrtQxwsQqpnm4iE02H6Jfjwigl6ZYu
4ZFovuwFkAn//yOt6mK9WOS1zzxJ/cfvdaHecN6+CYt58bEnH61yYqCfvolB
uv8JJ7L3JR/fC0v79f/R+T3OkmYhuZ/OeaHhNEwi65NhPUgnt/STw1NG2Zuz
U80A2vjm4kK/8UxtKRnk/6JJqAYNTD3NQQKEXc8PCZD7Ogjnwjh5HqZ9/1br
KYv12048LHDS2pObdEEBHTGv/00n2j01UTnKv3auyUvSCY+4b5VYWsnn6Pc8
cG7z2qfZ3nf5/Go0rdrO17gFAVH98jdfu7BPv9nKRa94Km3h/tL7Qy/qPPIT
ffBvvRS5/6fffuo8lN9q0vzwp1GyIA6Fuajwu2V2E9kc9UTsDH77OW8r2/rX
TvwXAaXcP4QhFIM+RefDJTfEXyjixH/jUerUs//LV/bX1D+75JJoWVJPw3/j
6hi9/1ar85WVEveXCTi1XaLFChmH/S+nHIJQQzKyc/HV/nmjqr22Z34xZ/k3
PP6cPPGbHf2vyuZx/uv/RuqL2rn9VrP/FQ1Lf7t5+ibAv9Ekf70b+ksOaNd5
hpxK56KLk4/+WxUjc9r+ZmqRvQDK4D7NK8+++wsauBUfW3z3Ey3UwXeP8QVN
Xz7L6GK9dK+Pa/mP/wa9YXs7qH+5hOs0OtMOPDhD0lYrjW18ucOZ+4ruWo6/
Chz6+m5Fa/2VHbxc+L7zhK9r2MW43d1bv7qDlwvfp4/47SU5zuW/XHyHwz4q
m4o28z9FMI/IfPhJxDZ/8TS7Q94TiH9RLYH0PMKFd87x5/T9gQhT+ZYOl/yJ
Kq8s/Ons2fTRd32cIlo/qJvwSv7rD9SJ5JIOQ8UAB8HXvK5RBuq/bFnh/7AE
VqaPeH70rx+HXOr/fMqn7UEGC41+/hv//D3//E/+ecw/h/zzv3p6u04E69v7
Dl9lvf/RixQDIU8dCGlA2Xc6IhdRbvx1tCO0v6D2oEPdc53unLNPwlUPkE8r
X9CnWJOafZQPsvVqJb/Lt7hYbqPvmE4grJYw2afOhRufZt9+fLg7enRinOhY
njrib08unp+dZXMUP6GqJh/9TKPyb+KbD3ZHh9HN/OXWm09G/4dulqFkvL7f
ftzfGe0/CTcjMMYBKfRColt2Rk/oFh21bMm3vWzvhxf/QY9xTv6lT21+PJqD
h/wbTerhQ3rmNelx0fOGJ6OXw3x0Rc8V+pHHjpgI/i///B3/fMo/+/xz4F1c
iA29NSg6cJHUdXniS9e+3j9pWbV35t5P3DOdlFoAAQVs9X+mr7Bz75ecmrPp
jRx2u9tkKdJeVc9Iuv3MfzrG19WoqJQ2pBPA3vky0CgtUIIB78/fBKSapPag
0tYI0Si6rcJLab6CMLkfQpIxOpm8e3XKTaIsAEF/v8n676qVgtGfSp9c7N4A
HRrwbfyZT0KJ59wMOl26pKKb4/Wa57ne6tETj1mnNnalDAupmFXTjJzNWOrd
LF7XJsnrwBH4Y/Rk2pVzLkCpc+4RukmPv5I4TpCPuX3ph9ziGSSh2KeMESSZ
cs3kukCJGFcCRD2r7xsr5w/Ha2sBNuDDcBjDCTagz1FIBbhgL1lBUn/TZWnE
JdHKjTK95NWWfcaFIUz13k/jGJDUDHO0LPr0iV6GDR1J5Q/37kJlEudI5Stp
6dGduQu7JCgAvsfIaaEU/OIjcVDujJMEFlvGx555cFZxjW8cNRpDlFwkMRzS
JKeCvouZuXzTs9sNWVZJpE465Qp0gCxOZoUil/Vxk1fjVb6eVwBnoL9RJdyM
Z/TCsukZ0poWSSnOo2Y8GNY9ZsKEGpq+eTerIGbmMwVORzZL1MtrK31KkVmS
tBt/7fT8aX5wROe4495DFSgyiyjSbRYrr+qSI10BiGUTFZQzeQSBUAvB1Mk1
SJzZCmRlMWNfhtkBZ6SHWH71NtpNiDykQIapceWYT+7dckpma8CCYs6uAwEe
ZdkPo5ozj9YaAZW7aLuSY0cvkRXd4sHnY8B5kM6yZhrSMYAHxLkrxpFFBy2X
kikErMy5JkzlN1U59RmAUuwGlF99VhycrjiqKoAGulUGEMdLVXJw0jf9ADq7
LzTj8G5U7c7b20iVgZSfR40RXICU4tVeS6kgOMaoXI443yCVMCE11jig1Kzm
C034mAGFU+gQTJebJ3Dq8AI5gblk8zfEm5etgL+N8luUzyYt1sKWYiGIVNCb
pLIGMb94GLSfHgSvddlLGlM1ocigU5ph5XxbsGwcF2SRJotm4nceKRYBc2aO
8dGGVHxZLgO2XRgxJ35MIfNJ9mPcavFG49b0Oheo3Uv/iDCTBoJpaoOjHbPx
CbISP5PBjrm7a7KCnD7AIXSFP+VHaOOwOL/LBrHRG5WTTTbi7JLfLBUuMjGe
O5c0WHl+ADlF7D/BUEcYgokn7jnTxaCcJMmHLGPu7YUYrRG9j7jjDRO7h8+T
UtIoy3YhObhcU5uiQwQpoZDLlaZICMFi+6PGQ++9/nRfhdhZVM9vBQqdwDzO
0AY6sdsapu0mB27uV5SQfg8ztLraiOD8Yw34r9vvQfDRK0muTCCgfD90f2Y+
fbI0lc+fmSRd2im+v1VGbZdOOjyUuOgLLr8sQ9EZQbN0OCNK8Gim/JHTvBg5
W9xk7I0WcvA2yvm5Vzqzvsmp+lOFrfAsxmtLchhojKJiCgkJPBN69kUvl11g
sSgZSoLUTlII3KnQZHKcviAZxqIzb21skRByEHeafolK8UXRKsBiyP4JKkBs
CuDMqruMXsNVPL74ncbtYpj30CZBQjVqcgwVvtssNlaEW2lviX01Iamev5gq
hgGobCkVeINhdrku59NGxD8NM8rvG0eHkNNoJ9fcOAyzIEuBoZGzfIaz22rC
VZvPq9ma0/usmoZz//QQ8K6l5/wtHPkNIzACdZ9VJRFoX2f0qDIaPQWsNWIN
U+7L0lhSO+k1eYKj4xLgPKkVVuQcHOapgbIzcxNCnlUhU4oYqxO7SdMEvRYS
bTuLrHSIYN21phg1YdFD5p+tGY6SaLux3oFLnr8575InTru+H1ymvS62GKLb
+N+xlQdqFVPKJGM3ga7jZd6UTeAoy9mIu1Wy0e46BnZlYHrCNfsqEtmcF7Pd
JyYGZiq4Hh7u6j79M6qOUncCYmySn0cHEjmQ5XLNVbE4tyXKDIdeLIoEl51p
kmvUyvFNhrOExUWzMj4qVTTljYgQFPHOYK+JIbMFv6ms460ReECR+5EmqrgH
aevq7U2Mu4bCu1DQKZWh97G0VDYz55a3ah0lZ9ly61yU1urqkqgSIaN56tGa
awqx8RNbO+0WzNX04qYdZ2+l0ZCiooSGaJOEEQxdpIVMuQGO8VcpNE416FQi
szZCb17P27RGmZj2tdZQh9l3duoqrpMhW++mmDfxvnsEHAUhsg6g0IKRhi0Y
xyr5YdInIi1futRSsW5dd9aC4LqcXTPWZFPW0kFZ5S+scWS0Xt5p5iqNHYsG
oQyxCAgnJig1eyL0rISiQ95rzOyCj0LELEqAYyaJa1XRZOmPJm8My3nHeJ78
Qlhp+WWlj4qxQbE063kjVHrWsa7tmZk9k/aM0Rx5v7kguZnQdwCLzZczMDlf
GeFdnFMY06rHKfVybyYxlf8uuepslm7Z7/bL4iSYxHSAeSg0i/MCZUWF9m8J
/OI89ON9K+6SX5H5KgxIm1ZlJ+jiBnjGyH92wRr8VzoH5XFt3nwI9YV+dPBh
ltpplFf/yjNWqYyBmIusGvUVe2dOAOmR5qwmJc5YhSnacZY9k4LVGkVYfLvY
H/pCZSOxDqlUXJezqobFDndiseR6DD4LBba/EMcKiZtFySiv1uvi9M3FcJtN
4HyvYEM3iFkX9tMmh24qGdwFhfDscrlat/ChGA451+xBJhs2MtxwqHtNOpKL
BewiTBPNf6sW/EHxkZH05cC5CPJW6Jq+bsabqAi+7zHztSYFui4WKNEseRfy
7IoWgBk9d96sLuHh9A16p+y4NIAfsQhRicuYkBrXxVZExId+0KIG3FbAEp8y
uDDZnkHnPIJJeQ0hwOuWNECmjUm89ErFAnSRu8CyNslT14RFFG3W+/NXjY92
CIx36/R8JrS50JEY22ZCMNSdOXd2sa64WoYWMKe8dqHKNq0qFId1EzWpV28Z
reWEVsxstfOXz/cPdg6Qo69u8ZZBQJS8sA5vTt6+O3ckJdFQyJ1sO5E4GKZM
dE+t2DXwr6oL08X9Hud3I9F9ucpNaks70utUHuy1mU2sST4kKtXWS6kXzuHr
sf7kZrdFqpp6hoOUKesvjJqh+IQqmQLq4OLQsqmtQS4ovzw4r29b98ziI9u2
2sR+WU7GZev64vUv6b2fPw9kISua1s9R1bdQbDTSPhf+5nPQFcCQ6NHjdb0c
5/Uq7w01kCDbfIinMrgVm/Pmjy9ii97l0+tCylTuiUGE6hOvKyvW1GXNYABu
U7kxI5fDEERT8XFTUsMDAWrJNcquQ01z85LatDU4p05/X4DIiJkCa1/HOWa8
7fQ+soG0QJcU6LKDMsewBApNqE6yI56SdAOWPkE41Ld5PW2MikgMywbZrdgA
0nHyaTUmhW98KQ3/XpUfCjSPt3aVcdvhTYDSTrAhoKh5b3A6QgNxMsnJpGuu
tbB8RExOKRC7oKzUnrg5cJ6Yzr9am6/ORdRniyGeCuHXzYb55YGF1NYL0+F6
5qZclBAJt/mdVZXex02IfSjVPUgsLLRgV9V3c4E0gFTNq97AxdvnVybaQF2H
vBrxHfEesucTC2eLIYfRYwFzGntchQWKCgInxsL4dmQ5ByGfhe12M4e4il5w
H1W7Ee5Cj8QWvn/3cvRYjEm2yjAqZtFDFRaNKJJEnRwuQRAqIBiu1ss73BsD
SzKTOHz8ZPfzZzpSDLbWaPUppmL8/929Ohl6fWmbAAhdD0pBo0MH8HkxnYlc
dn02nZpQlup9MlxFZyYmt5MPfIJtAi+Bq6v2Vj1rPDQeZPqeAAz43J7faCta
G//9aimcGaZDefdIuZRQykSgCtVguGLAKIbDVUQP3yt86OS2WBuzh7Rp+W8T
NF4FtDQB76SRybrh3rcSfUJvyXU5b4MChlrjuBeBdSDn7ntsnYRx8otkDqby
qa5XWiW8tUbw7mQ6w7TZvkkES2EI2uF9hmPY1aFXx1zucWfyOdfLXgooLvq/
zWaMusX+/FKBveaAQmYKh5lJuqAoiiL3fYtgT44q1TXw6isLY7efRM9FtouW
Ky1jrHcWR96cB9/A/lnyaYoekyaTdOI0FhZOkjQbDxfiJyuSSfFyNv26tqqN
7wYTLWrwCOSd6HqEc5CWiCo2jzOnHjM1G8q5GR3PiuscbtEvZ/8gEFY3iin1
//q6lt22sRi6v18heDYJoBhtMbtZuZ0HXCRp4aSY2cqPJJo6UiDLE7hfPzx8
XUpWumiBNo4s3ctLHh5Sh56wqJaWq5NylESQHdf/k/3EandlEYdeoV1OL4Jh
q54/O+pVauN+0gDsNnwBATBiOdd41fHqrP1RtgFi1M1/XO11j8Sqy+3zLqQT
lstT9Gqb2ngfL96SMXMd9Sjws9p0bXN6JgdBKKXKbrZar0FJ2yg43J53bUXQ
wB6jTGRYlNp02/qHz+ca1lNyTdiPrb3/kyKdYaWYWE92wdkodxWXPOx3j3CV
HXE+bTIDWdUKLSiqmmsccGyv4Fs/ABO9HJVt35CyhEoEBeQ7n0trXQy8MW4r
wR0qUAy+l3Bq9svcJIQJrQwHyuJpd5TWB7TZdC2O54WnlJpOJ8WTl4OZyAA0
dtWYKF/IrGcT6zOE4GWxPHZtYEQDA71UtVXVtd2KYm+1/01AR/F0JHcDt7zV
enq+gTzWZmZ3t51xjYQwiUYPmXrcqzXqAclXUG8bxN9NTrIXWR51u2xkLL80
cg1akD4eslewsx8TgsTsrGS6XHyqBwpLYWS1R0q/VCktlwDaQvKyyDYvdNPX
XRhTR4hc5mYKcxfGfpuOx+Etz4ZR6bw26x1GMEGYC5kLv7If5L3kl01KchAt
RLvciolmC8NY4RkZJ6aqDAguak45+Fv3bJv0E7fGcbVMzH7Snu1KJ2iAxOTC
Pg3edYtzCGdR6By/QpJFz0SgfPwYscjHHV08bMlf6Cj9ZX9Tqhm0V4xXH0Ke
zdaIFYkUv8wyiE6x82AUXaLzrvV5v62W5C+qR7Zo+mFad+0r4RxplaFPIkLu
yLgRjkelv7e7be0XhiUCqQQz0yZnWKqOI+6GHS3bRwhrzCbRDdso+WKRJWIO
b3xbFkxLSuY94RBszmdGb1uZiUKpBvIZdcHoxhjKl5VpLeHr5J/1L+cA0rF4
G95YPYzGsgjjak8ppWCm4ckSCNRK/zQehhANv9NRsmYQ+sm704sQCTCQRC5m
cbsYbQU0AUGaTG2J/gLzhdrhE4TUJ2mbM01YOnYvMqqv5wF92JIPc28O4H/j
C9YYEzmoqygcVEF35INZbkIr+6fAyZHRivrk+18pDxvCWBGyxbmUoYGR+4wZ
GSf1cnro3F21Dw9nXZ1S6jL5QCb4jHthXK9Oy7gCuu35YvV1oSyli5JHqmnO
bxstb/Vqxft37/BXUcxm+c8k7TUfSKtNfyZLHgn+5p/hScCwMVGVt+XDZZFU
MXuSWxmwCVMGUChFyE1yRjm+AiixO0iLjeeZMpVuuiiiYzz9CkGxGE1h3KfS
fHfvfzi+8KiPjnPURACIQaY4Wk9FpITT6wj6U54g+AhQo3pnfHqD5OE/N9cm
KdfDwO4Wq3vK8q28xi0cO0nHMYbneFDdQY3lMgu7arzt6O+248j5F8H1lzSb
luuUTNi7Bxzcw5XN8KGljD1NGAi9WzYrpMcUElngyWtcxtuiY447j+juvy5v
+WwMFvmVj8RuzcwBFoOQspAj94QGP3bHjYaaXefj6g3jXPOtLgMnuVSo7bTr
p7ZrkN59a7i0i3WEPtjd5qnF/EfsmLws0GjjjMRiYHkl4aMFYC3R4Cho9Vj3
tHEpLr3OzAMg3HMaSOug3upBFEm76gEFq7gGsCuAJ510wiAJFnZDCJwS26b4
8lL/S5G4uPj9SMi1uNEpT3jGu+DH02cZ6SmvJrA6bbU/cjnLzA+2cR4ftCTv
i6BC9XL34eYFcAz69nLzwvMzQUBm0io6f3wFWin6T8oAij8+XS959c6/HOla
Bc1g0Qxq0+e2aovFfk2RCq0OxZc9bV3dVcV1jfcHoiaoEqEUQvang/HB6WNX
/ahhosWf2t0ukx1LOwuLvq/3FRlYtzmAOCgHMDaUDxCZ6YkrtDDncoP0+u+2
g1WVVSIYnniLz91HfqlDjwaTAFgG6NPWORNND1ENOLx6wBmjP8SqxQoVqxoY
ausUB5+JNH0mLn56Gi5LazcV8WyrfWQtttF52xxAPXCeWDAa2lOW18ME3ERS
5fm1vCWQ18U/mhd2ylyTpCUY4nWo9hFmPoMb7cV2HmE5xTVlxbR5tN1d19Ie
89soYZn3p7GN+67JwfT8KewbfeXV1RXB6M13iiH/AypYH+8GZwEA
</rfc> </rfc>
 End of changes. 417 change blocks. 
2345 lines changed or deleted 2775 lines changed or added

This html diff was produced by rfcdiff 1.48.