Three critical reasons against the string comparison as proposed by the IRT
\na) It subverts the bottom-up consensus of the new gTLD process.
\nString confusion issue was firstly researched by the GNSO IDN WG, which eventually stated that string confusion should be limited to visual similiarity. This is confirmed by the GNSO document to the Board. Although the gTLD guidebook is ambiguous on string confusion, which only says that any string should not inflict “user confusion”, the IRT proposal should not betray the community consensus by stretching it to “meaningful” confusion.
\nb) It is legally baseless.
\nNo international law allows for trademark protection in translated form except for well-known marks. The string confusion extending to commerical impression (meaningful similarity) is equivalent to create additional protection indiscrimatively for all the marks, which is not acceptedly internationally.
\nc) It breaches free speech.
\nNo trademark owner owns the meaning of a trademark, let alone the meaning in any script or language. A cross-script monopoly for words or “meaning” of a trademark is obvously not the intent of the new gTLD program.<\/p>\n
Unreasonableness of IP Clearing House<\/p>\n
It is a sham for uniform mandatory sunrise imposed on indiscriminately on all the potential new gTLD operators. This mandatory uniform sunrise approach can easily be gamed. Look at the thousands of trademarks registered in preparation for the new gTLDs. I can see hundreds of “.music” trademarks in various territories that can be searched and verified, not Tunisian registrations, but why should they be prioritized? I really want to know if such “clearing” covers the translation of a federally registered trademark or limited to the original mark string per se. If it were the first case, it would almost become a death sentence to IDNs (thinking about the trademark flooding to game the clearing house!).<\/p>\n","protected":false},"excerpt":{"rendered":"
Three critical reasons against the string comparison as proposed by the IRT a) It subverts the bottom-up consensus of the new gTLD process. String confusion issue was firstly researched by the GNSO IDN WG, which eventually stated that string confusion should be limited to visual similiarity. This is confirmed by the GNSO document to the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1,4],"tags":[],"_links":{"self":[{"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/posts\/142"}],"collection":[{"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=142"}],"version-history":[{"count":2,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/posts\/142\/revisions"}],"predecessor-version":[{"id":150,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=\/wp\/v2\/posts\/142\/revisions\/150"}],"wp:attachment":[{"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=142"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/wiki.iipl.org.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}