This document specifies a reference set of Label Generation Rules (LGR) for the Hebrew script 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.
The repertoire contains 27 code points for letters, 5 of which are variants (final forms) of 5 others. The repertoire supports the Hebrew and Yiddish languages 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 to U+0039, 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.
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].
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].
According to Section 7, "Whole Label Evaluation (WLE) Rules" in [Proposal-Hebrew], the LGR does not define rules specific to the Hebrew script.
This reference LGR for Hebrew for the 2nd Level has been developed by Michel Suignard and Asmus Freytag, based on the Root Zone LGR for Hebrew 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.
The following general references are cited in this document:
For references consulted particularly in designing the repertoire for the Hebrew script 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. Reference [101] corresponds to a source justifying the inclusion of the corresponding code points. Entries in the table may have multiple source reference values. References [150] and up indicate the source for common rules.
]]>