Introduction

Each EAC document contains two mandatory elements, the <eacheader> and the <condesc>-context description. The <eacheader> contains data used in the control of the creator description, and to provide the context of the description. The <condesc>-context description encompasses the description of the creator. Both the <eacheader> and <condesc> contain specific elements to support the functional intentions of the parent or containing element.

<eacheader>

The <eacheader> contains the following subelements:

•	<eacid>-eac identifier. Contains a unique identifier for the descriptive document within the owning system. Accommodates both machine- and human-readable versions of the identifier. Required.
•	<mainhist>-maintenance history. Contains one or more <mainevent>-maintenance events that document creating, importing, updating, and deletion of the description. Each maintenance event contains the name of the person or system responsible for the event, date, and description of the event. Each <mainevent> has a MAINTYPE attribute to accommodate one of four possible values: create, update, import, or delete. <date> and MAINTYPE are machine-readable. Required.
•	<languagedecl>-language declaration. Contains one or more machine- or human-readable declarations of the language of the description. Optional.
•	<ruledecl>-rules declaration. Contains one or more machine- or human- readable declarations of the content rules used in the creation of the description. Optional.
•	<sourcedecl>-source declaration. Contains one or more machine- or human-readable declarations of the sources for the information used in the description. Optional.
•	<authdecl>-authority declaration. Contains one or more machine- or human-readable declarations of authorities from which either descriptive categories or values are taken. Optional.

In addition to the subelements, the <eacheader> element also contains several attributes. The TYPE attribute is used to designate the type of creator described in the EAC document: corporate, personal, or family. The STATUS attribute is used to designate the editorial status of the description, draft, edited, or deleted. The ENCODINGANALOGSYS is used to designate the system in which there are semantic analogs for descriptive values used in the EAC document. This attribute is used in conjunction with the EA-encoding analog attribute, available on EAC descriptive elements. The value given in an EA attribute is the analog designation for the containing element used in the system identified in the ENCODINGANALOGSYS.

Four other attributes associated with the <eacheader> are used to designate authorities for values used in the description or rules for formulating such values. These have default values:

•	LANGENCODING Code values for language of description. Defaults to iso639-2b
•	SCRIPTENCODING Code values for script used. Defaults to iso15924
•	DATEENCODING Rules for formulating normalized date values: Defaults to iso8601
•	COUNTRYENCODING Code values for designating countries. Defaults to iso3166-1
•	OWNERENCODING Code value rules for repository or owner codes. Defaults to iso11551

<condesc>

<abbr> Abbreviation

A generic element for a shortened form of a word, including an acronym.

The EXPAN attribute can be used to supply the full form of an abbreviated word for indexing or searching purposes.

See also related element Expansion <expan>.

May contain: #pcdata

May occur within: abstract, addressline, altdate, archref, auth, bibref, bibseries, container, corpname, date, descnote, didentifier, dimensions, edition, emph, entry, event, existdate, extent, extref, famname, funact, genreform, head, head01, head02, head03, ignore, item, langmaterial, language, legalid, maindate, maindesc, materialspec, name, nameadd, note, num, origination, p, part, persname, physdesc, physfacet, physloc, place, publisher, ref, repository, rule, sourceinfo, sourceref, subarea, subject, title, unitdate, unitid, unittitle, usedate, value

Example:

 TABLE OF CONTENTS 

<abstract> Abstract

Within <archref> or <archunit>, a very brief summary of related archival materials described in an archival reference to an EAD instance. Used primarily to encode bits of biographical or historical information about the creator and abridged statements about the scope, content, arrangement, or other descriptive details about the archival unit or one of its components.

While <abstract> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, lb, note, ptr, ref, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<address> Address

A generic element for information about the place where someone or something is located and may be reached. Examples include a postal address, or the electronic mail address and phone number of the party granting publication permission.

Consider using an entity reference to store address information that occurs in many instances, as it is easier to update the information when located in a single, shared file. The entity reference can contain both the elements and their content. A style sheet can also be used to supply this kind of information.

May contain: addressline

May occur within: assetstruct, bioghist, blockquote, causa, character, descnote, entry, env, event, extref, funactdesc, item, location, locations, note, ocd, p, ref, repository, sourceinfo

Example:

 TABLE OF CONTENTS 

<addressline> Address Line

A generic element for one line of a postal or other address. May be repeated as many times as necessary to enter all available lines of an address.

May contain: #pcdata, abbr, emph, expan, extptr, extref, lb, ptr, ref

May occur within: address

Example:

 TABLE OF CONTENTS 

<altdate> Alternative Date

This element may be used in either in two ways. First to record an alternative machine-readable date using the NORMAL attribute on the <altdate>. Such recording of an alternative machine-readable date may be desirable when one wants to record both a Gregorian date, and the parallel date in another calendar, for example, the Muslim calendar. The second use of <altdate> would be to supply an alternative human-readable date. For example, the <date> or <existdate> may be given in modern English as a Gregorian calendar date, while the <altdate> may povide a regional date.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: date, existdate, usedate

Example:

 TABLE OF CONTENTS 

<archref> Archival Reference

A reference element that provides a citation and/or an electronic link to separately described archival materials of special interest. Examples of such materials include a record group, one of its large series (which might have separate EAD-encoded finding aids), a general reference to a collection with similar content or any of their components.

The <archref> element can be helpful in several situations. It can be used, with the HREF or ENTITYREF attribute, for linking to related EAD instance. The <archref> element can also be used to cite archival materials within a <bibref>, <descnote>, or <abstract> element. The <archref> may contain just text or some of the content-specific elements such as <origination>, <repository>, and <unittitle> to identify the different kinds of information in a citation.

Do not confuse <archref> with the Bibliographic Reference <bibref> element, which is used to cite works that are published entities or individual items that are not usefully designated as archival materials.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

May contain: #pcdata, abbr, abstract, bibref, container, descnote, emph, expan, extptr, extref, langmaterial, lb, materialspec, origination, physdesc, physloc, ptr, ref, repository, title, unitdate, unitid, unittitle

May occur within: abstract, bibref, container, descnote, dimensions, entry, event, extent, extref, item, langmaterial, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, ref, repository, sourceinfo, subarea, unitdate, unitid, unittitle

Example:

 TABLE OF CONTENTS 

<archunit>Archival Unit

<archunit> contains the description of an archival unit. The element contains the same elements as the EAD <did> in a referenced EAD <archdesc>, <c>, or <c01>-<c12> description.

While this information may be stored in the EAC instance, the currency of the information will be ensured if it is imported into the EAC instance from the EAD instance at the time of display or interchange.

May contain: abstract, container, descnote, langmaterial, materialspec, origination, physdesc, physloc, repository, unitdate, unitid, unittitle

May occur within: resourcerel

Example:

 TABLE OF CONTENTS 

<assetstruct> Assets and Structure

A description of the internal structure of a corporate body or the genealogy of a family.

May contain: address, blockquote, chronlist, descentry, head, list, p, table

May occur within: corpdesc, famdesc

Example:

 TABLE OF CONTENTS 

<auth> Authority

A subelement of <authdecl> within <eacheader> that specifies an authorized controlled vocabulary or thesaurus used for composing the authority record.

When the authorized controlled vocabularies are available on the web it is recommended that the URLs are declared as entities that may be referred to in the SYSTEM attribute of <auth>. The attribute SYSKEY accommodates the unique machine readable identifier of the record within the system referred to in the SYSTEM attribute. The value of SYSTEM must by an entity declared in the head of the EAC instance containing the path to the system.

References to declared authorities can be made in the attributes TYPEAUTH—Authority for type specification—and VALUEAUTH—authority for values—by referring to the mandatory ID of <auth>. These attributes are available in elements such as <funact>, <genreform>, <legalid>, <name>, <place>, <subject>, and <value>.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: authdecl

Example:

 TABLE OF CONTENTS 

<authdecl> Authority Declaration

A subelement within the <eacheader> that provides one or more machine- or human-readable declarations of authorized controlled vocabularies or thesauri used in the description.

May contain: auth

May occur within: eacheader

Example:

 TABLE OF CONTENTS 

<bibref> Bibliographic Reference

