.קוֹם: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 5: | Line 5: | ||
|language = Hebrew | |language = Hebrew | ||
|translation = Transliteration of "com" | |translation = Transliteration of "com" | ||
|manager = | |manager =[[Verisign]] | ||
|registryprovider = | |registryprovider = [[Verisign]] | ||
|registrations = | |registrations = | ||
|date = | |date = | ||
| Line 23: | Line 23: | ||
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: | ||
Latest revision as of 19:48, 4 October 2013
| Status: | Proposed |
| Language: | Hebrew |
| Translates to: | Transliteration of "com" |
| Manager: | Verisign |
| Registry Provider: | Verisign |
| Type: | IDN gTLD |
| Category: | Technology |
More information: 
| |
קוֹם is an IDN gTLD being proposed in ICANN's New gTLD Program. The applicant is Verisign.[1]
IDN Transliterations of .com & .net[edit | edit source]
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[edit | edit source]
Excerpted from applicant response to question #18 in TLD application:
"As of this writing, more than 800,000 internationalized second-level domain names are registered
in .com, including approximately 12,000 in Hebrew. The HEBREW_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” domain names. That is, registrants can use their preferred script in both the second-level domain name and the gTLD name. Doing so improves these domain names’ functionality and accessibility to speakers of non-Latin-based languages.
[..]
The initial target audience for HEBREW_TRANSLITERATION_OF_.COM is the registrants of the approximately 12,000 IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. HEBREW_TRANSLITERATION_OF_.COM addresses."[7]
References[edit | edit source]
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ 2011 Results Earnings Call Transcript, SeekingAlpha.com. Published 26 January 2012.
- ↑ Verisign Plans to Apply for About 12 New Top Level Domain Names, DomainNameWire.com. Published 26 January 2012.
- ↑ Verisign to Apply for a Dozen New gTLDs, DomainIncite.com. Published 27 January 2012.
- ↑ Update on Versigns IDNs Versigininc.com Retrieved 4 Oct 2013
- ↑ Verisign lays out buy once IDN gTLD plans, Domain Incite Retrieved 4 Oct 2013
- ↑ Application Download, gTLDresult.ICANN.orgRetrieved 17 Jan 2013