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 Hebrew Language

Overview

This document specifies a set of Label Generation Rules (LGR) for the Hebrew language for the second level domain or domains identified above. The ultimate starting point for the development of this LGR can be found in the related Root Zone LGR [RZ-LGR-Hebr]. Note that while it is the Hebrew Script Root Zone LGR that forms the starting point, the LGR defined here covers the Hebrew Language. The format of this file follows [RFC 7940]. This LGR is adapted from the “Reference LGR for the Second Level for the Hebrew Language” [Ref-LGR-he-Hebr], for details, see Change History below.

For details and additional background on the Hebrew script, see “Proposal for Hebrew Script Root Zone LGR”, Version 1.2, February 2019 [Proposal-Hebrew].

Standalone LGR: This LGR is designed to be used in a zone that does not cater to IDNs other than those valid under this LGR. This LGR lacks features that would allow its use in the context of another LGR in the same zone, and it may contain other features incompatible with such use.

Repertoire

The repertoire contains 27 code points for letters, 5 of which are variants (final forms) of 5 others. The repertoire supports the Hebrew language with restrictions appropriate for domain names. The repertoire is a subset of [Unicode 11.0.0]. For details, see Section 5, “Repertoire” in [Proposal-Hebrew]. (The proposal cited has been adopted for the Hebrew script portion of the Root Zone LGR.)

The Hebrew script is written from right to left. More details can be found in Section 3, “Background About the Script and Languages Using it” in [Proposal-Hebrew].

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 38 repertoire elements.

Any code points outside the Hebrew Language 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, 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

This LGR defines five in-script variants that are final forms of Hebrew letters. For details, see Section 6, “Variants”, in “[Proposal-Hebrew]”.

No ASCII Variants: This LGR does not contain definitions for “blocked” variants for letters that look indistinguishable from ASCII letters (homoglyphs). If concurrent use of LDH labels is desired, the resulting conflicts can be handled by using the “Common LGR” in processing. For details, see Section 3, “Use of Multiple Reference LGRs in the Same Zone” in [Level-2-Overview].

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

This LGR does not define allocatable variants.

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

Right-To-Left Rules

• leading-digit — RFC 5893 [160] restrictions on the allowable placement of digits (no leading digit), see section 2.1; implemented here as a context rule on each digit.

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

Hebrew-specific Rules

This LGR does not define rules specific to the Hebrew 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 Hebrew Language was developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for the Hebrew script and information contained or referenced therein; see [RZ-LGR-Hebr]. Suitable extensions for the second level have been applied according to the [Guidelines] and with community input. As part of that process, features have been removed or modified as appropriate for the target language. The original proposal for a Root Zone LGR for the Hebrew script, that this LGR is based on, was developed by the Hebrew Generation Panel. For more information on methodology and contributors to the underlying Root Zone LGR, see Sections 4 and 8 in [Proposal-Hebrew], as well as [RZ-LGR-Overview].

[IL-IDN] was consulted during the work on this LGR.

Changes from Version Dated 22 April 2021

Language tag has been updated.

Changes from Version Dated 18 May 2021

Unicode Version has been updated.

Changes from Version Dated 24 January 2024

Adopted from the Second Level Reference LGR for the Hebrew Language [Ref-LGR-he-Hebr] without normative changes.

References

The following references are cited in the first part of 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

[IL-IDN]

Hebrew IDN Table for .IL
https://www.iana.org/domains/idn-tables/tables/il_he_1.0.html

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

Hebrew Generation Panel, “Proposal for a Hebrew Script Root Zone Label Generation Ruleset (LGR)”, 24 April 2019,
https://www.icann.org/en/system/files/files/proposal-hebrew-lgr-24apr19-en.pdf

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

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

[Ref-LGR-he-Hebr]

ICANN, Second Level Reference Label Generation Rules for the Hebrew Language (he-Hebr), 24 January 2024 (XML)
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-hebrew-language-24jan24-en.xml
non-normative HTML presentation:
https://www.icann.org/sites/default/files/packages/lgr/lgr-second-level-hebrew-language-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 Hebrew Language for the second level please see details in the Table of References below.

Reference [0] refers to the Unicode Standard version in which the corresponding code points were initially encoded. References [101] and above correspond to sources given in [Proposal-Hebrew] justifying the inclusion of the corresponding code points or rules. Entries in the table may have multiple source reference values. In the listing of whole label evaluation and context rules, references [150] and [160] indicate 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:Hebr	27	{05D0-05EA}		Any character tagged as Hebrew
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	3
Used to trigger actions	1
Used as context rule (C)	2
Anchored context rules	2

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 - ⍟
leading-digit	((start))← ⚓︎		✔	C	[160]	RFC 5893 RTL labels cannot start with a digit ⍟

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, out-of-repertoire-var. This is not necessarily an error.