A reference element that provides a citation and/or electronic link for a published work such as a book, article, dissertation, motion picture, or sound recording. The <bibref> may contain just text or some of the content-specific elements such as <title>, <imprint>, or <edition>, although the latter two elements are unlikely to be used for unpublished works.

A list of <bibref>s may be gathered into a <bibliography>. A single <bibref> may be part of a Paragraph <p>. Use the HREF or ENTITYREF attribute to point to an electronic bibliographic work.

Use the more specific <archref> element to cite or link to separately described archival materials.

Do not confuse with the Reference <ref> element, which is an internal link from one place in a finding aid to another place in the same finding aid.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

May contain: #pcdata, abbr, archref, bibseries, corpname, edition, emph, expan, extptr, extref, famname, imprint, lb, name, num, persname, ptr, ref, title

May occur within: abstract, archref, container, descnote, dimensions, entry, event, extent, extref, item, langmaterial, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, ref, repository, sourceinfo, subarea, unitdate, unitid, unittitle

Example:

 TABLE OF CONTENTS 

<bibseries> Bibliographic Series

Information about the published series in which a book, encoded finding aid, or other published work has appeared. Refers to monographic series only. Not to be used for archival series.

May contain: #pcdata, abbr, emph, expan, lb, num, title

May occur within: bibref, bibunit, musunit, source, unittitle

Example:

 TABLE OF CONTENTS 

<bibunit> Bibliographic Description

<bibunit> contains the description of a bibliographic unit or item. The <bibunit> may contain just text or some of the content-specific elements such as <title>, <imprint>, or <edition>.

While this information may be stored in the EAC instance, the currency of the information will be ensured if it is imported into the EAC instance from a machine-readable bibliographic record at the time of display or interchange.

May contain: #pcdata, bibseries, descnote, edition, imprint, name, title

May occur within: resourcerel

Example:

 TABLE OF CONTENTS 

<bioghist> Biography or History

A concise essay or chronology that places the corporate body, person or family in its historical context. Includes significant information about the administrative history of a corporate body, or the life of an individual or family. The <bioghist> may contain just text in a series of Paragraphs <p>, and/or a Chronology List <chronlist> that matches dates and date ranges with associated events.

<bioghist> is recursive (i.e., the element is available within itself) to facilitate the use of multiple headings with subdivided descriptions for complex collections, and to enable EAC markup to be used for a variety of output. The <bioghist> element may also be nested to designate a portion of the essay or chronology that might be extracted as a subfield in another system.

May contain: address, bioghist, blockquote, chronlist, didentifier, head, list, p, table

May occur within: bioghist, desc

Example:

 TABLE OF CONTENTS 

<blockquote> Block Quote

A formatting element that designates an extended quotation. The quotation is set off from the text by spacing or other typographic distinction.

Use the Emphasis <emph> element, not <blockquote>, to tag words that are set off with quotations for emphasis or as a small quoted phrase that occurs, "as these words do," in the line of text.

May contain: address, chronlist, list, p, table

May occur within: assetstruct, bioghist, causa, character, descnote, env, event, funactdesc, item, locations, note, ocd, p, sourceinfo

Example:

 TABLE OF CONTENTS 

<causa> Causa

The source of authority or mandate for the corporate body in terms of its powers, functions, responsibilities or sphere of activities, such as a law, directive or charter.

References to the actual document sources can be contained in <bibref> or <archref> within a list or paragraph.

May contain: address, blockquote, chronlist, descentry, head, list, p, table

May occur within: corpdesc

Example:

 TABLE OF CONTENTS 

<character> Characteristics

Distinguishing characteristics of a person, such as sex, hair color, height, and so on. These characteristics may be described formally using <sex> or <descentry>, in informal prose, or a combination of both within <character>.

May contain: address, blockquote, chronlist, descentry, head, list, p, sex, table

May occur within: persdesc

Example:

 TABLE OF CONTENTS 

<chronhead> Chronological List Head

Contains column headings for a Chronological List. A Chronological List may contain three columns, and thus the Chronological Head may contain three column headers: <head01>, <head02>, and <head03>.

May contain: head01, head02, head03

May occur within: chronlist

Example:

 TABLE OF CONTENTS 

<chronitem> Chronological List Item

Within a Chronological List, Chronological List Item associates related date, optional place name, and an event or group of events. Each <chronitem> contains a <date> (either a single date or date range), followed by an optional <place>, followed by an <event>. When multiple <event>s are associated with a single <date>, the <event>s are bundled in an <eventgrp> tag, which is then easily paired with the appropriate <date> and optional <place>. <chronitem> is repeated for each set of associated date, place name, and event or group of events.

May contain: date, event, eventgrp, place

May occur within: chronlist

Example:

 TABLE OF CONTENTS 

<chronlist> Chronological List

Chronological List contains a sequentially structured list of significant events in the life of the person or during the existence of the family or corporate body described in the EAC record. Such events are associated with the date of occurrence and optionally with the name of a place. Each <chronlist> contains a series of <chronitem>s, each associating a <date>, an optional <place>, and an <event> or <eventgrp>.

A <chronlist> most often appears as part of the Biography or History <bioghist> element, but <chronlist> is also available for use in other elements that might need to present historical dates, places, and events in a multi-column list.

May contain: chronhead, chronitem, head

May occur within: assetstruct, bioghist, blockquote, causa, character, descnote, env, event, extref, funactdesc, item, locations, note, ocd, p, ref, sourceinfo

Example:

 TABLE OF CONTENTS 

<colspec> Column Specification

An empty formatting element that designates the position and size of a single column in a Table <table>. Attributes specify the unique name of the column, its unique number within the table, its width and rules, and the horizontal alignment of text within the column. The quantity of columns in a <table> is determined by the COLS attribute of the <tgroup> element, not by the number of <colspec>s defined. The values set for <colspec> override any values implied from <tgroup> or <thead> elements.

See also related elements <table> and <tgroup>.

May contain: EMPTY

May occur within: tgroup

Example:

 TABLE OF CONTENTS 

<condesc> Context Description

A container element for the bulk of an EAC instance consisting of groups of elements for identifying and describing a corporate body, person or family.

May contain: desc, eacrels, funactrels, head, identity, resourcerels

May occur within: eac

Example:

 TABLE OF CONTENTS 

<condescgrp>Group Context Description

A container element used only within <eacgrp>. The <condescgrp> consists of two or more EAC instances, and optional elements for identifying the group and its relations.

May contain: eac, eacrels, funactrels, head, identity, resourcerels

May occur within: eacgrp

Example:

 TABLE OF CONTENTS 

<container> Container

Within <archref> or <archunit>, an element for information that contributes to locating materials described in an EAD instance by indicating the kinds of devices that hold the materials and identifying any sequential numbers assigned to those devices.

Use of the TYPE attribute is strongly recommended to clarify the nature of the storage device. Use any useful designations, such as "box," "folder," and "reel."

While <container> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, lb, note, ptr, ref, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<corpdesc> Corporate Body Description

A container element for structured information about a corporate body and its context.

Subelements are available for specifications of the type <corptype>, legal status <legalstatus>, and business location <location> of the entity. A general descriptive entry <descentry> element is also available for expanding the descriptive categories according to local contents rules. The context of the corporate body can be described in subelements for its mandates and warrants <causa>, functions and activities <funactdesc>, assets and administrative structure <assetstruct>, as well as its general cultural and physical environment <env>. Each of these elements represents a particular descriptive category, and has the same subelements: <value>, optionally followed by <date>, <place>, <descnote>, and <sourceref>.

May contain: assetstruct, causa, corptype, descentry, env, existdesc, funactdesc, head, legalstatus, location, locations, ocd

May occur within: desc

Example:

 TABLE OF CONTENTS 

<corpgrp> Corporate Body Heading Group

An element used to associate parallel corporate names in various languages or script forms.

May contain: corphead, descnote, descnotes, nameadds, sourceref, sourcerefs

May occur within: identity

Example:

 TABLE OF CONTENTS 

<corphead> Corporate Body Heading

An element containing a heading for the corporate body described in the EAC instance. The heading may combine name elements with additional qualifiers so that the corporate body can be identified with certainty and distinguished from others bearing the same or similar names. The element is used both for authoritative and alternative headings.

