Service: Language
This property is: Optional.
Definition
The language that a transactional service presents to its users.
Examples
| Value | Explanation |
|---|---|
| en | The LinkFinderPlus at MIMAS service presents English to its users. |
| en-gb | The transactional service presents English used in the United Kingdom to its users. |
| chr | The service presents Cherokee, Cheyenne and Creek. |
| chy | |
| mus |
Guidelines
This property is intended primarily for transactional services, but may be entered for collection-based services. The depth of analysis is at your discretion, but you should attempt to capture all languages offered by the service.
The terms used to encode languages are defined by RFC 3066. They may be:
- a two-letter language code taken from ISO 639 part 1
or
a three-letter language code taken from ISO 639 part 2- 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
- optionally
followed by a two-letter country code taken from ISO 3166- If a country code is included then separate the country code from the language code with a hyphen ("-"), for instance en-gb
Some language values, such as the value en, for English, may be qualified by country. This is optional and should only be used for countries where English is the native language. This is mainly for use with English used in the United Kingdom (en-gb) and American English (en-us). Another example is fr-ca for French used in Canada . Do not qualify en by country of origin where English is not the principal language. For instance, do not use en-es for Spanish English. If in doubt use en only.
Terms should be entered in lower case.
References
- [ISO 639] http://www.loc.gov/standards/iso639-2/php/English_list.php
- [ISO 3166] http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Occurrence
Repeatable: there may be multiple values for this property. Enter each value into its own text box.