- ChineseGP - lists.icann.org

[lgr] FW: ICANN News Alert -- Maximal Starting Repertoire Version 1 (MSR-1)‬ for the Development of Label Generation Rules for the Root Zone
by Fahd Batayneh June 21, 2014

June 21, 2014

FYI… Fahd Batayneh ICANN Sent: Friday, June 20, 2014 11:54 PM Subject: ICANN News Alert -- Maximal Starting Repertoire Version 1 (MSR-1) for the Development of Label Generation Rules for the Root Zone <http://www.icann.org/> ICANN News Alert https://www.icann.org/news/announcement-2-2014-06-20-en _____ Maximal Starting Repertoire Version 1 (MSR-1) for the Development of Label Generation Rules for the Root Zone 20 June 2014 To support IDN labels in the root zone, the ICANN community, at the direction of the Board, undertook several projects to study and make recommendations on their viability and delegation. One of these projects is the implementation of the Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels <https://www.icann.org/en/resources/idn/variant-tlds/draft-lgr-procedure-20m…> [PDF, 1.39 MB] (the Procedure) allowing for the development of Label Generation Rules (LGR) for the Root Zone. The LGR for the Root Zone is a mechanism for creating and maintaining rules with respect to IDN labels for the root. In the context of the implementation of the Procedure, ICANN is pleased to announce that the Integration Panel has released the first version of the Maximal Starting Repertoire (MSR-1) <https://www.icann.org/resources/pages/reports-2013-04-03-en> . The MSR-1 is the first deliverable from the Integration Panel under the Procedure and will serve as a fixed collection of code points from which Generation Panels may make a selection in constructing the repertoire for their respective LGR proposals. The MSR-1 covers the following 22 scripts: Arabic, Bengali, Cyrillic, Devanagari, Georgian, Greek, Gujarati, Gurmukhi, Han, Hangul, Hebrew, Hiragana, Kannada, Katakana, Lao, Latin, Malayalam, Oriya, Sinhala, Tamil, Telugu, and Thai. MSR-1 contains 32,790 code points short-listed from 97,973 PVALID/CONTEXT code points of Unicode version 6.3. This release of MSR-1 sets the stage for the work by Generation Panels. In addition to selecting their repertoire from within the MSR for developing LGR proposals, Generation Panels will also evaluate whether any such code points are variants and if any rules are needed to further constrain the labels generated using these code points. The resulting LGR proposals by the Generation Panels will be released for public comment before they are reviewed by the Integration Panel for integration into the Root Zone LGR. If it becomes necessary to stage the release of the LGR, for example because not all Generation Panels are able to submit proposals at the same time, subsequent versions of the LGR may be released. MSR-1 defers some of the eligible scripts, so as to balance timeliness with comprehensiveness. At a later stage, another version of the MSR will be developed to include repertoires from the deferred scripts and make other additions to the repertoire as warranted. It would be the foundation for any subsequent LGR versions. All future versions of the MSR and all versions of the LGR must retain full backwards compatibility. MSR-1 release consists of the following documents: * Maximal Starting Repertoire - MSR-1-Overview and Rationale-20140606 <https://www.icann.org/en/system/files/files/msr-overview-06jun14-en.pdf> [PDF, 468 KB] * MSR-1-Annotated-Han-Tables-20140606 <https://icann.box.com/shared/static/4mxq49h6tsc0kldf1cnv.pdf> [PDF, 43.3 MB] * MSR-1-Annotated-Hangul-Tables-20140606 <https://www.icann.org/en/system/files/files/msr-hangul-06jun14-en.pdf> [PDF, 4.19 MB] * MSR-1-Annotated-non-CJK-Tables-20140606 <https://www.icann.org/en/system/files/files/msr-non-cjk-06jun14-en.pdf> [PDF, 1.86 MB] * MSR-1-Repertoire+WLE-Rules-20140606 <https://www.icann.org/en/system/files/files/msr-wle-rules-06jun14-en.xml> [XML, 741 KB] <http://click.icptrack.com/icp/track.php?msgid=940141&act=MI8Z&r=25971199&c=…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

CJK Coordination Meeting during London Meeting
by Han Chuan Lee June 20, 2014

June 20, 2014

Hi, We would like to hold a CJK Coordination Meeting during the London Meeting. There will be attendance from the Integration Panel. Agenda 1. Updates from CGP, prospective JGP and prospective KGP 2. Discussion on coordination efforts. 3. Next steps Venue: To be determined. We are trying to secure a private room with teleconferencing facilities. Time: Depending on availability of room. It will be a 60mins session. We will keep you informed of the room and timing nearer to the London Meeting. Remote participation to be provided if available. Regards Han Chuan, Lee

3 4

[lgr] Universal Acceptance of TLDs Draft Roadmap
by Fahd Batayneh June 19, 2014

June 19, 2014

Friends and Colleagues, Universal Acceptance of TLDs Draft Roadmap has just been posted at https://www.icann.org/public-comments/tld-acceptance-initiative-2014-06-18-e n. Thank you, Fahd Batayneh ICANN _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] LGR sessions - London ICANN meeting
by Nicoleta M. Munteanu June 16, 2014

