Hi Anne,
For completeness' sake I'll include Steve's response to your first part re "familiarity". I will still say that everyone should read it, your mileage may vary whether that is considered familiarity or not.
"Jennifer is right, that language is inspired by the IDNs EPDP Charter. The reason for its inclusion in that instance, as well as the suggested inclusion for the Latin Script Diacritics, is the recognition that these are rather niche topics, where requiring complete expertise of every single member is unreasonable. However, collective expertise is both more attainable, yet also important to the success of the work. I hope this helps."
For your second question about "delineating scope":
If the Latin GP identified variant code points that are allocatable, then the mechanism to handle them will be informed by the recommendations of Phase 1 and Phase 2 of the IDN EPDP.
Since they did not, this Latin Diacritics PDP is chartered to handle the process as appropriate. The reason the Latin RZ LGR is specifically called out in the scope, or what is not in scope is that the Latin RZ LGR does have cross-script variants (included because of cross-script transitivity reasons and blocked for various reasons) included in section 3 that I specifically called out. According to the issue report and the charter questions, these are not in scope - "This PDP is limited to examining a single issue. In circumstances where a base ASCII gTLD and the Latin script diacritic version of the gTLD are NOT variants of each other, what mechanism is needed in order to allow a single registry operator to simultaneously operate both gTLDs?" (p2, Latin Diacritics PDP draft charter).
All potential Latin Diacritics PDP WG members will need to know that this variant group exists in the Latin RZ LGR, and the rationale and impact of what it means when they start considering the charter questions.
Hope this helps clarify and not confuse!
Best,
Jennifer
From: Anne ICANN <anneicanngnso@gmail.com>
Sent: Saturday, December 14, 2024 1:39 AM
To: jen@dot.asia
Cc: 陳曼茹 Manju Chen <manju@nii.org.tw>; council@gnso.icann.org
Subject: Re: [council] Re: Motion to Adopt Charter for Latin Diacritics PDP
Thanks Jen. Just wanted to make sure the familiarity is not being required of each member as a pre-condition to joining the open model WG on this EPDP.
Separately, could you please clarify the meaning of "delineate scope" in your addition to the language of the Charter? Does this mean that if the Latin RZ-LGR concluded that quebec with an accent is NOT a variant of quebec without the accent, then quebec with the accent cannot be delegated to anyone because it's too similar to quebec without the accent and is not a variant thereof? (The problem we discovered under current policy was that quebec with an accent could not be delegated because it is not a variant of quebec without an accent in the Latin script RZ-LGR.)
Apologies for my lack of background in this matter. (I don't plan to join the WG.)
Thank you,
Anne
Apologize for
On Fri, Dec 13, 2024 at 7:10 AM <jen@dot.asia> wrote:
Hi Anne,
I believe this language: "Collectively as a group, the WG Members MUST possess:" was taken from the framework of the IDN EPDP charter (https://gnso.icann.org/sites/default/files/policy/2021/presentation/CharterGNSOIDNsEPDPWorkingGroup20May21.pdf , p 23). I defer to staff who prepared this language for the Latin Diacritics PDP, as to the interpretation of this chapeau.
My addition to the charter is on the scope (attached, pp 2-3), which also speaks to your question about "understanding of the Latin RZ LGR". This is a foundational document that all who participate in this PDP should read and understand the rationale and impact of it to start contemplation of the charter questions.
Hope this helps, happy to discuss further.
Best,
Jennifer
From: Anne ICANN <anneicanngnso@gmail.com>
Sent: Thursday, December 12, 2024 8:07 PM
To: 陳曼茹 Manju Chen <manju@nii.org.tw>
Cc: jen@dot.asia; council@gnso.icann.org
Subject: Re: [council] Re: Motion to Adopt Charter for Latin Diacritics PDP
Hi Jennifer and Manju,
Just one question regarding this Charter. It states that members MUST have certain background characteristics but lists the requirements as being applicable "collectively as a group." The first of these is a requirement for familiarity with the Latin Root Zone Label Generation Rules. I'm just wondering if every member of the WG is required to have that background or if we mean that some members having it are sufficient? This question arises because the draft charter says MUST (capitals and underlined) but also says it's an open model and the MUST is modified by an introductory clause "Collectively as a group".
Could you please clarify?
Thank you,
Anne
On Fri, Dec 6, 2024 at 9:02 PM 陳曼茹 Manju Chen via council <council@icann.org> wrote:
Hi all,
Happy to second this motion. Thanks!
Best,
Manju
On Sat, Dec 7, 2024 at 11:59 AM jen--- via council <council@icann.org> wrote:
Dear All,
I would like to submit the attached Motion to Adopt Charter for Latin Diacritics PDP. The draft charter (also attached) has been edited per Council discussion in Istanbul. The changes to the draft charter are as follows:
- Addition of language referencing Latin RZ LGR (section three: variants) to clarify scope
- Addition of the Global Public Interest and the reference to the checklist
- Adjustment of the WG membership structure to make it “Open model”
Best,
Jennifer
_______________________________________________
council mailing list -- council@icann.org
To unsubscribe send an email to council-leave@icann.org
_______________________________________________
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._______________________________________________
council mailing list -- council@icann.org
To unsubscribe send an email to council-leave@icann.org
_______________________________________________
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.