Dear LD PDP WG, It appears the wiki link for background docs was broken and we have fixed the issue. It is now available at the following link: https://icann-community.atlassian.net/wiki/x/2wPVBg Please find the proposed agenda for Meeting #1: 1. Welcome and SOIs (3mins) 2. Updates Since ICANN82 (2mins) 3. Scope Management and Discussion (75mins) 4. Next Steps (5mins) 5. AOB (5mins) John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org <http://www.icann.org> On 3/24/25, 15:04, "Saewon Lee via Gnso-latin-diacritics" <gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> wrote: Dear All, It seems like the wiki link I shared with you below (Background Docs.) got broken along the way. Sharing it with you all again just in case: https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/space... <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/114623451/3>.*Background*Documents__;Kys!!PtGJab4!5ZRyftsuOUZqi-33yqgpPIDXNniM2xMAfAUVbSnsP0U8BUVq1i4PKnvfg7PkJCpH5beWQGc39jRjs0d562R8l-KpF0UDwwQLyMM$ [icann-community[.]atlassian[.]net] Best regards, Saewon On 3/24/25, 10:48 PM, "Saewon Lee via Gnso-latin-diacritics" <gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>>> wrote: Dear LD PDP WG, Please find the proposed agenda for Meeting #1: 1. Welcome and SOIs (3mins) 2. Updates Since ICANN82 (2mins) 3. Scope Management and Discussion (75mins) 4. Next Steps (5mins) 5. AOB (5mins) As we prepare for Meeting #1, please review the Latin RZ-LGR doc. again. This document as well as other relevant documents to support the WG can be found on wiki here: https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/space... <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/space...> <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/space...> <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/114623451/3>>.*Background*Documents__;Kys!!PtGJab4!_QyQZTs_fUnb_dkVjZ-rcgwr2aHwLPooYV967x0ZdymThAL1Noi2FOvPjG6U4LGjgqTz0yOhH8Zy-ooV4e5fPQeCRLh_Co5pSA$ [icann-community[.]atlassian[.]net] Today, you would have also received meeting invites for the next month. Please let us know through the mailing list if you were unable to receive them. Tapani and Amadeu: Thank you for initiating the scope discussions again. The points you made provided lots of food for thought for Leadership-Staff while preparing for the next meeting. As we do a deep dive into the scope, the points you have raised will be discussed upon/responded to during the meeting through the understanding of the Charter, RZ-LGR Table for Latin Script, Unicode characters, and the String Similarity Review concerns. Looking forward to seeing you all! Best regards, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee@icann.org <mailto:saewon.lee@icann.org> <mailto:saewon.lee@icann.org <mailto:saewon.lee@icann.org>> <mailto:saewon.lee@icann.org <mailto:saewon.lee@icann.org> <mailto:saewon.lee@icann.org <mailto:saewon.lee@icann.org>>> Skype: saewon.lee.icann Website: http://www.icann.org <http://www.icann.org> <http://www.icann.org> <http://www.icann.org>> <http://www.icann.org> <http://www.icann.org>> <https://urldefense.com/v3/__http://www.icann.org>__;!!PtGJab4!5ZRyftsuOUZqi-33yqgpPIDXNniM2xMAfAUVbSnsP0U8BUVq1i4PKnvfg7PkJCpH5beWQGc39jRjs0d562R8l-KpF0UDhacck-o$ <https://urldefense.com/v3/__http://www.icann.org>__;!!PtGJab4!5ZRyftsuOUZqi-33yqgpPIDXNniM2xMAfAUVbSnsP0U8BUVq1i4PKnvfg7PkJCpH5beWQGc39jRjs0d562R8l-KpF0UDhacck-o$> [icann[.]org>]> On 3/24/25, 6:16 PM, "Amadeu Abril i Abril (CORE) via Gnso-latin-diacritics" <gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>>>> wrote: Hello all. I would say “yes” to both your questions. As I explained in previous mail exchanges, we should not base our decisions and distinctions in linguistic, semantic, morphological or otrhographic criteria. TLDs may be grammaticaly incorrect, or mean jut nothing in no language. And indeed, what is a diacritic varies from context to context. In linguistic terms, it also varies historically: w was,and still is in some lalnguages, a variant, a diacritic version, of v. And u and v were just variants of the same character, as G amc C…. The point is not whehter they are considered proper charactars in a given alphabet or a modification/diacritic of another character. The point, for us, is that a set of the Latin charactr repoertoire iknon as ASCII does NOT require specicalencoding inthe DNS. While allthe rest does require althe IDN/punycode encoding. So when we say ASCII and diacrtitics we mean ASCII and non-ASCII (if they are similar enough to raise issues under the String Evaluation test which is a requirement for new gTLDs). And indeed there may be more than one “similar” IDN/non-ASCII/string with diacritics which falls ntothe “too similar to be allowed” scenario, so the solution(s) we are toduscuss mayapply to more than 2 TLDs strings at once. Even if unlikely for practical (including financial) reasons. Regards. AAA
El 24 març 2025, a les 15:14, Tapani Tarvainen via Gnso-latin-diacritics <gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>>>> va escriure:
Dear all,
In preparation for our next call, I wrote down a few issues I'd like to clarify about our scope:
(1) We use the term "diacritics" differently than linguists do. If I understand correctly, we're including all non-ASCII characters that various Latin-based alphabets use, such as æ, ŋ, ß, ð, þ etc.
(2) The base ASCII gTLD version of a diacritic is for us by definition a single ASCII letter with the sole exception of German ß. Other cases where the conventional ASCII conversion is two or more letters are not treated similarly (as per RZ-LGR). Presumably we could, however, take the existence of such as a factor in our recommendations.
E.g., to pick an example from Finnish, consider ".šakki" vs ".sakki", should the existence of ".shakki" matter? (Both "šakki" and "sakki" are Finnish words with completely unrelated meanings, while "shakki" is an alternative spelling of "šakki" - not a computer-era fallback, but actually older and still more common spelling even though deprecated by modern ortography.)
Or consider "æ", which also looks obviously similar to "ae".
(3) Our first question talks about "a base ASCII gTLD and *the* Latin script diacritic version", in singular. It seems pretty clear to me, however, that we should also consider cases with multiple diacritic versions of the same ASCII letter, like the "sjö" / "sjø" case I brought up earlier.
-- Tapani Tarvainen _______________________________________________ Gnso-latin-diacritics mailing list -- gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>>> To unsubscribe send an email to gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>>>
Gnso-latin-diacritics mailing list -- gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>>> To unsubscribe send an email to gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>>> _______________________________________________ Gnso-latin-diacritics mailing list -- gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> <mailto:gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org>> To unsubscribe send an email to gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org> <mailto:gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>> _______________________________________________ Gnso-latin-diacritics mailing list -- gnso-latin-diacritics@icann.org <mailto:gnso-latin-diacritics@icann.org> To unsubscribe send an email to gnso-latin-diacritics-leave@icann.org <mailto:gnso-latin-diacritics-leave@icann.org>