<?xml version='1.0' encoding='utf-8'?> encoding='UTF-8'?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.18 (Ruby 3.0.2) -->

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-spinosa-urn-lex-24" number="9676" updates="" obsoletes="" category="info" submissionType="independent" version="3"> tocInclude="true" version="3" xml:lang="en" symRefs="true" sortRefs="true">

  <front>
<!-- xml2rfc v2v3 conversion 3.22.0 [rfced] Title

a) May we update the document title in one of the following ways? The current
placement of "(LEX)" makes it seem like LEX is an abbreviation.

Current:
  A Uniform Resource Name (URN) Namespace for Sources of Law (LEX)

Perhaps:
  LEX: A Uniform Resource Name (URN) Namespace for Sources of Law

Or:
  "lex": A Uniform Resource Name (URN) Namespace for Sources of Law

b) Similarly, may we update the abbreviated title (appears in the running
header at the top of each page in the pdf output) in one of the following
ways?

Current:
  URN LEX Namespace for Sources of Law

Perhaps:
  LEX: URN Namespace for Sources of Law

Or:
  "lex": URN Namespace for Sources of Law
-->
  <front>
<title abbrev="URN LEX Namespace for Sources of Law">A Uniform Resource Name (URN) Namespace for Sources of Law (LEX)</title>
    <seriesInfo name="Internet-Draft" value="draft-spinosa-urn-lex-24"/> name="RFC" value="9676"/>
    <author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa">
      <organization/>
      <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>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">
      <organization/>
      <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>
    <date year="2024" month="August" day="17"/> month="November"/>

<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search. -->

<keyword>example</keyword>

    <abstract>
      <?line 154?>

<t>This
<!-- [rfced] Would including "LEX" or "lex" in the abstract be helpful to
readers?

Original:
   This document describes a Uniform Resource Name (URN) Namespace
   Identifier for identifying, naming, assigning, and managing
   persistent resources in the legal domain.

Perhaps:
   This document describes LEX, a Uniform Resource Name (URN) namespace
   identifier that identifies, names, assigns, and manages
   persistent resources in the legal domain.

Or:
   This document describes "lex", a Uniform Resource Name (URN) namespace
   identifier that identifies, names, assigns, and manages
   persistent resources in the legal domain.
-->
<t>This document describes a Uniform Resource Name (URN) namespace identifier
for identifying, naming, assigning, and managing persistent resources in the
legal domain.  This specification is published to allow allows adoption of a common
convention by multiple jurisdictions to facilitate ease of reference and
access to resources in the legal domain.<br/>
This domain.</t>
<t>This specification is an independent submission Independent
Submission to the RFC series. Series. It is not a standard, standard and does not have the
consensus of the IETF.</t>
    </abstract>
  </front>
  <middle>
    <?line 165?>
<section anchor="introduction">
      <name>Introduction</name>
      <section anchor="the-purpose-of-namespace-lex">
        <name>The Purpose
        <name>Purpose of Namespace "lex"</name> the "lex" Namespace</name>
        <t>The purpose of the "lex" namespace is to assign a unique identifier
        in a well-defined format to documents that are sources of law.
In this context, "sources of law" include any legal document within the domain
of legislation, case law and law, administrative acts acts, or regulations. Potential
sources of law (acts under the process of law formation, such as bills) are
included as well. "Legal doctrine", that is is, the body of knowledge and
theoretical speculation typical of legal scholars (e.g. (e.g., commentary on judgment,<br/>
judgment, jurisprudence review, commentary on legislation, encyclopedic
entries, monographs, articles in magazines, manuals, etc.) is explicitly not
covered.</t>
        <t>The identifier is conceived so that its construction depends only on
the content of the document itself and not its on-line online availability, its physical location, and access mode. The identifier itself is assigned
by the jurisdiction of the identified document.  Even a  A document that
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
more generally, any type of relation) among various sources of law.
In an on-line online environment with resources distributed among different
web publishers, lex URNs
allow a simplified global interconnection of legal documents by means
of automated resoluton. resolution.
LEX URNs consist of persistent and
location-independent identifiers and are particularly
useful when they can be mapped into or associated with locators such
as HTTP URLs. Moreover, LEX URNs URN details can be used as a reference
to create HTTP-based persistent and location-independent identifiers that are HTTP-based
<xref target="RFC3986"/>.</t>
      </section>
      <section anchor="background">
        <name>Background</name>
        <t>This specification of a unique identifier for legal documents
follows a number of initiatives in the field of legal document
management.</t>

<t>Since 2001 2001, the Italian Government, Government promoted the NormeInRete project
        through the National Center for Information Technology in the Public
        Administration, the Ministry of
Justice Justice, and CNR (the the National Research
        Council of Italy) promoted
the Italy (CNR). The NormeInRete project. It project was aimed at introducing standards for describing and identifying sources
        of law description and identification using XML and URN
        techniques.</t>
        <t>Other national initiatives in Europe introduced standards for the
description of legal sources <xref target="FRAN"/>.  Collaborations
between government, national research institutes, and
universities,
universities have defined national XML standards for legal document
management, as well as schemes for legal document identification.
Outside of Europe, similar initiatives have addressed similar problems
<xref target="FRAN"/>.
	Several of these identifiers are based on a URN schema.</t>
        <t>In

<!-- [rfced] Please review "legal information knowledge". Would simply "legal
information" be correct here? We note that "legal information" is used in
the sentence that follows.

Original:
   In today's information society the processes of political, social and
   economic integration of European Union member states as well as the
   increasing integration of the world-wide legal and economic processes
   are causing a growing interest in exchanging legal information
   knowledge at national and trans-national levels.

Perhaps:
   In today's information society, the processes of political, social
   and economic integration of European Union (EU) member states, as
   well as the increasing integration of the worldwide legal and
   economic processes, are causing a growing interest in the exchange of
   legal information at national and transnational levels.
-->

	<t>In today's information society, the processes of political, social, and
economic integration of European Union (EU) member states, as well as the
increasing integration of the worldwide legal and economic processes,
are causing a growing interest in the exchange of legal information
knowledge at national and transnational levels.
The growing desire for improved quality and accessibility of legal
information amplifies the need for interoperability among legal
information systems across national boundaries. A common common, well-defined
schema used to identify sources of law at an international level is an
essential prerequisite for interoperability.</t>
        <t>Interest groups within several countries have already expressed
        their intention to adopt a shared solution based on a URN technique.<br/> technique.

<!-- [rfced] FYI: We updated this long sentences as follows to improve
clarity. Let us know any concerns.

Original:
   The need for a unique identifier of sources of law in different EU
   Member States, based on open standards and able to provide advanced
   modalities of document hyper-linking, has been expressed in several
   conferences (as <xref target="LVI"/>) [LVI]) by representatives of the Publications Office
   of the European Union (OP), with the aim of promoting
   interoperability among national and European institution information
   systems.

Updated:
   In several conferences (such as [LVI]), representatives of the
   Publications Office of the European Union (OP) have expressed the
   need for a unique identifier for sources of law, based on open
   standards and able to provide advanced modalities of document
   hyperlinking, with the aim of promoting interoperability among
   national and European institution information systems.
-->

	In several conferences (such as <xref target="LVI"/>), representatives
	of the Publications Office of the European Union (OP) have expressed
	the need for a unique identifier for sources of law,
	based on open standards and able to provide advanced
	modalities of document hyperlinking, with the aim of promoting
	interoperability among national and European institution information
	systems.

Similar concerns have been raised by
        international groups concerned with free access to legal information,
        and the Permanent Bureau of the Hague Conference on Private
        International Law <xref target="HCPIL"/>
that encourage encourages State Parties
        to "adopt neutral methods of citation of their legal materials,
        including methods that are medium-neutral, provider-neutral and
        internationally consistent.". consistent".
In a similar
direction direction, the CEN Metalex
        initiative is moving, at the European level, towards the definition of a
        standard interchange format for sources of law, including
        recommendations for defining naming conventions to for them.</t>
        <t>The
        <t>Additionally, the need of for unique identifiers for sources of law is of
particular interest also in the domain of case law.
<!-- [rfced] We are having trouble parsing the following sentence. Please
clarify.

Original:
   This is acutely felt within both common law systems, where cases are
   the main law sources, and civil law systems, in order to provide an integrated
   access to cases and legislation, as well as to track the relationships between
   them.

Perhaps:
   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 provide
   integrated access to cases and legislation, as well as the ability to track the
   relationships between them.
-->
This is
acutely felt within both common law systems, where cases are the
main law sources, and civil law systems, in order to
provide an integrated access to cases and legislation, as well as
to track the relationships between them. This domain is characterized
by a high degree of fragmentation in case law information systems,
which usually lack interoperability.</t>
        <t>In the European Union, the community institutions have stressed the
need for citizens, businesses, lawyers, prosecutors prosecutors, and judges to
become more aware not only of (directly applicable) EU law, but laws and also
of
the various national legal systems.

<!-- [rfced] We are having trouble understanding the part of the first
sentence below starting with "in view of...". Also, is "In this view"
needed in the second sentence? Please review.

Original:
   Similarly the Council of the European Union has underlined the
   importance of cross-border access to national case law, as well as
   the need for its standardisation, in view of an integrated access in
   a decentralized architecture.  In this view the Working Party on
   Legal Data Processing (e-Law) of the Council of the European Union
   formed a task group to study the possibilities for improving cross-
   border access to national case law.

Perhaps:
   Similarly, the Council of the European Union has underlined the
   importance of cross-border access to national case law, as well as
   the need for its standardization, with a vision of a
   decentralized architecture with integrated access.
   The Working Party on
   Legal Data Processing (e-Law) of the Council of the European Union
   formed a task group to study the possibilities for improving cross-
   border access to national case law.
-->

The growing importance of
national judiciaries for the application of Community community law was
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/>
Similarly system.
Similarly, the Council of the European Union has underlined the
importance of cross-border access to national case law, as well as
the need for its standardisation, standardization, in view of an integrated access in
a decentralized architecture. In this view view, the Working Party on Legal
Data Processing (e-Law) of the Council of the European Union formed a
task group to study the possibilities for improving cross-border
access to national case law.
<!-- [rfced] FYI: We rephrased the following sentence to improve
readability. Please review and let us know any concerns.

Original:
   Taking notice of the report of the Working Party's task group, the
   Council of the EU decided in 2009 to elaborate on a uniform, European system
   for the identification of case law (ECLI: European Case-Law Identifier) and
   uniform Dublin Core-based set of metadata.</t> metadata.

Updated:
   Taking notice of the report of the
   Working Party's task group, in 2009, the Council of the European
   Union decided to elaborate on a uniform European system for the
   identification of case law (i.e., the European Case-Law Identifier
   (ECLI)) and a uniform set of metadata based on the Dublin Core.
-->
Taking notice of the report of the
Working Party's task group, in 2009, the Council of the European Union decided to
elaborate on a uniform European system for the identification of
case law (i.e., the European Case-Law Identifier (ECLI)) and a uniform set of metadata based on the Dublin Core.</t>
        <t>The Council of the European Union invited the Member States to
        introduce in the legal information systems the European Legislation Identifier (ELI), (ELI) in the legal
        information systems, which is an http-based http-based, Semantic Web oriented Web-oriented
        identification system for legislation of the European Union and Member States legislation.</t>
        <t>The States.</t>
<!-- [rfced] May we update "legislative" to "legislation", "legislative
document", or something similar?

Original:
   The LEX identifier (also referred in this text as "LEX name") is
   conceived to be general enough so as to provide guidance at the core
   of the standard and sufficient flexibility to cover a wide variety of
   needs for identifying all the legal documents of different nature,
   namely legislative, case-law and administrative acts.

Perhaps:
   The LEX identifier (also referred 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, legislation, case law, and administrative acts.
-->

        <t>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.

<!-- [rfced] Is "items" the correct word choice here? Would "version" or
something else be better in this context?

Original:
   Moreover, it can be effectively used within a federative environment
   where different publishers (public and private) can provide their own items of
   a legal document (that is there is more than one manifestation of the same
   legal document).

Perhaps:
   Moreover, the LEX identifier can be effectively used within a
   federative environment where different publishers (public and private) can
   provide their own versions of a legal document (that is, if there is more than
   one version of the same legal document).
-->
Moreover, it
can be effectively used within a federative environment where
different publishers (public and private) can provide their own items
of a legal document (that is, there is more than one manifestation of
the same legal document).</t>
        <t>Specifications and syntax rules of for the LEX identifier can also be used
also
for http-based naming convention conventions to cope with
different requirements in legal information management, for example example,
the need of having to have an identifier that is compliant with the Linked Open Data
principles.</t>
        <t>This document supplements the required name syntax with a naming
convention that interprets all these recommendations into an original
solution for sources of law identification.</t>
      </section>
      <section anchor="general-characteristics-of-the-system">
        <name>General Characteristics of the System</name>
        <t>The specifications in this document promote interoperability
among legal information systems by defining a namespace
convention and structure that will create and manage identifiers for
legal documents. The identifiers are intended to be:</t> have the following qualities:</t>
        <ul spacing="normal">
          <li>
            <t>globally unique</t>
          </li>
          <li>
            <t>transparent</t>
          </li>
          <li>
            <t>reversible</t>
          </li>
          <li>
            <t>persistent</t>
          </li>
          <li>
            <t>location-independent, and</t>
            <t>location-independent</t>
          </li>
          <li>
            <t>language-neutral.</t>
            <t>language-neutral</t>
          </li>
        </ul>
        <t>These qualities facilitate legal document management of legal documents and
a mechanism of for stable cross-collections cross-collection and cross-country
references.</t>
<t>Transparency means that that, for a given an act and its relevant metadata
(issuing authority, type of measure, etc.), it is possible to create
the
a related URN that is able to
uniquely identify the act in a way that is reversible
(from an act to its URN and from a
URN to the act).</t>
        <t>Language-neutrality,
        <t>Language neutrality, in particular, is an important feature that
promotes adoption of the standard by organizations that must adhere to
official-language
official language requirements. This specification provides
guidance to both public and private groups that create, promulgate,
and publish legal documents. Registrants wish to minimize the
potential for creating conflicting proprietary schemes, while
preserving sufficient flexibility to allow for diverse document types
and to respect the need for local control of collections by an
equally diverse assortment of administrative entities.</t>
        <t>The challenge is to provide the right amount guidance at the
core of the specification while providing sufficient flexibility to
cover a wide variety of needs. LEX does this by
splitting the identifier into parts.  The first part uses a
pre-existing
preexisting standard specification ("country/jurisdiction name
standard") to indicate the country (or more generally generally, the
jurisdiction) of origin for the legal document being identified; the
remainder ("local name") is intended for local use in identifying
documents issued in that country or jurisdiction.</t>
        <t>The second part depends only on the identification
        system for sources of law identification system operating in that nation nation, and it is mainly composed by
        formalized information related to the enacting authority, the type of
        measure, the details details, and possibly the annex.</t>
        <t>The identification system based on uniform names includes:</t>
        <ul spacing="normal">
          <li>
            <t>a
            <t>A schema for assigning names capable of representing unambiguously
            representing any addressed source of law (namely legislation, case law
            law, and administrative acts), acts) issued by any authority
            (intergovernmental, supranational, national, regional regional, and local)
            at any time (past,
present present, and future);</t> future).</t>
          </li>
          <li>
            <t>a
            <t>A resolution mechanism - -- in a distributed environment - -- that ties a
uniform name to the on-line online location of the corresponding
resource(s).</t>
          </li>
        </ul>
        <t>This document considers the first of these requirements. It also
contains a few references to the architecture of the resolution
service and to the corresponding software.</t>
      </section>
      <section anchor="linking-a-lex-name-to-a-document">
        <name>Linking a LEX Name to a Document</name>
        <t>The

<!-- [rfced] Is "meta-information" correct here? Or should this be updated to
"metadata"?

Original:
   The LEX name is linked to the document through meta-information which
   may be specified as follows:

Perhaps:
   The LEX name is linked to the document through metadata, which
   may be specified as follows:
-->

        <t>The LEX name is linked to the document through meta-information, which
may be specified as follows:</t>
<!-- [rfced] FYI: We do not see "META" (all caps) in [W3C.HTML]. We have
updated to "meta" (all lowercase). Please let us know any concerns.

Original:
   *  within the document itself through a specific element within an
   XML schema or by an [W3C.HTML] META tag;

Updated:
   *  Within the document itself through a specific element within an
      XML schema or by a meta tag [W3C.HTML].
-->

<ul spacing="normal">
          <li>
            <t>within
            <t>Within the document itself through a specific element within
an XML schema or by an a meta tag <xref target="W3C.HTML"/> META tag;</t> target="W3C.HTML"/>.</t>
          </li>
          <li>
            <t>externally
            <t>Externally by means of a Resource Description Framework <xref target="W3C.rdf-schema"/> target="W3C.RDF-SCHEMA"/>
triple, a specific attribute in a database, etc.</t>
          </li>
        </ul>
        <t>At least one of these references is necessary to enable automated
construction and
construction, an update of catalogues (distributed and centralized) centralized),
and the implementation of resolvers that associate the uniform name
of a document with its physical location(s). location. LEX assumes no
particular relationship between the originator of the document, its
publisher, and the implementer of catalogues catalogues, or resolution services.</t>
      </section>
      <section anchor="use-of-lex-names-in-references">
        <name>Use of LEX Names in References</name>
        <t>LEX names can be used in references as an HREF attribute value of the
hypertext link to the referred document.
This link can be created in two ways:</t>
        <ul spacing="normal">
          <li>
            <t>by manually
<t>Manually inserting in the referring document the link with the
uniform name: this name in the referring document. This is a burdensome procedure, especially for
documents that are already on-line;</t> online.</t>
          </li>
          <li>
            <t>by
<!-- [rfced] Please clarify "through reference parsers of a text".

Original:
   *  by automatically constructing (either permanently or temporarily)
      the link with the uniform name, through reference parsers of a
      text: this is a more time-saving procedure even if subject to a
      certain percentage of errors, since references are not always
      accurate or complete.

Perhaps:
   *  Automatically constructing (either permanently or temporarily) 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
      accurate or complete.
-->

            <t>Automatically constructing (either permanently or temporarily)
