skip navigationThe Library of Congress » Standards » MODS Official Web Site |
Top-level Element: <language>
GUIDELINES | EXAMPLES | MAPPINGS GUIDELINES FOR USE<language> is a container element; the actual language values are recorded in the subelement <languageTerm>. If the content of the resource is in more than one language, the objectPart attribute for <language> is used and the <language> element is repeated. <language> may also be expressed in conjunction with each element in a MODS encoding by means of the xml:lang and/or lang attributes to designate the language used in the metadata value; see the section on language in Attributes Used Throughout the MODS Schema for more information. The subelement <languageOfCataloging> under <recordInfo> is used to give the language of the metadata in the record as a whole. It designates the language of the metadata record, while this <language> element designates the language of the resource. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer Implementation Guidelines for Shareable MODS Records require at least one <language> element for all resources in which language is primary to understanding the resource. These resources include textual resources, as well as audio and video resources with spoken word components. Although <language> is usually not required for non-textual resources such as images, it could be used effectively for such resources when language is a primary component. Examples of the latter might include a photograph of a sign with text or a monument with an inscription. The <language> element is optional for resources in which language is important to understanding the resource, but not primary. For example, the caption of a photograph may in some instances be important to understanding the photograph, but not primary. Whether to include a <language> element based on the language's importance or primacy is left to the data provider's discretion. Repeat the <language> element as necessary. See the <language> entry in the DLF/Aquifer Summary of MODS Requirements and Recommendations table for further information on requirements of this element, its attributes, and subelements. Language is discussed as a general class of element in the "Language" section of the DLF/NSDL Best Practices for Shareable Metadata . Aggregator information: <language> is a primary descriptive element and is used for narrowing search results. Element DescriptionAttributesusage Definition
Primacy of the language vis-a-vis the resource.
Application
This attribute is used with usage="primary" when the main language of the resource is specified in the element.
objectPart Definition
Designates which part of the resource is in the language supplied.
Application
The following example indicates that only the summary is in Spanish:
<language objectPart="summary">
<languageTerm type= "code" authority="iso639-2b">spa</languageTerm>
</language>
The values of this attribute are not controlled, although it is preferable that institutions use consistent forms. altRepGroup; lang; xml:lang; script; transliteration; displayLabel See the Attributes used throughout the schema for description for each. SubelementsThe following subelement is described below: Subelement: <languageTerm>
Guidelines for UseIf expressed in coded form, the source of the code is contained in the value of the authority attribute. If no authority is given, it is assumed that the content is textual. If there is more than one representation of the same language, e.g. using different forms of the same language (code or text) or from different authorities, <languageTerm> is repeated within the <language> container. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer Implementation Guidelines for Shareable MODS Records require at least one pair of <languageTerm> elements representing the primary language of the text contained in a single <language> element. One of these <languageTerm> elements should carry the attribute type="text" and the other should have type="code". Additional pairs of <languageTerm> elements representing secondary languages may be included in separate <language> elements. These DLF/Aquifer guidelines require using the value "iso639-2b" for the authority attribute in the <languageTerm> element that contains the attribute type="code". Do not use an authority attribute in the <languageTerm> element that contains the attribute type="text". Element DescriptionAttributestype Definition
Indicates whether the language is expressed in a coded or textual form.
Application
This attribute may be used with the following values:
authority Definition
The controlled list from which the value is taken.
Application
This attribute may contain the following values:
authorityURI Definition
A URI uniquely identifying the vocabulary from which the controlled term has been selected, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying authorities may or may not be dereferenceable to human- or machine-readable information on the authority file, controlled vocabulary, or thesaurus.
valueURI Definition
A URI uniquely identifying the term or controlled value from a vocabulary, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying terms may or may not be dereferenceable to human- or machine-readable records for the term.
lang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <languageTerm>. Subelement <scriptTerm>
Guidelines for Use<scriptTerm> may be expressed in textual or coded form. If in coded form, the source of the code is contained in the value of the authority attribute. If no authority is given, it is assumed that the element content is textual. If there is more than one representation of the same script (e.g., text and code), <scriptTerm> is repeated. If the resource is in more than one script, <languageOfCataloging> is repeated. Element DescriptionAttributestype Definition
Identifies what type of <scriptTerm> is recorded.
Application
This attribute may be used with the following values:
authority Definition
The controlled list from which the value is taken.
Application
Record the name of the authoritative list used, if applicable, e.g. authority="iso15924". The Library of Congress maintains an online listing: Script Code and Term Source Codes.
authorityURI Definition
A URI uniquely identifying the vocabulary from which the controlled term has been selected, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying authorities may or may not be dereferenceable to human- or machine-readable information on the authority file, controlled vocabulary, or thesaurus.
valueURI Definition
A URI uniquely identifying the term or controlled value from a vocabulary, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying terms may or may not be dereferenceable to human- or machine-readable records for the term.
lang; xml:lang; script; transliteration See the Attributes used throughout the schema for descriptions of each.
SubelementsThere are no subelements for <scriptTerm>. EXAMPLES<language>
<languageTerm type="text">French</languageTerm>
<languageTerm type="code" authority="iso639-2b">fre</languageTerm> </language>
<language>
<languageTerm type="code" authority="iso639-2b">fre</languageTerm>
</language>
An XSLT stylesheet could be applied to transform this code to: Language: French <language>
<languageTerm type="text" objectPart="caption">English</languageTerm>
<languageTerm type="code" objectPart="caption" authority="iso639-2b">eng</languageTerm> </language>
This resource is a Persian/English dictionary: <language>
<languageTerm type="code" authority="iso639-2b">per</languageTerm>
<scriptTerm type="code" authority="iso15924">Arab</scriptTerm>
</language>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<scriptTerm type="code" authority="iso15924">Latn</scriptTerm>
</language>
This resource contains both English and French text: <language>
<languageTerm type="code" authority="iso639-2b">eng<languageTerm>
</language>
<language> <languageTerm type="code" authority="iso639-2b">fre<languageTerm>
</language>
This resource contains text in Egyptian Arabic, which is coded as an individual language in ISO 639-3: <language>
<languageTerm type="code" authority="rfc4646" >zh-Hans</languageTerm>
</language>
<language> <languageTerm type="code" authority="iso639-3" >arz</languageTerm>
</language>
This resource contains text in Navajo: <language>
<languageTerm type="code" authority="rfc5646" >i-navajo</languageTerm>
</language>
This record gives the language of the resource in two languages and a code and also indicates the script of the resource: <language>
<languageTerm type="text" authority="iso639-2b" lang="eng" >German</languageTerm>
<languageTerm type="text" authority="iso639-2b" lang-"fre" >allemand</languageTerm>
<languageTerm type="code" authority="iso639-2b">ger</languageTerm>
<scriptTerm type="code" authority="iso15924" >Latn</scriptTerm>
</language>
MAPPINGSMARC Mapping (Bibliographic)<languageTerm> = MARC 21 fields 008/35-37 or 041 with various subfields, depending on the attribute used. See also MARC Mapping to MODS for the <language> element. Dublin Core MappingThe MODS to Dublin Core Metadata Element Set Mapping recommends mapping the contents of the <language> element to <dc:language>. These guidelines further recommend mapping each subelement <languageTerm> to a distinct <dc:language> element. MODS examples expressed in Dublin Core: <dc:language>French</dc:language>
<dc:language>fre</dc:language> <dc:language>English</dc:language> <dc:language>eng</dc:language> Last Updated: March 1, 2013 |
March 1, 2013 |