March 2025 - Gnso-latin-diacritics

Notes and Action Items from LD PDP Meeting #1
by Steve Chan March 28, 2025

March 28, 2025

Dear WG Members, Please find the high-level notes, outcomes, and action items from the LD PDP meeting #1<https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/12215910…> on 26 March 2025. Best, Steve ACTION ITEMS: * None NOTES: Welcome & SOIs * None Updates Since ICANN82 * Request for (voluntary) input shared with SO/AC/SG/Cs Scope Management and Discussion * Reviewed variants sets to help clarify what is NOT in scope for this PDP. * Question of whether this WG’s scope of work includes things like æ, ŋ, þ, ß &c. Noted that strictly speaking, no. Reviewed Unicode table to demonstrate when code points are combinable (i.e.,, an ASCII code point and a diacritic) or not. Do not necessarily need to review the table – it can serve as an input/reference to this WG’s potential recommendations. * Question about strict interpretation of Unicode – was it intended by the Council? Recommendation to adhere to the boundaries, established by Unicode. Outcome: Tentative agreement to adhere to Charter and define Latin Script Diacritics per Unicode. Outcome: Helpful also to include discussion and conclusions of what was determined to be out of scope and potentially, but perhaps as well, how the rules can be extended (e.g., through a separate process). * Suggestion that it might not limiting to establish a specific list of allowable characters and instead, flexibility can potentially be gained by relying on rules that strings must adhere to. * Some questions raised about cases that that might exist outside of the Latin repertoire. Agreement to explore further how this might be accommodated, or not, given the limited scope of this PDP. * Question raised about possibility of having ASCII/diacritic pairs being operated by separate entities. Noted that the charter envisions a single registry operator, to avoid the potential for user confusion. * Question raised about the possibility of trying to prevent the application for the corresponding ASCII or diacritic version from a third party. Noted that the string similarity process in the New gTLD Program should prevent this outcome, with an objection mechanism also present to help mitigate the concern. * Question about whether the string similarity panel only looks at pair-wise comparisons between codepoints, or it looks at the full gTLD. Clarified that the panel will have the pair-wise comparisons as an input to their evaluation, but will analyze the complete strings in determining whether there is string confusion or not. In other words, the panel will evaluate strings, not characters. Next Steps: * Work plan will be submitted to Council. * Members are encouraged to review relevant materials (RZ-LGR for the Latin Script and relevant parts of the ccTLD Fast Track process). * Question about a small Phase 1 process, which could potentially allow for the application of ASCII/diacritic gTLD strings, which would await completion of Phase 2 of this PDP. Performed some initial analysis that demonstrates that the timeline is too lengthy to align with the AGB. However, still evaluating whether there might be another way to add language to the AGB. AOB * Suggestion that as a way to narrow this PDP, may want to focus on .Brands and city names (or more generally, proper nouns), but perhaps to separate out generic strings. Noted that this is a matter for deliberations for this PDP (e.g., considering whether the criteria for allowable ASCII/diacritic pairs should be further narrowed). Some concern noted that the sequencing of the Next Round would make this sort of differentiation, by application type, difficult to implement. Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

3 2

Scope: only two strings?
by Tapani Tarvainen March 26, 2025

March 26, 2025

Dear all, Many questions about our scope were made clear in the call, but not all. Notably, the limitation to a maximum of two strings was implied (see slide 21) but not explicitly decided as far as I could tell. It sounds like a strange limitation to me, given that there are cases where more than two words, even proper names, differ only in having different diacritics. My earlier examples included ø which was declared out of scope, but there're similar cases with "real" diacritics, e.g., Sjoberg, Sjöberg and Sjóberg. Can we consider cases where someone applies for three or more such at the same time, or where one already has two of them and applies for a third one &c? -- Tapani Tarvainen

5 6

Post Call | Latin Script Diacritics PDP | Wednesday, 26 March 2025
by Devan Reed March 26, 2025

March 26, 2025

Dear all, All recordings for the Latin Script Diacritics PDP call held on Wednesday, 26 March 2025 at 13:00 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AQBIBw?atlOrigin=eyJpIjoiMTVhY…> (attendance included) and the GNSO Master calendar<https://gnso.icann.org/en/group-activities/calendar/2025>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-latin-diacritics@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/EwDVBg?atlOrigin=eyJpIjoiMWI2M…>. Thank you. With kind regards, Devan

1 0

Scope issues
by Tapani Tarvainen March 26, 2025

March 26, 2025

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

7 16

Re: Proposed Agenda for Meeting #1
by Saewon Lee March 24, 2025

