Elements
<abstract>
Summary:
An optional element within <biogHist> that contains a brief summary of
the information contained within the <biogHist> as a whole.
May contain:
May occur within:
Description and Usage:
The <abstract> is a brief synopsis of the identity's biography or
history that is often based on the longer descriptions found in
<biogHist>. Its purpose is to help readers quickly identify the
identity described in the EAC-CPF instance. The content within this element may
also be harvested by other systems to provide explanatory context for the
<nameEntry> data when it appears in a set of search results.
<abstract> may include one or more <reference> elements to point
to external resources that provide additional descriptive data.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<address>
Summary:
An optional child element of <place> that binds together one or more
<addressLine> elements to encode a postal or other address.
See also:
Use <contact> to encode digital addresses and contact
information.
May contain:
May occur within:
Description and Usage:
<address> is an optional wrapper element within <place> used to
encode a physical or analog address.
Ideally <address> should be bundled with a <placeName> element
within <place> to provide both the name and address of a location.
<address> must include one or more <addressLine> element(s) that
provide full or sufficient information identifying a postal or other physical
address related to the entity being described.
One of <address>, <placeName>, <placeRole>,
<geographicCoordinates>, or <contact> is required within
<place>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<addressLine>
Summary:
A required child element of <address> used for recording one line of a
postal or other address.
Attribute usage:
Use one of the set values in the optional @addressLineType
attribute to encode the part of the address that the <addressLine>
refers to, for example "street".
May contain:
[text]
May occur within:
Description and Usage:
<addressLine> is used to encode parts or lines of a physical address
within a parent <address> element.
<addressLine> may be repeated as many times as necessary to enter all
parts of an address.
Attributes:
Optional (values limited to: county, country, district, municipality,
postBox, postalCode, region, street)
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<agencyCode>
Summary:
A child element of <maintenanceAgency> that provides a code for the
institution or service responsible for the creation, maintenance, and/or
dissemination of the EAC-CPF instance.
Attribute usage:
Use @status with the value "authorized" or "alternative" to
declare whether the <agencyCode> is using an authorized value, e.g. a
registered ISIL code, or an alternative one.
See also:
Use <agencyName> to record the name of the agency.
Use <otherAgencyCode> to record any alternative codes representing
the agency.
Use <recordId> in combination with <agencyCode> to provide
a globally unique identifier for the EAC-CPF instance.
May contain:
[text]
May occur within:
Description and Usage:
Use <agencyCode> to record a code indicating the institution or service
responsible for the creation, maintenance and/or dissemination of the EAC-CPF
instance. Use of <agencyCode> is recommended, as the combination of
<agencyCode> and the required <recordId> provide a globally
unique identifier for the instance.
<maintenanceAgency> must include one or both of <agencyCode> and
<agencyName>.
It is recommended that the code follow the format of the International Standard
Identifier for Libraries and Related Organizations (ISIL: ISO 15511): a prefix,
a dash, and an identifier. The code is alphanumeric (characters A-Z, 0-9,
solidus, hyphen-minus, and colon) with a maximum of 16 characters. If
appropriate to local or national convention, insert a valid ISIL for an
institution, whether provided by a national authority (usually the national
library) or a service (such as OCLC). If this is not the case then local
institution codes may be given with the ISO 3166-1 alpha-2 country code as the
prefix to ensure international uniqueness in <agencyCode>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional (values limited to: alternative, authorized)
Optional
Optional
Optional
Optional
Availability:
Example:
<agencyName>
Summary:
A child element of <maintenanceAgency> that provides the name of the
institution or service responsible for the creation, maintenance, and/or
dissemination of the EAC-CPF instance.
See also:
Use <agencyCode> to record a code representing the institution or
service responsible for the creation, maintenance, and/or dissemination of
the EAC-CPF instance.
May contain:
[text]
May occur within:
Description and Usage:
Use <agencyName> to record the name of the institution or service
responsible for the creation, maintenance, and/or dissemination of the EAC-CPF
instance. Examples include the repository name or the name of an aggregation
service.
<maintenanceAgency> must include one or both of <agencyName> and
<agencyCode>.
It is recommended to use the form of the agency name that is authorized by an
appropriate national or international agency or service.
<agencyName> may be repeated in order to provide the name of the
institution or service responsible for the EAC-CPF instance in multiple
languages. If <agencyName> is repeated it is recommended to indicate the
language of each name using languageOfElement.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<agent>
Summary:
A required child element of <maintenanceEvent> that provides the name of
a person, institution, or system responsible for a specific event in the
EAC-CPF instance's maintenance history, such as its creation, modification, or
deletion.
Attribute usage:
Use the required @agentType attribute to specify whether the
agent is "human", "machine", or "unknown".
May contain:
[text]
May occur within:
Description and Usage:
Use <agent> to indicate the person, institution, or system responsible
for a maintenance event. Examples include the name of the author or encoder,
the database responsible for creating the EAC-CPF instance, and the style sheet
used to update an instance to a new version of EAC-CPF.
Each <maintenanceEvent> element must have a child <agent>
element.
Attributes:
Required (values limited to: human, machine, unknown)
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<alternativeSet>
Summary:
A container for one or more authority records derived from one or more
authority systems, expressed within a single EAC-CPF instance.
See also:
<alternativeSet> should not be confused with <sources>,
wherein authority records are not intended to be displayed as alternative
versions.
May contain:
May occur within:
Description and Usage:
<alternativeSet> is a container element for one or more authority
records derived from one or more alternative systems. Authority record
aggregation may be used in cooperative or consortial contexts that gather
together records describing the same CPF entity in different languages, from
different rules, or from different contexts, when it is desirable to provide
users with alternative descriptions of the same entity. For example in the
context of the European Union, an international cooperative project may want to
provide users the option of storing descriptions in English, French, German,
Italian, Spanish, and in other European languages.
Alternative authority records are contained within the required
<setComponent> child elements. This approach allows different
descriptions of the same CPF entity to be contained within a single EAC-CPF
instance.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<biogHist>
Biography or History [toc]
Summary:
A concise essay and/or chronology that provides biographical or historical
information about the EAC-CPF entity.
May contain:
May occur within:
Description and Usage:
<biogHist> includes significant details about the life of an individual
or family, or the administrative history of a corporate body.
The <biogHist> element may contain text in a series of paragraphs
(<p>), and/or a chronology list (<chronList>) that matches
dates and date ranges with associated events and/or places. The
<abstract> element is intended to provide a very brief synopsis of
the full <biogHist> content that could be extracted for inclusion in a
remote source, such as a MARC record.
The optional <list> element is used to accommodate greater complexity in
expressing or representing the biography or history of the CPF entity. A
simpler discursive expression of the information may be encoded as one or more
<p> elements. The optional <head> element can be used to add a
title or caption to the text.
The prescribed order of all child elements (both required and optional) is:
<head>
<abstract>
One or more of <chronList>, <list>, or <p>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<chronItem>
Summary:
A required element within <chronList> that pairs a date with one or more
events and zero or more places within a chronology list.
Attribute usage:
Use @localType, if local use requires specification of the type
of chronological item.
May contain:
May occur within:
Description and Usage:
A required element within a chronology list, <chronItem> must contain
<date>, <dateRange>, or <dateSet> followed by an
<event> or <chronItemSet>. Use <dateRange> to record an
inclusive pair of dates or <dateSet> to record multiple dates or date
ranges.
An optional <place> element may be used alongside <event> to
detail a place that is relevant to the chronology item.
<chronItemSet> can be used to record multiple events or places within a
single <chronItem>.
The prescribed order of all child elements (both required and optional) is:
One of <date>, <dateRange>, or <dateSet>
Either <event> or <chronItemSet>
<place> (only when <event> is used)
<reference>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<chronItemSet>
Chronology Item Set [toc]
Summary:
An element for binding together one or more <event> elements and zero or
more <place> elements within <chronItem>.
May contain:
May occur within:
Description and Usage:
Use <chronItemSet> within <chronItem> when it is necessary to
associate multiple <event> elements and multiple <place>
elements. Possible combinations include multiple events, a single event
associated with multiple locations, multiple events associated with a single
location, or multiple events associated with multiple locations.
<chronItemSet> may be repeated within <chronItem> when
necessary to associate multiple instances of such combinations with the date or
dates recorded within <chronItem>.
The prescribed order of all child elements (both required and optional) is:
<event>
One or more of <place> or <reference>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<chronList>
Summary:
An optional child element of <biogHist> used to document a structured
chronological list of events, dates, and (optionally) places.
May contain:
May occur within:
Description and Usage:
<chronList> comprises 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-CPF instance. Such events are associated
with the date of occurrence and optionally with the name of a place.
Each <chronList> contains one or more <chronItem> elements, each
associating a <date>, <dateRange>, or <dateSet> with an
<event> and an optional <place>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<citedRange>
Summary:
An optional child element of <source> that identifies precisely where
supporting evidence was found within the source.
Attribute usage:
Use the optional @unit attribute to specify the format that the
<citedRange> refers to, for example page number or volume
number.
May contain:
[text]
May occur within:
Description and Usage:
The <citedRange> element can be used to refer to a specific location
within a source where supporting evidence can be found. It may refer to a
specific location such as a single page, or a broader location such as a range
of pages.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<componentEntry>
Summary:
A child element of <setComponent> that can be used to provide
identification and access to a linked resource.
May contain:
[text]
May occur within:
Description and Usage:
<componentEntry> is used within <setComponent> to provide a
textual note about the alternative authority record that is being bundled
together with others describing the same entity. The bundled alternative
records for a given EAC-CPF entity may be in different languages or come from
different authority systems. The bundling allows them to be transmitted or
stored together. The <componentEntry> element provides a place where a
particular alternative record can be described or explained in relation to the
other authority records.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<contact>
Summary:
An optional child element of <place> that binds together one or more
<contactLine> elements to encode contact details or digital
addresses.
See also:
Use <address> to encode a physical or analog address.
May contain:
May occur within:
Description and Usage:
<contact> is an optional wrapper element within <place> used to
encode digital addresses and contact information.
<contact> must include one or more <contactLine> element(s) that
provide relevant contact details for the entity being described.
One of <contact>, <placeName>, <placeRole>,
<geographicCoordinates>, or <address> is required within
<place>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<contactLine>
Summary:
A required child element of <contact> used for recording one line of
contact details or digital addresses.
Attribute usage:
Use one of the set values in the optional @contactLineType
attribute to encode the type of contact detail that the <contactLine>
refers to, for example "phoneNumber".
May contain:
[text]
May occur within:
Description and Usage:
<contactLine> is used to encode separate details or lines of contact
details or digital addresses within a parent <contact> element.
<contactLine> may be repeated as many times as necessary to enter all
relevant contact details.
Attributes:
Optional (values limited to: external, internal)
Optional (values limited to: email, fax, homepage, mobileNumber,
phoneNumber)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<control>
Summary:
A required child element of <eac> that contains information about the
creation, maintenance, status and the rules and authorities used in the
composition of the EAC-CPF instance.
Attribute usage:
Use the required @maintenanceStatus attribute to document the
current version status of the EAC-CPF instance.
Use the optional @publicationStatus attribute to record the
editorial status of the EAC-CPF instance.
May contain:
conventionDeclaration (0..n),
languageDeclaration (0..n),
localControl (0..n),
localTypeDeclaration (0..n),
maintenanceAgency (1..1),
maintenanceHistory (1..1),
otherRecordId (0..n),
recordId (1..1),
rightsDeclaration (0..n),
representation (0..n),
sources (0..1)
May occur within:
Description and Usage:
This required wrapper element within <eac> contains the information
necessary to manage the instance. This includes information about its creation,
maintenance and status as well as the languages, rules and authorities used in
the composition of the description.
It must contain a unique identifier for the instance within the
<recordId> element. Other associated identifiers may be given in
<otherRecordId>. There must be a description of the agency
responsible for its creation and maintenance in <maintenanceAgency> as
well as statements about its current drafting status in
maintenanceStatus and the creation, maintenance, and disposition
of the instance in <maintenanceHistory>.
There are optional elements available to declare languages, rules, conventions
and sources used in the EAC-CPF instance. Other control elements considered
necessary but not otherwise included may be given in the <localControl>
element. Similarly, local types for certain elements used throughout the
EAC-CPF instance are recommended to be defined in the
<localTypeDeclaration> element
The available child elements (both required and optional), in their prescribed
order, are:
<recordId> - Required. Contains the unique identifier for the
EAC-CPF instance.
<maintenanceAgency> - Required. Contains the name and coded
information about the institution or service responsible for the creation,
maintenance, and/or dissemination of the EAC-CPF instance.
<maintenanceHistory> - Required. Contains information about the
date, type and events within the life cycle of an EAC-CPF instance.
<sources> - Optional. Contains information about the sources
consulted in creating the description of the entity or entities in the
EAC-CPF instance.
The following elements may appear in any order after the above elements:
<conventionDeclaration> - Optional. Contains information on
the rules or conventions used to construct the EAC-CPF
instance.
<languageDeclaration> - Optional. Contains coded and natural
language information about the language or languages of the EAC-CPF
instance.
<localControl> - Optional. Contains any administrative
metadata necessary due to local practice that are not represented by
the other elements in <control>.
<localTypeDeclaration> - Optional. Contains information
about local conventions used in the @localType
attribute.
<otherRecordId> - Optional. An element that allows the
recording of additional identifiers that may be associated with the
EAC-CPF instance.
<representation> - Optional. Used for recording a link to a
transformed and deliverable version of the EAC-CPF instance.
<rightsDeclaration> - Optional. Contains information about
the usage rights of the EAC-CPF instance.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional (values limited to: iso3166-1, otherCountryEncoding)
Optional (values limited to: iso8601, otherDateEncoding)
Optional
Optional (values limited to: ietf-bcp-47, iso639-1, iso639-2b,
iso639-3, otherLanguageEncoding)
Optional
Required (values limited to: cancelled, deleted, deletedMerged,
deletedReplaced, deletedSplit, derived, new, revised)
Optional (values limited to: approved, inProcess, published)
Optional (values limited to: iso15511, otherRepositoryEncoding)
Optional (values limited to: iso15924, otherScriptEncoding)
Optional
Optional
Availability:
Example:
<conventionDeclaration>
Convention Declaration [toc]
Summary:
An optional child element of <control>, used to declare the rules or
conventions, including authorized controlled vocabularies and thesauri, applied
in creating the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<conventionDeclaration> is used for declaring references to any rules
and conventions, including authorized controlled vocabularies or thesauri,
applied in the construction of the description. The element binds together the
required <reference> element with optional <shortCode> and
<descriptiveNote> elements that identify rules or conventions applied
in compiling the EAC-CPF instance.
Each additional rule or set of rules, controlled vocabulary, or standard should
be contained in a separate <conventionDeclaration>.
<shortCode> may be used to identify the standard or controlled
vocabulary in a coded structure. Any notes relating to how these rules or
conventions have been used may be given within <descriptiveNote>.
It may not be necessary to include <conventionDeclaration> in such cases
where the above scenarios are addressed in local or consortial
documentation.
The prescribed order of all child elements (both required and optional) is:
<reference>
<shortCode>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<cpfDescription>
Summary:
A wrapper element that binds together the descriptive information of one CPF
identity.
Attribute usage:
Use the @id attribute to identify individual
<cpfDescription> elements when using the
<multipleIdentities> structure.
May contain:
May occur within:
Description and Usage:
<cpfDescription> contains the description of one identity.
The <cpfDescription> includes a required <identity> element
containing the entity type and authorized or alternative name entries. It also
includes the optional <description> and <relations> elements that
provide contextual information about the CPF entity being described, including
the relations to other corporate bodies, persons, families, resources, and
functions.
An optional <alternativeSet> element allows the incorporation of one or
more authority records derived from one or more authority systems.
The prescribed order of all child elements (both required and optional) is:
<identity>
<description>
<relations>
<alternativeSet>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <eac>: one of <cpfDescription> or
<multipleIdentities> required, not repeatable
Within <multipleIdentities>: two or more <cpfDescription>
required, repeatable
Example:
<date>
Summary:
The single date of an event in the history of the person, family, or corporate
body being described, or in their relationship to, e.g., a name entry, a place,
an occupation, another CPF entity, a resource, or a function.
Attribute usage:
Use @certainty to indicate the degree of precision in the
dating, for example, "uncertain" or "approximate".
Use @localType to supply a more specific characterization of
the date.
Use @notAfter and @notBefore to capture the latest
and earliest possible dates in machine-processable form in cases when the
date is uncertain.
Use @standardDate to provide a machine-processable form of the
date.
May contain:
[text]
May occur within:
chronItem,
dateSet,
existDates,
function,
legalStatus,
localControl,
localDescription,
mandate,
occupation,
otherEntityType,
place,
relation,
useDates
Description and Usage:
An element for expressing the single date of an event in the history of the
person, corporate body or family being described, or in their relationship to,
e.g., a name entry, a place, an occupation, another CPF entity, a resource, or a
function.
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
standardDate attribute, formulated according to ISO 8601.
If the event or relationship has inclusive dates use the <dateRange>
element, while more complex dates (combining singles dates and date ranges) can
be expressed in <dateSet>.
Dates of existence for the entity being described are encoded with the
<existDates> element, while the dates of use of a particular name of
an entity are encoded in <useDates>. The date and time of a maintenance
event in the history of the EAC-CPF instance are given in the
<eventDateTime> element.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <function>, <legalStatus>, <localDescription>,
<mandate>, <occupation>, <otherEntityType>,
<place>, <relation>: one of <date>, <dateRange>,
or <dateSet> optional, not repeatable
Within <chronItem>, <existDates> and <useDates>: one of
<date>, <dateRange>, or <dateSet> required, not
repeatable
Within <dateSet>: at least two of <date> and/or
<dateRange> required, repeatable
Within <localControl>: one of <date> or <dateRange>
optional, not repeatable
Example:
<dateRange>
Summary:
A wrapper element for binding together <fromDate> and <toDate> in
order to represent a range of dates. Either <fromDate> or
<toDate> must be present within a <dateRange>, but it is
recommended to use both child elements whenever possible.
Attribute usage:
Use @localType to supply a more specific characterization of
the date range.
May contain:
May occur within:
chronItem,
dateSet,
existDates,
function,
legalStatus,
localControl,
localDescription,
mandate,
occupation,
otherEntityType,
place,
relation,
useDates
Description and Usage:
An element that expresses inclusive dates of an event in the history of, or a
relationship with, the person, family, or corporate body being described in the
EAC-CPF instance.
<dateRange> contains <fromDate> and/or <toDate>, and
therefore may express a range of dates as a starting point with no end point, a
start and end point, or an end point with no starting point. Either
<fromDate> or <toDate> must be present within a
<dateRange>, but it is recommended to use both child elements
whenever possible.
The content of the children of <dateRange> is intended to be a
human-readable, natural language expression of the dates. If, however, indexing
or other machine processing of dates is desired, standardDate should
be used on the children of <dateRange> to record the date in
machine-processable form as well.
Dates of existence for the identity being described are encoded with the
<existDates> element, while the dates of use of a particular name of
an identity are encoded in <useDates>. The date and time of a
maintenance event in the history of the EAC-CPF instance are given in the
<eventDateTime> element.
The prescribed order of all child elements (both required and optional) is:
<fromDate>
<toDate>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <function>, <legalStatus>, <localDescription>,
<mandate>, <occupation>, <otherEntityType>,
<place>, <relation>: one of <date>, <dateRange>,
or <dateSet> optional, not repeatable
Within <chronItem>, <existDates> and <useDates>: one of
<date>, <dateRange>, or <dateSet> required, not
repeatable
Within <dateSet>: at least two of <date> and/or
<dateRange> required, repeatable
Within <localControl>: one of <date> or <dateRange>
optional, not repeatable
Example:
<dateSet>
Summary:
A wrapper element for encoding complex dates that cannot be adequately
represented in one <date> or <dateRange>.
May contain:
May occur within:
chronItem,
existDates,
function,
legalStatus,
localDescription,
mandate,
occupation,
otherEntityType,
place,
relation,
useDates
Description and Usage:
<dateSet> binds together single dates and date ranges, multiple single
dates, or multiple date ranges. <dateSet> is used in situations where
complex date information needs to be conveyed and requires at least two child
elements. These can be any combination of <date> and
<dateRange>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <function>, <legalStatus>, <localDescription>,
<mandate>, <occupation>, <otherEntityType>,
<place>, <relation>: one of <date>, <dateRange>,
or <dateSet> optional, not repeatable
Within <chronItem>, <existDates>, <useDates>: one of
<date>, <dateRange>, or <dateSet> required, not
repeatable
Example:
<description>
Summary:
An optional child element of <cpfDescription>, <description> is a
wrapper element for all of the content elements comprising descriptive
information about the CPF entity.
May contain:
biogHist (0..n),
existDates (0..n),
functions (0..1),
generalContext (0..n),
languagesUsed (0..1),
legalStatuses (0..1),
localDescriptions (0..1),
mandates (0..1),
occupations (0..1),
places (0..1),
structureOrGenealogy (0..n)
May occur within:
Description and Usage:
The child elements that constitute <description> together permit
descriptive information to be encoded in either structured or unstructured
fashions, or in a combined approach. <description> accommodates the
encoding of all the data elements that comprise the Description Area of ISAAR
(CPF) including historical, biographical, and genealogical information; legal
status and mandates; functions, occupations, and activities, and the dates and
places that further constrain those elements.
The prescribed order of all child elements (both required and optional) is:
<functions>
<languagesUsed>
<legalStatuses>
<localDescriptions>
<mandates>
<occupations>
<places>
Any of <biogHist>, <existDates>, <generalContext>,
and <structureOrGenealogy>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<descriptiveNote>
Summary:
An element used to provide general descriptive information related to its
parent element.
May contain:
May occur within:
conventionDeclaration,
existDates,
function,
functions,
identity,
languageDeclaration,
languageUsed,
languagesUsed,
legalStatus,
legalStatuses,
localDescription,
localDescriptions,
localTypeDeclaration,
maintenanceAgency,
mandate,
mandates,
occupation,
occupations,
otherEntityType,
otherEntityTypes,
place,
places,
relation,
relations,
rightsDeclaration,
setComponent,
source,
sources
Description and Usage:
<descriptiveNote> provides additional descriptive information about the
element in which it is contained. <descriptiveNote> must contain one or
more <p> elements.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<eac>
Encoded Archival Context - Corporate Bodies, Persons, and Families [toc]
Summary:
The required root element of an EAC-CPF instance.
May contain:
Description and Usage:
<eac> wraps all other elements in a particular instance of an archival
authority record encoded with the EAC-CPF XML Schema.
<eac> must contain <control> followed by either a
<cpfDescription> or a <multipleIdentities> element.
In order to validate an EAC-CPF instance, it is highly recommended to include
according information about the EAC-CPF namespace and the EAC-CPF schema
location.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Availability:
Example:
<entityType>
Summary:
A required child element of <identity> encoding the type of CPF entity
being described.
Attribute usage:
Use the required @value attribute with one of the values
"corporateBody", "family", or "person" to identify the type of
entity.
See also:
Use <otherEntityType> to encode additional or alternative entity
types, such as a translation or a specification of the default entity
types.
May contain:
[empty]
May occur within:
Description and Usage:
Within <identity> the required <entityType> element specifies the
type of CPF entity being described in the EAC-CPF instance as being a corporate
body, family or person.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Required (values limited to: corporateBody, family, person)
Availability:
Example:
<event>
Summary:
A child element of <chronItem> or <chronItemSet> that is used to
encode an event associated with a date, and optionally a place, within a
structured chronology.
May contain:
May occur within:
Description and Usage:
<event> contains discursive text identifying the event described by the
<chronItem> or <chronItemSet>. <chronItem> must include
one of either <event> or <chronItemSet>. <chronItemSet>
must include one or more <event> elements.
Every <event> must have date(s) (<date>, <dateRange>, or
<dateSet>) associated with it. It may also have optional
<place> element associated with it.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <chronItem>: One of <chronItemSet> or <event>
required, not repeatable.
Within <chronItemSet>: required, repeatable.
Example:
<eventDateTime>
Maintenance Event Date and Time [toc]
Summary:
A required child element of <maintenanceEvent> that records the date and
time of a specific maintenance action for an EAC-CPF instance.
Attribute usage:
Use @standardDateTime to provide a machine-processable
expression of the date or date and time, formulated according to the ISO
8601 standard.
May contain:
[text]
May occur within:
Description and Usage:
A required child element of <maintenanceEvent>, <eventDateTime>
is for recording the date and time that a maintenance event occurred. Examples
of maintenance events include the creation, update, revision, or other
modification to an EAC-CPF instance.
The date and time may be captured in natural language in the element. It is
highly recommended to provide at least a human-readable date in
<eventDateTime> directly or a machine-processable date in
standardDateTime, in case it is not possible to provide both.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<eventDescription>
Maintenance Event Description [toc]
Summary:
An optional child element of <maintenanceEvent> that provides the
description of a maintenance event in the life of the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A child element of <maintenanceEvent> used for describing the
maintenance event. The element allows a full description of the maintenance
event to be given alongside information about the maintenance agent, and the
type, time and date of the maintenance event.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Availability:
Example:
<existDates>
Summary:
An optional element within <description> used for encoding the dates of
existence of the CPF entity being described, such as dates of establishment and
dissolution for corporate bodies and dates of birth and death or floruit for
persons.
See also:
Do not confuse with <useDates>, which is a child element of
<nameEntry> or <nameEntrySet> and represents the dates of
use for a particular name or set of names.
May contain:
May occur within:
Description and Usage:
The dates of existence of the CPF entity being described, such as dates of
establishment and dissolution for corporate bodies and dates of birth and death
or floruit for persons.
<existDates> must contain one of <date>, <dateRange>, or
<dateSet>. These child elements may contain actual or approximate
dates. A <descriptiveNote> may be included if a fuller explanation of
the dates of existence is needed.
Use the <date> element to record the date of a single event, such as a
date of birth or date of incorporation. Use <dateRange> to encode a pair
of inclusive dates. Use <dateSet> to encode more complex date
expressions that intermix <date> and <dateRange> elements.
The prescribed order of all child elements (both required and optional) is:
One of <date>, <dateRange>, or <dateSet>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<fromDate>
Summary:
A child element of <dateRange> that records the starting point in a
range of dates.
Attribute usage:
Use @certainty to indicate the degree of precision in the
dating, for example, "uncertain" or "approximate".
Use @localType to supply a more specific characterization of
the start date.
Use @notAfter and @notBefore to capture the latest
and earliest possible dates in machine-processable form in cases when the
date is uncertain.
Use @standardDate to provide a machine-processable form of the
date.
Use @status with the value "unknown" to indicate where the
start of a date range is unknown.
See also:
Use <toDate> to record the ending point of a date range.
May contain:
[text]
May occur within:
Description and Usage:
Use <fromDate> to record the beginning date in a range of dates.
<fromDate> may contain actual, approximate or unknown dates. The
content of the element is intended to be a human-readable, natural language
expression of the date. If, however, indexing or other machine processing of
dates is desired, the standardDate should be used to record the date
in machine-processable form as well. If the <fromDate> is not known, it
may be omitted from <dateRange>, or the status attribute
used.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional (values limited to: unknown)
Optional
Optional
Availability:
Example:
<function>
Summary:
A required child element of <functions> that provides information about
a function, activity, role, or purpose performed by the CPF entity being
described.
See also:
Use <relation> with <targetEntity> having the
@targetType "function" when describing the relationship between
the function and the CPF entity being described in more detail.
May contain:
May occur within:
Description and Usage:
A <function> element is a wrapper element used to encode an index term,
using the required child element <term>. Terms are used to identify the
functions, processes, activities, tasks, or transactions performed by the CPF
entity. They may be drawn from controlled vocabularies or may be natural
language terms.
<function> must include at least one <term> element.
<term> can be repeated within <function> to include
translations of the same function. Use the languageOfElement
attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and
place(s) (<placeName>) may be included to further constrain the term's
meaning. A <descriptiveNote> may be included if a fuller textual
explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<functions>
Summary:
An optional child element of <description> used for grouping together
one or more <function> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <functions> element to group together one or more
occurrences of <function>. <functions> must include at least one
<function> element.
The prescribed order of all child elements (both required and optional) is:
<function>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<generalContext>
Summary:
An optional child element of <description> that encodes information
about the general social and cultural context of the CPF entity being
described.
May contain:
May occur within:
Description and Usage:
<generalContext> encodes information about the social, cultural,
economic, political, and/or historical context in which the CPF entity being
described existed. The general context provides wide latitude to record
contextual information not specifically accommodated by other elements
contained in <description>.
The optional <list> element may be used to accommodate greater
complexity in expressing or representing the general context being described.
The optional <head> element may be used to encode a title or caption. A
simpler discursive expression of the general context may be encoded as one or
more <p> elements.
The prescribed order of all child elements (both required and optional) is:
<head>
Any of <list> and <p>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<geographicCoordinates>
Geographic Coordinates [toc]
Summary:
An optional child element of <place> that encodes a set of geographic
coordinates.
Attribute usage:
Use the required @coordinateSystem attribute to provide a
commonly used code for the system used to express the coordinates. Examples
include WGS84, OSGB36, ED50.
May contain:
[text]
May occur within:
Description and Usage:
Use <geographicCoordinates> to express a set of geographic coordinates
such as latitude, longitude, and altitude representing a point, line, or area
on the surface of the earth.
It is recommended that the values included in <geographicCoordinates>
are based on a commonly used system for expressing geographic coordinates.
One of <geographicCoordinates>, <placeName>, <placeRole>,
<address>, or <contact> is required within <place>.
Attributes:
Optional (values limited to: external, internal)
Optional
Required
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<head>
Summary:
An element that encodes a title or caption for a section of text.
May contain:
May occur within:
Description and Usage:
<head> is used for supplying title-like statements to a section of text
or a list. When <head> is used, it must be the first child element,
followed by one or more other elements.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<identity>
Summary:
A required child element of <cpfDescription> used to encode the name or
names related to the identity being described within the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<identity> is a wrapper element used to group the elements necessary to
encode the name or names related to the identity of the CPF entity within the
<cpfDescription> element.
The required child element <entityType> specifies the type of entity
(i.e., corporate body, family, or person). The optional
<otherEntityTypes> element can be used to encode other entity types
used in the local context. An optional <identityId> is available for any
identifiers associated with the CPF entity.
One or more <nameEntry> elements and/or one or more
<nameEntrySet> elements must be included. All names by which the
identity being described within one <cpfDescription> element is known
are provided within <identity>. Each of the names, whether authorized or
alternatives, should be recorded in a separate <nameEntry> element.
<identity> may accommodate two or more parallel names in different
languages or scripts. In countries where there is more than one official
language, such as Canada or Switzerland, names of CPF entities are frequently
provided in more than one language. Within <identity>, a
<nameEntrySet> element should be used to group two or more
<nameEntry> elements that represent parallel forms of the name of the
CPF entity being described.
Within <identity>, a <descriptiveNote> element may be used to
record other information in a textual form that assists in the identification
of the CPF entity.
In case of multiple identities of the same entity in one EAC-CPF instance, a
separate <identity> element is contained in each of the
<cpfDescription> elements of the EAC-CPF instance.
The prescribed order of all child elements (both required and optional) is:
<entityType>
<nameEntry> and/or <nameEntrySet>
<otherEntityTypes>
<identityId>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional (values limited to: acquired, given)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<identityId>
Identity Identifier [toc]
Summary:
An optional child element of <identity> used to record any identifier
associated with the CPF entity being described.
See also:
Do not confuse with <recordId> within <control>, which
refers to an identifier for the EAC-CPF instance rather than the entity it
describes.
May contain:
[text]
May occur within:
Description and Usage:
<identityId> may be used to record any identifier associated with the
CPF entity being described in the EAC-CPF instance. Identifiers such as legal
identifiers, typically assigned by an authoritative agency, may be recorded in
this element.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<item>
Summary:
A child element of <list> that encodes the individual items in a
list.
See also:
Do not confuse with <chronItem>, which encodes entries within a
structured chronology, <chronList>.
May contain:
May occur within:
Description and Usage:
The <item> element is used for general lists within descriptive
elements.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<language>
Summary:
An optional child element of <languageUsed> that identifies a particular
language used in the creative work of the CPF entity being described.
Attribute usage:
Use @languageCode to provide a code for the language
itself.
Use @languageOfElement to provide a code for the language in
which the element is given.
May contain:
[text]
May occur within:
Description and Usage:
An optional element within <languageUsed> that gives the language or
languages used by the CPF entity being described.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<languageDeclaration>
Language Declaration [toc]
Summary:
An optional child element of <control> that indicates the language and
script in which an EAC-CPF instance is written.
Attribute usage:
Use the required @languageCode to provide a code for the
language used in the EAC-CPF instance.
Use @languageOfElement to provide a code for the language in
which the <languageDeclaration> element is given.
Use @scriptCode to provide a code for the writing system used
in the EAC-CPF instance.
Use @scriptOfElement to provide a code for the writing system
in which the <languageDeclaration> element is given.
May contain:
May occur within:
Description and Usage:
An optional child element of <control> that declares the languages and
scripts in which an EAC-CPF instance is written in the languageCode
and scriptCode attributes. Any comments about the languages and
scripts in which the EAC-CPF instance is written may be included in the
optional <descriptiveNote> element.
Attributes:
Optional (values limited to: external, internal)
Optional
Required
Optional
Optional
Optional
Optional
Availability:
Example:
<languageUsed>
Summary:
A required child element of <languagesUsed> describing the language and
writing system used by the CPF entity being described.
See also:
Do not confuse with <languageDeclaration> which refers to the
language and script of the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<languageUsed> is an element used to indicate the language and writing
system, or script, in which the CPF entity being described was creative or
productive. Use the <language> element to specify the language and a
corresponding <writingSystem> element for the writing system.
The prescribed order of all child elements (both required and optional) is:
<language> and/or <writingSystem>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<languagesUsed>
Summary:
An optional child element of <description> used for grouping together
one or more <languageUsed> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <languagesUsed> element to group together one or more
occurrences of <languageUsed>. <languagesUsed> must include at
least one <languageUsed> element.
The prescribed order of all child elements (both required and optional) is:
<languageUsed>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<legalStatus>
Summary:
A required child element of <legalStatuses> used to encode information
about the legal status of a corporate body.
May contain:
May occur within:
Description and Usage:
The legal status of a corporate body is typically defined and granted by
authorities or through authorized agencies. Enter terms in accordance with
provisions of the controlling legislation. Terms may be drawn from controlled
vocabularies or may be natural language terms.
<legalStatus> must include at least one <term> element, where the
legal status of the corporate body is encoded. <term> can be repeated
within <legalStatus> to include translations of the same term. Use the
languageOfElement attribute to identify the language used in each
<term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and
place(s) (<placeName>) may be included to further constrain the term's
meaning. A <descriptiveNote> element may be included if a fuller textual
explanation is needed.
Multiple <legalStatus> elements may be grouped within a
<legalStatuses> element.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<legalStatuses>
Summary:
An optional child element of <description> used to bundle together one
or more <legalStatus> element.
May contain:
May occur within:
Description and Usage:
<legalStatuses> groups together one or more occurrences of
<legalStatus>. <legalStatuses> must include at least one
<legalStatus> element.
The prescribed order of all child elements (both required and optional) is:
<legalStatus>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<list>
Summary:
A wrapper element used to encode a simple list consisting of one or more
<item> elements, or a complex list with one or more child
<list> elements.
Attribute usage:
Use @listType to identify and format the list as a particular
type. The choices are: "ordered," and "unordered."
See also:
Do not confuse with <chronList>, which encodes a structured
chronology.
May contain:
May occur within:
Description and Usage:
The <list> element is used for general lists that can be embedded with a
large number of descriptive elements.
To encode a simple list, include one or more <item> elements within
<list>. To encode more complex lists, such as hierarchies, additional
<list> elements can be included within <list>. <head>
can be used to encode a title or caption within a <list>.
The prescribed order of all child elements (both required and optional) is:
<head>
One or both of <list> and <item>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional (values limited to: ordered, unordered)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<localControl>
Summary:
An optional child element of <control>, used to specify any control
information necessary to accommodate local practice.
Attribute usage:
Use @localType if local practice requires recording the type of
entry.
May contain:
May occur within:
Description and Usage:
An element used to record and define any control information necessary to
accommodate local practice, in addition to the elements otherwise made
available within <control>.
The value of the entry must be given in a child <term> element and an
associated date or range of dates can be given as either <date> or
<dateRange>.
The prescribed order of all child elements (both required and optional) is:
<term>
<date> or <dateRange>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<localDescription>
Summary:
A required child element of <localDescriptions> used to extend the
descriptive categories to others available in a local system.
May contain:
May occur within:
Description and Usage:
<localDescription> provides a means to extend the list of description
elements specified in the EAC-CPF schema. It should be used to record
structured index terms rather than discursive text. The
<localDescription> element should be used whenever a separate
semantic process of the descriptive information is required in a local system
that cannot be accommodated by the existing categories available in
EAC-CPF.
<localDescription> must contain at least one <term> child
element. Terms may be drawn from controlled vocabularies or may be natural
language terms. Associated date(s) (<date>, <dateRange>, or
<dateSet>) and place(s) (<placeName>) may be included to
further constrain the term's meaning. A <descriptiveNote> may be
included if a fuller textual explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<localDescriptions>
Summary:
An optional child element of <description> used for grouping together
one or more <localDescription> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <localDescriptions> element to group together one or
more occurrences of <localDescription>. <localDescriptions> must
include at least one <localDescription> element.
The prescribed order of all child elements (both required and optional) is:
<localDescription>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<localTypeDeclaration>
Local Type Declaration [toc]
Summary:
An optional child element of <control> used to declare any local
conventions or controlled vocabularies used in localType in the
EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<localTypeDeclaration> specifies the local conventions and controlled
vocabularies used in localType attributes in the EAC-CPF
instance.
The child <reference> must be used to cite the resource that lists the
local rules or controlled terms. Any notes relating to how these rules or
conventions have been used may be given in <descriptiveNote>. The child
<shortCode> may be used to identify any abbreviation or code
representing the local convention or controlled vocabulary.
The prescribed order of all child elements (both required and optional) is:
<reference>
<shortCode>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<maintenanceAgency>
Summary:
A required child element of <control> that identifies the institution or
service responsible for the EAC-CPF instance.
Attribute usage:
Use @countryCode to indicate a unique code for the country of
the maintenance agency.
May contain:
May occur within:
Description and Usage:
<maintenanceAgency> encodes information about the institution or service
responsible for the creation, maintenance, and/or dissemination of the EAC-CPF
instance.
<maintenanceAgency> must include one or both of <agencyCode> or
<agencyName> to provide the name of the institution or service. It
may also include the optional child element <otherAgencyCode> to provide
any additional identifiers. Any general information about the institution in
relation to the EAC-CPF instance may be given in <descriptiveNote>.
The prescribed order of all child elements (both required and optional) is:
<agencyCode>
<agencyName>
<otherAgencyCode>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<maintenanceEvent>
Summary:
A required child element of <maintenanceHistory> used to record
information about maintenance activities in the history of the EAC-CPF
instance.
Attribute usage:
Use the required @maintenanceEventType to document the type of
maintenance activity that the <maintenanceEvent> is recording, using
one of the values from the available controlled list.
May contain:
May occur within:
Description and Usage:
A required child element of <maintenanceHistory>,
<maintenanceEvent> is used to record an activity in the creation and
ongoing maintenance of an EAC-CPF instance, including revisions, updates, and
deletions. There will always be at least one maintenance event for each
instance, which will typically be its creation.
<maintenanceEvent> must include <agent> and
<eventDateTime> child elements to record the agent that carried out
the maintenance event, and the date and time the maintenance event
occurred.
The prescribed order of all child elements (both required and optional) is:
<agent>
<eventDateTime>
<eventDescription>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Required (values limited to: cancelled, created, deleted, derived,
revised, unknown, updated)
Optional
Optional
Availability:
Example:
<maintenanceHistory>
Maintenance History [toc]
Summary:
A required child element of <control> that captures the history of the
creation and maintenance of the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A required child element of <control>, <maintenanceHistory> is
for recording the history of the creation, revisions, updates, and other
modifications to the EAC-CPF instance.
There must be at least one child <maintenanceEvent> in
<maintenanceHistory>, which usually will be a record of the creation
of the instance. There may be many other <maintenanceEvent> elements
documenting the milestone changes or activities in the maintenance of the
instance.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Availability:
Example:
<mandate>
Summary:
A required child element of <mandates> used for identifying the source
of authority or mandate for the corporate body in terms of its powers,
functions, responsibilities or activities, such as a law, directive, or
charter.
May contain:
May occur within:
Description and Usage:
<mandate> is used to identify 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.
<mandate> must include at least one <term> element. Terms may be
drawn from controlled vocabularies or may be natural language terms.
<term> can be repeated within <mandate> to include
translations of the same mandate. Use the languageOfElement
attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and
place(s) (<placeName>) may be included to further constrain the term's
meaning. A <descriptiveNote> may be included if a fuller textual
explanation is needed.
Multiple <mandate> elements may be grouped within a <mandates>
element.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<mandates>
Summary:
An optional child element of <description> used for grouping together
one or more <mandate> elements.
May contain:
May occur within:
Description and Usage:
<mandates> groups together one or more occurrences of <mandate>.
<mandates> must include at least one <mandate> element.
The prescribed order of all child elements (both required and optional) is:
<mandate>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<multipleIdentities>
Multiple Identities [toc]
Summary:
A child element of <eac> used to group together more than one
<cpfDescription> within a single EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A grouping element used to encode more than one <cpfDescription> in a
single EAC-CPF instance.
The use of the <multipleIdentities> element can resolve two identity
circumstances. Firstly, it can be used to represent more than one identity
(including official identities) of the same CPF entity, each with a separate
<cpfDescription>. Secondly, it can be used to represent a
collaborative identity that includes multiple individuals operating under a
shared identity (such as a shared pseudonym).
<multipleIdentities> must include two or more <cpfDescription>
elements.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Availability:
Within <eac>: one of <cpfDescription> or
<multipleIdentities> required, not repeatable
Example:
<nameEntry>
Summary:
An element containing a name entry for a corporate body, person, or family.
Attribute usage:
The @status attribute may be used to indicate whether the
<nameEntry> is an authorized or alternative form of the
name.
The @scriptOfElement and @languageOfElement
attributes can be used to specify the script and language of each name
recorded in <nameEntry>.
May contain:
May occur within:
Description and Usage:
Within <identity>, the element <nameEntry> is used to record a
name by which the corporate body, person, or family described in the EAC-CPF
instance is known.
When <nameEntry> occurs within <nameEntrySet> it is used to
record two or more parallel forms of a name, for example official forms of the
name in different languages and/or scripts.
Each form of the name is recorded in a separate <nameEntry> element.
Each <nameEntry> must contain at least one <part> element. Within
<nameEntry> each of the component parts of a name may be recorded in
a separate <part> element.
The <nameEntry> element may also contain a <useDates> element to
indicate the dates the name was used.
The prescribed order of all child elements (both required and optional) is:
<part>
<useDates>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional (values limited to: false, true)
Optional
Optional
Optional (values limited to: alternative, authorized)
Optional
Optional
Optional
Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet>
required, repeatable
Within <nameEntrySet>: two or more <nameEntry> required,
repeatable
Example:
<conventionDeclaration audience="external" id="cd1" localType="transliteration">
<abbreviation>DIN 32708:2014</abbreviation>
<citation href="https://www.iso.org/standard/9029.html">Information
and documentation - Romanization of Japanese</citation>
<descriptiveNote id="dn1">Angewendet werden nur die eigentlichen
Umschriftvorgaben, nicht aber die Regeln zur Wortbildungin der
lateinischen Umschrift. Diese erfolgt analog der Praxis von
NACSIS.</descriptiveNote>
</conventionDeclaration>
[...]
<nameEntrySet localType="parallel">
<nameEntry languageOfElement="de" scriptOfElement="Latn" preferredForm="true" status="authorized" localType="native">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
<nameEntry languageOfElement="ja" scriptOfElement="Jpan" preferredForm="false" status="authorized" conventionDeclarationReference="#cd1">
<part localType="surname">?????</part>
<part localType="firstname">??</part>
</nameEntry>
<nameEntry languageOfElement="en" scriptOfElement="Latn" preferredForm="false" status="authorized">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
<useDates>
<dateRange>
<fromDate standardDate="1906">1906</fromDate>
<toDate standardDate="1975">1975</toDate>
</dateRange>
</useDates>
</nameEntrySet>
<nameEntrySet>
Summary:
An optional child element of <identity> used as a wrapper element for
two or more <nameEntry> elements representing different forms of the
same name (e.g., official forms of the name in different languages and/or
scripts).
May contain:
May occur within:
Description and Usage:
A wrapper element used to group two or more <nameEntry> elements
representing parallel forms of the name for the same CPF entity which are used
at the same time (e.g., official forms of the name in different languages
and/or scripts).
The <nameEntrySet> element may contain a <useDates> element to
indicate the dates the set of name forms was used.
The prescribed order of all child elements (both required and optional) is:
<nameEntry>
<useDates>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet>
required, repeatable
Example:
<objectXMLWrap>
Summary:
An optional child element of <relation>, <setComponent>, and
<source> that allows for the inclusion of an XML element from any XML
namespace other than EAC-CPF.
May contain:
[any element from any namespace]
May occur within:
Description and Usage:
A wrapper element that provides a place to express data in any XML encoding
language.
To facilitate interoperability the XML should conform to an open, standard XML
schema and a namespace attribute should be present on the root element
referencing the namespace of the standard.
<objectXMLWrap> may be used to store related XML data locally rather
than linking to external resources in order to facilitate processing or in
cases where the related data may not be reliably accessible.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Availability:
Example:
<occupation>
Summary:
A required child element of <occupations> that provides information
about an occupation of the CPF entity being described.
May contain:
May occur within:
Description and Usage:
<occupation> is a wrapper element that uses the child element
<term> to identify an occupation held by the CPF entity. Terms may be
drawn from controlled vocabularies or may be natural language terms.
<occupation> must include at least one <term> element.
<term> can be repeated within <occupation> to include
translations of the same function. Use the languageOfElement
attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and
place(s) (<placeName>) may be included to further constrain the term's
meaning. A <descriptiveNote> element may be included if a textual
explanation needed.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<occupations>
Summary:
An optional child element of <description> used for grouping together
one or more <occupation> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <occupations> element to group together one or more
occurrences of <occupation>. <occupations> must include at least
one <occupation> element.
The prescribed order of all child elements (both required and optional) is:
<occupation>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<otherAgencyCode>
Summary:
An optional child element of <maintenanceAgency> that provides an
alternative code for the institution or service responsible for the EAC-CPF
instance.
Attribute usage:
Use @localType to specify the type of code being
provided.
Use @status to encode whether the <otherAgencyCode> is
an authorized or alternative code.
May contain:
[text]
May occur within:
Description and Usage:
Use <otherAgencyCode> to provide an alternative and/or local code that
represents the institution or service responsible for the creation,
maintenance, and/or dissemination of the EAC-CPF instance. Any code other than
that given in <agencyCode> may be provided in <otherAgencyCode>.
The addition of an ISO 3166-1 alpha-2 country code as the prefix to a local
code is recommended to ensure international uniqueness.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional (values limited to: alternative, authorized)
Optional
Optional
Optional
Optional
Availability:
Example:
<otherEntityType>
Summary:
A required and repeatable child element of <otherEntityTypes> used to
encode additional or alternative entity types.
May contain:
May occur within:
Description and Usage:
<otherEntityType> is a required child element of
<otherEntityTypes> used to encode any additional or alternative
entity types used for the CPF instance in addition to the required
<entityType> element with values of corporateBody, person, or family.
For example, in a local context "organization" might be used as an entity type
instead of "corporateBody". <otherEntityType> allows "organization" to
be encoded.
<otherEntityType> must include one <term> element containing the
term for the other entity type.
Each CPF instance may include more than one <otherEntityType> element
within the <otherEntityTypes> wrapper element.
The prescribed order of all child elements (both required and optional) is:
<term>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<otherEntityTypes>
Summary:
An optional child element of <identity> used for grouping one or more
<otherEntityType> elements.
May contain:
May occur within:
Description and Usage:
A wrapper element used to group one or more <otherEntityType> elements.
These elements are used to encode any additional or alternative entity types
used for the CPF instance in addition to the required <entityType>
element with values of corporateBody, person or family.
<otherEntityTypes> must include at least one <otherEntityType>
element.
<descriptiveNote> can be used to add any additional descriptive
information to the <otherEntityTypes>.
The prescribed order of all child elements (both required and optional) is:
<otherEntityType>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<otherRecordId>
Other Record Identifier [toc]
Summary:
An optional child element of <control> that encodes any local identifier
for the EAC-CPF instance.
Attribute usage:
Use @localType to identify the institution or service
responsible for providing the associated record identifier, if not the same
as that given in <maintenanceAgency>.
May contain:
[text]
May occur within:
Description and Usage:
<otherRecordId> can be used to record an identifier that is an
alternative to the mandatory identifier provided in <recordId>. These
might include the identifiers of merged EAC-CPF instances representing the same
CPF entity or those of records that are no longer current but had some part in
the history and maintenance of the EAC-CPF instance.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<p>
Summary:
A general purpose element used to encode blocks of text.
May contain:
May occur within:
Description and Usage:
Use <p> for blocks of text. A paragraph may be a subdivision of a larger
composition or it may exist alone. It is usually typographically distinguished:
A line space is often left blank before it; the text begins on a new line; and
the first letter of the first word may be indented, enlarged, or both.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <descriptiveNote>: required, repeatable.
Within all other parents: optional, repeatable.
Example:
<part>
Summary:
A required and repeatable child of <nameEntry> and <targetEntity>
used to distinguish components of the CPF entity's name, or the name of a
related entity.
Attribute usage:
The designation of the information contained in the <part> can be
specified by the attribute @localType.
May contain:
[text]
May occur within:
Description and Usage:
Within <nameEntry> each of the components of a name, such as forename,
surname or honorific title, may be recorded in a separate <part>
element. <part> may also contain the full name of the entity when it is
not possible to distinguish the different components of the name.
<part> cannot be empty and requires at least one non-whitespace
character, such as a hyphen, if no actual name can be given.
Within <targetEntity> the name or term for the related entity is encoded
within <part> elements.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<place>
Summary:
An element that provides information about a place or jurisdiction, including
places where the CPF entity was based, lived, or with which it had some other
significant connection.
May contain:
May occur within:
Description and Usage:
A <place> element is a wrapper element used to encode information about
a place or jurisdiction. This includes identifying the places or jurisdictions
where the CPF entity was based, lived, or with which it had some other
significant connection. It can also be used to encode address and contact
information.
<place> must include at least one of <address>, <contact>,
<geographicCoordinates>, <placeName> or
<placeRole>.
<placeName> may be used to encode the name of a place that is related to
the CPF entity described. The <placeRole> element is available to
specify the nature of the connection of the place with the CPF entity being
described, and its use is strongly recommended. Terms in <placeName> and
<placeRole> may be drawn from controlled vocabularies or may be
natural language terms. These controlled vocabularies can be identified with
the vocabularySource and vocabularySourceURI
attributes.
The <address> element is available for specifying a postal or other
address. The <contact> element is available for specifying a digital
address or other contact information.
Associated date or date range (<date>, <dateRange>, or
<dateSet>) information may be included to further constrain the
place's meaning. A <descriptiveNote> may be included if a fuller
explanation of the significance of the place to the CPF entity described is
needed.
The prescribed order of all child elements (both required and optional) is:
One or more of <address>, <contact>,
<geographicCoordinates>, <placeName>, and
<placeRole>
One of <date>, <dateRange>, or <dateSet>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <chronItem>: optional, not repeatable.
Within <chronItemSet>, <relation>: optional, repeatable.
Within <places>: required, repeatable.
Example:
<placeName>
Summary:
An optional child element of <place> used to encode the name of a place
or geographic feature that is related to the CPF entity described.
Attribute usage:
The @vocabularySource attribute may be used to indicate the
controlled vocabulary from which the <placeName> term is
derived.
May contain:
[text]
May occur within:
Description and Usage:
<placeName> should be identified by the proper noun that commonly
designates the place, natural feature, or political jurisdiction. It is
recommended that place names be taken from authorized vocabularies.
Within <place>, a companion <placeRole> is strongly recommended
to describe the nature of the association of the <placeName> to the
entity. Furthermore a companion <geographicCoordinates> is available
beside <placeName>, when used within <place>, to encode latitude,
longitude and altitude information.
One of <placeName>, <placeRole>, <geographicCoordinates>,
<address>, or <contact> is required within <place>.
The <placeName> element is repeatable. It is strongly recommended that
within <place>, the <placeName> element be repeated only to
represent the same place name in various languages, with an accompanying
languageOfElement attribute.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<placeRole>
Summary:
An optional child element of <place> used to identify the contextual
role the place or jurisdiction has in relation to the CPF entity described.
Attribute usage:
The @vocabularySource attribute may be used to indicate the
controlled vocabulary from which the <placeRole> is derived.
May contain:
[text]
May occur within:
Description and Usage:
<placeRole> provides a contextual role for a <placeName> within
<place>. Places should be identified in <placeName> by the
proper noun that commonly designates the place, natural feature, or political
jurisdiction. It is strongly recommended that each place name is accompanied by
a <placeRole> element in order to describe the nature of the association
of the place to the CPF entity.
One of <placeRole>, <placeName>, <geographicCoordinates>,
<address>, or <contact> is required within <place>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<places>
Summary:
An optional child element of <description> used for grouping together
one or more <place> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <places> element to group together one or more
occurrences of <place>. <places> must include at least one
<place> element. A <descriptiveNote> element may be included
if a fuller textual explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<place>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<recordId>
Summary:
A required child element of <control> that designates a unique
identifier for the EAC-CPF instance.
See also:
Use <agencyCode> in combination with <recordId> to provide
a globally unique identifier for the EAC-CPF instance.
May contain:
[text]
May occur within:
Description and Usage:
<recordId> is used for recording a unique identifier for the EAC-CPF
instance. The institution assigning the identifier ensures uniqueness of the
<recordId> value within the archival descriptions under its control.
A globally unique identifier may be constructed within <recordId>
according to various external protocols (i.e. HTTP URI, DOI, PURL, or UUID), or
in combination with <agencyCode>, which is an optional element within
<maintenanceAgency>.
<recordId> cannot be empty. Any alternative or additional record
identifiers may be recorded in <otherRecordId>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Availability:
Example:
<reference>
Summary:
An element that cites an external resource.
Attribute usage:
Use @href to link to the cited resource.
See also:
<reference> is used for external linking only. If any internal
linking is required within the EAC-CPF instance, use the @target
attribute.
May contain:
May occur within:
abstract,
chronItem,
chronItemSet,
conventionDeclaration,
event,
eventDescription,
item,
localTypeDeclaration,
p,
rightsDeclaration,
source
Description and Usage:
An element used for referencing external resources that have been used to
compile the EAC-CPF instance, that provide additional context to the EAC-CPF
instance, or that identify rules or conventions that have been applied.
<reference> is a required child element of
<conventionDeclaration>, <localTypeDeclaration>, and
<rightsDeclaration> for identifying any rules and conventions applied
in the compilation of the description. It is also a required child element of
<source>, used to identify any sources used in compiling the
description. <source> may include multiple child <reference>
elements.
<reference> is an optional child element of <abstract>,
<chronItem>, <chronItemSet>, <event>,
<eventDescription>, <item>, and <p> where it is used to
reference any external resources that provide additional context to the content
of that element.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Within <conventionDeclaration>, <localTypeDeclaration>,
<rightsDeclaration>: required, not repeatable
Within <source>: required, repeatable
Within <abstract>, <chronItem>, <chronItemSet>,
<event>, <eventDescription>, <item>, <p>:
optional, repeatable
Example:
<relation>
Summary:
A required child element of <relations> for describing a relationship
between the entity described in the EAC-CPF instance and a related entity.
May contain:
May occur within:
Description and Usage:
<relation> records descriptive information about a relationship between
the entity being described and a related entity, such as: a corporate body,
person, or family; a function; or an archival, bibliographic, or other
resource.
Use the required child element <targetEntity> to provide a textual
identification of the related entity, such as a name or a title. Use the
optional child element <relationType> to specify the type of relation.
Use the optional child element <targetRole> to specify the role of the
related entity. It is recommended that the terms used in <relationType>,
<targetEntity>, and <targetRole> be taken from an authorized
vocabulary.
Use <objectXMLWrap> to embed XML documenting the related entity from any
namespace. Use <date>, <dateRange>, or <dateSet> for
specifying the time period of the relationship and <place> for relevant
location information. <descriptiveNote> may be included for more
detailed specifications or explanations of the relationship.
The prescribed order of all child elements (both required and optional) is:
<targetEntity>
One of <date>, <dateRange>, or <dateSet>
One or more of <place>, <relationType>, and
<targetRole>
<descriptiveNote>
<objectXMLWrap>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<relations>
Summary:
An optional child element of <cpfDescription> that groups one or more
<relation> elements, which identify external entities and
characterize the nature of their relationships to the entity being
described.
May contain:
May occur within:
Description and Usage:
A wrapper element that groups together one or more <relation> elements,
each of which encodes a specific relationship.
The prescribed order of all child elements (both required and optional) is:
<relation>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<relationType>
Summary:
A child element of <relation> used to specify the type of relation that the entity being described within the EAC-CPF
instance has to the <targetEntity>.
May contain:
[text]
May occur within:
Description and Usage:
Use <relationType> within <relation> to specify the type of
relation that the entity being described has to the <targetEntity>.
The <relationType> element contains a textual description of the
relation. It is recommended that values used in <relationType> be taken
from an authorized vocabulary.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<representation>
Summary:
An optional child element of <control> for recording a link to a
deliverable version of the EAC-CPF instance or to the XML version of the
EAC-CPF instance itself.
Attribute usage:
Use @href to specify a link to a deliverable version of the
EAC-CPF instance.
Use @localType to differentiate between multiple
<representation> elements.
See also:
Use <otherRecordId> to provide any local identifier for the
EAC-CPF instance that does not link to a deliverable version.
May contain:
[text]
May occur within:
Description and Usage:
Use <representation> to record a link to a deliverable version of an
EAC-CPF instance, for example an HTML or PDF version, or to the XML version of
the EAC-CPF instance itself.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<rightsDeclaration>
Summary:
An optional child element of <control> that indicates a standard rights
statement associated with the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
Use <rightsDeclaration> to provide structured information about the
usage rights of the EAC-CPF instance. <rightsDeclaration> should only be
used to reference shared published licenses, such as Creative Commons,
RightsStatements.org, and published locally-defined licenses.
<reference> must be used to provide a machine-readable reference to a
license statement (for example, a dereferenceable URI). It may also be used to
encode the name of the license statement.
<shortCode> may be used to provide the abbreviated name for the rights
statement. The value of <shortCode> should align with the rights
statement referenced by <reference> and <descriptiveNote>.
<descriptiveNote> may be used to provide a human-readable description of
the license statement.
The prescribed order of all child elements (both required and optional) is:
<reference>
<shortCode>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<setComponent>
Summary:
A required child element of <alternativeSet> that allows an alternative
authority record of the EAC-CPF instance being described to be referenced and
described, as well as allowing the inclusion of the entire encoding of such
alternative authority record in any XML format.
Attribute usage:
Use @href to provide a general reference to alternative
sets.
May contain:
May occur within:
Description and Usage:
<setComponent> provides a wrapper to link to, describe, or contain one
or more alternative authority record, so that multiple records for the same
entity from separate authority systems, or in different languages, may be
combined together within a single EAC-CPF instance.
The <componentEntry> child element allows for the provision of a name or
title for the alternative authority record and the inclusion of a link to the
record in an external system, if using a vocabulary or similar..
Use the optional <descriptiveNote> for a textual note providing further
information about the record referenced in <setComponent>.
Use the optional <objectXMLWrap> child element when including the entire
authority record within the EAC-CPF instance.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<shortCode>
Summary:
An optional element for encoding the shortened form of a word or phrase.
May contain:
[text]
May occur within:
Description and Usage:
Used to record the shortened form of a word or phrase, for example, an
acronym.
Use <shortCode> within <conventionDeclaration> or
<localTypeDeclaration> to identify the code for a thesaurus,
controlled vocabulary, or another standard used in creating the EAC-CPF
description. Use within <rightsDeclaration> to provide an abbreviated
name for the rights statement.
To improve interoperability, it is recommended that the value be selected from
an authorized list of codes such as the MARC Code List
(http://www.loc.gov/marc/sourcelist/).
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Availability:
Example:
<source>
Summary:
A required child element of <sources> used to identify a particular
source of evidence used for the establishment of the description of the CPF
entity in the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
Use <source> to cite a published resource used in describing the CPF
entity. Use the required child element <reference>to include a textual
identification of the reference. In the case of online sources, use
href with <reference> to provide a URI.
Use the optional child element <citedRange> to point to a specific
location within a source.
Use the optional <descriptiveNote> for any additional notes about the
source. Use the optional <objectXMLWrap> to embed XML documenting the
source from any namespace.
The prescribed order of all child elements (both required and optional) is:
<reference>
<citedRange>
<descriptiveNote>
<objectXMLWrap>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<sources>
Summary:
An optional child element of <control> that groups one or more
<source>s of evidence used in the description of the CPF entity in
the EAC-CPF instance.
Attribute usage:
Use @base to specify a URI (other than the base URI of the
EAC-CPF instance) to be used for resolving relative URIs within
<sources> or descendant elements.
May contain:
May occur within:
Description and Usage:
Use <sources> to bind together one or more <source> elements.
<sources> must include at least one <source> element.
The prescribed order of all child elements (both required and optional) is:
<source>
<descriptiveNote>
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<span>
Summary:
Specifies the beginning and the end of a span of text.
Attribute usage:
Use the optional @style attribute to affect an arbitrary
stylistic difference.
Use the optional @localType attribute to identify qualities of
words or phrases.
May contain:
[text]
May occur within:
Description and Usage:
<span> is an optional formatting element for distinguishing words or
phrases that are intentionally stressed or emphasized for linguistic effect or
identifying some qualities of the words or phrases.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<structureOrGenealogy>
Structure or Genealogy [toc]
Summary:
An optional child element of <description> used to describe internal
administrative structure(s) of a corporate body or the genealogy of a
family.
May contain:
May occur within:
Description and Usage:
<structureOrGenealogy> encodes information expressing the internal
administrative structure(s) of a corporate body and the dates of any changes to
that structure that are significant to understanding the way that corporate
body conducted affairs (such as dated organization charts), or the genealogy of
a family (such as a family tree) in a way that demonstrates the
interrelationships of its members with relevant dates.
The optional <list> element may be used to accommodate greater
complexity in expressing or representing the structure(s) or genealogy being
described. <head> may be used to encode a title or caption. A simpler
discursive expression of the structure(s) or genealogy may be encoded as one or
more <p> elements.
The prescribed order of all child elements (both required and optional) is:
<head>
One or both of <list> or <p>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<targetEntity>
Summary:
A required child element of <relation> used to identify the entity that
is being targeted by the relation.
Attribute usage:
Use the required @targetType, to identity the type of entity
related to in <targetEntity>, using one of the following values:
"agent", "corporateBody", "family", "function", "person", or
"resource".
May contain:
May occur within:
Description and Usage:
<targetEntity> is used within <relation> to identify an entity
that is related to the subject of the EAC-CPF instance.
<targetEntity> must include at least one <part> element, encoding
the name or term for the related entity.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (values limited to: agent, corporateBody, family, function,
person, resource)
Optional
Optional
Optional
Availability:
Example:
<targetRole>
Summary:
An optional child element of <relation> used to specify the role of a
related entity towards the CPF entity being described.
May contain:
[text]
May occur within:
Description and Usage:
<targetRole> is used with <relation> to specify the role of a
related entity towards the CPF entity being described.
The <targetRole> element contains a textual description of the relation.
It is recommended that the terms in <targetRole> be taken from
authorized vocabularies.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<term>
Summary:
An element used to specify a descriptive term in accordance with authorized
vocabularies or local rules.
May contain:
[text]
May occur within:
Description and Usage:
<term> is a required child element of <function>,
<legalStatus>, <localControl>, <localDescription>,
<mandate>, <occupation>, and <otherEntityType>, used to
specify a descriptive term in accordance with authorized vocabularies or local
rules.
<term> can be repeated within its parent element to include translations
of the same term. Use the languageOfElement attribute to identify
the language used in each <term> grouped within a single parent
element.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<toDate>
Summary:
A child element of <dateRange> that records the end point in a range of
dates.
Attribute usage:
Use @certainty to indicate the degree of precision in the
dating, for example, "uncertain" or "approximate".
Use @localType to supply a more specific characterization of
the start date.
Use @notAfter and @notBefore to capture the latest
and earliest possible dates in machine-processable form in cases when the
date is uncertain.
Use @standardDate to provide a machine-processable form of the
date.
Use @status with the values "unknown" or "ongoing" to indicate
where part of a date range is unknown, or the date range is ongoing.
See also:
Use <fromDate> to record the starting point of a date
range.
May contain:
[text]
May occur within:
Description and Usage:
Use <toDate> to record the end date in a range of dates, whether they be
known, approximate or unknown. The content of the element is intended to be a
human-readable, natural language expression of the date. If, however, indexing
or other machine processing of dates is desired, the standardDate
should be used to record the date in machine-processable form as well.
<toDate> may be omitted from <dateRange>, or the
status attribute used, if the date span is ongoing or the
<toDate> is unknown.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional (values limited to: ongoing, unknown)
Optional
Optional
Availability:
Example:
<useDates>
Summary:
An optional child element of <nameEntry> and <nameEntrySet> that
provides the dates when the name or names were used for or by the CPF entity
being described.
May contain:
May occur within:
Description and Usage:
Within <nameEntry>, <useDates> provides the dates during which
the name was used for or by the CPF entity. For parallel names (e.g., official
forms of the name in different languages and/or scripts), <useDates> may
occur in <nameEntrySet> rather than in the individual <nameEntry>
elements contained in <nameEntrySet>.
<useDates> must include one of <date>, <dateRange>, or
<dateSet>.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
<writingSystem>
Summary:
An optional child element of <languageUsed> that identifies the writing
script for a language in which the CPF entity being described was creative or
productive.
Attribute usage:
Use @scriptCode to provide a code for the writing system
itself.
Use @scriptOfElement to provide a code for the writing system
in which the element is given.
May contain:
[text]
May occur within:
Description and Usage:
An optional element within <languageUsed> that gives the main script
used by the CPF entity being described in his/her creative or productive
work.
Attributes:
Optional (values limited to: external, internal)
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Availability:
Example:
[toc]