Bureaucrats, staff, Administrators
8,157
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 15:
Line 15: − + Line 24:
Line 24: + + +
no edit summary
{{TLD|
{{TLD|
|logo =
|logo =
|status = Proposed
|status = Delegated
|manager = [[Verisign]]
|manager = [[Verisign]]
|country =
|country =
|keypeople =
|keypeople =
}}
}}
'''كوم.'''is one of 9 transliteration of [[.com]] that [[Verisign]] has applied for via [[ICANN]]'s [[New gTLD Program]]. The company also applied for 3 transliterations of [[.net]].<ref>[http://idnblog.com/2012/06/13/com-transliterated-8-languages/ Com Transliterated 8 languages]</ref>
'''كوم.'''is one of 9 transliteration of [[.com]] that [[Verisign]] has applied for via [[ICANN]]'s [[New gTLD Program]]. The company also applied for 3 transliterations of [[.net]].<ref>[http://idnblog.com/2012/06/13/com-transliterated-8-languages/ Com Transliterated 8 languages]</ref> Verisign manages this TLD and is its [[Registry]]. The proposed application succeeded and was delegated to the [[Root Zone]] on 28 July, 2015.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated String, ICANN.org] Retrieved 30 Jul 2015</ref>
This particular application was criticized during the comment period of the new gTLD program given that no such "COM" word exists in Arabic and so Verisign is essentially inventing an Arabic word. The objection states that Verisign should not be given the TLD without approval of the Arabic Language Academy.<ref>[https://gtldcomment.icann.org/comments-feedback/applicationcomment/commentdetails/208 CommentDetails, gTLDComment.ICANN.org]</ref>
This particular application was criticized during the comment period of the new gTLD program given that no such "COM" word exists in Arabic and so Verisign is essentially inventing an Arabic word. The objection states that Verisign should not be given the TLD without approval of the Arabic Language Academy.<ref>[https://gtldcomment.icann.org/comments-feedback/applicationcomment/commentdetails/208 CommentDetails, gTLDComment.ICANN.org]</ref>
In the end, the languages chosen for transliterations are: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].
In the end, the languages chosen for transliterations are: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].
In July 2013, Verisign's [[Pat Kane]] outlined in an article<ref>[http://blogs.verisigninc.com/blog/entry/update_on_verisign_s_idn Update on Versigns IDNs Versigininc.com] Retrieved 4 Oct 2013</ref> the company's plans for allowing existing registrants of second-level [[IDN]] domain names to secure the matching domain under Verisign's new [[IDN]] gTLDs. For example, if you're the registrant of the Hebrew word for "website" that is registered as a second-level domain under [[.com]], you will have the rights to that second-level name under the gTLD "[[.קוֹם|קוֹם.]]" but you will not have the rights under the Hebrew transliteration of ".net" if it existed.<ref>[http://domainincite.com/13702-verisign-lays-out-buy-once-idn-gtld-plans Verisign lays out buy once IDN gTLD plans, Domain Incite] Retrieved 4 Oct 2013</ref>
===Application===
===Application===
Excerpted from applicant response to question #18 in TLD application:
Excerpted from applicant response to question #18 in TLD application: