| Name of Term | language | |
| Term URI | http://purl.org/dc/elements/1.1/language | |
| Label | Language | |
| Defined By | http://dublincore.org/documents/dcmi-terms/ | |
| Source Definition | A language of the intellectual content of the resource. | |
| DC-Gov Definition | ||
| Source Comments | Recommended best practice is to use RFC 3066 [RFC3066], which, in conjunction with ISO 639 [ISO639], defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian, and "en-GB" for English used in the United Kingdom | |
| DC-Gov Comments | Language code may be used as a value for the Language qualifier to any DCMES element. Recommend codes rather than text, taken from ISO 639-2 bibliographic codes. Mandatory if applicable means if there is any spoken or written text, supply. | |
| Type of term | element | |
| Refines | ||
| Refined By | ||
| Has Encoding Scheme | ISO639-2 - DCMI approved encoding scheme. Use of the ISO 639-2 bibliographic code is preferred. A mapping is available at http://lcweb.loc.gov/standards/iso639-2/englangn.html. RFC 1766 - This scheme has been replaced by RFC 3066, which allows for a code from ISO 639-2 when there is no corresponding ISO 639-1 code. RFC 3066 is being registered as a DCMI approved scheme. RFC 3066 - Internet RFC 3066 'Tags for the Identification of Languages' specifies a primary subtag which is a two-letter code taken from ISO 639 part 1 or a three-letter code taken from ISO 639 part 2, followed optionally by a two-letter country code taken from ISO 3166. When a language in ISO 639 has both a two-letter and three-letter code, use the two-letter code; when it has only a three-letter code, use the three-letter code. This RFC replaces RFC 1766. | |
| Obligation | MA (ISO 639-2), O (RFC 1766, RFC 3066) | |
| Occurence | ||