the link with the uniform name through reference parsers of a
text.
This procedure offers more time savings, even if it is subject to a
certain percentage of errors, since references are not always
accurate or complete. Nevertheless, this solution could nevertheless be
acceptable for already published already-published documents.</t>
          </li>
        </ul>
        <t>Whatever

        <t>No matter which method is adopted, new documents produced
in whatever a certain format (for example example, XML, XHTML, etc) etc.)
should express references through the uniform name
of the document referred to.</t>
      </section>
      <section anchor="definitions">
        <name>Definitions</name>
        <t>The following terms are used in
these specifications:</t>
        <ul this document:
	</t>
        <dl spacing="normal">
          <li>
            <t>Source
            <dt>Source of Law:
a Law:</dt><dd>
A general concept to refer that refers to legislation, case
law, regulations regulations, and administrative acts. In its broadest sense,
the source of law is anything that can be conceived as the
originator of 'erga omnes' legal rules. In this document "Source document, "source of
Law" refers
law" also refers to acts during their making creation, such as bills bills, that
might or might not become laws;</t>
          </li>
          <li>
            <t>Jurisdictional Registrar:
an laws.</dd>
            <dt>Jurisdictional Registrar:</dt><dd>
An organization in any
jurisdiction that shares and defines in any
jurisdiction the assignment of the main components of the resource
identifier through which the identifier uniqueness is guaranteed.</t>
          </li>
        </ul> guaranteed.</dd>
        </dl>
      </section>
      <section anchor="terminology">
        <name>Terminology</name>
        <t>The
        <t>
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
    "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and
"OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are to be
    interpreted as described in BCP
14 BCP&nbsp;14 <xref target="RFC2119"/> <xref
    target="RFC8174"/> when, and only when, they appear in all capitals, as
    shown here.</t> here.
        </t>

      </section>
      <section anchor="syntax-used-in-this-document">
        <name>Syntax Used in this This Document</name>
        <t>This document uses the a syntax common to many Internet RFCs, which that is based on the ABNF (Augmented Augmented
        Backus-Naur Form) Form (ABNF) <xref target="RFC5234"/> meta-
language.</t> meta-language, which
        is used in many RFCs.</t>
      </section>
      <section anchor="namespace-registration">
        <name>Namespace Registration</name>
        <t>The "lex" namespace has already been registered in the "Formal URN
Namespaces" registry.</t> registry. See <xref target="iana"/>.</t>
      </section>
    </section>
    <section anchor="registration-of-lex">
      <name>Registration of LEX</name>
      <section anchor="identifier-structure">
        <name>Identifier Structure</name>
        <t>The identifier has a the following hierarchical structure as follows:</t>
        <artwork><![CDATA[ structure:</t>

        <sourcecode><![CDATA[
   "urn:lex:" NSS
]]></artwork>
]]></sourcecode>
        <t>where NSS is the Namespace Specific String composed as follows:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
   NSS = jurisdiction ":" local-name
]]></artwork>
]]></sourcecode>
        <t>where:</t>
        <ul

<dl newline="false" spacing="normal">
          <li>
            <t>jurisdiction
identifies
            <dt>jurisdiction:</dt><dd>
Identifies the scope (state, regional,
municipal, supranational supranational, or of an organization) organizational) where a set of
sources of law have validity. It is also possible to represent
international organizations (either states or states, public
administrations
administrations, or private entities);</t>
          </li>
          <li>
            <t>local-name is the entities).</dd>

            <dt>local-name:</dt><dd>The uniform name of the source of law in the
            country or jurisdiction where it is issued; its internal structure
            is common to the already adopted already-adopted schemas.
It
represents all aspects of an intellectual production,
from its initial idea, through its
evolution during the time, to its realisation realization by different
means (paper, digital, etc.).</t>
          </li>
        </ul> etc.).</dd>
        </dl>
        <t>The jurisdiction element is composed of two specific fields:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
   jurisdiction = jurisdiction-code *(";" jurisdiction-unit)
]]></artwork>
]]></sourcecode>
        <t>where:</t>
        <ul

<dl newline="false" spacing="normal">
          <li>
            <t>jurisdiction-code is usually
            <dt>jurisdiction-code:</dt><dd><t>Usually the identification code of the
            country where the source of law is issued.<br/> issued.  To facilitate the
            transparency of the name, the jurisdiction-code
follows usually follows
            the rules of identification of other Internet applications, based
            on domain name (for details and special cases cases, see <xref target="jur-cod-regist"/>).<br/>
Due
            target="jur-cod-regist"/>).</t>
	    <t>Due to the differences in representation in the various
	    languages of a country,
for an easier identification of the country the use of the standard <xref target="ISO3166-1"/> target="ISO.3166-1"/> is
	    strongly RECOMMENDED.<br/>
Therefore <bcp14>RECOMMENDED</bcp14> for easier identification
	    of the country.  Therefore, a urn-lex ID always begins with a
	    sequence of ASCII characters: "urn:lex:ccTLD". For all the other
	    components that follow the jurisdiction-code, the Jurisdictional
	    Registrar decides the mode of representation (ASCII or UTF-8 %-encoding) (see
	    percent-encoding; see <xref target="non-ascii-char"/>).<br/>
Where target="non-ascii-char"/>).</t>
<t>Where applicable, the domain name of the country or multinational or
international organisation organization is used.<br/> used.  If such information is not available for
a particular institution, a specific code will be defined (see <xref
target="jur-cod-regist"/>).  Examples reported in this document are
hypothetical and assume that the corresponding domain name is used for the
jurisdiction-code.</t>
          </li>
          <li>
            <t>jurisdiction-unit are
          </dd>
<!-- [rfced] Would it be helpful to rephrase this sentence as follows?

Original:
   Therefore acts of
   the same type issued by similar authorities in different areas
   differ for the jurisdiction-unit specification.

Perhaps:
   Therefore, the jurisdiction-unit differs for acts of
   the same type issued by similar authorities in different areas.
-->

          <dt>jurisdiction-unit</dt><dd><t>The possible administrative hierarchical
sub-structures defined by each country or organisation organization within their
specific legal system.
This additional information can be used in
case when two or more levels of legislative or judicial production exist
(e.g., federal, state state, and municipality level) and the same bodies may
be present in each jurisdiction. Therefore Therefore, acts of the same type
issued by similar authorities in different areas differ for the
jurisdiction-unit specification.<br/>
An example can be the following:<br/> specification.</t>
<t>The following is an example:</t>

<artwork>
"br:governo:decreto" (decree of federal government),<br/> government)
"br;sao.paulo:governo:decreto" (decree of SU+00E3o Paulo state) <br/>
"br;sao.paulo;campinas:governo:decreto" (decree of Campinas <br/>
municipality).</t>
          </li>
        </ul>
        <t>Fictitious
municipality)</artwork>
          </dd>
        </dl>
        <t>The following are fictitious examples of sources of law identifiers are:</t> identifiers:</t>
        <artwork><![CDATA[
urn:lex:it:stato:legge:2003-09-21;456
    (Italian act)
urn:lex:fr:etat:loi:2004-12-06;321
    (French act)
urn:lex:es:estado:ley:2002-07-12;123
    (Spanish act)
urn:lex:ch;glarus:regiere:erlass:2007-10-15;963
    (Glarus Swiss Canton decree)
urn:lex:eu:commission:directive:2010-03-09;2010-19-EU
    (EU Commission Directive)
urn:lex:us:supreme.court:decision:1978-04-28;77-5953
    (US SC decision: Riley vs Illinois)
urn:lex:be:conseil.etat:decision:2008-07-09;185.273
    (Decision of the Belgian Council of State)
]]></artwork>
      </section>
      <section anchor="jur-cod-regist">
        <name>Jurisdiction-code
        <name>Jurisdiction-Code Register</name>
        <t>A

<!-- [rfced] We have a few questions about the text below.

Original:
  2.2.  Jurisdiction-code Register

    A new jurisdiction-code registry has been created.  Each entry
    contains the following elements:

a) Should the title read "Jurisdiction-Code Registry" ("Registry" rather than
"Register")?

b) Is "jurisdiction-code" the name of the registry? If so, we will enclose in
quotation marks.

c) Would it be helpful to include a citation or URL so readers can access the
new jurisdiction-code registry?
-->

        <t>A new jurisdiction-code registry has been created. Note that this
        is a CNR registry and <strong>not</strong> an IANA registry.</t>
	<t>Each
        entry contains the following elements:</t>
        <ul
        <dl spacing="normal">
          <li>
            <t>jurisdiction-code:
            <dt>jurisdiction-code:</dt><dd>The identifier of jurisdiction assigned
to the country or organization.</dd>
<!-- [rfced] How may we update these definitions for clarity?

a) jurisdiction-code definition

Original:
   *  jurisdiction-code: the identifier of jurisdiction, assigned to the
   country or organisation;</t>
          </li>
          <li>
            <t>jurisdiction: organisation;

Perhaps:
   jurisdiction-code:  The identifier assigned to the jurisdiction (i.e., identifier
   assigned to the country or organization).

b) jurisdiction definition

Original:
   *  jurisdiction: the official name of the jurisdiction, country or organisation;</t>
          </li>
          <li>
            <t>registrant: essential
   organisation;

Perhaps:
   jurisdiction:  The official name of the jurisdiction (i.e., the country or
   organization).

Or:
   jurisdiction:  The official name of the country or
   organization.
-->

<dt>jurisdiction:</dt><dd>The official name of the jurisdiction,
country or organization.</dd>
            <dt>registrant:</dt><dd>Essential information to identify that identifies the organization
that requested the registration of the code. The registrant will
be responsible for its DNS zone and for zone, the attribution of sub-zone
delegations, and so on. It is RECOMMENDED <bcp14>RECOMMENDED</bcp14> that each jurisdiction
create a registry of all delegated levels so that the organization
responsible of for each sub-zone can easily be identified;</t>
          </li>
          <li>
            <t>reference: a identified.</dd>
            <dt>reference:</dt><dd>A reference to the defining document (if any).</t>
          </li>
        </ul> any).</dd>
        </dl>
        <t>The table registry is initially empty. Possible The following are possible example entries are:</t> entries:</t>
        <artwork><![CDATA[
"br"; "Brazil"; "Prodasen, Federal Senate, address, contact";
      \[reference\]
"eu"; "European Union"; "DG Digit, European Commission, address,
      contact"; \[reference\]
"un.org"; "United Nations"; "DPI, United Nations, address,
          contact"; \[reference\]
]]></artwork>
        <t>Note that this is a CNR registry and <strong>not</strong> an IANA registry.</t>
        <t>CNR is responsible for the
jurisdiction-code and the root lex-nameserver.nic.it registries of the resolution
routing.</t>
        <t>A

<!-- [rfced] Would including either a URL or a citation with a corresponding
reference entry for "CNR website dedicated to the LEX governance" be
helpful to readers here? If so, please provide the necessary information.

Original:
   A new Jurisdictional Registrar will contact CNR or the Designated
   Expert(s) according to the established rules of governance (published
   in the CNR website dedicated to the LEX governance).
-->

<t>A new Jurisdictional Registrar will contact CNR or the designated
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
authoritativeness and the offered guarantees.  The Designated
Expert(s) designated
expert(s) will evaluate such applications, applications with a similar approach as
evaluations of the DNS. Typically Typically, such applications should come from public
administrations, as authorities enacting sources of law.</t>
        <t>The adopted registration policy is similar to that of the "Expert Review"
as
policy specified in <xref target="RFC8126"/>. Designated Experts The designated expert(s) will assign
jurisdiction codes based on the following principles:</t>
        <ul spacing="normal">
          <li>
            <t>If a request comes from a jurisdiction that corresponds to a
country and the jurisdiction code is the same as a top level ccTLD, top-level Country Code Top-Level Domain (ccTLD),
then the top level top-level ccTLD should be
used as the jurisdiction code;</t> code.</t>
          </li>
          <li>
            <t>If a request comes from a jurisdiction that corresponds to a
            multi-national organization (e.g., European Union) or international organization (e.g.,
            United
Nations, Nations and World Trade Organization) organizations Organization), the Top Level
            Top-Level Domain Name (e.g., "eu") or the Domain Name (e.g., "un.org",
            "un.org" and "wto.org") of the organization should be used as the
            jurisdiction
code;</t> code.</t>
          </li>
          <li>
            <t>in case when such
            <t>If a multi-national or international organization does
not have a registered domain, Designated Expert(s) the designated expert(s) should assign
something like name.lex.arpa, "name.lex.arpa", where the name will be the
acronym of the organization name, name in the language chosen by the organization itself.
For example, the jurisdiction code of the European Economic Community
could be "eec.lex.arpa".
Anyway the The alias mechanism allows to have for acronyms in different languages.</t>
          </li>
        </ul>

        <t>Jurisdiction codes MUST NOT <bcp14>MUST NOT</bcp14> be renamed, because that
would violate rules the rule that URN assignments are be persistent.</t>
        <t>Jurisdiction codes MUST NOT <bcp14>MUST NOT</bcp14> ever be deleted. They can only be marked as
"obsolete", i.e. i.e., closed for new assignments within the jurisdiction.
Requests to obsolete a jurisdiction code are also processed by
Designated Expert(s).</t>
the designated expert(s).</t>
        <t>Designated Expert(s) expert(s) can unilaterally initiate allocation or
obsolescence of a jurisdiction code.</t>
        <t>Request
        <t>Requests for new jurisdiction code assignment assignments must include
the organization or country requesting it and Contact contact information (email)
of who requested the assignment.</t>
      </section>
      <section anchor="conformance-with-urn-syntax">
        <name>Conformance with URN Syntax</name>
        <t>The "lex" namespace identifier (NID) syntax conforms to
<xref target="RFC8141"/>. However, a series of characters are reserved to identify for identifying
elements or sub-elements, or for future extensions of the LEX naming
convention (see <xref target="res-chars"/>).</t>
      </section>
      <section anchor="validation-mechanism">
        <name>Validation Mechanism</name>
        <t>The Jurisdictional Registrar (or those it delegates) of each adhering
country or organization is responsible for the definition or
acceptance of the uniform name's primary elements (issuing authority
and type of legal measure).</t>
      </section>
      <section anchor="scope">
        <name>Scope</name>
        <t>Global
<!-- [rfced] How may we update "global interest" to form a complete sentence?
If the suggestion below does not accurately capture your intended
meaning, please feel free to provide updated text.

Original:
   Global interest.  In fact each body that enacts sources of law can
   identify them by this scheme.

Perhaps:
   The scope is global. In fact, each body that enacts
   sources of law can identify them by this scheme.
-->
        <t>Global interest.  In fact, each body that enacts sources of law can
        identify them by this scheme.  Furthermore, other bodies (even not
enacting non-enacting sources of law, such as newspaper or newspapers, magazine publishers, etc.) aiming that aim to refer reference legal documents, documents can unequivocally identify them
        by this scheme.</t>
      </section>
    </section>
    <section anchor="general-syntax-and-features-of-the-lex-identifier">
      <name>General Syntax and Features of the LEX Identifier</name>
      <t>This section lists the general features applicable to all
jurisdictions.</t>
      <section anchor="allowed-and-not-allowed-characters">
        <name>Allowed and Not Allowed Characters</name>
        <t>These
        <t>The characters are defined in accordance with the <xref target="RFC8141"/>
"Uniform Resource Names (URNs)". target="RFC8141"/>.
For various reasons, later
explained, in the "lex" NSS reasons that are
explained later, only a subset of characters is
allowed.
allowed in the "lex" NSS. All other characters are either eliminated or converted.</t>
        <t>For the full syntax of the uniform names in the "lex" space, please
see <xref target="urn-lex-syn"/>.</t>
      </section>
      <section anchor="res-chars">
        <name>Reserved Characters</name>

        <t>The following characters are reserved in the specific "lex"
namespace:</t>
        <artwork><![CDATA[
"@" separator
<dl indent="6">
<dt>"@"</dt><dd>Separator of the expression, expression that contains information on
    version and language;
"$" separator language.</dd>
<dt>"$"</dt><dd>Separator of the manifestation, manifestation that contains information on
    format, editor, etc.;
":" separator etc.</dd>
<dt>":"</dt><dd>Separator of the main elements of the name at any entity;
";" separator entity.</dd>
<dt>";"</dt><dd>Separator of the level. It identifies the introduction of an element
    at a hierarchically lower level, level or the introduction of a
    specification;
"+" separator
    specification.</dd>
<dt>"+"</dt><dd>Separator of the repetitions of an entire main element (e.g.,
    multiple authorities);
"|" separator authorities).</dd>
<dt>"|"</dt><dd>Separator between different formats of the same element (e.g.,
    date);
"," separator
    date).</dd>
<dt>","</dt><dd>Separator of the repetitions of individual components in the main
    elements, each bearing the same level of specificity (e.g.,
    multiple numbers);
"~" separator numbers).</dd>
<dt>"~"</dt><dd>Separator of the partition identifier in references (e.g.,
    paragraph of an article);
"*" and "!" are reserved article).</dd>
<dt>"*"</dt><dd>Reserved for future expansions.
]]></artwork> expansions.</dd>
<dt>"!"</dt><dd>Reserved for future expansions.</dd>
</dl>
        <t>To keep backward compatibility with existing applications in some
jurisdictions, the "lex" NID syntax does not include the use of the
character "/" in this version.<br/> version. This character is always converted into
"-", except in the formal annexes (see <xref target="annex-formal"/>).</t>
      </section>
      <section anchor="case-sensitivity">
        <name>Case Sensitivity</name>
        <t>For all the languages where different cases (upper (uppercase or lower cases) lowercase)
        or different spelling spellings of the same word are possible, names belonging
        to "lex" namespace are case-insensitive.
It is RECOMMENDED that, in latin  For the Latin alphabet, they it is
        <bcp14>RECOMMENDED</bcp14> that names be created in
        lower case, but names that differ only in case, case or in the spelling, spelling of
        the same word
MUST <bcp14>MUST</bcp14> be considered to be equivalent<br/> equivalent
        (e.g., "Ministry" will be recorded as "ministry").</t>
      </section>
      <section anchor="non-ascii-char">
        <name>Unicode Characters outside Outside the ASCII Range</name>

        <t>In order to exploit the DNS as a routing tool towards the proper
