Hi Jorge,

Thanks for laying out these options in a clear format. Perhaps it indeed does make sense to take a step back and focus not on the text suggested earlier in the week, but on the alternatives raised:

(1) maintain “all languages”

(2) official languages and official UN languages

(3) some intermediate solution covering all languages commonly used in a given country to identify its name… (there could be several options: “common languages”; “commonly used languages”; “relevant national, regional and community languages”, etc.)

All are encouraged to provide feedback.

Kind regards,

Emily

From: "Jorge.Cancio@bakom.admin.ch" <Jorge.Cancio@bakom.admin.ch>
Date: Thursday, 9 August 2018 at 16:30
To: Emily Barabas <emily.barabas@icann.org>, "gnso-newgtld-wg-wt5@icann.org" <gnso-newgtld-wg-wt5@icann.org>
Subject: [Ext] AW: Additional Input Requested - "in any language"

Dear Emily

As a threshold consideration: as there is no clear “room consensus” on this question I feel that there should be no preference given to any of the, as I see, three main options at hand: (1) maintain “all languages”; (2) official languages and official UN languages; (3) some intermediate solution covering all languages commonly used in a given country to identify its name… (there could be several options: “common languages”; “commonly used languages”; “relevant national, regional and community languages”, etc.)

Therefore either we have the AGB (amended) language for the three main options or we have it for none. We cannot just have the amended language as “suggested recommendation” reflecting only option (2) above.

Thanks for considering and best regards

Jorge

Von: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> Im Auftrag von Emily Barabas
Gesendet: Donnerstag, 9. August 2018 15:44
An: gnso-newgtld-wg-wt5@icann.org
Betreff: [Gnso-newgtld-wg-wt5] Additional Input Requested - "in any language"

Dear all,

On our call yesterday there was some robust discussion about draft recommendations 3, 4, and 6, which suggest changing “in any language” to “official languages of the country and the official UN languages” for several AGB categories. Please reply to this thread to provide additional input on the suggested edits or alternate options listed at the bottom of this message. For reference, here is an excerpt of AGB text with redline reflecting suggested recommendations:

2.2.1.4.1 Treatment of Country or Territory Names

Applications for strings that are country or territory names will not be approved, as they are not available under the New gTLD Program in this application round. A string shall be considered to be a country or territory name if: 

• it is a long-form name listed in the ISO 3166-1 standard, or a translation of the long-form name in any language official languages of the country and the official UN languages.
• it is a short-form name listed in the ISO 3166-1 standard, or a translation of the short-form name in any language official languages of the country and the official UN languages.
• it is a separable component of a country name designated on the “Separable Country Names List,” or is a translation of a name appearing on the list, in any language official languages of the country and the official UN languages. See the Annex at the end of this module.

Below you will find an excerpt from the Working Document (https://docs.google.com/document/d/1BRzHr2FxSTYHX1I8F3FHSt6Bo1cvJsKyWX8WZXRUXAo/edit [docs.google.com]) highlighting some of the ideas and arguments shared on the mailing list and on calls:

Some Work Track members stated that the text “in any language” results in a very large number of reserved strings and does not provide a clear and objective list that can be used as reference. From this perspective, the provision is not predictable or transparent. One Work Track member also noted that some languages are spoken by very few people, therefore reserving representations in all languages may not be appropriate. From another perspective, “in any language” should remain in place unless there is a factual basis for limiting the languages covered in this provision. Many languages may be spoken by and relevant to communities within a given country, and the list should therefore not be limited. Work Track members suggested the following possible options as alternatives to “in any language”:

• Limit the list to the official UN languages.
  • One Work Track member stated that if the UN languages are included, the text should state “including but not limited to official UN languages.”
  • Another WT member stated that there are no “official UN languages.” There are “UN working languages.”
  • One Work Track member suggested that Portuguese should be added to this list as it is an ICANN language.
• Limit the list to Create a list of languages using the official languages of each country and official UN languages.
  • Some Work Track members stated that it might be difficult to identify the official languages of each country. One WT member asked in the WT would take on the task of creating such a list.
    • One Work Track member suggested using as a starting point Working Paper 54 [unstats.un.org] of the UN Group of Experts on Geographical Names (UNGEGN).
  • Another WT member stated that there are no “official UN languages.” There are “UN working languages.”
  • From one perspective, the list should not be limited in this way. Official UN languages are largely irrelevant in many countries. Also from this perspective, the concept of official languages only appears in certain countries. In this view, the administrations in many countries use languages that are not official. People of the country also use languages that may not be official, and these languages are important to specific communities.
  • Alternate to “official languages” suggested: “official and relevant languages.”
    • Example used in relation to “relevant languages”: “We have more than 25% of foreign-born people living in Switzerland. They refer to Switzerland in their languages and scripts. These are relevant languages/scripts that should be covered.”
  • Alternate to “official languages” suggested: “official and commonly spoken languages.”
  • One Work Track member suggested that Portuguese should be added to this list as it is an ICANN language.
• Develop a list using the Expanded Graded Intergenerational Disruption Scale and categorization based on Official Recognition [ethnologue.com].
• Create an exhaustive repository of all country names in all languages.
• Change “in any language” to “in any script.”

Kind regards,

Emily