<HTML><HEAD>
<META content="text/html charset=windows-1252" http-equiv=Content-Type></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Thanks Mikey,</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">it reflects
to a certain extent the views within the WG. But we did not yet reach that far.
We are still collecting questions, then try to prioritize them...<BR><BR>Best
regards<BR><BR>Wolf-Ulrich<BR><BR></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=mike@haven2.com
href="mailto:mike@haven2.com">Mike O'Connor</A> </DIV>
<DIV><B>Sent:</B> Friday, February 28, 2014 12:15 AM</DIV>
<DIV><B>To:</B> <A title=ispcp@icann.org
href="mailto:ispcp@icann.org">ispcp@icann.org</A> </DIV>
<DIV><B>Subject:</B> [ispcp] translation and transliteration of contact
information</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>hi
all,
<DIV> </DIV>
<DIV>i’m responding to Wolf-Ulrich’s request for thoughts on this topic — mostly
by starting this thread on our list. i have to admit i’m pretty clueless
about this issue so view these comments as the ravings of the Village Idiot,
Wolf-Ulrich</DIV>
<DIV> </DIV>
<DIV>it seems to me that maybe a way to carve a middle ground is for
registry/registrars to provide the *opportunity* for registrants to enter *their
own* translated/transliterated information in a non-latin script if they so
choose. it seems that might address both the problem of accuracy (which
seems really hard if it’s done by machine) and cost (since the burden of data
entry and accuracy would remain with the registrant and all the R’s would have
to do is provide data-collection and display mechanisms — essentially extending
Whois data to cover optional scripts).</DIV>
<DIV> </DIV>
<DIV>i think the notion of having the Ry/Rr doing the
translating/transliterating is going to be really hard for them to do
accurately, and that the cost of that effort would be prohibitive. </DIV>
<DIV> </DIV>
<DIV>the question of *requiring* the registrant to enter information into a
non-Latin script is interesting/complicated, especially if they’re not familiar
with the language/script. </DIV>
<DIV> </DIV>
<DIV>it seems this project is dependent on the outcome of the EWG and the
subsequent PDP to a certain extent. how can this PDP really make solid
recommendations without knowing what the capabilities of the underlying
registrant data system will be? it seems as though this effort will be
hampered by that.</DIV>
<DIV> </DIV>
<DIV>it seems as though this project will also run into “universal acceptance”
type problems until the transition from current Whois to The Next Thing is
complete — so an aggressive implementation schedule seems complicated</DIV>
<DIV> </DIV>
<DIV>see? ravings of an idiot. but maybe that’s enough to get
conversation started. does that help, Wolf-Ulrich?</DIV>
<DIV> </DIV>
<DIV>mikey</DIV>
<DIV> </DIV>
<DIV>
<DIV> </DIV>
<DIV apple-content-edited="true"><BR class=Apple-interchange-newline><SPAN
style="WHITE-SPACE: normal; WORD-SPACING: 0px; TEXT-TRANSFORM: none; FLOAT: none; COLOR: rgb(0,0,0); FONT: 12px helvetica; ORPHANS: 2; WIDOWS: 2; DISPLAY: inline !important; LETTER-SPACING: normal; TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px; -webkit-text-size-adjust: auto">PHONE:
651-647-6109, FAX: 866-280-2356, WEB: <A
href="http://www.haven2.com">www.haven2.com</A>, HANDLE: OConnorStP (ID for
Twitter, Facebook, LinkedIn, etc.)</SPAN> </DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV></BODY></HTML>