March 2018 - Latingp - lists.icann.org

[lgr] FW: ICANN News Alert -- Maximal Starting Repertoire Version 3 (MSR-3) for the Development of Label Generation Rules for the Root Zone
by Sarmad Hussain March 30, 2018

March 30, 2018

Dear All, We are pleased to inform you that MSR-3 has been released. Please see below for details. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2-2018-03-29-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Maximal Starting Repertoire Version 3 (MSR-3) for the Development of Label Generation Rules for the Root Zone 29 March 2018 LOS ANGELES – 29 March 2018 - The Internet Corporation for Assigned Names and Numbers (lCANN) today announced the release of the third version of the Maximal Starting Repertoire (MSR-3[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). This version is upwardly compatible with MSR-2 and adds three code points each to the repertoires of Han and Latin scripts. Under the Procedure to Develop and Maintain Label Generation Rules for the Root Zone with Respect to IDN Labels[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_resou…> [PDF, 72 KB] , the MSR is the starting point for the work by community based Generation Panels[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> which are developing the proposals for relevant scripts for the Root Zone Label Generation Rules (RZ-LGR[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). The contents of MSR-3 and the detailed rationale behind its development are described in MSR-3-Overview and Rationale[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 242 KB]. The RZ-LGR is a mechanism for determining valid IDN top-level domain labels and their variant labels. MSR-3 covers the following 28 scripts: Arabic, Armenian, Bengali, Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Gurmukhi, Han, Hangul, Hebrew, Hiragana, Kannada, Katakana, Khmer, Lao, Latin, Malayalam, Myanmar, Oriya, Sinhala, Tamil, Telugu, Thaana, Tibetan, and Thai. For these scripts, MSR-3 contains 33,496 code points short-listed from 97,973 PVALID/CONTEXT code points of Unicode version 6.3. In addition to selecting their repertoire from within the MSR for developing the RZ-LGR proposals, Generation Panels will also evaluate whether any such code points are variant code points and if any rules are needed to further constrain the labels generated using these code points. The resulting RZ-LGR proposals by the Generation Panels will be released for public comment before they are reviewed by the Integration Panel for integration into the RZ-LGR. MSR-3 defers code points that are already encoded in later releases of Unicode. In addition, the Integration Panel monitors any scripts not included in the MSR for indications change in the MSR is warranted. Until such a change of the MSR, MSR-3 will be the foundation for any RZ-LGR versions developed. All future versions of the MSR and all versions of the RZ-LGR must retain full backwards compatibility. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

Re: [Latingp] AGENDA for the GP call on March, the 22nd, 2018, 16:00UTC
by Mirjana Tasić March 29, 2018

March 29, 2018

Dear Sarmad, Dear all, This is an error in outlook, from time to time it makes my life hard, it does not accept Latin GP as valid address. After restarting the computer it has sent something I did not expect to be sent. Sorry for this, normal agenda for the next call will be sent on time. Regards Mirjana From: Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, March 29, 2018 at 12:35 To: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Subject: RE: [Latingp] AGENDA for the GP call on March, the 22nd, 2018, 16:00UTC Hi Mirjana, The date for the meeting seems to be incorrect in your email. Regards, Sarmad From: Latingp [mailto:latingp-bounces@icann.org] On Behalf Of Mirjana Tasic Sent: Thursday, March 29, 2018 2:41 PM To: latingp(a)icann.org Subject: [Latingp] AGENDA for the GP call on March, the 22nd, 2018, 16:00UTC Dear GP members , Please find in line the agenda for the next call on March 22nd. I have added some teht to the final report, please try to look at it and give your comments. Regards Mirjana __________________________________________________________ AGENDA for the GP call on March, the 22ND, 2018, 16:00UTC 1. Roll call 2. Adoption of minutes from the F2F meeting in Brussels https://docs.google.com/document/d/13KIVQlkHYc6_ib1ZDSbxRcLVlSHnhAVvc99ZrGw…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 3. Finalization of Repertoire table https://docs.google.com/document/d/1Usd8zv_5TJ-cJaNZ2Iprf-uVIRVan8wZZlkqFGv…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 4. Report from Variant group Denis send the revised variant section: https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> All members should try to contribute to the document before meeting 1. First review of final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 2. AOB

2 1

AGENDA for the GP call on March, the 22nd, 2018, 16:00UTC
by Mirjana Tasić March 29, 2018

March 29, 2018

Dear GP members , Please find in line the agenda for the next call on March 22nd. I have added some teht to the final report, please try to look at it and give your comments. Regards Mirjana __________________________________________________________ AGENDA for the GP call on March, the 22ND, 2018, 16:00UTC 1. Roll call 2. Adoption of minutes from the F2F meeting in Brussels https://docs.google.com/document/d/13KIVQlkHYc6_ib1ZDSbxRcLVlSHnhAVvc99ZrGw… 3. Finalization of Repertoire table https://docs.google.com/document/d/1Usd8zv_5TJ-cJaNZ2Iprf-uVIRVan8wZZlkqFGv… 4. Report from Variant group Denis send the revised variant section: https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y… All members should try to contribute to the document before meeting 1. First review of final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp… 2. AOB

1 0

Re: [Latingp] Latin GP Code Points Repertoire 22 Mar 18
by Sarmad Hussain March 27, 2018

March 27, 2018

Dear Latin GP members, Following the previous mail, please find attached the references converted to the numbered system and encoded in XML (and the corresponding HTML) for your further review and use. Please let us know if you have any feedback or need any further support. Regards, Sarmad From: Latingp [mailto:latingp-bounces@icann.org] On Behalf Of Pitinan Kooarmornpatana Sent: Friday, March 23, 2018 12:07 AM To: latingp(a)icann.org Subject: [Latingp] Latin GP Code Points Repertoire 22 Mar 18 Dear Latin GP members, As discussed during the call, the GP agreed on the repertoire and ICANN staff will use the current repertoire information from Google Doc for indexing the references and for creating the first repertoire section of the LGR XML. For your information, in purpose of version management, we downloaded the current Google Doc as a Word file as attached and we will work on this file. If there is any changes after this version, kindly let us know. Regards, Pitinan

1 0

Latin GP Bi-weekly meeting Thursday 1600UTC
by Pitinan Kooarmornpatana March 25, 2018

March 25, 2018

Dear Latin-GP members, This is a place holder for Latin GP Bi-weekly meeting Thursday 1600UTC Regards, Pitinan ------------------------------ How to connect: [GlobalMeet] [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet® audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me[go.conferencinghub.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.conferencinghub.com…> Not at your computer? You can join by dialing one of the access numbers below. Dial in Number USA /Canada (toll free): 1-866-398-2885 Guest Passcode: 599 105 1297 Additional Access: USA: 1-605-475-5604 USA: 1-712-770-4203 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria, Vienna: +43 (0)1 928 2773 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226

1 0

Latin GP Bi-weekly meeting Thursday 1600UTC
by Pitinan Kooarmornpatana March 25, 2018

March 25, 2018

Dear Latin GP members, As the bi-weekly meeting has shifted one week due to the ICANN meeting. I will end the previous series at 22 March and the new invitation will be sent out again. Regards, Pitinan

1 0

Latin GP Code Points Repertoire 22 Mar 18
by Pitinan Kooarmornpatana March 22, 2018

March 22, 2018

Dear Latin GP members, As discussed during the call, the GP agreed on the repertoire and ICANN staff will use the current repertoire information from Google Doc for indexing the references and for creating the first repertoire section of the LGR XML. For your information, in purpose of version management, we downloaded the current Google Doc as a Word file as attached and we will work on this file. If there is any changes after this version, kindly let us know. Regards, Pitinan

1 0

Variant discussion and samples
by Pitinan Kooarmornpatana March 22, 2018

March 22, 2018

Dear all, Here is the information I shared during the meeting and rewriting again for clarification: …………………… Adding on Mats intervention regards CJK and IP meeting. The CJK has been conducting the variants analysis by using the semantic methodology e.g. 国 and 國 are variants due to their same meaning and same pronunciation. However, IP raised that CJK GP should also include the sameness of the glyph as well. Therefore, the IP pointed out to the text in the LGR procedure https://www.icann.org/en/system/files/files/draft-lgr-procedure-20mar13-en.… A3.2. Variants … An IDN variant, as understood here, is an alternate code point (or sequence of code points) that could be substituted for a code point (or sequence of code points)in a candidate label to create a variant label that is considered the “same” in some measure by a given community of Internet users. There is not general agreement of what that sameness requires, and many of the things people seem to want from that sameness are not technically achievable. The IP shared the ‘Sameness’ is depend on the GP analysis. The IP also suggested not using the word ‘visual similarity’ as it is interpreted in this context as not primary objective of the LGR. A.3.3.Benefits of a well-defined LGR process There are a number of aspects of label and variant evaluation for root zone allocation that are not properly the subject of case-by-case analysis. The primary benefit of the LGR process is as a mechanism that delivers hands-off evaluation for these aspects. By doing so, the process may not be able to replace case-by-case analysis altogether: there will still be a role for additional types of review, such as for String Similarity, and which are not included in the LGR process. Instead the LGR process is designed to clear the table of all the straightforward, non-subjective cases, mainly by returning a “blocked” disposition(see Section B.1). Even for variants based on visual similarity, there exists a subset of evaluation rules that could be applied in an automated manner, obviating the need for further case-by-case or even contextual review. The LGR process as drafted would allow such rules, but only within the bounds established for the types of evaluation rules permissible under this process. While the process described here could be expanded to address cases of visual similarity, that is not the primary intention; if such rules are desirable, they should be a result of evolution of the string similarity rules. At one end, the homoglyph or identical case should be defined as variants as stated in A.3.3. “…the LGR process is designed to clear the table of all the straightforward, non-subjective cases”. On the other end, the ‘visual similarity’ could be the role of other mechanism as also stated in A3.3.3. “… the (LGR) process may not be able to replace case-by-case analysis altogether: there will still be a role for additional types of review, such as for String Similarity” ………………….. Besides that, I’d like to share some sample from other scripts – Devanagari and Gurmukhi, the below two pairs are very similar. One is defined as variant, included in the LGR XML, while the other is only added to the appendix for further use by String Similarity panel, and will not be included in the LGR XML. Variant set: Devanagari Gurmukhi प्टे (092A 094D 091F 0947) ਏ (0A0F) Appendix set: Devanagari Gurmukhi प्टॆ (092A 094D 091F 0946) ਏ (0A0F) The rational is because the Devanagari users could distinguish the second case, but not the first case. The NBGP identify the identical cases as a baseline variant sets, then the indistinguishable cases were also included. The decision of distinguishable or not for each pair was made by the GP discussion over the online meeting. You can find the full list of Neo-Brahmi cross-script variants analysis at NBGP wiki page or here (work in progress) https://community.icann.org/download/attachments/53776300/NBGP-cross-script… . This might be one of the possible methods other GPs could use. However, please note that the NBGP proposals has not been published, and the final decision on analyzing methodology is depend on each GP. Regards, Pitinan

1 0

Re: [Latingp] Within-script variant discovery
by Tan Tanaka, Dennis March 22, 2018

March 22, 2018

Re-sending. Thanks. From: Latingp <latingp-bounces(a)icann.org> on behalf of "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> Reply-To: Dennis Tan Tanaka <dtantanaka(a)verisign.com> Date: Thursday, March 8, 2018 at 9:13 PM To: "latingp(a)icann.org" <latingp(a)icann.org> Subject: [EXTERNAL] [Latingp] Within-script variant discovery Dear generation panel, I have created a new document explaining the process to capture variant candidates within the Latin script. Please review the link below (i.e., Methodology). The methodology was discussed in Brussels. We can review the document and process in our next call. However, I encourage panel members to start recording variant candidates that you already know of based on your language expertise. Do review our inclusion principles to determine whether a proposed candidate is a strong candidate for inclusion. The principles can be found in the link below: Main Document. -Dennis Methodology https://docs.google.com/document/d/1mdqnrNO-MWAs7XZpvCxkPus2yPUZbx5obLdlO6P… Main document https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y…

4 6

Re: [Latingp] Latin GP Bi-weekly meeting Thursday 1600UTC
by Tan Tanaka, Dennis March 22, 2018

March 22, 2018

Nevermind, I found the info From: Latingp <latingp-bounces(a)icann.org> on behalf of "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> Reply-To: Dennis Tan Tanaka <dtantanaka(a)verisign.com> Date: Thursday, March 22, 2018 at 12:02 PM To: "pitinan.koo(a)icann.org" <pitinan.koo(a)icann.org>, "LatinGP(a)icann.org" <LatinGP(a)icann.org>, Mirjana Tasić <Mirjana.Tasic(a)rnids.rs>, Sarmad Hussain <sarmad.hussain(a)icann.org>, Fahd Batayneh <fahd.batayneh(a)icann.org>, Mats Dufberg <mats.dufberg(a)iis.se> Subject: [EXTERNAL] Re: [Latingp] Latin GP Bi-weekly meeting Thursday 1600UTC Are we using global meet or something else for this call? From: pitinan.koo(a)icann.org When: 12:00 PM - 1:00 PM March 22, 2018 Subject: Latin GP Bi-weekly meeting Thursday 1600UTC Location: participate.icann.org/idn Dear Latin GP members, As discussed in call, the next meeting of the Latin GP will be held on Thursday 22 March 2018 at 16.00 UTC. Regards, Pitinan ------------------------------------------------------------------------------------------------------------ How to connect: Link to Adobe Connect: https://participate.icann.org/idn/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-… Participant Passcode: 1064158692

1 0