SaudiNIC Comments - IDN TLD‬ Program - Label Generation Ruleset (LGR) Tool Project (P1) - LGR Tool Set Specifications

[Raed Al-Fayez <rfayez@xxxxxxxxxxx>]

Dear ICANN,

The following are comments as a response to the request for comments on the LGR 
Tool Set Specifications document ("Tools for the LGR Creation, Management and 
Use<https://www.icann.org/en/system/files/files/idn-lgr-toolset-reqs-03dec14-en.pdf>"):


1-    In our opinion, we would like to emphasize that the system should enable 
each registry to generate their own language table based on their local 
requirements regardless of other TLDs. For example: the language table for TLD 
(A) may differs than the language table for TLD (B) even if they use the same 
script. In other words, the end user can choose the TLD along with its language 
table to verify any label for validity under that TLD along with generating the 
possible variants for that label. Currently it is not clear in the document if 
the system can handle this requirement.

2-    For the benefits of Arabic script communities, it is recommended to 
support the "Whole  Label  Evaluation (WLE) rules" in Phase 1 of the project 
but not as optional.

3-    The system should be capable of displaying all interfaces, text labels, 
lookup choices, messages, and error in different (main) languages and not only 
a subset of it.

With best regards,

Raed I. Al-Fayez
------------------------------------------
Saudi Network Information Center (SaudiNIC)
Communication and Information Technology Commission (CITC)
Tel: + 966-11-4618216   - Fax: + 966-11-2639393
http://www.nic.net.sa<http://www.nic.net.sa/>

-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain 
legally
privileged information. If you are not the intended recipient, please contact 
the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this 
e-mail
are those of the sender, and do not necessarily reflect those of the 
Communications
and Information Technology Commission (CITC). CITC accepts no liability for 
damage
caused by this email.