New gTLD Program: Next Round: Difference between revisions

Line 35:

=== String Similarity ===

On string similarity~~, the Working Group reaffirms the 2007 policy that~~ applied-for strings ~~must not be confusingly similar to existing TLDs or reserved names~~. ~~One of~~ the ~~most visible updates~~ for the Next Round concerns plurals and singulars: SubPro recommends prohibiting delegation of singular and plural versions of the same word in the same language or script (for example, “.example” and “.examples”) in order to reduce the risk of user confusion.

The 2026 Round includes string similarity review to assess potential user confusion with existing TLDs and other applied-for strings. In addition, the AGB implements a separate process for 'Singular/Plural Notifications.

~~In limited cases where two~~ applied-for ~~strings would normally be treated as~~ a ~~singular~~/~~plural pair but the applicants can demonstrate genuinely different intended meanings~~, ~~both applications may proceed only if each applicant accepts a mandatory Public Interest Commitment (PIC)~~ in ~~its Registry Agreement. That commitment must state~~ the ~~intended use~~ of the ~~TLD and require registrants to use second-level domains~~ in ~~line with that stated purpose~~ (for example, ~~distinguishing clearly between a~~ string ~~used for~~ a ~~season and one used for~~ a ~~manufactured object~~).<ref name="~~subpro-final~~" />

Under this mechanism, third parties may submit a notification within 30 days after the "String Confirmation Day" asserting that an applied-for string is the singular or plural version of another relevant string. If a Singular/Plural Notification is confirmed, outcomes in the AGB include:

* placement of the strings into a singular/plural contention set; or

* in specified cases (for example, where the applied-for string is the singular/plural version of a delegated TLD or a blocked name), the application may not proceed.<ref name="agb" />

=== Applicant Freedom and Safeguards ===

@@ Line 35: / Line 35: @@
 === String Similarity ===
-On string similarity, the Working Group reaffirms the 2007 policy that applied-for strings must not be confusingly similar to existing TLDs or reserved names. One of the most visible updates for the Next Round concerns plurals and singulars: SubPro recommends prohibiting delegation of singular and plural versions of the same word in the same language or script (for example, “.example” and “.examples”) in order to reduce the risk of user confusion.
+The 2026 Round includes string similarity review to assess potential user confusion with existing TLDs and other applied-for strings. In addition, the AGB implements a separate process for 'Singular/Plural Notifications.
-In limited cases where two applied-for strings would normally be treated as a singular/plural pair but the applicants can demonstrate genuinely different intended meanings, both applications may proceed only if each applicant accepts a mandatory Public Interest Commitment (PIC) in its Registry Agreement. That commitment must state the intended use of the TLD and require registrants to use second-level domains in line with that stated purpose (for example, distinguishing clearly between a string used for a season and one used for a manufactured object).<ref name="subpro-final" />
+Under this mechanism, third parties may submit a notification within 30 days after the "String Confirmation Day" asserting that an applied-for string is the singular or plural version of another relevant string. If a Singular/Plural Notification is confirmed, outcomes in the AGB include:
+* placement of the strings into a singular/plural contention set; or
+* in specified cases (for example, where the applied-for string is the singular/plural version of a delegated TLD or a blocked name), the application may not proceed.<ref name="agb" />
 === Applicant Freedom and Safeguards ===