June 16, 2014

Dear Colleagues, The IDN Variant Program team invites you to join us at the following events during the ICANN London meeting: * IDN Variant TLDs Program session – Wed, 25 June 2014 - 08:30 -10:00 BST - http://london50.icann.org/en/schedule/wed-idn-variant-tld * The session will focus on updates on the IDN Variant TLD Program, and more specifically on the Root Zone LGR Project, including developments around the MSR-1, program outreach efforts and script community updates on the LGR work. * IDN Root Zone LGR Generation Panels Workshop - Wed, 25 June 2014 - 13:00 -15:00 BST - http://london50.icann.org/en/schedule/wed-lgr * This workshop, similar to the one held during the ICANN Singapore meeting, will focus on interactions between LGR community members, community feedback on experiences to establish Generation Panels and initiate the LGR work, various script community presentations and discussions among community members, ICANN staff and Integration Panel members. * Please feel free to suggest in return to this email, desired topics of discussion related to the Root Zone LGR Project that you would see necessary for the workshop agenda to include. In addition, please note that, in response to community members’ requests, the IDN Variant Program team has created a new mailing list where LGR community members may write directly to the Integration Panel members on matters related to their LGR work. This mailing list is: IntegrationPanel(a)icann.org<mailto:IntegrationPanel@icann.org>. In the meantime, the LGR(a)icann.org<mailto:LGR@icann.org> mailing list will continue to fulfill its role for project-wide communications, where all panels’ members (Integration, existing and prospective Generation) as well as ICANN staff, have access to all exchanges. Further details on project's mailing lists may be found at: https://community.icann.org/display/croscomlgrprocedure/LGR+Mailing+List+Da…<https://community.icann.org/display/croscomlgrprocedure/Root+Zone+LGR+Proje…> We are looking forward to your suggestions for the workshop agenda and your participation at the LGR Project sessions during the ICANN London meeting. IDN Variant Program Team ICANN _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] TF-AIDN Second F2F Meeting
by Fahd Batayneh June 14, 2014

June 14, 2014

Friends and Colleagues, The Task Force on Arabic Script IDNs (TF-AIDN) had its second F2F meeting over the course of 5-days during June 8-12, 2014. The meetings took place in Istanbul, Turkey. The agenda <https://community.icann.org/download/attachments/43982588/TF-AIDN%202nd%20F 2F%20Meeting%20Agenda.pdf?version=1&modificationDate=1402773826556&api=v2> consisted of two main topics: 1. 3 days of LGR and Variant Discussions (June 8-10) 2. 2 days of Universal Acceptance of Arabic Script IDNs (June 11-12) You can find the slides that were presented during the 5-days on the dedicated wiki space at https://community.icann.org/display/MES/TF-AIDN+Work+Space. Some sessions did not have slides prepared as respective presenters demonstrated their talk visually. Finally, below is a group picture in the middle of one of the sessions. A small group, yet a very productive meeting. cid:image003.jpg@01CF872C.199F6120 Members of the TF-AIDN Present in Istanbul Thank you, Fahd _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] TF-AIDN 2nd F2F Meeting Agenda
by Fahd Batayneh June 4, 2014

June 4, 2014

All, Please find attached the FINAL version of our TF-AIDN 2nd F2F meeting in Istanbul, Turkey during June 8-12, 2014. You will note that the meeting with the Integration Panel has shifted to June 10 during 16.00 - 18.00 Istanbul time (UTC+3.00). Thank you, Fahd Batayneh ICANN _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

2 1

[lgr] Possible IP participation at the TF-AIDN meeting in Istanbul
by Asmus Freytag May 27, 2014

May 27, 2014

Dear Sarmad, ICANN staff has forwarded a request sent by you on behalf of TF-AIDN for interaction with the Integration Panel at the upcoming TF-AIDN meeting at Istanbul. We have discussed this among the Integration Panel members and with staff and we do not quite know how best to respond to this request. For one, some of our members are absent this week and not reachable for discussion. Others are not available during the dates of your meeting. The Integration Panel also has its own F2F meeting scheduled the weekend before in Los Angeles, making for rather difficult travel schedule even for those members who would otherwise be available. Your request mentioned that TF-AIDN felt that expertise in "Arabic and DNS" would be useful, but the material forwarded to us by staff did not contain any further specifics on the issues to be covered or the objectives that you would like to achieve by such a meeting. By its nature, the expert members of the Integration Panel were selected to have expertise that is broadly applicable across all scripts; as is commensurate with the role of panel in integrating the many LGRs produced by local Generation Panels, whose members encompass individuals with strong linguistic background and expertise in the subject script. For specific Arabic expertise, we can recommend Tom Milo as advisor. The integration panel has used him as advisor on Arabic matters; his expertise as designer of Arabic typesetting and font technology, we found, gives him a uniquely valuable perspective. (If he were to attend it would be as advisor to the GP and not as representative of the IP.) As for DNS expertise, it would help us if we could better understand the likely concerns and issues you expect to resolve in the session. A./ Asmus Freytag _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

2 2

