Try to imagine the same page when Montenegro (after Croatia / Croatian HR) will join the EU!
Dear Havard,Dear Christian,In my personal opinion, the situation is not so evident.I will give some examples of code elements that have a quasi-reserved status.1/ Concerning ISO 639-1 alpha-2 code elements:(i) "ji" (Yiddish) that was published in ISO 639 (1988), was replaced by "yi" on 11-03-1989;(ii) in" (Indonesian) that was published in ISO 639 (1988), was replaced by "in" on 11-03-1989;(iii) "iw" (Hebrew/ Iwrith) that was published in ISO 639 (1988), was replaced by "he" on 11-03-1989;(iv) sh" (Serbo-Croatian that was published in ISO 639 (1988) and was deprecated on 18-02-2000. The same code element was further reinstalled with the publication of ISO 639-1 (2002) and one more time deprecated in 2005;(v) "jw" (Javanese) was published in table 1 of ISO 639 (1988), but was in fact a double with "jv" that was given in tables 2 and 3 of ISO 639 (1988), so that "jw" and has been deleted on 13-08-2001;(vi) "mo" (Moldovan) that had been created in ISO 639-1 on 26-06-2008 was rapidly (only after 5 months) deprecated on 03-11-2008 and replaced by "ro"; the corresponding change notice states that this identifier will not be assigned to different items, and recordings using these identifiers will not be invalid, so that the ISO 3166 uses "mo" to represent the name of language "Moldovan" following the fact that article 13 of the Moldovan Constitution writes " (1) The national language of the Republic of Moldova is Moldovan, and its writing is based on the Latin alphabet".2/ Concerning ISO 639-2 alpha-3 code elements(i) "jaw"(Javanese) that was published as ISO 639-2/T code element, with "jav" as corresponding ISO 639-2/B code element, in ISO 639-2(1998) was replaced by "jav"on 13-08-2001;(ii) esp" (Spanish) was not initially published as an official code element in ISO 639-2 (1998); in fact spa" was published as initial ISO 639-2:B and T code element. But the following note was written in the three published tables "After a period of five years from the publication of this standard, "esp" may be used as the ISO 639-2/T (terminology) code for Spanish". So that, because ISO 3166 uses the T version of ISO 639-2, "esp" was published in ISO 3166-1 (2006) and in ISO 3166-2 (2007). It seems that the JAC decided in 2004 not to replace "spa" by "esp" as the ISO 639-2/T code element for Spanish. I never saw this decision, that is not to be found in the ISO 639-2 change notice list. Anyway, as no revision of the text of ISO 639-2 has been made from 1998 on to act this, it remains possible to challenge the legitimity of such a JAC decision(iii) "scc" (Serbian) that was published as ISO 639-2/B code element, with "srp" as corresponding ISO 639-2/T code element in ISO 639-2 (1998)was replaced by "srp" on 28-08-2008;(iv)"scr" (Croation) that was published as ISO 639-2/B code element , with "hrv" as corresponding ISO 639-2/T code element in ISO 639-2 (1998 ) was replaced by "hrv" on 28-06-2008(v) "mol" (Moldovan) that had been created in ISO 639-2 on 26-06-2008 was rapidly (only after 5 months) deprecated on 03-11-2008 and replaced by "ron"(B) and "rum" (T); the corresponding change notice states that this identifier will not be assigned to different items, and recordings using these identifiers will not be invalid, so that ISO 3166 uses "mol" to represent the name of language "Moldovan", following the Constitution of the Republic of Moldova.As everybody seems to be OK that no ISO 639 code element having represented a name of language in the past from the beginning should be reused to represent another name of language, it seems that my examples concerning ISO 639-1 and ISO 639-2 must be considered as reserved code elements. Moreover, in the case of "mo" and "mol" we are practically vey near of the case of immediate rejection of a new proposed code element. Let me also add that the normative clause A.3.4 "Reservation of codes" of ISO 639-2 (for example) is still explicitely in force today and that this cannot be changed by a vote of the JAC; only a revision of the text of ISO 639-2 could achieive this.3/ Moreover, concening ISO 639-3 alpha-3 code elements, we have the ugly case of "eur"."eur" was on the initial list of the ISO 639-3/RA published after the adoption of the ISO 639-3 standard (2007).The definition of the considered language name was "Europanto: this is the name of the language commonly used by the bureaucrats of the European Communities in their headquarter in Brüssels".I rapidly asked the ISO 639/RA to suppress from their list this code element, considering that the alleged "name of language" did not correspond to anything existing and was using a very useful alpha-3 code element.. It was answered that "eur" was certainly interesting, at least as a good joke, and that no reason for the requested suppression was found. So, I made a very official request for the creation of the new alpha-3 ISO 639-3 code element "neg" to represent the name of language defined as "Neglish: this is the name of the language commonly used by the bureaucrats of NATO in their headquarter near Brüssels". ISO 639-3 refused to register this very official request, but miraculously decided soon after that to suppress the code element "eur".I do not find it intelligent to block the use of such an useful and meaningful code element like "eur". So that I propose, as an exceptional and elegant reestablishment for this case to slightly change the interpretation of "eur" from an indistinct and not-existing combination between all official languages of the European Community to the very list of the (currently) 24 official languages of the European Community. We would then create the first example of an alpha-3 ISO 639-5 code element to represent a language group (defined by clause 3.6 of ISO 639-5 as "two or more individual languages that, for some purpose, may suitably be treated as a unit") by definig "eur" as the code element representing the name of the group of languages "Official languages of the European Union".Bien amicalement.Gérard LangLe 11 sept. 2013 à 05:38, Håvard Hjulstad a écrit