Hi Dennis and hi everyone,

thank you for clarifying. It's not always easy understanding current discussions when following up by email.

The language is fine, but I believe that the yellow highlighted part calls for a specific change, namely to include "languages which have more native peakers than the smallest of the “official languages” [...] already included".  Your explanations state why we have restricted our choice of languages for analysis and potential inclusion originally and that our choice doesn't necessarily stop other languages from using IDNs except for that not all words from these languages may be represented. So you have provided a very good summary of why we did not do that which was asked for here originally and why we thought it may be an acceptable solution, but there is no definitive proof disproving the view of commenters, how clearly seem to feel that our proposal will not provide reasonable coverage across all languages and our chosen threshold of 1 Million speakers is clearly arbitrary as pointed out by that comment.

So I don't see any explanation why we cannot honour that request now except for we didn't do it at first and had our reasons at the time and neither do I see a reason not to do this apart from a diffuse sentiment of exhaustion as a group, because of the long time it took for this work to develop and mature.

If I understood correctly, Mats pointed out a small language included, so we know the scope of what larger "than the smallest official language" means, and Bill already compiled a list of languages and code points that may be involved, so I would agree with Bill (and Michael I believe), that there is no real cost involved in including these and it can be done in a reasonably concise way without significantly delaying the proposal foreseeably and it is a specific request from the community so we should try to implement it. That is what public comment phases are for in my opinion.

Best,

Meikal
Am 7. Dez. 2021, 21:10 +0100 schrieb Tan Tanaka, Dennis <dtantanaka@verisign.com>:

Hi Meikal,

 

I believe it does. Essentially, they asserted the LGR proposal would restrict certain language communities from choosing TLD labels in their own language. This assertion is obviously not correct. The response addresses this by explaining that the review process indeed took into account an arbitrary (but reasonable) threshold to limit the extent of the panel’s review. However the LGR can guarantee coverage of all languages using the Latin script —including Obolo. The LGR won’t allow 100% of dictionary words (e.g. because of some explicit, and potentially implicit, excluded code points), but will provide reasonable coverage across all languages.

 

We also address their assertion about using a native speaker number as the threshold. The number (i.e., 1 million) was used to limit the extent of review of EGDIS 5 languages only.

 

If you think there is something missing please feel free to suggest additional clarifying language to the draft response.

 

Best,

Dennis

 

From: Meikal Mumin <meikal@mumin.de>
Date: Tuesday, December 7, 2021 at 2:00 PM
To: "Michael.Bauland@knipp.de" <Michael.Bauland@knipp.de>, "latingp@icann.org" <latingp@icann.org>, Dennis Tan Tanaka <dtantanaka@verisign.com>
Subject: [EXTERNAL] Re: [Latingp] Agenda for the Latin GP meeting on 1 December 2021, 16:00 UTC

 

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. 

Hi Dennis,

so that means your response address this paragraph from Mirjanas summary?

Repertoire

The objective of the IDN Project is to make domain names available in the languages of all non-native

speakers of English. To restrict the repertoire for the Latin script to less than half of the living languages

which use that script is contrary to that goal. The ALAC believes that the LGP should go back and include

all of the languages which use the Latin script. (At a minimum, languages which have more native

speakers than the smallest of the “official languages” which are already included, should be added.) For

example, Hawaiian has perhaps 25,000 native speakers, but is included because it is an official language

of the State of Hawaii, despite the stated threshold of 1 million speakers.


Reading through your suggested reply, it seems that you are explaining our limitations and how we approached them globally, which is fine and correct. But it seems that we need to give a qualified answer to the point regarding the minimum inclusion principle asked for in the highlighted part. It seems that the email thread with Bill is going in that direction, and may already have provided the answers to that question.

 

Thanks,

Meikal

Am 6. Dez. 2021, 14:59 +0100 schrieb Tan Tanaka, Dennis <dtantanaka@verisign.com>:

Hi Meikal,

 

I agree that ALAC raised several points, but my response was specific to repertoire. This is how PCs were organized —by topics. If you believe I missed a point please let me know which specific part of ALAC comments on repertoire was left un-addressed (except for uppercase letters and digits, because these are deemed separate).

 

Thanks,

Dennis

 

From: Meikal Mumin <meikal@mumin.de>
Date: Monday, December 6, 2021 at 3:00 AM
To: "Michael.Bauland@knipp.de" <Michael.Bauland@knipp.de>, "latingp@icann.org" <latingp@icann.org>, Dennis Tan Tanaka <dtantanaka@verisign.com>
Subject: [EXTERNAL] Re: [Latingp] Agenda for the Latin GP meeting on 1 December 2021, 16:00 UTC

 

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. 

Hi Dennis,

thank you for your draft of a response, which seems very neutral, specific and along those lines we have based our work on so far. But I am not sure which specific comments this is supposed to answer? For example comments by the ALAC seem to me to be raising much more general questions, which I don’t find addressed in your answer. Is the panel planning on addressing those in a separate response?


Thanks,

Meikal

Am 3. Dez. 2021, 22:34 +0100 schrieb Tan Tanaka, Dennis via Latingp <latingp@icann.org>:

All —here is the draft response to the repertoire related comments.

Dennis

On 12/2/21, 3:27 AM, "Latingp on behalf of Michael Bauland via Latingp" <latingp-bounces@icann.org on behalf of latingp@icann.org> wrote:

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 Mirjana,

as discussed during yesterday's call I have drafted an answer to Igor
Mkrtumyan. We can discuss this further in our next call.

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.