I think last we heard from ICANN/IP (I forgot whether it was Sarmad or Asmus who said it), their view is to use lowercase only as that is the framework for IDNA2008. However I am not sure if the Latin GP has already resolved the issue. Edmon -----Original Message----- From: hotta@jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Tuesday, February 12, 2019 12:26 AM To: Edmon <edmon@registry.asia> Cc: ChineseGP@icann.org; JapaneseGP@icann.org; KoreanGP@icann.org Subject: Re: [Japanesegp] on the issue of visual similarity Hi Edmon, Thank you for the information. I understand and agree to your logic. BTW, when I read your mail a question, which might have already been answered, came up to my mind. Are 'l' (lower-case 'L') and 'I' (upper-case 'i') defined as variants because of their visual similarity? Hiro On Mon, 11 Feb 2019 16:49:20 +0800 "Edmon" <edmon@registry.asia> wrote:
Hi Everyone,
Building on the correspondence already sent to ICANN: https://www.icann.org/resources/pages/correspondence (Jan 25, 2019 https://www.icann.org/en/system/files/correspondence/wei-et-al-to-marby-25ja...), in a recent conversation, I came across a further realization that I think is useful to share here.
In our previous discussion with ICANN and the IP, there was a question posed on whether the Latin GP would take into consideration the issues of the digits "0"/"1" and the letters "O"/"l"/"I". The response summarily provided was that because the rootzone did not allow for digits and hyphens the Latin GP would not have to tackle the issue.
That logic is flawed.
The development of the root zone LGR for Latin must take into consideration such visual similarities IF visual similarities are to be considered for ANY rootzone LGRs. That is because digits are "reserved names" and any new TLD proposed must NOT conflict with "reserved names".
As such, IF visual similarities for any rootzone LGR needs to be considered, it must also be applied to the Latin GP for reserved names. I.e. whether "OOI" should be a "variant" or not with "001" or whether it should be handled by other string confusion mechanisms, in this case, string confusion with a reserved string.
Of course, my position remains that these issues are and should correctly be addressed with such other string confusion mechanisms. Anyway, just a note for everyone so that we can more properly ask the question of ICANN and IP on the visual similarity issue.
Edmon
_______________________________________________ japanesegp mailing list japanesegp@icann.org https://mm.icann.org/mailman/listinfo/japanesegp