.ged: Difference between revisions
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
==Letter to ICANN on String Similarity== | ==Letter to ICANN on String Similarity== | ||
Weeks prior to the announcement of the [[String Similarity Panel]]'s decision, the VPs of the [[.gea]] and .ged bids sent a letter to ICANN imploring them to recognize the differences in their TLD regardless of any perceived visual similarity. THe results of the string similiarity panel had been long delayed and the lack of guidance or sense of direction for the results can be read into the move by these new gTLD applicants. They note that their scopes are entirely different, serving different niche industries, and that they will be operating close registries. This leaves little room for any overlap, they argue, writing "for any likelihood of confusion to exist, it must be probable, not merely theoretically possible, that confusion will actually arise in the mind fo the average, reasonable Internet user. Mere visual similarity is not a sufficient basis to support a finding of string confusion."<ref>[http://www.icann.org/en/news/correspondence/laul-mussell-to-icann-18feb13-en Correspondence 18Feb13] Retrieved 25 Feb 2013</ref> | Weeks prior to the announcement of the [[String Similarity Panel]]'s decision, the VPs of the [[.gea]] and .ged bids sent a letter to ICANN imploring them to recognize the differences in their TLD regardless of any perceived visual similarity. THe results of the string similiarity panel had been long delayed and the lack of guidance or sense of direction for the results can be read into the move by these new gTLD applicants. They note that their scopes are entirely different, serving different niche industries, and that they will be operating close registries. This leaves little room for any overlap, they argue, writing "for any likelihood of confusion to exist, it must be probable, not merely theoretically possible, that confusion will actually arise in the mind fo the average, reasonable Internet user. Mere visual similarity is not a sufficient basis to support a finding of string confusion."<ref>[http://www.icann.org/en/news/correspondence/laul-mussell-to-icann-18feb13-en Correspondence 18Feb13] Retrieved 25 Feb 2013</ref> | ||
It was revealed days later that only 2 contention sets were created by ICANN, [[.unicom]] with [[.unicorn]], and [[.hotels]] with [[.hoteis]].<ref>[http://www.icann.org/en/news/announcements/announcement-26feb13-en.htm Announcement 26Feb13, ICANN.org] Retrieved 27 Feb 2013</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Revision as of 18:39, 27 February 2013
| Status: | Proposed |
| Type: | Generic |
| Category: | Education |
More information: 
| |
.ged is a proposed TLD in ICANN's New gTLD Program. The applicant is GED Domains LLC.[1]
Letter to ICANN on String Similarity[edit | edit source]
Weeks prior to the announcement of the String Similarity Panel's decision, the VPs of the .gea and .ged bids sent a letter to ICANN imploring them to recognize the differences in their TLD regardless of any perceived visual similarity. THe results of the string similiarity panel had been long delayed and the lack of guidance or sense of direction for the results can be read into the move by these new gTLD applicants. They note that their scopes are entirely different, serving different niche industries, and that they will be operating close registries. This leaves little room for any overlap, they argue, writing "for any likelihood of confusion to exist, it must be probable, not merely theoretically possible, that confusion will actually arise in the mind fo the average, reasonable Internet user. Mere visual similarity is not a sufficient basis to support a finding of string confusion."[2]
It was revealed days later that only 2 contention sets were created by ICANN, .unicom with .unicorn, and .hotels with .hoteis.[3]
References[edit | edit source]
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ Correspondence 18Feb13 Retrieved 25 Feb 2013
- ↑ Announcement 26Feb13, ICANN.org Retrieved 27 Feb 2013