March 24, 2025

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://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/11462345… Best regards, Saewon On 3/24/25, 10:48 PM, "Saewon Lee via Gnso-latin-diacritics" <gnso-latin-diacritics(a)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/spac… <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spac…>.*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(a)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>> On 3/24/25, 6:16 PM, "Amadeu Abril i Abril (CORE) via Gnso-latin-diacritics" <gnso-latin-diacritics(a)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(a)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(a)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(a)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(a)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(a)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(a)icann.org <mailto:gnso-latin-diacritics@icann.org> To unsubscribe send an email to gnso-latin-diacritics-leave(a)icann.org <mailto:gnso-latin-diacritics-leave@icann.org>

2 1

Proposed Agenda for Meeting #1
by Saewon Lee March 24, 2025

March 24, 2025

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://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/11462345… 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(a)icann.org <mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org <http://www.icann.org> On 3/24/25, 6:16 PM, "Amadeu Abril i Abril (CORE) via Gnso-latin-diacritics" <gnso-latin-diacritics(a)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(a)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(a)icann.org <mailto:gnso-latin-diacritics@icann.org> > To unsubscribe send an email to gnso-latin-diacritics-leave(a)icann.org <mailto:gnso-latin-diacritics-leave@icann.org> _______________________________________________ Gnso-latin-diacritics mailing list -- gnso-latin-diacritics(a)icann.org <mailto:gnso-latin-diacritics@icann.org> To unsubscribe send an email to gnso-latin-diacritics-leave(a)icann.org <mailto:gnso-latin-diacritics-leave@icann.org>

1 0

About yesterday's meeting
by Sergio Salinas Porto March 13, 2025

March 13, 2025

*Español y abajo Ingles* Queridos amigos, el día de ayer concurrí a la reunión de nuestro grupo de trabajo, realmente estoy muy feliz de poder trabajar con ustedes y avanzar en algo que para los latinoamericanos es de suma importancia como son los caracteres diacríticos, que utilizamos a diario en nuestra comunicación verbal y escrita aquellos que estamos atravesados por la cultura latina. Lamentablemente me tuve que retirar al darme cuenta que no estaba previsto en una reunion a tratar temas concernientes al idioma latino (Castellano, Francés y Portugués en principio), interpretación para las personas que provenimos de paises de justamente esas lenguas. ICANN, ha hecho y hace por cierto un gran esfuerzo por ser una organización inclusiva y sensible de que todos aquellos que provenimos de otras culturas, para que podamos participar y comunicarnos, y es por eso que ha previsto un cuerpo de interpretes para que TODOS podamos participar. El 26 de Marzo tenemos nuestra reunión por Zoom, creo que es necesario que tengamos interpretación en la reunion, y que asumamos que en una organización con anclaje internacional, debemos ser inclusivos, prever sumar a aquellos que trabajan y no hablan el idioma ingles y que tienen mucho para aportar al trabajo cotidiano de ICANN. Espero que podamos avanzar en ese sentido de forma positiva. Saludos cordiales! *Ingles* Dear friends, Yesterday I attended the meeting of our working group. I am really happy to be able to work with you and move forward on something that is of utmost importance to Latin Americans, such as diacritical characters, which we use daily in our verbal and written communication, those of us who are influenced by Latin culture. Unfortunately, I had to leave when I realized that there was no meeting scheduled to discuss issues concerning the Latin language (Spanish, French and Portuguese in principle), or interpretation for people who come from countries with precisely those languages. ICANN has made and continues to make a great effort to be an inclusive and sensitive organization for all of us who come from other cultures, so that we can participate and communicate, and that is why it has provided a body of interpreters so that ALL of us can participate. On March 26th we have our meeting via Zoom. I think it is necessary to have interpretation at the meeting, and to assume that in an organization with international anchorage, we must be inclusive, planning to include those who work and do not speak English and who have a lot to contribute to the daily work of ICANN. I hope we can move forward in that direction in a positive way. Best regards! *Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra * * conciencia o violan nuestro sentido común" Eduardo Galeano*

2 1

LD PDP 8 March Action Items and Meeting Notes
by John Emery March 9, 2025

March 9, 2025