resolution system, to keep editing and communication more simple simple, and
to avoid character percent-encoding, it is RECOMMENDED <bcp14>RECOMMENDED</bcp14> that the characters outside the ASCII range
(e.g.
(e.g., national characters, diacritic signs, ...) are turned into etc.) be replaced by base ASCII
characters (e.g.,
characters. For example, the Italian term "sanitU+00E0" can be replaced into by
"sanita", the French term "ministU+00E8re" can be replaced into
"ministere"), in case by transliteration (e.g.
"ministere", and "MU+00FCnchen"
can be replaced into "muenchen").</t> by "muenchen" (transliteration).</t>
        <t>This mapping consists of:</t>

        <ul spacing="normal">
          <li>
            <t>transcription
            <t>Transcription from non-Latin alphabets;</t> alphabets</t>
          </li>
          <li>
            <t>transliteration
            <t>Transliteration of some signs (diaeresis, eszett, ...);</t> (e.g., diaeresis and eszett)</t>
          </li>
          <li>
            <t>preservation
            <t>Preservation of the only the basic characters, eliminating the signs
placed above (accents, tilde, ...), (e.g., accents and tilde), below (cedilla, (e.g., cedilla and little tail,
...) tail), or on (oblique cut, ...).</t> (e.g., oblique cut)</t>
          </li>
        </ul>
        <t>The
<!-- [rfced] We are having trouble understanding "or, in agreement with this
one". Please clarify.

Original:
   The most suitable, well-known and widespread mapping system for a
   given language MUST be chosen by the jurisdiction, or, in agreement
   with this one, by the jurisdiction-unit in case of different
   languages in the various regions, also taking into account the
   choices made for the same language by other jurisdictions.<br/>
Certainly jurisdictions.

Perhaps:
   The most suitable, well-known, and widespread mapping system for a
   given language MUST be chosen by the jurisdiction or
   by the jurisdiction-unit (in agreement with the jurisdiction) in the case of different
   languages in various regions, also taking into account the
   choices made for the same language by other jurisdictions.
-->
<t>The most suitable, well-known, and widespread mapping system for a given language <bcp14>MUST</bcp14> be chosen by the
jurisdiction, or in agreement with this one, by the jurisdiction-unit in
case of different languages in various regions,
also taking into account the choices made for the same language by other jurisdictions.
This mapping is simpler and more feasible for languages that
use the Latin alphabet and gradually becomes more complex both for
other alphabets and for writing systems with that use opposite orientation
(from right to left) or are based on ideographic symbols.</t>
        <t>If this conversion is not acceptable by a specific jurisdiction or
        it is not available in a given language, UNICODE MUST Unicode <bcp14>MUST</bcp14>
        be used and, used, and for accessing network protocols, any UNICODE Unicode code points
        outside the ASCII range MUST <bcp14>MUST</bcp14> be converted in to UTF-8 %-encoding
        percent-encoding according to <xref target="RFC3986"/> and <xref target="RFC3629"/>.<br/>
        target="RFC3629"/> .</t>

<!-- [rfced] Should "as" be updated to "and" in "as some of its parts"?

Original:
   In this case it should be noted that the generated URN (as some of
   its parts) cannot be used directly for routing through DNS, and
   therefore the jurisdiction must adopt one of the following
   strategies:

Perhaps:
   In this case, it should be noted that the generated URN (and some of
   its parts) cannot be used directly for routing through the DNS.
   Therefore, the jurisdiction must adopt one of the following
   strategies:
-->
<t>In this case, it should be noted that the
        generated URN (as some of its parts) cannot be used directly for
        routing through the DNS. Therefore, the jurisdiction must adopt one of
        the following strategies:</t>
        <ul spacing="normal">
          <li>
            <t>to convert
            <t>Convert non-ASCII characters within the DNS into the IDN
encoding,
encoding using the Punycode translation <xref target="RFC5894"/> punycode translation (e.g. (e.g.,
mU+00FCnchen in xn--mnchen-3ya), xn--mnchen-3ya) and to develop a
software interface that converts the URN before the navigation in DNS, or</t> the DNS.</t>
          </li>
          <li>
            <t>to create
            <t>Create a routing service relying on a software, out outside of the DNS,
addressing
that addresses a proper resolution service.</t>
          </li>
        </ul>
        <t>Note that the urn:lex ID, ID could contain groups of characters (UTF-8 %-encoded) percent-encoded)
of some languages with different orientations: in orientations. In this case case, the BiDi rules apply <xref target="RFC5893"/>.</t>
        <t>Summarizing, the preference
        <t>The preferred order is summarized as follows:</t>
<!-- [rfced] Please clarify the text starting with "(for not having...".

Original:
   *  Conversion into basic ASCII, RECOMMENDED solution (for not having
      to make conversions for network protocols and DNS);

Perhaps:
   *  Conversion into basic ASCII is the RECOMMENDED solution (because
      conversions for network protocols and the following:</t> DNS are not needed).
-->

        <ul spacing="normal">
          <li>
            <t>Conversion into basic ASCII, RECOMMENDED ASCII is the <bcp14>RECOMMENDED</bcp14> solution (for not having to make conversions
for network protocols and DNS);</t> the DNS).</t>
          </li>
          <li>
            <t>Using UNICODE, Unicode and convert into converting to UTF-8 %-encoding percent-encoding <xref target="RFC3629"/>, target="RFC3629"/> for accessing network protocols, protocols
and to punycode Punycode <xref target="RFC5894"/>, target="RFC5894"/> only for navigation in DNS, DNS via software interface;</t> interface.</t>
          </li>
          <li>
            <t>Creation of a routing service relying on a software, out software outside of DNS, DNS
and addressing a proper resolution service.</t>
          </li>
        </ul>
        <t>The first solution allows native DNS routing, routing while the other two
solutions require software development for the interface or the routing.
However
However, it is up to the specific jurisdiction to choose the preferred
solution.</t>
        <t>Two
        <t>The following are two examples (Latin and Cyrillic alphabet) alphabets) relating to the different
solutions adopted are here reported:</t>
        <artwork><![CDATA[
a adopted:</t>

<ul spacing="normal">

<li><t>A circular adopted by the Municipality of Munich (Rundschreiben der
Stadt MU+00FCnchen):
- ascii = urn:lex:de:stadt.munchen:rundschreiben:...
- unicode = urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...
- utf-8 = urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben:...
- punycode = urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben:... MU+00FCnchen):</t>

<ul spacing="normal">

<li><t>ASCII:</t>
<artwork><![CDATA[
urn:lex:de:stadt.munchen:rundschreiben: ...
]]></artwork>
</li>

<li><t>Unicode:</t>
<artwork><![CDATA[
a
urn:lex:de:stadt.mU+00FCnchen:rundschreiben: ...
]]></artwork>
</li>

<li><t>UTF-8:</t>
<artwork><![CDATA[
urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben: ...
]]></artwork>
</li>

<li><t>Punycode:</t>
<artwork><![CDATA[
urn:lex:de:stadt.xn--mnchen-3ya:rundschreiben: ...
]]></artwork>
</li>
</ul>
</li>

<li><t>A state law of the Russian Federation (latin: (Latin: gosudarstvo zakon;
  cyrillic:
Cyrillic: U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435
  U+0437U+0430U+043AU+043EU+043D):
- ascii = urn:lex:ru:gosudarstvo:zakon:...
- unicode =
U+0437U+0430U+043AU+043EU+043D):</t>

<ul spacing="normal">
<li><t>ASCII:</t>
<artwork><![CDATA[
urn:lex:ru:gosudarstvo:zakon: ...
]]></artwork>
</li>

<li><t>Unicode:</t>
<artwork><![CDATA[
urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D
            U+0438U+0435:U+0437U+0430U+043AU+043EU+043D:...
- utf-8 =
U+0438U+0435:U+0437U+0430U+043AU+043EU+043D: ...
]]></artwork>
</li>

<li><t>UTF-8:</t>
<artwork><![CDATA[
urn:lex:ru:%xD1%x81%xD0%xBE%xD1%x81%xD1%x82%xD0%xBE%xD1
%x8F%xD0%xBD%xD0%xB8%xD0%xB5:%xD0%xB7%xD0%xB0%xD0%xBA
          %xD0%xBE%xD0%xBD:...
- punycode = urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme:...

assuming
%xD0%xBE%xD0%xBD: ...
]]></artwork>
</li>

<li><t>Punycode:</t>
<artwork><![CDATA[
urn:lex:ru:xn--80aebe3cdmfdkg:xn--80ankme: ...
]]></artwork>
</li>
</ul>
</li>
</ul>

<aside><t>Note: The above assumes that the Russia jurisdiction-code is
expressed in ASCII ("ru"), while the Cyrillic version ("U+0440U+0444") has the
puny-code "xn--p1ai".
]]></artwork>
Punycode "xn--p1ai".</t>
</aside>

      </section>
      <section anchor="abbreviations">
        <name>Abbreviations</name>
        <t>Abbreviations are often used in law for indicating institutions (e.g. (e.g.,
Min.), structures (e.g. (e.g., Dept.), or legal measures (e.g. Reg.) (e.g., Reg.), but they are not
used in a uniform way, therefore way. Therefore, their expansion is highly RECOMMENDED<br/> <bcp14>RECOMMENDED</bcp14>
(e.g., "Min." is reported expanded as "ministry").</t>
      </section>
      <section anchor="dat-form">
        <name>Date Format</name>
        <t>The <xref
        <t><xref target="ISO.8601.1988"/> is describes the international format for representing dates:
therefore dates MUST dates. Dates <bcp14>MUST</bcp14> always be represented in this format (4 digits for the year,
2 digits for the month, and 2 digits for the day):</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
    date-iso = yyyy-mm-dd
]]></artwork>
        <t>(e.g.,
]]></sourcecode>
        <t>For example, "September 2, 99" will be written as "1999-09-02").</t> "1999-09-02".</t>
        <t>This format ensures interoperability between different
        representation systems systems, and there are several programs for mapping
        other formats to this one.<br/>
However, one.</t>

<t>However, to make facilitate reading and understanding such
        other formats (e.g. (e.g., Jewish calendar), the urn:lex scheme provides that allows
        for the date can to be added in the jurisdiction's own format<br/>
(e.g. format. For example, the
        date in the previous example would be 21.Elul,5759, that is:</t>
        <artwork><![CDATA[
- in

	<ul spacing="normal">
<li><t>In Hebrew characters:
  "U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.U+05EA
   U+05E9U+05E0U+05F4U+05D8";
- in UTF-8 code:
  "%x5c%x75%x30%x35%x44%x42%x5c%x75%x30%x35%x46%x34%x5c%x75%x30%x35 characters:</t>

<artwork><![CDATA[
 U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.U+05EA
 U+05E9U+05E0U+05F4U+05D8
]]></artwork>
</li>
<li><t>In UTF-8:</t>

<artwork><![CDATA[
 %x5c%x75%x30%x35%x44%x42%x5c%x75%x30%x35%x46%x34%x5c%x75%x30%x35
 %x44%x30%x2e%x5c%x75%x30%x35%x44%x30%x5c%x75%x30%x35%x42%x31%x5c
 %x75%x30%x35%x44%x43%x5c%x75%x30%x35%x44%x35%x5c%x75%x30%x35%x42
 %x43%x5c%x75%x30%x35%x44%x43%x2e%x5c%x75%x30%x35%x45%x41%x5c%x75
 %x30%x35%x45%x39%x5c%x75%x30%x35%x45%x30%x5c%x75%x30%x35%x46%x34
   %x5c%x75%x30%x35%x44%x38").
 %x5c%x75%x30%x35%x44%x38
]]></artwork>
</li>

</ul>

        <t>Therefore, for all the dates in the urn:lex identifier
(see Sections <xref target="det-elem"/> target="det-elem" format="counter"/> and <xref target="ide-vers"/>), target="ide-vers" format="counter"/>),
it is also possible to indicate the one date in the local format:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
    date = date-iso [ "|" date-loc ]
]]></artwork>
        <t>(e.g.,
]]></sourcecode>
        <t>For example, "September 2, 99" will be written in ISO plus format and Hebrew format as<br/>
"1999-09-02|U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.
U+05EAU+05E9U+05E0U+05F4U+05D8").</t> as follows:</t>
<artwork><![CDATA[
  1999-09-02|U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.
  U+05EAU+05E9U+05E0U+05F4U+05D8
]]></artwork>
        <t>The characters which that are not allowed (e.g. (e.g., "/") or which are reserved (e.g. (e.g., ",") cannot exist
inside the date-loc and therefore MUST <bcp14>MUST</bcp14> be turned into ".".</t>
      </section>
    </section>
    <section anchor="specific-syntax-and-features-of-the-lex-identifier">
      <name>Specific Syntax and Features of the LEX Identifier</name>
      <t>In this
      <t> This section there are other discusses features related to specific
jurisdictions and the
      jurisdictions. The implementation of which these features is RECOMMENDED.</t>
      <bcp14>RECOMMENDED</bcp14>.</t>
      <section anchor="spaces-connectives-and-punctuation-marks">
        <name>Spaces, Connectives Connectives, and Punctuation Marks</name>
        <t>All the
        <t>When explicitly present, all language connectives (e.g., articles, prepositions, etc.),
the punctuation marks marks, and all the special characters (as (e.g., apostrophes, dashes, etc.), when explicitly present, 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".<br/> space (e.g.,
        "Ministry of Finances, Budget Budget, and of Economic Planning" becomes "ministry.finances.budget.economic.planning";<br/>
        "ministry.finances.budget.economic.planning" and "Ministerstvo Finansov"
        becomes "ministerstvo.finansov")</t> "ministerstvo.finansov").</t>
      </section>
      <section anchor="acronyms">
        <name>Acronyms</name>
        <t>The use of acronyms might be confusing and encourage ambiguity in
uniform names (the same acronym may indicate two different
institutions or structures), therefore structures); therefore, their expansion is highly
RECOMMENDED<br/>
<bcp14>RECOMMENDED</bcp14>
(e.g., "FAO" is expanded as "food.agriculture.organization").</t>
      </section>
      <section anchor="ordinal-numbers">
        <name>Ordinal Numbers</name>
        <t>To

<!-- [rfced] Will readers understand what "To even the representation" means?

Original:
   To even the representation, it is highly RECOMMENDED that any ordinal
   number included in a component of a document name (e.g., in the
   description of an institution body) is indicated in Western Arabic
   numerals, regardless to the original expression: whether in Roman
   numerals, or with an adjective, or in Arabic numeral with apex, etc.
   (IV, third, 1U+00B0, 2^, etc.)<br/> etc.)
   (e.g., "Department IV" becomes "department.4").

Perhaps:
   To make the representation consistent, it is highly RECOMMENDED that any ordinal
   number included in a component of a document name (e.g., in the
   description of an institution body) is indicated in Western Arabic
   numerals, regardless the original expression, whether Roman
   numerals, an adjective, Arabic numerals with an apex, etc.
   (such as IV, third, 1U+00B0, and 2^).  For example, "Department IV"
   becomes "department.4".
-->

        <t>To even the representation, it is highly <bcp14>RECOMMENDED</bcp14> that any ordinal
number included in a component of a document name (e.g., in the
description of an institution body) is indicated in Western Arabic
numerals, regardless to the original expression, whether Roman
numerals, an adjective, Arabic numerals with an apex, etc.
(such as IV, third, 1U+00B0, and 2^). For example, "Department IV" becomes "department.4").</t> "department.4".</t>
      </section>
    </section>
    <section anchor="creation">
      <name>Creation of the Source of Law LEX Identifier - Identifier: Baseline structure</name> Structure</name>
      <section anchor="basic-principles">
        <name>Basic Principles</name>
        <t>The uniform name must identify one and only one document (more
precisely a "bibliographic resource" <xref target="ISBD"/>, target="ISBD"/>; see also <xref target="src-law"/>)
and is created in such a way that it is:</t>
        <ul spacing="normal">
          <li>
            <t>self-explanatory;</t>
            <t>self-explanatory,</t>
          </li>
          <li>
            <t>identifiable through simple and clear rules;</t> rules,</t>
          </li>
          <li>
            <t>compatible with the practice commonly used for references;</t> references,</t>
          </li>
          <li>
            <t>able to be created from references in the text, automatically (by
parser) or manually;</t> manually, and</t>
          </li>
          <li>
            <t>representative of both the formal and the substantive aspects of
the document.</t>
          </li>
        </ul>
      </section>
      <section anchor="src-law">
        <name>Model of Sources of Law Representation</name>
        <t>According to the <xref target="FRBR"/> (Functional Functional Requirements for Bibliographic
Records) Records
        (FRBR) <xref target="FRBR"/> model developed by IFLA (International
        Federation of Library Associations and Institutions), four
        fundamental entities (or aspects) can be specified in a source of law,
        as in any intellectual production, four fundamental entities (or aspects) can be
specified.</t> production.</t>
        <t>The first two entities reflect its contents:</t>
        <ul
        <dl spacing="normal">
          <li>
            <t>work:

<!-- [rfced] Please review "our case" here. Is the intent "in this document",
"in LEX", or something else?

Original:
   *  work: identifies a distinct intellectual creation; in our case, it
      identifies a source of law both in its original form as amended
      over time;</t>
          </li>
          <li>
            <t>expression: time;

   *  expression: identifies a specific intellectual realisation of a
      work; in our case it identifies every different (original or up-
      to-date) version of the source of law over time and/or language in
      which the text is expressed.
   ...
   *  manifestation: identifies a physical embodiment of an expression
      of a work; in our case it identifies embodiments in different
      media (printing, digital, etc.), encoding formats (XML, PDF,
      etc.), or other publishing characteristics;

   *  item: identifies a specific copy of a manifestation; in our case
      it identifies individual physical copies as they are found in
      particular physical locations.
-->

<!-- [rfced] Please clarify the text starting with "both...".

Original:
   work:  identifies a distinct intellectual creation; in our case, it
      identifies a source of law both in its original form as amended
      over time;

Perhaps:
   work:  Identifies a distinct intellectual creation; in our case, it
      identifies a source of law in both its original form and its amended
      form over time.
-->
            <dt>work:</dt><dd>Identifies a distinct intellectual creation; in our case, it
identifies a source of law both in its original form
as amended over time.</dd>
            <dt>expression:</dt><dd>Identifies a specific intellectual realization of a
