EAD Tag Library for Version 1.0


Tag Library Conventions

The EAD Elements section of the tag library contains descriptions of 145 elements, which are arranged alphabetically by their tag names. The Index by Element Name makes it possible to locate those elements with tag names that might be hard to find alphabetically. For example, the index entry for Restrictions on Use points to the tag name <userestrict>. The Index by Element Name also serves as a concise, easily browsable list of all EAD elements.

The EAD Elements section presents information for each element as shown in Figure 11. Some of a DTD's specialized SGML terminology is explained on the following pages as a reminder of basic SGML conventions involved in encoding documents with EAD. (9)

This section also includes the three elements that occur in the EAD Group DTD: <eadgrp>, <archdescgrp>, and <dscgrp>. The EAD Group DTD allows several EAD-encoded finding aids to be combined into a single document and uses many EAD elements.

Tag Name:
Short, mnemonic form of the element name that is used in the machine-readable SGML-tagged document. The tag name is the first word at the top of the page. Tag names appear between angle brackets, e.g., <archdesc>, except in the listings under "May occur within" and "May contain," and are always in lowercase.

Element Name:
Expanded version of the tag name which more fully describes the element's meaning. The full name of the element is usually a word or phrase that identifies the element's purpose. In the tag library, the element name follows the tag name on the page defining that element and appears with initial capital letters, e.g., <archdesc> Archival Description.

Description:
The first paragraph of the description defines the element by drawing from terminology in archival glossaries, basic dictionaries, and data dictionaries such as ISAD(G), USMARC format, the Categories for the Description of Works of Art, and the Text Encoding Initiative DTD. (10) Any additional paragraphs describe how the element is used, differentiate it from similar elements, point out useful attributes, provide an illustrative example, or direct the reader to related elements. Stock phrases are used to suggest the kind of element being discussed. "Wrapper element" indicates an element that cannot contain text directly; a second, nested element must be opened first. Wrapper elements designate sets of elements that comprise a distinctive section of a finding aid, for example, the Descriptive Identification <did>. "Generic element" refers to elements common to many kinds of documents that contain information that does not specifically relate to the structural parts of a finding aid, e.g., <address> and <date>. "Formatting element" indicates elements that can be used to invoke special character or text presentation, such as block quotes, chronologies, and emphasis. When an element is required, that fact is also stated. Specific ISAD(G) data elements and/or MARC fields that relate to a given element are provided when applicable. For information on specified sequences of elements, consult the DTD itself. For example, you may wish to check the list of subelements in an SGML authoring program or DTD visualization tool.

May contain:
Identifies what may occur within the element being defined. Elements may be empty (e.g., containing only an attribute); or they may contain text (called #PCDATA); other elements; or a mixture of text and other elements.

The abbreviation #PCDATA (parsed character data) means that text content is allowed directly inside of an element, but the text cannot include characters that would be interpreted by an SGML parser as action codes. For example, a left angle bracket has to be represented as the character entity reference ⟨ so that it is not misinterpreted as the start of an element name.

The list of nested elements usually includes more elements than are generally needed, because similar elements sharing the same content model travel together as a group. This is an SGML device to ease the authoring of a DTD and to aid machine processing of encoded documents. For example, once one reference element such as <ref> is listed under May contain, all the reference elements appear, including <archref>, <bibref>, <extptr>, <extref>, and <ptr>, even though the simple internal <ref> element is the most likely choice in a particular context.

May occur within:
Identifies all of the parent elements within which the described element may appear. This information conveys the sense of where and how often an element is available throughout the DTD. Definitions for parent elements may provide additional information about an element's usage.

Attributes:
Identifies all attributes that can be associated with an element. Attributes are represented in lowercase letters in SGML coding, but the EAD Tag Library uses the convention of small capital letters to distinguish attributes from elements within the tag library context. See the EAD Attributes section of the tag library for definitions and additional information.

Examples:
Most element descriptions include a tagged example to indicate how attributes and elements can be used together. Many examples are taken from real finding aids; others have been specially constructed for the tag library. The examples illustrate any required sequences of elements, as in the case of subelements within the <eadheader>, or required attributes such as LEVEL in <archdesc>. In other cases, the examples are intended simply to show what is possible. Some elements have multiple examples--one may show very dense markup that uses numerous attributes while another may illustrate a minimalist approach to the markup. Either approach is valid in EAD, and it is up to the repository (and, as we gain more experience with EAD, the archival community) to determine the optimal level of markup. The examples are not intended to recommend depth of markup.


9. For basic information about SGML and pointers to additional SGML sources, consult the SGML/XML Web Page: <http://www.oasis-open.org/cover/sgml-xml.html>.
10. International Council on Archives. ISAD(G): General International Standard Archival Description, adopted by the Ad Hoc Commission on Descriptive Standards, Stockholm, Sweden, 21-23 January 1993. (Ottawa, Ont.: International Council on Archives, 1994. <http://www.archives.ca/ica/cds/isad(g)e.html>). Categories for the Description of Works of Art. (Santa Monica, Calif.: Getty Information Institute, 1996. <http://www.ahip.getty.edu/gii/index/cdwa.html>). Library of Congress. USMARC Format for Bibliographic Data. (Washington, D.C.: Library of Congress, 1994. <//www.loc.gov/marc/bibliographic/ecbdhome.html>). The Text Encoding Initiative is an international research project sponsored by the Association for Computing in the Humanities (ACH), the Association for Literary and Linguistic Computing (ALLC), and the Association for Computational Linguistics (ACL), and has developed an SGML encoding standard for a wide range of document types in the domain of humanities computing. (<http://www-tei.uic.edu/orgs/tei/>).

Table of Contents
Home
Page
Acknowledgments Introduction EAD Design
Principles
Overview of
EAD Structure
Tag Library
Conventions
EAD Attributes EAD Elements
by Tag Name
Index of
EAD Element Names


Go to:


Copyright Society of American Archivists, 1998.
All Rights Reserved.


[VIEW OF LC DOME] The Library of Congress

Library of Congress Help Desk (10/12/99)