October 2019 - Latingp - lists.icann.org

Re: [Latingp] Missing In-Script Cases
by Tan Tanaka, Dennis Oct. 31, 2019

Oct. 31, 2019

I have a more nuanced view; our analysis and views can be independent that of IP’s so long they don’t conflict with the LGR Procedure. IMHO, we have crossed that line in some proposed cases and IP is making this observation. -Dennis From: Latingp <latingp-bounces(a)icann.org> on behalf of Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Thursday, October 31, 2019 at 5:53 AM To: Meikal Mumin <meikal(a)mumin.de>, "latingp(a)icann.org" <latingp(a)icann.org>, Michael Bauland <Michael.Bauland(a)knipp.de> Subject: [EXTERNAL] Re: [Latingp] Missing In-Script Cases Dear Colleagues, I agree with Meikal’s view. First item of our agenda for the next telephone call will be discussion about IP’s paper and our conversation with them during ICANN66. Regards Mirjana From: Latin GP <latingp-bounces(a)icann.org> on behalf of Meikal Mumin <meikal(a)mumin.de> Date: Wednesday, 30 October 2019 at 18:00 To: Latin GP <latingp(a)icann.org>, Michael Bauland <Michael.Bauland(a)knipp.de> Subject: Re: [Latingp] Missing In-Script Cases Dear colleagues, I don’t see any issue in putting this on-hold until after having a meeting with IP, but I also believe that IP has misunderstood some of the analysis based on a quick look at their response, and our analysis and views should be independent of IPs. So even if we hold this off for now, we should continue with a unified and coherent approach to the variant analysis and modify it only where we see a need, instead of arbitrarily omitting individual cases. Let IP judge on the final product featuring all of our own evidence and rationale for each actual variant case instead of speculating and discarding cases without having a clear understanding of the situation. Currently this simply remains unfinished. Best wishes, Meikal Am 30. Okt. 2019, 14:50 +0100 schrieb Michael Bauland <Michael.Bauland(a)knipp.de>: Hi all, On 30.10.2019 14:37, Tan Tanaka, Dennis via Latingp wrote: Should we put this on-hold in light of IP’s preliminary feedback and pending comments from our meeting with them next week? I agree with Dennis. We should discuss this with IP and then internally first before continuing. See you next week, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland(a)knipp.de Software Development E-mail: Michael.Bauland(a)knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Latingp mailing list Latingp(a)icann.org https://mm.icann.org/mailman/listinfo/latingp _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Rationales for Cases suggested for Variant Analysis
by Meikal Mumin Oct. 31, 2019

Oct. 31, 2019

Dear colleagues, As per the suggestion from Dennis, I have inserted a hypothesis as rationale for each case in the Appendix D for the current version 6 of the proposal. My suggestion is to discuss these one by one together with the data for each case after ICANN66. Safe travels for everyone. Best, Meikal

2 1

Missing In-Script Cases
by Meikal Mumin Oct. 31, 2019

Oct. 31, 2019

Dear colleagues, I have created template sections for each missing case of a potential in-script variant to be analyzed in Appendix D and have updated the Trello list assigning each case to a reviewer. Assigned reviewers are asked to insert results of their analyses into the relevant template section and email Mirjana and myself on completion so we could check them off in Trello. The Trello list is available here: https://trello.com/c/BoKkXTzF/1-in-script-variants-analysis The current Template v6 is available here: https://docs.google.com/document/d/1Ev8jyIjLr3L1gkUEozkS3Xj3RVp1HSbrgZTlM85… Best, Meikal

4 4

FW: FOR IP: Proposal for a Latin Script Root Zone LGR V5
by Mirjana Tasić Oct. 29, 2019

Oct. 29, 2019

Dear Latin GP members, Here is the letter I sent to Pitinan for IP. Regards Mirjana From: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Sunday, 13 October 2019 at 19:05 To: Pitinan Kooarmornpatana <pitinan.koo(a)icann.org> Subject: FOR IP: Proposal for a Latin Script Root Zone LGR V5 Dear Pitinan, Please send the following material to IP. I am sorry we had no time to format the document properly, I have corrected some formatting but did not have enough time to correct all . Conversion from Google docs to word produced some formatting problems, so the .pdf version of the report is not properly formatted also. We have not finalized yet test label data set, we shall do it in the near future. I hope that IP will accept our apologies, time was very critical resource. Best regards Mirjana