A corporate name is the proper noun name that identifies an organization or group of people that acts as an entity. Examples include names of associations, institutions, business firms, nonprofit enterprises, governments, government agencies, projects, programs, religious bodies, churches, conferences, athletic contests, exhibitions, expeditions, fairs, and ships.

An agency may designate one of the headings as the authoritative or preferred heading within the context of its descriptive system by assigning its owner or repository code as a value in the attribute AUTHORIZED. The descriptive rules applied for establishing the heading shall be stated in the RULE attribute.

The other forms of the heading may be

•	any variant to the established forms or an incomplete piece of an established heading
•	translations of the name
•	changes of name over time
•	acronyms

The subelement <part> is used to distinguish components of names. While an entire name may be recorded in a single <part>, specific content rules may require use of <part> to distinguish name components such as the name of a corporate body when used as the entry component of the heading.

Use the subelements <existdate> for chronological qualifiers, <place> for topographical, and <nameadd> for other qualifiers that form the corporate heading. For changes of name over time use HEADTYPE to specify if the form was used earlier or later. The dates of when a form of name was used may be recorded in the element <usedate>.

Note that the dates of existence should always be recorded separately within <existdesc> even if it is included in the <corphead> as a qualifier.

Do not confuse with <head> which is used for display purposes only.

See also related element <corpname>.

May contain: descnote, descnotes, existdate, nameadd, part, place, sourceref, sourcerefs, usedate

May occur within: corpgrp, identity

Example:

 TABLE OF CONTENTS 

<corpname> Corporate Name

The proper noun name that identifies an organization or group of people that acts as an entity. In contrast to <corphead>, <corpname> is not a formal heading intended for use in indexing, sorting, and display.

The <corpname> element may be used in text elements such as <p>, and elements that may only contain other elements, such as <eacrel>.

See also the related element <corphead>.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, descnote, eacrel, entry, event, extref, item, note, origination, p, physdesc, physfacet, ref, repository, sourceinfo, unittitle

Example:

 TABLE OF CONTENTS 

<corptype> Corporate Body Type

The corporate body or organization type is an element for formal classifications of an entity with other or more specified terms than contained in the element <legalstatus>.

Enter terms in accordance with local rules, and use the TYPEAUTH attribute to specify any controlled vocabulary applied. If the type has changed, use the date element for the covering dates when the term applied.

May contain: date, descnote, place, sourceref, value

May occur within: corpdesc

Example:

 TABLE OF CONTENTS 

<date> Date

A generic element that contains a month, day, or year in any format. Use <date> to identify any dates that merit encoding.

For the dates of existence of the corporate body and the life dates of the person use <existdate> within the context of <existdesc>, and, when necessary for distinguishing a name heading, also within <corphead>, <pershead> or <famhead>.

A standard numeric form of the date (YYYYMMDD, etc.) can be specified with the NORMAL attribute to facilitate machine comparison of dates for searching, for example, 19480101/19980401 (YYYYMMDD/YYYYMMDD), or 1948/1998 (YYYY/YYYY). The TYPE attribute can be used to supply a more specific designation, for example, "life," "flourish," "depiction," "publication," or "acquisition." The CERTAINTY attribute may be used to indicate the degree of precision in the dating, for example, "circa," "approximately," or "after." The CALENDAR attribute can be used to specify the calendar from which the date stems, such as "gregorian" or "julian". The value "ce" (common or Christian era) is the default for the ERA attribute.

May contain: #pcdata, abbr, altdate, emph, expan, lb

May occur within: chronitem, corptype, descentry, descnote, eacrel, entry, event, extref, funactrel, imprint, item, legalstatus, location, note, p, physdesc, physfacet, ref, resourcerel, sex, sourceinfo, title, unittitle

Example:

 TABLE OF CONTENTS 

<desc> Description

Description contains either formal, informal, or a combination of formal and informal description of the entity described in the EAC instance.

After an optional <head>, three optional elements are available for formal description of each entity type: <corpdesc>, <persdesc> and <famdesc>. The formal information can be replaced or supplemented by an informal description using <bioghist>. Any other related information can be contained in the <ocd> or Other Context Description.

May contain: bioghist, corpdesc, famdesc, head, ocd, persdesc

May occur within: condesc

Example:

 TABLE OF CONTENTS 

<descentry> Description Entry

Within <corpdesc>, <famdesc>, and <perdesc>, <descentry> provides a means to extend the available descriptive categories. Its meaning will be dependent of the context in which it occurs, and the specifications entered in the TYPE attribute.

Each <descentry> contains a descriptive term entered within <value>, optionally followed by <date>, <place>, <descnote>, and <sourceref>.

May contain: date, descnote, place, sourceref, value

May occur within: assetstruct, causa, character, corpdesc, env, famdesc, funactdesc, ocd, persdesc

Example:

 TABLE OF CONTENTS 

<descnote> Descriptive Note

A generic element that provides additional information and specifications on the descriptive element in which it is contained.

Use TYPE to specify the kind of note provided. In order to accomodate more than one type and a <head>, see <descnotes>.

See also related element note.

May contain: #pcdata, abbr, address, archref, bibref, blockquote, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, table, title

May occur within: archref, archunit, bibunit, corpgrp, corphead, corptype, descentry, descnotes, eacrel, eacrels, existdesc, famgrp, famhead, funactrel, funactrels, identity, legalstatus, location, musunit, persgrp, pershead, resourcerel, resourcerels, sex, source

Example:

 TABLE OF CONTENTS 

<descnotes>

A container element for two or more descriptive notes.

May contain: descnote, head

May occur within: corpgrp, corphead, eacrel, eacrels, famgrp, famhead, funactrel, funactrels, identity, persgrp, pershead, resourcerel, resourcerels

Example:

 TABLE OF CONTENTS 

<didentifier> Digital Identifier

The Digital Identifier contains a machine-readable reference to an internet accessible digital portrait or other non-textual digital identifiers of the described entity.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bioghist, identity

Example:

 TABLE OF CONTENTS 

<dimensions> Dimensions

Within <physdesc>, <dimensions> provides information about the size of the materials being referenced. Measurements may be expressed in any convenient unit. Attributes may be used when the unit of measurement or type of dimension is not clear in the reference. The UNIT attribute specifies the kind of measurement, for example, "inches" or "meters." The TYPE attribute specifies the kind of dimensions being measured, for example, "height" or "circumference." Multiple dimensions, for example, height-by-width, can be tagged in a single <dimensions> element or in separate <dimensions> with distrinctive attribute values.

May contain: #pcdata, abbr, archref, bibref, dimensions, emph, expan, extptr, extref, lb, note, ptr, ref, title

May occur within: dimensions, physdesc

Example:

 TABLE OF CONTENTS 

<eac> Encoded Archival Context

The root element of an EAC instance. An EAC instance contains the description of one corporate body, family, or person as well as technical and intellectual information used in the creation, maintenance, and control of the description.

The <eac> element defines a particular instance of a document encoded with the EAC Document Type Definition. It contains two required elements — the<eacheader> and the <condesc>. The TYPE attribute is required to indicate whether the entity being described is a corporate body, person or family.

May contain: condesc, eacheader

May occur within: condescgrp

Example:

 TABLE OF CONTENTS 

<eacgrp>Group of EAC instances

The root element of a document containing two or more EAC instances.

Three types of EAC groups can be disignated:

disparate:	any package of records, linked or not, for the purpose of data exchange
identity:	a group of different eac records (from different sources) representing the same entity. A common header should then be contained in the condescgrp
related:	any group of eac instances representing related and linked entities, such as parents and children

The eac.dtd contains an entity eacgrp that should be set to 'INCLUDE' in order to enable this function.

May contain: condescgrp, eacheader

May occur within: Not applicable, highest-level element in EAC Group DTD.

Example:

 TABLE OF CONTENTS 

<eacheader> EAC Header

<eacheader> contains technical and intellectual information used in the creation, maintenance, and control of the EAC instance.

The element is required, and must contain <eacid> with a unique identifier for the instance; and <mainhist> providing information on the creation, maintenance, and disposition of the instance. Optionally, <eadheader> may also contain <authdecl> providing information on authorities or controlled vocabularies used in the description; <languagedecl> providing information on languages and scripts used in the description; <ruledecl> providing information on content or descriptive rules used in the the rules used in the composition of the description; and <sourcedecl> providing citation information for the documentary sources used in the composition of the description.

