[Gnso-newgtld-wg] String Similarity Recommendation

Tue Jan 5 20:45:59 UTC 2021

Jeff and Cheryl

I'm in the process of reviewing the Final Report and I have a question regarding Recommendation 24.3 and the dot points that follow the recommendation.  The last dot point appears inconsistent with the Recommendation and also inconsistent with my recollection of our discussions on this topic that concluded the meaning of the string could not be a determining factor. Perhaps I'm missing something so would appreciate clarification.

Recommendation 24.3: The Working Group recommends updating the standards of both (a) confusing similarity to an existing top-level domain or a Reserved Name, and (b) similarity for purposes of determining string contention, to address singular and plural versions of the same word, noting that this was an area where there was insufficient clarity in the 2012 round. Specifically, the Working Group recommends prohibiting plurals and singulars of the same word within the same language/script in order to reduce the risk of consumer confusion. For example, the TLDs .EXAMPLE156 and .EXAMPLES may not both be delegated because they are considered confusingly similar. This expands the scope of the String Similarity Review to encompass singulars/plurals of TLDs on a per-language/script basis.

  *   An application for a single/plural variation of an existing TLD or Reserved Name will not be permitted if the intended use of the applied-for string is the single/plural version of the existing TLD or Reserved Name. For example, if there is an existing TLD .SPRINGS that is used in connection with elastic objects and a new application for .SPRING that is also intended to be used in connection with elastic objects, .SPRING will not be permitted.
  *   If there is an application for the singular version of a word and an application for a plural version of the same word in the same language/script during the same application window, these applications will be placed in a contention set, because they are confusingly similar.
  *   Applications will not automatically be placed in the same contention set because they appear visually to be a single and plural of one another but have different intended uses. For example, .SPRING and .SPRINGS could both be allowed if one refers to the season and the other refers to elastic objects, because they are not singular and plural versions of the same word. However, if both are intended to be used in connection with the elastic object, then they will be placed into the same contention set. Similarly, if an existing TLD .SPRING is used in connection with the season and a new application for .SPRINGS is intended to be used in connection with elastic objects, the new application will not be automatically disqualified.

Thanks

Donna
From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces at icann.org> On Behalf Of Jeff Neuman
Sent: Thursday, December 3, 2020 9:45 AM
To: gnso-newgtld-wg at icann.org
Subject: [Gnso-newgtld-wg] Fourth Topical Questions: String Similarity Outstanding Questions

Notice: This email is from an external sender.

All,

This is the Fourth topical E-mail on outstanding questions being "put to the list."  The first was on Predictability, second on Applicant Support, third was the Guidebook, and this covers string similarity (Topic 24).

Remember:  We are down to the wire on this, so unless you have a VERY strong objection to these, we will put these into the document.  If you do have a big issue with the responses to these (all of which were previously discussed and in emails over the past 1.5 months), please let us know ASAP.  Only comments that provide the rationale for the objection with proposed replacement text to address the specific outstanding questions will now be considered.

Lets not let the perfect be the enemy of the good.

  1.  Intended Use Comments

     *   Comments:  Some commenters have expressed concerns about Recommendation 24.3 in that it calls for an evaluation of the "intended use" of an applied-for string to determine whether terms that appear to be the singular/plural of each other will be allowed to co-exist (our paraphrasing).

     *   WG Recommendations

                                                               i.      Recommendation 24.3.  ...Specifically, the Working Group recommends prohibiting plurals and singulars of the same word within the same language/script in order to reduce the risk of consumer confusion. For example, the TLDs .EXAMPLE74 and .EXAMPLES may not both be delegated because they are considered confusingly similar. This expands the scope of the String Similarity Review to encompass singulars/plurals of TLDs on a per-language/script basis.

           *   An application for a single/plural variation of an existing TLD or Reserved Name will not be permitted if the intended use of the applied-for string is the single/plural version of the existing TLD or Reserved Name. For example, if there is an existing TLD .SPRINGS that is used in connection with elastic objects and a new application for .SPRING that is also intended to be used in connection with elastic objects, .SPRING will not be permitted...

     *   Path Forward

                                                               i.      First, put aside for the moment the issues expressed by the Board on "content" and assume for now that we can make these recommendations.  An e-mail later will address the content / bylaws issue.

                                                             ii.      Second, most of the Working Group had little/no issue when the Plural / Singular evaluation was between two brands or a brand and a generic application.

           *   Examples:  Apple (brand) / apples (generic); Caterpillar (Brand) / caterpillars (generic); Gap (brand) / gaps (generic); Whirlpool (Brand) / whirlpools (generic).

                                                           iii.      Remember also that we have added sections to the Report to now require that applicants describe their proposed use of a TLD in their application and that the evaluators can ask Clarifying questions if they are unable to ascertain the intended use from the Applicant Responses (IG 24.4).  Finally, If both versions (singular/plural) are allowed, then both applicants (in the case where they are both applied for strings) or the 1 successful applicant (in the case where the application is for a singular/plural of an existing TLD) will have to agree to be bound by its commitment to use the TLD only in the manner in which it proposed in its application.

           *   Again, please ignore the potential Bylaws issue FOR NOW.  We promise that we will address this later.

                                                           iv.      Here are the options we have

           *   Leave the language As-Is;
           *   Ban the co-existence of Singulars and Plurals except for where either one or both of the strings are a Specification 13 (Brand TLD); or
           *   Ban the co-existence of Singulars and Plurals regardless of intended use completely.

                                                             v.      Absent agreement on either 2 or 3, we will stick with the language that we have (Option 1).  A lot of work has gone into this already so we need a good amount of support from within the Working Group to change.

Please have your comments (If any) by no later than 23:59:59 UTC on Monday, December 7, 2020.

Sincerely,

Jeff & Cheryl
SubPro Co-Chairs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20210105/332123d1/attachment-0001.html>