<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Kim,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I am not certain registries would want to use an automated/machine-readable mechanism for importing tables from other registry IDN implementations. Implementations vary widely from one registry to another, each IDN implementation often requires hand-verification of allowed code points combined with business policies.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Let’s try an example:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">CDNC regularly publishes and updates the set of valid codepoints in the Han script, along with contextual and variant generation rules/guidelines. Publishing those set of rules in this rich format would be useful; however, registries will still need to manually verify both the codepoints and the rules for variant generation, and create business rules for allocation and delegation of applied for strings.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Feels like a nice to have, not a must have.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-Ram</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">---------------------------------------------------------------------------------</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Ram Mohan</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">(o) +1.215.706.5700 x103 (m) +1.215.431.0958 (f) +1.215.706.5701</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><a href="mailto:rmohan@afilias.info"><span style="color:#1f497d">rmohan@afilias.info</span></a> | Skype: gliderpilot30 | Twitter @rmohan123</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">---------------------------------------------------------------------------------</span></p></div><p class="MsoNormal">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kim Davies [mailto:<a href="mailto:kim.davies@icann.org">kim.davies@icann.org</a>] <br>
<b>Sent:</b> Monday, March 12, 2012 9:24 AM<br><b>To:</b> Jaap Akkerhuis<br><b>Cc:</b> <a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a>; Dillon, Chris; Abdulrahman I. ALGhadir; <a href="mailto:vip@icann.org">vip@icann.org</a><br>
<b>Subject:</b> Re: Draft on IDN Tables in XML</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal">Hi Jaap,</p><div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On Mar 12, 2012, at 3:34 AM, Jaap Akkerhuis wrote:</p>
</div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal"><span style="color:black"><br></span>As far as I know, the idea of the tables have always been to provide<br>a public central place where the registries could list which<br>
characters they support and which they don't in their registrer<br>plolicies. It is an "for your information only" registry and meant<br>for human consumption.<br><br>And Kim, do correct me if this isn't the case anymore.</p>
</div></blockquote></div><p class="MsoNormal"> </p><div><p class="MsoNormal">It is certainly correct that the notion of tables is to publicly share registry policy as it relates to code points that are accepted for registration. I think, however, it is a bit beyond merely informational, as a key driver in publishing them has been to allow sharing and re-use by other registries. Having a machine readable format that allows the tables to be imported and repurposed aids this greatly.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">One of the reasons I feel this is a good initiative is an increasing number of tables appear to be published as PDF files with various contextual rules described in paragraphs of normative text. It would be nice to reverse this trend and have a format rich enough that it can express most if not all registry policies in a common way using a set of agreeable primitives.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">kim</p></div></div></div></div></body></html>