ICANN/GNSO GNSO Email List Archives

[ispcp]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ispcp] translation and transliteration of contact information

  • To: "Mike O'Connor" <mike@xxxxxxxxxx>, <ispcp@xxxxxxxxx>
  • Subject: Re: [ispcp] translation and transliteration of contact information
  • From: "WUKnoben" <wolf-ulrich.knoben@xxxxxxxxxxx>
  • Date: Fri, 7 Mar 2014 21:35:35 +0100
  • Importance: Normal
  • In-reply-to: <96935841-E2F9-4C7B-8F90-3A3BC305F200@haven2.com>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <96935841-E2F9-4C7B-8F90-3A3BC305F200@haven2.com>
  • Reply-to: "WUKnoben" <wolf-ulrich.knoben@xxxxxxxxxxx>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx

Thanks Mikey,

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...

Best regards

Wolf-Ulrich



From: Mike O'Connor 
Sent: Friday, February 28, 2014 12:15 AM
To: ispcp@xxxxxxxxx 
Subject: [ispcp] translation and transliteration of contact information

hi all, 

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

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).

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.  

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.  

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.

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

see?  ravings of an idiot.  but maybe that’s enough to get conversation started.  does that help, Wolf-Ulrich?

mikey



PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) 


<<< Chronological Index >>>    <<< Thread Index >>>