﻿<?xml version="1.0" encoding="utf-8"?>
<lgr xmlns="urn:ietf:params:xml:ns:lgr-1.0">
  <meta>
    <version comment="Second Level Reference LGR">2</version>
    <date>2024-10-25</date>
    <language>und-Geor</language>
    <unicode-version>11.0.0</unicode-version>
    <description type="text/html"><![CDATA[
       <div class="instructions">
<h2>INSTRUCTIONS</h2>
  <ul>
    <li>These instructions cover how to adopt an LGR based on this reference LGR for a given
    zone and how to prepare the file for deposit in the IANA Repository of IDN Practices.</li>
    <li>As described  the IANA procedure (https://www.iana.org/help/idn-repository-procedure) an 
    LGR MUST contain the following elements in its header:
      <ul style="list-style-type:square;">
        <li>Script or Language Designator (see below for guidance) </li>
        <li>Version Number (this must increase with each amendment to the LGR, even if the updates 
            are limited to the header itself) </li>
        <li>Effective Date (the date at which the policy becomes applicable in operational use) </li>
        <li>Registry Contact Details (contact name, email address, and/or phone number)</li>
      </ul>
    </li>
    <li>The following information is optional:
    <ul style="list-style-type:square;">
    <li>Document creation date</li>
    <li>Applicable Domain(s)</li>
    <li>Changes made to the Reference LGR before adopting</li>
    </ul>
    </li>
  </ul>
  <p>Please add or modify the following items in the <b>XML source code for this file</b> before 
  depositing the document in the IANA Repository. (https://www.iana.org/domains/idn-tables)</p>
<h3>Meta Data</h3>
<p>Note: version numbers start at 1. RFC 7940 recommends using simple integers. The version comment is optional, 
   please replace or delete the default comment. Version comments may be used by some tools as part of the page header.</p>
  <p><code>&lt;version comment=&quot;</code>[Please replace (or delete) the optional comment]<code>&quot;&gt;</code>[Please fill in version number, starting at 1]<code>&lt;/version&gt;</code></p>
  <p><code>&lt;date&gt;</code>[Please fill in with publication date, in YYYY-MM-DD format]<code>&lt;/date&gt;</code></p>
  <p><code>&lt;validity-start&gt;</code>[Please fill in effective date, in YYYY-MM-DD format]<code>&lt;/validity-start&gt;</code></p>
  <p>Note: the scope element may be repeated, so that the same document can serve for multiple domains.</p>
  <p><code>&lt;scope type=&quot;domain&quot;&gt;</code>[Please provide, in &quot;.domain&quot; format]<code>&lt;/scope&gt;</code></p>
<p><strong>Registry Contact Information:</strong></p>
  <p>Please fill in the <a href="#registry_contact_details">Registry Contact Details</a>.</p>
<p><strong>Change History</strong></p>
  <p>If you made technical modifications to the LGR, please summarize them in the <a href="#change_history">Change History</a> (and also note the details in the appropriate section of the description).</p>
<p>PLEASE DELETE THESE INSTRUCTIONS BEFORE DEPOSITING THE DOCUMENT</p></div>
       
       <section id="registry_contact_details">
<h2>Registry Contact Details</h2>
<ul style="list-style:none;">
<li><b>Contact Name:</b> [Please fill in Contact Name]</li>
<li><b>Email address:</b> [Please fill in Email address]</li>
<li><b>Phone Number:</b> [Please fill in optional Phone Number]</li>
</ul>
</section>

        <h1>Label Generation Rules for the Georgian Script</h1>

        <h2>Overview</h2>
        
        <p>This document specifies a reference set of Label Generation Rules for Georgian Mkhedruli (modern) for the second level
        domain or domains identified above. 
        The starting point for the development of this LGR can be found in the related Root Zone LGR [RZ-LGR-Geor]. 
        The format of this file follows [RFC 7940]. 
        This LGR is adapted from the “Reference LGR for the Second Level for the Georgian Mkhreduli” [Ref-LGR-und-Geor], for details, see <a href="#change_history">Change History</a> below.</p>

        <p>For details and additional background on the Georgian script, see “Proposal for a Georgian Script Root Zone LGR” [Proposal-Georgian].</p>

        <h2>Repertoire</h2>
        <p>The repertoire contains 33 code points for letters used by 
        languages that are actively written in the Mkhedruli alphabet. 
        The repertoire is a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Georgian].
        (The proposal cited has been adopted for the Georgian script portion of the Root Zone LGR.)</p>

        <p>For the second level, the repertoire has been augmented with the ASCII digits, U+0030 to U+0039, plus U+002D HYPHEN-MINUS, for a total of 44 repertoire elements.</p>

        <p><b>Repertoire Listing:</b> Each code point or range is tagged with the script or scripts with which the code point is used and one or more other character categories. For each repertoire element,
      one or more references document sufficient justification for inclusion in the repertoire; see the <a href="#ref_desc_sec_References">“References”</a> below.
     For code points in the repertoire, comments identify the language using the code point.</p>

        <h2>Variants</h2>

        <p>The variants defined in this LGR are limited to those required for use in zones not shared with any other script. 
    As such, this LGR does not define cross-script variants. 
    However, using this LGR concurrently with any LGR for Myanmar in the same zone will create potential cross-script issues. For details, see Section 6, “Variants” in [Proposal-Georgian].
    Mitigation of these cross-script variants can be addressed by using the Common LGR. 
    For details, see Section 3, 
    “Use of Multiple Reference LGRs in the Same Zone” in [Level-2-Overview].
    In addition to variants defined by this LGR, the full variant information related to this script and required for concurrent use with the Myanmar LGR(s) can be found 
    in the following LGR: [Ref-LGR-Myanmar-Full-Variant-Script]
  </p>

        <p>This version of the LGR defines no variants. For details, see Section 6, “Variants” in [Proposal-Georgian].</p>

        <p><b>Additional variants</b> When integrated to be used with another script LGR in the same zone, this LGR may inherit additional blocked cross-script
    variants by integration; they may not be listed here unless they reflect resulting in-script variants.  
    Always use an applicable merged, or Common LGR created by integration for determining cross-script collisions of labels.</p>

        <p>The specification of variants in this LGR follows the guidelines in [RFC 8228].</p>

        <h2>Character Classes</h2>

        <p>This LGR does not define named character classes.</p>

        <h2>Whole Label Evaluation (WLE) and Context Rules</h2>
        <h3>Common Rules</h3>

        <p>By default, the LGR includes the rules and actions to implement the following restrictions mandated by the IDNA protocol. They are marked with &#x235F;.</p>
       <ul>
       <li><b>Hyphen Restrictions</b> &mdash; restrictions on the allowable placement of hyphens (no leading/ending hyphen
             and no hyphen in positions 3 and 4). These restrictions are described in Section 4.2.3.1 of RFC 5891 [150]. 
             They are implemented here as context rule on U+002D (-) HYPHEN-MINUS.</li>
          <li><b>Leading Combining Marks</b>   &mdash;  restrictions on the allowable placement of combining marks
             (no leading combining mark). This rule is described in Section 4.2.3.2 of RFC 5891 [150].</li>
       </ul>

        <h3>Default Actions</h3> 

        <p>This LGR includes the default actions for LGRs as well as the action needed to
        invalidate labels with misplaced combining marks. They are marked with &#x235F;.
        For a description see [RFC 7940].</p>

        <h3>Georgian-specific Rules</h3>

        <p>This LGR does not define rules specific to the Georgian script.</p>

        <h2>Methodology and Contributors</h2>

        <p>The LGR in this document has been adapted from the corresponding Reference LGR for the Second Level. The Second Level Reference LGR for the Georgian Mkhreduli was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Georgian 
       script and information contained or referenced therein; see [RZ-LGR-Geor]. Suitable extensions for the second level have been applied according to the [Guidelines] and with community input. 
       The original proposal for a Root Zone LGR for the Georgian script, that this LGR is based on, was developed by the Georgian Generation Panel. 
       For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Georgian], as well as [RZ-LGR-Overview].</p>
        
        <section id="change_history">
        <h3>Changes from Version Dated 15 December 2020</h3> <p>Unicode Version has been updated.</p>

        <h3>Changes from Version Dated 25 October 2024</h3>
        <p>Adopted from the Second Level Reference LGR for the Georgian Mkhreduli [Ref-LGR-und-Geor] without normative changes.</p>
        </section>

        <h2>References</h2> 
        <p>The following general references are cited in this document: </p>
        <dl class="references">
        <dt>[Guidelines]</dt>
        <dd>ICANN, “Guidelines for Developing Reference LGRs for the Second Level”, (Los Angeles, California: ICANN, 27 May 2020), https://www.icann.org/en/system/files/files/lgr-guidelines-second-level-27may20-en.pdf</dd>
        <dt>[Level-2-Overview]</dt>
        <dd>Internet Corporation for Assigned Names and Numbers, (ICANN),“Reference Label Generation Rules (LGR) for the Second Level: Overview and Summary” (PDF), 
     (Los Angeles, California: ICANN, 25 October 2024), https://www.icann.org/en/system/files/files/level2-lgr-overview-summary-25oct24-en.pdf
      </dd>
        <dt>[Proposal-Georgian]</dt>
        <dd><i>Proposal for the Georgian Script Root Zone LGR</i>, 14 November 2016,
         https://www.icann.org/en/system/files/files/proposal-georgian-lgr-24nov16-en.pdf</dd> 
        <dt>[Ref-LGR-und-Geor]</dt>
        <dd>ICANN, Second Level Reference Label Generation Rules for the Georgian Mkhreduli (und-Geor), 25 October 2024 (XML)
      https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-25oct24-en.xml
      non-normative HTML presentation: https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-25oct24-en.html</dd>
        <dt>[Ref-LGR-Myanmar-Full-Variant-Script]</dt>
        <dd>ICANN, Second Level Reference Label Generation Rules for the Myanmar Script (und-Mymr), 25 October 2024 (XML)
      https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-25oct24-en.xml
      non-normative HTML presentation: https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-25oct24-en.html</dd>
        <dt>[Unicode 11.0.0]</dt>
        <dt>[RFC 7940]</dt>
        <dd>Davies, K. and A. Freytag, “Representing Label Generation Rulesets Using XML”, 
     RFC 7940, August 2016, https://www.rfc-editor.org/info/rfc7940</dd>
        <dt>[RFC 8228]</dt>
        <dd>A. Freytag, “Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels”, RFC 8228, August 2017,
    https://www.rfc-editor.org/info/rfc8228</dd>
        <dt>[RZ-LGR-Overview]</dt>
        <dd>Integration Panel, “Root Zone Label Generation Rules (RZ LGR-5): Overview and Summary”, 26 May 2022 (PDF), https://www.icann.org/sites/default/files/lgr/rz-lgr-5-overview-26may22-en.pdf</dd>
        <dt>[RZ-LGR-Geor]</dt>
        <dd>ICANN, Root Zone Label Generation Rules for the Georgian Script (und-Geor), 26 May 2022 (XML)
      https://www.icann.org/sites/default/files/lgr/rz-lgr-5-georgian-script-26may22-en.xml</dd>

        <dd>The Unicode Consortium. The Unicode Standard, Version 11.0.0, (Mountain View, CA: The Unicode Consortium, 2018. ISBN 978-1-936213-19-1) 
     https://www.unicode.org/versions/Unicode11.0.0/</dd>
        </dl>

        <p>For references consulted particularly in designing the repertoire for the Georgian Mkhreduli for the second level 
      please see details in the <a href="#table_of_references">Table of References</a> below.</p>

     <p>Reference [0] refers to the Unicode Standard version in which corresponding code points 
      were initially encoded. Reference [100] corresponds to a source given in [Proposal-Georgian] for justifying 
      the inclusion of for the corresponding code points. Entries in the table may have
        multiple source reference values. 
        In the listing of <a href="#whole_label_evaluation_and_context_rules">whole label evaluation and context rules</a>,
        reference [150] indicates the source for common rules.</p>
]]></description>
    <references>
      <reference id="0" comment="Any code point originally encoded in Unicode Version 1.1">The Unicode Standard, Version 1.1</reference>
      <reference id="100">Omniglot Georgian Mkhedruli, https://www.omniglot.com/writing/georgian.htm#mkhedruli</reference>
      <reference id="150">RFC 5891, Internationalized Domain Names in Applications (IDNA): Protocol https://tools.ietf.org/html/rfc5891</reference>
    </references>
  </meta>
  <data>
    <char cp="002D" not-when="hyphen-minus-disallowed" tag="sc:Zyyy" ref="0" comment="HYPHEN-MINUS; &#x235F;" />
    <char cp="0030" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT ZERO; &#x235F;" />
    <char cp="0031" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT ONE; &#x235F;" />
    <char cp="0032" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT TWO; &#x235F;" />
    <char cp="0033" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT THREE; &#x235F;" />
    <char cp="0034" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT FOUR; &#x235F;" />
    <char cp="0035" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT FIVE; &#x235F;" />
    <char cp="0036" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT SIX; &#x235F;" />
    <char cp="0037" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT SEVEN; &#x235F;" />
    <char cp="0038" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT EIGHT; &#x235F;" />
    <char cp="0039" tag="Common-digit sc:Zyyy" ref="0" comment="DIGIT NINE; &#x235F;" />
    <char cp="10D0" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D1" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D2" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D3" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D4" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D5" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D6" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D7" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D8" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10D9" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DA" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DB" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DC" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DD" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DE" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10DF" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E0" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E1" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E2" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E3" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E4" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E5" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E6" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E7" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E8" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10E9" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10EA" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10EB" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10EC" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10ED" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10EE" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10EF" tag="sc:Geor" ref="0 100" comment="Georgian" />
    <char cp="10F0" tag="sc:Geor" ref="0 100" comment="Georgian" />
  </data>
  <!--Rules section goes here-->
  <rules>
    <!--Character class definitions go here-->
    <!--Whole label evaluation and context rules go here-->
    <rule name="leading-combining-mark" ref="150" comment="RFC 5891 restrictions on placement of combining marks &#x235F;">
      <start />
      <union>
        <class property="gc:Mn" />
        <class property="gc:Mc" />
      </union>
    </rule>
    <rule name="hyphen-minus-disallowed" ref="150" comment="RFC 5891 restrictions on placement of U+002D HYPHEN-MINUS &#x235F;">
      <choice>
        <rule comment="no leading hyphen">
          <look-behind>
            <start />
          </look-behind>
          <anchor />
        </rule>
        <rule comment="no trailing hyphen">
          <anchor />
          <look-ahead>
            <end />
          </look-ahead>
        </rule>
        <rule comment="no consecutive hyphens in third and fourth position in the label">
          <look-behind>
            <start />
            <any />
            <any />
            <char cp="002D" comment="hyphen-minus" />
          </look-behind>
          <anchor />
        </rule>
      </choice>
    </rule>
    <!--Action elements go here - order defines precedence-->
    <action disp="invalid" match="leading-combining-mark" ref="150" comment="labels with leading combining marks are invalid &#x235F;" />
    <action disp="invalid" any-variant="out-of-repertoire-var" comment="any variant label with a code point out of repertoire is invalid &#x235F;" />
    <action disp="blocked" any-variant="blocked" comment="any variant label containing blocked variants is blocked &#x235F;" />
    <action disp="allocatable" all-variants="allocatable" comment="variant labels with all variants allocatable are allocatable &#x235F;" />
    <action disp="valid" comment="catch all (default action) &#x235F;" />
  </rules>
</lgr>