The drafting status of the record must be recorded in the STATUS attribute. The value "edited" indicates that the record is approved for publication . It is also recommended that the attribute DETAILLEVEL is used to indicate whether the record consists of minimal, partial or full level of detail in accordance with the rules applied. The TYPE and TYPEKEY attributes can be used for a specification or a local terms for the general entity type--corporate body, person or family--entered in eac@type.

The following attributes have default values:

COUNTRYENCODING specifies the authority for the value that appears in COUNTRYCODE on a variety of elements. DATEENCODING specifies the authority for composing the value that appears in <date> and <usedate>. LANGENCODING specifies the authority for the value that appears in LANG on a variety of elements. OWNERENCODING specifies the authority used for the value that appears in the OWNERCODE attributes on a variety of elements. SCRIPTENCODING specifies the authority used for the value that appears in theSCRIPT attributes on a variety of elements.

May contain: authdecl, eacid, languagedecl, mainhist, ruledecl, sourcedecl

May occur within: eac, eacgrp

Example:

 TABLE OF CONTENTS 

<eacid> EAC Identifier

A required subelement of <eacheader> that designates a unique identifier for a particular EAC instance.

The assigning owner ensures the uniqueness of the value within the EAC descriptive system under its control. The <eacid>when used in combination with the values in COUNTRYCODE and OWNERCODE will provide a globally unique identifier.

The attribute SYSKEY accommodates the unique machine readable identifier of the record within the system referred to in the SYSTEM attribute. The value of SYSTEM must by an entity declared in the head of the EAC instance containing the path to the system.

May contain: #pcdata

May occur within: eacheader

Example:

 TABLE OF CONTENTS 

<eacrel> EAC Relation

EAC Relation contains the description of a relation with another corporate body, person or family. Such related entities are typically described in another EAC instance. Use the <date> elements for specifying when the relation applied, and the <descnote> for more detailed specifications or explanations of the relation.

The attribute SYSKEY combined with SYSTEM accommodates a machine readable identifier of the related entity. The value of SYSKEY should hence be the same as the value of SYSKEY of <eacid> of the related EAC instance.

Use the RELTYPE attribute to specify the relationship of the related entity to the entity being described.

superior, subordinate:	any hierarchical relation
earlier, later:	any temporal relations, such as predecessor, successor
parent, child:	a biological or adoptive relation
associative:	any other relationship, "see also"
identity:	for linking different eac instances describing the same entity (used esp. for linking to external systems or when it otherwise is not possible to remove the duplicate)

The relations can be further specified with the attributes TYPE or preferably TYPEKEY, which can be associated with a thesaurus or local term list identified by the TYPEAUTH attribute.

Be careful to enter the RELTYPE values in such a way that the relation points in the right direction. If the EAC instance X has the relations:

<eacrel reltype="parent"><persname>Y</persname></eacrel>

   <eacrel reltype="child"><persname>Z</persname></eacrel>

    it means that "Y is the parent of X and Z is the child of X". These relations can also be displayed in the following structure:

    Relations of X

    Parent: Y

    Child: Z

   

Note that the temporal relations should not be applied for earlier/later forms of names for the same entity. Such names should be entered in the <corphead>, <pershead> or <famhead> elements with earlier/later specified in the attribute HEADTYPE. The criteria for when a change of name of a corporate body should be regarded as a mere name change or as a creation of a new entity should be based on content rules.

This element can also be used for a reference to another authority record for the same entity in another system, such as a national authority file. The value of the attribute RELTYPE should then be "identity".

May contain: corpname, date, descnote, descnotes, famname, persname, place, source

May occur within: eacrels

Example:

 TABLE OF CONTENTS 

<eacrels> EAC Relations

An element used for grouping one or more <eacrel> elements with an optional <head>.

May contain: descnote, descnotes, eacrel, head, sourceref, sourcerefs

May occur within: condesc, condescgrp

Example:

 TABLE OF CONTENTS 

<edition> Edition

An element used to record the version or edition of a published work in <bibref> or <bibunit>, or a museum object in <musunit>.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, bibunit, musunit, source, unittitle

Example:

 TABLE OF CONTENTS 

<emph> Emphasis

A formatting element for marking arbitrary words or phrases that are stressed or emphasized for linguistic effect. Use the RENDER attribute to specify the kind of emphasis, e.g., bold or italics.

When the content of an entire element should always be rendered in italics or some other display feature, use the style sheet functions instead of the <emph> element.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: abstract, addressline, altdate, archref, auth, bibref, bibseries, container, corpname, date, descnote, didentifier, dimensions, edition, emph, entry, event, existdate, extent, extref, famname, funact, genreform, head, head01, head02, head03, ignore, item, langmaterial, language, legalid, maindate, maindesc, materialspec, name, nameadd, note, num, origination, p, part, persname, physdesc, physfacet, physloc, place, publisher, ref, repository, rule, sourceinfo, sourceref, subarea, subject, title, unitdate, unitid, unittitle, usedate, value

Example:

 TABLE OF CONTENTS 

<entry> Entry

Entry is used to record the contents of a cell in a table row. A cell is the intersection of a row and a column. The <entry> attributes control cell spanning, alignment of the contents, and the rules on the cell edges. The attributes can be specified for <entry> or inherited from the nearest of the following table elements: <table>, <tgroup>, <colspec>, <tbody>, or <row>.

Three attributes are used together to force horizontal alignment on a specific character, such as a decimal point. The ALIGN attribute must be set to "char" (align="char"). The CHAR attribute should be set to the specific character on which the text will align (for example the decimal point, char="."). The CHAROFF attribute controls the position of the alignment by naming the percentage of the current column width that is to the left of the alignment character (for example, charoff="30").

The extent of a horizontal span is determined by naming the first column (NAMEST) and the last column (NAMEEND) in the span.

By convention, the specified rule is printed or displayed to the right of the column. External rules are specified using the FRAME attribute of the <table> element, horizontal rules are specified using ROWSEP.

May contain: #pcdata, abbr, address, archref, bibref, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, title

May occur within: row

Example:

 TABLE OF CONTENTS 

<env> Environment

Information on the social, cultural, economic, and political context in which the corporate body, person or family operated.

May contain: address, blockquote, chronlist, descentry, head, list, p, table

May occur within: corpdesc, famdesc, persdesc

Example:

 TABLE OF CONTENTS 

<event> Event

That part of a Chronological List Item <chronitem> which describes a significant occurrence, milestone, or activity. The <event> is paired with a <date> and optionally with a <place>. When two or more events occur in association with the same date, multiple <event>s can be grouped using <eventgrp>.

See related element Chronology List <chronlist>.

May contain: #pcdata, abbr, address, archref, bibref, blockquote, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, table, title

May occur within: chronitem, eventgrp

Example:

 TABLE OF CONTENTS 

<eventgrp> Event Group

An element within a Chronology List Item <chronitem> used for grouping two or more <event> elements associated with the same <date>.

See related element Chronology List <chronlist>.

May contain: event

May occur within: chronitem

Example:

 TABLE OF CONTENTS 

<existdate> Dates of existence

The dates of existence of the entity being described, such as dates of establishment and dissolution for corporate bodies, and dates of birth and death or floruit for persons.

Use <existdate> within the context of <existdesc> for the dates of existence of a corporate body and the life dates of a person. Use <existdate> in the context of a <corphead>, <famhead>, and <pershead> when necessary for distinguishing a name heading.

The element may contain a month, day, or year in any format. A standard numeric form of the date (YYYYMMDD, etc.) can be specified with the NORMAL attribute to facilitate machine comparison of dates for searching, for example, 19480101/19980401 (YYYYMMDD/YYYYMMDD), or 1948/1998 (YYYY/YYYY). The TYPE and TYPEKEY attributes can be used to supply a more specific designation, for example, "floruit", or to indicate the degree of precision in the dating, for example, "circa", "approximately", "before" or "after." The CALENDAR attribute can be used to specify the calendar from which the date stems, such as "gregorian" or "julian". The ERA attribute can be used to specify the era from which the data stems, such as "ce" (common or Christian era) or "bce" (before common or Christian era).

