[Idngwg] latest draft of the IDN Guidelines 4.0

[Sarmad Hussain]

Dear All,

Please find the updated version 3.4 of the document, with the suggested changes incorporated.

Regards,
Sarmad

From: Idngwg [mailto:idngwg-bounces at icann.org] On Behalf Of Sarmad Hussain
Sent: Wednesday, April 18, 2018 8:27 PM
To: Feher, Kal <Kalman.Feher at team.neustar>; Tan Tanaka, Dennis <dtantanaka at verisign.com>; idngwg at icann.org
Subject: Re: [Idngwg] [EXTERNAL] Re: Harmonization of Variant Sets

Thank you Dennis and Kal.

If there is no further feedback on this, I will update the guidelines by removing the yellow highlighted portions shared earlier, removing the same-script requirement.  We can finalize during the call tomorrow.

Regards,
Sarmad

From: Feher, Kal [mailto:Kalman.Feher at team.neustar]
Sent: Wednesday, April 18, 2018 6:20 AM
To: Tan Tanaka, Dennis <dtantanaka at verisign.com<mailto:dtantanaka at verisign.com>>; Sarmad Hussain <sarmad.hussain at icann.org<mailto:sarmad.hussain at icann.org>>; idngwg at icann.org<mailto:idngwg at icann.org>
Subject: [Ext] Re: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets

I agree that removing the "same script|particular script" qualifiers will correctly convey the intent for guideline 13. I think that guideline 17 complements the harmonisation advice by ensuring that confusables, including pre-composed/decomposed representations, are considered across scripts. My reading of TR39 suggests that the two cases described would be covered in principle.

--
Kal Feher
Melbourne, Australia
Neustar
From: Idngwg <idngwg-bounces at icann.org<mailto:idngwg-bounces at icann.org>> on behalf of "idngwg at icann.org<mailto:idngwg at icann.org>" <idngwg at icann.org<mailto:idngwg at icann.org>>
Reply-To: "Tan Tanaka, Dennis" <dtantanaka at verisign.com<mailto:dtantanaka at verisign.com>>
Date: Wednesday, 18 April 2018 at 05:27
To: Sarmad Hussain <sarmad.hussain at icann.org<mailto:sarmad.hussain at icann.org>>, "idngwg at icann.org<mailto:idngwg at icann.org>" <idngwg at icann.org<mailto:idngwg at icann.org>>
Subject: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets

Another way to look at this (at least I do) is to consider two uses cases:
-use case 1: two (or more) IDN tables, same script
-use case 2: two (or more) IDN tables, different scripts

The core of the guideline is to harmonize variant rules (i.e. ensure symmetry and transitivity) across all IDN tables under a TLD. I think we were thinking Japanese and Chinese (at least I was) when we discussed the detail and final language. I don’t think it was our intention to discriminate same script vs cross-script. In this sense, it make sense to remove the “same script” qualifier.

-Dennis

From: Idngwg <idngwg-bounces at icann.org<mailto:idngwg-bounces at icann.org>> on behalf of Sarmad Hussain <sarmad.hussain at icann.org<mailto:sarmad.hussain at icann.org>>
Date: Thursday, April 12, 2018 at 8:46 AM
To: "idngwg at icann.org<mailto:idngwg at icann.org>" <idngwg at icann.org<mailto:idngwg at icann.org>>
Subject: [EXTERNAL] [Idngwg] Harmonization of Variant Sets

Dear All,

As discussed in the call today, here is a brief document discussing the harmonization of variant sets.  The “same-script IDN tables” in the guidelines allows for the examples in the document.  Additional guidelines on cross-script labels would prevent cross-script issues implicitly.   However, if the WG considers to make it explicit, it could be done by, for example, removing the yellow highlighted text in the attached document.

Regards,
Sarmad


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20180419/7ffa752e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IDN Guidelines 4.0 final draft 3.4.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 55116 bytes
Desc: IDN Guidelines 4.0 final draft 3.4.docx
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20180419/7ffa752e/IDNGuidelines4.0finaldraft3.4-0001.docx>