work; in our case, it identifies every different (original or
up-to-date) version of the source of law over time and/or language in
which the text is expressed.</t>
          </li>
        </ul> expressed.</dd>
        </dl>
        <t>The other two entities relate to its form:</t>
        <ul
        <dl spacing="normal">
          <li>
            <t>manifestation: identifies
            <dt>manifestation:</dt><dd>Identifies a physical embodiment of an expression of a work;
in our case case, it identifies embodiments in different media
(printing, digital, etc.), encoding formats (XML, PDF, etc.),
or other publishing characteristics;</t>
          </li>
          <li>
            <t>item: identifies characteristics.</dd>
            <dt>item:</dt><dd>Identifies a specific copy of a manifestation; in our case case, it
identifies individual physical copies as they are found in
particular physical locations.</t>
          </li>
        </ul> locations.</dd>
        </dl>
        <t>In this document document, the <xref target="FRBR"/> model has been interpreted for the
specific characteristics of the legal domain. In particular, apart
from the language that does produce a specific expression, the
discriminative criterion between expression and manifestation is
based on the difference of the juridical effects that a variation can
provide with respect to the involved actors (citizens, parties,
and institutions). In this scenario scenario, the main characteristic of the
expression of an act is represented by its validity over the time, time
during which it provides the same juridical effects. These effects may
change as a result of amendments or annulments of other legislative or
jurisprudential acts. Therefore Therefore, notes, summarizations, summaries, comments,
anonymizations
anonymizations, and other editorial activities over the same text do
not produce different expressions, but expressions. Instead, they produce different manifestations.</t>
      </section>
      <section anchor="the-structure-of-the-local-name">
        <name>The Structure
        <name>Structure of the Local Name</name>
        <t>The local-name within the "lex" namespace MUST <bcp14>MUST</bcp14> contain all the
necessary pieces of information enabling the unequivocal
identification of a legal document.  If the local-name violates
this requirement, the related URN is not a valid one within the "lex"
namespace.</t>
        <t>In the legal domain, at "work" level, three components are always
present:
present at the "work" level: the enacting authority, the type of provision provision, and the
details. A fourth component, the annex, can also be added if any. added.
It is often necessary to differentiate various expressions, that is:</t>
        <ul spacing="normal">
          <li>
            <t>the original version and all the amended versions of the same
document;</t>
document, and</t>
          </li>
          <li>
            <t>the versions of the text expressed in the different official
languages of the state or organization.</t>
          </li>
        </ul>
        <t>Finally
        <t>Finally, the uniform name allows a distinction among diverse
manifestations, which
manifestations that may be produced by multiple publishers using
different means and formats.</t>
        <t>In every case, the basic identifier of the source of law (work)
remains the same, but information is added regarding the specific
version under consideration (expression); similarly (expression). Similarly, a suffix is added
to the expression for representing the characteristics of the
publication (manifestation).</t>
        <t>Information that forms a uniform name for a source of law uniform name at each level
(work, expression, and manifestation) is expressed in the official
language of the relevant jurisdiction; jurisdiction. More language-dependent names (aliases) are
created in case of cases where there are multiple official
languages (as in Switzerland) or more involved jurisdictions (as in
international treaties), more language-dependent names (aliases) are
created.</t> treaties).</t>

        <t>Therefore, the more general structure of the local name appears as
follows:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
       local-name = work ["@" expression] ["$" manifestation]
]]></artwork>
]]></sourcecode>
        <t>However, consistent with legislative practice, the uniform name of
the main original provision (work) becomes the identifier of an
entire class of documents which includes: that includes the following: the original main document,
the annexes, and all their the versions, languages languages, and formats
that are subsequently generated.</t>
      </section>
      <section anchor="structure-of-the-document-identifier-at-work-level">
        <name>Structure of the Document Identifier at "Work" Level</name>
<!-- [rfced] The first sentence below mentions "the type of provision" as one
of the components, but the ABNF uses "measure". Please review and let us
know if any updates are needed.

Original:
   In the legal domain, at "work" level, three components are always
   present: the enacting authority, the type of provision and the
   details.  A fourth component, the annex, can be added if any.
   ...
      work = authority ":" measure ":" details *(":" annex)
-->

        <t>The structure of the document identifier is comprised of the four
fundamental elements mentioned above, distinguished one from
the other, other and ordered by increasingly narrow
domains and competencies:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
   work = authority ":" measure ":" details *(":" annex)
]]></artwork>
]]></sourcecode>
        <t>where:</t>
        <ul

<dl newline="false" spacing="normal">
          <li>
            <t>authority is the
            <dt>authority:</dt><dd>The issuing or proposing authority of the measure
(e.g., State, Ministry, Municipality, Court, etc.);</t>
          </li>
          <li>
            <t>measure is the state, ministry, municipality, court, etc.).</dd>

            <dt>measure:</dt><dd>The type of the measure, both public nature (e.g.,
constitution, act, treaty, regulation, decree, decision, etc.) as
well as and
private one (e.g., license, agreement, etc);</t>
          </li>
          <li>
            <t>details are the etc.).</dd>

            <dt>details:</dt><dd>The terms associated to with the measure, typically the date
(usually the signature date) and the number included in the heading
of the act;</t>
          </li>
          <li>
            <t>annex is the act.</dd>

            <dt>annex:</dt><dd>The identifier of the annex, if any (e.g., Annex 1).</t>
          </li>
        </ul>
        <t>In 1).</dd>

        </dl>
<!-- [rfced] May we update "identifier of the annex adds a suffix" and
"identifier of an annex of an annex adds an ending" as follows in these
sentences to improve clarity?

Original:
   In case of annexes, both the main document and its annexes have their
   own uniform name so that they can individually be referenced; the
   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
   to that of the annex which it is attached to.</t> to.

Perhaps:
   Both the main document and its annexes have their own uniform names
   so that they can be referenced individually; the identifier of an
   annex consists of a suffix added to the identifier of the main document.
   In similar way, the
   identifier of an annex to another annex consists of another suffix added to the
   identifier of the previous annex.
-->

<t>Both the main document and its annexes have their
own uniform names so that they can be referenced individually; the
identifier of the annex adds a suffix to that of the main document.
   In a similar way, the identifier of an annex of an annex adds an ending
   to that of the annex that it is attached to.
</t>
        <t>The main elements of the work name are generally divided into several
elementary components, and for each component, specific rules of
representation are established (criteria, modalities, syntax syntax, and
order).
For the details regarding each element, please see the <xref target="syn-work"/>.
Examples (hypothetical)
The following are hypothetical examples of work identifiers are:</t> identifiers:</t>
        <artwork><![CDATA[
urn:lex:it:stato:legge:2006-05-14;22
urn:lex:uk:ministry.justice:decree:1999-10-07;45
urn:lex:ch;glarus:regiere:erlass:2007-10-15;963
urn:lex:es:tribunal.supremo:decision:2001-09-28;68
urn:lex:fr:assemblee.nationale:proposition.loi:13.legislature;1762
urn:lex:br:estado:constituicao:1988-10-05;lex-1
urn:lex:un.org:united.nations;general.assembly:resolution:
    1961-11-28;a-res-1661
urn:lex:nl:hoge.raad:besluit:2008-04-01;bc8581
]]></artwork>
        <t>The type of measure is important to identify
case law, as well as law and legislation, especially within the legal systems
where cases are identified 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
able to differentiate between materials belonging to a
specific case.</t>
        <t>Here below
        <t>The following is an example where the type of measure or the full date
are essential for identify specific materials of a case:</t>
        <artwork><![CDATA[
- 4/59

<ul spacing="normal">

<li><t>4/59 Judgment of the EEC Court of Justice 04/04/1960, Mannesmann AG and others / ECSC High Authority Authority</t>

<artwork><![CDATA[
  urn:lex:eec.lex.arpa:court.justice:judgement:1960-04-04;4-59
- 4/59
]]></artwork>
</li>

<li><t>4/59 Order of the EEC Court of Justice 18/05/1960, Mannesmann AG and others / ECSC High Authority Authority</t>

<artwork><![CDATA[
  urn:lex:eec.lex.arpa:court.justice:order:1960-05-18;4-59
]]></artwork>
</li>

</ul>
      </section>
      <section anchor="aliases">
        <name>Aliases</name>
        <t>International treaties involve multiple signatory jurisdictions, jurisdictions
and are therefore represented through multiple identifiers, each of them related
to a signatory. For example, a bilateral France and
Germany treaty is identified through two URNs (aliases) belonging to
either the "fr" or "de" jurisdiction<br/> jurisdiction
(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> jurisdictions).</t>
        <t>In the states or organisations organizations that have multiple official
languages, a document has multiple identifiers, each of them identifiers. Each identifier is expressed in
a different official language, language and is basically a set of equivalent aliases.
This system permits manual or automated construction of the uniform
name of the referred source of law in the same language used in the
document itself<br/> itself
(e.g., "urn:lex:eu:council:directive:2004-12-07;31",
"urn:lex:eu:consiglio:direttiva:2004-12-07;31", etc.).</t> "urn:lex:eu:council:directive:2004-12-07;31" and
"urn:lex:eu:consiglio:direttiva:2004-12-07;31").</t>
        <t>Moreover, a document can be assigned more than one uniform name in
order to facilitate its linking from other documents. This option can
be used for documents that, although unique, are commonly referenced
from different perspectives. For perspectives, for example, the form of a document's
promulgation and its specific content (e.g., a Regulation promulgated
through a Decree of the President of the Republic).</t>
      </section>
      <section anchor="structure-of-the-document-identifier-at-expression-level">
        <name>Structure of the Document Identifier at "Expression" Level</name>
        <t>There may be several expressions of a legal text, text connected to
specific versions or languages.</t>
        <t>Each version is characterized by the period of time during which that
text is to be considered to be in force or effective.
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>
        <ul spacing="normal">
          <li>
            <t>amendments due to the issuing of other legal
acts and to the subsequent production of updated or consolidated
texts;</t>
texts,</t>
          </li>
          <li>
            <t>correction of publication errors (rectification or errata corrige);</t> corrige), and</t>
          </li>
          <li>
            <t>entry into or departure from a particular time span, depending on
the specific date in which different partitions of a text come into
force.</t>
          </li>
        </ul>
        <t>Each such version may be expressed in more than one language,
with each language-version language version having its own specific identifier.
The identifier of a source of law expression adds such information to
the work identifier, identifier using the following main structure:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
    expression = version [":" language]
]]></artwork>
]]></sourcecode>
        <t>where:</t>
        <ul
<dl newline="false" spacing="normal">
          <li>
            <t>version is the
            <dt>version:</dt><dd>The identifier of the version of the original or
amended source of law. In general general, it is expressed by the
promulgation date of the amending act; other specific
information can be used for particular documents. If necessary, the
original version is specified by the string "original", "original" and is expressed in
the language of the act or version (for the details regarding this
element, please see the <xref target="syn-ver"/>);</t>
          </li>
          <li>
            <t>language is the target="syn-ver"/>).</dd>

            <dt>language:</dt><dd>The identification code of the language in which the
document is expressed, according to <xref target="RFC5646"/> (it=Italian, fr=French,
de=German, etc.). The granularity level of the language (for example example,
the specification of the German language as used in Switzerland
rather than the standard German) is left to each specific
jurisdiction. The information is not necessary when the text is
expressed in the sole official language of the country or
jurisdiction.</t>
          </li>
        </ul>
        <t>Hypothetical
jurisdiction.</dd>
        </dl>
        <t>The following are hypothetical examples of document identifiers for expressions are:</t> expressions:</t>
        <artwork><![CDATA[
urn:lex:ch:etat:loi:2006-05-14;22@originel:fr
    (original version in French)
urn:lex:ch:staat:gesetz:2006-05-14;22@original:de
    (original version in German)
urn:lex:ch:etat:loi:2006-05-14;22@2008-03-12:fr
    (amended version in French)
urn:lex:ch:staat:gesetz:2006-05-14;22@2008-03-12:de
    (amended version in German)
urn:lex:be:conseil.etat:decision:2008-07-09;185.273@originel:fr
    (original version in French of a Belgian decision)
]]></artwork>
      </section>
      <section anchor="struct-manif">
        <name>Structure of the Document Identifier at "Manifestation" Level</name>
        <t>To identify a specific manifestation, the uniform name of the
expression is followed by a suitable suffix containing the following
main elements:</t>
        <ul
        <dl spacing="normal">
          <li>
            <t>editor:
<!-- [rfced] We updated "its Internet domain name" to "the publisher's
Internet domain name" for clarity. Please let us know if this is
incorrect.

Original:
   *  editor: editorial staff who produced it, expressed according to
   its Internet domain name.

Updated:
   *  editor: Editorial staff who produced it, expressed according to
   the publisher's Internet domain name.
-->

<!-- [rfced] Will readers know who "them" is in the phrase "for each of them a
new manifestation with the new domain name"?

Original:
      In this case, in order to make its materials accessible, the
      publisher will have to create for each of them a new manifestation
      with the new domain name;

Perhaps:
      In this case, in order to make its materials accessible, the
      publisher will have to create a new manifestation with a new domain name
      for each object.

Or:
      In this case, in order to make its materials accessible, the
      publisher will have to create a new manifestation with a new domain name
      for each object that is not accessible.
-->

            <dt>editor:</dt><dd>Editorial staff who produced it, expressed according to
the publisher's Internet domain name. Since publishers' domain names may vary
over time, manifestations already assigned by a publisher remain
unchanged
unchanged, even if the identified object is no longer accessible. In
this case, in order to make its materials accessible, the publisher
will have to create for each of them a new manifestation with the a
new domain name;</t>
          </li>
          <li>
            <t>format: the name for each of them.</dd>
            <dt>format:</dt><dd>The digital format (e.g., XML, HTML, PDF, etc.) expressed
according to the MIME Content-Type standard <xref target="RFC2045"/>, where the
"/" character is to be substituted by with the "-" sign;</t>
          </li>
          <li>
            <t>component: possible sign.</dd>
            <dt>component:</dt><dd>Possible components of the expressions
            contained in the manifestation. Such components are expressed by language-
dependent
            language-dependent labels representing the whole document (in
            English "all")
or "all"), the main part of the document (in English "body") "body"),
            or the caption label of the component itself (e.g. (e.g., Table 1,
            Figure 2, etc.);</t>
          </li>
          <li>
            <t>feature: other etc.).</dd>
            <dt>feature:</dt><dd>Other features of the document (e.g., anonymized
decision text).</t>
          </li>
        </ul>
        <t>The text).</dd>
        </dl>
        <t>Thus, the manifestation suffix thus reads:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
    manifestation = editor ":" format
                    [":" component [":" feature]]
]]></artwork>
        <t>To
]]></sourcecode>
<!-- [rfced] May we rephrase the following sentence starting at "for example
as regards..." as follows to improve clarity?

Original:
   To indicate possible features or peculiarities, each main element of
   the manifestation MAY be followed by further specifications
   (separated by ";"), for example as regards editor the archive name
   and the electronic publisher, for format the version, etc.
Therefore

Perhaps:
   To indicate possible features or peculiarities, each main element of
   the manifestation MAY be followed by further specifications
   (separated by “;”), for example, the archive name and electronic publisher
   for editor and the version for format.
-->
        <t>To indicate possible features or peculiarities, each main element of
the manifestation <bcp14>MAY</bcp14> be followed by further specifications
(separated by ";"), for example as regards editor the archive name
and the electronic publisher, for format the version, etc.
Therefore, the main elements of the manifestation will assume the
following forms:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
    editor = publisher *(";" specification)
    format = mime *(";" specification)
    component = part *(";" specification)
    feature = attribute *(";" specification)
]]></artwork>
]]></sourcecode>
        <t>The syntax details of the manifestation element is are shown in