May contain: #pcdata, abbr, altdate, emph, expan, lb

May occur within: corphead, existdesc, famhead, nameadds, pershead

Example:

 TABLE OF CONTENTS 

<existdesc> Description of dates and places of existence

A container element for the dates of existence (<existdate>) and associated places, such as place of birth and place of death (<place>), of the entity .

May contain: descnote, existdate, place, sourceref

May occur within: corpdesc, famdesc, persdesc

Example:

 TABLE OF CONTENTS 

<expan> Expansion

A generic element to designate the full form of a word that often appears as an abbreviation or acronym. Use the ABBR attribute to supply the abbreviated form for indexing or searching purposes.

See also related element Abbreviation <abbr>.

May contain: #pcdata

May occur within: abstract, addressline, altdate, archref, auth, bibref, bibseries, container, corpname, date, descnote, didentifier, dimensions, edition, emph, entry, event, existdate, extent, extref, famname, funact, genreform, head, head01, head02, head03, ignore, item, langmaterial, language, legalid, maindate, maindesc, materialspec, name, nameadd, note, num, origination, p, part, persname, physdesc, physfacet, physloc, place, publisher, ref, repository, rule, sourceinfo, sourceref, subarea, subject, title, unitdate, unitid, unittitle, usedate, value

Example:

 TABLE OF CONTENTS 

<extent> Extent

A <physdesc> subelement for information about the quantity of the materials being described or an expression of the physical space they occupy in an <archref> or <archunit>. Includes such traditional archival measurements as cubic and linear feet and meters; also includes counts of microfilm reels, photographs, or other special formats, the number of logical records in a database, or the volume of a data file in bytes.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, lb, note, ptr, ref, title

May occur within: physdesc

Example:

 TABLE OF CONTENTS 

<extptr> External Pointer

An empty linking element that uses attributes to reference or link to an electronic object that is external to the EAC instance.

Use the ENTITYREF or HREF attribute to reference the external object

Do not confuse with the Pointer <ptr> element, which is an internal link for movement from one place in an EAC instance to another place in the same instance.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

May contain: EMPTY

May occur within: abstract, addressline, archref, bibref, container, descnote, dimensions, entry, event, extent, extref, head01, head02, head03, item, langmaterial, maindesc, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, ref, repository, sourceinfo, subarea, unitdate, unitid, unittitle

Example:

 TABLE OF CONTENTS 

<extref> External Reference

A linking element that can include text and subelements as part of its reference to an electronic object that is external to the EAC instance.

Use the ENTITYREF or HREF attribute to reference the external object.

Use the <ref> element to point to another location within the EAC document.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

May contain: #pcdata, abbr, address, archref, bibref, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, num, persname, place, ptr, subject, table, title

May occur within: abstract, addressline, archref, bibref, container, descnote, dimensions, entry, event, extent, extref, item, langmaterial, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, ref, repository, sourceinfo, subarea, unitdate, unitid, unittitle

Example:

 TABLE OF CONTENTS 

<famdesc> Family Description

Family Description contains elements used to provide a formal, structured description of a family.

Subelements are available for specifications of its legal status <legalstatus> and residence <location>. A general descriptive entry <descentry> element is also available for expanding the descriptive categories according to local contents rules. The context of the family can be described in subelements for its functions <funactdesc>, assets <assetstruct>, and the general cultural and physical environment <env>. Each of these elements represents a particular descriptive category and has the same subelements: <value>, optionally followed by <date>, <place>, <descnote>, and <sourceref>.

May contain: assetstruct, descentry, env, existdesc, funactdesc, head, legalstatus, location, locations, ocd

May occur within: desc

Example:

 TABLE OF CONTENTS 

<famgrp> Family Heading Group

An element used to associate parallel family names in various languages or script forms.

May contain: descnote, descnotes, famhead, nameadds, sourceref, sourcerefs

May occur within: identity

Example:

 TABLE OF CONTENTS 

<famhead> Family Heading

An element containing a heading for the family described in the EAC instance. The heading may combine name elements with additional qualifiers so that the family can be identified with certainty and distinguished from others bearing the same or similar names. The element is used both for authoritative and alternative headings.

A family name is the proper noun designation for a group of persons closely related by blood or persons who form a household. Includes single families and family groups.

When more than one heading is assigned, an agency may designate one of the headings as the authoritative or preferred heading within the context of its descriptive system by assigning its owner or repository code as a value in the attribute AUTHORIZED. The descriptive rules applied for establishing the heading shall be stated in the RULE attribute.

Within a family heading <part> should be used for components of names.

Use <date> for chronological qualifiers, <place> for topographical, and <nameadd> for other qualifiers. For changes of name over time use HEADTYPE to specify if the form was used earlier or later. The dates of when a form of name was used may be recorded in the element <usedate>.

Note that the dates of existence should always be recorded separately even if it is included in the <famhead> as a qualifier.

Do not confuse with <head> which is used for display purposes only.

See also the related element <famname>.

May contain: descnote, descnotes, existdate, nameadd, part, place, sourceref, sourcerefs, usedate

May occur within: famgrp, identity

Example:

 TABLE OF CONTENTS 

<famname> Family Name

The proper noun designation for a group of persons closely related by blood or persons who form a household. Includes single families and family groups.

The <famname> element may be used in text elements such as <p>, and elements that may only contain other elements, such as <eacrel>.

See also the related element <famhead>.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, descnote, eacrel, entry, event, extref, item, note, origination, p, physdesc, physfacet, ref, sourceinfo, unittitle

Example:

 TABLE OF CONTENTS 

<funact> Function or Activity

A term for a function, profession or activity performed by the entity.

Use the VALUEAUTH attribute to specify the vocabulary from which the term has been taken, and the VALUEKEY attribute for the unique identifier for the term in the case that this has not been stated in the funactrels.

May contain: #pcdata, abbr, emph, expan, ignore, lb, part

May occur within: descnote, entry, event, extref, funactrel, item, note, p, physdesc, physfacet, ref, sourceinfo, unittitle

Example:

 TABLE OF CONTENTS 

<funactdesc> Function or Activity Description

A prose description of the functions and activities of the corporate body or person.

In addition to or instead of <funactdesc>, it is recommended that functions and activities be formally represented using one or more terms selected from a controlled vocabulary or classification scheme and recorded using <funact>. See <funactrels>, <funactrel>, and <funact> for detailed instructions.

May contain: address, blockquote, chronlist, descentry, head, list, p, table

May occur within: corpdesc, famdesc, persdesc

Example:

 TABLE OF CONTENTS 

<funactrel> Function or Activity Relation

<funactrel> contains a function or activity term selected from a controlled vocabulary or classification scheme in <funact>. In addition to the term, the <date> of the function or activity, the <place> of jurisdiction or occurrence, <source> , and a descriptive note <descnote> may also be associated with the term.

Use the SYSKEY and SYSTEM attributes to point to the applied scheme and the defintion of the function or activity.

May contain: date, descnote, descnotes, funact, place, source

May occur within: funactrels

Example:

 TABLE OF CONTENTS 

<funactrels> Function or Activity Relations

An element used for grouping one or more <funactrel> elements with an optional <head>.

May contain: descnote, descnotes, funactrel, head, sourceref, sourcerefs

May occur within: condesc, condescgrp

Example:

 TABLE OF CONTENTS 

<genreform> Genre or Form Term

Within the <archunit> and <archref>, <genreform> is used within <physdesc> to identify the types of material being described by naming the style or technique of their intellectual content (genre); order of information or object function (form); and physical characteristics. Examples include: account books, architectural drawings, portraits, short stories, sound recordings, and videotapes.

May contain: #pcdata, abbr, emph, expan, ignore, lb, part

May occur within: descnote, entry, event, extref, item, note, p, physdesc, physfacet, ref, sourceinfo, unittitle

Example:

 TABLE OF CONTENTS 

<head> Head

<head> is available as the lead element in structurally complex elements. <head> functions as an optional element that can be used to enhance intelligibility of the record by labeling descriptive content for readers. <head> is thus an editorial addition to the record and not inherently a component of the description as such.

Do not confuse with the <listhead> subelements <head01>, <head02> and <head03>, which designate headings for columns in a <list> or <chronlist>. When used within <list> and <chronlist>, <head> labels the entire contents of the list.

