ISO 639-3
ISO 639-3:2007, Codes for the representation of names of languages – Part 3: Alpha-3 code for comprehensive coverage of languages, is an international standard for language codes in the ISO 639 series. It defines three-letter codes for identifying languages. The standard was published by International Organization for Standardization (ISO) on 1 February 2007.[1]
ISO 639-3 extends the ISO 639-2 alpha-3 codes with an aim to cover all known natural languages. The extended language coverage was based primarily on the language codes used in the Ethnologue (volumes 10–14) published by SIL International, which is now the registration authority for ISO 639-3.[2] It provides an enumeration of languages as complete as possible, including living and extinct, ancient and constructed, major and minor, written and unwritten.[1] However, it does not include reconstructed languages such as Proto-Indo-European.[3]
ISO 639-3 is intended for use as metadata codes in a wide range of applications. It is widely used in computer and information systems, such as the Internet, in which many languages need to be supported. In archives and other information storage, it is used in cataloging systems, indicating what language a resource is in or about. The codes are also frequently used in the linguistic literature and elsewhere to compensate for the fact that language names may be obscure or ambiguous.
Code space[edit]
Since the code is three-letter alphabetic, one upper bound for the number of languages that can be represented is 26 × 26 × 26 = 17,576. Since ISO 639-2 defines special codes (4), a reserved range (520) and B-only codes (22), 546 codes cannot be used in part 3. Therefore, a stricter upper bound is 17,576 − 546 = 17,030.
The upper bound gets even stricter if one subtracts the language collections defined in 639-2 and the ones yet to be defined in ISO 639-5.
There are 58 languages in ISO 639-2 which are considered, for the purposes of the standard, to be "macrolanguages" in ISO 639-3.[10]
Some of these macrolanguages had no individual language as defined by ISO 639-3 in the code set of ISO 639-2, e.g. 'ara' (Generic Arabic). Others like 'nor' (Norwegian) had their two individual parts ('nno' (Nynorsk), 'nob' (Bokmål)) already in ISO 639-2.
That means some languages (e.g. 'arb', Standard Arabic) that were considered by ISO 639-2 to be dialects of one language ('ara') are now in ISO 639-3 in certain contexts considered to be individual languages themselves.
This is an attempt to deal with varieties that may be linguistically distinct from each other, but are treated by their speakers as two forms of the same language, e.g. in cases of diglossia.
For example:
A complete list is available on the ISO 639-3 registrar's website.[11]
Four codes are set aside in ISO 639-2 and ISO 639-3 for cases where none of the specific codes are appropriate. These are intended primarily for applications like databases where an ISO code is required regardless of whether one exists.
In addition, 520 codes in the range qaa
–qtz
are 'reserved for local use'. For example, Rebecca Bettencourt assigns a code to constructed languages, and new assignments are made upon request.[14] The Linguist List uses them for extinct languages. Linguist List has assigned one of them a generic value: qnp
, unnamed proto-language. This is used for proposed intermediate nodes in a family tree that have no name.
The code table for ISO 639-3 is open to changes. In order to protect stability of existing usage, the changes permitted are limited to:[15]
The code assigned to a language is not changed unless there is also a change in denotation.[16]
Changes are made on an annual cycle. Every request is given a minimum period of three months for public review.
The ISO 639-3 Web site has pages that describe "scopes of denotation"[17] (languoid types) and types of languages,[18] which explain what concepts are in scope for encoding and certain criteria that need to be met. For example, constructed languages can be encoded, but only if they are designed for human communication and have a body of literature, preventing requests for idiosyncratic inventions.
The registration authority documents on its Web site instructions made in the text of the ISO 639-3 standard regarding how the code tables are to be maintained.[19] It also documents the processes used for receiving and processing change requests.[20]
A change request form is provided, and there is a second form for collecting information about proposed additions. Any party can submit change requests. When submitted, requests are initially reviewed by the registration authority for completeness.
When a fully documented request is received, it is added to a published Change Request Index. Also, announcements are sent to the general LINGUIST discussion list at Linguist List and other lists the registration authority may consider relevant, inviting public review and input on the requested change. Any list owner or individual is able to request notifications of change requests for particular regions or language families. Comments that are received are published for other parties to review. Based on consensus in comments received, a change request may be withdrawn or promoted to "candidate status".
Three months prior to the end of an annual review cycle (typically in September), an announcement is sent to the LINGUIST discussion list and other lists regarding Candidate Status Change Requests. All requests remain open for review and comment through the end of the annual review cycle.
Decisions are announced at the end of the annual review cycle (typically in January). At that time, requests may be adopted in whole or in part, amended and carried forward into the next review cycle, or rejected. Rejections often include suggestions on how to modify proposals for resubmission. A public archive of every change request is maintained along with the decisions taken and the rationale for the decisions.[21]
Linguists Morey, Post and Friedman raise various criticisms of ISO 639, and in particular ISO 639-3:[16]
Martin Haspelmath agrees with four of these points, but not the point about language change.[22] He disagrees because any account of a language requires identifying it, and we can easily identify different stages of a language. He suggests that linguists may prefer to use a codification that is made at the languoid level since "it rarely matters to linguists whether what they are talking about is a language, a dialect or a close-knit family of languages." He also questions whether an ISO standard for language identification is appropriate since ISO is an industrial organization, while he views language documentation and nomenclature as a scientific endeavor. He cites the original need for standardized language identifiers as having been "the economic significance of translation and software localization", for which purposes the ISO 639-1 and 639-2 standards were established. But he raises doubts about industry need for the comprehensive coverage provided by ISO 639-3, including as it does "little-known languages of small communities that are never or hardly used in writing and that are often in danger of extinction".