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 Oriya Script

Overview

This document specifies a reference set of Label Generation Rules (LGR) for the Oriya (Odia) script 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-Orya]. The format of this file follows [RFC 7940]. This LGR is adapted from the “Reference LGR for the Second Level for the Oriya Script” [Ref-LGR-und-Orya], for details, see Change History below.

For details and additional background on the Oriya script, see “Proposal for an Oriya Script Root Zone Label Generation Ruleset (LGR)" [Proposal-Oriya].

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

The repertoire contains 62 code points for letters, covering 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 a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Oriya]. (The proposal cited has been adopted for the Oriya 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 73 repertoire elements.

Any code points outside the Oriya Script repertoire that are targets for out-of-repertoire variants would be included here only if the variant is listed in this file. In this case they are identified as a reflexive (identity) variant of type “out-of-repertoire-var”. Whether or not they are listed, they do not form part of the repertoire.

Repertoire Listing: Each code point or range is tagged with the script or scripts with which the code point is used, 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 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 Malayalam and Myanmar in the same zone will create potential cross-script issues. For details, see Section 6, “Variants” in [Proposal-Oriya]. 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 Malayalam and Myanmar LGR(s) can be found in the following LGR: [Ref-LGR-Myanmar-Full-Variant-Script]

This LGR defines no in-script variants. For details, see Section 6, “Variants” in [Proposal-Oriya].

Digit Variants: The Oriya reference LGR does not include native digits, so there are no semantic variants defined.

However, one Oriya digit is a near homoglyph of a European digit of a different value. U+0B68 ୨ ORIYA DIGIT TWO is a near homoglyph of U+0039 9 DIGIT NINE.

Should an extension be contemplated that adds native digits, these might require variant relations. At the same time, however, any native digits would normally be semantic variants of the ASCII digits. In any zone containing multiple scripts, these two types of variant relation for digits may lead to complication once transitivity is applied.

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 labels should be blocked. There is no preference among these labels.

This LGR does not define allocatable variants.

The specification of variants in this 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

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

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 LGR in this document has been adapted from the corresponding Reference LGR for the Second Level. The Second Level Reference LGR for the Oriya Script was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Oriya script and information contained or referenced therein; see [RZ-LGR-Orya]. 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 Oriya script, that this reference LGR is based on, was developed by the Neo-Brahmi Generation Panel (NBGP). For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Oriya], 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 Oriya Script [Ref-LGR-und-Orya] without normative changes.

References

The following general references are cited in this document:

[EGIDS]

Lewis and Simons, “EGIDS: Expanded Graded Intergenerational Disruption Scale,” documented in [SIL-Ethnologue] and summarized here:
https://en.wikipedia.org/wiki/Expanded_Graded_Intergenerational_Disruption_Scale_(EGIDS)

[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-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

[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

[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-Orya]

ICANN, Root Zone Label Generation Rules for the Oriya Script (und-Orya), 26 May 2022 (XML)
https://www.icann.org/sites/default/files/lgr/rz-lgr-5-oriya-script-26may22-en.xml

[SIL-Ethnologue]

David M. Eberhard, Gary F. Simons & Charles D. Fennig (eds.). 2021. Ethnologue: Languages of the World, Twenty fourth edition. Dallas, Texas: SIL International. Online version available as
https://www.ethnologue.com

[Ref-LGR-und-Orya]

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

[Unicode 11.0.0]

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 Oriya Script for the second level please see details in the Table of References below.

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

Character Classes

Number of named classes	5
Implicit (except script)	5
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
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=Common-digit	10	{0030-0039}		Any character tagged as Common-digit
implicit	Tag=Halant	1	{0B4D}		The character tagged as Halant
implicit	Tag=Visarga	1	{0B03}		The character tagged as Visarga
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
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	5
Used to trigger actions	1
Used as context rule (C)	4
Anchored context rules	4

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

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.

[: :] - named or implicit character set

Reference to a named character set [:name:] or an implicit character set [:tag:]. A leading “^” before name or tag indicates the set complement.

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

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