<xref target="urn-lex-syn"/>, target="urn-lex-syn"/> in the related part.</t>
        <t>(examples (hypothetical):</t>
        <t>the

<t>The following are hypothetical examples:</t>
<ul spacing="normal">
        <li><t>The original version of the Italian act 3 April 2000, n. 56 might have
the following manifestations with their relative uniform names:</t>
        <artwork><![CDATA[
- PDF

<ul spacing="normal">

<li><t>PDF format (vers. 1.7) of the whole act edited by the Italian
  Parliament:
  "urn:lex:it:stato:legge:2000-04-03;56$application-pdf;
  1.7:parlamento.it"
- XML Parliament:</t>

<artwork><![CDATA[
  urn:lex:it:stato:legge:2000-04-03;56$application-pdf;
  1.7:parlamento.it
]]></artwork>
</li>

<li><t>XML format (version 2.2 DTD NIR) of the text of the act and PDF format
(version 1.7) of the "Figura 1" (figure 1) contained in the body, edited by
the Italian Senate:
  "urn:lex:it:stato:legge:2000-04-03;56$text-xml;dtd-nir-2.2:
  senato.it:testo"
  "urn:lex:it:stato:legge:2000-04-03;56$application-pdf;1.7:
  senato.it:figura.1" Senate:</t>

<artwork><![CDATA[
  urn:lex:it:stato:legge:2000-04-03;56$text-xml;dtd-nir-2.2:
  senato.it:testo
  urn:lex:it:stato:legge:2000-04-03;56$application-pdf;1.7:
  senato.it:figura.1
]]></artwork>
        <t>the
</li>
</ul>
	</li>
        <li><t>The Spanish URN of the html HTML format of the whole Judgment of the
European Court of Justice n. 33/08 of 11/06/2009, in Spanish version,
published in the Jurifast database in anonymized form:</t>
        <artwork><![CDATA[
"urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
@original:es$text-html:juradmin.eu;jurifast:todo:anonimo")
]]></artwork>
urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
@original:es$text-html:juradmin.eu;jurifast:todo:anonimo
]]></artwork></li>
</ul>
        <t>It is useful to be able to assign a uniform name to a
manifestation (or to a part of it) in case non-textual objects are
involved. These may be multimedia objects that are non-textual in
their own right (e.g. (e.g., geographic maps, photographs, etc.), etc.) or texts
recorded in non-textual formats, such as formats (e.g., image scans of documents.</t> documents).</t>
      </section>
      <section anchor="sources-of-law-references">
        <name>Sources of Law References</name>
        <t>References to sources of law often refer to specific partitions of
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, block that
represents a logical subdivision of an act.</t>
        <t>As regards
        <t>In the digital representation, a partition is represented
        by an element (a block of text) with its own ID; this ID aims to
        identify the related element and to locate it. In this case,
therefore, Therefore,
        it is possible either to either extract or to point to a
        partition.</t>
        <t>In a mark-up

        <t>For markup that does not fitting fit the logical structure of the text (as (like HTML),
generally only the starting point of the partition, rather than the
whole block of text or element, is identified through a label (a (e.g., &lt;a
id=partitionID&gt;&lt;/a&gt; tag in Html Markup Language the HTML markup language <xref target="W3C.HTML"/>). In this case
therefore case, it is not only possible to extract point to a partition but only to point
to not extract it.</t>

        <t>Partitions should be assigned unique labels or
IDs within the including document document, and their value should be the same
regardless of document format.</t>
        <t>For enabling
        <t>To enable the construction of the partition identifier between
        different collections of documents, specific construction rules for
        IDs or labels will be defined and shared, shared within each country or
jurisdiction,
        jurisdiction for any document type<br/>
(e.g., for type. For example, in legislation, the paragraph 2 of the
        article 3 might have the value "art3;par2" as the label or ID the value
"art3;par2", similarly ID;
        similarly, for case-law, case law, paragraph 22 of the judgment in
        Case 46/76 Bauhuis v Netherlands, Netherlands might have the value "par22" as the label or ID the value
"par22").</t> ID.</t>
        <t>Furthermore, it is useful to foresee the compatibility with
applications that are able to manage this information (e.g., returning the
proper element); these procedures are particularly useful in the case
of rather long acts, such as codes, constitutions, regulations, etc.
For this purpose purpose, it is necessary that the partition identifier is be
transmitted to the servers (resolution and application) and therefore application). Therefore,
it cannot be separated by the typical "#" character of URI fragment,
which is not transmitted to the server.</t>
        <t>According to these requirements, the syntax of a reference is:</t>
        <artwork><![CDATA[
        <sourcecode type="abnf"><![CDATA[
     URN-reference = URN-document ["~" partition-id]
]]></artwork>
        <t>(e.g., to refer
]]></sourcecode>
        <t>For example, referring to the paragraph 3 of the article 15 of the French
Act of 15 May 2004, n. 106, the reference can be
"urn:lex:fr:etat:loi:2004-05-15;106~art15;par3").</t>
        <t>Using
"urn:lex:fr:etat:loi:2004-05-15;106~art15;par3".</t>
<!-- [rfced] How may we clarify "Using a different separator ("~") from the
document name" here?

Original:
   Using a different separator ("~") from the document name, the
   partition ID is not withheld by the browser but it is transmitted to
   the resolution process. This enables

Perhaps:
   If a different separator ("~") is used after the resolver document name, the
   partition ID is not withheld by the browser but is transmitted to retrieve (for
example, out of
   the resolution process.
-->

<t>Using a database) only different separator ("~") from the referred partition, if document name, the
partition ID is not withheld by the browser but is transmitted to
the resolution process.
If the
partition syntax is compatible with the media type used, otherwise this enables the resolver to
return retrieve (for
example, out of a database) only the referred partition; otherwise, the whole act.</t> act is returned.
	</t>
        <t>When resolving to HTTP,
the resolver SHALL <bcp14>SHALL</bcp14> transform the partition ID
to an appropriate internal reference (#) in on the page, page
or at the beginning if that point cannot be found.
The transformation in the URI fragment is obtained by appending to
the URL the "#" character followed by the partition ID to
the URL (in the
example above, the returned URL will be &lt;URL-document&gt;#art15;par3).
Doing this, knowing the granularity of the act markup, the resolver
could exploit the hierarchical structure of the ID, ID by eliminating
sub-partitions that are not addressed. If In the previous example, if only the article was identified in the
act, in the previous example it could return &lt;URL-document&gt;#art15
only.</t>
        <t>It is possible to use the general syntax (with "#"); in this
case
case, only the URN document component of the reference is transmitted
to the resolver, therefore resolver; therefore, the whole document will always be
retrieved.</t>
      </section>
    </section>
    <section anchor="syn-work">
      <name>Specific Syntax of the Identifier at "Work" Level</name>
      <section anchor="the-authority-element">
        <name>The authority Authority Element</name>
        <section anchor="indication-of-the-authority">
          <name>Indication of the Authority</name>
          <t>The authority element of a uniform name may indicate, indicate the following in the
various cases:</t>
          <ul spacing="normal">
            <li>
              <t>the
              <t>The actual authority issuing the legal provision. More
specifically, the authority adopting the provision or enacting it;</t> it.</t>
            </li>
            <li>
              <t>the
              <t>The institution where the provision is registered, known known, and
referenced to, even if produced by others (e.g., the bills
identified through the reference to the Chamber where they are
presented);</t>
presented).</t>
            </li>
            <li>
              <t>the
              <t>The institution regulated (and referred to in citations) by the
legal provision even when this is issued by another authority
(e.g., the statute of a Body);</t> Body).</t>
            </li>
            <li>
              <t>the
              <t>The entity that proposed the legal material not yet included in the
institutional process (e.g. (e.g., a proposed bill written by a
political party).</t>
            </li>
          </ul>
        </section>
        <section anchor="multiple-issuers">
          <name>Multiple Issuers</name>
          <t>Some sources of law are enacted by a number of issuing parties (e.g.,
inter-ministerial decrees, agreements, etc.). In this case, the
authority element contains all the issuing parties (properly
separated),
separated) as follows:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
   authority = issuer *("+" issuer)
]]></artwork>
          <t>(e.g., "ministry.justice+ministry.finances").</t>
]]></sourcecode>
          <t>This is an example: "ministry.justice+ministry.finances".</t>
        </section>
        <section anchor="indication-of-the-issuer">
          <name>Indication of the Issuer</name>
          <t>Each issuing authority is essentially represented by either an
institutional office (e.g., Prime Minister) or an institution (e.g.,
Ministry); in the last case, the authority is indicated in accordance
with the institution's hierarchical structure, from the more general
to more specific (Council, Department, etc.), ending with the
relative office (President, Director, etc.).
Therefore, the structure of the issuer is as follows:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
   issuer = (institution *(";" body-function)) / office
]]></artwork>
          <t>(e.g., "ministry.finances;department.revenues;manager")</t>
]]></sourcecode>
          <t>This is an example: "ministry.finances;department.revenues;manager".</t>
        </section>
        <section anchor="indication-of-the-body">
          <name>Indication of the Body</name>
          <t>Depending on the kind of measure, the body within the issuing
authority is unambiguously determined (e.g., the Council for Regional
Acts)
Acts), and normally it is not normally indicated in the references.
Just like in practice, the indication of the enacting authority is
limited to the minimum in relation to the type of measure<br/> measure
(e.g., "region.tuscany:act" and not "region.tuscany;council:act").</t>
        </section>
        <section anchor="indication-of-the-function">
          <name>Indication of the Function</name>
          <t>Generally, the function is indicated, sometimes instead of the body
itself:</t>
          <ul spacing="normal">
            <li>
              <t>in
              <t>In the case of political, representative representative, or elective offices<br/> offices
(e.g., "university.oxford;rector:decree" instead of
"university.oxford;rectorship:decree");</t>
"university.oxford;rectorship:decree").</t>
            </li>
            <li>
              <t>when it refers
              <t>When referring to a top officer in the institution (e.g., general
manager, general secretary, etc.) etc.), which is not always possible to
associate a specific internal institutional structure to<br/> to
(e.g., "national.council.research;general.manager").</t>
            </li>
          </ul>
          <t>It is not indicated when it clearly corresponds to the person in
charge of an institution (typically, a general director); in this
case, only the structure and not the person in charge is indicated<br/> indicated
(e.g., "ministry.justice;department.penitentiary.administration").</t>
          <t>The function MUST <bcp14>MUST</bcp14> be indicated when:</t>
          <ul spacing="normal">
            <li>
              <t>it
              <t>It is not the same of as the director or the person in charge of the
structure (for example, in case of an undersecretary, a deputy
director, etc.);</t> etc.). </t>
            </li>
            <li>
              <t>the
              <t>The type of measure may be both monocratic or collegial: collegial; the
indication of the office eliminates the ambiguity.</t>
            </li>
          </ul>
        </section>
        <section anchor="conventions-for-the-authority">
          <name>Conventions for the Authority</name>
          <t>Acts and measures bearing the same relevance as an act, issued or
enacted since the foundation of the State, have conventionally
indicated "state" (expressed in each country country's official language) as
authority;
the authority. The same convention is used for constitutions, codes
(civil, criminal, civil procedure, criminal procedure, etc) etc.), and
international treaties.</t>
        </section>
      </section>
      <section anchor="the-measure-element">
        <name>The measure Measure Element</name>
        <section anchor="criteria-for-the-indication-of-the-type-of-measure">
          <name>Criteria for the Indication of the Type of Measure</name>

          <t>In uniform names names, the issuing authority 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
if it is widely used.
When the authority-measure combination clearly identifies a specific
document, the type of measure is not defined through attributes
referring to the enacting authority<br/> authority
(e.g., "region.tuscany:act" and not "region.tuscany:regional.act").</t>
        </section>
        <section anchor="further-specification-to-the-type-of-measure">
          <name>Further Specification to the Type of Measure</name>
          <t>In the measure element, it is usually sufficient to indicate the
          type of a measure. As usual, references to sources of law, rather than through the formal details
          (date and number), references to sources of law may be made through
          some of their characteristics characteristics, such as the subject-matter subject matter covered
          (e.g., accounting regulations), nicknames referring to the promoter
          (e.g., Bolkestein directive) directive), or to the topic of the act (e.g.,
          Bankruptcy Law), etc.. etc.  In these cases, the type of measure MAY
          <bcp14>MAY</bcp14> be followed by further specifications that are
          useful in referencing referencing, even if the details are lacking:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
      measure = measure-type *(";" specification)
]]></artwork>
          <t>(e.g.,
]]></sourcecode>
          <t>These are examples: "regulations;accounting" or "act;bankruptcy").</t> "act;bankruptcy".</t>
        </section>
        <section anchor="aliases-for-sources-of-law-with-different-normative-references">
          <name>Aliases for Sources of Law with Different Normative References</name>
          <t>There are legislative measures that, although unique, are usually
          cited in different ways, for example through the legislative act example, introducing them into the
          legal order through a legislative act (President's decree,
          legislative decree, etc.) or through their legislative category
          (regulations, consolidation, etc.).  In order to ensure, in all the cases, ensure the validity of the references, references in all cases, an alias (additional (an additional URN LEX identifier),
          identifier) that takes into account the measure category, category is added
          to what represents the legislative form of the same act<br/> act (e.g.,
          "state:decree.legislative:1992-07-24;358" and
          "state:consolidation;public.contracts:1992-07-24;358").</t>
        </section>
        <section anchor="relations-between-measure-and-authority-in-the-aliases">
          <name>Relations between Between Measure and Authority in the Aliases</name>

          <t>The sources of law including different normative references are
usually introduced in legislation through the adoption or the issuing
of an act, which they are either included or attached to. It is,
therefore, Therefore, it is
 necessary to create an alias linking the two aspects of
the same document. Specifically, the different measures can be:</t>
          <ul spacing="normal">
            <li>
              <t>adopted/issued
              <t>Adopted/issued by an authority different from the one regulated by
the provision (e.g., the statute of a Body); in Body). In this case, the
correlation is established between two uniform names names, each featuring
a completely different authority element<br/> element
(e.g., "italian.society.authors.publishers:statute" and
"ministry.cultural.activities+ministry.finances.budget.economic.
planning:decree");</t>
planning:decree").</t>
            </li>
            <li>
              <t>issued
              <t>Issued by the institution itself either because it has issuing
authority or by virtue of a proxy (e.g., a provision that refers to
the functioning of the Body itself); in itself). In this case, the two aliases
share the first part of the authority<br/> authority
(e.g., "municipality.firenze:statute" and
"municipality.firenze;council:deliberation");</t>
"municipality.firenze;council:deliberation").</t>
            </li>
            <li>
              <t>issued
              <t>Issued by the same Body to regulate a particular sector of its own
competence; in
competence. In this case case, the authority element is the same<br/> same
(e.g., "ministry.justice:regulation;use.information.tools.
telematic.process" and "ministry.justice:decree").</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="det-elem">
        <name>The Details Element</name>
        <section anchor="indication-of-the-details">
          <name>Indication of the Details</name>
          <t>The details of a source of law usually include the date of the
enactment and the identification number (inclusion in the body of
laws, register, protocol, etc.).</t>
          <t>Some measures can have multiple dates; there dates. There are also cases in which
the number of the measure does not exist (unnumbered measures) or a
measure has multiple numbers (e.g., unified cases). For these
reasons, the set up setup of both elements (date and number) includes
multiple values.</t>
          <t>Some institutions (e.g., the Parliaments) usually identify documents
through their period of reference (e.g., the legislature number)
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
legislature). In these cases, the component period is used in
substitution of
substitued for the component dates.</t>
          <t>Usually
          <t>Usually, details of a measure are not reported according to a specific
sequence; in
sequence. In accordance with the global structure of the uniform
name, which goes from the general to the specific, the sequence
date-number has the following form:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
    details = (dates / period) ";" numbers
]]></artwork>
          <t>(e.g., "2000-12-06;126", "14.legislature;s.2544").</t>
]]></sourcecode>
          <t>The following are examples: "2000-12-06;126" and "14.legislature;s.2544".</t>
        </section>
        <section anchor="multiple-dates">
          <name>Multiple Dates</name>
          <t>Some sources of law, even if unique, are identified by more than one
date; in
date. In this case, in the field dates all the given dates are to
be reported and indicated as follows:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
dates = date *("," date)
]]></artwork>
          <t>(e.g.,
]]></sourcecode>

<t>For example, the measure of the Data Protection Authority of
          December 30, 1999-January 13, 2000, No. 1/P/2000 has the following
          uniform name:<br/>
"personal.data.protection.authority:measure:1999-12-30,2000-01-13;
1-p-2000").</t> name:</t>
<artwork><![CDATA[
  personal.data.protection.authority:measure:1999-12-30,2000-01-
  13;1-p-2000
]]></artwork>

          <t>As specified in <xref target="dat-form"/>, all the dates can have, in addition to the ISO format,
also have
          the date typical of the jurisdiction.</t> jurisdiction in addition to the ISO
          format.</t>
        </section>
        <section anchor="unnumbered-measures">
          <name>Unnumbered Measures</name>
          <t>Measures not officially numbered in the publications may have a
non-unequivocal identifier, because several measures of the same type
can exist, exist and can be issued on the same day by the same authority.
To ensure that the uniform name is unambiguous, the numbers field
MUST,
<bcp14>MUST</bcp14>, in any case, contain a discriminating element, which can be any
identifier used internally, internally and not published, published by the authority
(e.g., protocol).</t>
          <t>If the authority does not have its own identifier, one identifier
MUST
<bcp14>MUST</bcp14> be created for the name system. In order to easily differentiate
it, such number is preceded by the string "lex-":</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
   number-lex = "lex-" 1*DIGIT
]]></artwork>
          <t>(e.g., "ministry.finances:decree:1999-12-20;lex-3").</t>
]]></sourcecode>
          <t>The following is an example: "ministry.finances:decree:1999-12-20;lex-3".</t>
          <t>It is the responsibility of the authority issuing a document to assign a
discriminating specification to it; in case of it. When there are multiple authorities,
only one of them is responsible for the assignment of the number to
the document (e.g., the proponent).</t>
          <t>The unnumbered measures published on an official publication (e.g.,
the Official Gazette), instead of by a progressive number are
recognized by the univocal identifying label printed on the paper. paper instead of by a progressive number.
Such an identifier, even if it is unofficial but assigned to a document in
an official publication, is to be preferred because it has the clear
advantage to be of being public and is therefore easier to be found.</t> find.</t>
        </section>
        <section anchor="mult-num">
          <name>Multiple Numbers</name>
          <t>Some legal documents (e.g., bills), even if unique, are identified by
a set of numbers (e.g., the unification of cases or bills).
In this case, in the numbers field, all the identifiers are
reported, according to the following structure:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
  numbers = document-id *("," document-id)
]]></artwork>
          <t>(e.g., "2000-06-12;c-10-97,c-11-97,c-12-97").</t>
]]></sourcecode>
          <t>The following is an example: "2000-06-12;c-10-97,c-11-97,c-12-97".</t>
          <t>The characters which that are not allowed (e.g., "/") or reserved (e.g.,
":"), including the comma, cannot exist inside the document-id, document-id and
therefore MUST <bcp14>MUST</bcp14> be turned into "-".</t>
          <t>Where

<t>When special characters contained in the number of the act are
distinctive of the act itself (e.g. (e.g., bill n. 123-bis (removal of 123)
and n. 123/bis (return of 123)) and would disappear with the
conversion to "-", a further ending must be added, allowing added to
distinguish the acts (e.g. (e.g., bill n.123-bis-removal and 123-bis-
return).</t> 123-bis-return).</t>
        </section>
      </section>
      <section anchor="the-annex-element">
        <name>The annex Annex Element</name>
        <section anchor="annex-formal">
          <name>Formal Annexes</name>
          <t>Although annexes are an integral part of the a legal document, they
          may be referred to and undergo amendments separately from the act to
          which they are annexed. It is, therefore, Therefore, it is necessary that both the
          main document as well as each formal individual annex is
          unequivocally identified.</t>
          <t>Formal annexes may be registered as separate parts or together
          with a legal provision; they may also or may not be autonomous in nature or not. nature. In
          any case, they MUST <bcp14>MUST</bcp14> be given a uniform name, which name that
          includes the uniform name of the source of law to which they are attached,
          attached and a suffix
which that identifies the annex itself.</t>
          <t>The suffix of formal annexes includes the official heading of the
annex and, possibly, further specifications (e.g., the title) which that
will facilitate the retrieval of the annex in case the identifier is
missing:</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
    annex = annex-id *(";" specification)
]]></sourcecode>
          <t>The following is an example:</t>
