Elements
<abbreviation>
Summary: The <abbreviation> element is used to provide authorized codes for
thesauri, controlled vocabularies, and standards used in the construction of the EAC-CPF
instance.
Description
The <abbreviation> element is used to provide authorized codes for thesauri,
controlled vocabularies, and standards used in the construction of the EAC-CPF instance.
Values should be derived from an authorized list of codes such as the MARC Code List.
May contain:
[token]
May occur within:
conventionDeclaration, localTypeDeclaration
Attributes:
None
Occurrence:
0...1
<abstract>
Summary: An element that encodes a brief summary of the information contained within
the <biogHist> as a whole.
Description
The <abstract> is a 1-2 sentence synopsis of the identity’s biography or history
that is often extracted from the longer descriptions found in <biogHist>. Its
purpose is to help readers quickly identify the entity 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.
May contain:
[text], span
May occur within:
biogHist
Attributes:
Optional
Occurrence:
0…∞
<activities>
Summary: An optional grouping element that encodes information about one or more
activities performed by the entity being described.
Description
<activities> is a grouping element to record one or more <activity>
elements. Use the optional <activities> to group together one or more occurrences
of <activity> so that they can be manipulated as a package. A single
<activity> may stand alone or may be wrapped within <activities>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the activities being
described. A simpler narrative expression of the activities may be encoded as one or more
<p> elements.
May contain:
activity, citation, descriptiveNote, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.5
Occurrence:
0...∞
<activity>
Summary: An element that encodes information about an activity performed by the
entity being described.
Description
An <activity> element is used to encode an index term, along with a corresponding
@localType attribute to identify the terminology source. Terms are used to
identify the activities that define or are otherwise significant to the EAC-CPF entity. They
may be drawn from controlled vocabularies or may be natural language terms. An associated
date or date range(s) and place(s) may be included to define the activity more precisely. A
<descriptiveNote> may be included if a fuller explanation of an activity is
needed.
An activity reflects anything a corporate body, person, or family engaged in or performed.
Activities may also be reflected in the narrative text that comprises the
<biogHist> (ISAAR (CPF) History 5.2.2). However, the <activity> element
should be used whenever separate semantic processing of this information may be
required.
A single <activity> element may appear alone within <description>.
Alternatively, multiple <activity> elements may be grouped within an
<activities> wrapper that facilities manipulating them as a group.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
activities, description
Attributes:
Optional
References:
ISAAR 5.2.5
Occurrence:
0...∞
<agencyCode>
Summary: The code that represents the institution or service responsible for the
creation, maintenance and/or dissemination of the EAC-CPF instance.
Description
An element of <maintenanceAgency> within <control> providing a code
representing the institution or service responsible for the creation, maintenance and/or
dissemination of the EAC-CPF instance. The name of the agency is given in
<agencyName>. This is used in combination with the content of the required
<recordId> to provide a globally unique identifier for the instance.
The format of the code is constrained to that of the International Standard Identifier for
Libraries and Related Organizations (ISIL: ISO 15511): a prefix, a dash, and an identifier.
The code is alphanumeric (A-Z, 0-9, solidus, hyphen-minus, and colon only) 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). Otherwise local institution codes may be given with the ISO 3166-1
alpha-2 country code as the prefix to ensure international uniqueness.
<maintenanceAgency> must contain either an <agencyCode> or an
<agencyName> element. It may also contain both, which is recommended.
May contain:
[text]
May occur within:
maintenanceAgency
Attributes:
None
References:
ISAAR 5.4.2
Occurrence:
1
<agencyName>
Summary: The name of the institution or service responsible for the creation,
maintenance, and/or dissemination of the EAC-CPF instance.
Description
An element of <maintenanceAgency> within <control> that provides the
name of the institution or service responsible for the creation, maintenance and/or
dissemination of the EAC-CPF instance.
It is recommended that one uses the form of the agency name that is authorized by an
appropriate national or international agency or service.
<maintenanceAgency> must contain either an <agencyCode> or an
<agencyName> element. It may also contain both, which is recommended.
May contain:
[text]
May occur within:
maintenanceAgency
Attributes:
None
References:
ISAAR 5.4.2
Occurrence:
1
<agent>
Summary: The agent (human or machine) responsible for an event in the maintenance of
the EAC instance.
Description
For each maintenance event described in a <maintenanceEvent> element, the name of
the agent responsible for the maintenance event must be given. This might be a person or
institution in which case the <agentType> should be set as "human," or the name of
a system, in which case set the <agentType> to "machine."
It is recommended that one uses the form of the agency name that is authorized by an
appropriate national or international agency or service.
May contain:
[text]
May occur within:
maintenanceEvent
Attributes:
None
References:
ISAAR 5.4.9
Occurrence:
1
<agentType>
Summary: The type of agent responsible for a maintenance event of the EAC-CPF
instance.
Description
For each maintenance event described in a <maintenanceEvent> element, the type of
agent given in the <agent> element must be given as either "human" or
"machine."
May contain:
"human" or "machine"
May occur within:
maintenanceEvent
Attributes:
None
References:
ISAAR 5.4.9
Occurrence:
1
<alternativeSet>
Summary: A container element for two or more authority records derived from two or
more authority systems, expressed within a single EAC-CPF instance.
Description
Alternative Set is a container element for two or more authority records derived from two
or more authority systems. Alternative authority records are contained with
<alternativeSet> in <setComponent> elements. This device allows different
descriptions of the same entity to be contained within a single EAC-CPF instance.
Authority record aggregation may be used in cooperative or consortial contexts that gather
together records describing the same entity in different languages, or from different rules
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 descriptions in Italian, French, German, English, Spanish,
and in other European languages.
<alternativeSet> should not be confused with <sources>, wherein authority
records referenced are not intended to be displayed as alternative versions.
May contain:
setComponent
May occur within:
cpfDescription
Attributes:
None
Occurrence:
0...1
<biogHist>
Biographical or Historical Note [toc]
Summary: A concise essay and/or chronology that provides biographical or historical
information about the EAC-CPF entity.
Description
The <biogHist> includes significant details about the life of an individual or
family, or the administrative history of a corporate body. The <biogHist> may
contain just text in a series of Paragraphs <p>, and/or a Chronology List
<chronList> that matches dates and date ranges with associated events 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 <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the biography or
history being described. A simpler narrative expression of the information may be encoded as
one or more <p> elements.
May contain:
abstract, chronList, citation, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.2
Occurrence:
0...∞
<chronItem>
Summary: A container element that keeps a date or a date range paired with an
associated event and an optional place within a Chronology List <chronList>.
Description
Each <chronItem> contains a <date> (a single date) or a
<dateRange> (an inclusive date span) coupled with an <event>. A
<place> element is optionally available to ground the event in a particular
location.
May contain:
date, dateRange, event, place
May occur within:
chronList
Attributes:
Optional
References:
ISAAR 5.2.2
Occurrence:
1...∞
<chronList>
Summary: A structured chronological list of events, dates, and (optionally) places
that may be used within the <biogHist> element.
Description
Chronology list 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 a series of <chronItem>
elements, each associating a <date> or <dateRange> with an
<event> and an optional <place>.
May contain:
chronItem
May occur within:
biogHist
Attributes:
Optional
References:
ISAAR 5.2.2
Occurrence:
0...∞
<citation>
Summary: A linking element that cites an external resource.
Description
<citation> is a generic linking element that cites an external resource in machine
and / or human readable form. In most contexts it is optional, but at least one
<citation> must be given within <conventionDeclaration> in
<control>. Provide the formal title or name of the resource, making use of the
<span> element to indicate any formatting (such as italic or bold etc) thought
necessary. The user experience can be controlled by use of the available XML Linking
Language (Xlink) attributes for which consult the specification at
http://www.w3.org/TR/xlink/.
The <citation> element is available within a number of elements wherein there may
be a need to provide an external link to a resource that supports or explains information in
the parent element. These might include references to enabling documents, statutes,
published works, genealogical charts, and other such supporting resources.
May contain:
[text], span
May occur within:
activity, biogHist, conventionDeclaration, descriptiveEntry, function,
legalStatus, localTypeDeclaration, mandate, occupation, placeDate
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
Occurrence:
0...∞ or 1...∞
<componentEntry>
Summary: A descriptive element for a component within a set.
Description
A descriptive element for components within a set that provides narrative text identifying
an instance that constructs the alternative set.
May contain:
[text], span
May occur within:
setComponent
Attributes:
Optional
Optional
Optional
Occurrence:
1...∞
<control>
Summary: The area of the instance that contains control information about its
identity, creation, maintenance, status, and the rules and authorities used in the
composition of the description.
Description
This required wrapper element within <eac-cpf> contains the information necessary
to control the instance. This includes information about its identity, creation,
maintenance, and status as well 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 and 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>. It must also include a <languageDeclaration>
element providing information on the language and script used as well as the
<sources> element to provide information about the documentary sources used in the
composition of the description.
Optionally, <control> may also contain a <conventionDeclaration> element
providing information on authorities or controlled vocabularies used and on content or
descriptive rules used. Other control elements considered necessary but not otherwise
included may be given in <localControlEntry>.
May contain:
conventionDeclaration, languageDeclaration,localControlEntry,
localTypeDeclaration, maintenanceAgency, maintenanceHistory, maintenanceStatus,
otherRecordId, recordId, sources
May occur within:
eac-cpf
Attributes:
None
References:
ISAAR 5.4
Occurrence:
1
<conventionDeclaration>
Convention Declaration [toc]
Summary: A declaration of the rules or conventions, including authorized controlled
vocabularies and thesauri, applied in creating the EAC-CPF instance.
Description
An optional element of <control> for declaring references in the
<citation> element to any rules and conventions, including authorized controlled
vocabularies or thesauri, applied in the construction of the description. Any notes relating
to how rules or conventions have been used may be given within a <descriptiveNote>
element. The <abbreviation> element may be used to identify the standard or
controlled vocabulary in a coded structure.
May contain:
abbreviation, citation, descriptiveNote
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.3
Occurrence:
0...∞
<cpfDescription>
Corporate Body, Person, or Family Description [toc]
Summary: The broad area of the instance that describes the history or biography,
roles, context, activities, and functions of the entity being described.
Description
This required wrapper element, which contains the bulk of the EAC-CPF instance, describes
the identity and context of the entity being described. The <cpfDescription>
includes a required <identity> element containing authorized and parallel name
forms and optional <description> and <relations> sections to provide
contextual information for the entity being described.
An optional <alternativeSet> element allows the incorporation of two or more
authority records derived from two or more authority systems. The @id attribute
allows individual <cpfDescription> elements to be individually identified.
May contain:
alternativeSet, description, identity, relations
May occur within:
eac-cpf, multipleIdentities
Attributes:
Optional
References:
ISAAR 5.1, 5.2, 5.3
Occurrence:
1...∞
<cpfRelation>
Corporate Body, Person, or Family Relation [toc]
Summary: A corporate body, person, or family related to the described entity.
Description
The <cpfRelation> element contains the description of a corporate body, person,
or family related to the described entity. Such related entities are typically described in
another EAC-CPF instance or other encoding language such as MARC. Use the
<objectXMLWrap> to incorporate XML elements from any XML namespace or
<objectBinWrap> for base64-encoded binary data. A <relationEntry> element
is provided for textual identification of the related entity.
Use the <date>, <dateRange>, or <dateSet> elements for
specifying the time period during which the relationship applied and the <place>
element for recording relevant locative information. A <descriptiveNote> element
may be included for a more detailed specifications or explanations of the relationship.
The @cpfRelationType attribute may be used to specify the nature of the
<cpfRelation> entity’s relationship to the entity described in the
<eac-cpf> instance. Values are chosen from a closed list.
May contain:
date, dateRange, dateSet, descriptiveNote, objectXMLWrap, place,
objectBinWrap, relationEntry
May occur within:
relations
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
References:
ISAAR 5.3
Occurrence:
0...∞
<date>
Summary: The single date of an event in the history of, or a relationship with, the
person, family, or corporate body being described in the EAC-CPF instance.
Description
A generic element expressing the single date of an event in the history of, or a
relationship with, the person, family, or corporate body being described in the EAC-CPF
instance. 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>.
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. Other attributes include @notBefore and
@notAfter for dates of uncertainty. The @localType attribute can be
used to supply a more specific characterization of the date.
Dates of existence for the entity being described in the EAC-CPF instance are instead
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.
May contain:
[text]
May occur within:
activity, chronItem, cpfRelation, dateSet, descriptiveEntry, existDates,
function, functionRelation, legalStatus, localControlEntry, mandate, occupation, placeDate,
resourceRelation, useDates
Attributes:
Optional
Optional
Optional
Optional
Occurrence:
0...∞
<dateRange>
Summary: The date range of an event in the history of, or a relationship with, the
person, family, or corporate body being described in the EAC-CPF instance.
Description
A generic 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 mandatory <fromDate> and <toDate>
child elements. If the event or relationship has a single date use the <date>
element, while more complex dates (combining singles dates and date ranges) can be expressed
in <dateSet>.
The @localType attribute can be used to supply a more specific characterization
of the date.
Dates of existence for the identity being described in the EAC-CPF instance are instead
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.
May contain:
fromDate, toDate
May occur within:
activity, chronItem, cpfRelation, dateSet, descriptiveEntry, existDates,
function, functionRelation, legalStatus, localControlEntry, mandate, occupation, placeDate,
resourceRelation, useDates
Attributes:
Optional
References:
ISAAR 5.3.4, 5.2.2-5.2.6
Occurrence:
0...∞
<dateSet>
Summary: A grouping element that facilitates complex date expressions by being able
to combine a set comprising single dates and date ranges, multiple single dates, or multiple
date ranges.
Description
A grouping element to combine single dates and date ranges, multiple single dates, or
multiple date ranges. The <dateSet> element is used in situations where complex
date information needs to be conveyed. It requires at least two elements. These can be a
combination of <date> and <dateRange> elements.
May contain:
date, dateRange
May occur within:
activity, cpfRelation, descriptiveEntry, existDates, function,
functionRelation, legalStatus, mandate, occupation, placeDate, resourceRelation,
useDates
Attributes:
Optional
References:
ISAAR 5.1, 5.2, 5.3
Occurrence:
0...∞
<description>
Summary: A wrapper for all of the content elements comprising description (as
specified in the ISAAR (CPF) Description Area) of the entity described in the EAC-CPF
instance.
Description
The elements that constitute <description> together permit descriptive
information to be encoded in either structured or unstructured fashions, or in a combined
approach. <description> accommodates encoding all of 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.
May contain:
activities, activity, biogHist, descriptiveEntries, descriptiveEntry,
existDates, function, functions, generalContext, legalStatus, legalStatuses, mandate,
mandates, occupation, occupations, placeDate, placeDates, structureOrGenealogy
May occur within:
cpfDescription
Attributes:
None
References:
ISAAR 5.2
Occurrence:
0...1
<descriptiveEntries>
Descriptive Entries [toc]
Summary: A grouping element for one or more <descriptiveEntry>
elements.
Description
A grouping element for one or more <descriptiveEntry> elements. Use the optional
<descriptiveEntries> to group together one or more occurrences of
<descriptiveEntry> so that they can be manipulated as a package. A single
<descriptiveEntry> may stand alone or may be wrapped within
<descriptiveEntries>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the description being
created. A simpler narrative may be encoded as one or more <p> elements.
May contain:
citation, descriptiveEntry, descriptiveNote, list, outline, p
May occur within:
description
Attributes:
Optional
Occurrence:
0...∞
<descriptiveEntry>
Summary: A means, within description, to extend the descriptive categories available
in the local system. Its meaning will depend on the context in which it occurs.
Description
<descriptiveEntry> provides a means to extend the list of description elements
defined by ISAAR (CPF) and specified in the EAC-CPF schema. It should be used to record
structured index terms rather than narrative text. It contains a <term> element,
with optional <date>, <dateRange> or <dateSet> elements to
provide temporal information and a <place> element for location information. A
<descriptiveNote> may be included if a fuller explanation of the
<descriptiveEntry> is needed.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, descriptiveEntries
Attributes:
Optional
Occurrence:
0...∞
<descriptiveNote>
Summary: A generic element that provides additional information and specifications,
in textual form, concerning the descriptive element in which it is contained.
Description
A generic element available in a number of descriptive elements which can be used to
provide any additional descriptive notes that might be appropriate. Notes must be contained
in paragraphs (<p>) and any necessary formatting may be indicated by use of the
<span> element within <p>.
May contain:
p
May occur within:
activities, activity, conventionDeclaration, cpfRelation,
descriptiveEntries, descriptiveEntry, existDates, function, functionRelation, functions,
identity, languageDeclaration, legalStatus, legalStatuses, localTypeDeclaration,
maintenanceAgency, mandate, mandates, occupation, occupations, placeDate, placesDates,
resourceRelation, setComponent, source
Attributes:
None
Occurrence:
0...1
<eac-cpf>
Encoded Archival Context - Corporate Bodies, Persons, and Families [toc]
Summary: The <eac-cpf> element defines a particular instance of a document
encoded with the EAC-CPF XML Schema. It contains a required <control> and either a
<cpfDescription> or a <multipleIdentities> element.
Description
The outermost wrapper element that defines a particular instance of an archival authority
record encoded with the EAC-CPF XML Schema. It contains a required <control> and
either a <cpfDescription> or a <multipleIndentities> element.
May contain:
control, cpfDescription, multipleIdentities
Attributes:
None
Occurrence:
1
<entityId>
Summary: An optional element of <identity>, which provides any formal
identifier used to designate the entity being described.
Description
An optional element of <identity> which may be used to record any identifier
associated with the 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.
May contain:
[text]
May occur within:
identity
Attributes:
Optional
References:
ISAAR 5.1.6
Occurrence:
0...∞
<entityType>
Summary: The type of entity being described. Values available are: person,
corporateBody, or family.
Description
Within <identity> this mandatory element specifies the type of entity being
described in the EAC-CPF instance. Values available are: person, corporateBody, or
family.
May contain:
"person" or "corporateBody" or "family"
May occur within:
identity
Attributes:
None
References:
ISAAR 5.1.1
Occurrence:
1
<event>
Summary: An element used to encode an event associated with a date and, optionally, a
place within a structured chronology.
Description
The element contains narrative text identifying the event described by the
<chronItem>.
May contain:
[text]
May occur within:
chronItem
Attributes:
Optional
Occurrence:
1
<eventDateTime>
Maintenance Event Date and Time [toc]
Summary: The date and time of a maintenance event for the EAC-CPF instance.
Description
A required element within the <maintenanceEvent>, giving the date and time of a
maintenance event for the EAC-CPF instance. The date and time may be recorded manually or
machine generated in natural language as well as in machine-readable format by use of the
@standardDateTime attribute.
May contain:
[text]
May occur within:
maintenanceEvent
Attributes:
Optional
References:
ISAAR 5.4.6
Occurrence:
1
<eventDescription>
Maintenance Event Description [toc]
Summary: The description of a maintenance event in the life of the EAC-CPF
instance.
Description
A required element within the <maintenanceEvent> element for describing the
maintenance event. The element allows a full description of the maintenance event to be
given alongside the basic definition of the event in the <eventType> element.
May contain:
[text]
May occur within:
maintenanceEvent
Attributes:
None
References:
ISAAR 5.4.9
Occurrence:
1
<eventType>
Maintenance Event Type [toc]
Summary: The type of maintenance event for the EAC-CPF instance.
Description
A required element within <maintenanceEvent> that identifies the type of event.
The available values are: "created," "revised," "deleted," or "cancelled."
May contain:
"cancelled" or "created" or "deleted" or "derived" or "revised"
May occur within:
maintenanceEvent
Attributes:
None
References:
ISAAR 5.4.9
Occurrence:
1
<existDates>
Summary: The dates of existence of the identity being described, such as dates of
establishment and dissolution for corporate bodies and dates of birth and death or flourit
for persons.
Description
<existDates> may contain actual or approximate dates expressed through its elements
<date>, <dateRange>, or <dateSet>. 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.
May contain:
date, dateRange, dateSet, descriptiveNote
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.1
Occurrence:
0...∞
<fromDate>
Summary: The beginning date in a date range.
Description
May contain actual or approximate dates expressed as a month, day, or year in any format.
A standard numerical form of the date (YYYYMMDD, etc.) can be specified with the
@standardDate attribute. The @notBefore and @notAfter
attributes may be used to indicate uncertainty.
May contain:
[text]
May occur within:
dateRange
Attributes:
Optional
Optional
Optional
Occurrence:
1
<function>
Summary: An element that provides information about a function, role, or purpose
performed or manifested by the entity being described.
Description
<function> is a repeatable wrapper element for the content elements
<term>, which contains the term denoting the function, and
<descriptiveNote>, a note providing additional information about it.
A <function> element is used to encode an index term, and a corresponding
@localType attribute to identify the terminology source. Terms are used to
identify the functions that are definitive or otherwise significant to the EAC-CPF entity.
They may be drawn from controlled vocabularies or may be natural language terms. An
associated date or date range and place(s) may be included to further constrain the term’s
meaning. A <descriptiveNote> may be included if a fuller textual explanation is
needed.
A function reflects a process, task, or transaction a corporate body, person, or family
performed. Functions may also be reflected in the narrative text found in
<biogHist> (ISAAR (CPF) History 5.2.2). The <term> element here should be
used to enable separate processing of this information.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, functions
Attributes:
Optional
References:
ISAAR 5.2.5, 5.2.2
Occurrence:
0...∞
<functionRelation>
Summary: A function related to the described entity.
Description
The <functionRelation> element contains the description of a function related to
the described entity. Such related functions are typically described in another encoding
language. Use <objectXMLWrap> to incorporate XML elements from any XML namespace or
<objectBinWrap> for base64-encoded binary data. A <relationEntry> element
is provided for textual identification of the related function.
Use the <date>, <dateRange>, or <dateSet> elements for
specifying when the relation applied and the <place> element for relevant locative
information. A <descriptiveNote> element may be included for a more detailed
specifications or explanations of the relationship.
The @functionRelationType attribute is used to specify the nature of the
relationship that exists between the <function> and the <eac-cpf> entity.
Values are chosen from a closed list.
May contain:
date, dateRange, dateSet, descriptiveNote, objectXMLWrap, place,
objectBinWrap, relationEntry
May occur within:
relations
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
References:
ISDF Chapter 6
Occurrence:
0...∞
<functions>
Summary: A grouping element used to bundle together individual <function>
elements.
Description
Use the optional <functions> element to group together one or more occurrences of
<function> so that they can be manipulated as a package. A single
<function> may stand alone or may be wrapped within <functions>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the functions being
described. A simpler narrative expression of the functions may be encoded as one or more
<p> elements.
May contain:
citation, descriptiveNote, function, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.5
Occurrence:
0...∞
<generalContext>
Summary: An element that encodes information about the general social and cultural
context of the entity being described.
Description
The element <generalContext> may contain a <list>, <outline>,
or <p> element to format information about the social, cultural, economic,
political, and/or historical milieu in which the entity being described existed. The general
context provides wide latitude to record contextual information not specifically
accommodated by other <description> elements.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the general context
being described. A simpler narrative expression of the general context may be encoded as one
or more <p> elements.
May contain:
citation, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.8
Occurrence:
0...∞
<identity>
Summary: A wrapper element for the name portion of the EAC-CPF instance.
Description
<identity> is a container element grouping all the necessary elements to the name
identification of the EAC-CPF instance. Within this element the <entityType>
element is required and specifies the type of entity being described (I.e., corporateBody,
family, or person), and either a <nameEntry> or <nameEntryParallel>
element specifying names by which the entity is known. An optional <entityId> is
available for any identifiers associated with the entity. A <descriptiveNote> may
be included if a fuller explanation of an identity is needed.
All the names by which the entity being described in the EAC-CPF instance is known are
provided within this element as well. Within <identity>, the names of the entity,
whether authorized or alternatives, should be recorded in a <nameEntry> element. If
there is more than one name for the entity, each of them should be recorded in a separate
<nameEntry> element.
In addition to needing to accommodate one or more names used for or by the entity,
<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 entities are frequently provided in more than one language. Within
<identity>, only one <nameEntryParallel> element should be used to group
two or more <nameEntry> elements that represent parallel forms of the name of the
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 entity.
May contain:
descriptiveNote, entityId, entityType, nameEntry,
nameEntryParallel
May occur within:
cpfDescription
Attributes:
Optional
Optional
References:
ISAAR 5.1
Occurrence:
1
<item>
Summary: A formatting element that encodes the individual entries comprising
lists.
Description
The <item> element is used for general lists within a <biogHist> and
within levels in an outline. Do not confuse with <chronItem>, which encodes entries
within a structured chronology <chronList>.
May contain:
[text], span
May occur within:
level, list
Attributes:
Optional
Occurrence:
1...∞
<language>
Summary: The predominant language used in the EAC-CPF instance.
Description
A required element within <languageDeclaration> that gives the main language in
which the EAC-CPF instance is written. The content of the @languageCode attribute
must be given in the form of valid code from ISO 639-2b.
May contain:
[text]
May occur within:
languageDeclaration
Attributes:
Required
References:
ISAAR 5.4.7
Occurrence:
1...∞
<languageDeclaration>
Language Declaration [toc]
Summary: The declaration of the predominant language and script used in the EAC-CPF
instance.
Description
A mandatory wrapper element within <control> that declares the main language and
script in which an EAC-CPF instance is written. Any comments about the languages and scripts
in which the EAC-CPF instance is written may be included in the optional
<descriptiveNote> element.
May contain:
descriptiveNote, language, script
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.7
Occurrence:
1
<legalStatus>
Summary: An element in <description> used to encode information about the
legal status of a corporate body.
Description
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. <legalStatus> contains a <term> element to encode an index
term. Terms may be drawn from controlled vocabularies or may be natural language terms. A
@localType attribute is used to identify the terminology source.
Use the <date>, <dateRange>, or <dateSet> elements for
specifying when the legal status applied and a <place> element for relevant
location information. A <descriptiveNote> element may be included for a more
detailed specification or explanation of the relation.
<legalStatus> may be encoded directly within <description>, or one or more
occurrences may be wrapped within <legalStatuses>.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, legalStatuses
Attributes:
Optional
References:
ISAAR 5.2.4
Occurrence:
0...∞
<legalStatuses>
Summary: A grouping element for one or more <legalStatus> elements in a
description of an entity.
Description
A grouping element for one or more <legalStatus> elements in a description of an
entity. Use the optional <legalStatuses> to group together one or more occurrences
of <legalStatus> so that they can be manipulated as a package. A single
<legalStatus> may stand alone or may be wrapped within
<legalStatuses>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the legal status being
described. A simpler narrative expression of the legal status may be encoded as one or more
<p> elements.
May contain:
citation, descriptiveNote, legalStatus, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.4
Occurrence:
0...∞
<level>
Summary: A required element for <outline> which delineates the outline
format.
Description
A required element for the formatting of outlines.
May contain:
item, level
May occur within:
level, outline
Attributes:
Optional
Occurrence:
1...∞
<list>
Summary: A wrapper element to encode a simple list consisting of two or more
<item> elements.
Description
The <list> element is used for general lists within a descriptive element. Do not
confuse with <chronList>, which encodes a structured chronology.
May contain:
item
May occur within:
activities, biogHist, descriptiveEntries, functions, generalContext,
legalStatuses, mandates, occupations, placesDates, structureOrGenealogy
Attributes:
Optional
Occurrence:
0...∞
<localControlEntry>
Local Control Entry [toc]
Summary: Any additional control entry necessary due to local practice.
Description
An element used to record any control entries necessary due to local practice, in addition
to the elements otherwise made available within <control>. The name of the entry
may be given in a <term> element and an associated date can be given either as a
single date in the <date> element or a date range in the <dateRange>
element.
The type of entry may be defined using the @localType attribute.
May contain:
date, dateRange, term
May occur within:
control
Attributes:
Optional
Occurrence:
0...∞
<localTypeDeclaration>
Local Type Declaration [toc]
Summary: <localTypeDeclaration> is used to declare the local conventions in
@localType in the EAC=CPF instance.
Description
The <localTypeDeclaration> is available to declare the local conventions and
controlled vocabularies used in @localType in the EAC-CPF instance. The
<citation> element may be used to site the resource that lists the used values
(semantic scope and intention) and where the values are used.
May contain:
abbreviation, citation, descriptiveNote
May occur within:
control
Attributes:
None
Occurrence:
0...∞
<maintenanceAgency>
Summary: The institution or service responsible for the creation, maintenance, and/or
dissemination of the instance.
Description
A required element within <control> for wrapping information about the
institution or service responsible for the creation, maintenance, and/or dissemination of
the EAC-CPF instance.
This must include one only of the elements <agencyCode> or <agencyName>
to identify the institution or service. Any general information about the institution in
relation to the EAC-CPF instance may also be given in <descriptiveNote>.
May contain:
agencyCode, agencyName, descriptiveNote
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.2
Occurrence:
1
<maintenanceEvent>
Summary: A maintenance event in the life of the EAC-CPF instance.
Description
A wrapper element within <maintenanceHistory> to record information about
maintenance events in the history of the EAC-CPF instance. There will always be at least one
maintenance event for each instance, usually its creation, and each event must be defined in
the <eventType> element. The event must be described in the
<eventDescription> element and information must also be given about who or what
carried out, or was otherwise responsible for, the work on the EAC-CPF instance in the
<agent> and <agentType> elements and when the event took place in the
<eventDateTime> element.
May contain:
agent, agentType, eventDateTime, eventDescription, eventType
May occur within:
maintenanceHistory
Attributes:
None
References:
ISAAR 5.4
Occurrence:
1...∞
<maintenanceHistory>
Maintenance History [toc]
Summary: The history of the creation and maintenance of the EAC-CPF instance.
Description
A required wrapper element within <control> to record the history and creation of
the EAC-CPF instance. There must be at least one <maintenanceEvent>, usually the
creation, but there may be many other <maintenanceEvent> elements documenting the
milestone events or activities in the maintenance of the instance.
May contain:
maintenanceEvent
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.6, 5.4.9
Occurrence:
1
<maintenanceStatus>
Summary: The current drafting status of the EAC-CPF instance.
Description
A required element within <control> that records the current drafting status of
an EAC-CPF instance: as an EAC-CPF instance is modified or other events happen to it (as
recorded in the <maintenanceHistory> element), the maintenance status should also
be amended to reflect the current drafting status.
On first creation the status would be "new", which on revision can be changed to
"revised". Because it is important to be clear what has happened to records particularly
when sharing and making links between them, a number of status values are available for
records that are no longer current. A record that is simply deleted from a system can be
given the status "deleted", but in cases where a record is marked as not current (obsolete
or rejected) but kept for reference then it should be given the status "cancelled". If a
record is deleted though because it has become superseded by two or more records then its
status should be given as "deletedSplit", while if it has simply been replaced by a new
record then "deletedReplaced" is the appropriate status value.
May contain:
"cancelled" or "deleted" or "deletedReplaced" or "deletedSplit" or "new"
or "revised"
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.4
Occurrence:
1
<mandate>
Summary: 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.
Description
Use the <date>, <dateRange>, or <dateSet> elements for
specifying when that temporal constraint applied and a <place> element for relevant
location information. A <descriptiveNote> element may be included for more detailed
specifications or explanations of the relation. mandate.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, mandates
Attributes:
Optional
References:
ISAAR 5.2.6
Occurrence:
0...∞
<mandates>
Summary: A wrapper element used to group one or more <mandate> elements,
each of which identifies an authority or mandate for the corporate body in terms of its
powers, functions, responsibilities or sphere of activities.
Description
Use the optional <mandates> element to group together one or more occurrences of
<mandate> so that they can be manipulated as a package. A single
<mandate> may stand alone or may be wrapped within <mandates>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the mandates being
described. A simpler narrative expression of the mandates may be encoded as one or more
<p> elements.
May contain:
citation, descriptiveNote, list, mandate, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.6
Occurrence:
0...∞
<multipleIdentities>
Multiple Identities [toc]
Summary: A wrapper element that may be used to group together more than one
<cpfDescription> within a single EAC-CPF instance.
Description
A wrapper element to encode more than one <cpfDescription> in a single EAC-CPF
instance. An EAC-CPF instance can contain more than one <cpfDescription> in one of
two ways. The first is used to represent more than one persona (including official personae)
each with a separate description; the second is used to represent a collaborative personae
which includes multiple individuals operating under a shared personae (such as a shared
pseudonym).
May contain:
cpfDescription
May occur within:
eac-cpf
Attributes:
None
Occurrence:
1
<nameEntry>
Summary: An element containing a name entry for a corporate body, person, or family.
<nameEntry> is made up of <part> elements so that the entity can be
identified with certainty and distinguished from others bearing the same or similar
names.
Description
Within <identity>, the element <nameEntry> is used to record a name by
which the corporate body, the person, or the family described in the EAC-CPF instance is
known.
The element <nameEntry> is used to record either the authorized form(s) of the
name or the alternative ones, whether standardized or not. Each form of name is recorded in
a separate <nameEntry> element.
Each <nameEntry> should 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 contain a <useDates> element to indicate the
dates of use of the name, only when <nameEntry> is not included within
<nameEntryParallel>.
The attributes @scriptCode and @languageCode are used to specify the
script and the language of each of the names recorded in <nameEntry>.
If the form of the name recorded in <nameEntry> is a transliterated one, the
attribute @transliteration is used to record the conventions or rules applied to
transliterate this form of the name.
The attribute @rules is used to specify the conventions or rules applied to
establish the form of the name recorded in <nameEntry>.
The attribute @authorizedByRules is used to specify the conventions or rules
used in formulating the <nameEntry> and designating it authorized.
May contain:
part, useDates
May occur within:
identity, nameEntryParallel
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
References:
ISAAR 5.1.2, 5.1.4, 5.1.5
Occurrence:
1...∞
<nameEntryParallel>
Name Entry Parallel [toc]
Summary: A wrapper element for two or more <nameEntry> elements that
represent the same entity.
Description
A container element used to group two or more <nameEntry> elements representing
parallel forms of the name for the same entity (e.g., official forms of the name in
different languages and/or scripts, transliterated forms of the name).
Do not use for pairing authorized and unauthorized forms of the same name (e.g., an
authorized form with see references).
The <nameEntryParallel> element may contain a <useDates> element to
indicate the dates of use of the set of parallel name forms.
The attribute @rules is used to specify the conventions or rules applied to
establish the form of the names recorded in <nameEntryParallel>.
The attributes @authorizedByRules is used to specify the name of the agency by
which the form of the names recorded in <nameEntryParallel> has been
constructed.
May contain:
nameEntry, useDates
May occur within:
identity
Attributes:
Optional
Optional
Optional
References:
ISAAR 5.1.3
Occurrence:
0...1
<objectBinWrap>
Summary: This element provides a place for a base64-encoded binary representation of
a resource.
Description
This element provides a place for a base64-encoded binary representation of a resource.
The datatype of base64-encoded binary is based on the W3C Schema Part 2: Datatypes.
May contain:
base64Binary
May occur within:
cpfRelation, functionRelation, resourceRelation, setComponent,
source
Attributes:
None
Occurrence:
0...∞
<objectXMLWrap>
Summary: A place for incorporating XML elements from any XML namespace.
Description
This element provides a place to express data in another XML encoding language. While the
element is not restricted with respect to namespace, 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.
May contain:
any element from any namespace
May occur within:
cpfRelation, functionRelation, resourceRelation, setComponent,
source
Attributes:
None
Occurrence:
0...1
<occupation>
Summary: A descriptive element used to encode information about the EAC-CPF entity’s
occupation.
Description
A <term> element may be used to record an occupational name from a controlled
vocabulary specified in the @localType attribute. Terms may be drawn from
controlled vocabularies or may be natural language terms.
Use the <date>, <dateRange> or <dateSet> elements for
specifying when the occupation was performed and a <place> element for relevant
location information. A <descriptiveNote> element may be included for more detailed
specifications or explanations of the occupation.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, occupations
Attributes:
Optional
References:
ISAAR 5.2.5
Occurrence:
0...∞
<occupations>
Summary: A wrapper element used to group one or more <occupation> elements
in the <description>.
Description
Use the optional <occupations> to group together one or more occurrences of
<occupation> so that they can be manipulated as a package. A single
<occupation> may stand alone or may be wrapped within <occupations>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the occupations being
described. A simpler narrative expression of the occupations may be encoded as one or more
<p> elements.
May contain:
citation, descriptiveNote, list, occupation, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.5
Occurrence:
0...∞
<otherRecordId>
Other Record Indentifier [toc]
Summary: Alternate record identifiers that may be associated with the EAC-CPF
instance.
Description
An element in <control> for the provision of alternate record identifiers to the
mandatory identifier in <recordId> that may be associated with the EAC-CPF
instance. These might include the identifiers of merged EAC-CPF instances representing the
same entity or those of records that are no longer current but had some part in the history
and maintenance of the EAC-CPF instance.
The @localType attribute can be used to identify the kind of institution or
service responsible for each associated record if not the same as that given in the
<maintenanceAgency> element for this EAC-CPF instance.
May contain:
[text]
May occur within:
control
Attributes:
Optional
Occurrence:
0...∞
<outline>
Summary: An element used within the description area to encode information in an
outline format.
Description
<outline> contains one or more <level> elements, which contain either
<item> elements or further <level> elements in a hierarchical
fashion.
May contain:
level
May occur within:
activities, biogHist, descriptiveEntries, functions, generalContext,
legalStatuses, mandates, occupations, placesDates, structureOrGenealogy
Attributes:
Optional
Occurrence:
0...∞
<p>
Summary: A generic element in the description area which marks one or more sentences
that form a logical prose passage.
Description
A paragraph may be a subdivision of a larger composition, or it may exist alone. It is
usually typographically distinct. A line space is often left blank before it; the text
begins on a new line; and the first letter of the first word is often indented, enlarged, or
both.
The <p> element is an important textual feature, which must be used as part of
any general description within a <descriptiveNote> element and may be used inside
many of the descriptive elements within the description area. While it generally contains
narrative text, it may also contain a <span> element to further stress or style
specific character strings by particular formatting (such as italic or bold, etc.).
May contain:
[text], span
May occur within:
activities, biogHist, descriptiveEntries, functions, generalContext,
legalStatuses, mandates, occupations, placeDates, structureOrGenealogy
Attributes:
None
Occurrence:
0...∞
<part>
Summary: <part> is used to distinguish components of the name of the entity.
Description
Within <nameEntry> each of the component parts of a name, such as forename,
surname, 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 component parts of the name.
The designation of the information contained in the <part> is specified by the
attribute @localType.
May contain:
[text]
May occur within:
nameEntry
Attributes:
Optional
Occurrence:
1...∞
<place>
Summary: An element used in both the description and relations areas to encode
information about the place or jurisdiction where the EAC-CPF entity was based, lived, or
with which it had some other significant connection.
Description
Places should be identified by the proper noun that commonly designates the place, natural
feature, or political jurisdiction. @latitude, @longitude, and
@altitude attributes are available for specific geographical data. The
@localType attribute may be used to identify the vocabulary from which the place
name was taken. It is recommended that place names be taken from authorized
vocabularies.
May contain:
[text]
May occur within:
activity, chronItem, cpfRelation, descriptiveEntry, function,
functionRelation, legalStatus, mandate, occupation, placeDate, resourceRelation
Attributes:
Optional
Optional
Optional
Optional
Optional
Occurrence:
0...∞
<placeDate>
Summary: A grouping element in the description area used to bind a place element with
a date(s) element in a persistent fashion.
Description
<placeDate> allows closely related place and date information to be grouped
together within a binder that prevents the two values from being parsed apart. Use the
<date>, <dateRange>, or <dateSet> elements for specifying when
the relation applied and a <place> element for relevant location information. A
<descriptiveNote> element may be included for more detailed specifications or
explanation of the relation between the values.
May contain:
citation, date, dateRange, dateSet, descriptiveNote, place, term
May occur within:
description, placesDates
Attributes:
Optional
References:
ISAAR 5.2.3
Occurrence:
0...∞
<placesDates>
Summary: A wrapper element used to group together one or more <placeDate>
elements.
Description
Use the optional <placesDates> to group together one or more occurrences of
<placeDate> so that they can be manipulated as a package. A single
<placeDate> may stand alone or may be wrapped within <placesDates>.
The optional <citation>, <list>, and <outline> elements are
used to accommodate greater complexity in expressing or representing the places and dates
being described. A simpler narrative expression of the places and dates may be encoded as
one or more <p> elements.
May contain:
citation, descriptiveNote, list, outline, p, placeDate
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.3
Occurrence:
0...∞
<recordId>
Summary: The unique identifier for a particular instance.
Description
A required element within <control> that designates a unique identifier for the
EAC-CPF instance. The assigning owner ensures the uniqueness of the value within the EAC-CPF
descriptive system under its control. The <recordId>, when used in combination with
the content of the required <agencyCode> element within
<maintenanceAgency>, will provide a globally unique identifier.
May contain:
[NMTOKEN]
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.1
Occurrence:
1
<relationEntry>
Summary: A descriptive element for relations that provides narrative text.
Description
A descriptive element for relations that provides narrative text identifying a related
entity, which may be either another name (CPF) entity, a resources created by or otherwise
related to the named entity (e.g., archival records), or the name of a related function.
May contain:
[text], span
May occur within:
cpfRelation, functionRelation, resourceRelation
Attributes:
Optional
Optional
Optional
Occurrence:
0...∞
<relations>
Summary: A wrapper element for grouping one or more specific relations.
Description
A wrapper element that groups together one or more terms, each of which denotes a specific
relationship. Entities may have relationships with other corporate bodies, persons or
families, which may be expressed using <cpfRelation>; functions, which may be
expressed using <functionRelation>; or resources such as archival collections,
which may be expressed using <resourceRelation>.
May contain:
cpfRelation, functionRelation, resourceRelation
May occur within:
cpfDescription
Attributes:
None
References:
The general concept of providing connections from archival authority
records to other related resources is stated in ISAAR(CPF) 6.0: "Archival authority records
are created primarily to document the context of records creation. To make this documentation
useful it is necessary to provide explicit connections to the authority records to
descriptions of records. Archival authority records can also be linked to other relevant
information resources."
Occurrence:
0…1
<resourceRelation>
Summary: A resource related to the described entity.
Description
The <resourceRelation> element contains the description of a resource related to
the described entity. Use <objectXMLWrap> to incorporate XML elements from any XML
namespaces or <objectBinWrap> for base64-encoded binary data. A
<relationEntry> element is provided for textual identification of the related
resource.
Use the <date>, <dateRange>, or <dateSet> elements for
specifying when the relationship applied and the <place> element for relevant
locative information. A <descriptiveNote> element may be included for a more
detailed specifications or explanations of the relationship.
The @resourceRelationType attribute is used to specify the nature of the
relationship between the resource and the entity described in the <eac-cpf>
instance.
May contain:
date, dateRange, dateSet, descriptiveNote, objectXMLWrap, place,
objectBinWrap, relationEntry
May occur within:
relations
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
References:
ISAAR 6
Occurrence:
0...∞
<script>
Summary: The predominant script used in the EAC-CPF instance.
Description
A required element within <languageDeclaration> that gives the main script in
which the EAC-CPF instance is written. The content of the @scriptCode attribute
must be given in the form of a valid code from ISO 15924.
May contain:
[text]
May occur within:
languageDeclaration
Attributes:
Required
References:
ISAAR 5.4.7
Occurrence:
0...1
<setComponent>
Summary: A wrapper element within <alternativeSet> that contains the EAC-CPF
encoding for one entire authority record, thereby permitting the bundling of authority
records from multiple authority systems within a single <cpfDescription>.
Description
<setComponent> provides an encoding wrapper to contain an entire authority record,
so that multiple records for the same identity from separate authority systems or in
different languages, may be combined together within a single EAC-CPF instance. The
mandatory <componentEntry> element encodes the link to the authority record in the
external authority system. An optional <descriptiveNote> may be used for a textual
note providing further information about the record referenced in
<setComponent>.
May contain:
componentEntry, descriptiveNote, objectXMLWrap, objectBinWrap
May occur within:
alternativeSet
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
Occurrence:
1...∞
<source>
Summary: A source of evidence used in describing the entity in the EAC-CPF
instance.
Description
An element for identifying a particular source of evidence used in describing the entity.
A record for the source can be included in either <objectXMLWrap> or
<objectBinWrap>; or a textual identification can be given in the
<sourceEntry> element. Use the optional <descriptiveNote> for any
additional notes about the source.
A link to the source may be made using the XML Linking Language (Xlink) attributes (for
which consult the specification at http://www.w3.org/TR/xlink/) and the last date and time
that the source was verified can be given in the @lastDateTimeVerified
attribute.
May contain:
descriptiveNote, objectXMLWrap, objectBinWrap, sourceEntry
May occur within:
sources
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
References:
ISAAR 5.4.8
Occurrence:
1...∞
<sourceEntry>
Summary: A textual identification of a particular source of evidence used in
describing the entity in the EAC-CPF instance.
Description
The <sourceEntry> element may be used within the <source> element to
identify a source used in the construction of the EAC-CPF instance. While it generally
contains narrative text, it may also contain a <span> element to further stress or
style specific character strings by particular formatting (such as italic or bold,
etc.).
May contain:
[text], span
May occur within:
source
Attributes:
None
Occurrence:
0...1
<sources>
Summary: A record of the sources used for the description of the entity or entities
in the EAC-CPF instance.
Description
A mandatory wrapper element within <control> used to record one or more sources
consulted in creating the description of the entity or entities in the EAC-CPF instance.
May contain:
source
May occur within:
control
Attributes:
None
References:
ISAAR 5.4.8
Occurrence:
1
<span>
Summary: Specifies the beginning and the end of a span of text.
Description
A formatting element for marking arbitrary words or phrases that are stressed or
emphasized for linguistic effect or identifying some qualities of the words or phrases. Use
the @style attribute to affect an arbitrary stylistic difference. Use the
@type attribute to assign other characteristics.
May contain:
[text]
May occur within:
abstract, citation, componentEntry, item, p, sourceEntry
Attributes:
Optional
Optional
Occurrence:
0...∞
<structureOrGenealogy>
Structure or Genealogy [toc]
Summary: A description of the internal administrative structure(s) of a corporate
body or the genealogy of a family.
Description
<structureOrGenealogy> encodes within the description area, 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), and the genealogy of a family (such as a family
tree) in a way that demonstrates the interrelationships of its members with covering
dates.
The optional <list> and <outline> elements are used to accommodate
greater complexity in expressing or representing the activities being described.
<citation> may be used to provide a link to external documents like organizational
charts and family trees. A simpler narrative expression of the activities may be encoded as
one or more <p> elements.
Note: when persons are being described, information on their genealogy may be recorded in
the History element (5.2.2) and/or in the Relationships Area (5.3)
May contain:
citation, list, outline, p
May occur within:
description
Attributes:
Optional
References:
ISAAR 5.2.7
Occurrence:
0...∞
<term>
Summary: A generic element used to encode a descriptive term in accordance with local
descriptive rules.
Description
The local authority – thesaurus or local controlled vocabulary – should be declared in the
<authorityDeclaration> element within the <control> section.
May contain:
[text]
May occur within:
activity, descriptiveEntry, function, legalStatus, localControlEntry,
mandate, occupation, placeDate
Attributes:
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required (if any XLINK attributes used)
Occurrence:
0...∞
<toDate>
Summary: The ending date in a date range.
Description
May contain actual or approximate dates expressed as a month, day, or year in any format.
A standard numerical form of the date (YYYYMMDD, etc.) can be specified with the
@standardDate attribute. The @notBefore and @notAfter
attributes may be used to indicate uncertainty.
May contain:
[text]
May occur within:
dateRange
Attributes:
Optional
Optional
Optional
Occurrence:
1
<useDates>
Summary: The dates when the name or names were used by the entity being described.
Description
Within <nameEntry>, <useDates> provides the dates when the name was
used. For parallel names, <useDates> may occur in <nameEntryParallel>
rather than in the <nameEntry>s contained in <nameEntryParallel>.
May contain:
date, dateRange, dateSet
May occur within:
nameEntry, nameEntryParallel
Attributes:
None
References:
ISAAR 5.1.3
Occurrence:
0...1
[toc]
Attributes
@altitude
Summary: The altitude or elevation of the geographic place.
Description
The @altitude may occur on <place>. The value of the
attribute is the altitude or elevation of the geographic place named. @altitude
should be used in conjunction with @longitude and @latitude.
Data Type:
NMTOKEN
@authorizedByRules
Authorized by Rules [toc]
Summary: The abbreviation or abbreviations of the rules or conventions used in
forming the entry and that the form of the entry is authorized.
Description
The @authorizedByRules may occur on <nameEntry> or
<nameEntryParallel>. The value of the attribute contains one or more abbreviations,
separated by a space, identifying the descriptive convention or conventions used to form the
entry and that designate the entry recorded in the <nameEntry> or the names recorded
in the <nameEntryParallel>
authorized.
Data Type:
NMTOKENS
@countryCode
Summary: A standard code representing a country.
Description
The @countryCode may occur on <place>. The Country
Code may be used to provide an standard code designating the country within which the
geographic place named in <place> exists, or, if the placed named is a country, the
code for that country.
Data Type:
ISO 3166-1 Codes for the Representation of Names of Countries, column
A2.
@cpfRelationType
Corporate Body, Person, or Family Relation Type [toc]
Summary: The type of relation that the corporate body, person, or family has to the
entity being described.
Description
The @cpfRelationType may occur on <cpfRelation>. The
value designates the type of relation that a corporate body, person, or family has to the
entity being described in the EAC-CPF instance. If the nature of the relation is more
specific than one of the values given below, @xlink:arcrole can be used in addition
to @cpfRelationType.
Data Type:
identity, hierarchical, hierarchical-parent, hierarchical-child, temporal,
temporal-earlier, temporal-later, family, or associative.
@functionRelationType
Function Relation Type [toc]
Summary: The type of relation that the entity being described has to the related
function.
Description
The @functionRelationType may occur on
<functionRelation>. The value desginates the type of relation that the entity being
described has to the related function. If the type of relation is more specific than one of
the values given below, @xlink:arcrole may be used in addition to
@functionRelationType.
Data Type:
"controls" or "owns" or "performs"
@id
Summary: A unique identifier for the description that can be used to identify
specific descriptions when the EAC-CPF instance describes multiple identities.
Description
The @id may occur on <cpfDescription>. The
@id may be used to uniquely identify two or more <cpfDescription> within
<multipleIdentities>. Uniquely identifying or distinguishing two or more
<cpfDescription> may be essential or useful in maintenance environments when
relating resources, functions, or corporate bodies, persons, or families to one among two or
more identities represented in one EAC-CPF instance.
Data Type:
NMTOKEN
@identityType
Summary: Indicates whether whether the identity is given or acquired. May be usefule
for processing when multiple identities are described in the same instance.
Description
The @identityType may occur on <identity>. Though
optional, it is recommended that it be used when multiple identities are described in the
same EAC-CPF instance using <multipleIdentities>. It will enable processors to
distinguish between the description of a person and one or more personae.
Data Type:
given or acquired.
@languageCode
Summary: Three-letter ISO 639-2 language code.
Description
The @languageCode may occur on <nameEntry>,
<componentEntry>, and <relationEntry>, and
must occur on <language>. The Language Code is used to provide a standard
code representing a lanuage.
Data Type:
IS0 639-2 Codes for the Representation of Names of Languages.
@lastDateTimeVerified
Last Date and Time Verified [toc]
Summary: Last date or date and time the linked resource was verified.
Description
The @lastDateTimeVerified may occur on <citation>,
<cpfRelation>, <functionRelation>, <resourceRelation>,
<setComponent>, or <term>. The value of the attribute provides the last
date or last date and time when a related (or linked) object was verified. Verification may
include link resolution as well as verification of the version of the linked object.
Data Type:
Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime.
The following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.
@latitude
Summary: The geographic latitude of the place.
Description
The @latitude may occur on <place>. The value of the
attribute is the geographic latitude of the place named. @latitude should be used
in conjunction with @longitude and @latitude.
Data Type:
NMTOKEN
@localType
Summary: Used to make the semantics of the element more specific or to provide
semantic specificity to elements that are semantically weak. Value should be an absolute
URI.
Description
The @localType is broadly available on many descriptive and a
few contral elements. It is intended to provide a means to narrow the semantics of some
elements or provide semantics for elements that are primarily structural or that are
semantically weak. The value of the @localType must conform to W3C Schema Part 2:
Datatypes, anyURI. To facilitate exchange of EAC-CPF instances, it is highly recommend that
the URI be absolute and resolvable to a local resource that describes the semantic scope and
use of the value.
Data Type:
anyURI
@longitude
Summary: The longitude of the place.
Description
The @longitude may occur on <place>. The value of the
attribute is the geographic longitude of the place named. @longitude should be used
in conjunction with @latitude and @altitude.
Data Type:
NMTOKEN
@notAfter
Summary: The latest date possible for an uncertain date.
Description
The @notAfter may occur on <dateSingle>,
<fromDate>, and <toDate>. For uncertain dates, used in conjunction with
@standardDate, the value of @notAfter is the latest date possible. See
also @notBefore.
Data Type:
Union of the XML Schema Datatypes date, gYear, and gYearMonth. The
following are all valid patterns: 2009-12-31, 2009, 2009-12.
@notBefore
Summary: The earliest date possible for an uncertain date.
Description
The @notBefore may occur on <dateSingle>,
<fromDate>, and <toDate>. For uncertain dates, used in conjunction with
@standardDate, the value of @notBefore is the earliest date possible.
See also @notAfter.
Data Type:
Union of the XML Schema Datatypes date, gYear, and gYearMonth. The
following are all valid patterns: 2009-12-31, 2009, 2009-12.
@relatedCpfEntityType
Related Corporate Body, Person, or Family Type [toc]
Summary: The type of entity related to the entity be described.
Description
The @relatedCpfEntityType may occur on <cpfRelation>.
The value designates the type of the related entity: corporate body, person, or family. If a
more specific type is needed for local processing, @xlink:role may be used in
addition to @relatedCpfEntityType.
Data Type:
"person" or "corporateBody" or "family"
@relatedFunctionType
Related Function Type [toc]
Summary: The type of function related to the entity being described.
Description
The @relatedFunctionType may occur on
<functionRelation>. The value designates the type of function related to the entity
being described: activity, ambientFunction, function, process, transaction, or other. If a
more specific type is needed for local processing, @xlink:role may be used in
addition to @relatedFunctionType.
Data Type:
"activity" or "ambientFunction" or "function" or "process" or "transaction"
or "other"
@relatedResourceType
Related Resource Type [toc]
Summary: The type of resource related to the entity being described.
Description
The @relatedResourceType may occur on
<resourceRelation>. The value designates the type of resource related to the entity
being described: library, archival, museum, monument, or site. If a more specific type is
needed for local processing, @xlink:role may be used in addition to
@relatedResourceType.
Data Type:
"library" or "archival" or "museum" or "monument" or "site"
@resourceRelationType
Resource Relation Type [toc]
Summary: The type of relation of entity being described to the resource.
Description
The @ResourceRelationType may occur on
<resourceRelation>. The value desginates the type of relation that the entity
described in the EAC-CPF instance has to the resource. If the nature of the relation is more
specific than one of the available values, @xlink:arcrole may be used in addition
to @resourceRelationType.
Data Type:
creatorOf, subjectOf, and other.
@rules
Summary: Abbreviation of the rules or conventions used in forming the name
entry.
Description
The @rules may occur on <nameEntry> or
<nameEntryParallel>. The value of the attribute contains one or more abbreviations,
separated by a space, identifying the descriptive rules or conventions used in forming the
string in the <nameEntry> or the names recorded in the <nameEntryParallel>.
Do not confuse with @authorizedByRules, which adds the addition qualification that
the entry is
autorized.
Data Type:
NMTOKENS
@scriptCode
Summary: The ISO 15924 three-letter code for the writing script used.
Description
A standard three-letter code for the writing script used with a given
language.
Data Type:
ISO 15924 Code for the Representation of Names and Scripts
@standardDate
Summary: The date represented in a standard form for computer processing.
Description
The @standardDate may occur on <dateSingle>,
<fromDate>, and <toDate>. The value of @standardDate provides a
standard form of the date expressed in <dateSingle>, <fromDate>, or
<toDate> that can be used in computer processing, such as searching.
Data Type:
Union of the XML Schema Datatypes date, gYear, and gYearMonth. The
following are all valid patterns: 2009-12-31, 2009, 2009-12.
@standardDateTime
Standard Date and Time [toc]
Summary: The date or date and time represented in a standard form for computer
processing.
Description
The @standardDateTime may occur on <eventDateTime>.
The value of @standardDateTime provides a standard form of the date or date and
time expressed in the <eventDateTime> that can be used in computer processing. For
example, using both the value in <eventType> and @standardDateTime, all
EAC-CPF instances "revised" on a particular date can be identified.
Data Type:
Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime.
The following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.
@style
Summary: Used to specify a rendering style for string. It is recommended that the
value conform to W3C CSS.
Description
The @style may occur on <span>. In a limited number
of contexts that accommodate discursive description, <span> with @style
may be used to identify an arbitrary string that is intended to be rendered in a specific
style. It is highly recommended that the value of @style be expressed as a W3C CSS
style to facilitate interoperability.
Data Type:
string
@transliteration
Summary: A value designating the transliteration scheme used in representing
converting one script into a another script.
Description
The conventions or rules that prescribe a method for converting one
script into another script.
Data Type:
NMTOKEN
@xlink:actuate
Summary: Used to signal intended behavior with respect to whether the remote resource
link is resolved when the containing resource is rendered, or when the user requests the
resource.
Description
The @xlink:actuate should be used with the
@xlink:show to indicate intended behavior. The @xlink:actuate is used to
signal intended behavior with respect to when the remote resource is to appear. The values
indicate whether the resource is to appear automatically when the containing resource is
rendered ("onLoad"), or only after the user requests the resource ("onRequest"). "None" or
"other" are also valid values.
Data Type:
"onLoad" or "onRequest" or "other" or "none"
@xlink:arcrole
Summary: URI defining the purpose of the link.
Description
An absolute URI that indicates the nature of the relation between the
entity being described, for example, in <resourceRelation>, or the EAC-CPF instance
itself, for example in <source>, and the resource referenced in the
<xlink:href>. The value of the attribute should indicate the direction of the
relation. It is recommended that the direction of the relation be from local resource to
remote resource.
Data Type:
string
@xlink:href
Summary: Contains a URI, possibly relative, pointing to the related resource
Description
The address for a remote resource. The @xlink:href takes the
form of a Uniform Resource Identifier (URI). While it is permissible to use a relative URI,
and absolute URI is recommended.
Data Type:
anyURI
@xlink:role
Summary: Identifies the type or nature of the remote resource with an absolute
URI.
Description
Identifies the type or nature of the remote resource with an absolute
URI.
Data Type:
string
@xlink:show
Summary: Used to signal intended behavior with respect to where the remote resource
is to appear when the link is resolved.
Description
The @xlink:show should be used with the
@xlink:actuate to indicate intended behavior. The @xlink:show is used to
signal intended behavior with respect to where the remote resource is to appear when the link
is resolved. The values indicate whether the resource is to appear embedded at the point of
the link ("embed"), replace the resource in which it appears ("replace"), or in a new window
("new"). "None" or "other" are also valid values.
Data Type:
"embed" or "new" or "replace" or "none" or "other"
@xlink:title
Summary: Information that may be used as a viewable caption for the remote
resource.
Description
Information that serves as a viewable caption that indicates the name or
type of the linked remote source.
Data Type:
string
@xlink:type
Summary:
Description
A fixed value that identifies an XLINK compliant element of a particular
type. Only one XLINK type is used in EAC-CPF, "simple." While the attribute is optional in
instances validated against the W3C Schema version of EAC-CPF, the Relax NG version of
EAC-CPF requires it. To support exchange of EAC-CPF instances, it is recommened that the
@xlink:type be present in the instance whenever any of the other XLINK attributes
are used.
Data Type:
Fixed value: "simple"
[toc]