- ChineseGP - lists.icann.org

[lgr] Updated LGR Toolset (version1.8.1) Information
by Pitinan Kooarmornpatana Dec. 7, 2017

Dec. 7, 2017

Dear GP members, We'd like to inform you that the new version of LGR Toolset is ready. You can access the tool at https://lgrtool.icann.org/ User name: lgr Password: 37zEfM2LyN3DmSzjLaYoA For the details of all functions, please visit User Manual at https://www.icann.org/en/system/files/files/lgr-toolset-user-guide-24oct17-… The key features are: * Create single LGR or merge multiple LGRs * View LGR in XML form or user friendly HTML form * Use a LGR to validate a label and determine its variant labels * Manage LGRs, by comparing or combining them * Review impact of a new or a revised LGR on existing labels Regards, Pitinan Kooarmornpatana ICANN IDN Programs _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] Request for Input on the Maximal Starting Repertoire - MSR
by Sarmad Hussain Nov. 25, 2017

Nov. 25, 2017

Dear All, Please find below a request for input on the Maximal Starting Repertoire (MSR) from the Integration Panel. ------------- The Integration Panel (IP) is actively considering an update to the Root Zone Maximal Starting Repertoire (MSR) now in its second version<https://www.icann.org/resources/pages/msr-2015-06-21-en>. The update aims to add a small number of currently omitted code points for scripts that are already covered. In addition there will be editorial improvements to the way the repertoire is documented and presented. Generation Panels and interested parties are encouraged to review MSR-2<https://www.icann.org/resources/pages/msr-2015-06-21-en> and to communicate to the IP any concerns with the existing MSR such as inaccuracies or omissions. In developing an LGR for the Root Zone, the MSR serves as an absolute upper bound on the code points that may be permitted in the Root Zone. (The actual LGR will represent a subset). Because of that, it is essential that any code points needed for a given script LGR and not excludable based on the principles discussed in [MSR-2] should be reviewed for potential addition to MSR-3. (Not all code points used in writing certain scripts are permissible in IDNs or the Root Zone, and the majority of exclusions is expected to stand). The IP does not anticipate the addition of as yet unsupported scripts to MSR-3, but, in principle, remains open to consider that option for future revisions. Such additions would expected to be based on sufficient community interest in the support of a given script, including, but not limited to a successful proposal to form a Generation Panel. Comments are requested no later than December 15, 2017, as it is planned to put MSR-3 to public comment by January 15, 2018. Please send all comments to integrationpanel(a)icann.org<mailto:integrationpanel@icann.org>. ------------- Regards Sarmad _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

CGP work updates
by 王伟 Nov. 13, 2017

Nov. 13, 2017

Dear All CGP submitted the new version of LGR proposal to IP in summer as attached, and received the feedback document from IP before ICANN63 Abu Dhabi. In the feedback document, IP does not question the size of repertoire any more, ask CGP to provide background information about variant mapping difference between CGP and SLD, and, STILL request CGP to limit the number of allocatable labels. In ICANN63, CGP members had a thorough discussion within CJK and with IP, analyzed all 136 characters who have multiple allocatable variant mappings, and proposed a new solution to limit the number of allocatable labels. The new solution does not change the current repertoire and variant mappings, but creates some new sub-types which will help the LGR BLOCK the repeated/redundant labels and uncommon labels, enabling applicant to get any arbitrary label as original input, as well as the "standard" simplified one and "standard" traditional one. The new solution could be regarded as an case-by-case engineering mechanism to reduce the risk of over-production of allocatable labels. IP accept and approve this solution. Please refer to the attached documents, including the current version of LGR proposal, the IP feedback documents and the new solution. As discussed, IP asked CGP to provide TWO new versions after ICANN63. One is the revised version according to the feedback document. Another one is the updated version including the redundancy removing solution as above. I am working on the two versions and will send out them to everyone before submit to IP. Hopefully, we could complete CGP work by the end of this year, and have ICANN approve/publish CGP document in ICANN64. Regards WANG Wei

1 0

[lgr] Proposal for the Cyrillic Script Root Zone LGR published for public comments
by Sarmad Hussain Oct. 18, 2017

Oct. 18, 2017

Dear All, The Proposal for the Cyrillic Script Root Zone LGR has been released for public comment<https://www.icann.org/public-comments/cyrillic-lgr-2017-10-17-en>. See the announcement at https://www.icann.org/news/announcement-2017-10-17-en. We look forward to your comments. Regards, Sarmad _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] Call for feedback on Latin GP working documents on principles
by Sarmad Hussain Sept. 13, 2017

Sept. 13, 2017

Dear All, Please see the relevant message below on behalf of Latin GP. Regards, Sarmad ---------------------- Dear all, The Latin script community has formed the Latin script Generation Panel (GP), which is developing a Proposal for the Latin Script Root Zone Label Generation Rules, following the LGR Procedure<https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf> and based on the proposal and work plan<https://www.icann.org/en/system/files/files/proposal-latin-lgr-15may17-en.p…> developed by the Latin GP. The Latin GP has drafted its guiding principles to determine the code point repertoire for inclusion in the root zone LGR proposal and to determine the variant code points. The principles are being posted for public comments to allow the GP members to get feedback from the language and technical communities as the GP undertakes the tasks of repertoire and variant code point analysis. Based on the feedback, the Latin script GP will finalize the principles to guide its work. Please review the following documents and send feedback to LatinGP(a)icann.org<mailto:LatinGP@icann.org> by 23 October 2017. * Principles for Inclusion and Exclusion of Code points for Latin Script Root Zone LGR<https://community.icann.org/download/attachments/52897663/Latin%20GP%20Prin…> * Principles for variants for Latin Script Root Zone LGR<https://community.icann.org/download/attachments/52897663/Latin%20GP%20Prin…> We look forward to your comments. For further details visit the Latin GP wiki page<https://community.icann.org/display/croscomlgrprocedure/Latin+GP>. Regards, Latin GP _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FYI - Recent RFC 8228: Designing LGR Supporting Variant Labels
by Sarmad Hussain Aug. 30, 2017

