16 Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string
Prototypical answer:
gTLD | Full Legal Name | E-mail suffix | Detail | .みんな | Charleston Road Registry Inc. | google.com | View |
Charleston Road Registry (a wholly-owned subsidiary of Google Inc.) will use technology outsourced to Google to provide this registry solution. Details of Google’s implementation are discussed below.
Google limited its rendering⁄operational testing to the scope of domain names. That is, Google assumes the label is read left-to-right (LTR) and is used in conjunction with other LTR-read labels. As such, Google made no attempt to identify potential bidirectional (BIDI) or right-to-left (RTL) issues. With that said, Google did verify the string by:
1. Comparing the characters to the Unicode list of confusables [1] and RFC 5892 [2] and found no issues.
2. Validating that the string has meaning only in Japanese and found that to be true.
[1]. The Unicode Consortium, ʺʺRecommended confusable mapping for IDN, Version 2.1ʺʺ, April 2010, 〈http:⁄⁄www.unicode.org⁄Public⁄security⁄revision-04⁄confusables.txt〉.
[2]. P. Faltstrom, Ed. ʺʺThe Unicode Code Points and Internationalized Domain Names for Applications (IDNA)ʺʺ.RFC 5892. August 2010, http:⁄⁄tools.ietf.org⁄html⁄rfc5892.ʺ
Similar gTLD applications: (0)
gTLD | Full Legal Name | E-mail suffix | z | Detail |