<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-AU">-- <o:p></o:p></span></p>
<div>
<p class="MsoNormal">Kal Feher<o:p></o:p></p>
<p class="MsoNormal">Melbourne, Australia<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">Neustar<o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Idngwg <idngwg-bounces@icann.org> on behalf of "idngwg@icann.org" <idngwg@icann.org><br>
<b>Reply-To: </b>"Tan Tanaka, Dennis" <dtantanaka@verisign.com><br>
<b>Date: </b>Wednesday, 18 April 2018 at 05:27<br>
<b>To: </b>Sarmad Hussain <sarmad.hussain@icann.org>, "idngwg@icann.org" <idngwg@icann.org><br>
<b>Subject: </b>[EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets</span><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-AU"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN">Another way to look at this (at least I do) is to consider two uses cases:
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN">-use case 1: two (or more) IDN tables, same script</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN">-use case 2: two (or more) IDN tables, different scripts</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN">-Dennis</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:ZH-CN"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Idngwg <idngwg-bounces@icann.org> on behalf of Sarmad Hussain <sarmad.hussain@icann.org><br>
<b>Date: </b>Thursday, April 12, 2018 at 8:46 AM<br>
<b>To: </b>"idngwg@icann.org" <idngwg@icann.org><br>
<b>Subject: </b>[EXTERNAL] [Idngwg] Harmonization of Variant Sets</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><a name="_MailOriginalBody">Dear All,<o:p></o:p></a></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">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
<span style="background:yellow;mso-highlight:yellow">yellow highlighted</span> text in the attached document.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Regards,<br>
Sarmad<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
</div>
</body>
</html>