Aug. 30, 2017

Dear All, Please see a recent RFC 8228: Guidance on Designing Label Generation Rulesets (LGRs) Supporting Variant Labels https://www.rfc-editor.org/rfc/rfc8228.txt Abstract Rules for validating identifier labels and alternate representations of those labels (variants) are known as Label Generation Rulesets (LGRs); they are used for the implementation of identifier systems such as Internationalized Domain Names (IDNs). This document describes ways to design LGRs to support variant labels. In designing LGRs, it is important to ensure that the label generation rules are consistent and well behaved in the presence of variants. The design decisions can then be expressed using the XML representation of LGRs that is defined in RFC 7940. Regards, Sarmad _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] RZ-LGR-2 published
by Sarmad Hussain Aug. 10, 2017

Aug. 10, 2017

Dear All, We are pleased to let you know that Root Zone Label Generation Rules version 2.0 (RZ-LGR-2) has been published. The second version integrates Arabic, Ethiopic, Georgian, Khmer, Lao and Thai scripts. To access it, you can go to www.icann.org/idn<http://www.icann.org/idn> and scroll down to Root Zone LGR link or go directly to https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en. Regards, Sarmad _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

CDNC meeting in Taiwan August 28
by 王伟 Aug. 8, 2017

Aug. 8, 2017

Dear All CDNC 2018 summer meeting will be held in Taiwan, August 28~ September 1. The CDNC members will discuss the issues like CDNC IDN Table as well as CGP rules for root zone. Some CGP experts from CDNC members have registered for the meeting. If anyone else want to join us on site or remotely, if let me know by replying the email. Regards WANG Wei

1 0

CGP LGR Proposal Update
by 王伟 July 20, 2017

July 20, 2017

Dear all CGP and KGP reached consensus on variant mappings in the CK joint meeting, March, Beijing. After that, CGP participated in the ICANN Helsinki meeting remotely with the help from Edmon CHUNG. According to the discussion between CJK and IP, we generated LGR proposal as attached. The <http://cn.bing.com/dict/search?q=Main&FORM=BDVSP6&mkt=zh-cn> Main <http://cn.bing.com/dict/search?q=changes&FORM=BDVSP6&mkt=zh-cn> changes <http://cn.bing.com/dict/search?q=are&FORM=BDVSP6&mkt=zh-cn> are as follows: - Section 3.3 explains the CGP’s attempt to reduce the repertoire, and the reason why CGP decided to keep the current size. - Section 4.2.3 illustrates the inconsistency between CGP and dotAsia. According to the discussion with Edmon CHUNG, dotAsia would adjust its SLD repertoire and variant mappings to comply with CGP LGR rules once finalized. - Section 4.2.4 introduces the coordination outcome between C and K, and the final CJK consensus. - Section 4.3 explains the CGP’s attempt to eliminate the multiple mappings and the reason why CGP decided to keep multiple mappings; alternatively, CGP proposed two solutions to limit the number of allocatable labels for further discussion with the IP. Special thanks for Chris DILLON and QI Chao for the proofread and XML generation. Please feel free to give your comment before I send it to IP next weekend. @Edmon, please advise if the document answers all doubts and concerns from IP. Best Regards WANG Wei

1 0

CGP LGR Proposal Update
by 王伟 July 20, 2017

July 20, 2017

Dear all CGP and KGP reached consensus on variant mappings in the CK joint meeting, March, Beijing. After that, CGP participated in the ICANN Helsinki meeting remotely with the help from Edmon CHUNG. According to the discussion between CJK and IP, we generated LGR proposal as attached. The <http://cn.bing.com/dict/search?q=Main&FORM=BDVSP6&mkt=zh-cn> Main <http://cn.bing.com/dict/search?q=changes&FORM=BDVSP6&mkt=zh-cn> changes <http://cn.bing.com/dict/search?q=are&FORM=BDVSP6&mkt=zh-cn> are as follows: - Section 3.3 explains the CGP’s attempt to reduce the repertoire, and the reason why CGP decided to keep the current size. - Section 4.2.3 illustrates the inconsistency between CGP and dotAsia. According to the discussion with Edmon CHUNG, dotAsia would adjust its SLD repertoire and variant mappings to comply with CGP LGR rules once finalized. - Section 4.2.4 introduces the coordination outcome between C and K, and the final CJK consensus. - Section 4.3 explains the CGP’s attempt to eliminate the multiple mappings and the reason why CGP decided to keep multiple mappings; alternatively, CGP proposed two solutions to limit the number of allocatable labels for further discussion with the IP. Special thanks for Chris DILLON and QI Chao for the proofread and XML generation. Please feel free to give your comment before I send it to IP next weekend. @Edmon, please advise if the document answers all doubts and concerns from IP. Best Regards WANG Wei

1 0