<html xmlns:v="urn:schemas-microsoft-com:vml" 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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Dear Shanmugam, all,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Please find below the review of the proposal by IP. Please visit <a href="https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en">here</a> to see the Arabic proposal, in case you would like to review the no-mix rule. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Kindly let us know if you have any queries. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>We look forward to the final version, incorporating the feedback.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Regards,<br>Sarmad<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><span style='color:windowtext'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:windowtext'><o:p> </o:p></span></p><p>To: NeoBrahmi Generation Panel<br>From: Integration Panel<br>Subject: Review of Tamil LGR dated Dec 6, 2018<br><br>We have reviewed the updated proposal dated 2018-12-06 including XML and TXT files.<o:p></o:p></p><p>Here are our findings:<o:p></o:p></p><p><b>TECHNICAL / DOCUMENTATION ISSUE</b><o:p></o:p></p><div><p class=MsoNormal>Tamil is one of the few LGRs that assign an "allocatable" variant, yet the LGR did not defined a "no-mix" rule to prevent needless multiplication of variant labels where the same label alternates the variant used.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The LGR makes the two encodings of SRI/SHRI allocatable but it is not clear why it would be essential, or even desirable to support all 4 permutations in a case where SHRI/SRI occurs twice in the same label.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>--- SRI ---- SRI ---<o:p></o:p></p></div><p class=MsoNormal>--- SRI ---- SHRI ---<o:p></o:p></p></div><p class=MsoNormal>--- SHRI ---- SRI --- <o:p></o:p></p><div><div><p class=MsoNormal>--- SHRI ---- SHRI ---<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal>Here "---" stands for some code points common to both labels.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>It seems only necessary to allow one or the other spelling consistently for a single label.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If, unexpectedly, there is some requirement to cater to all possible permutations, then this needs to be documented very clearly and the cost for supporting it (potentially many more than 2 allocatable labels) must be spelled out.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Alternatively, the LGR should be amended to contain a "no-mix" rule, patterned after the Arabic LGR's no-mix rules, or other suitable restriction.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><b>DOCx:</b><o:p></o:p></p></div><div><p class=MsoNormal>The main document shows no changes other than what looks like minor copy editing/editorial. No additional issues identified. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In section 5.2.1, only the variant sequences for 6.1.3 have been listed, but not the ones for 6.1.1 (U+0B92 U+0BB3) and 6.1.2 (U+0BC6 U+0BB3). This is not consistent and is at odd with the XML/HTML where obviously sequences appear along single code points.<o:p></o:p></p><p class=MsoNormal>The remedy is add these 2 sequences in section in 5.2.1 with references to 6.1.1 and 6.1.2 as it has already been done for the other pair.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>While the two sets are slightly different because the sets for 6.1.1 and 6.1.2 are 2 to 1 variants unlike the one in 6.1.3, the difference appears immaterial for this purpose and having a full list of sequences in section 5 makes sense. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><b>XML:</b><o:p></o:p></p></div><div><p class=MsoNormal>No changes found other than Date. One common <b>editorial issue</b>:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>(1) as with all LGRs the placeholders in the <description> need to be updated with <u>final date and URL:</u><o:p></o:p></p></div><div><p class=MsoNormal> Neo-Brahmi Generation Panel, "Proposal for a Tamil Script Root Zone Label Generation Rule-Set (LGR)", [URL and Date TBD]<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The XML passes the tool<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><b>TXT:</b><o:p></o:p></p></div><div><p class=MsoNormal>Test label file verified; existing TLDs show as valid.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>