Satish and Bill,

Some notes for a possible design rule checking are given below:

This reference LGR is designed for use in zones shared by more than one script. 

Both the Generation Panel and Integration Panel need to be looked into together.  The Integration Panel is a vital component in the implementation.

Where appropriate, cross-script variants have been defined to mutually exclude labels from different scripts that could otherwise be substituted by the users. 

Once a label has been delegated for one script, any variant labels from other scripts consisting of cross-script variants would be blocked. 

Any label containing at least one code point that is not a cross-script variant would be considered distinct. Because of that, even large numbers of defined cross-script variants generally do not lead to a high percentage of labels experiencing a collision.

I suppose IDNs is more towards the Machine rather than the Human.

Sincerely,



Gopal T V
0 9840121302
https://vidwan.inflibnet.ac.in/profile/57545
https://www.facebook.com/gopal.tadepalli
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Dr. T V Gopal
Professor
Department of Computer Science and Engineering &
Director, Centre for Applied Research in Indic Technologies [CARIT]
College of Engineering, Guindy Campus
Anna University
Chennai - 600 025, INDIA
Ph : (Off) 22351723 Extn. 3340
       (Res) 24454753
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: Satish Babu via CPWG <cpwg@icann.org>
Sent: 21 January 2025 07:28
To: Bill Jouris <b_jouris@yahoo.com>
Cc: CPWG <cpwg@icann.org>
Subject: [CPWG] Re: Recommendations for the Third Public Comment Proceeding on Draft AGB Text
 
Hi Bill

My understanding on this matter is that irrespective of the actual use by language/script communities, allocatable variants are those that are identified by its Generation Panel (GP) output as allocatable. If the GP has taken a position that goes against practices of script communities, then such issues should be (or should have been) taken up with the GP itself.

Currently, the online RZ-LGR provides an authoritative mechanism (and the only mechanism, according to the EPDP on IDNs Phase 1 Recommendations) to identify allocatable variants for a given string. There is thus no ambiguity for applicants.

With kind regards




satish



On Mon, Jan 20, 2025 at 11:49 PM Bill Jouris via CPWG <cpwg@icann.org> wrote:
Hi Justine, 

I'm not sure if this constitutes a suggestion, or merely a comment.  Regarding the first point (on 1.2.2.6 and 1.2.2.7).  

Allocatable variants are those which are used interchangeably (to at least some extent, and in some languages using the script).  For the Latin script, there are no more than 2.  The reason for that being that the Latin Generation Panel had speakers of maybe a half dozen of the hundreds of languages which use that script.  Meaning that it was impossible to know what characters were used interchangeably in one or another of those languages.  So there are, potentially, a very large number of cases (and for certain several known ones) which should be allocatable variants, but are not so identified. 

I'm not sure how, or whether, the next round proposes to address this shortcoming.  And the Applicant Guidebook may not be the right place to do something about it.  But I persist in noting the elephant in the room. 

Bill Jouris

On Friday, January 17, 2025 at 04:36:53 PM PST, Justine Chew via CPWG <cpwg@icann.org> wrote:


All,

At the last CPWG Call on 15 Jan, the review team for the Third Proceeding for Proposed Language for Draft Sections of Next Round AGB had very briefly presented 5 points which could form an ALAC Comment for this public comment proceeding.

It is our recommendation that the 5 points (found in summary on slide #3) be developed further into a first draft ALAC Comment and presented subsequently for CPWG comment.  

In order to take the recommended step, and given that we did not have time to do the same during the 15 Jan call, we are now seeking input for support and/or additional suggestions to our 5 recommended points - which touch on 3 topics of (1) TLD Types, (2) Security and Stability and (3) Community Input and Dispute Resolution.

Please let us have your input by Monday, 20 Jan at 23:59 UTC, to allow the review team (who have also agreed to be penholders for the comment) to prepare the first draft of an ALAC Comment in time for consideration at the next CPWG Call on 22 Jan.  

For avoidance of doubt, the review team shall take no forthcoming input or non-significant objection as a sign of support for us to proceed with drafting an ALAC Comment as mentioned. We would be happy to take questions regarding our recommendations as well, in reply to this thread.

Kind regards,

Avri Doria, Nthabiseng Pule and Justine Chew

_______________________________________________
CPWG mailing list -- cpwg@icann.org
To unsubscribe send an email to cpwg-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.

Virus-free.www.avg.com
_______________________________________________
CPWG mailing list -- cpwg@icann.org
To unsubscribe send an email to cpwg-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.