2 1

Consistency in analysis
by Tan Tanaka, Dennis Oct. 25, 2019

Oct. 25, 2019

All, let me try to explain the problem of excluding certain code points from different sets when doing the analysis. Let’s assume two scenarios for the hypothetical analysis: Scenario 1: Set 1 = {A, B} Set 2 = {A, C} For Set 1, it was concluded A is a variant of B. In Set 2, it was concluded A is not a variant of C. Then, the only resulting variant set is A --> B (symmetry implied) Scenario 2: Set 1 = {A, B} Set 3 = {A, B, C} For Set 1, A is deemed variant of B In Set 3, A is deemed variant of B, B deemed a variant of C, but A not a variant of C. The resulting variant sets are A --> B, B--> C; and due to transitivity A-->C is also a variant pair. My point was that by excluding a code point from the analysis can result in different result as to the variant sets identified. Hope this helps clarify. Dennis

2 2

[lgr] IDN Program Update at ICANN66
by Pitinan Kooarmornpatana Oct. 25, 2019

Oct. 25, 2019

Dear All Generation Panel members, Please join us for the IDN Program Update at ICANN66 on Wednesday 6 November 2019, 1515 - 1645 local time at Room #514A. Link to ICANN66 schedule: https://66.schedule.icann.org/meetings/1119560 Remote participation: https://icann.zoom.us/my/yul66.514a Warm Regards, Pitinan _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

IDN: Latin GP Meeting with IP at ICANN66
by Pitinan Kooarmornpatana Oct. 25, 2019

Oct. 25, 2019

Dear Latin GP members, This is a placeholder for the IDN: Latin GP Meeting with IP session on Monday 4 November 2019, 1215 - 1315 local time at Room #518. Link to ICANN66 schedule: https://66.schedule.icann.org/meetings/1116977 Remote participation: https://icann.zoom.us/my/yul66.518 Regards, Pitinan

1 0

IDN and UA Sessions at ICANN66
by Pitinan Kooarmornpatana Oct. 25, 2019

Oct. 25, 2019

Dear Latin GP members, Please find agenda for Latin GPs at ICANN66 as following and please find the full agenda for IDN and UA related sessions as attached. GP Meetings Mon, 4 Nov. 1215 - 1315 518 IDN: Latin GP Meeting with IP Tue, 5 Nov 1030 - 1200 523B IDN: Armenian, Cyrillic, Greek and Latin GPs Meeting with IP IDN Program Formal Session Wed, 6 Nov. 1515 - 1645 514A IDN Program Update Please note that some meetings are not listed on the ICANN66 schedule. The calendar invitations including the online participation information for these sessions will be sent shortly following this email. Regards, Pitinan

1 0

Summary of Latin GP Meeting on 24 October 2019
by Pitinan Kooarmornpatana Oct. 24, 2019

Oct. 24, 2019

Dear Latin GP members, Please find attached the summary of the Latin GP meeting on 24 October 2019. Please let us know if you would like to suggest any edits or additions. Action Items S. No.Action ItemsOwner 1Conduct the analysis as assigned and document the results in the corresponding sub-section in the proposal version6 ALL 2Finalize the excel file for in-script variant rating and share the GP members BJ 3Add explanation of in-script variant grouping for each sub-section of Appendix D MM This summary and the recording are also posted at the Latin Wiki Page at https://community.icann.org/display/croscomlgrprocedure/Latin+GP In addition, following are the sessions which Latin GP is presenting at ICANN66. Date TimeRoomSession Mon, 4 Nov.1215 - 1315518IDN: Latin GP meeting with Integration Panel Tue, 5 Nov1030 - 1200523BIDN: Armenian Cyrillic Greek Latin GP Meeting Wed, 6 Nov.15:15 - 16:45514AIDN Program Updates The full schedule will be shared soon. Regards, Pitinan

1 0

Latin GP Meeting
by Pitinan Kooarmornpatana Oct. 24, 2019

Oct. 24, 2019

Dear Latin GP members, This is a placeholder for the weekly Latin GP meeting on Thursdays, 16:00-17:00 UTC. This invitation recurs weekly until the up-coming F2F meeting. The meeting room is https://icann.zoom.us/j/806371056 Regards, Pitinan

1 0