...
Questions from the Expert Working Group to Define Requirements for Internationalized Registration Data and Corresponding Data Model for gTLD Registries See: http://www.icann.org/en/news/announcements/announcement-08jul13-en.htm. 10 April 2014: Interim Report (Page 17)
The WG did note the following issues related to translation and transliteration and recommend the GNSO PDP to consider:
- If registrants are allowed to submit localized registration data, what languages or scripts are registrars or registry operators expected to support?
- If registrants are allowed to submit internationalized registration data, whether to require that users submit a corresponding single common script version of the internationalized registration data?
- If registrants are required to submit a single common script version of the internationalized registration data, are users expected to submit a translated version, a transliterated version, or “either” (provided there is a convention or method to distinguish between the two)?
- If registrants are required to submit a single common script version of the internationalized registration data and the user is unfamiliar with or unable to submit such a transformation, are registrars or registry operators expected to provideassistance provide assistance (and if so, how would such assistance be manifested)?
- If registrants are required to submit a single common script version and an internationalized version of their registration data, should there be a requirement to detect whether both literally match each other?
- If there are two versions of the registration data, which version should be considered primary or authoritative if there is a mismatch?
- If translated / transliterated versions of the data are required, how will data be maintained simultaneously in multiple languages/scripts? Should there be additional meta-level information?
- For company and individual names, should translation or transliteration be required?
...