Do not confuse with <corphead>, <famhead>, and <pershead> which are used for headings for corporate bodies, families, and personal names described in the EAC instance.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: assetstruct, bioghist, causa, character, chronlist, condesc, condescgrp, corpdesc, desc, descnotes, eacrels, env, famdesc, funactdesc, funactrels, identity, list, locations, ocd, persdesc, resourcerels, sourcerefs, table

Example:

 TABLE OF CONTENTS 

<head01> Head One

Within <listhead>, <head01> is used to provide a heading for the first column in a two-column list.

Within <chronhead>, <head01> is used to provide a heading for the first or <date>-column in either a two- or three-column list.

Do not confuse with <head>, which designates a heading for an entire list or other complex text structure.

May contain: #pcdata, abbr, emph, expan, extptr, lb, ptr

May occur within: chronhead, listhead

Example:

 TABLE OF CONTENTS 

<head02> Head Two

Within <listhead>, <head02> is used to provide a heading for the second column in a two-column list.

Within <chronhead>, <head02> is used to provide a heading for the second or <place>-column in either a two- or three-column list. <head02> should be omitted when <place> is not provided in at least one of the <chronitem>s in <chronlist>.

Do not confuse with <head>, which designates a heading for an entire list or other complex text structure.

May contain: #pcdata, abbr, emph, expan, extptr, lb, ptr

May occur within: chronhead, listhead

Example:

 TABLE OF CONTENTS 

<head03> Head Three

Within <chronhead>, <head03> is used to provide a heading for the third or <event>-column. If <head02> is omitted because <place> is not provided in at least one of the <chronitem>s in the <chronlist>, <head03> constitutes the second column in a two-column list. Otherwise it is the third column in a three-column list.

Do not confuse with <head>, which designates a heading for an entire list or other complex text structure.

May contain: #pcdata, abbr, emph, expan, extptr, lb, ptr

May occur within: chronhead

Example:

 TABLE OF CONTENTS 

<identity> Identity

<identity> is a mandatory element that groups elements to provide both authorized and alternative name headings that identify the entity described in the EAC instance, as well as other elements that assist in identification of the entity.

Qualifying additions to the names that are common to all of the headings can be incorporated into a single <nameadds> directly within <identity>. Qualifying additions to names that are not common to all headings should be recorded in <corphead>,<famhead>, or <pershead>, as appropriate.

May contain: corpgrp, corphead, descnote, descnotes, didentifier, famgrp, famhead, head, legalid, nameadds, persgrp, pershead, sourceref, sourcerefs

May occur within: condesc, condescgrp

Example:

 TABLE OF CONTENTS 

<ignore> Ignore

Within a controlled-value element, <ignore> may be used to designate an arbitrary string that is to be ignored in display, indexing, sorting, any combination of display, indexing, and sorting, or all three functions. The TYPE attribute is used to designate which functions are to be ignored. TYPE attribute values and their meaning are provided in the following table:

i:	indexing
s:	sorting
d:	display
di:	display and indexing
is:	indexing and sorting
ds:	display and sorting
all:	all

Within shared systems, the repository code should be entered in the AUTHORIZED attribute.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: funact, genreform, part, subject

Example:

 TABLE OF CONTENTS 

<imprint> Imprint

Information relating to the publication or distribution of a work cited in a Bibliographic Reference <bibref>, <bibunit>, <musunit>, or <source>. In each of these elements the place of publication, name of the publisher, and date of publication can be encoded as either plain text or wrapped in the <imprint> subelements <place>, <publisher>, and <date>. It is seldom, if ever, appropriate to use <imprint> in a citation for an unpublished work cited in a <bibref> or <bibunit>.

May contain: date, place, publisher

May occur within: bibref, bibunit, musunit, source, unittitle

Example:

 TABLE OF CONTENTS 

<item> Item

<item> is used for entries or members of lists. When used directly within a <list>, item is a member of a simple list. When used within <items>, the first <item> represents the first cell in a two-column table, and the second <item> the second cell.

Do not confuse with <chronitem>, which designates entries in a Chronology List <chronlist>.

See also related elements <list>, <defitem>, and <change>.

May contain: #pcdata, abbr, address, archref, bibref, blockquote, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, table, title

May occur within: items, list

Example:

 TABLE OF CONTENTS 

<items> Items

Within a <list>, <items> groups or associates two <item>s to form a simple two-column table. Such two-column tables are commonly used for lists in which the first <item> is a label or category and the second <item> is a member of or explains the category.

May contain: item

May occur within: list

Example:

 TABLE OF CONTENTS 

<langmaterial> Language of the Material

Within <archref> or <archunit>, a prose statement enumerating the language(s) of related archival material described in an archival reference to an EAD instance.

While <langmaterial> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

Language of the material may also be recorded in coded form in the The LANGUAGECODE attribute in the <language> subelement using the ISO 639-2b three-letter language codes.

Do not confuse with the Language Declaration <languagedecl> element which specifies the predominant language(s) used in the descriptive content of the records. See also the description for the <language> element.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, language, lb, note, ptr, ref, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<language> Language

Within <languagedecl> in the <eacheader>, <language> specifies the predominant language and script used in the descriptive content of the authority record. If the descriptive content employs more than one language or script, <language> should be repeated for each language and script pair. The LANGUAGECODE attribute should have the appropriate value selected from ISO 639-2b and the SCRIPTCODE attribute should have an appropriate value from ISO 15924. In addition to the attributes, the natural language name of the language and script should be entered as the content of the element.

In a multilingual authority record with headings in different languages or scripts, the languages and scripts used in the heading are to be identified in the attributes LANGUAGECODE and SCRIPTCODE on <pershead>, <corphead> or <famhead>, as appropriate.

The LANGUAGECODE attribute should be used to provide the three-letter ISO 639-2b code for the language.

The SCRIPTCODE attribute may be used to specify the ISO 15924 code for the script in which the language is written.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: langmaterial, languagedecl

Example:

 TABLE OF CONTENTS 

<languagedecl> Language Declaration

Within <eacheader>, <languagedecl> contains one or more <language> elements that declare the predominant language or languages used in the descriptive content of the record.

May contain: language

May occur within: eacheader

Example:

 TABLE OF CONTENTS 

<lb> Line Break

<lb> is a widely available element used to mark an intended arbitrary line break in the display of the otherwise in-line content of the containing element. <lb> should be used sparingly and not instead of formatting that can be applied by a stylesheet or another element, such as <list> or <p>.

May contain: EMPTY

May occur within: abstract, addressline, altdate, archref, auth, bibref, bibseries, container, corpname, date, descnote, didentifier, dimensions, edition, emph, entry, event, existdate, extent, extref, famname, funact, genreform, head, head01, head02, head03, ignore, item, langmaterial, language, legalid, maindate, maindesc, materialspec, name, nameadd, note, num, origination, p, part, persname, physdesc, physfacet, physloc, place, publisher, ref, repository, rule, sourceinfo, sourceref, subarea, subject, title, unitdate, unitid, unittitle, usedate, value

Attributes: This element has no attributes.

Example:

 TABLE OF CONTENTS 

<legalid> Legal Identifier

<legalid> contains a unique identifier for the entity described in the EAC instance. Such legal identifiers are typically assigned by an authoritative and typically public agency.

Although legal identifiers are used also for individuals—such as civic registration numbers, Swedish birth registration number, and US social security number—such identifiers typically should not be recorded for public display if the person is alive. Such display of legal identifiers for individuals constitutes an illegal act in many countries.

The authority under which the legal identifier has been allocated may be referenced in the TYPEAUTH attribute.

May contain: #pcdata, abbr, emph, expan, lb, part

May occur within: identity

Example:

 TABLE OF CONTENTS 

<legalstatus> Legal Status

The legal status of an entity, as the name suggests, is typically defined by government authorities and granted by the same government authorities or through authorized agencies.

Enter terms in accordance with legislation. Use the TYPEAUTH attribute to specify any controlled vocabulary applied. If the status has changed, use the date element for the covering dates when the status applied.

For corporate bodies the <corptype> element can also be used for more detailed classifications without legal significances.

May contain: date, descnote, place, sourceref, value

May occur within: corpdesc, famdesc, persdesc

