27,652
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + Line 15:
Line 15: + +
no edit summary
It remains unclear whether or not many of the 3 character new gTLD applications will face a high probability of being deemed too similar to existing ccTLDs. According to industry blog, [[DomainIncite]], 304 of 375 applications for three-letter gTLDs have only one character variance with one or more existing [[ccTLD]]. In total, if a single additional character is enough to create similarity, there are 368 potential ccTLD/gTLD conflicts in the current application round. Furthermore, the visual similarity ratio between ccTLDs and gTLDs, as measured by ICANN's [[SWORD Algorithm]] is generally only a few percentage points lower than in the case of TLDs that have already been rejected on confusing similarity grounds.<ref>[http://domainincite.com/pro/tag/string-similarity-panel/ String Similarity Panel, DomainIncite.com/pro]</ref>
It remains unclear whether or not many of the 3 character new gTLD applications will face a high probability of being deemed too similar to existing ccTLDs. According to industry blog, [[DomainIncite]], 304 of 375 applications for three-letter gTLDs have only one character variance with one or more existing [[ccTLD]]. In total, if a single additional character is enough to create similarity, there are 368 potential ccTLD/gTLD conflicts in the current application round. Furthermore, the visual similarity ratio between ccTLDs and gTLDs, as measured by ICANN's [[SWORD Algorithm]] is generally only a few percentage points lower than in the case of TLDs that have already been rejected on confusing similarity grounds.<ref>[http://domainincite.com/pro/tag/string-similarity-panel/ String Similarity Panel, DomainIncite.com/pro]</ref>
[[ICANN]]'s deadline for the results of the String Similarity Review has been passed and rescheduled at least twice, first in November, 2012, then January, 2013. It is currently set to be released on March 8th, 2013. There is concern about this date given that formal objections are currently due March 13th.<ref>[https://twitter.com/jintlaw/status/289827051924496384 Status, Jintlaw Twitter.com]Published and Retrieved 11 Jan 2013</ref><ref>[https://twitter.com/gTLDNews/status/289833996639158273 Status, gTLDNews, Twitter.com]Published and Retrieved 11 Jan 2013</ref>
[[ICANN]]'s deadline for the results of the String Similarity Review has been passed and rescheduled at least three times, first in July 2012, then November, 2012, and then January, 2013. It is currently set to be released on March 8th, 2013. There is concern about this date given that formal objections are currently due March 13th.<ref>[https://twitter.com/jintlaw/status/289827051924496384 Status, Jintlaw Twitter.com]Published and Retrieved 11 Jan 2013</ref><ref>[https://twitter.com/gTLDNews/status/289833996639158273 Status, gTLDNews, Twitter.com]Published and Retrieved 11 Jan 2013</ref>
==Sword Algorithm==
==Sword Algorithm==
The '''Sword Algorithm''' is the string similarity assessment tool adopted by ICANN to automatically determine if a new gTLD being applied for is not confusingly similar to a reserved name or existing TLD. SWORD, an international IT company expert in verbal search algorithms, developed the tool to automate the process of examining the similarities of proposed and existing TLD strings. The tool is intended to provide an open, objective and predictable mechanism to determine the level of visual likeness between gTLDs.<ref>[https://icann.sword-group.com/algorithm/ String Similarity Assessment Tool]</ref>
The '''Sword Algorithm''' is the string similarity assessment tool adopted by ICANN to automatically determine if a new gTLD being applied for is not confusingly similar to a reserved name or existing TLD. SWORD, an international IT company expert in verbal search algorithms, developed the tool to automate the process of examining the similarities of proposed and existing TLD strings. The tool is intended to provide an open, objective and predictable mechanism to determine the level of visual likeness between gTLDs.<ref>[https://icann.sword-group.com/algorithm/ String Similarity Assessment Tool]</ref>
'''You may utilize the Sword Algorithm [https://icann.sword-group.com/algorithm/ here].'''
'''You may utilize the Sword Algorithm [https://icann.sword-group.com/algorithm/ here].'''
==Criticism==
Criticism of the String SImilarity Panel includes that it has no review or appeal process; it is not clear whether the intended registration policies will affect delegation, so closed TLDs may be deeemd similar when there will likely be little room for practical overlap and so confusion; it does not build upon the flawed process first undertaken in reviewing [[IDN]] [[ccTLD]]s; and its total lack of transparency and community input.<ref>[http://www.circleid.com/posts/20130121_a_serious_bug_in_the_similarity_check/ A Serious Bug in The Similarity Check, CircleID.com]<ref> Published Jan 21, Retrieved Jan 22</ref>
==Related Panels==
==Related Panels==
Other Panels and evaluations involved in the Initial Evaluation Process:<ref>[http://www.gtld.com/news/2012/closer-look-new-gtld-evaluation-program Closer Look New gTLD Evaluation Program, gTLD.com]</ref>
Other Panels and evaluations involved in the Initial Evaluation Process:<ref>[http://www.gtld.com/news/2012/closer-look-new-gtld-evaluation-program Closer Look New gTLD Evaluation Program, gTLD.com]</ref>