27,652
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − + − + − '''.SUGAR EXAMPLE''' − − ''The registry operator of .SUGAR, a Community gTLD launched in support of the American Sugar Producers Association (ASPA), requests a Community gTLD Change to modify their registration policies to allow registration for all entities that are members of associations belonging to the newly established Global Sugar Association (GSA), having most of the world’s national sugar producer associations as members, including ASPA. Supporting documentation for this change is provided from both ASPA and GSA. − − ''The public comments end with a lot of spam, plus one contribution by the European Sugar Beet Growers Association, ESBGA, claiming that the change would allow European sugar producers to register under this gTLD while not allowing ESBGA members to register, increasing the exposure and market power of the sugar producers to the detriment of the sugar beet growers, already being under pressure by the producers.'' − '' − − −
no edit summary
A '''Community TLD''' is a regulated type of [[gTLD|generic top level domain name]] (gTLD) made possible through [[ICANN]]'s [[New gTLD Program]]; it is intended for community groups that are interested in operating their own TLD [[registry]].
A '''Community TLD''' is a regulated type of [[gTLD|generic top level domain name]] (gTLD) made possible through [[ICANN]]'s [[New gTLD Program]]; it is intended for community groups that are interested in operating their own TLD [[registry]].
Community TLDs must represent a clearly delineated group or groups of people or entities. Examples could include cultural, religious, social or industry associations. The existence of the group must be clearly established. An example of a community TLD used by ICANN, is the .SUGAR TLD. This example was used by ICANN Staff to brief the Board on a proposed registry change request. <ref>[http://archive.icann.org/en/topics/new-gtlds/explantory-memo-community-change-request-21feb11-en.pdf]</ref>
Community TLDs must represent a clearly delineated group or groups of people or entities. Examples could include cultural, religious, social or industry associations. The existence of the group must be clearly established.
Community groups are given precedence for TLDs in contention; that is, if there are multiple applicants for a given string, and one of the applicants applies and proves community status, the community group is automatially given precedence to the TLD. Community status is proven through a process known as '''Community Priority Evaluation'''.
Community groups are given precedence for TLDs in contention; that is, if there are multiple applicants for a given string, and one of the applicants applies and proves community status, the community group is automatically given precedence to the TLD. Community status is proven through a process known as '''Community Priority Evaluation'''.
The scoring process is conceived to identify qualified community-based applications, while preventing both “false positives” (awarding undue priority to an application that refers to a “community” construed merely to get a sought-after generic word as a gTLD string) and “false negatives” (not awarding priority to a qualified community application).
The scoring process is conceived to identify qualified community-based applications, while preventing both “false positives” (awarding undue priority to an application that refers to a “community” construed merely to get a sought-after generic word as a gTLD string) and “false negatives” (not awarding priority to a qualified community application).