Reserved for local use
qaa-qtz is a range, not a single code: every three-letter code from qaa to qtz is left unassigned by ISO 639-2 so that institutions can define their own, and the same range is reserved for private use in ISO 639-3 and BCP 47.
Most entries in ISO 639-2 identify one language or one group of languages. The entry qaa-qtz identifies nothing in particular, on purpose. It marks a block of three-letter codes, from qaa through qtz, that the standard promises never to assign. Any library, archive or software project may give those codes a local meaning.
That makes qtz, the last code in the block, one of the more frequently looked-up strings in the list: it turns up in exported records, in subtitle tracks and in data dumps, and the person who finds it usually wants to know which language it is. The honest answer is that the code alone cannot tell.
Why a reserved block exists
ISO 639-2 has about 480 entries. Real collections need distinctions the list does not make: a regional variety cataloged separately, a historical orthography, a constructed language used in one research project, or an internal flag such as “language to be reviewed”. Without a sanctioned range, institutions would invent codes in the free space of the alphabet, and some of those inventions would later collide with codes the registration authority assigns.
The block is 520 codes long (q, followed by a–t, followed by a–z). ISO 639-3 keeps the same range for local use, and the IANA language subtag registry lists qaa..qtz as private-use primary subtags for BCP 47 tags (RFC 5646). Subtitle and audio track metadata in media containers sometimes uses these codes for commentary or descriptive tracks, which is how many people first meet them.
Using a local code responsibly
A local code is a private agreement. The agreement has to be written down somewhere that outlives the person who made it:
- Record each code, its meaning and the date it was introduced in the repository’s metadata profile or cataloging manual.
- Add a human-readable note in the record itself (a
dcterms:descriptionor MARC 546 note) so the value can be read without the manual. - Never reuse a retired local code for a new meaning.
- Before export or harvesting, map local codes to a standard value where one exists, or to mis or und where none does.
In MARC 21 practice the MARC Code List for Languages has its own conventions, and local codes in field 008 are generally discouraged for records contributed to shared catalogs such as OCLC WorldCat. They are better kept to local fields or local systems.
Checking for a standard code first
A surprising share of local codes duplicate something that already exists. Before reaching for qaa–qtz, it is worth checking the full ISO 639-2 table in the language code vocabulary, then ISO 639-3, which covers several thousand individual languages that 639-2 does not, and finally the special codes. If the resource contains no language, zxx is the answer; if the language is known but uncoded, mis is; if it simply has not been identified, und is.
One practical consequence: validators that check language values against the published code list must treat the whole qaa–qtz range as valid, or they will reject records that are formally correct. A regular expression such as ^q[a-t][a-z]$ covers it exactly.
Example in RDF
@prefix dcterms: <http://purl.org/dc/terms/> .
# Local convention documented in the repository's profile:
# qtz = in-house transcription orthography for field recordings
<https://example.org/fieldnotes/box12/item04.txt>
dcterms:title "Field notebook, transcription of session 4" ;
dcterms:language "qtz"^^dcterms:ISO639-2 ;
dcterms:description "Local code qtz: see repository language profile, section 3." .
Questions about qaa-qtz
What does qtz mean as a language code?
qtz has no fixed meaning. It is the last code in the ISO 639-2 range qaa–qtz, which the standard leaves unassigned so that each organization can define its own codes. A qtz in one catalog and a qtz in another can refer to completely different things.
How many codes are in the qaa–qtz range?
The first letter is always q, the second runs from a to t and the third from a to z. That gives 20 × 26 = 520 possible codes, more than any single institution normally needs for local distinctions.
Can qaa–qtz codes be used in BCP 47 language tags?
Yes. RFC 5646 reserves the same range as private-use primary language subtags, so a tag such as qaa or qtz-Latn is well formed. The tag carries no shared meaning, so it should only be exchanged between parties who have agreed on a definition.
When should a local-use code be avoided?
Whenever a standard code fits. Check ISO 639-2 first, then ISO 639-3 for individual languages it lacks, and the special codes mis, mul, und and zxx. A local code in a record that is shared, harvested or archived long term turns into an unreadable value once its local definition is lost.
Does the Library of Congress assign codes in this range?
No. The registration authority deliberately keeps qaa–qtz empty. The id.loc.gov entry describes the range as a whole and states that it is reserved for local use; it lists no individual codes inside it.