Hello LD PDP WG Members, It was great to meet everyone yesterday both virtually and in person to kick off our LD PDP WG. Here are some high-level notes and action items from yesterday’s session. We look forward to working through this PDP with all of you going forward. Decisions and Action Items * Decision: The abbreviation for the Latin Script Diacritics was determined to be the LD PDP WG * AIs: 1) Staff to refine the project plan with the timeframe shared with the team to submit to Council next month 2) Support staff to send early input request to SO/AC/SG/Cs 3) WG Members to review the background docs in the wiki: https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/11462345… 4) WG Members to consult groups and provide early feedback through the early input request Slides 8 March Meeting: https://docs.google.com/presentation/d/1CLIPoPU-B4lXnzx1NmFbNl6fxIl8kk4j/ed… Meeting Notes * The leadership team was confirmed to be Michael Bauland as Chair, Mark Datysgeld as Vice-Chair, and Prudence Malinki as GNSO Council liaison * The WG established weekly 90-minute meetings Wednesdays at 13:00 UTC beginning on 26 March * Staff gave an overview of the Charter and the proposed project plan timeline to be submitted to GNSO Council for approval in their April meeting * There was a robust discussion of the scope of work most of which was deferred until the first meeting, some highlights for future reference: * Discussion of defining what is in scope and out of scope for the work including “visually confusingly similar” * Sarmad shared the Supporting Document for Latin athttps://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en for details on repertoire and variant code points * Michael clarified that everything already defined in the variant relationship is out of scope and is covered by previous PDPs. There are variants that are blocked and those that are allocatable. * Sarmad: whatever outcomes comes from this PDP is that for ASCII and diacritic. There is a possibility that ASCII is not found similar to a diacritized version, and this particular question does not make that distinction. Will the outcome of these constraints will build on this and will it be applicable to both scenarios where ASCII and diacritized version are found similar or where ASCII and diacritized are not found similar may proceed even with this PDP * Michael noted that in future meetings members will need to address Sarmad’s point * Discussion of the draft that was circulated for WG member input for the early input request to SO/AC/SG/Cs. Staff noted that this is optional, and members should aid their respective groups with any technical questions they may have if they decide to provide early input Other Relevant Links LD PDP Charter: https://gnso.icann.org/sites/default/files/policy/2025/draft/latin-script-d… Latin RZ-LGR: https://www.icann.org/sites/default/files/lgr/rz-lgr-5-latin-script-26may22… As a reminder here is the PDP wiki space: https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/overview Thank you, Saewon Lee, John Emery, and Steve Chan 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>

1 0

[LSD PDP] Review Request: Draft Message for Early Input Request
by Saewon Lee March 6, 2025

March 6, 2025

Dear LSD PDP WG, In accordance with the GNSO’s PDP requirements, the first step of the process after the WG is formed is to seek an input from each Supporting Organization, Advisory Committee, and GNSO’s Stakeholder Group/Constituency on the topics within the WG Charter. As we prepare for the Kick-off meeting, please share any concerns/suggested edits through sidebar comments within the google doc.<https://docs.google.com/document/d/1omNCnlnVUVecAPSrTkJgK6Ien_sAKApD/edit?u…> by Wednesday, 05 March, at 23:59 UTC. Any substantive concerns/comments will be addressed during Kick-off (08 March). Subsequently, the finalized message will be sent out to SO/AC/SG/Cs by mid-end of March. Kind 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(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

8 16

RESULT: VC Poll
by Saewon Lee March 6, 2025

March 6, 2025

Dear All, Thank you again for participating in the poll. Per the attached results, Mark Datysgeld has been elected as Vice Chair of the Latin Script Diacritics PDP WG. We extend our deepest gratitude to all candidates for volunteering and now would like to welcome our new Vice Chair, Mark Datysgeld! 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(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org> From: Saewon Lee via Gnso-latin-diacritics <gnso-latin-diacritics(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Friday, February 28, 2025 at 6:16 PM To: Devan Reed <devan.reed(a)icann.org>, "GNSO-Latin-diacritics(a)icann.org" <gnso-latin-diacritics(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-latin-diacritics] VC CfV CLOSED_Latin Script Diacritics PDP Vice-Chair Election Notification Dear All, The Call for Volunteers for Vice Chair is now closed. Thank you, Sebastien Ducos and Mark Datysgeld, for volunteering for the Vice Chair position. The PDP WG Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> stipulates that one (1) Vice Chair may be selected to assist the Chair. As there are currently two (2) candidates, a poll will open for voting by the WG members. As guided below, please look out for the email to vote for the Latin Script Diacritics PDP WG Vice Chair and kindly complete the selection by next Wednesday, 05 March, 2025. Thank you for your kind cooperation. 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(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org> From: Devan Reed via Gnso-latin-diacritics <gnso-latin-diacritics(a)icann.org> Reply-To: Devan Reed <devan.reed(a)icann.org> Date: Friday, February 28, 2025 at 12:28 PM To: "GNSO-Latin-diacritics(a)icann.org" <gnso-latin-diacritics(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-latin-diacritics] Latin Script Diacritics PDP Vice-Chair Election Notification Dear all, You will recieve a separate email to vote for Latin Script Diacritics PDP Vice-Chair. Voting opens 28 February at 11:59 UTC and closes 05 March at 11:59 UTC. Subject line: Credentials to Access Ballot: Latin Script Diacritics Vice-Chair Election To vote, please click the URL provided in the email. Do not share your link. Two Candidates: Mark Datysgeld Sebastien Ducos After voting, you will receive a follow up email confirming your vote. If you do not see this email, check your spam, and reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Thank you. Kind regards, Devan

1 0