Registry Contact Details

• Contact Name: [Please fill in Contact Name]
• Email address: [Please fill in Email address]
• Phone Number: [Please fill in optional Phone Number]

Label Generation Rules for the Georgian Script

Overview

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 Change History below.

For details and additional background on the Georgian script, see “Proposal for a Georgian Script Root Zone LGR” [Proposal-Georgian].

Repertoire

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

For the second level, the repertoire has been augmented with the ASCII digits, U+0030 0 to U+0039 9, plus U+002D - HYPHEN-MINUS, for a total of 44 repertoire elements.

Repertoire Listing: Each code point or range is tagged with the script or scripts with which the code point is used, and one or more references documenting sufficient justification for inclusion in the repertoire, see “References” below. Comments provide additional information for some code points.

Variants

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]

This version of the LGR defines no variants. For details, see Section 6, “Variants” in [Proposal-Georgian].

Additional variants 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.

The specification of variants in this LGR follows the guidelines in [RFC 8228].

Character Classes

This LGR does not define named character classes.

Whole Label Evaluation (WLE) and Context Rules

Common Rules

By default, the LGR includes the rules and actions to implement the following restrictions mandated by the IDNA protocol. They are marked with ⍟.

• Hyphen Restrictions — 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.
• Leading Combining Marks — 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].

Default Actions

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 ⍟. For a description see [RFC 7940].

Georgian-specific Rules

This LGR does not define rules specific to the Georgian script.

Methodology and Contributors

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

Changes from Version Dated 15 December 2020

Unicode Version has been updated.

Changes from Version Dated 24 January 2024

Adopted from the Second Level Reference LGR for the Georgian Mkhreduli [Ref-LGR-und-Geor] without normative changes.

References

The following general references are cited in this document:

[Guidelines]

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

[Level-2-Overview]

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, 24 January 2024),
https://www.icann.org/en/system/files/files/level2-lgr-overview-summary-24jan24-en.pdf

[Proposal-Georgian]

Proposal for the Georgian Script Root Zone LGR, 14 November 2016,
https://www.icann.org/en/system/files/files/proposal-georgian-lgr-24nov16-en.pdf

[Ref-LGR-und-Geor]

ICANN, Second Level Reference Label Generation Rules for the Georgian Mkhreduli (und-Geor), 24 January 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-24jan24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-georgian-script-24jan24-en.html

[Ref-LGR-Myanmar-Full-Variant-Script]

ICANN, Second Level Reference Label Generation Rules for the Myanmar Script (und-Mymr), 24 January 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-24jan24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-myanmar-full-variant-script-24jan24-en.html

[Unicode 11.0.0]

[RFC 7940]

Davies, K. and A. Freytag, “Representing Label Generation Rulesets Using XML”, RFC 7940, August 2016,
https://www.rfc-editor.org/info/rfc7940

[RFC 8228]

A. Freytag, “Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels”, RFC 8228, August 2017,
https://www.rfc-editor.org/info/rfc8228

[RZ-LGR-Overview]

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

[RZ-LGR-Geor]

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

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/

For references consulted particularly in designing the repertoire for the Georgian Mkhreduli for the second level please see details in the Table of References below.

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 whole label evaluation and context rules, reference [150] indicates the source for common rules.

Character Classes

Implicit (except script)	1
Implict defined by script tag	2

The following table lists all named and implicit classes with their definition and a list of their members intersected with the current repertoire (for larger classes, this list is elided).

Name	Definition	Count	Members or Ranges	Ref	Comment
implicit	Tag=Common-digit	10	{0030-0039}		Any character tagged as Common-digit
implicit	Tag=sc:Geor	33	{10D0-10F0}		Any character tagged as Georgian
implicit	Tag=sc:Zyyy	11	{002D 0030-0039}		Any character tagged as Common

Legend

Members or Ranges

Lists the members of the class as code points (xxx) or as ranges of code points (xxx-yyy). Any class too numerous to list in full is elided with "...".

Tag=ttt

A named or implicit class defined by all code points that share the given tag value (ttt).

Implicit

An anonymous class implicitly defined based on tag value and for which there is no named equivalent.

Whole label evaluation and context rules

Number of rules	2
Used to trigger actions	1
Used as context rule (C)	1
Anchored context rules	1

The following table lists all named rules defined in the LGR and indicates whether they are used as trigger in an action or as context (when or not-when) for a code point or variant.

Name	Regular Expression	Used as Trigger	Anchor	Used as Context	Ref	Comment
leading-combining-mark	(start)[∅=[[∅=\p{gc=Mn}] ∪ [∅=\p{gc=Mc}]]]	✔			[150]	RFC 5891 restrictions on placement of combining marks ⍟
hyphen-minus-disallowed	(((start))← ⚓︎)|(⚓︎ →((end)))|(((start)..\u002D)← ⚓︎)		✔	C	[150]	RFC 5891 restrictions on placement of U+002D - ⍟

Legend

Used as Trigger

This rule triggers one of the actions listed below.

Used as Context

This rule defines a required or prohibited context for a code point C or variant V.

Anchor

This rule has a placeholder for the code point for which it is evaluated.

Regular Expression

A regular expression equivalent to the rule, shown in a modified notation as noted:

⚓︎ - context anchor

Placeholder for the actual code point when a context is evaluated. The code point must occur at the position corresponding to the anchor. Rules containing an anchor cannot be used as triggers.

(...)← - look-behind

If present encloses required context preceding the anchor.

→(..) - look-ahead

If present encloses required context following the anchor.

( ) - group

An anonymous nested rule is used to group match operators.

(... | ...) - choice

When there is more than one alternative in a rule, the choices are separated by the alternation operator (...|...).

start or end

(start) matches the start of the label; (end) matches the end of the label.

. - any code point

. matches any code point.

[\p{ }] - property

Set of all characters matching a given value for a Unicode property [\p{prop=val}]. Note: uppercase “\P” defines the complement of a property set.

∪, ∩, ∖, ∆ - set operators

Sets may be combined by set operators (∪ = union, ∩ = intersection, ∖ = difference, ∆ = symmetric difference).

∅= - empty set

Indicates that the following set is empty because of the result of set operations, or because none of its elements is part of the repertoire defined here. A rule with a non-optional empty set never matches.

⍟ - default rule

Rules marked with ⍟ are included by default and may or may not be triggered by any possible label under this LGR.

Actions

The following table lists the actions that are used to assign dispositions to labels and variant labels based on the specified conditions. The order of actions defines their precedence: the first action triggered by a label is the one defining its disposition.

#	Condition	Rule / Variant Set		Disposition	Ref	Comment
1	if label matches	leading-combining-mark	→	invalid	[150]	labels with leading combining marks are invalid ⍟
2	if at least one variant is in	{out-of-repertoire-var}	→	invalid		any variant label with a code point out of repertoire is invalid ⍟
3	if at least one variant is in	{blocked}	→	blocked		any variant label containing blocked variants is blocked ⍟
4	if each variant is in	{allocatable}	→	allocatable		variant labels with all variants allocatable are allocatable ⍟
5	if any label (catch-all)		→	valid		catch all (default action) ⍟

Legend

{...} - variant type set

In the “Rule/Variant Set” column, the notation {...} means a set of variant types.

⍟ - default action

Actions marked with ⍟ are included by default and may or may not be triggered by any possible label under this LGR.

Note: The following variant types are used in one or more actions, but are not defined in this LGR: allocatable, blocked, out-of-repertoire-var. This is not necessarily an error.