<artwork><![CDATA[
  region.sicily;council:deliberation:1998-02-12;14:annex.a;
  borders.park
]]></artwork>
          <t>(e.g., "region.sicily;council:deliberation:1998-02-12;14:annex.a;
borders.park").</t>
          <t>The characters which that are not allowed (e.g. (e.g., "/") or which that are
          reserved
(e.g. (e.g., ":") must not be featured in the annex-id and
          therefore MUST <bcp14>MUST</bcp14> be turned into ".".</t>
        </section>
        <section anchor="annex-annex">
          <name>Annexes of Annexes</name>

<t>When there are annexes to an annex, their corresponding identifiers 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/>
(e.g., it). For example,
   Table 1 attached to the Annex A of the preceding legal act has the
   following uniform name:<br/>
"region.sicily;council:deliberation:1998-02-12;14:annex.a;
borders.park:table.1;municipality.territories").</t> name:</t>
<artwork><![CDATA[
  region.sicily;council:deliberation:1998-02-12;14:annex.a;
  borders.park:table.1;municipality.territories
]]></artwork>
      </section>
      </section>
    </section>
    <section anchor="syn-ver">
      <name>Specific Syntax of the Version Element of the "Expression"</name>
      <section anchor="the-version-element">
        <name>The version Version Element</name>
        <section anchor="different-versions-of-a-legislative-document">
          <name>Different Versions of a Legislative Document</name>
          <t>The creation of an updated text of a document may have one of the
following forms:</t>
          <ul
          <dl spacing="normal">
            <li>
              <t>"multi-version": when specific mark-ups which
              <dt>"multi-version":</dt><dd>Specific markups that identify the modified
parts of a document (added, substituted substituted, or deleted parts) and their
related periods of effectiveness are indicated inside one a single
object (e.g., an xml XML file). Such a document will be able, in a
dynamic way, to appear in different forms according to the
requested date of effectiveness.
In this document type, usually a set of metadata usually contains the
lifecycle
life cycle of the document (from the original to the last
modification), including the validity time interval of each version
and of each related text portion;</t>
            </li>
            <li>
              <t>"single-version": when, on the contrary, a portion.</dd>
              <dt>"single-version":</dt><dd>A new and distinct object
is created for each amendment to the text at a given time. Each
object is, therefore, characterized by its own period of validity.
In any case case, all the versions SHOULD <bcp14>SHOULD</bcp14> be linked to one another and
immediately navigable.</t>
            </li>
          </ul> navigable.</dd>
          </dl>
          <t>In a "multi-version" document, each time interval should have a link
to the related in-force document version which that can be therefore
displayed.
In a "single-version" document, the metadata should contain links to
all the previous modifications and a link only to the following
version, if any.</t>
          <t><xref target="RFC8288"/> can be used as a reference to establish links between
different document versions, either in the "multi-version" or in the
"single-version" document. According to <xref target="RFC8288"/> target="RFC8288"/>, the following
relations are useful:</t>
          <ul
          <dl spacing="normal">
            <li>
              <t>current
              <dt>current (or last or last-version): in-force version</t>
            </li>
            <li>
              <t>self: this version</t>
            </li>
            <li>
              <t>next: next version</t>
            </li>
            <li>
              <t>previous: previous version</t>
            </li>
            <li>
              <t>first: original version</t>
            </li>
          </ul> last-version):</dt><dd>in-force version</dd>
              <dt>self:</dt><dd>this version</dd>
              <dt>next:</dt><dd>next version</dd>
              <dt>previous:</dt><dd>previous version</dd>
              <dt>first:</dt><dd>original version</dd>
          </dl>
          <t>It is RECOMMENDED <bcp14>RECOMMENDED</bcp14> that these relations are be inserted in the header of
each version (if "single-version") or associated to each entry
containing a single URN (if "multi-version").</t>
        </section>
        <section anchor="ide-vers">
          <name>Identification of the Version</name>
          <t>In order to identify the different time versions of the same act, a specific suffix has to be added to
the uniform name of the original document has to be added a specific
suffix.</t> document.</t>
          <t>Such a suffix identifies each version of a legal provision and
includes, first and foremost, one of the following elements:</t>
          <ul spacing="normal">
            <li>
              <t>the
              <t>The issuing date of the last amending measure taken into account;</t> account.</t>
            </li>
            <li>
              <t>the
              <t>The date in which that the communication of the rectification or of the
errata corrige, is published;</t> corrige was published.</t>
            </li>
            <li>
              <t>a
              <t>A specification which that must identify the reason concerning the
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>
            </li>
          </ul>
<!-- [rfced] How may we update this fragment to be a complete sentence? Also,
please clarify "in-force or effectiveness".

Original:
   For example with regard to changes of the in-force
   or effectiveness of any partition or portion of the text itself
   (e.g., when the amendments introduced by an act are applied at
   different times) or different events occurring on the same date.

Perhaps:
   Examples include changes to the in-force
   or effective version of any partition or portion of the text itself
   (e.g., when the amendments introduced by an act are applied at
   different times) or different events occurring on the same date.
-->

          <t>It is possible to add further specifications that will
distinguish each of the different versions of the text to guarantee
identifier unequivocalness. For example with regard to changes of the
in-force or effectiveness of any partition or portion of the text
itself (e.g., when the amendments introduced by an act are applied at
different times) or different events occurring on the same date.</t>
          <artwork><![CDATA[
          <sourcecode type="abnf"><![CDATA[
   version = (amendment-date / specification)
             *(";" (event-date / event))
]]></artwork>
]]></sourcecode>
          <t>where:</t>
          <ul
<dl newline="false" spacing="normal">
            <li>
              <t>amendment-date contains
              <dt>amendment-date:</dt><dd>Contains the issuing date of the last considered
amendment or of the last communication of amendment. In case If the
original text introduces differentiated periods in which an act is
effective and the information system produces one version for each
of them, such element contains the string "original" expressed in
the language of the act or version;</t>
            </li>
            <li>
              <t>specification contains version.</dd>

              <dt>specification:</dt><dd>Contains any information that is useful to identify the version unambiguously
and univocally the version;</t>
            </li>
            <li>
              <t>event-date contains univocally.</dd>

              <dt>event-date:</dt><dd>Contains the date in which a version is put into
force, is effective effective, or is published;</t>
            </li>
            <li>
              <t>event is a published.</dd>

              <dt>event:</dt><dd>A name assigned to the event producing a further version
(e.g., amendment, decision, etc.).</t>
            </li>
          </ul> etc.).</dd>

          </dl>
          <t>The issuing date of an amending act was chosen as the identifier of a
version because it can be obtained from the heading (formal data)<br/>
(e.g., data). For example, the name "state:royal.decree:1941-01-30;12@1998-02-19"
identifies the updated text of the "Royal Decree of 30/1/1941, No.
12" with the amendments introduced by the "Law Decree of 19/2/1998,
No. 51", 51" without any indication of its actual entry into force.<br/> force.
The same uniform name with the additional ending ";1999-01-01" indicates
the in-force or effective version starting in on a different date (from
1/1/99).</t>
          <t>For (1/1/99).</t>
<!-- [rfced] How may we clarify the text starting with "even if the object
remains only one"?

Original:
   For a full compatibility, every updating of a text or of the
   effectiveness of a "multi-version" document implies the creation of a
   new uniform name, even if the object remains only one, containing the
   identifier of the virtually generated version, exactly as in the case
   of a "single-version" document. A specific meta-data

Perhaps:
   For full compatibility, every update of text or of the
   effectiveness of a "multi-version" document implies the creation of a
   new uniform name, even if there is only one object that contains the
   identifier of the virtually generated version, as in the case
   of a "single-version" document.
-->

<t>For full compatibility, every update of text or of the
effectiveness of a "multi-version" document implies the creation of a
new uniform name, even if the object remains only one, containing the
identifier of the virtually generated version, exactly as in the case
of a "single-version" document.

Specific metadata will associate
every uniform name with the period of time during which such a name name,
together with its corresponding text text, is to be considered valid<br/> valid
(e.g., the multi-version "multi-version" document containing the "R.D. of 01/30/1941,
no. 12", updated by the amendments introduced by the "D.Lgs. of
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
version "state:royal.decree:1941-01-30;12@1998-02-19").</t>
          <t>Please note
          <t>Note that in case of if there are attachments or annexes, the creation of a
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
to guarantee their alignment (i.e., the main document, the
attachments
attachments, and annexes).</t>
          <t>As specified in <xref target="dat-form"/>, all the dates can have, in addition to the ISO format,
also have the date typical of the jurisdiction.</t> jurisdiction in addition to the date in ISO format.</t>
        </section>
      </section>
    </section>
    <section anchor="urn-lex-syn">
      <name>Summary of the Syntax of the Uniform Names of the "lex" Namespace</name>
      <t>;-------------------------------------------------------------------<br/>

<sourcecode type="abnf"><![CDATA[
;-------------------------------------------------------------------
; Structure of a Uniform Resource Name (URN) of the "lex" namespace<br/> namespace
; - NID-lex = namespace<br/> namespace
; - NSS-lex = specific name<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ name
;-------------------------------------------------------------------

URN-lex = "urn:" NID-lex ":" NSS-lex

NID-lex = "lex"
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of a "lex" specific name<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ name
;-------------------------------------------------------------------

NSS-lex = jurisdiction ":" local-name
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the jurisdiction element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

jurisdiction = jurisdiction-code *(";" jurisdiction-unit)

jurisdiction-code = 2*alf-dot

jurisdiction-unit = alf-dot
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the local-name element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

local-name = work ["@" expression] ["$" manifestation]
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the work element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

work = authority ":" measure ":" details *(":" annex)
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the authority element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

authority = issuer *("+" issuer)

issuer = (institution *(";" body-function)) / office

institution = alf-dot

body-function = alf-dot

office = alf-dot
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the measure element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

measure = measure-type *(";" specification)

measure-type = alf-dot

specification = alf-dot
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the details element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

details = (dates / period) ";" numbers

dates = date *("," date)

period = alf-dot

numbers = (document-id *("," document-id)) / number-lex

document-id = alf-dot-oth

number-lex = "lex-" 1*DIGIT
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the annex element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

annex = annex-id *(";" specification)

annex-id = alf-dot
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the expression element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

expression = version [":" language]
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the version element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

version = (amendment-date / specification)
       *(";" (event-date / event))

amendment-date = date

event-date = date

event = alf-dot
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the language element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

language = 2*3alfa *["-" extlang] / 4*8alfa

extlang  = 3alfa *2("-" 3alfa)
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the manifestation element<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ element
;-------------------------------------------------------------------

manifestation = format ":" editor
             [":" component [":" feature]]

format = mime *(";" specification)

mime = alf-dot-hyp

editor = publisher *(";" specification)

publisher = alf-dot-hyp

component = part *(";" specification)

part = alf-dot-hyp

feature = attribute *(";" specification)

attribute = alf-dot-hyp
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Structure of the date<br/>
;-------------------------------------------------------------------</t>
      <artwork><![CDATA[ date
;-------------------------------------------------------------------

date = date-iso ["|" date-loc]

date-iso = year "-" month "-" day

year  = 4DIGIT
month = 2DIGIT
day   = 2DIGIT

date-loc = *(alfadot / other)
]]></artwork>
      <t>;-------------------------------------------------------------------<br/>

;-------------------------------------------------------------------
; Allowed, reserved reserved, and future characters<br/>
;-------------------------------------------------------------------<br/> characters
;-------------------------------------------------------------------
; - allowed = alfadot / other / reserved<br/> reserved
; - reserved = ":" / "@" / "$" / "+" / "|" / ";" / "," / "~"<br/> "~"
; - future   = "*" /  "!"</t>
      <artwork><![CDATA[  "!"

alf-dot = alfanum *alfadot
alf-dot-hyp = alfanum *(alfadot / "-")

alf-dot-oth = alfanum *(alfadot / other)

alfadot = alfanum / "."

alfa = lowercase / uppercase

alfanum = alfa / DIGIT / encoded

lowercase = %x61-7A        ; lower-case ASCII letters (a-z)

uppercase = %x41-5A        ; upper-case ASCII letters (A-Z)

DIGIT     = %x30-39        ; decimal digits (0-9)

encoded   = "%" 2HEXDIG

HEXDIG = DIGIT / %x41-46 / %x61-66 ; hex digits (0-9,A-F,a-f)

other    = "-" / "_" / "'" / "=" / "(" / ")"
]]></artwork>
]]></sourcecode>
    </section>
    <section anchor="the-procedure-of-uniform-names-assignment">
      <name>The Procedure
      <name>Procedure of Uniform Names Assignment</name>
      <section anchor="specifying-the-jurisdiction-element-of-the-lex-identifier">
        <name>Specifying the jurisdiction Jurisdiction Element of the LEX Identifier</name>
        <t>Under the "lex" namespace, each country or international organization
is assigned with a jurisdiction code, which characterizes the URNs of
the source of law of that country or jurisdiction.
This code is
assigned according to ccTLD (as well as TLDN (Top Level (Top-Level Domain Name)
or DN (Domain Name) for the organizations) representation representation, and it is
the value of the jurisdiction-code element, which preserves cross-
country cross-country uniqueness of the identifiers.</t>
      </section>
      <section anchor="jurisdictional-registrar-for-names-assignment">
        <name>Jurisdictional Registrar for Names Assignment</name>
        <t>Any
<!-- [rfced] We have some questions about the text below.

a) The first sentence says a country or jurisdiction "MUST identify a
Jurisdictional Registrar" and the second sentence below says "It must appoint
a Jurisdictional Registrar". Is this redundant?

b) Please clarify the second sentence. Specifically, what should the
designated experts be informed about? What is meant by "together with the
registration of a jurisdiction code"?

Original:
   Any country or jurisdiction, who intends to adopt this schema, MUST
   identify a Jurisdictional Registrar, an organization which shares and
   defines the structure of the optional part (jurisdiction-unit) of the
   name, according to the organization of the state or institution (for
   details see Section 2.2).  It must appoint a Jurisdictional Registrar
   and inform the Designed Experts, together with the registration of a
   jurisdiction code.
-->

        <t>Any country or jurisdiction that intends 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
the name, according to the organization of the state or institution
(for details, see <xref target="jur-cod-regist"/>).  It must appoint a Jurisdictional
Registrar and inform the Designed Experts, together with the
registration of a jurisdiction code.  For example, in a federal state state,
a jurisdiction-unit corresponding to the name of each member state<br/>
(e.g. state
(e.g., "br;sao.paulo", "br;minas.gerais", etc.) may be defined.</t>
        <t>The process of assigning the local-name is managed by each
specific country or jurisdiction under the related jurisdiction
element.</t>
        <t>In any country country, the Jurisdictional Registrar shares and defines the
assignment of the primary elements (issuing authority and type of
legal measure) of the local names considering the characteristics of
its own state or institution organization.</t>
        <t>Such a
        <t>The Jurisdictional Registrar MUST <bcp14>MUST</bcp14> establish, according to the guidelines
indicated in this document, a uniform procedure within the
country or organization to define local-name elements, to take make
decisions upon normalizations and finally to about normalizations, solve and avoid possible
name collisions as well as to collisions, and maintain authoritative registries of
various kinds (e.g., for authorities, types of measures, etc.). In
particular, accurate point-in-time representations of the structure
and naming of government entities are important to semantically-aware semantically aware
applications in this domain.</t>
        <t>Moreover, the Jurisdictional Registrar shares and defines the rules to construct
partition IDs for each document type, possibly in accordance with
those already defined in other jurisdictions.</t>
        <t>Finally, the Jurisdictional Registrar will develop and publish the rules and the
        guidelines for the local-name construction as well as the predefined
        values and codes. The Jurisdictional Registrar should also promote the urn:lex
        identifier for the sources of law of its jurisdiction.</t>
        <t>Such a set of rules will have to be followed by all institutional
bodies adopting the URN LEX identification system in a country or
jurisdiction, as well as by private publishers, and each publishers. Each of them will
be responsible for assigning names to their domains.</t>
      </section>
      <section anchor="identifier-uniqueness">
        <name>Identifier Uniqueness</name>

        <t>Identifiers in the "lex" namespace are defined through a
jurisdiction element assigned to the sources of law of a specific
country or organization, and a local-name is assigned by the issuing
authority,
authority in conformance with the syntax defined in <xref target="creation"/>. The
main elements (authority and type of measure) of the local-name are
defined by the Jurisdictional Registrar, so that it is ensured that
the constructed URNs are unique. The Jurisdictional Registrar MUST <bcp14>MUST</bcp14>
provide clear documentation of rules by which names are to be
constructed,
constructed and MUST <bcp14>MUST</bcp14> update its registries and make accessible its registries.</t> them accessible.</t>
        <t>Any enacting authority is responsible to define for defining formal parameters to
guarantee local name uniqueness by attributing, if necessary, a
conventional internal number, which, which when combined with the other local-
name local-name components (authority, measure measure, and date), builds a unique
identifier. Uniqueness is achieved by checking against the catalogue
of previously assigned names.</t>
      </section>
      <section anchor="identifier-persistence-considerations">
        <name>Identifier Persistence Considerations</name>
        <t>The persistence of identifiers depends on the durability of the
institutions that assign and administer them. The goal of the LEX
schema is to maintain uniqueness and persistence of all resources
identified by the assigned URNs.</t>
        <t>In particular, the CNR is responsible of for maintaining
the uniqueness of the jurisdiction element; given element. Given that the
jurisdiction is assigned on the basis of the long-held ccTLD
representation of the country (or the TLDN or DN of the organization)
and that the associated code for country or organization associated code is expected to
continue indefinitely, the URN also persists indefinitely.</t>
        <t>The rules for the construction of the name are conceived to delegate
the responsibility of their uniqueness to a set of authorities which that
is identified within each country or organization.</t>
        <t>Therefore, each authority is responsible for assigning URNs which that
have a very long life expectancy and can be expected to remain unique
for the foreseeable future. Practical and political considerations,
as well as diverse local forms of government organization, will
result in different methods of assigning responsibility for different
levels of the name.</t>
        <t>Where this cannot be accomplished by the implementation of an
authoritative hierarchy, it is highly desirable that it be done by
creating consensus around a series of published rules for the
creation and administration of names by institutions and bodies that
operate by means of collaboration rather than compulsion.</t>
        <t>Issuing authorities that operate in more localized scopes, ranging
from the national scope down to the very local, MUST local scope, <bcp14>MUST</bcp14> equally take
responsibility for the persistence of identifiers within their scope.</t>
      </section>
    </section>
    <section anchor="recommendations-for-the-resolution-process">
      <name>Recommendations for the Resolution Process</name>
      <section anchor="the-general-architecture-of-the-system">
        <name>The General
        <name>General Architecture of the System</name>
        <t>The task of the resolution service is that of associating to associate a LEX
identifier with a specific document address on the Internet.  By  In
contrast with systems that can be constructed around rigorous and
enforceable engineering premises, such as DNS, the "lex" namespace
resolver will be expected to cope with a wide variety of inputs
that are incomplete or partially incorrect, particularly those
created by the automated extraction of
references from texts.  In this document,
the result is a particular emphasis on a flexible and robust resolver
design.</t>
        <t>The system has a distributed architecture based on two fundamental
components: a chain of information in the DNS (Domain Name System) and a
series of resolution services from URNs to URLs, each competent
within a specific domain of the namespace.</t>
        <t>The client retrieves the document associated with this URN using the
procedure described in <xref target="RFC3404"/>, which starts with a DNS NAPTR
query.</t>
        <t>A resolution service can delegate the resolution and management of
hierarchically-dependent
hierarchically dependent portions of the name.
Delegation of this responsibility will not be unreasonably withheld
provided that the processes for their resolution and management are
robust and are followed.</t>
        <t>For
<!-- [rfced] Note that we added numbers to this sentence to aid in
readability.  Would updating "in correspondence with the adhesion" as
suggested below further improve clarity?

Original:
   For the "lex" namespace, CNR will maintain in the lex-nameserver.nic.it lex-
   nameserver.nic.it (see <xref target="iana"/>) Section 12) the root zone of the chain
   resolution (equivalent to "lex.urn.arpa", see <xref target="RFC3405"/>) [RFC3405]) and, in
   correspondence with the adhesion (see <xref target="jur-cod-regist"/>) Section 2.2) of a new country
   (e.g., "br") or organization, will update the DNS information with a
   new record to delegate the relative resolution.