[lgr] On drafting and LGR in the new XML format
by Asmus Freytag May 22, 2014

May 22, 2014

LGR list members, the requirement that the LGRs created by the Generation Panels must be submitted in the new XML Format For Representing Label Generation Rules <link> continues to be the cause of some apprehensions. My intent with this message is to start a discussion and perhaps help dispel some of these apprehensions. The MSR drafted by the integration panel contains an XML file, that lists the repertoire of the MSR in the XML format. If your Generation Panel does NOT support variants and does NOT support script-specific WLE rules, the simplest way to generate the required XML file might be to delete from the MSR all entries that are not included in your LGR. A more generic approach would be to use a plain text file in a private format to list the code points and variants to do all the editing. This file could be in one of the several existing format for IDN tables. Because /generating /XML is much easier than /editing /XML, the approach that we followed in creating the MSR is to do our editing in such a private format, and then to use a short Perl script to generate the XML from that. By doing this, we avoid introducing the kinds of XML errors that are the result of hand-editing an XML file. For those scripts that use variants on the second level today, existing IDN tables have ways to express variants, and these can be converted to the new format by a Perl script as well. The effort required is quite moderate. If I may, I'd like to refer to my own experience. For a different ICANN project, I managed to write a functioning reader in a full-fledged programming language (not a script language) in about a week, supporting not just one IDN table format, but as many formats as existed in the IANA registry. To write the method that outputs the same data in XML format took some additional time. I assume that most GPs already have draft repertoire lists that could be converted to the same format as the MSR, and a simple diff could be used to find out whether the draft repertoire accidentally contains code points not allowed in the MSR. Alternatively, there are many tools that read XML files and can translate them into columnar tables. MS- Excel can do that, for example. Once saved in .CSV format, such tables are simple to transform into whatever private format your GP has decided to use for editing. Either way, you will have your draft data in a format that you are familiar with while you are editing, and a format that is easily compared to both your starting collection (the one you derived from the MSR intersected by your script) and to later versions of your draft repertoire. Now, when it comes to creating whole label evaluation rules, no such shortcuts exist. What I would propose is that any Generation Panel that intends to define such rules, create a detailed description with regular expressions or pseudo code (as in RFC 5892 for example). Those of us who are more familiar with the format would then be able to assist you in translating these rules into the XML format. The resulting XML for the rules can be appended by script to the part that is created from the plain text list of repertoire and variants. That way, your Generation Panel can continuously have an updated draft of its complete LGR in the XML format without doing any actual XML editing. Finally, there is the matter of validation and correctness of the XML specification. If your GP produces XML drafts according to these suggestions, it would be a simple matter to assist the GPs in making sure that the XML is valid and satisfies any other restrictions that are specific to the Root Zone LGR work. It's not clear whether those tools that Integration Panel members wrote for our own purposes on the panel can be shared, or whether ICANN staff at this time has a tool that is shareable, but I know this is being looked into. Until then, we can always run any early LGR drafts that are shared with us through our tools and report any issues. The main goal is to make sure that no LGR is rejected based on a simple typo or syntax error. A./ Asmus Freytag _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 1

[lgr] Project-wide communication
by Asmus Freytag May 22, 2014

May 22, 2014

All, the Integration Panel recently discussed how best to use this list for project-wide communication. This was partially a follow-up on some of the discussions with GPs during the Singapore meeting. The general idea is to to try to use as few lists as possible and to use a publicly archived list for as much of the inter-panel and project-wide communcations as possible - so as to increase transparency of the project. If the mail traffic should become so large, that it needs to be managed, we can discuss alternate strategies when we know better what will be needed. There is one issue that's worth addressing up front and that has to do with whether a posting formally captures a decision or act by a Panel, or whether it's a more informal level of contribution to the discussion. I suspect that the minority of contributions will be "formal" statements, so a reasonable policy would be to require that those are explicitly identified as such. The presumption will then be that /*all other* /postings have not been reviewed and formally approved by the membership of the respective panel. For example, while this particular message, arose out of a discussion during an IP phone meeting, it would be a stretch to say that it represents a formal decision of or request by the Integration Panel. Therefore, under the proposed convention I would not identify it as such. From the contents, you may, of course, infer that I believe that others share my position, so that in my view that on the whole this is something more than just a personal proposal. This does leave a bit of a gray zone, but I think that we have to deal with gray zones anyway everyday, so as long as the formal decisions and actions of any panel are clearly and explicitly identified, we escape having to disclaim every other communication, which should simplify things enormously. A./ _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] Reminder - MSR public comment forum
by Nicoleta M. Munteanu May 15, 2014

May 15, 2014

Dear Colleagues, This message is a reminder that the Public Comment Process for the Maximal Starting Repertoire Version 1 (http://www.icann.org/en/news/public-comment/msr-03mar14-en.htm) corresponding to the first deliverable under the Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels<http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en…> will close on 21 May 2014 at 23:59 UTC. Please note that all comments and replies must be posted prior to the public comment process closure date mentioned above. We appreciate your time to review the materials posted and provide us with your input. Kind regards, Nicoleta Munteanu ICANN _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0