|The Library of Congress >> Standards >> MADS|
HOME >> MADS - XML Format for Authorities Data
MADS 2.0 - XML Format for Authorities Data (June 2, 2011)
MADS is a MARC21-compatible XML format for the type of data carried in the MARC 21 Authority format. An individual MADS description consists of at least one main <authority> element and any number of additional main elements: <authority>, <related>, and/or <variant>. Each of these main elements contains one or more of the following descriptor subelements: <name>, <titleInfo>, <topic>, <temporal>, <genre>, <geographic>, <hierarchicalGeographic>, <occupation>. One or more descriptor subelements may be combined within an <authority> element to control an authoritative heading that consists of multiple parts, for example, name/title headings and subject strings with various components (e.g. <topic> and <geographic>). MADS main elements (containing descriptor subelements) are then supplemented by any number of minor elements.
At a higher level, the <madsCollection> root element is used to contain a group of MADS descriptions, while the <mads> root element is used to contain main and minor elements within an individual MADS description.
This document does not include descriptions of all MADS elements and attributes. Please see Outline of Elements and Attributes in MADS 2.0 for a comprehensive list.
The <madsCollection> element contains a group of MADS descriptions.
The <mads> element contains an individual MADS description.
The <authority> element is a container that includes a standardized "authoritative" form of an agent (person or organization), an event, a title, or a term (topic, genre, geographic). The authority container may only be repeated to give multiple authoritative forms in different languages or scripts
The geographicSubdivision attribute can be used with the <authority> element to indicate whether or not a concept can append a geographic facet, such as the name of a country or other jurisdiction, region, or geographic feature. This information is important to some controlled vocabularies, such as LCSH. For vocabularies to which this does not apply, the attribute would not be used. The geographicSubdivision attribute is comparable to MARC Authority 008/06, and can carry the following values:
none - no geographic facet applies
The <related> element includes a name or term that has some relation to the authoritative form. It is not a variant because it is a legitimate, authoritative heading on its own. These are equivalent to "see also" references in library catalogs. The type attribute designates the type of relationship, using the following values:
earlier - used for the earlier form of a name, especially
corporate bodies that have changed name over time.
The <variant> element includes a reference such as a name or term that is not considered the authoritative form. For example, if the person's authoritative name is John J. Jones, but he is sometimes referred to as J.J. Jones, then J.J. Jones can be entered as a name reference under <variant>. In library catalogs, variant headings are only used as "see" references and are not used on the catalog's bibliographic, but lead users to the correct heading. The type attribute designates the type of variant, using the following values:
acronym - an acronym which is considered a variant of the
name in <authority>. Used most frequently for corporate names.
Corresponds to MARC Authority 4XX $w/0, value "d".
<affiliation> allows for encoding the full affiliation and contact information for a person or organization, including position, organization name, address, phone and fax numbers, email address, and a date that the contact information was valid. It can be used to carry one or more affiliations related to a personal name. It is equivalent to MARC Authority field 373.
<classification> includes a designation applied to a resource that indicates the subject by applying a formal system of coding and organizing resources according to subject areas. The classification or call number of a resource is included in the <classification> element. It is equivalent to MARC Authority fields 053, 055, 060, 065, 070, 080, 082, 083, 086, 087.
<fieldOfActivity> includes a field of endeavor or business, area of expertise, or area of competence of a person or organization. It is equivalent to MARC Authority field 372.
<identifier> includes an identifier associated with the entity described in the record. The type attribute specifies the identifier scheme, which is an uncontrolled list. An example of an identifier type appropriate for a MADS record is "istc". It is equivalent to MARC Authority fields 010, 016, 020, 022, 024, 035.
<language> is a container element; the actual language values are recorded in the subelement <languageTerm> and actual script values are recorded in the subelement <scriptTerm>. If the content of the resource is in more than one language, the <language> element is repeated. It is equivalent to MARC Authority field 377.
<note> can include general information--if no attribute is specified, the field is treated as a general note, e.g., MARC Authority 680 field. Optionally, <note> can carry a "type" attribute with specific note type information. Specific type attribute values for the <note> element correspond to a number of notes fields in the MARC Authorities format:
<url> includes any URL associated with the entity described in the record. Examples are an organization's Web site or a personal home page. Note that standard identifiers associated with the entity (e.g. ISTC) are included in <identifier> field. It is equivalent to MARC Authority field 856.
<extension> is used to provide for information not covered by MADS. It may be used for elements that are local to the creator of the data, similar to MARC 9XX fields.
<recordInfo> is a container element that contains subelements relating to information necessary for managing metadata.
HOME >> MADS - XML Format for Authorities DataQuestions and comments: Contact Us ( June 6, 2011 )
|Legal | External Link Disclaimer|