Root Zone Label Generation Rules for the Oriya Script

Overview

This file contains Label Generation Rules (LGR) for the Oriya (Odia) script for the Root zone. For more details on this LGR and its development, as well as background on the script, see "Proposal for an Oriya Script Root Zone Label Generation Ruleset (LGR)" [Proposal-Oriya]. This file is one of a set of LGR files that together form an integrated LGR for the DNS Root Zone [RZ-LGR-4]. The format of this file follows [RFC 7940].

While Oriya is the name under which the script is encoded in Unicode, and is therefore used here to formally identify the script, the name Odia has become the preferred name in English for both script and language as it is closer to the pronunciation of their native names.

Repertoire

According to Section 5, "Repertoire" in [Proposal-Oriya], the Oriya LGR contains 62 single code points. This repertoire covers the Oriya (Odia) language as well as all other languages written with the Oriya script and ranging from 1 to 4 on the [EGIDS] scale.

The repertoire is based on [MSR-4], which is a subset of [Unicode 6.3].

As part of the Root Zone, this LGR includes neither digits nor the HYPHEN-MINUS.

Code points outside the Oriya script that are listed in this file are targets for out-of-script variants and are identified by a reflexive (identity) variant of type "out-of-repertoire-var". They do not form part of the repertoire.

Each code point is tagged with the script or scripts that the code point is used with, one or more tag values denoting character category, and one or more references documenting sufficient justification for inclusion in the repertoire; see "References" below. Comments provide alternate names of some code points.

Variants

This LGR defines one set of cross script variants with the Malayalam script, two sets of cross-script variants with the Myanmar script and no in-script variants. For details, see Section 6, "Variants", in [Proposal-Oriya].

Variant Disposition: All variants are of type “blocked”, making labels that differ only by these variants mutually exclusive: whichever label containing either of these variants is chosen earlier would be delegated, while any other equivalent label should be blocked. There is no preference among these variants.

This LGR does not define allocatable variants.

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

Character Classes

The basic characters in Oriya are classified into eight main categories. They are Consonants, Vowels, Matra, Halant, Nukta, Visarga, Candrabindu and Anusvara.

Consonants: The Oriya script is a syllabic alphabet in which all consonants have an inherent vowel. Diacritics, which can appear above, below, before, or after the consonant they belong to, are used to change the inherent vowel. More details in Section 3.5, "Structured consonants" and Section 3.6, "Unstructured consonants" in [Proposal-Oriya].

Vowels and Matras: A dependent vowel sign or "matra" is used to represent a vowel sound that is not inherent to the consonant. It is always depicted in combination with a single consonant, or with a consonant cluster. When vowels occur independently the are written with standalone vowel letters. More details in Section 3.12, "Matra sign (Dependent Vowel)" in [Proposal-Oriya].

Halant: A Halant, also known as Virama, is used after a consonant to "strip" it of its inherent vowel. The Halant form of a consonant is the form produced by adding the Halant, encoded as U+0B4D ( ୍ ) ORIYA SIGN VIRAMA to the nominal shape. A Halant follows all but the last consonant in every Oriya syllable. More details in Section 3.7, "The Implicit Vowel Killer Halant" in [Proposal-Oriya].

Nukta: The nukta sign ( ଼ ) is used in the Oriya language just like in many other scripts used in South Asia. It can be commonly used with U+0B21 ( ଡ ), U+0B22 ( ଢ ). More details in Section 3.8, "Nukta" in [Proposal-Oriya].

Visarga: U+0B03 (ଃ) ORIYA SIGN VISARGA is frequently used in Sanskrit and represents a sound very close to /h/. More details in Section 3.9, "Visarga & Avagraha" in [Proposal-Oriya].

Nasalization:

Candrabindu: The Candrabindu denotes nasalization of the preceding vowel and consonants as in ଅଁଳା /ãala/name of seasonal fruit (U+0B05 U+0B01 U+0B33 U+0B3E). Oriya users commonly use it for writing the words and sounds of Sanskrit. More details in Section 3.10, "Nasalization: Candrabindu" in [Proposal-Oriya].

Anusvara: Anusvara replaces a conjunct group of a Nasal Consonant+Halant+Consonant belonging to a particular varga (plosive). The Anusvara represents a homorganic nasal. Before a non-varga consonant (non-plosive) the Anusvara represents a nasal sound. More details in Section 3.11, "Anusvara" in [Proposal-Oriya].

Whole Label Evaluation (WLE) and Context Rules

Default Whole Label Evaluation Rules and Actions

The LGR includes the set of required default WLE rules and actions applicable to the Root Zone and defined in [MSR-4]. They are marked with ⍟. The default prohibition on leading combining marks is equivalent to ensuring that a label only starts with a consonant or vowel.

Oriya-specific Rules

These rules have been formulated so that they can be adopted for LGR specification.

The following symbols are used in the WLE rules:
C → Consonant
M → Matra
V → Vowel
B → Anusvara
H → Halant
N → Nukta
C1 → Consonants used with Nukta
X → Visarga
D → Candrabindu

The rules are:

