Agenda for Latin GP call on 20 August 2020 16:00UTC
Dear GP members, Please find enclosed the proposal of Agenda for our next call. Any comments, corrections and suggestions are welcome. Here where I am residing, I have very poor Internet connection , I might be forced to use phone instead. Regards Mirjana Agenda for Latin GP call on 20 August 2020 16:00UTC 1. Review of the Appendix E: Confusable. Mirjana has tried to shape the document, she gave,also, some comments. Please read the document, give your comments in order to finalize the document. It is uploaded to old LATIN GP google drive , which is allocated with Mirjana’s account: https://drive.google.com/file/d/18VU1PzjxpQNFoShfyajukPjks7KT3Cvh/view?usp=s... 1. Appendix C reordering of letters, Bill’s proposal e-mail on 23.7 2020 1. Capital Letters Discussion, Mats sent an e-mail on 23.7 2020 2. Next tasks- discuss the priorities: * Report finalization Updated version 30 July 2020 at https://onedrive.live.com/?authkey=%21AkZhpDj508j%2DWW4&id=48AA6AACD70E3A81%... [onedrive.live.com]<https://urldefense.com/v3/__https:/onedrive.live.com/?authkey=*21AkZhpDj508j...> * XML production and correction of possible errors * Test data production 3. Next meeting 27 August, 2020, 16:00 UTC 4. AOB
Dear colleagues, Just a philosophical note. When we designate variants, we are creating something which is a hard block: if a proposed TLD differs from an existing TLD only by one or more variants, it is blocked. Period. That was our rationale for using a very narrow filter to designate variants. In contrast, Confusables are merely a statement to the Similarity Review Panel saying "You might want to look at this." If they decide it is a problem, fine. If they decide it is not a problem in a particular case, fine. If they decide it is never a problem and can always be ignored, that's fine too -- no harm done. The thing is, if we do NOT include something which the Similarity Review Panel would have thought important, except that they didn't think of it because we didn't mention it -- that is a problem. Which is why we should err on the side of including cases here. Bill Jouris On Tuesday, August 18, 2020, 08:59:12 AM PDT, Mirjana Tasić via Latingp <latingp@icann.org> wrote: <!--#yiv8168360637 _filtered {} _filtered {}#yiv8168360637 #yiv8168360637 p.yiv8168360637MsoNormal, #yiv8168360637 li.yiv8168360637MsoNormal, #yiv8168360637 div.yiv8168360637MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv8168360637 a:link, #yiv8168360637 span.yiv8168360637MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv8168360637 span.yiv8168360637EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv8168360637 .yiv8168360637MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered {}#yiv8168360637 div.yiv8168360637WordSection1 {}#yiv8168360637 _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {}#yiv8168360637 ol {margin-bottom:0cm;}#yiv8168360637 ul {margin-bottom:0cm;}--> Dear GP members, Please find enclosed the proposal of Agenda for our next call. Any comments, corrections and suggestions are welcome. Here where I am residing, I have very poor Internet connection , I might be forced to use phone instead. Regards Mirjana Agenda for Latin GP call on 20 August 2020 16:00UTC - Review of the Appendix E: Confusable. Mirjana has tried to shape the document, she gave,also, some comments. Please read the document, give your comments in order to finalize the document. It is uploaded to old LATIN GP google drive , which is allocated with Mirjana’s account: https://drive.google.com/file/d/18VU1PzjxpQNFoShfyajukPjks7KT3Cvh/view?usp=s... - Appendix C reordering of letters, Bill’s proposal e-mail on 23.7 2020 - Capital Letters Discussion, Mats sent an e-mail on 23.7 2020 - Next tasks- discuss the priorities: - Report finalization Updated version 30 July 2020 at https://onedrive.live.com/?authkey=%21AkZhpDj508j%2DWW4&id=48AA6AACD70E3A81%... [onedrive.live.com] - XML production and correction of possible errors - Test data production - Next meeting 27August, 2020, 16:00 UTC - AOB _______________________________________________ Latingp mailing list Latingp@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.
Hi Bill, I agree with your summary, but I have to disagree with your conclusion. I don't think it's our job to do the Similarity Review Team's (SRT) job. Neither is it our responsibility if the SRT is mistaken. We can publish something, that the SRT may or may not use, but they have to do their work independently from ours and are responsible for their decisions themselves. So, if they didn't think of something that is important, we can't and shouldn't be held responsible. It's our job to find the clear-cut variant cases. Everything else is bonus. For this reason I don't think we should add any more corner cases, just to have as many potential confusables as possible. On the contrary, this could even dilute (if that's the correct word for it) our result and make our important cases be hidden within this big list of cases. Cheers, 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@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp
Hi Michael, I agree that it's not our job to do the Similarity Review Team's (SRT) job. But I think narrowing the list of confusables is exactly doing their job. Rather than giving them the information we have on which pairs are potentially confusable, so that they can more readily do their job of deciding if there is a problem in a particular in a particular case. I also agree that it's not our responsibility to identify all possible cases, or eliminate all possible non-problems. Clearly it is not. But it would, I think, be remiss of us to restrict what information we pass along. That is making a judgement that should be their responsibility. I take your point about the hazard of losing the more important cases in a longer list. But really, even with everything already included, the list just isn't that long. Especially once you realize that the SRT won't need to look at everything we list every time -- some pairs will be obviously irrelevant to whatever proposed TLD they are considering. Cheers, Bill Sent from Yahoo Mail on Android On Thu, Aug 20, 2020 at 11:03 PM, Michael Bauland<Michael.Bauland@knipp.de> wrote: Hi Bill, I agree with your summary, but I have to disagree with your conclusion. I don't think it's our job to do the Similarity Review Team's (SRT) job. Neither is it our responsibility if the SRT is mistaken. We can publish something, that the SRT may or may not use, but they have to do their work independently from ours and are responsible for their decisions themselves. So, if they didn't think of something that is important, we can't and shouldn't be held responsible. It's our job to find the clear-cut variant cases. Everything else is bonus. For this reason I don't think we should add any more corner cases, just to have as many potential confusables as possible. On the contrary, this could even dilute (if that's the correct word for it) our result and make our important cases be hidden within this big list of cases. Cheers, 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@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Latingp mailing list Latingp@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.
participants (3)
-
Bill Jouris -
Michael Bauland -
Mirjana Tasić