Difference between revisions of ".コム"

From ICANNWiki
Jump to navigation Jump to search
(Created page with "{{TLD| |logo = |status = Proposed |country = |language = Japanese Katakana |translation = Transliteration of "com" |manager = |registryprovider = Verisign |regist...")
 
 
(4 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
|status = Proposed
 
|status = Proposed
 
|country  =  
 
|country  =  
|language = Japanese Katakana
+
|language = Japanese (Katakana)
 
|translation = Transliteration of "com"
 
|translation = Transliteration of "com"
|manager  =
+
|manager  =[[Verisign]]
 
|registryprovider  = [[Verisign]]
 
|registryprovider  = [[Verisign]]
 
|registrations  =  
 
|registrations  =  
Line 12: Line 12:
 
|category  = [[:Category:Technology New gTLDs|Technology]]
 
|category  = [[:Category:Technology New gTLDs|Technology]]
 
|community  =  
 
|community  =  
 +
|priority =  105
 
|keypeople  =
 
|keypeople  =
 
}}
 
}}
  
 
'''.コム''' is an [[IDN]] [[gTLD]] being proposed in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Verisign]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
 
'''.コム''' is an [[IDN]] [[gTLD]] being proposed in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Verisign]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
 +
===IDN Transliterations of .com & .net===
 +
Verisign's [[Pat Kane]] noted in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be [[IDN]] transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript], SeekingAlpha.com. Published 26 January 2012.</ref> Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names], DomainNameWire.com. Published 26 January 2012.</ref><ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs], DomainIncite.com. Published 27 January 2012.</ref>
  
 +
During its first quarter earnings report, on April 26, 2012, it was confirmed that Verisign would be applying for 14 new gTLDs, 12 of which are foreign language transliterations of .com and .net.
 +
 +
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===
 +
Excerpted from applicant response to question #18 in TLD appliation:
 +
<br><br>
 +
"As of this writing, more than 800,000 internationalized second-level domain names are registered in .com, including approximately 50,000 in Katakana. The JAPANESE_TRANSLITERATION_OF_.COM gTLD, along with the other proposed IDN transliterations of .com, provide an immediate benefit to registrants of those names by giving them the opportunity to register IDN second-level domain names as “IDN.IDN”
 +
 +
[..]
 +
 +
The initial target audience for JAPANESE_TRANSLITERATION_OF_.COM is the registrants of the approximately 50,000 IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. JAPANESE_TRANSLITERATION_OF_.COM addresses."<ref>[http://gtldresult.icann.org/application-result/applicationstatus Application Download, gTLDresult.ICANN.org]Retrieved 17 Jan 2013</ref>
 +
 +
domain names.
 
==References==
 
==References==
 
{{reflist}}
 
{{reflist}}

Latest revision as of 19:44, 4 October 2013

Status: Proposed
Language: Japanese (Katakana)
Translates to: Transliteration of "com"
Manager: Verisign
Registry Provider: Verisign
Type: IDN gTLD
Category: Technology
Priority #: 105

.コム is an IDN gTLD being proposed in ICANN's New gTLD Program. The applicant is Verisign.[1]

IDN Transliterations of .com & .net

Verisign's Pat Kane noted in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be IDN transliterations of .com.[2] Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.[3][4]

During its first quarter earnings report, on April 26, 2012, it was confirmed that Verisign would be applying for 14 new gTLDs, 12 of which are foreign language transliterations of .com and .net.

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[5] 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.[6]

Application

Excerpted from applicant response to question #18 in TLD appliation:

"As of this writing, more than 800,000 internationalized second-level domain names are registered in .com, including approximately 50,000 in Katakana. The JAPANESE_TRANSLITERATION_OF_.COM gTLD, along with the other proposed IDN transliterations of .com, provide an immediate benefit to registrants of those names by giving them the opportunity to register IDN second-level domain names as “IDN.IDN”

[..]

The initial target audience for JAPANESE_TRANSLITERATION_OF_.COM is the registrants of the approximately 50,000 IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. JAPANESE_TRANSLITERATION_OF_.COM addresses."[7]

domain names.

References