Reference LGR for language: Hebrew (he-Hebr)	lgr-second-level-hebrew-language-15dec20-en

This document is mechanically formatted from the above XML file for the LGR. It provides additional summary data and explanatory text. The XML file remains the sole normative specification of the LGR.

Date	2020-12-15
LGR Version	1 (Second Level Reference LGR)
Language	he-Hebr (Hebrew Language)
Unicode Version	6.3.0

1 Description
2 Repertoire
3 Variant Sets
4 Classes, Rules and Actions
4.1 Character Classes
4.2 Whole Label Evaluation and Context Rules
4.3 Actions
5 Table of References

1 Description

Reference Label Generation Ruleset for the Hebrew Language

Overview

This document specifies a reference set of Label Generation Rules (LGR) for the Hebrew language for the second level. The starting point for the development of this LGR can be found in the related Root Zone LGR [RZ-LGR-4-Hebr]. For details and additional background on the script, see "Proposal for Hebrew Script Root Zone LGR", Version 1.2, February 2019 [Proposal-Hebrew]. The format of this file follows [RFC 7940].

This is a DRAFT document released for public comments and not final. Please see the announcement on the ICANN website for public comments on the Second Level Reference LGRs for details on how to submit comments.

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 6.3]. 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), and U+002D (-) HYPHEN-MINUS for a total of 38 repertoire elements.

Each code point or range is tagged with the script or scripts that the code point is used with 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 reference LGR is designed for use in zones shared by more than one script. Where appropriate, cross-script variants have been defined to mutually exclude labels from different scripts that could otherwise be substituted by the users. Once a label has been delegated for one script, any variant labels from other scripts consisting of cross-script variants would be blocked. Any label containing at least one code point that is not a cross-script variant would be considered distinct. Because of that, even large numbers of defined cross-script variants generally do not lead to a high percentage of labels experiencing a collision.

According to Section 6, "Variants", in "[Proposal-Hebrew]", this LGR defines five in-script variants, which are final forms of five in-script letters.

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.

This LGR does not define allocatable variants.

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

Whole Label Evaluation (WLE) and Context Rules

Common Rules

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 restrictions on the allowable placement of digits (no leading digit), see section 2.1 of [160]; implemented here as a context rule on each digit.

Default Actions

Actions include the default actions for LGRs as well as that needed to invalidate labels with misplaced combining marks. They are marked with ⍟. For a description see [RFC 7940].

Hebrew-specific Rules

According to Section 7, "Whole Label Evaluation (WLE) Rules" in [Proposal-Hebrew], the LGR does not define rules specific to the Hebrew script.

Methodology and Contributors

This reference LGR for the Hebrew language for the 2nd Level has been 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-4-Hebr]. Suitable extensions for the second level have been applied according to the [Guidelines]. The original proposal for a Root Zone LGR for the Hebrew script, that this reference 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.

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-06jan16-en.pdf
[IL-IDN]: Hebrew IDN Table for .IL
https://www.iana.org/domains/idn-tables/tables/il_he_1.0.html
[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,
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-Overview]: Integration Panel, "Root Zone Label Generation Rules - LGR-4: Overview and Summary", 5 November 2020 (PDF),
https://www.icann.org/sites/default/files/lgr/lgr-4-overview-05nov20-en.pdf
[RZ-LGR-4-Hebr]: ICANN, Root Zone Label Generation Rules for the Hebrew Script (und-Hebr) , 5 November 2020 (XML)
https://www.icann.org/sites/default/files/lgr/lgr-4-hebrew-script-05nov20-en.xml
[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 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. References [150] and up indicate the source for common rules.

2 Repertoire

Repertoire Summary

Number of elements in repertoire

Number of code points
for each script

Hebrew	27
Common	11

Longest code point sequence

Repertoire by Code Point

The following table lists the repertoire by code point (or code point sequence). The data in the Script and Name column are extracted from the Unicode character database. Where a comment in the original LGR is equal to the character name, it has been suppressed.

For any code point or sequence for which a variant is defined, additional information is provided in the Variants column. See also the legend provided below the table.

Code Point	Glyph	Script	Name	Ref	Tags	Required Context	Variants	Comment
U+002D	-	Common	HYPHEN-MINUS	[0]	Hyphen	not: hyphen-minus-disallowed		⍟
U+0030	0	Common	DIGIT ZERO	[0]	Common-digit	not: leading-digit		⍟
U+0031	1	Common	DIGIT ONE	[0]	Common-digit	not: leading-digit		⍟
U+0032	2	Common	DIGIT TWO	[0]	Common-digit	not: leading-digit		⍟
U+0033	3	Common	DIGIT THREE	[0]	Common-digit	not: leading-digit		⍟
U+0034	4	Common	DIGIT FOUR	[0]	Common-digit	not: leading-digit		⍟
U+0035	5	Common	DIGIT FIVE	[0]	Common-digit	not: leading-digit		⍟
U+0036	6	Common	DIGIT SIX	[0]	Common-digit	not: leading-digit		⍟
U+0037	7	Common	DIGIT SEVEN	[0]	Common-digit	not: leading-digit		⍟
U+0038	8	Common	DIGIT EIGHT	[0]	Common-digit	not: leading-digit		⍟
U+0039	9	Common	DIGIT NINE	[0]	Common-digit	not: leading-digit		⍟
U+05D0	א	Hebrew	HEBREW LETTER ALEF	[0], [101]
U+05D1	ב	Hebrew	HEBREW LETTER BET	[0], [101]
U+05D2	ג	Hebrew	HEBREW LETTER GIMEL	[0], [101]
U+05D3	ד	Hebrew	HEBREW LETTER DALET	[0], [101]
U+05D4	ה	Hebrew	HEBREW LETTER HE	[0], [101]
U+05D5	ו	Hebrew	HEBREW LETTER VAV	[0], [101]
U+05D6	ז	Hebrew	HEBREW LETTER ZAYIN	[0], [101]
U+05D7	ח	Hebrew	HEBREW LETTER HET	[0], [101]
U+05D8	ט	Hebrew	HEBREW LETTER TET	[0], [101]
U+05D9	י	Hebrew	HEBREW LETTER YOD	[0], [101]
U+05DA	ך	Hebrew	HEBREW LETTER FINAL KAF	[0], [101]			set 1	Final form
U+05DB	כ	Hebrew	HEBREW LETTER KAF	[0], [101]			set 1	Nominal form
U+05DC	ל	Hebrew	HEBREW LETTER LAMED	[0], [101]
U+05DD	ם	Hebrew	HEBREW LETTER FINAL MEM	[0], [101]			set 2	Final form
U+05DE	מ	Hebrew	HEBREW LETTER MEM	[0], [101]			set 2	Nominal form
U+05DF	ן	Hebrew	HEBREW LETTER FINAL NUN	[0], [101]			set 3	Final form
U+05E0	נ	Hebrew	HEBREW LETTER NUN	[0], [101]			set 3	Nominal form
U+05E1	ס	Hebrew	HEBREW LETTER SAMEKH	[0], [101]
U+05E2	ע	Hebrew	HEBREW LETTER AYIN	[0], [101]
U+05E3	ף	Hebrew	HEBREW LETTER FINAL PE	[0], [101]			set 4	Final form
U+05E4	פ	Hebrew	HEBREW LETTER PE	[0], [101]			set 4	Nominal form
U+05E5	ץ	Hebrew	HEBREW LETTER FINAL TSADI	[0], [101]			set 5	Final form
U+05E6	צ	Hebrew	HEBREW LETTER TSADI	[0], [101]			set 5	Nominal form
U+05E7	ק	Hebrew	HEBREW LETTER QOF	[0], [101]
U+05E8	ר	Hebrew	HEBREW LETTER RESH	[0], [101]
U+05E9	ש	Hebrew	HEBREW LETTER SHIN	[0], [101]
U+05EA	ת	Hebrew	HEBREW LETTER TAV	[0], [101]

Legend

Code Point: A code point or code point sequence.
Glyph: The shape displayed depends on the fonts available to your browser.
Script: Shows the script property value from the Unicode Character Database. Combining marks may have the value Inherited and code points used with more than one script may have the value Common.
Name: Shows the character or sequence name from the Unicode Character Database.
Ref: Links to the references associated with the code point or sequence, if any.
Tags: LGR-defined tag values. Any tags matching the Unicode script property are suppressed in this view.
Required Context: Link to a rule defining the required context a code point or sequence must satisfy. If prefixed by “not:” identifies a context that must not occur.
Variants: Link to the variant set the code point or sequence is a member of, except where a coded point or sequence maps only to itself, in which case the type of that mapping is listed.
Comment: The comment as given in the XML file. However, if the comment for this row consists only of the code point or sequence name, it is suppressed in this view. By convention, comments starting with “=” denote an alias. If present, the symbol ⍟ marks a default item shared among a set of LGRs.

3 Variant Sets

Variant Set Summary

Number of variant sets

Largest variant set

Variants by Type

blocked

The following tables list all variant sets defined in this LGR, except for singleton sets. Each table lists all variant mapping pairs of the set; one per row. Mappings are assumed to be symmetric: each row documents both forward (→) and reverse (←) mapping directions. In each table, the mappings are sorted by Source value in ascending code point order; shading is used to group mappings from the same source code point or sequence.

Where the type of both forward and reverse mappings are the same, a single value is given in the Type column; otherwise the types for forward and reverse mappings, as well as comments and references, are listed above one another. For summary counts, both forward and reverse mappings are always counted separately.

In any LGR with variant specifications that are well behaved, all members within each variant set are defined as variants of each other; the mappings in each set are symmetric and transitive; and all variant sets are disjoint.

Common Legend

Source: By convention, the smaller of the two code points in a variant mapping pair.
Target: By convention, the larger of the two code points in a variant mapping pair.
Glyph: The shape displayed for source or target depends on the fonts available to your browser.
→ - forward: Indicates that Type, Ref and Comment apply to the mapping from source to target.
← - reverse: Indicates that Type, Ref and Comment apply to the reverse mapping from target to source.
↔ - both: Indicates that Type, Ref and Comment apply to both forward and reverse mapping.
Type: The type of the variant mapping. There are some predefined variant types such as “allocatable” and “blocked”, while others are defined specifically for each LGR.
Ref: One or more reference IDs (optional). A “/” separates references for reverse / forward mappings, if different.
Comment: A descriptive comment (optional). A “/” separates comments for reverse / forward mappings, if different.

Variant Set 1 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
05DA	ך	05DB	כ	↔	blocked		Final form variant / Nominal form variant

Variant Set 2 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
05DD	ם	05DE	מ	↔	blocked		Final form variant / Nominal form variant

Variant Set 3 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
05DF	ן	05E0	נ	↔	blocked		Final form variant / Nominal form variant

Variant Set 4 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
05E3	ף	05E4	פ	↔	blocked		Final form variant / Nominal form variant

Variant Set 5 — 2 Members

Source	Glyph	Target	Glyph		Type	Ref	Comment
05E5	ץ	05E6	צ	↔	blocked		Final form variant / Nominal form variant

4 Classes, Rules and Actions

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	Comment
hyphen	Tag=Hyphen	1	{002D}	The Hyphen-minus character ⍟
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 for which there is no named equivalent.

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}]]]`	✔			[150]	RFC 5891 restrictions on placement of combining marks ⍟
hyphen-minus-disallowed	`(((start))← ⚓)\|(⚓ →((end)))\|(((start)..[:hyphen:])← ⚓)`		✔	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.
(... | ...) - 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 character set: 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.

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

5 Table of References

The following lists the references cited for specific code points, variants, classes, rules or actions in this LGR. For General references refer to the "References" section in the Description.

[0]	The Unicode Standard 6.3.0, http://unicode.org/versions/Unicode6.3.0/
[101]	Omniglot, Hebrew (עברית) https://omniglot.com/writing/hebrew.htm
[150]	RFC 5891, Internationalized Domain Names in Applications (IDNA): Protocol http://tools.ietf.org/html/rfc5891
[160]	RFC 5893, Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) http://tools.ietf.org/html/rfc5893