Dear colleagues,

I generally tend to agree with Dennis here. Greek GP has used different criteria in my eyes than we have, and I think it is because - as I had mentioned on the call - in their case the script using community is essentially identical with the language using community. Therefore, they have encoded variants on the basis of speakers’ understanding and not based on visual factors. In our case, this would be a non-visual variant or - as IP called it - a semantic variant and if it was restricted to only one language we would refrain from encoding that because of the impact it would have upon other languages.

Therefore, I also believe that the ball is in the arena of Integration Panel, as they should inform Greek GP that such variants are not eligible for the route zone.

However, maybe we can provide them with arguments from the point of view of Latin GP why these should not be eligible. For example, if this is truly because of a certain national legal regulations within Greece, maybe Greek GP should be informed that since this is an international zone local law is not applicable here and that they are free to enforce such rules at the second level. However, I also agree with Dennis that if Integration Panel chooses to simply accept these variants it then becomes an integration issue, which they should handle.

Am 26. Feb. 2021, 17:54 +0100 schrieb Tan Tanaka, Dennis via Latingp :

Thank you for putting this together. IMO, this case highlights the limitation of the tool. Trying to accommodate competing rules across various scripts can be a complex undertaking. I believe there is a misconception what the RZ-LGR can do or what even the DNS can do in terms of variant names at the top-level, but that’s for another time to chat about ☺

I read certain sections of the Greek GP’s proposal and it is clear to me that their criteria is not the same as that of Latin GP. So applying their rationale to ours, does not make sense. If transitivity is enforced, then so be it, but Latin GP should not agree with it. Let the IP figure out the solution for the combined LGR; it’s their job. Or am I missing something?

Dennis

From: Latingp <latingp-bounces@icann.org> on behalf of Pitinan Kooarmornpatana via Latingp <latingp@icann.org>
Reply-To: Pitinan Kooarmornpatana <pitinan.koo@icann.org>
Date: Thursday, February 25, 2021 at 12:54 PM
To: "latingp@icann.org" <latingp@icann.org>
Subject: [EXTERNAL] Re: [Latingp] Meeting material - Decision tree for imposed variant

Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dear Latin GP members,

Today Mats Bill Michael have met for an informal discussion on Bill’s email and the presentation sent earlier.

Please find attached the updated material (adding some example on the second page).

This will be discussed again in the next meeting (4 March 2021)

Regards,

Pitinan

From: Latingp <latingp-bounces@icann.org> on behalf of Pitinan Kooarmornpatana via Latingp <latingp@icann.org>
Reply-To: Pitinan Kooarmornpatana <pitinan.koo@icann.org>
Date: Thursday, February 25, 2021 at 10:43 PM
To: "latingp@icann.org" <latingp@icann.org>
Subject: [Latingp] Meeting material - Decision tree for imposed variant

Dear All,

We have consulted with the chair to developed a summary slide to lay out possible options of Latin GP regarding the imposed variant from other script LGR.

Please find attached the slide. This is planned to be used during the meeting today.

Regards,

Pitinan

_______________________________________________
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.