• 1. N: must be preceded by C1
• 1. B: must be preceded by V, C, N or M
• 3. X: must be preceded by V, C, N or M
• 4. D: must be preceded by V, C, N or M
• 5. H: must be preceded by C or N
• 6. M: must be preceded by C or N

More details in Section 7, Whole Label Evaluation Rules (WLE)" in [Proposal-Oriya].

Methodology and Contributors

The Root Zone LGR for the Oriya script was developed by the Neo-Brahmi Generation Panel (NBGP) the members of which have experience in linguistics and computational linguistics in a wide variety of languages written with Neo-Brahmi scripts. Under the Neo-Brahmi Generation Panel, there are nine scripts belonging to separate Unicode blocks. Each of these scripts has been assigned a separate LGR, with the Neo-Brahmi GP ensuring that the fundamental philosophy behind building each LGR is in sync with all other Brahmi derived scripts. For further details on methodology and contributors, see Sections 4 and 8 in [Proposal-Oriya], as well as [RZ-LGR-4-Overview].

References

The following general references are cited in this document:

[EGIDS]

Expanded Graded Intergenerational Disruption Scale,
https://www.ethnologue.com/about/language-status
(Accessed on 13 Nov. 2017)

[MSR-4]

Integration Panel, "Maximal Starting Repertoire — MSR-4 Overview and Rationale", 7 February 2019,
https://www.icann.org/en/system/files/files/msr-4-overview-25jan19-en.pdf

[Proposal-Oriya]

Neo-Brahmi Generation Panel, "Proposal for an Oriya Script Root Zone Label Generation Rule-set ", 6 March 2019,
https://www.icann.org/en/system/files/files/proposal-oriya-lgr-06mar19-en.pdf

[RFC 7940]

Davies, K. and A. Freytag, "Representing Label Generation Rulesets Using XML", RFC 7940, August 2016,
http://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-4-Overview]

Integration Panel, "Root Zone Label Generation Rules - LGR-4: Overview and Summary", 05 November 2020 (PDF),
https://www.icann.org/sites/default/files/lgr/lgr-4-overview-05nov20-en.pdf

[RZ-LGR-4]

Integration Panel, "Label Generation Rules for the Root Zone — LGR-4", 05 November 2020 (XML),
https://www.icann.org/sites/default/files/lgr/lgr-4-common-05nov20-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/lgr/lgr-4-common-05nov20-en.html

[Unicode 6.3]

The Unicode Consortium. The Unicode Standard, Version 6.3.0, (Mountain View, CA: The Unicode Consortium, 2013. ISBN 978-1-936213-08-5)
http://www.unicode.org/versions/Unicode6.3.0/

For references consulted particularly in designing the repertoire for the Oriya script for the Root Zone please see details in the Table of References below. References [0] to [6] refer to the Unicode Standard versions in which the corresponding code points were initially encoded. References [101] and above correspond to sources given in [Proposal-Oriya] justifying the inclusion of the corresponding code points. Entries in the table may have multiple source reference values.

4.1 Character Classes

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
C	Tag=Consonant	35	{0B15-0B28 0B2A-0B30 0B32-0B33 0B36-0B39 0B5F 0B71}		Any Oriya consonant
M	Tag=Matra	11	{0B3E-0B43 0B47-0B48 0B4B-0B4C 0B56}		Any Oriya vowel sign
V	Tag=Vowel	11	{0B05-0B0B 0B0F-0B10 0B13-0B14}		Any Oriya vowel letter
N	Tag=Nukta	1	{0B3C}		The Oriya Nukta
C1	Tag=C1	2	{0B21-0B22}		Specific consonants preceding Oriya Nukta
implicit	Tag=Anusvara	1	{0B02}		The character tagged as Anusvara
implicit	Tag=Candrabindu	1	{0B01}		The character tagged as Candrabindu
implicit	Tag=Halant	1	{0B4D}		The character tagged as Halant
implicit	Tag=Visarga	1	{0B03}		The character tagged as Visarga
implicit	Tag=sc:Mlym	1	{0D20}		Any character tagged as Malayalam
implicit	Tag=sc:Mymr	2	{101D 1031}		Any character tagged as Myanmar
implicit	Tag=sc:Orya	62	{0B01-0B03 0B05-0B0B 0B0F-0B10 0B13-0B28 0B2A-0B30 0B32-0B33 0B36-0B39 0B3C 0B3E-0B43 0B47-0B48 0B4B-0B4D 0B56 0B5F 0B71}		Any character tagged as Oriya

4.2 Whole label evaluation and context rules

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}]]	✔				Default WLE rule matching labels with leading combining marks ⍟
follows-C1	([:C1:])← ⚓		✔	C		Section 7, WLE 1: N must be preceded by C1
follows-V-C-N-or-M	([:V:]|[:C:]|[:N:]|[:M:])← ⚓		✔	C		Section 7, WLE 2: B must be preceded by V, C, N or M; WLE 3: X must be preceded by V, C, N or M; WLE 4: D must be preceded by V, C, N or M
follows-C-or-N	([:C:]|[:N:])← ⚓		✔	C		Section 7, WLE 5: H must be preceded by C or N; WLE 6: M must be preceded by C or N

4.3 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		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) ⍟