Current:
   For the "lex" namespace, CNR will 1) maintain the root zone of the
   chain resolution, equivalent to "lex.urn.arpa" (see [RFC3405]), in
   the lex-nameserver.nic.it (see Section 12) and 2) update the DNS
   information with a new record to delegate the relative resolution in
   correspondence with the adhesion (see Section 2.2) of a new country
   (e.g., "br") or organization.

Perhaps:
   For the "lex" namespace, CNR will 1) maintain the root zone of the
   chain resolution, equivalent to "lex.urn.arpa" (see [RFC3405]), in
   the lex-nameserver.nic.it (see Section 12) and 2) update the DNS
   information with a new record to delegate the relative resolution
   when a new country (e.g., "br") or organization is added (see Section 2.2).
-->

<!-- [rfced] Will readers understand what "This" refers to here?

Original:
   This may be obtained
   by a regular expression that matches the initial part of the URN
   (e.g., "urn:lex:br") and redirects towards the proper zone (e.g.,
   "lex.senado.gov.br").
-->

<t>For the "lex" namespace, CNR will 1) maintain the root zone of the
        chain resolution, equivalent to "lex.urn.arpa" (see <xref
        target="RFC3405"/>), in the lex-nameserver.nic.it (see <xref
        target="iana"/>) and 2) update the DNS information with a new record
        to delegate the relative resolution in correspondence with the
        adhesion (see <xref target="jur-cod-regist"/>) of a new country (e.g.,
        "br") or organization. This may be obtained by a regular expression
        that matches the initial part of the URN (e.g., "urn:lex:br") and
        redirects towards the proper zone (e.g., "lex.senado.gov.br").</t>
        <t>Likewise, the institution responsible for the jurisdiction uniform
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
resolution towards its resolvers on the basis of parts of the uniform
names. In a similar way way, it can delegate the resolution of
country/organization sub-levels (e.g., "urn:lex:br;sao.paolo")
towards the relative zone (e.g., "lex.sao-paolo.gov.br").</t>
        <t>Such a DNS routing chain does not work for all the URN components
containing %-encoded percent-encoded characters. Therefore, when converting a "lex" URN
in UTF-8 code to a DNS query, clients MUST <bcp14>MUST</bcp14> perform any necessary punycode
conversion <xref target="RFC5891"/> before sending the query.</t>
        <t>The resolution service is made up of two elements: a knowledge base
(consisting in a catalogue or a set of transformation rules) and a
software to query the knowledge base itself.</t> base.</t>
      </section>
      <section anchor="catalogues-for-resolution">
        <name>Catalogues for Resolution</name>
        <t>Incompleteness and inaccuracy are rather frequent in legal citations,
and citations;
thus, incomplete or inaccurate uniform names of the referred document
are thus likely to be built from textual references (this is even
more frequent if they are created automatically through a specific
parser). For this reason, the implementation of a catalogue, based on
a relational-database, relational database, is suggested, as it will lead to a higher
flexibility in the resolution process.</t>
        <t>In addition addition, the catalogue must manage the aliases, the various
versions and languages of the same source of law as well as law, and the
related manifestations.</t>
        <t>It is suggested that each enacting authority implements implement its own
catalogue, assigning a corresponding unambiguous uniform name to each
resource.</t>
      </section>
      <section anchor="suggested-resolver-behaviour">
        <name>Suggested Resolver Behaviour</name> Behavior</name>
        <t>First, the resolver SHOULD <bcp14>SHOULD</bcp14> separate the part corresponding to
the partition ID, through the "~" separator, ID from the document name.</t> name, with the "~" separator.</t>
        <t>The resolution process SHOULD <bcp14>SHOULD</bcp14> implement a normalization of the
uniform name to be resolved. This may involve transforming some
components to the canonical form (e.g., filling out the acronyms,
expanding the abbreviations, unifying the institution names,
standardizing the type of measures, etc.). For this function function,
authorities and types of measure registers are useful.</t>
        <t>The resolver SHOULD <bcp14>SHOULD</bcp14> then query the catalogue searching for the URN
which
that corresponds exactly to the given one (normalized if necessary).
Since the names coming from the references may be inaccurate or
incomplete, an iterative, iterative and heuristic approach (based on partial
matches) is indicated. Incomplete
references (not including all the elements to create the canonical
uniform name) are normal and natural; for a human reader, the
reference would be "completed" by contextual understanding of the
reference in the document in which it occurs.</t>

        <t>In this phase, the resolver should use the partition ID information
to retrieve, if it is possible, only the referred partition,
otherwise to return partition;
otherwise, the entire document.</t> document is returned.</t>
        <t>Lacking more specific indications, the resolver SHOULD <bcp14>SHOULD</bcp14> select the
best (most recent) version of the requested source of law, law and
provide all the manifestations with their related items.
A more specific indication in the uniform name to be resolved will,
of course, result in a more selective retrieval, based on any
suggested expression and/or manifestations components (e.g. (e.g., date,
language, format, etc.).</t>
        <t>Finally,
<!-- [rfced] We have updated the sentence below for ease of the reader. Please
let us know any objections.

Original:
   Finally, the resolver SHOULD append to URLs the "#" character
   followed by partition ID, transforming it in a URI fragment for
   browser pointing.

Current:
   Finally, the resolver SHOULD append the "#" character followed by the
   partition ID to URLs, to create URI fragments for browser pointing.
-->
        <t>Finally, the resolver <bcp14>SHOULD</bcp14> append the "#" character
followed by the partition ID to URLs, to create URI fragments for
browser pointing.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Security considerations are those normally associated with the use and
resolution URNs in general. Additional security considerations concerning
the authenticity of a document do not pertain to the LEX specifications,
but they pertain to security and trust issues which that can be addressed with other means,
like digital signature, signatures, data encryption, etc.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>IANA has already registered the "lex" namespace, according to the
template at section 2. Registration has been accomplished as namespace in the
Formal
"Formal URN Namespace Namespaces" registry described by <xref target="RFC8141"/>.</t>
      <t>In addition, to activate a distributed resolution system, the one-off
registration of IANA has registered the following NAPTR record is requested in the URN.ARPA domain:</t>
      <artwork><![CDATA[
lex.urn.arpa.
    IN NAPTR  100  10  ""  ""  ""  lex-nameserver.nic.it.
    ]]></artwork>
      <t>where
      <t>Note that lex-nameserver.nic.it indicates the server of CNR server (see section 2.2) <xref target="jur-cod-regist"/>)
that is responsible for the resolution of the "lex" namespace at the time of this writing.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>

	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2045.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3404.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3405.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5893.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5894.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml"/>

        <reference anchor="ISO.8601.1988" xml:base="https://bib.ietf.org/public/rfc/bibxml2/reference.ISO.8601.1988.xml">
          <front>
            <title>Data elements and interchange formats - Information interchange - Representation of dates and times</title>
            <author>
              <organization>ISO</organization>
            </author>
            <date month="June" year="1988"/>
          </front>
          <seriesInfo name="ISO" value="8601:1988"/>
        </reference>

        <reference anchor="W3C.HTML" target="https://www.w3.org/TR/html/" xml:base="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.HTML.xml">
          <front>
            <title>HTML</title>
            <author/>
          </front>
          <seriesInfo name="W3C REC" value="HTML"/>
          <seriesInfo name="W3C" value="HTML"/>
        </reference>

      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>

        <reference anchor="FRAN">
          <front>
            <title>Technologies for European Integration.  Standards-based Interoperability of Legal Information Systems</title>
            <author initials="E." surname="Francesconi" fullname="Enrico Francesconi">
              <organization>European Press Academic Publishing</organization>
            </author>
            <date year="2007"/>
          </front>
          <seriesInfo name="ISBN" value="978-88-8398-050-3"/>
        </reference>

        <reference anchor="FRBR" target="https://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf">
          <front>
            <title>Functional Requirements for Bibliographic Records</title>
            <author>
              <organization>International Federation of Library Associations and Institutions</organization>
            </author>
            <date month="February" year="2009"/>
          </front>
        </reference>

        <reference anchor="HCPIL" target="https://assets.hcch.net/docs/b093f152-a4b3-4530-949e-65c1bfc9cda1.pdf">
          <front>
            <title>Access to Foreign Law in Civil and Commercial Matters</title>
            <author>
              <organization>The European Commission</organization>
            </author>
            <date month="February" year="2012"/>
          </front>
	  <refcontent>The Hague Conference on Private International Law</refcontent>
        </reference>

        <reference anchor="ISBD">
          <front>
            <title>ISBD: International Standard Bibliographic Description – Consolidated Edition</title>
            <author>
              <organization>The Standing Committee of the IFLA Cataloguing Section Berlin/Munich: De Gruyter Saur</organization>
            </author>
            <date year="2011"/>
          </front>
          <seriesInfo name="ISBN" value="978-3-11-026379-4"/>
        </reference>

<!-- [rfced] FYI - We alphabetized the references as that seemed to be the
intent (only two were out of order).
-->

<!-- [rfced] Please confirm the correct version of the following reference
(2006, 2013, or 2020) and let us know how we should update.

Original:
   [ISO3166-1]
              International Organization for Standardization, "Codes for
              the representation of names of countries and their
              subdivisions - Part 1: Country codes".

Perhaps (a):
   [ISO.3166-1]
              ISO, "Codes for the representation of names of countries
              and their subdivisions - Part 1: Country codes",
	      ISO 3166-1:2006, 2006.

Perhaps (b):
   [ISO.3166-1]
              ISO, "Codes for the representation of names of countries
              and their subdivisions - Part 1: Country codes",
	      ISO 3166-1:2013, 2013.

Perhaps (c):
   [ISO.3166-1]
              ISO, "Codes for the representation of names of countries
              and their subdivisions - Part 1: Country code",
	      ISO 3166-1:2020, 2020.
-->
        <reference anchor="ISO.3166-1">
          <front>
            <title>Codes for the representation of names of countries and their subdivisions - Part 1: Country codes</title>
            <author>
              <organization>ISO</organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="LVI">
          <front>
            <title>Law via the Internet. Free Access, Quality of Information, Effectiveness of Rights</title>
            <author initials="G." surname="Peruginelli" fullname="Ginevra Peruginelli" role="editor">
              <organization>European Press Academic Publishing</organization>
            </author>
            <author initials="M." surname="Ragona" fullname="Mario Ragona" role="editor">
              <organization>European Press Academic Publishing</organization>
            </author>
            <date month="April" year="2009"/>
          </front>
          <seriesInfo name="ISBN" value="9788883980589"/>
        </reference>

        <reference anchor="SART">
          <front>
            <title>Legislative XML for the Semantic Web: Principles, Models, Standards for Document Management</title>
            <author initials="G." surname="Sartor" fullname="Giovanni Sartor">
              <organization/>
            </author>
            <author initials="M." surname="Palmirani" fullname="Monica Palmirani">
              <organization/>
            </author>
            <author initials="E." surname="Francesconi" fullname="Enrico Francesconi">
              <organization/>
            </author>
            <author initials="M." surname="Biasiotti" fullname="Maria Angela Biasotti">
              <organization/>
            </author>
            <date year="2011"/>
          </front>
          <seriesInfo name="ISBN" value="978-94-007-1887-6"/>
        </reference>

<!-- [rfced] We were unable to locate the reference listed below. Please
review the reference entry and confirm it is correct.

Original:
[SPIN]     Spinosa, P., "The Assignment of Uniform Names to Italian
           Legal Documents, URN-NIR 1.4", ITTIG technical Report n.
           8/2010., June 2020.
-->
        <reference anchor="SPIN">
          <front>
            <title>The Assignment of Uniform Names to Italian Legal Documents, URN-NIR 1.4</title>
            <author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa">
              <organization/>
            </author>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="ITTIG" value="technical Report n. 8/2010"/>
        </reference>

        <reference anchor="W3C.RDF-SCHEMA" target="https://www.w3.org/TR/rdf-schema/" xml:base="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.rdf-schema.xml">
          <front>
            <title>RDF Schema 1.1</title>
            <author fullname="Dan Brickley" role="editor"/>
	    <author fullname="R.V. Guha" role="editor"/>
	    <date year="2014" month="February"/>
          </front>
          <seriesInfo name="W3C REC" value="rdf-schema"/>
          <seriesInfo name="W3C" value="rdf-schema"/>
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>The authors of this document wish to thank all the supporters for
giving those who provided
      suggestions and comments.</t>
      <t>They
      <t>The authors are also grateful to the Legislative XML community <xref
      target="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 provided guidance provided <xref
      target="SPIN"/>.</t>
      <t>The authors owe a debt of gratitude to Tom Bruce, <contact fullname="Tom
      Bruce"/>, former director of the Legal Information Institute of the
      Cornell University Law School, for his contribution in revising this
      document and sharing fruitful discussions which that greatly improved the final draft.
      document.  The authors wish to specially thank Marc <contact
      fullname="Marc van Opijnen Opijnen"/> (Dutch Ministry of Security and Justice)
      for his valuable comments on LEX specifications specifications, which contributed to improve the final result,
      improving this document, as well as for the common work aimed to
      harmonize the ECLI and LEX specifications. Thanks also to
Joao <contact
      fullname="Joao Alberto de Oliveira Lima, legislative system analyst Lima"/>, Legislative System Analyst
      of the Brazilian Federal Senate, and to Attila Torcsvari, information
management consultant, <contact fullname="Attila
      Torcsvari"/>, Information Management Consultant, for their detailed
      comments on the first
drafts draft versions of this document, which provided
      significant hints improvements to the final version of the standard, and document. Thanks also to Robert Richards <contact
      fullname="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> document.</t>
      <t>Finally, many thanks go to Loriana Serrotti <contact fullname="Loriana Serrotti"/>, who
      significantly contributed to the first drafting draft versions of this document.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2045" target="https://www.rfc-editor.org/info/rfc2045" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2045.xml">
          <front>
            <title>Multipurpose Internet Mail Extensions (MIME) Part One: Format

<!-- [rfced] Please review each instance of Internet Message Bodies</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
            <date month="November" year="1996"/>
            <abstract>
              <t>This initial document specifies the various headers used U+ notation and let us know if
you would like to describe replace with the structure of MIME messages. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2045"/>
          <seriesInfo name="DOI" value="10.17487/RFC2045"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are character itself.

The <u> element (which can be used to signify provide the requirements in U+ notation) is only
required for cases where the specification. These words non-ASCII characters are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices needed for the Internet Community, and requests discussion and suggestions correct
protocol operation.

For more information, please see:
https://authors.ietf.org/en/non-ascii-characters-in-rfcxml
https://www.rfc-editor.org/styleguide/part2/#nonascii

For examples from published RFCs, please see (search for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3629" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml">
          <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 Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and "non-ASCII"):
https://www.rfc-editor.org/rpc/wiki/doku.php?id=v3_feature_usage

Some examples from this has led to the development of UTF-8, document:

Example 1 (from Section 3.4):

Original:
  (e.g.,
  the object of this memo. UTF-8 has Italian term "sanitU+00E0" replaced into "sanita", the characteristic of preserving French
  term "ministU+00E8re" replaced into "ministere"), in case by
  transliteration (e.g. "MU+00FCnchen" replaced into "muenchen”).

Perhaps:
  For example,
  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 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/rfc3404" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3404.xml">
          <front>
            <title>Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="October" year="2002"/>
            <abstract>
              <t>This document describes a specification for taking Uniform Resource Identifiers (URI) and locating an authoritative server for information about that URI. The method used to locate that authoritative server Italian term "sanità” is replaced by "sanita", the Dynamic Delegation Discovery System. This document French
  term "ministère” is part of a series that replaced by "ministere”, and
  "München” is specified replaced by “muenchen” (transliteration).

Example 2 (from Section 3.4):

Original:
   - unicode = urn:lex:de:stadt.mU+00FCnchen:rundschreiben: ...

Perhaps no changes are needed when the U+ notation appears in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible a "urn:lex"
string like this.
-->

<!-- [rfced] Sourcecode

a) We updated <artwork> to read and understand any document <sourcecode type="abnf"> in this series without reading Section 8. We also
updated the ABNF snippets throughout the others. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3404"/>
          <seriesInfo name="DOI" value="10.17487/RFC3404"/>
        </reference>
        <reference anchor="RFC3405" target="https://www.rfc-editor.org/info/rfc3405" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3405.xml">
          <front>
            <title>Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="October" year="2002"/>
            <abstract>
              <t>This document is fifth in a series from <artwork> to