Example:

 TABLE OF CONTENTS 

<list> List

<list> is used to form two types of lists. The first type of list is a simple list consisting of a series of two or more <item> elements. Simple lists can be “marked,” for example, with bullets; “ordered,” for example, with Arabic numerals; or displayed “as is.”

The second type is a definition list. A definition list consists of a series of two or more <items> elements, each of which contains two <item> elements. Definition lists are essentially two-column tables. Generally the first <item> contains a term or phrase and the second <item> a description or definition of the term or phrase.

The TYPE attribute is used to identify the type of list. Values of TYPE are:

simple:	list is a simple series of entries.
marked:	a simple list prefixed with a character, for example, as bullet.
ordered:	a simple list prefixed with an indication of order such as a numeral or alphabetical character.
deflist:	a definition list

If the TYPE attribute value is “marked”, the MARK attribute can be used to provide the character that is intended to be used as the entry prefix. For example, "&#8226;" for a bullet.

If the TYPE attribute value is “ordered”, the NUMERATION attribute can be used to indicate the method of indicating order. The following values are available:

arabic:	Arabic number
upperalpha:	Upper case alphabetic character
loweralpha:	Lower case alphabetic character
upperroman:	Upper case Roman numeral
lowerroman:	Lower case Roman numeral

If ordering is to take place across two or more lists, the CONTINUATION attribute value should be “continues”. While “starts” is also a value option, “starts” is implied when the CONTINUATION attribute is absent.

See also the related elements <items> and <item>.

May contain: head, item, items, listhead

May occur within: assetstruct, bioghist, blockquote, causa, character, descnote, entry, env, event, extref, funactdesc, item, locations, note, ocd, p, ref, sourceinfo

Example:

 TABLE OF CONTENTS 

<listhead> List Head

A formatting element that groups headings for columns in a definition list. The headings are called <head01> and <head02>.

See <list> for additional information on definition lists.

May contain: head01, head02

May occur within: list

Example:

 TABLE OF CONTENTS 

<location> Location

An element used to contain information on the place or jurisdiction where the entity was based, lived or resided or had some other connection. <place> should be used for the name of the place, and <address> may be used for a full or partial address. <date> may be used to specify the date or dates the location is relevant to the described entity. Use the TYPE attribute to specify how the location is related to the entity.

May contain: address, date, descnote, place, sourceref

May occur within: corpdesc, famdesc, locations, persdesc

Example:

 TABLE OF CONTENTS 

<locations>

An element used for grouping two or more <location> elements with an optional <head>.

May contain: address, blockquote, chronlist, head, list, location, p, table

May occur within: corpdesc, famdesc, persdesc

Example:

 TABLE OF CONTENTS 

<maindate> Maintenance Date

Within the <mainevent>, <maindate> contains the occurrence date of a maintenance event. The date may be machine generated or entered manually. The content of the element is intended to be a human-readable natural language date, with a machine-readable date provided as the value of the NORMAL attribute, formulated according to ISO 8601.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: mainevent

Example:

 TABLE OF CONTENTS 

<maindesc> Maintenance Description

Within the <mainevent>, <maindesc> contains a description of a maintenance event. The description may be machine generated or entered manually.

May contain: #pcdata, abbr, emph, expan, extptr, lb, ptr

May occur within: mainevent

Example:

 TABLE OF CONTENTS 

<mainevent> Maintenance Event

Within the <mainhist>, each <mainevent> contains the name, date, and description of an EAC description maintenance event or activity.

Each <mainevent> has a required MAINTYPE attribute to accommodate one of four possible values: create, update, import, or delete.

May contain: maindate, maindesc, name

May occur within: mainhist

Example:

 TABLE OF CONTENTS 

<mainhist> Maintenance History

Within the <eacheader>, <mainhist> contains one or more <mainevent>s documenting milestone events or activities in the maintenance of the EAC instance. <mainhist> is a required element containing at least one <mainevent>.

<mainhist> is required because it is considered essential in the effective management and communication or exchange of EAC descriptive instances.

May contain: mainevent

May occur within: eacheader

Example:

 TABLE OF CONTENTS 

<materialspec> Material Specific Details

Within the <archref> or <archunit>, data which are unique to a particular class or form of material and which are not assigned to any other element of description in an archival reference to an EAD instance. Examples of material specific details include mathematical data, such as scale for cartographic and architectural records, jurisdictional and denominational data for philatelic records, and physical presentation data for music records.

While <materialspec> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, lb, materialspec, note, num, ptr, ref, title

May occur within: archref, archunit, materialspec

Example:

 TABLE OF CONTENTS 

<musunit> Museum Description

<musunit> contains the description of a museum object or collection.

While this information may be stored in the EAC instance, the currency of the information will be ensured if it is imported into the EAC instance from a machine-readable museum description at the time of display or interchange.

May contain: #pcdata, bibseries, descnote, edition, imprint, name, title

May occur within: resourcerel

Example:

 TABLE OF CONTENTS 

<name> Name

In most contexts of use, <name> contains a proper noun or noun phrase designation for a named entity that is difficult to tag more specifically as a <corpname>, <famname>, <geogname>, <persname>, or <title>. <name> may be used in place of the more specific access elements when it is not known what kind of name is being described or when a high degree of precision is unnecessary.

Within <mainevent>, where formal designation of the type of name is not considered important, <name> is used for the person or agency responsible for a maintenance event.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, bibunit, mainevent, musunit, origination, repository, source

Example:

 TABLE OF CONTENTS 

<nameadd> Name Addition

<nameadd> is used for descriptive or distinguishing information other than date or place added to names within <corphead>, <famhead>, and <pershead>. Date and place are to be encoded using <date> and <place>.

Use the TYPE attribute to specify the type of addition.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: corphead, famhead, nameadds, pershead

Example:

 TABLE OF CONTENTS 

<nameadds> Name Additions

Used directly within <corpgrp>, <famgrp>, <persgrp>, or <identity> for distinguishing or descriptive additions to names that are common to all headings in the containing element. Common additions generally reflect characteristics of the described entity rather than a characteristics of a particular form of name, for example, dates of existence or place.

May contain: existdate, nameadd, place

May occur within: corpgrp, famgrp, identity, persgrp

Example:

 TABLE OF CONTENTS 

<note> Note

A generic element that provides a short statement explaining the text, indicating the basis for an assertion, or citing the source of a quotation or other information.

For additional descriptive information of an associated entry use descnote.

May contain: #pcdata, abbr, address, archref, bibref, blockquote, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, table, title

May occur within: abstract, container, descnote, dimensions, entry, event, extent, item, langmaterial, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, repository, sourceinfo, subarea, unitdate, unitid, unittitle

Example:

 TABLE OF CONTENTS 

<num> Number

<num> may be used to encode a number or numeric designation when such encoding would facilitate specific processing. In general, such encoding is not necessary. The TYPE attribute may be used to different types or uses of numbers or numeric designation.

Do not confuse with other more specific elements that may contain numeric information.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, bibseries, descnote, entry, event, extref, item, materialspec, note, p, ref, sourceinfo, title, unittitle

Example:

 TABLE OF CONTENTS 

<ocd> Other Context Data

<ocd> for textually complex information about the described entity that is not easily incorporated into one of the other named elements within <condesc>. When converting authority records to an EAC compliant format, the <ocd> element helps to minimize conversion difficulties by designating as "OCD" information that does not fit easily into one of EAC's more distinct categories.

The element should be used with restraint and only after carefully considering the consequences that unspecified content designation poses for searching, retrieving, and displaying information in a networked environment.

May contain: address, blockquote, chronlist, descentry, head, list, ocd, p, table

May occur within: corpdesc, desc, famdesc, ocd, persdesc

Example:

 TABLE OF CONTENTS 

<origination> Origination

Within <archref> or <archunit>, <origination> contains the name or names of the creators of related archival materials described in an archival reference to an EAD instance.

While <origination> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, corpname, emph, expan, extptr, extref, famname, lb, name, note, persname, ptr, ref, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<p> Paragraph

<p> contains one or more sentences that form a logical prose passage. A paragraph may be a subdivision of a larger composition, or it may exist alone. It is usually typographically distinct: A line space is often left blank before it; the text begins on a new line; and the first letter of the first word is often indented, enlarged, or both.

