May 2014 - Koreangp - lists.icann.org

[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

Root Zone LGR Generation Panel Mailing list
by Jia-Juh Kimoto May 1, 2014

May 1, 2014

Dear Colleague, During the ICANN Singapore LGR workshop, community members expressed the need to establish a cross communication platform between all existing and prospective Generation Panels and the Integration Panel to initiate the Label Generation Rules (LGR) work. This message is to notify you that ICANN has created a dedicated, public, LGR mailing list LGR(a)icann.org<mailto:LGR@icann.org>, where community members can share information regarding the LGR work. Membership includes the Integration Panel members and all members of script base mailing lists as described on the project website<https://community.icann.org/display/croscomlgrprocedure/All+Panels+Status+U…>. Public archive of exchanges taking place on this mailing list are available at: http://mm.icann.org/pipermail/lgr/. Within 5 business days, you should receive an auto-generated e-mail confirming your subscription to the LGR mailing list. Any questions about the list or its contents can be sent to idntlds(a)icann.org<mailto:idntlds@icann.org>. As mailing list's membership and archive represent public information, please let us know whether you do not wish to be subscribed. Thank you for your participation. Sincerely, Jia-Juh Yuh Kimoto IDN Variant TLD Program Team ICANN - Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

1 0