<sourcecode type="abnf">. Please review.

b) In Section 2.1, we changed the following from <artwork> to
<sourcecode>. Please confirm that this is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: correct. If so, should the "type"
attribute be set?

Original:
  "urn:lex:" NSS

Note: The Comprehensive DDDS" (RFC 3401). It current list of preferred values for "type" is very important available here:
https://www.rfc-editor.org/rpc/wiki/doku.php?id=sourcecode-types. If this list
does not contain an applicable type, then feel free to note that let us know.  Also, it
is impossible acceptable to read and understand any document in this series without reading leave the others. This document specifies an Internet Best Current Practices for "type" attribute not set.

c) In Section 5.8, we changed the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="65"/>
          <seriesInfo name="RFC" value="3405"/>
          <seriesInfo name="DOI" value="10.17487/RFC3405"/>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines following from <artwork> to
<sourcecode>. We set the generic URI syntax and a process for resolving URI references that might be type to "abnf", but please confirm this is
correct. We do not see this in relative form, along with guidelines and security considerations for the use of URIs on Section 8.

Original:
   URN-reference = URN-document ["~" partition-id]

d) In Section 8, please review the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation spacing. For example, would you like to parse the common components of add
a URI reference without knowing blank line after the scheme-specific requirements "alf-dot" definition and remove one of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5234" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over blank lines
after the "alfa" definition? Or is the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences spacing okay?

Original:
   alf-dot = alfanum *alfadot
   alf-dot-hyp = alfanum *(alfadot / "-")

   alf-dot-oth = alfanum *(alfadot / other)

   alfadot = alfanum / "."

   alfa = lowercase / uppercase

   alfanum = alfa / DIGIT / encoded

Perhaps:
   alf-dot = alfanum *alfadot

   alf-dot-hyp = alfanum *(alfadot / "-")

   alf-dot-oth = alfanum *(alfadot / other)

   alfadot = alfanum / "."

   alfa = lowercase / uppercase

   alfanum = alfa / DIGIT / encoded
-->

<!-- [rfced] We see some mismatches between standard BNF and the ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of snippets in the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5646" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml">
          <front>
            <title>Tags for Identifying Languages</title>
            <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/>
            <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/>
            <date month="September" year="2009"/>
            <abstract>
              <t>This document describes
and the structure, content, construction, corresponding lines in Section 8. Please review and let us know
how/if to update.

a) NSS/NSS-lex definition

Section 2.1:
   NSS = jurisdiction ":" local-name

Section 8:
   NSS-lex = jurisdiction ":" local-name

b) date-iso definition

Section 3.6:
   date-iso = yyyy-mm-dd

Section 8:
   date-iso = year "-" month "-" day

c) date definition - note the spaces after "[" and semantics before "]" in Section 3.6
that don't appear in Section 8.

Section 3.6:
   date = date-iso [ "|" date-loc ]

Section 8:
   date = date-iso ["|" date-loc]

d) manifestation definition

Section 5.7:
       manifestation = editor ":" format
                       [":" component [":" feature]]

Section 8:
   manifestation = format ":" editor
   [":" component [":" feature]]

e) numbers definition

Section 6.3.4:
   numbers = document-id *("," document-id)

Section 8:
   numbers = (document-id *("," document-id)) / number-lex

f) version definition - note the indent of language tags for use second line

Section 7.1.2:
      version = (amendment-date / specification)
                *(";" (event-date / event))

Section 8:
   version = (amendment-date / specification)
          *(";" (event-date / event))
-->

<!-- [rfced] We updated some <artwork> to <ul>. We have noted these instances
below along with further edits made to each. Please review these in cases where it is desirable all
output formats (txt, html, pdf) and let us know any concerns.

a) Section 3.4: We updated the following <artwork> to indicate be nested lists (<ul>),
with just the language used in an information object. It "urn:lex" part tagged as <artwork>. We also describes how to register values for use in language tags and made the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for following
changes:

- replaced the Internet Community, "=" with ":"
- updated capitalization (of ascii, unicode, and requests discussion utf-8, and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="47"/>
          <seriesInfo name="RFC" value="5646"/>
          <seriesInfo name="DOI" value="10.17487/RFC5646"/>
        </reference>
        <reference anchor="RFC5891" target="https://www.rfc-editor.org/info/rfc5891" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml">
          <front>
            <title>Internationalized Domain Names in Applications (IDNA): Protocol</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, punycode)
- updated the relationship text starting with "assuming that..." to the older specification, and important terminology are provided be a note in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in
<aside> element.

Original:
   a way circular adopted by the Municipality of Munich (Rundschreiben der
     Stadt MU+00FCnchen):
   - ascii = urn:lex:de:stadt.munchen:rundschreiben:...
   - unicode = urn:lex:de:stadt.mU+00FCnchen:rundschreiben:...
   - utf-8 = urn:lex:de:stadt.m%xC3%xBCnchen:rundschreiben:...
   - punycode = urn:lex:de:stadt.xn-mnchen-3ya:rundschreiben:...

   a state law of the Russian Federation (latin: gosudarstvo zakon;
     cyrillic: U+0441U+043EU+0441U+0442U+043EU+044FU+043DU+0438U+0435
     U+0437U+0430U+043AU+043EU+043D):
   - ascii = urn:lex:ru:gosudarstvo:zakon:...
   - unicode = urn:lex:ru:U+0441U+043EU+0441U+0442U+043EU+044FU+043D
               U+0438U+0435:U+0437U+0430U+043AU+043EU+043D:...
   - utf-8 = urn:lex:ru:%xD1%x81%xD0%xBE%xD1%x81%xD1%x82%xD0%xBE%xD1
             %x8F%xD0%xBD%xD0%xB8%xD0%xB5:%xD0%xB7%xD0%xB0%xD0%xBA
             %xD0%xBE%xD0%xBD:...
   - punycode = urn:lex:ru:xn-80aebe3cdmfdkg:xn-80ankme:...

   assuming that does not require changes to the DNS itself. IDNA Russia jurisdiction-code is only meant for processing domain names, not free text. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5891"/>
          <seriesInfo name="DOI" value="10.17487/RFC5891"/>
        </reference>
        <reference anchor="RFC5893" target="https://www.rfc-editor.org/info/rfc5893" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5893.xml">
          <front>
            <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="C. Karp" initials="C." surname="Karp"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>The use of right-to-left scripts expressed
   in Internationalized Domain Names (IDNs) ASCII ("ru"),
   while the Cyrillic version ("U+0440U+0444") has presented several challenges. This memo provides a new Bidi rule for Internationalized Domain Names for Applications (IDNA) labels, based on the encountered problems
   puny-code "xn-p1ai".

b) Section 3.6: We updated the following <artwork> to be <ul>, with some scripts and some shortcomings in just the 2003 IDNA Bidi criterion. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5893"/>
          <seriesInfo name="DOI" value="10.17487/RFC5893"/>
        </reference>
        <reference anchor="RFC5894" target="https://www.rfc-editor.org/info/rfc5894" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5894.xml">
          <front>
            <title>Internationalized Domain Names for Applications (IDNA): Background, Explanation,
character strings tagged <artwork>. We also removed the semicolon after the
first item, the close parentheses and Rationale</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>Several years have passed since period after the original protocol for Internationalized Domain Names (IDNs) was completed second item, and deployed. During that time, a number of issues have arisen, including the need to update
quotation marks.

Original:
   - in Hebrew characters:
     "U+05DBU+05F4U+05D0.U+05D0U+05B1U+05DCU+05D5U+05BCU+05DC.U+05EA
      U+05E9U+05E0U+05F4U+05D8";

   - in UTF-8 code:
     "%x5c%x75%x30%x35%x44%x42%x5c%x75%x30%x35%x46%x34%x5c%x75%x30%x35
      %x44%x30%x2e%x5c%x75%x30%x35%x44%x30%x5c%x75%x30%x35%x42%x31%x5c
      %x75%x30%x35%x44%x43%x5c%x75%x30%x35%x44%x35%x5c%x75%x30%x35%x42
      %x43%x5c%x75%x30%x35%x44%x43%x2e%x5c%x75%x30%x35%x45%x41%x5c%x75
      %x30%x35%x45%x39%x5c%x75%x30%x35%x45%x30%x5c%x75%x30%x35%x46%x34
      %x5c%x75%x30%x35%x44%x38").

c) Section 5.4: We updated the system following <artwork> to deal be <ul>, with newer versions of Unicode. Some of these issues require tuning just
the "urn:lex" parts tagged as <artwork>.

Original:
   - 4/59 Judgment of the existing protocols EEC Court of Justice 04/04/1960, Mannesmann
     AG and others / ECSC High Authority
     urn:lex:eec.lex.arpa:court.justice:judgement:1960-04-04;4-59

   - 4/59 Order of the tables on which they depend. This document provides an overview EEC Court of a revised system Justice 18/05/1960, Mannesmann AG
     and provides explanatory material for its components. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5894"/>
          <seriesInfo name="DOI" value="10.17487/RFC5894"/>
        </reference>
        <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml">
          <front>
            <title>Guidelines for Writing an IANA Considerations others / ECSC High Authority
     urn:lex:eec.lex.arpa:court.justice:order:1960-05-18;4-59

d) Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use 5.7: We updated the following <artwork> to be <ul>, with just the
"urn:lex" parts tagged as <artwork>. We also removed the quotation marks
around the "urn:lex" parts.

Original:
   - PDF format (vers. 1.7) of points the whole act edited by the Italian
     Parliament:
     "urn:lex:it:stato:legge:2000-04-03;56$application-pdf;
     1.7:parlamento.it"
   - XML format (version 2.2 DTD NIR) of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses text of the act and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled PDF
     format (version 1.7) of the "Figura 1" (figure 1) contained in the
     body, edited by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments Italian Senate:
     "urn:lex:it:stato:legge:2000-04-03;56$text-xml;dtd-nir-2.2:
     senato.it:testo"
     "urn:lex:it:stato:legge:2000-04-03;56$application-pdf;1.7:
     senato.it:figura.1"

e) Section 5.7: We removed the close parentheses at the end of this artwork
block. We also removed the quotation marks.

Original:
   "urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
   @original:es$text-html:juradmin.eu;jurifast:todo:anonimo")

Current:
   "urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
   @original:es$text-html:juradmin.eu;jurifast:todo:anonimo"

Perhaps:
   urn:lex:eu:tribunal.justicia:sentencia:2009-06-11;33-08
   @original:es$text-html:juradmin.eu;jurifast:todo:anonimo
-->

<!-- [rfced] Please review each artwork element in a given registry prudently, guidance describing the conditions under which new values current xml
file. Specifically, should any artwork element be assigned, tagged as well as when and how modifications to existing values can be made, is needed. This document defines a framework <sourcecode>,
<ul>, <t>, or another element?
-->

<!-- [rfced] FYI - We have added expansions for the documentation following abbreviation(s)
upon first use per Section 3.6 of these guidelines by specification authors, RFC 7322 ("RFC Style Guide"). Please
review each expansion in order to assure that the provided guidance for document carefully to ensure correctness.

Country Code Top-Level Domain (ccTLD)
-->

<!-- [rfced] Please review the IANA Considerations is clear and addresses "Inclusive Language" portion of the various issues that online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are likely in the operation needed.  Updates of a registry.</t>
              <t>This this nature typically
result in more precise language, which is helpful for readers.

For example, please consider whether the third edition of following term should be updated:

native

Additionally, please consider whether "tradition" should be updated for
clarity.  While the NIST website
<https://www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions#table1>
indicates that this document; term is potentially biased, it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8141" target="https://www.rfc-editor.org/info/rfc8141" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml">
          <front>
            <title>Uniform Resource Names (URNs)</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="April" year="2017"/>
            <abstract>
              <t>A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that also ambiguous.
"Tradition" is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. With regard to URN syntax, this document defines subjective term, as it is not the canonical syntax same for URNs (in a way that is consistent everyone.  -->

<!-- [rfced] Please review the capitalization and use of quotation marks with URI syntax), specifies methods for determining URN-equivalence,
"lex" and discusses URI conformance. With regard to URN namespaces, this document specifies "LEX". Is there a method pattern to follow for defining a URN namespace and associating it with a namespace identifier, these? We listed some
specific scenarios below; please review and it describes procedures let us know if any updates
are needed for registering namespace identifiers consistency.

a) We see inconsistency with the Internet Assigned Numbers Authority (IANA). This document obsoletes both RFCs 2141 and 3406.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8141"/>
          <seriesInfo name="DOI" value="10.17487/RFC8141"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be following forms:

lex schema vs. LEX schema
lex URN vs. "lex" URN vs. LEX URN

b) We also see these phrases:

"lex” namespace
"lex” NSS
"lex” space
"lex” NID syntax

LEX identifier
LEX name
LEX identifier
LEX governance
LEX naming convention
LEX specifications

c) We also see "LEX" used by itself in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage following:

Original:
  A Uniform Resource Name (URN) Namespace for Sources of Law (LEX)
    Note: This is the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8288" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml">
          <front>
            <title>Web Linking</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="October" year="2017"/>
            <abstract>
              <t>This specification defines a model for document title. Please also see question #1.

  LEX does this by splitting the relationships identifier
  into parts.

  LEX assumes no
  particular relationship between resources on the Web ("links") and the type originator of those relationships ("link relation types").</t>
              <t>It also defines the serialisation document,

  Registration of such links in HTTP headers with the Link header field.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8288"/>
          <seriesInfo name="DOI" value="10.17487/RFC8288"/>
        </reference>
        <reference anchor="ISO.8601.1988" xml:base="https://bib.ietf.org/public/rfc/bibxml2/reference.ISO.8601.1988.xml">
          <front>
            <title>Data elements and interchange formats - Information interchange LEX
-->

<!-- [rfced] Terminology

a) FYI - Representation of dates and times</title>
            <author>
              <organization>International Organization for Standardization</organization>
            </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:base="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.HTML.xml">
          <front>
            <title>HTML</title>
            <author/>
          </front>
          <seriesInfo name="W3C REC" value="html"/>
          <seriesInfo name="W3C" value="html"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="FRAN">
          <front>
            <title>Technologies for European Integration.  Standards-based Interoperability We updated instances of Legal Information Systems</title>
            <author initials="E." surname="Francesconi" fullname="Enrico Francesconi">
              <organization>European Press Academic Publishing</organization>
            </author>
            <date year="2007"/>
          </front>
          <seriesInfo name="ISBN" value="978-88-8398-050-3"/>
        </reference>
        <reference anchor="FRBR" target="https://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf">
          <front>
            <title>Functional Requirements for Bibliographic Records</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="HCPIL" target="https://assets.hcch.net/docs/b093f152-a4b3-4530-949e-65c1bfc9cda1.pdf">
          <front>
            <title>The Hague Conference on Private International Law "Access "URN LEX" to Foreign Law "LEX URN".

b) We note inconsistencies in Civil and Commercial Matters. Conclusions and Recommendations"</title>
            <author>
              <organization>The European Commission</organization>
            </author>
            <date year="2012"/>
          </front>
        </reference>
        <reference anchor="ISBD">
          <front>
            <title>International Standard Bibliographic Description - Consolidated Edition.</title>
            <author>
              <organization>The Standing Committee of the IFLA Cataloguing Section Berlin/Munich\: De Gruyter Saur</organization>
            </author>
            <date year="2011"/>
          </front>
          <seriesInfo name="ISBN" value="978-3-11-026379-4"/>
        </reference>
        <reference anchor="ISO3166-1">
          <front>
            <title>Codes for terms listed below. We chose the representation of names of countries and their subdivisions -- Part 1: Country codes</title>
            <author>
              <organization>International Organization for Standardization</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="LVI">
          <front>
            <title>Law via form on the Internet. Free Access, Quality of Information, Effectiveness of Rights</title>
            <author initials="G." surname="Peruginelli" fullname="Ginevra Peruginelli" role="editor">
              <organization>European Press Academic Publishing</organization>
            </author>
            <author initials="M." surname="Ragona" fullname="Mario Ragona" role="editor">
              <organization>European Press Academic Publishing</organization>
            </author>
            <date year="2008"/>
          </front>
          <seriesInfo name="ISBN" value="9788883980589"/>
        </reference>
        <reference anchor="SART">
          <front>
            <title>Legislative XML for
right. Please let us know any objections.

urn-lex ID vs. urn:lex ID
UNICODE vs. Unicode
Registrar vs. Jurisdictional Registrar
%-encoded vs. percent-encoded

c) We note inconsistencies in the Semantic Web. Principles, Models, Standards for Document Management, Law, Governance and Technology Series</title>
            <author initials="G." surname="Sartor" fullname="Giovanni Sartor">
              <organization/>
            </author>
            <author initials="M." surname="Palmirani" fullname="Monica Palmirani">
              <organization/>
            </author>
            <author initials="E." surname="Francesconi" fullname="Enrico Francesconi">
              <organization/>
            </author>
            <author initials="M." surname="Biasiotti" fullname="Maria Angela Biasotti">
              <organization/>
            </author>
            <date year="2011"/>
          </front>
          <seriesInfo name="ISBN" value="978-94-007-1887-6"/>
        </reference>
        <reference anchor="SPIN">
          <front>
            <title>The Assignment terms below throughout the text. Should
these be uniform? If so, please let us know which form is preferred.

http vs. HTTP (in the context of Uniform Names to Italian Legal Documents, URN-NIR 1.4</title>
            <author initials="P." surname="Spinosa" fullname="PierLuigi Spinosa">
              <organization/>
            </author>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="ITTIG" value="technical Report n. 8/2010."/>
        </reference>
        <reference anchor="W3C.rdf-schema" target="https://www.w3.org/TR/rdf-schema/" xml:base="https://bib.ietf.org/public/rfc/bibxml4/reference.W3C.rdf-schema.xml">
          <front>
            <title>RDF Schema 1.1</title>
            <author/>
          </front>
          <seriesInfo name="W3C REC" value="rdf-schema"/>
          <seriesInfo name="W3C" value="rdf-schema"/>
        </reference>
      </references>
    </references>
    <?line 2288?>

  </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 "http-based")
local-name vs. local name
body vs. Body
jurisdiction code vs. jurisdiction-code
Member State vs. member state
-->

</back> </rfc>