ACTION NEEDED: Re: IP Interim Review of Latin-LGR-v6
Dear Latin GP members As Sarmad mentioned, Pitinan and Sarmad can prepare the red-line version of the document based on the IP feedback, addressing all the opening issues. Once the red-line version is ready, the Latin GP can then review the redline version. I want to hear your opinion about this. Pitinan and Sarmad need some time to prepare the document, so I think you should give your opinion ASAP, no later than the end of this week. I am spending next three weeks working on my physical rehabilitation after COVID in one spa in Serbia. I hope my health will improve, so I could chair our next call. Otherwise I shall ask Bill to chair the call. Regards Mirjana From: Latin GP <latingp-bounces@icann.org> on behalf of Latin GP <latingp@icann.org> Reply to: Sarmad Hussain <sarmad.hussain@icann.org> Date: Saturday, 22 May 2021 at 14:09 To: Latin GP <latingp@icann.org> Subject: [Latingp] IP Interim Review of Latin-LGR-v6 Dear Latin GP members, Please find attached the zip file which contains Latin LGR marked with IP feedback. They have also included a short summary of changes they request to address as a separate document in the zip file. Kindly note that they request the following changes/additions: 1. Update variants sets based on the Greek LGR, because now the Greek LGR is available. IP considers it important to include in the proposal especially because it creates many in-script variants for Latin script. Also, this detail is important for readers to see in the Latin LGR proposal when it is released for public comment. Please note that earlier Chinese, Japanese and Korean script LGRs have also accommodated such cross-script impacts. 2. Capture the complete set of variants in a single additional table so that readers can see the complete picture of (in-script and cross-script) variants along with variants caused by transitivity. 3. Update text as indicated in comments of the documents (especially adjusting text where it appears to diverge from IDNA2008 requirements – they consider this as a show-stopper). Kindly also note that, in the interest of time, IP had finalized this review before the Latin GP shared its summary of changes with IP. IP has taken note of the summary and will use it for further analysis of the next version. Here is a note from Asmus further explaining the review done by the IP. ============ Dear Colleagues, Please find attached an "incomplete" review of the Latin LGR Proposal. Let me explain: we are calling it "incomplete" because, in the interest of time, we have not done certain steps that we normally perform and have postponed them to the planned review for the next draft. One of these steps consists of a mechanical verification by doing a tentative integration. Unfortunately, with the Latin and Greek drafts being so far apart, this verification has not been possible. That also means, we were unable to verify many other aspects normally checked by our verification tools. Another one of these steps would normally have consisted of a comparison between our previous feedback and the work done by the GP in the interim. That's how we usually note the progress made by a Generation Panel. This release in particular proved very challenging for us in this regard, because the changes to some of the files were substantial without either redlining or the ability to generate a mechanical diff (due to extensive changes). We decided instead to focus on any issues that we could identify quickly by direct reading of the latest text without reference to the previous version. We are hoping that this will allow you to address these remaining issues while also dealing with your reaction to the Greek Proposal draft now available. You may be curious as to the IP's position on "how close" the Latin LGR is to being ready for public comment. I can only give you my personal opinion due to the rather substantial outstanding work related to Greek. All the other items that we have identified as "critical issues" are in and of themselves showstoppers, but at the same time, they all would seem to be readily addressable, leaving as one remaining piece of substantial effort dealing with the imposed variants from Greek accented vowels. From a superficial reading it looks like the Latin LGR is set to explicitly list all the imposed variants (except for the missing Greek ones). From our perspective, that is the preferred outcome. ICANN staff should be able to assist you in preparing the XML file as they are familiar with what we would expect. We are looking forward to your next draft and anticipate that it will allow us to once again do a mechanical verification pass on the Latin LGR. With a bit of luck, and absent any other showstoppers, there's good chance that the next draft will rapidly close the remaining distance to being ready for Public Comment. Keep up the good work, A./ ========== Please let us know if you have any queries. Regards, Sarmad
This makes sense to me. Certainly for the items (for example, a consolidated Variant table) which are basically mechanical. Do we need to meet, perhaps in parallel, about the items which are not just a matter of mechanically making consolidations, edits, etc.? Bill Jouris On Monday, May 24, 2021, 11:53:41 PM PDT, Mirjana Tasić via Latingp <latingp@icann.org> wrote: <!--#yiv1951515483 _filtered {} _filtered {} _filtered {} _filtered {}#yiv1951515483 #yiv1951515483 p.yiv1951515483MsoNormal, #yiv1951515483 li.yiv1951515483MsoNormal, #yiv1951515483 div.yiv1951515483MsoNormal {margin:0cm;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv1951515483 p.yiv1951515483MsoListParagraph, #yiv1951515483 li.yiv1951515483MsoListParagraph, #yiv1951515483 div.yiv1951515483MsoListParagraph {margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv1951515483 span.yiv1951515483EmailStyle20 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv1951515483 .yiv1951515483MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv1951515483 div.yiv1951515483WordSection1 {}#yiv1951515483 _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {} _filtered {}#yiv1951515483 ol {margin-bottom:0cm;}#yiv1951515483 ul {margin-bottom:0cm;}--> Dear Latin GP members As Sarmad mentioned, Pitinan and Sarmad can prepare the red-line version of the document based on the IP feedback, addressing all the opening issues. Once the red-line version is ready, the Latin GP can then review the redline version. I want to hear your opinion about this. Pitinan and Sarmad need some time to prepare the document, so I think you should give your opinion ASAP, no later than the end of this week. I am spending next three weeks working on my physical rehabilitation after COVID in one spa in Serbia. I hope my health will improve, so I could chair our next call. Otherwise I shall ask Bill to chair the call. Regards Mirjana From: Latin GP <latingp-bounces@icann.org> on behalf of Latin GP <latingp@icann.org> Reply to: Sarmad Hussain <sarmad.hussain@icann.org> Date: Saturday, 22 May 2021 at 14:09 To: Latin GP <latingp@icann.org> Subject: [Latingp] IP Interim Review of Latin-LGR-v6 Dear Latin GP members, Please find attached the zip file which contains Latin LGR marked with IP feedback. They have also included a short summary of changes they request to address as a separate document in the zip file. Kindly note that they request the following changes/additions: - Update variants sets based on the Greek LGR, because now the Greek LGR is available. IP considers it important to include in the proposal especially because it creates many in-script variants for Latin script. Also, this detail is important for readers to see in the Latin LGR proposal when it is released for public comment. Please note that earlier Chinese, Japanese and Korean script LGRs have also accommodated such cross-script impacts. - Capture the complete set of variants in a single additional table so that readers can see the complete picture of (in-script and cross-script) variants along with variants caused by transitivity. - Update text as indicated in comments of the documents (especially adjusting text where it appears to diverge from IDNA2008 requirements – they consider this as a show-stopper). Kindly also note that, in the interest of time, IP had finalized this review before the Latin GP shared its summary of changes with IP. IP has taken note of the summary and will use it for further analysis of the next version. Here is a note from Asmus further explaining the review done by the IP. ============ Dear Colleagues, Please find attached an "incomplete" review of the Latin LGR Proposal. Let me explain: we are calling it "incomplete" because, in the interest of time, we have not done certain steps that we normally perform and have postponed them to the planned review for the next draft. One of these steps consists of a mechanical verification by doing a tentative integration. Unfortunately, with the Latin and Greek drafts being so far apart, this verification has not been possible. That also means, we were unable to verify many other aspects normally checked by our verification tools. Another one of these steps would normally have consisted of a comparison between our previous feedback and the work done by the GP in the interim. That's how we usually note the progress made by a Generation Panel. This release in particular proved very challenging for us in this regard, because the changes to some of the files were substantial without either redlining or the ability to generate a mechanical diff (due to extensive changes). We decided instead to focus on any issues that we could identify quickly by direct reading of the latest text without reference to the previous version. We are hoping that this will allow you to address these remaining issues while also dealing with your reaction to the Greek Proposal draft now available. You may be curious as to the IP's position on "how close" the Latin LGR is to being ready for public comment. I can only give you my personal opinion due to the rather substantial outstanding work related to Greek. All the other items that we have identified as "critical issues" are in and of themselves showstoppers, but at the same time, they all would seem to be readily addressable, leaving as one remaining piece of substantial effort dealing with the imposed variants from Greek accented vowels.
From a superficial reading it looks like the Latin LGR is set to explicitly list all the imposed variants (except for the missing Greek ones). From our perspective, that is the preferred outcome. ICANN staff should be able to assist you in preparing the XML file as they are familiar with what we would expect.
We are looking forward to your next draft and anticipate that it will allow us to once again do a mechanical verification pass on the Latin LGR. With a bit of luck, and absent any other showstoppers, there's good chance that the next draft will rapidly close the remaining distance to being ready for Public Comment. Keep up the good work, A./ ========== Please let us know if you have any queries. Regards, Sarmad _______________________________________________ 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.
Dear Bill, I think that we should meet and discuss changes when Pitinan and Sarmad prepare the documents. But, I shall not be available till the June 11th. If the documents will be ready for discussion sooner, I will ask you to chair the call. Regards Mirjana From: Bill Jouris <b_jouris@yahoo.com> Date: Monday, 31 May 2021 at 19:35 To: Sarmad Hussain <sarmad.hussain@icann.org>, Latin GP <latingp@icann.org>, Mirjana Tasić <Mirjana.Tasic@rnids.rs> Subject: Re: [Latingp] ACTION NEEDED: Re: IP Interim Review of Latin-LGR-v6 This makes sense to me. Certainly for the items (for example, a consolidated Variant table) which are basically mechanical. Do we need to meet, perhaps in parallel, about the items which are not just a matter of mechanically making consolidations, edits, etc.? Bill Jouris On Monday, May 24, 2021, 11:53:41 PM PDT, Mirjana Tasić via Latingp <latingp@icann.org> wrote: Dear Latin GP members As Sarmad mentioned, Pitinan and Sarmad can prepare the red-line version of the document based on the IP feedback, addressing all the opening issues. Once the red-line version is ready, the Latin GP can then review the redline version. I want to hear your opinion about this. Pitinan and Sarmad need some time to prepare the document, so I think you should give your opinion ASAP, no later than the end of this week. I am spending next three weeks working on my physical rehabilitation after COVID in one spa in Serbia. I hope my health will improve, so I could chair our next call. Otherwise I shall ask Bill to chair the call. Regards Mirjana From: Latin GP <latingp-bounces@icann.org> on behalf of Latin GP <latingp@icann.org> Reply to: Sarmad Hussain <sarmad.hussain@icann.org> Date: Saturday, 22 May 2021 at 14:09 To: Latin GP <latingp@icann.org> Subject: [Latingp] IP Interim Review of Latin-LGR-v6 Dear Latin GP members, Please find attached the zip file which contains Latin LGR marked with IP feedback. They have also included a short summary of changes they request to address as a separate document in the zip file. Kindly note that they request the following changes/additions: 1. Update variants sets based on the Greek LGR, because now the Greek LGR is available. IP considers it important to include in the proposal especially because it creates many in-script variants for Latin script. Also, this detail is important for readers to see in the Latin LGR proposal when it is released for public comment. Please note that earlier Chinese, Japanese and Korean script LGRs have also accommodated such cross-script impacts. 2. Capture the complete set of variants in a single additional table so that readers can see the complete picture of (in-script and cross-script) variants along with variants caused by transitivity. 3. Update text as indicated in comments of the documents (especially adjusting text where it appears to diverge from IDNA2008 requirements – they consider this as a show-stopper). Kindly also note that, in the interest of time, IP had finalized this review before the Latin GP shared its summary of changes with IP. IP has taken note of the summary and will use it for further analysis of the next version. Here is a note from Asmus further explaining the review done by the IP. ============ Dear Colleagues, Please find attached an "incomplete" review of the Latin LGR Proposal. Let me explain: we are calling it "incomplete" because, in the interest of time, we have not done certain steps that we normally perform and have postponed them to the planned review for the next draft. One of these steps consists of a mechanical verification by doing a tentative integration. Unfortunately, with the Latin and Greek drafts being so far apart, this verification has not been possible. That also means, we were unable to verify many other aspects normally checked by our verification tools. Another one of these steps would normally have consisted of a comparison between our previous feedback and the work done by the GP in the interim. That's how we usually note the progress made by a Generation Panel. This release in particular proved very challenging for us in this regard, because the changes to some of the files were substantial without either redlining or the ability to generate a mechanical diff (due to extensive changes). We decided instead to focus on any issues that we could identify quickly by direct reading of the latest text without reference to the previous version. We are hoping that this will allow you to address these remaining issues while also dealing with your reaction to the Greek Proposal draft now available. You may be curious as to the IP's position on "how close" the Latin LGR is to being ready for public comment. I can only give you my personal opinion due to the rather substantial outstanding work related to Greek. All the other items that we have identified as "critical issues" are in and of themselves showstoppers, but at the same time, they all would seem to be readily addressable, leaving as one remaining piece of substantial effort dealing with the imposed variants from Greek accented vowels. From a superficial reading it looks like the Latin LGR is set to explicitly list all the imposed variants (except for the missing Greek ones). From our perspective, that is the preferred outcome. ICANN staff should be able to assist you in preparing the XML file as they are familiar with what we would expect. We are looking forward to your next draft and anticipate that it will allow us to once again do a mechanical verification pass on the Latin LGR. With a bit of luck, and absent any other showstoppers, there's good chance that the next draft will rapidly close the remaining distance to being ready for Public Comment. Keep up the good work, A./ ========== Please let us know if you have any queries. Regards, Sarmad _______________________________________________ Latingp mailing list Latingp@icann.org<mailto: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.
OK, I can do that Get well soon. Bill Sent from Yahoo Mail on Android On Mon, May 31, 2021 at 11:31 AM, Mirjana Tasić via Latingp<latingp@icann.org> wrote: _______________________________________________ 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 All, We will be able to prepare the document and share with the GP early next week. Therefore, we would propose that we resume the Latin GP meeting on Thursday 10th June. Please let us know if that works. Regards, Pitinan From: Latingp <latingp-bounces@icann.org> on behalf of Bill Jouris via Latingp <latingp@icann.org> Reply-To: Bill Jouris <bill.jouris@insidethestack.com> Date: Tuesday, June 1, 2021 at 2:17 AM To: Mirjana Tasić <Mirjana.Tasic@rnids.rs>, Mirjana Tasić via Latingp <latingp@icann.org>, Bill Jouris <b_jouris@yahoo.com>, Sarmad Hussain <sarmad.hussain@icann.org>, Latin GP <latingp@icann.org> Subject: Re: [Latingp] ACTION NEEDED: Re: IP Interim Review of Latin-LGR-v6 OK, I can do that Get well soon. Bill Sent from Yahoo Mail on Android [go.onelink.me]<https://urldefense.com/v3/__https:/go.onelink.me/107872968?pid=InProduct&c=G...> On Mon, May 31, 2021 at 11:31 AM, Mirjana Tasić via Latingp <latingp@icann.org> wrote: _______________________________________________ Latingp mailing list Latingp@icann.org<mailto: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 Pitinan, On 01.06.2021 19:02, Pitinan Kooarmornpatana via Latingp wrote:
Hi All,
We will be able to prepare the document and share with the GP early next week.
Therefore, we would propose that we resume the Latin GP meeting on Thursday 10^th June.
Please let us know if that works.
thanks for the preparation work. I think next week works fine. I should be able to join the call then. 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
participants (5)
-
Bill Jouris -
Bill Jouris -
Michael Bauland -
Mirjana Tasić -
Pitinan Kooarmornpatana