MODS
User Guidelines
Version 2.0
General Application
The following lists top-level elements in MODS. All elements, subelements,
and attributes are described in the Detailed
Description of MODS Elements section in the order in which they appear
in the MODS XML schema.
Please see the Index
of MODS Elements by Element Name section for a complete list of all
elements (main and child) valid in the MODS
schema.
Language and Related Attributes.
Certain language and related attributes (e.g., script and transliteration
attributes) may be applied to most MODS elements, as indicated in the
MODS schema.
They are defined below:
- lang - This attribute is used to specify the language used
within individual elements, using the codes from ISO
639-2/b. This is equivalent to authority="iso639-2b" used
with the <language> element (which gives a language of the resource
described in the record), but is applied to the language used as content
of the metadata elements. There is no MARC 21 equivalent for this attribute,
since language cannot be currently indicated at the element level.
| |
<name type="personal"> |
| |
|
<namePart type="given">Jack</namePart> |
| |
|
<namePart type="family">May</namePart> |
| |
|
<namePart>I</namePart> |
| |
|
<description lang="eng">District
Commissioner</description> |
| |
|
<description lang="fre">Préfet
de région</description> |
| |
</name> |
- xml:lang - This attribute is used to specify the language used
within individual elements, using specifications in RFC
3066. RFC 3066 ("Request for Comments", which defines
Internet practice) uses the two-character ISO 639-1 codes along with
three-character ISO 639-2 codes for those languages not given in 639-1.
This is equivalent to authority="rfc3066" used with the <language>
element (which gives a language of the resource described in the record),
but is applied to the language used as content of the metadata elements.
There is no MARC 21 equivalent for this attribute, since language cannot
be currently indicated at the element level.
| |
<titleInfo xml:lang="fr"
type="translated"> |
|
| |
|
<nonSort>L'</nonSort> |
| |
|
<title>homme qui voulut être
roi</title> |
| |
</titleInfo> |
|
- script - This attribute specifies the script used within individual
elements, using codes from ISO
15924 (Code for the representation of names of scripts).
There is no MARC 21 equivalent for this attribute.
- transliteration - It specifies the transliteration technique
used within individual elements. There is no standard list of transliteration
schemes available, although one may be developed. There is no MARC 21
equivalent for this attribute.
Date Attributes. Certain date attributes may be applied to some
MODS elements, as indicated in the schema. They are defined below:
- encoding - The following values are used with the encoding
attribute:
- w3cdtf - This value is used for the profile of ISO 8601
that specifies the following date pattern: YYYY-MM-DD.
- iso8601 - This value is used for the profile of ISO 8601
that specifies the following date pattern: YYYYMMDD. It has been
used widely in MARC 21 date elements.
- marc - This value is used only for dates coded according
to MARC 21 rules in field 008/07-14. Thus, this would only apply
to the attribute in <dateIssued>. Examples include: 19uu (a
MARC convention to show unknown digits in a date), 9999 (a MARC
convention showing that the end date has not occured or is not known).
| |
<dateIssued encoding="marc">1999</dateIssued> |
- point - If no point attribute is specified, date is assumed
to be a single date. The following values are used with the point attribute:
- start - This value is used for the first date of a range
(or a single date, if used).
- end - This value is used for the end date of a range.
| |
<originInfo> |
|
| |
|
<dateOther point="start">20011008</dateOther> |
| |
|
<dateOther point="end">20011027</dateOther> |
| |
</originInfo> |
|
- keyDate - The following value is used with the keyDate attribute:
- yes - This value is used so that a particular date may
be distinguished among several dates. Thus for example, when sorting
MODS records by date, a date with keyDate="yes" would
be the date to sort on. It should occur only for one date at most
in a given record.
| |
<originInfo> |
|
| |
|
<dateOther keyDate="yes">20030328</dateOther> |
| |
|
<dateOther>20030427</dateOther> |
| |
</originInfo> |
|
Linking attributes. Certain linking attributes may be applied
to some MODS elements, as indicated in the schema. They are defined below:
- ID - This attribute is used to link internally and to reference
an element from outside the instance.
- xlink - This attribute is used for an external link. It is
defined in the MODS
schema as xlink:simpleLink, (see information about the XML
Linking Language), which in the XML schema specification has a further
breakdown for different types of xlinks. At this time, only xlink:href
is envisioned in MODS records. The guidelines will be revised if it
is found that there is a need for the other xlink attributes that are
available (e.g. xlink:role, xlink:title).
| |
<abstract xlink:href= "http://www.ojp.usdoj.gov/bjs/abstract/cchrie98.htm"/> |
MODS Homepage >> MODS
User Guidelines Homepage
Questions and comments:
Contact Us
(
08/18/2003
)
|