<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Chris,<br>
<br>
Is it possible to distribute the DOC version of the file? It's
much easier to comment inline than to write on paper or transcribe
comments into an email message.<br>
<br>
Thanks,<br>
<br>
Jim<br>
<br>
<br>
<br>
</tt>
<div class="moz-cite-prefix">On 11/26/14, 6:50 AM, Dillon, Chris
wrote:<br>
</div>
<blockquote
cite="mid:DB4PR01MB0461B85A2E28818C6D71B86ADD700@DB4PR01MB0461.eurprd01.prod.exchangelabs.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Century Gothic",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">Dear colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">As I mentioned in my last meeting I
would like to continue Thursday's call virtually,
encouraging you to comment on version 5 of the Draft initial
report (attached). Here are the comments I would have made
if we had had more time: <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">p.12 Mike asks us [MZ14 and MZ31]
whether "increase in users that are not familiar with the
Latin script" should be replaced with "increase in users
whose languages are not based on the Latin script". Both
aspects are true, but the latter wording hints at the former
and so is a good replacement. As a statement the latter
version would also be less Anglocentric.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">In MZ15, Mike suggests that some
statements about law enforcement are actually broader. That
seems true and I can at least add "for example". However,
does anyone have concrete examples of organizations apart
from law enforcement for which transformation to a Latin
script would be useful?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">p.13 In ER16 and ER17 Erika
highlights an apparent contradiction. The bullet point at
the top of p.12 says that transformation would need to take
place at a later stage (than entry by registered name
holders) and that this would be detrimental to accuracy and
consistency. The bullet point above the ccTLD graphic argues
that only the data fields should be transformed by the
registrar or registry. I will make clear the distinction
between transformation (of data - how we have been using the
term "transformation" on its own) and transformation of
field names. Moreover, accuracy (at least senses 1 and 2 in
the footnote) and consistency are likely to be worse the
greater number of players involved i.e. if registrants were
to do the transformation.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">CD18 Is anyone aware of reasons why
the ccTLD approach exemplified wouldn't work with gTLDs?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">I reckon MZ21 is addressed by "not
justified by benefits to others", the last line of p.12.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">MZ22 suggests the text "if no
consensus is reached the status quo will be maintained". The
key thing here is whether we're talking about the current
Whois status quo where the system cannot accept non-Latin
script data (answer "no" as this does not encourage the
development of the Internet in wide areas of the world not
using the Latin script), or a new DNRD with no Latin script
(answer "no" as such a system would be very expensive, as it
would need to be replaced soon) or a new DNRD with non-Latin
script functionality (answer: possibly "yes" as the status
quo would not involve transformation, except possibly of
field names).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">ER23 picks up how we would handle a
situation where we move from no clear consensus to a greater
level of consensus. The short answer is to use the GNSO
procedure.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">ER27 Automated transformation
cannot occur if data are not marked as being in a language.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">ER29 "it" refers to "contact
information data" and so should be "them". India-based
companies are an interesting case, as in many cases there
will be three or more possible languages - Hindi, English
and a local language. If the language is not stipulated,
there will be consistency issues in the event of
transformation. Lars suggests the language the registrar
operates in, but again there could be several and bad actors
could deliberately apply in different languages to different
registrars.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">As usual I welcome your views on
any of these issues, or issues not in this list. I shall
circulated a new version of the draft initial report shortly
before our meeting on Thurs. 4 December.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">Chris.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">--<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Century
Gothic",sans-serif">Research Associate in Linguistic
Computing, Centre for Digital Humanities, UCL, Gower St,
London WC1E 6BT Tel +44 20 7679 1599 (int 31599)
<a moz-do-not-send="true"
href="http://www.ucl.ac.uk/dis/people/chrisdillon">www.ucl.ac.uk/dis/people/chrisdillon</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>