Artificial languages
art is a collective code with no ISO 639-1 equivalent; it is not used for individual languages in ISO 639-3 and is carried over into ISO 639-5, the code list for language families and groups.
Collective codes are the less visible half of ISO 639-2. Besides individual languages, the list contains codes for groups: Bantu languages (bnt), Austronesian languages (map), Caucasian languages (cau). art is the group code for Artificial languages, the languages that someone designed on purpose instead of inheriting.
In the Library of Congress vocabulary the code resolves at http://id.loc.gov/vocabulary/iso639-2/art, with the French label artificielles, langues. The heading form, with the general term inverted, follows the convention used for all collective codes in the list.
What the group covers
Constructed languages come in three broad kinds, and art covers all of them:
- International auxiliary languages, designed to be easy to learn as a second language: Esperanto, Volapük, Ido, Interlingua.
- Fictional languages, built for novels, films, television and games: Klingon is the best known in library catalogs, Tolkien’s Quenya and Sindarin among the most studied.
- Engineered or philosophical languages, built to test ideas about logic or meaning: Lojban is the standard example.
A constructed language does not need many speakers to count. A grammar of a private language invented for a novel is still a constructed-language document.
Individual codes come first
The group code is a fallback. Several constructed languages have their own entries in ISO 639-2, and each of them should be used in preference to art:
| Language | ISO 639-2 | ISO 639-1 |
|---|---|---|
| Esperanto | epo | eo |
| Interlingua | ina | ia |
| Interlingue; Occidental | ile | ie |
| Ido | ido | io |
| Volapük | vol | vo |
| Klingon | tlh | none |
| Lojban | jbo | none |
ISO 639-3 covers further constructed languages that ISO 639-2 never coded individually. Where a 639-3 code exists and the metadata schema accepts it (BCP 47 tags do), the more specific code is the better value. Where the schema is restricted to the ISO 639-2 list, art is the correct choice for those languages.
Cataloging practice
MARC 21 records use art in field 008 when the main language of the work is a constructed language without its own code, and list it again in field 041 when a work mixes, say, English commentary with texts in an invented language. Subject access usually comes from a separate heading, since the language code alone tells a user nothing about which constructed language is meant. A free-text note naming the language closes that gap.
In Dublin Core, the example above uses two dcterms:language statements because the grammar sketch is written in English about an invented language. Both values belong in the record: one describes the language of the text, the other the language the text documents.
The keyword confusion
“art” is also an everyday English word, which makes the code easy to misread in data. In a flat export where language values sit next to subject keywords, a reader can take art for a subject term, and a full-text index will happily match it against records about painting or sculpture. Storing the URI from id.loc.gov instead of the bare three letters removes that ambiguity in linked-data contexts. In BCP 47 tags the string is unambiguous by position, so art in a lang attribute only ever means the language group.
Example in RDF
<rdf:Description rdf:about="https://example.org/texts/conlang-grammar-sketch.pdf"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/">
<dcterms:title>Grammar sketch of an invented language for a fantasy novel</dcterms:title>
<dcterms:language rdf:resource="http://id.loc.gov/vocabulary/iso639-2/art"/>
<dcterms:language rdf:resource="http://id.loc.gov/vocabulary/iso639-2/eng"/>
</rdf:Description>
Questions about art
What does the language code art stand for?
art is the ISO 639-2 code for "Artificial languages", the collective group of constructed languages: auxiliary languages designed for international communication, languages invented for fiction, games or films, and experimental languages built for logic or philosophy.
Should Esperanto be coded as art?
No. Esperanto has its own ISO 639-2 code, epo (ISO 639-1 eo). art is meant for constructed languages without an individual code. Coding an Esperanto text as art loses information that the standard already provides.
Which constructed languages have their own codes?
ISO 639-2 includes individual codes for Esperanto (epo), Interlingua (ina), Interlingue or Occidental (ile), Ido (ido), Volapük (vol), Klingon (tlh) and Lojban (jbo). ISO 639-3 adds more, so it is worth checking that list before falling back to art.
Is art valid in BCP 47 language tags?
art is registered as a collection subtag in the IANA language subtag registry, so it is well formed in a BCP 47 tag. For web content in a specific constructed language, an individual subtag gives software far more to work with than the collective one.
Is art the same as a local-use code?
No. art is a published, shared code with a fixed meaning. Local-use codes in the range qaa–qtz have no shared meaning at all. A constructed language with no individual code should take art, not a local code, if the record leaves the institution.