May contain: #pcdata, abbr, address, archref, bibref, blockquote, chronlist, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, list, note, num, persname, place, ptr, ref, subject, table, title

May occur within: assetstruct, bioghist, blockquote, causa, character, env, funactdesc, locations, ocd

Example:

 TABLE OF CONTENTS 

<part> Part

<part> may be used to distinguish components of the containing element when such distinguishing would be useful in processing of the information, or when content rules require such components to be distinguished.

<part> is particularly important in the construction of the controlled headings <corphead>, <famhead>, and <pershead>. It may also be useful in distinguishing components of <funact>, <genreform>, <legalid>, <place>, and <subject>.

Use the TYPE or TYPEKEY attributes to provide a precise designation of the name component, such as forename, surname or patronymic in personal name headings and parent body or subordinate unit in corporate name headings.

The punctuation used for distinguishing different parts at display should not be entered in the element but handled by the style sheet.

May contain: #pcdata, abbr, emph, expan, ignore, lb

May occur within: corphead, famhead, funact, genreform, legalid, pershead, place, subject

Example:

 TABLE OF CONTENTS 

<persdesc> Person Description

<persdesc> contains structured information about a person or the context of the person.

Within <persdesc>, several specific descriptive entries are available. Elements are available for specification of the legal status <legalstatus>, <sex>, and <location> (or residence) of the person. The context of the person can be described in elements for functions and activities, <funactdesc>; personal characteristics, <character>; as well as the general cultural and physical environment, <env>. A general descriptive element, <descentry>, is also available for expanding the descriptive categories according to local contents rules. Each of these elements represents a particular descriptive category, and has the same elements: <value>, optionally followed by <date>, <place>, <descnote>, and <sourceref>.

May contain: character, descentry, env, existdesc, funactdesc, head, legalstatus, location, locations, ocd, sex

May occur within: desc

Example:

 TABLE OF CONTENTS 

<persgrp> Personal Name Heading Group

An element used to associate parallel personal names in various languages or script forms.

May contain: descnote, descnotes, nameadds, pershead, sourceref, sourcerefs

May occur within: identity

Example:

 TABLE OF CONTENTS 

<pershead> Personal Name Heading

An element containing a heading for the person described in the EAC instance. The heading may combine name elements with additional qualifiers so that the person can be identified with certainty and distinguished from others bearing the same or similar names. The element is used both for authoritative and alternative headings.

A personal name is the name given to an individual, or a name by which he/she is known, consisting of such elements as surname, forename, patronymic, or toponym.

When more than one heading is assigned, an agency may designate one of the headings as the authoritative or preferred heading within the context of its descriptive system by assigning its owner or repository code as a value in the attribute AUTHORIZED. The descriptive rules applied for establishing the heading shall be stated in the RULE attribute.

The other forms of the heading may be

•	any variant to the established forms or an incomplete piece of an established heading
•	changes of name over time, such as maiden name
•	pseudonyms

Use the attributes TYPE or TYPEKEY to specify the type of name entered.

<part> is used to distinguish components of names. While an entire name may be recorded in a single <part>, specific content rules may require use of <part> to distinguish name components such as family name, patronymic and forename.

Use <existdate> for temporal, <place> for geographical, and <nameadd> for other qualifiers. For changes of name over time, the dates of when a form of name was used may be recorded in the element <usedate>.

Note that the dates of existence should always be recorded separately within <existdesc> even if it is included in the <pershead> as a qualifier.

Do not confuse with <head> which is used for display purposes only.

See also related element <persname>.

May contain: descnote, descnotes, existdate, nameadd, part, place, sourceref, sourcerefs, usedate

May occur within: identity, persgrp

Example:

 TABLE OF CONTENTS 

<persname> Person Name

The proper noun designation for an individual, including any or all of that individual's forenames, surnames, honorific titles, and added names.

The <persname> element may be used in text elements such as <p>, and elements that may only contain other elements, such as <eacrel>.

See also the related element <pershead>.

May contain: #pcdata, abbr, emph, expan, lb

May occur within: bibref, descnote, eacrel, entry, event, extref, item, note, origination, p, physdesc, physfacet, ref, sourceinfo, unittitle

Example:

 TABLE OF CONTENTS 

<physdesc> Physical Description

Within <archref> or <archunit>, a container element for bundling information about the appearance or construction of related archival materials, such as their dimensions, a count of their quantity or statement about the space they occupy, and terms describing their genre, form, or function, as well as any other aspects of their appearance, such as color, substance, style, and technique or method of creation. The information may be presented as plain text, or it may be divided into the <dimensions>, <extent>, <genreform>, and <physfacet> subelements.

While <physdesc> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, corpname, date, dimensions, emph, expan, extent, extptr, extref, famname, funact, genreform, lb, note, persname, physfacet, ptr, ref, subject, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<physfacet> Physical Facet

Within the <archunit> or <archref>, <physfacet> is an element of <physdesc> for information about an aspect of the appearance of the described materials, such as their color, style, marks, substances, materials, or techniques and methods of creation. It is used especially to note aspects of appearance that affect or limit use of the materials. It generally should not be used for aspects of physical description that are covered more directly by the <extent>, <dimensions>, and <genreform> elements, although use of <genreform> may be appropriate for further specification within some <physfacet> instances.

The TYPE attribute may be used to specify which aspect of the physical appearance is being designated, e.g., <physfacet type="color">red</physfacet>.

May contain: #pcdata, abbr, archref, bibref, corpname, date, emph, expan, extptr, extref, famname, funact, genreform, lb, note, persname, ptr, ref, subject, title

May occur within: physdesc

Example:

 TABLE OF CONTENTS 

<physloc> Physical Location

Within the <archunit> or <archref>, <physloc> is used for information identifying the place where the described materials are stored, such as the name or number of the building, room, stack, shelf, or other tangible area.

While <physloc> may be originally composed in the EAC instance, it is generally derived, manually or programmatically, from an EAD instance describing the related archival materials.

May contain: #pcdata, abbr, archref, bibref, emph, expan, extptr, extref, lb, note, ptr, ref, title

May occur within: archref, archunit

Example:

 TABLE OF CONTENTS 

<place> Place

The proper noun designation for a place, natural feature, or political jurisdiction. Examples include: Appalachian Mountains; Baltimore, Md.; Chinatown, San Francisco; and Kew Gardens, England.

Use the PLACETYPE attribute to specify whether the element refers to a geographic name or a jurisdictional area. More detailed specifications of the type of place can be done with the TYPE attribute. The NORMAL attribute can be used to provide the authority form of a term that has been encoded with <place> in narrative text, for example., within a <p>.

Use the VALUEAUTH attribute to specify the vocabulary from which the name has been taken, and the VALUEKEY attribute for the unique identifier for the thesaurus term.

May contain: #pcdata, abbr, emph, expan, lb, part

May occur within: chronitem, corphead, corptype, descentry, descnote, eacrel, entry, event, existdesc, extref, famhead, funactrel, imprint, item, legalstatus, location, nameadds, note, p, pershead, ref, resourcerel, sex, sourceinfo

Example:

 TABLE OF CONTENTS 

<ptr> Pointer

An empty linking element that uses attributes to provide information that can be used in rendering to enable navigating from one place in an EAC instance to another place in the same EAC instance. Unlike <ref>, <ptr> cannot contain text or elements to describe the referenced object.

Do not confuse with <extptr> which is used to connect the EAC instance to an external electronic object, which is not part of the described materials.

Either of two attributes may be used to provide addressing information to be used in enabling navigation: HREF or TARGETIN. Of the two, TARGETIN is the most stable and reliable method, as it employs dedicated XML features.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAC linking elements is stable, examples of EAC usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink/.

See related linking elements <extptr>, <extptrloc>, <extref>, <extrefloc>, <linkgrp>, <ptrgrp>, <ptrloc>, <ref>, and <refloc>.

May contain: EMPTY

May occur within: abstract, addressline, archref, bibref, container, descnote, dimensions, entry, event, extent, extref, head01, head02, head03, item, langmaterial, maindesc, materialspec, note, origination, p, physdesc, physfacet, physloc, publisher, ref, repository, sourceinfo, subarea, unitdate, unitid, unittitle