Encoded Archival Context - Corporate Bodies, Persons, and Families (EAC-CPF) Tag Library Version EAC-CPF 3.0.0
2026 Edition
Prepared and maintained by the
Technical Subcommittee for Encoded Archival Standards of the Society of American Archivists
and the Staatsbibliothek zu Berlin
Table of Contents
Related Standards
Release and Revision Notes
Tag Library Conventions
Elements
abstract description legalStatus otherEntityTypes structureOrGenealogy
address descriptiveNote legalStatuses otherRecordId term
addressLine eac localDescription p toDate
agencyCode entityType localDescriptions part useDates
agencyName eventDateTime localTypeDeclaration place writingSystem
agent eventDescription maintenanceAgency placeName
alternativeSet existDates maintenanceEvent places
biogHist formattingExtension maintenanceHistory recordId
citedRange fromDate mandate reference
componentEntry functionPerformed mandates relation
contact functionsPerformed multipleIdentities relations
contactLine generalContext nameEntry relationship
control geographicCoordinates nameEntrySet referringString
conventionDeclaration identity narrativeEvent rightsDeclaration
cpfDescription identityId objectXMLWrap role
date label narrativeEvent setComponent
dateRange language occupation shortCode
dateSet languageDeclaration occupations source
demographicDescription languageUsed otherAgencyCode sources
demographicDescriptions languagesUsed otherEntityType span
Attributes
addressLineType detailLevel maintenanceEventType relationType unit
addressLineTypeEncoding detailLevelEncoding maintenanceEventTypeEncoding relationTypeEncoding value
agentType era maintenanceStatus repositoryEncoding valueURI
agentTypeEncoding href maintenanceStatusEncoding scriptCode vocabularySource
audience id normalizedForm scriptEncoding vocabularySourceURI
audienceEncoding identityType notAfter scriptOfElement
calendar identityTypeEncoding notBefore sourceReference
certainty languageCode placeType standardDate
contactLineType languageEncoding placeTypeEncoding standardDateTime
contactLineTypeEncoding languageOfElement preferredForm status
conventionDeclarationReference linkRole publicationStatus statusEncoding
coordinateSystem linkTitle publicationStatusEncoding style
countryCode localType referredEntityRelationship target
countryEncoding localTypeDeclarationReference referredEntityType targetType
dateEncoding maintenanceEventReference referredEntityTypeEncoding targetTypeEncoding
Examples
eac
control
identity
description
relations
alternativeSet
Related Standards  [toc]
The standards maintained by the Society of American Archivists’ Technical Subcommittee on Encoded Archival Standards (TS-EAS) are XML schemas based on established models developed by the International Council on Archives (ICA).
EAC-CPF is based on the International Standard Archival Authority Record for Corporate Bodies, Persons and Families (ISAAR-CPF). Revisions to the EAD and EAC-CPF standards are being undertaken by TS-EAS based on the requirements of the Society of American Archivists’ standards maintenance schedule and policies, and are not tied to ongoing development of standards by the ICA, though keeping close connections to the ICA Experts Group on Archival Description as a related standards body.
For this reason, the EAC-CPF 2.0 continues to be based on ISAAR(CPF) rather than the draft versions of Records in Contexts. We anticipate that future versions of EAC-CPF and other standards maintained by TS-EAS will take the Records in Contexts - Conceptual Model into account once it is finalized and approved.
International Standard Archival Authority Record for Corporate Bodies, Persons and Families (ISAAR(CPF))
ISAAR(CPF) is a descriptive standard for descriptions of agent entities (corporate bodies, persons and families) associated with the creation and maintenance of archives. ISAAR(CPF) is maintained by the ICA.
Encoded Archival Description (EAD)
EAD is an XML standard for encoding archival finding aids, maintained by the TS-EAS of the Society of American Archivists, in partnership with the Library of Congress.
Encoded Archival Guide (EAG)
EAG is an XML standard for encoding data about archives and related organizations. EAG is maintained by the Archives Portal Europe Foundation and its Working Group on Standards (WGoS). The development of EAG is coordinated in close cooperation with the TS-EAS, which is responsible for EAD and EAC-CPF.
Encoding Standards
The international community of cultural heritage organizations is working on a broad set of diverse standards to meet the challenges of the digital age. Established standards concerning digitization and metadata are maintained by the Library of Congress.
Records in Contexts - Conceptual Model (RiC-CM)
RiC-CM is a high-level conceptual model that focuses on intellectually identifying and describing records, the people that created and use(d) them, and the activities pursued by the people that the records both facilitate and document. RiC-CM is maintained by the ICA.
Release and Revision Notes  [toc]
This is the release of the Tag Library for EAC-CPF 3.0. This major release includes changes and updates in the schema undertaken by the SAA Technical Subcommittee on Encoded Archival Standards (TS EAS) for the third major revision of the standard EAC-CPF. It supersedes the standard version EAC-CPF 2.0.1 (2024).
The release reflects the commitment to align all EAS where possible and practical.
The EAC-CPF Tag Library is a living document. As such, it will continue to be developed as users suggest areas in need of clarification or expansion. The TS-EAS still encourages implementers to provide any queries, comments, and suggestions regarding the tag library and its content. In addition, the contribution of examples is highly encouraged. Questions, comments or examples may be directed to the TS-EAS (ts-eas[at]archivists.org). The underlying encoding of the Tag Library is based on TEI P5 and is designed to facilitate incorporating documentation into the schema to provide guidance in XML editors. While the initial release of the Tag Library is in English, the underlying encoding is designed to facilitate providing the Tag Library in additional languages at later dates.
All elements and attributes in EAC-CPF 2.0.1 were evaluated with particular attention to elements and attributes shared across EAS.
Following ISAAR(CPF), the established structure of control area, identity area, description area, and relations is still available, as is the availability of encoding multiple identities in one EAC-CPF instance.
Working in parallel with the ICA Experts Group on Archival Description (ICA EGAD), EAC-CPF 3.0 reflects the Records on Contexts - Conceptial Model (RiC-CM) where feasible.
This tag library is focused on technical implementation of the EAC-CPF 3.0 standard. A companion document, the Best Practices Guide (BPG), provides guidance on applying the standard in archival practice. The BPG includes in-depth explanations of elements and attributes, use cases, and additional examples.
Tag Library Conventions  [toc]
The EAC-CPF Elements section of the Tag Library contains descriptions of the elements, arranged alphabetically by element name.
Tag Name:
Short, mnemonic form of the element name that is used in the machine-readable encoded document. The tag name is the first word at the top of the page. Tag names appear between angle brackets, e.g., <nameEntry>, except in the listings under "May occur within" and "May contain," and are always in camel case (camelCase).
Element Name:
Expanded version of the tag name that more fully describes the element's meaning. The full name of the element is usually a word or phrase that identifies the element's purpose. In the Tag Library, the element name follows the tag name on the page defining that element and appears with initial capital letters, e.g., <nameEntry> Name Entry.
Summary:
A brief statement that provides a concise definition of the element, suitable for quick reference.
May Contain:
Identifies what child nodes (text or elements) may occur within the element being defined. Elements are listed in alphabetical order by tag name. Elements may be empty (e.g., an element which allows no child text or element nodes), or they may contain text (listed as [text]), other elements, or a mixture of text and other elements.Text content cannot include characters that would be interpreted by a parser as action codes. For example, a left angle bracket must be represented as the character entity reference &lt; so that it is not misinterpreted as the start of an element name. The technical availability of child elements is listed in brackets beside each element, e.g. place (0..1). The first character represents the minimum occurrences of the child element and the final character represents the maximum occurrences of the child element, with 'n' representing unlimited occurrences.
May Occur Within:
Identifies all the parent elements within which the described element may appear, listed in alphabetical order by tag name. This information conveys information about where and how often an element is available throughout the schema. The definitions for parent elements may provide additional information about an element's usage.
Attributes:
Identifies all attributes that can be associated with an element. Attributes are represented in camelCase letters in XML coding. The Tag Library uses the convention of preceding an attribute name with an @ symbol (e.g., @localType), following XPath syntax. See the EAC-CPF Attributes section of the tag library for definitions and additional information.
Description and Usage:
This section begins with one or more paragraphs that provide a more thorough description of the element than that found in the Summary, which may be followed by guidance on use. The terms "parent" and "child" are used to indicate hierarchical relationships between elements. Standard terminology is also used to suggest the kind of element being discussed. "Wrapper element" indicates an element that cannot contain text directly; a second, nested element must be opened first. When the schema enforces a specific sequence of child elements, that sequence is indicated. If useful, context-specific guidance for the usage of an element's attributes is given in an "Attribute usage" section. A "See also" section may be provided to indicate additional elements that are similar, easily confused, or otherwise related to the element being described.
Availability:
Indicates, within the context of its parent(s), whether the element is required or optional, and whether or not it is repeatable.
Examples:
Element and attribute descriptions link to an example to indicate how attributes and elements can be used together. Many of the examples are taken from real authory records; others have been specially constructed for the Tag Library. The examples illustrate any required sequences of elements, as in the case of children within <control>, or required attributes such as @part in <nameEntry>. In other cases, the examples simply show what is possible. Some examples have ellipses, either between or within elements, indicating that other elements or text have been omitted. Some elements have multiple examples: one may show very dense markup with numerous attributes while another may illustrate a minimalist approach to the markup. Either approach is valid in EAC-CPF, and it is up to the instance creator to determine the optimal level of markup based on their specific purposes, functional requirements, resources, or consortial guidelines.
Elements
Abstract  
<abstract>
Summary:
An optional element within narrative elements such as <biogHist> that contains a brief summary of the information contained within the narrative element as a whole.
May contain:
[text]
reference 0..n
referringString 0..n
span 0..n
May occur within:
biogHist
Description and Usage:
The <abstract> is a brief synopsis of the information in the narrative element that it is used with. Its purpose is to help readers quickly identify the most important aspects in each context. The content within this element may also be harvested by other systems to provide explanatory context when appearing e.g. in a set of search results.
<abstract> may include one or more <reference> elements to point to external resources that provide additional descriptive data. It may furthermore include one or more <referringString> elements to emphasize entities' names as part of the descriptive texts and to point to external vocabularies for more information about these, where applicable.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Address  
<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:
addressLine 1..n
May occur within:
place
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 <label> 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.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Address Line  
<addressLine>
Summary:
A required child element of <address> used for recording one line of a postal or other address.
Attribute usage:
Use the optional @addressLineType attribute to encode the part of the address that the <addressLine> refers to, for example "street".
Use the optional @addressLineTypeEncoding in <control> to specify the source or rules for values supplied in @addressLineType.
May contain:
[text]
May occur within:
address
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.
Attribute usage:
Use the optional @addressLineType attribute to encode the part of the address that the <addressLine> refers to, for example "street".
Use the optional @addressLineTypeEncoding in <control> to specify the source or rules for values supplied in @addressLineType.
Attributes:
addressLineType Optional
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Agency Code  
<agencyCode>
Summary:
An optional child element of <maintenanceAgency> that provides a code for the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
Attribute usage:
Use @status with values such as “authorized” or “alternative” to declare whether the <agencyCode> is using an authorized value, e.g. a registered ISIL code, or an alternative code. Use @statusEncoding in <control> to specify the source or rules for values supplied in @status.
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 form a globally unique identifier for the EAS instance.
May contain:
[text]
May occur within:
maintenanceAgency
Description and Usage:
Use <agencyCode> to record a code indicating the institution or service responsible for the creation, maintenance and/or dissemination of the EAS instance. Use of <agencyCode> is recommended, as the combination of <agencyCode> and the required <recordId> can provide a globally unique identifier for the instance.
<maintenanceAgency> must include one or both of <agencyCode> and <agencyName>.
It is recommended that the code follows 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>.
Attribute usage:
Use @status with values such as “authorized” or “alternative” to declare whether the <agencyCode> is using an authorized value, e.g. a registered ISIL code, or an alternative code. Use @statusEncoding in <control> to specify the source or rules for values supplied in @status.
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
status Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, not repeatable
Examples:
See <control> encoding
Agency Name  
<agencyName>
Summary:
An optional child element of <maintenanceAgency> that provides the name of the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
See also:
Use <agencyCode> to record a code representing the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
May contain:
[text]
May occur within:
maintenanceAgency
Description and Usage:
Use <agencyName> to record the name of the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS 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 EAS instance in multiple languages or name settings. If <agencyName> is repeated it is recommended to indicate the language of each name using @languageOfElement.
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Agent  
<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 EAS instance's maintenance history, such as its creation, modification, or deletion. Also available in <narrativeEvent> to name a person, institution, or other type of agent of importance to the history of the CPF entity being described.
Attribute usage:
Use the @agentType attribute to specify whether the agent is, for example, a "corporateBody", "mechanism", or "person". Use the optional @agentTypeEncoding in <control> to specify the source or rules for values supplied in @agentType.
Use the attributes @valueURI, @vocabularySource, and @vocabularySourceURI with <agent> when referencing an entry of an external vocabulary, thesaurus, ontology applicable to the agent overall. In case of referencing different vocabularies or different entries within the same vocabulary for the name or the role of the agent, use the three attributes with the sub-elements <label> or <role> directly.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
label 1..n
placeName 0..n
relationship 0..n
role 0..n
May occur within:
maintenanceEvent, narrativeEvent
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 EAS instance, and the style sheet used to update an instance to a new version of the EAS. Each <maintenanceEvent> element must have a child <agent> element. Use <agent> as an optional sub-element in <narrativeEvent> to name a person, institution, or other type of agent of importance to a specific event in the history of the CPF entity being described.
The prescribed order of all child elements (both required and optional) is:
<label>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<role>
<relationship>
<descriptiveNote>
Attribute usage:
Use the @agentType attribute to specify whether the agent is, for example, a "corporateBody", "mechanism", or "person". Use the optional @agentTypeEncoding in <control> to specify the source or rules for values supplied in @agentType.
Use the attributes @valueURI, @vocabularySource, and @vocabularySourceURI with <agent> when referencing an entry of an external vocabulary, thesaurus, ontology applicable to the agent overall. In case of referencing different vocabularies or different entries within the same vocabulary for the name or the role of the agent, use the three attributes with the sub-elements <label> or <role> directly.
Attributes:
agentType Optional
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Within <maintenanceEvent>: required, not repeatable
Within <narrativeEvent>: optional, repeatable
Examples:
See <control> encoding
Alternative Set  
<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:
setComponent 1..n
May occur within:
cpfDescription
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:
audience Optional
conventionDeclarationReference Optional
languageOfElement Optional
id Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <alternativeSet> encoding
Biography or History  
<biogHist>
Summary:
A concise essay and/or chronology that provides biographical or historical information about the EAC-CPF entity.
May contain:
abstract 0..1
formattingExtension 0..1
narrativeEvent 0..n
p 0..n
May occur within:
description
Description and Usage:
<biogHist> includes significant details about the life of an individual or family, or the administrative history of a corporate body.
Use the element <abstract> to provide a brief summary of the information encoded in <biogHist> that could be extracted for inclusion in a remote source, such as a MARC record. Use the repeatable <p> element to structure longer texts in several paragraphs. If required and suitable, use <formattingExtension> to make use of more detailed formatting options such as lists, tables, or section headers in XHTML and to accommodate greater complexity in expressing or representing the biography or history of the CPF entity. Use <narrativeEvent> to provide a chronology of the biography or history of the entity.
The prescribed order of all child elements (both required and optional) is:
<abstract> (if used)
<formattingExtension> or <p>
<narrativeEvent>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Cited Range  
<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:
source
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.
Attribute usage:
Use the optional @unit attribute to specify the format that the <citedRange> refers to, for example page number or volume number.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
unit Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Component Entry  
<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:
setComponent
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <alternativeSet> encoding
Contact  
<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:
contactLine 1..n
May occur within:
place
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.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Contact Line  
<contactLine>
Summary:
A required child element of <contact> used for recording one line of contact details or digital addresses.
Attribute usage:
Use the optional @contactLineType attribute to encode the type of contact detail that the <contactLine> refers to, for example "phoneNumber".
Use @contactLineTypeEncoding in <control> to specify the source or rules for values supplied in @contactLineType.
May contain:
[text]
May occur within:
contact
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.
Attribute usage:
Use the optional @contactLineType attribute to encode the type of contact detail that the <contactLine> refers to, for example "phoneNumber".
Use @contactLineTypeEncoding in <control> to specify the source or rules for values supplied in @contactLineType.
Attributes:
audience Optional
contactLineType Optional
conventionDeclarationReference Optional
href Optional
id Optional
languageOfElement Optional
linkRole Optional
linkTitle Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Control  
<control>
Summary:
A required child element of the root element that contains information about the creation, maintenance, status and the rules and authorities used in the composition of the EAS instance.
Attribute usage:
Use the optional @maintenanceStatus, @publicationStatus, and @detailLevel attributes to document the current version status of the EAS instance, its current editorial status and the current level of detail included in its descriptive sections.
Use the optional encoding attributes such as @countryEncoding, @maintenanceEventTypeEncoding or @relationTypeEncoding to specify the source or rules for values supplied in those attributes used throughout the EAS instance that rely either on code lists from ISO standards or make use of the value lists defined and maintained by the Technical Subcommittee on Encoded Archival Standards (TS-EAS). Should you decide to use other authorized value lists in these attributes instead, it is highly recommended to indicate this by using the "other..." value in the encoding attributes and to name and refer to these other value lists in <conventionDeclaration> to still enable semantic interoperability.
May contain:
conventionDeclaration 0..n
languageDeclaration 0..n
localTypeDeclaration 0..n
maintenanceAgency 1..1
maintenanceHistory 1..1
otherRecordId 0..n
recordId 1..1
rightsDeclaration 0..n
sources 0..1
May occur within:
eac
Description and Usage:
This required wrapper element within the root element of an EAS instance contains the information necessary to manage the instance itself. 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 the creation, maintenance, and disposition of the instance, as applicable, in <maintenanceHistory>.
There are optional elements available to declare languages, rules, conventions and sources used in the EAS instance and licensing information about the EAS instance itself. Local types for certain elements used throughout the EAS 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 EAS instance.
<maintenanceAgency> - Required. Contains the name and coded information about the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
<maintenanceHistory> - Required. Contains information about the date, type and events within the life cycle of an EAS instance.
<sources> - Optional. Contains information about the sources consulted in creating the descriptive parts of the EAS 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 EAS instance.
<languageDeclaration> - Optional. Contains coded and natural language information about the language or languages of the EAS instance.
<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 EAS instance.
<rightsDeclaration> - Optional. Contains information about the usage rights of the EAS instance.
Attribute usage:
Use the optional @maintenanceStatus, @publicationStatus, and @detailLevel attributes to document the current version status of the EAS instance, its current editorial status and the current level of detail included in its descriptive sections.
Use the optional encoding attributes such as @countryEncoding, @maintenanceEventTypeEncoding or @relationTypeEncoding to specify the source or rules for values supplied in those attributes used throughout the EAS instance that rely either on code lists from ISO standards or make use of the value lists defined and maintained by the Technical Subcommittee on Encoded Archival Standards (TS-EAS). Should you decide to use other authorized value lists in these attributes instead, it is highly recommended to indicate this by using the "other..." value in the encoding attributes and to name and refer to these other value lists in <conventionDeclaration> to still enable semantic interoperability.
Attributes:
addressLineTypeEncoding Optional (values limited to: EASList, otherAddressLineTypeEncoding)
agentTypeEncoding Optional (values limited to: EASList, otherAgentTypeEncoding)
audience Optional
audienceEncoding Optional (values limited to: EASList, otherAudienceEncoding)
contactLineTypeEncoding Optional (values limited to: EASList, otherContactLineTypeEncoding)
countryEncoding Optional (values limited to: iso3166-1-alpha-2, iso3166-1-alpha-3, iso3166-1-numeric, iso3166-2, iso3166-3, otherCountryEncoding)
dateEncoding Optional (values limited to: iso8601, otherDateEncoding)
detailLevel Optional
detailLevelEncoding Optional (values limited to: EASList, otherDetailLevelEncoding)
id Optional
identityTypeEncoding Optional (values limited to: EASList, otherIdentityTypeEncoding)
languageEncoding Optional (values limited to: ietf-bcp-47, iso639-1, iso639-2, iso639-2b, iso639-2t, iso639-3, iso639-5, otherLanguageEncoding)
languageOfElement Optional
maintenanceEventTypeEncoding Optional (values limited to: EASList, otherMaintenanceEventTypeEncoding)
maintenanceStatus Optional
maintenanceStatusEncoding Optional (values limited to: EASList, otherMaintenanceStatusEncoding)
placeTypeEncoding Optional (values limited to: EASList, otherPlaceTypeEncoding)
publicationStatus Optional
publicationStatusEncoding Optional (values limited to: EASList, otherPublicationStatusEncoding)
referredEntityTypeEncoding Optional (values limited to: EASList, otherReferredEntityTypeEncoding)
relationTypeEncoding Optional (values limited to: EASList, otherRelationTypeEncoding)
repositoryEncoding Optional (values limited to: iso15511, otherRepositoryEncoding)
scriptEncoding Optional (values limited to: iso15924, otherScriptEncoding)
scriptOfElement Optional
statusEncoding Optional (values limited to: EASList, otherStatusEncoding)
target Optional
targetTypeEncoding Optional (values limited to: EASList, otherTargetTypeEncoding)
Availability:
Required, not repeatable
Examples:
See <control> encoding
Convention Declaration  
<conventionDeclaration>
Summary:
An optional child element of <control>, used to declare the rules or conventions, including authorized controlled vocabularies and thesauri, applied in creating the EAS instance.
See also:
Use <localTypeDeclaration> to indicate any local or consortial value lists that you might use with @localType throughout the EAS instance.
May contain:
descriptiveNote 0..1
reference 1..1
shortCode 0..1
May occur within:
control
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 EAS 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>.
Use <conventionDeclaration> to name and refer to other authorized value lists, if you use these instead of the EAS lists or ISO standards available with the optional encoding attributes in <control> (e.g. @countryEncoding, @maintenanceEventTypeEncoding or @relationTypeEncoding). It is recommended that <reference> includes a link to these other value lists to still enable semantic interoperability.
The prescribed order of all child elements (both required and optional) is:
<reference>
<shortCode>
<descriptiveNote>
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
CPF Description  
<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:
alternativeSet 0..1
description 0..1
identity 1..1
relations 0..1
May occur within:
eac, multipleIdentities
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>
Attribute usage:
Use the @id attribute to identify individual <cpfDescription> elements when using the <multipleIdentities> structure.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <eac>: one of <cpfDescription> or <multipleIdentities> required, not repeatable
Within <multipleIdentities>: two or more <cpfDescription> required, repeatable
Examples:
See <eac> encoding
Date  
<date>
Summary:
An element for encoding a single date relating to the entity or materials being described, or in their relationship to other entities.
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.
Use @status e.g. with the value "unknown" to indicate where a date is unknown.
See also:
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 EAS instance are given in the <eventDateTime> element.
May contain:
[text]
May occur within:
agent, dateSet, demographicDescription, existDates, functionPerformed, legalStatus, localDescription, mandate, narrativeEvent, 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 or another rule for encoding dates as defined by @dateEncoding within <control>. Uncertain or approximate dates can be encoded in @standardDate using Extended Date/Time Format (EDTF).
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.
Use @status e.g. with the value "unknown" to indicate where a date is unknown.
Attributes:
audience Optional
calendar Optional
certainty Optional
conventionDeclarationReference Optional
era Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
notAfter Optional
notBefore Optional
scriptOfElement Optional
standardDate Optional
status Optional
sourceReference Optional
target Optional
Availability:
Within <agent>, <demographicDescription>, <functionPerformed>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <existDates> and <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Within <narrativeEvent>: required, repeatable
Within <dateSet>: at least two of <date> and/or <dateRange> required, repeatable
Examples:
See <description> encoding
Date Range  
<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.
See also:
If the event or relationship has single dates use the <date> 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 EAS instance are given in the <eventDateTime> element.
May contain:
fromDate 0..1
toDate 0..1
May occur within:
agent, dateSet, demographicDescription, existDates, functionPerformed, legalStatus, localDescription, mandate, narrativeEvent, 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.
The prescribed order of all child elements (both required and optional) is:
<fromDate>
<toDate>
Attribute usage:
Use @localType to supply a more specific characterization of the date range.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <agent>, <demographicDescription>, <functionPerformed>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <existDates> and <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Within <dateSet>: at least two of <date> and/or <dateRange> required, repeatable
Examples:
See <identity> encoding
Date Set  
<dateSet>
Summary:
A wrapper element for encoding complex dates that cannot be adequately represented in one <date> or <dateRange>.
May contain:
date or dateRange 2..n
May occur within:
agent, demographicDescription, existDates, functionPerformed, 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <agent>, <demographicDescription>, <functionPerformed>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <existDates>, <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Demographic Description  
<demographicDescription>
Summary:
A required child element of <demographicDescriptions> that can be used to provide demographic information about the CPF entity being described.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..n
placeName 0..n
term 1..n
May occur within:
demographicDescriptions
Description and Usage:
<demographicDescription> is a wrapper element used to encode an index term, using the required child element <term>.
Terms are used within <demographicDescription> to encode demographic information about the CPF entity being described. This could include, but is not limited to, nationality, gender, age group, or religion. They may be drawn from controlled vocabularies or may be natural language terms.
<demographicDescription> must include at least one <term> element. <term> can be repeated within <demographicDescription> 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> 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Demographic Descriptions  
<demographicDescriptions>
Summary:
An optional child element of <description> used to group together one or more <demographicDescription> elements.
May contain:
demographicDescription 1..n
descriptiveNote 0..1
May occur within:
description
Description and Usage:
Use the optional <demographicDescriptions> element to group together one or more occurrences of <demographicDescription>. <demographicDescriptions> must include at least one <demographicDescription> element.
The prescribed order of all child elements (both required and optional) is:
<demographicDescription>
<descriptiveNote>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Description  
<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
demographicDescriptions 0..1
existDates 0..n
functionsPerformed 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:
cpfDescription
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:
<demographicDescriptions>
<functionsPerformed>
<languagesUsed>
<legalStatuses>
<localDescriptions>
<mandates>
<occupations>
<places>
Any of <biogHist>, <existDates>, <generalContext>, and <structureOrGenealogy>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Descriptive Note  
<descriptiveNote>
Summary:
An element used to provide general descriptive information related to its parent element, either as narrative text or encoded in a related standard.
May contain:
objectXMLWrap 0..1
p 1..n
May occur within:
agent, conventionDeclaration, demographicDescription, demographicDescriptions, existDates, functionPerformed, functionsPerformed, 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.
With the optional element <objectXMLWrap>, <descriptiveNote> also allows for the inclusion of information encoded in other formats and standards that add further details to its parent element which could not be encoded in the EAS.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Encoded Archival Context - Corporate Bodies, Persons, and Families  
<eac>
Summary:
The required root element of an EAC-CPF instance.
May contain:
control 1..1
cpfDescription or multipleIdentities 1..1
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:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
Availability:
Required, not repeatable
Examples:
See <eac> encoding
Entity Type  
<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:
identity
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.
Attribute usage:
Use the required @value attribute with one of the values "corporateBody", "family", or "person" to identify the type of entity.
Attributes:
audience Optional
id Optional
target Optional
value Required (values limited to: corporateBody, family, person)
Availability:
Required, not repeatable
Examples:
See <identity> encoding
Maintenance Event Date and Time  
<eventDateTime>
Summary:
A required child element of <maintenanceEvent> that records the date and time of a specific maintenance action for an EAS 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:
maintenanceEvent
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 EAS instance, e.g. in the context of reparative description or as a result of applying Artificial Intelligence models for improving the description.
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.
Attribute usage:
Use @standardDateTime to provide a machine-processable expression of the date or date and time, formulated according to the ISO 8601 standard.
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
standardDateTime Optional
target Optional
Availability:
Required, not repeatable
Examples:
See <control> encoding
Event Description  
<eventDescription>
Summary:
An optional child element of <maintenanceEvent> and <narrativeEvent> that provides the description of a maintenance event in the life of the EAS instance respectively the description of an event in the life of the CPF entity described.
May contain:
[text]
reference 0..n
referringString 0..n
span 0..n
May occur within:
maintenanceEvent, narrativeEvent
Description and Usage:
A child element of <maintenanceEvent> used for describing the maintenance event and of <narrativeEvent> used for describing a chronology of events in the life of the CPF entity described. The element allows a full description of the event to be given alongside information about the time and date of the event, the agent involved, and - in the context of <maintenanceEvent> - the type respectively - in the context of <narrativeEvent> - the place of the event.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <control> and <description> encoding
Dates of Existence  
<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:
date or dateRange or dateSet 1..1
descriptiveNote 0..1
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Formatting Extension  
<formattingExtension>
Summary:
An optional, wrapping element that may be utilized to encode more complex formatting features that are not part of the EAS data model such as lists, tables, nested headers, etc. When using the EAS-provided NVDL Schema validation procedure, this element will require that all elements encoded within are from the XHTML namespace.
May contain:
[Any element that is in a namespace other than the current namespace]
May occur within:
biogHist, generalContext, structureOrGenealogy
Description and Usage:
<formattingExtension> provides the option to embed external namespaces directly within the source file, when complex formatting is required. It should preferably be used for embedding XHTML data.
When using this element, it is recommended that the EAS file is associated with the EAS NVDL for validation purposes.
Attributes:
audience Optional
id Optional
target Optional
Availability:
Optional, not repeatable
In these narrative contexts, the encoder must choose between using a <formattingExtention> element (to wrap XHTML content), or using one or more <p> elements that are defined within the current EAS schema.
From Date  
<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:
dateRange
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.
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.
Attributes:
audience Optional
calendar Optional
certainty Optional
conventionDeclarationReference Optional
era Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
notAfter Optional
notBefore Optional
scriptOfElement Optional
standardDate Optional
status Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <identity> encoding
Function Performed  
<functionPerformed>
Summary:
A required child element of <functionsPerformed> 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:
date or dateRange or dateSet (0..1)
descriptiveNote (0..1)
placeName (0..n)
term (1..n)
May occur within:
functionsPerformed
Description and Usage:
A <functionPerformed> 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.
<functionPerformed> must include at least one <term> element. <term> can be repeated within <functionPerformed> 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Functions Performed  
<functionsPerformed>
Summary:
An optional child element of <description> used for grouping together one or more <functionPerformed> elements.
May contain:
descriptiveNote (0..1)
functionPerformed (1..n)
May occur within:
description
Description and Usage:
Use the optional <functionsPerformed> element to group together one or more occurrences of <functionPerformed>. <functionsPerformed> must include at least one <functionPerformed> element.
The prescribed order of all child elements (both required and optional) is:
<functionPerformed>
<descriptiveNote>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
General Context  
<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:
formattingExtension 0..n
p 0..n
May occur within:
description
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 <formattingExtention> element may be used to accommodate greater complexity in expressing or representing the general context being described. A simpler discursive expression of the general context may be encoded as one or more <p> elements.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Geographic Coordinates  
<geographicCoordinates>
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:
place
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.
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.
Attributes:
audience Optional
conventionDeclarationReference Optional
coordinateSystem Required
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Identity  
<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:
descriptiveNote 0..1
entityType 1..1
identityId 0..n
nameEntry or nameEntrySet 1..n
otherEntityTypes 0..n
May occur within:
cpfDescription
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, such that multiple <cpfDescription> elements are used, 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:
audience Optional
conventionDeclarationReference Optional
id Optional
identityType Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, not repeatable
Examples:
See <eac> encoding
Identity Identifier  
<identityId>
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 EAS instance rather than the entity it describes.
May contain:
[text]
May occur within:
identity
Description and Usage:
<identityId> may be used to record any identifier associated with the CPF entity being described in the EAS instance. Identifiers such as legal identifiers, typically assigned by an authoritative agency, may be recorded in this element. If multiple identifiers are recorded, each should be in its own <identityID>.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Label  
<label>
Summary:
A required child element of <agent>, <place>, and <relation> that indicates the name of the related entity.
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the entity in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource to identify the source where @valueURI comes from, and @vocabularySourceURI to point univocally to the organization system used.
See also:
Use this element in combination with type and role information which can also be encoded within the parent elements of <label>. E.g.: <label>: "John Bianchi", @agentType: "person", <role>: "author".
May contain:
[text]
May occur within:
agent, place, relation
Description and Usage:
Use <label> to indicate the name of the related entity, either in the generic <relation> element or in one of the specific entity elements. Depending on the type of related entity, such a name can also take the form of a numeric denominator.
In <agent>, this is the name of the agent responsible for the creation, modification, or deletion of an EAC-CPF instance, as captured in <maintenanceEvent>.In <place>, this might e.g. be the name of the place where a person was born or an organization was established.
It is recommended to use authorized vocabularies in cases where the element is valorized with a well-known corporation (i.e. "Library of Congress").
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the entity in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource to identify the source where @valueURI comes from, and @vocabularySourceURI to point univocally to the organization system used.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> and <relation> encoding
Language  
<language>
Summary:
An element that identifies the language or communication system used by the entity or in the materials 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.
See also:
Use <writingSystem> to specify, in a human-readable form, the script corresponding to the language.
May contain:
[text]
May occur within:
languageUsed
Description and Usage:
An optional element within <languageUsed> that gives the language or languages used by the 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.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageCode Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Language Declaration  
<languageDeclaration>
Summary:
An optional child element of <control> that indicates the language and script in which an EAS instance is written.
Attribute usage:
Use the required @languageCode to provide a code for the language used in the EAS 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 EAS instance.
Use @scriptOfElement to provide a code for the writing system in which the <languageDeclaration> element is given.
May contain:
descriptiveNote 0..1
May occur within:
control
Description and Usage:
An optional child element of <control> that declares the languages and scripts in which an EAS instance is written in the @languageCode and @scriptCode attributes. Any comments about the languages and scripts in which the EAS instance is written may be included in the optional <descriptiveNote> element. While <languageDeclaration> states the language(s) and script(s) for the EAS instance in general, the @languageOfElement and @scriptOfElement attributes available with all elements may be used to encode language and script information specific to the content of one element in cases where this is different from the overall language(s) and script(s).
Attribute usage:
Use the required @languageCode to provide a code for the language used in the EAS 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 EAS instance.
Use @scriptOfElement to provide a code for the writing system in which the <languageDeclaration> element is given.
Attributes:
audience Optional
id Optional
languageCode Required
languageOfElement Optional
scriptCode Optional
scriptOfElement Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Language Used  
<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:
descriptiveNote 0..1
language 0..n
writingSystem 0..n
May occur within:
languagesUsed
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Languages Used  
<languagesUsed>
Summary:
An optional child element of <description> used for grouping together one or more <languageUsed> elements.
May contain:
descriptiveNote 0..1
languageUsed 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Legal Status  
<legalStatus>
Summary:
A required child element of <legalStatuses> used to encode information about the legal status of a corporate body.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
placeName 0..n
term 1..n
May occur within:
legalStatuses
Description and Usage:
The legal status 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 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Legal Statuses  
<legalStatuses>
Summary:
An optional child element of <description> used to bundle together one or more <legalStatus> element.
May contain:
descriptiveNote 0..1
legalStatus 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Local Description  
<localDescription>
Summary:
A required child element of <localDescriptions> used to extend the descriptive categories to others available in a local system.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
placeName 0..n
term 1..n
May occur within:
localDescriptions
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Local Descriptions  
<localDescriptions>
Summary:
An optional child element of <description> used for grouping together one or more <localDescription> elements.
May contain:
descriptiveNote 0..1
localDescription 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Local Type Declaration  
<localTypeDeclaration>
Summary:
An optional child element of <control> used to declare any local conventions or controlled vocabularies used in @localType in the EAS instance.
See also:
Use <conventionDeclaration> to indicate any more broadly (i.e. nationally or internationally) used rules or conventions, including authorized controlled vocabularies and thesauri, applied in creating the EAS instance.
When using @localType throughout the EAS instance, use @localTypeDeclarationReference in parallel to refer back to the relevant <localTypeDeclaration> via its @id attribute.
May contain:
descriptiveNote 0..1
reference 1..1
shortCode 0..1
May occur within:
control
Description and Usage:
<localTypeDeclaration> specifies the local conventions and controlled vocabularies used in @localType attributes in the EAS instance.
Each additional rule or set of rules, controlled vocabulary, or standard should be contained in a separate <localTypeDeclaration>.
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:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Maintenance Agency  
<maintenanceAgency>
Summary:
A required child element of <control> that identifies the institution or service responsible for the EAS instance.
Attribute usage:
Use @countryCode to indicate a unique code for the country of the maintenance agency.
May contain:
agencyCode 0..1
agencyName 0..n
descriptiveNote 0..1
otherAgencyCode 0..n
May occur within:
control
Description and Usage:
<maintenanceAgency> encodes information about the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
<maintenanceAgency> must include one or both of <agencyCode> or <agencyName> to provide the identifier or 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 or service in relation to the EAS instance may be given in <descriptiveNote>.
The prescribed order of all child elements (both required and optional) is:
<agencyCode> (if used)
<agencyName>
<otherAgencyCode>
<descriptiveNote>
Attribute usage:
Use @countryCode to indicate a unique code for the country of the maintenance agency.
Attributes:
audience Optional
countryCode Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
vocabularySource Optional
vocabularySourceURI Optional
valueURI Optional
Availability:
Required, not repeatable
Examples:
See <control> encoding
Maintenance Event  
<maintenanceEvent>
Summary:
A required child element of <maintenanceHistory> used to record information about maintenance activities in the history of the EAS instance.
Attribute usage:
Use @maintenanceEventType to document the type of maintenance activity that the <maintenanceEvent> is recording. Use @maintenanceEventTypeEncoding in <control> to specify the source or rules for values supplied in @maintenanceEventType.
May contain:
agent 1..1
eventDateTime 1..1
eventDescription 0..n
May occur within:
maintenanceHistory
Description and Usage:
A required child element of <maintenanceHistory>, <maintenanceEvent> is used to record an activity in the creation and ongoing maintenance of an EAS instance, including revisions, updates, and deletions, e.g. as a result of reparative description or the application of Artificial Intelligence models. 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>
Attribute usage:
Use @maintenanceEventType to document the type of maintenance activity that the <maintenanceEvent> is recording. Use @maintenanceEventTypeEncoding in <control> to specify the source or rules for values supplied in @maintenanceEventType.
Attributes:
audience Optional
id Optional
languageOfElement Optional
maintenanceEventType Optional
scriptOfElement Optional
target Optional
Availability:
Required, repeatable
Examples:
See <control> encoding
Maintenance History  
<maintenanceHistory>
Summary:
A required child element of <control> that captures the history of the creation and maintenance of the EAS instance.
See also:
Use @maintenanceStatus within <control> to reflect the current drafting status of the EAS instance as recorded in <maintenanceHistory>.
May contain:
maintenanceEvent 1..n
May occur within:
control
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 EAS 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:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
Availability:
Required, not repeatable
Examples:
See <control> encoding
Mandate  
<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:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
placeName 0..n
term 1..n
May occur within:
mandates
Description and Usage:
<mandate> is used to identify the source of authority or mandate for the entity being described 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Mandates  
<mandates>
Summary:
An optional child element of <description> used for grouping together one or more <mandate> elements.
May contain:
descriptiveNote 0..1
mandate 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Multiple Identities  
<multipleIdentities>
Summary:
A child element of <eac> used to group together more than one <cpfDescription> within a single EAC-CPF instance.
May contain:
cpfDescription 2..n
May occur within:
eac
Description and Usage:
A grouping element used to encode more than one <cpfDescription> in a single EAC-CPF instance.
The <multipleIdentities> element can be used to 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:
audience Optional
id Optional
target Optional
Availability:
Within <eac>: one of <cpfDescription> or <multipleIdentities> required, not repeatable
Examples:
See <eac> encoding
Name Entry  
<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:
part 1..n
useDates 0..n
May occur within:
identity, nameEntrySet
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 forms of a name, for example official and non-official forms of the name in different languages and/or scripts.
When <nameEntry> occurs within <nameEntrySet> it is used to record two or more forms of a name, for example official and non-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>
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>.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
preferredForm Optional (values limited to: false, true)
scriptOfElement Optional
sourceReference Optional
status Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet> required, repeatable
Within <nameEntrySet>: two or more <nameEntry> required, repeatable
Examples:
See <identity> encoding
Name Entry Set  
<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 and non-official forms of the name in different languages and/or scripts).
May contain:
nameEntry 2..n
useDates 0..n
May occur within:
identity
Description and Usage:
A wrapper element used to group two or more <nameEntry> elements representing parallel or other forms of the name for the same CPF entity which are used at the same time (e.g., official and non-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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet> required, repeatable
Examples:
See <identity> encoding
Narrative Event  
<narrativeEvent>
Summary:
An optional child element of <biogHist> used to record chronological events in the history or biography of the CPF entity.
May contain:
agent 0..n
date 1..n
eventDescription 0..n
placeName 0..n
May occur within:
biogHist
Description and Usage:
Use <narrativeEvent> to record a chronology of life events of the CPF entity. This may include any event between the birth and the death of a person or between the foundation and the closure of an organization.
The type of each event may be defined with the attribute @localType. Use @localTypeDeclarationReference to refer to a <localTypeDeclaration> within <control> where you have defined those types. Use the required child element <date> to record when the event took place. Using the optional child element <agent> to provide information about who or what carried out, or was responsible for the activity is highly recommended. The child element <placeName> may be used to provide information about where the event happened. Information about the event may be described in <eventDescription>.
The prescribed order of all child elements (both required and optional) is:
<date>
<agent>
<placeName>
<eventDescription>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Object XML Wrap  
<objectXMLWrap>
Summary:
An optional child element of <descriptiveNote>, <relation>, <setComponent>, and <source> that allows for the inclusion of XML encoding from any other XML namespace.
May contain:
[any element from any namespace]
May occur within:
descriptiveNote, relation, setComponent, source
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.
If interoperability is not a main objective in a specific application context of the EAS, it is also possible to encode data in XML without a namespace within the <objectXMLWrap> element.
<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:
audience Optional
id Optional
target Optional
Availability:
Optional, not repeatable
Narrative Event  
<narrativeEvent>
Summary:
An optional child element of <biogHist> used to record chronological events in the history or biography of the CPF entity.
May contain:
agent 0..n
date 1..n
eventDescription 0..n
placeName 0..n
May occur within:
biogHist
Description and Usage:
Use <narrativeEvent> to record a chronology of life events of the CPF entity. This may include any event between the birth and the death of a person or between the foundation and the closure of an organization.
The type of each event may be defined with the attribute @localType. Use @localTypeDeclarationReference to refer to a <localTypeDeclaration> within <control> where you have defined those types. Use the required child element <date> to record when the event took place. Using the optional child element <agent> to provide information about who or what carried out, or was responsible for the activity is highly recommended. The child element <placeName> may be used to provide information about where the event happened. Information about the event may be described in <eventDescription>.
The prescribed order of all child elements (both required and optional) is:
<date>
<agent>
<placeName>
<eventDescription>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Occupation  
<occupation>
Summary:
A required child element of <occupations> that provides information about an occupation of the CPF entity being described.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
placeName 0..n
term 1..n
May occur within:
occupations
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
Occupations  
<occupations>
Summary:
An optional child element of <description> used for grouping together one or more <occupation> elements.
May contain:
descriptiveNote 0..1
occupation 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Other Agency Code  
<otherAgencyCode>
Summary:
An optional child element of <maintenanceAgency> that provides an alternative code for the institution or service responsible for the EAS instance.
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the code in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system.
Use @vocabularySource to identify the source where @valueURI comes from, and @vocabularySourceURI to point univocally to the organization system used.
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:
maintenanceAgency
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 EAS 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.
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the code in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system.
Use @vocabularySource to identify the source where @valueURI comes from, and @vocabularySourceURI to point univocally to the organization system used.
Use @localType to specify the type of code being provided.
Use @status to encode whether the <otherAgencyCode> is an authorized or alternative code.
Attributes:
audience Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
scriptOfElement Optional
status Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Other Entity Type  
<otherEntityType>
Summary:
A required and repeatable child element of <otherEntityTypes> used to encode additional or alternative entity types.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
placeName 0..n
term 1..n
May occur within:
otherEntityTypes
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <identity> encoding
Other Entity Types  
<otherEntityTypes>
Summary:
An optional child element of <identity> used for grouping one or more <otherEntityType> elements.
May contain:
descriptiveNote 0..1
otherEntityType 1..n
May occur within:
identity
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <identity> encoding
Other Record Identifier  
<otherRecordId>
Summary:
An optional child element of <control> that encodes any local identifier for the EAS instance.
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the alternative identifier in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system.
Use @vocabularySource to identify the source where @valueURI comes from, e.g, the institution or service providing the associated record identifier, and @vocabularySourceURI to point univocally to the organization system used, if available.
May contain:
[text]
May occur within:
control
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 EAS 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 EAS instance.
Attribute usage:
Use @valueURI to provide the sequence of characters (e.g., URI) that uniquely identifies the alternative identifier in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system.
Use @vocabularySource to identify the source where @valueURI comes from, e.g, the institution or service providing the associated record identifier, and @vocabularySourceURI to point univocally to the organization system used, if available.
Attributes:
audience Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Paragraph  
<p>
Summary:
A general purpose element used to encode blocks of text.
May contain:
[text]
reference 0..n
referringString 0..n
span 0..n
May occur within:
biogHist, descriptiveNote, generalContext, structureOrGenealogy
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <descriptiveNote>: required, repeatable.
Within all other parents: optional, repeatable.
In all parents except <descriptiveNote>, the encoder must choose between using one or more <p> elements that are defined within the current EAS schema, or using a <formattingExtention> element (to wrap XHTML content) for more complex formatting.
Examples:
See <description> encoding
Part  
<part>
Summary:
A required and repeatable child of <nameEntry> used to distinguish components of a name.
Attribute usage:
The designation of the information contained in the <part> element can be specified by the attribute @localType.
May contain:
[text]
May occur within:
nameEntry
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.
Attribute usage:
The designation of the information contained in the <part> element can be specified by the attribute @localType.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Examples:
See <identity> encoding
Place  
<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:
address 0..n
contact 0..n
date or dateRange or dateSet 0..1
descriptiveNote 0..1
geographicCoordinates 0..n
label 1..n
role 0..n
relationship 0..n
May occur within:
places
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, the role that the place has with regard to the entity described, the relationship between both as well as a temporal dimension of that relationship.
<place> must include at least one <label> to name the geographic feature or location that is related to the entity being described. The <role> element is available to specify the nature of the place in relation with the entity being described, e.g. "birthplace" for CPF entities or "placeOfStorage" for record resources, and its use is strongly recommended. The @placeType attribute may be used to classify the type of place for clarification, e.g., indicating whether the place is a city or town or a first or second-order administrative division. Use <relationship> to describe the nature of connection between the place and the entity being described more generally. Terms in these elements may be drawn from controlled vocabularies or may be natural language terms. These controlled vocabularies can be identified with the @vocabularySource and/or @vocabularySourceURI attributes.
The <address> element is available for specifying a postal or other address, while a digital address or other contact information can be encoded using the <contact> element. Specific coordinates for the geographic feature or location may be provided using the element <geographicCoordinates>.
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:
<label>
One of <date>, <dateRange>, or <dateSet>
<role>
<relationship>
One or more of <address>, <contact> and <geographicCoordinates>
<descriptiveNote>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
placeType Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Within <places>: required, repeatable.
Examples:
See <description> encoding
Place Name  
<placeName>
Summary:
An optional element used to encode the name of a place or geographic feature that is of importance in the relation between the CPF entity and related named entities or in the history of the CPF entity being described.
Attribute usage:
Use the attributes @valueURI, @vocabularySource, and @vocabularySourceURI with <placeName> when referencing an entry of an external vocabulary, thesaurus, ontology.
See also:
Within <place>, the required element <label> is used to capture the name of the geographic feature or location. This is to align with the element <relation> which also uses <label> to name the related entity. Use @target within <placeName> to link to the @id attribute of a <place>, which might include more detailed information about the same place.
May contain:
[text]
May occur within:
agent, demographicDescription, functionPerformed, legalStatus, localDescription, mandate, narrativeEvent, occupation, otherEntityType, relation
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.
Use <placeName> within <agent>, <demographicDescription>, <functionPerformed>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType> and <relation> to encode the name of a place or geographic feature that is of importance in the term's or the entity's relation with the CPF entity being described. Use <placeName> within <narrativeEvent> to encode the geographic dimension of the event.
Attribute usage:
Use the attributes @valueURI, @vocabularySource, and @vocabularySourceURI with <placeName> when referencing an entry of an external vocabulary, thesaurus, ontology.
Attributes:
audience Optional
conventionDeclarationReference Optional
countryCode Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Places  
<places>
Summary:
An optional child element of <description> used for grouping together one or more <place> elements.
May contain:
descriptiveNote 0..1
place 1..n
May occur within:
description
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <description> encoding
Record Identifier  
<recordId>
Summary:
A required child element of <control> that designates a unique identifier for the EAS instance.
See also:
Use <agencyCode> in combination with <recordId> to provide a globally unique identifier for the EAS instance.
Any alternative or additional record identifiers may be recorded in <otherRecordId>.
May contain:
[text]
May occur within:
control
Description and Usage:
<recordId> is used for recording a unique identifier for the EAS 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 (e.g. HTTP URI, DOI, PURL, or UUID), or in combination with <agencyCode>, which is an optional element within <maintenanceAgency>.
<recordId> cannot be empty.
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
Availability:
Required, not repeatable
Examples:
See <control> encoding
Reference  
<reference>
Summary:
An element that cites an external resource.
Attribute usage:
Use @href to link to the cited resource, in case this is available online.
See also:
<reference> is used for external linking only. If any internal linking is required, use the @target attribute to point to the @id of the referenced element.
May contain:
[text]
referringString 0..n
span 0..n
May occur within:
abstract, conventionDeclaration, eventDescription, localTypeDeclaration, p, rightsDeclaration, source
Description and Usage:
An element used for referencing external resources that have been used to compile the EAS instance, that provide additional context to the EAS 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.
In <abstract>, <eventDescription> and <p>, <reference> may be used to reference any external resources that provide additional context to the content of these elements, which may include multiple <reference> elements.
Attribute usage:
Use @href to link to the cited resource, in case this is available online.
Attributes:
audience Optional
conventionDeclarationReference Optional
href Optional
id Optional
languageOfElement Optional
linkRole Optional
linkTitle Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Within <conventionDeclaration>, <localTypeDeclaration>, <rightsDeclaration>: required, not repeatable
Within <source>: required, repeatable
Within <abstract>, <eventDescription>, <p>: optional, repeatable
Examples:
See <control> encoding
Relation  
<relation>
Summary:
A required child element of <relations> for describing a relationship between the entity or records described and a related entity.
May contain:
date or dateRange or dateSet 0..1
descriptiveNote 0..1
label 1..n
objectXMLWrap 0..1
placeName 0..n
role 0..n
May occur within:
relations
Description and Usage:
<relation> records descriptive information about a relationship between the CPF entity being described and other agents as well as all other types of entities like functions and records.
Use the required child element <label> to provide a textual identification of the related entity, such as a name or a title. Use the optional attribute @targetType to classify the type of the related entity, the optional attribute @relationType to specify the type of relation in its most generic form, and the optional child element <role> to specify the role of the related entity towards the entity or the materials being described more concretely.
It is recommended that the terms used in <label> and <role> be taken from an authorized vocabulary. When not using the EAS value lists for @relationType and @targetType, any alternative value lists should ideally also be taken from authorized vocabularies.
Use <objectXMLWrap> to embed XML documenting the related entity from any other namespace. Use <date>, <dateRange>, or <dateSet> for specifying the time period of the relationship and <placeName> 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:
<label>
One of <date>, <dateRange>, or <dateSet>
<placeName>
<role>
<descriptiveNote>
<objectXMLWrap>
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
relationType Optional
scriptOfElement Optional
sourceReference Optional
target Optional
targetType Optional
Availability:
Required, repeatable
Examples:
See <relations> encoding
Relations  
<relations>
Summary:
An optional element that groups one or more <relation> elements, which identify external entities and characterize the nature of their relationships to the entity or records being described.
May contain:
descriptiveNote 0..1
relation 1..n
May occur within:
cpfDescription
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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <relations> encoding
Relationship  
<relationship>
Summary:
A child element of <agent> and <place> used to specify the type of relationship that these entities have with the EAS instance respectively with the entity being described.
Attribute usage:
Use @valueURI to provide a number, code, or string (e.g., URI) that uniquely identifies the relationship in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource and/or @vocabularySourceURI to name and/or point to the organization system used.
See also:
Use <role> to more specifically indicate the role of the related entity towards the entity being described in the EAS instance respectively towards the EAS instance itself.
May contain:
[text]
May occur within:
agent, place
Description and Usage:
Use <relationship> within <agent> and <place> to specify the type of relation that these entities have with the entity being described within the EAS instance, e.g. "maintenance" for the agent named in <maintenanceEvent>, "residence" for places. To more specifically indicate the role of the related entity towards the entity being described in the EAS instance (e.g. "archivist" or "volunteer" for the agent in <maintenanceEvent>, "birthplace" or "currentResidence" for places), the element <role> should be used instead of or in combination with <relationship>.
The <relationship> element contains a textual description of the relation. It is recommended that values used in <relationship> be taken from an authorized vocabulary.
Attribute usage:
Use @valueURI to provide a number, code, or string (e.g., URI) that uniquely identifies the relationship in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource and/or @vocabularySourceURI to name and/or point to the organization system used.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, Repeatable
Examples:
See <control> encoding
Referring String  
<referringString>
Summary:
An element for marking words or phrases in a longer text as named entities.
Attribute usage:
Use @referredEntityType to indicate the type of entity that is named in the narrative text and @referredEntityRelationship to specify the relation between that named entity and the entity being described in the EAS instance. Use @normalizedForm to provide a standardized form of the name following e.g. an external vocabulary.
Use @valueURI to provide a number, code, or string (e.g., URI) that uniquely identifies the entity in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource and/or @vocabularySourceURI to name and/or point to the organization system used.
See also:
Only fall back on using <referringString> in the contexts mentioned above.
May contain:
[text]
May occur within:
abstract, eventDescription, p, reference
Description and Usage:
Use <referringString> in longer texts to indicate that certain words or phrases within these texts represent named entities such as persons, organizations, places, functions, resources, etc.
Use <referringString> e.g. when the identification of such named entities within existing archival descriptions is the result of some natural language processing or when capturing the results of named entity recognition having been conducted as part of Optical Character Recognition or Handwritten Text Recognition tasks.
Attribute usage:
Use @referredEntityType to indicate the type of entity that is named in the narrative text and @referredEntityRelationship to specify the relation between that named entity and the entity being described in the EAS instance. Use @normalizedForm to provide a standardized form of the name following e.g. an external vocabulary.
Use @valueURI to provide a number, code, or string (e.g., URI) that uniquely identifies the entity in a controlled vocabulary, taxonomy, ontology, or other knowledge organization system. Use @vocabularySource and/or @vocabularySourceURI to name and/or point to the organization system used.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
normalizedForm Optional
referredEntityRelationship Optional
referredEntityType Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <relations> encoding
Rights Declaration  
<rightsDeclaration>
Summary:
An optional child element of <control> that indicates a standard rights statement associated with the EAS instance.
May contain:
descriptiveNote 0..1
reference 1..1
shortCode 0..1
May occur within:
control
Description and Usage:
Use <rightsDeclaration> to provide structured information about the usage rights of the EAS instance. <rightsDeclaration> should only be used to reference shared published licenses, such as Creative Commons, RightsStatements.org, or published locally-defined licenses. In cases where different licenses apply depending on the type of descriptive metadata, e.g. the Public Domain Mark for any factual metadata, but CC BY for any more narrative metadata that requires an additional research effort in its creation such as scope and content notes or biographies of records creators, these can be encoded in two separate <rightsDeclaration> elements. Include an @id for each <rightsDeclaration> element and use @target with descriptive elements to point to the license that applies.
<reference> must be used to provide a machine-readable reference to a license statement (for example, a 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:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Role  
<role>
Summary:
An optional child element of <agent>, <place>, and <relation> that indicates the role of the related entity towards the entity being described in the EAS instance or the EAS instance itself.
See also:
Use the element <label> to encode the related entity’s name.
May contain:
[text]
May occur within:
agent, place, relation
Description and Usage:
Use <role> to indicate the role of the related entity towards the entity being described in the EAS instance or the EAS instance itself. It is recommended that the terms in <role> be taken from authorized vocabularies.
<role> might be used in combination with the specific type attribute available with each of the elements where <role> is available. While these attributes provide a generic typology of each entity class, e.g. "corporateBody", "person", and "family" for @agentType, <role> looks more specifically at the related entity itself in a certain context.
Furthermore, <role> may be used in combination with <relationship> which is available in <agent> and and <place>. While <relationship> is used to encode a more general denominator for the relation between the related entity and the entity being described in the EAS instance, e.g. "creation" or "authorship" for agents, <role> allows to be more specific to the individual related entity, e.g. by assigning the role of "archivist" to one <agent> and the role of "volunteer" to another.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Optional, repeatable
Examples:
See <relation> encoding
Set Component  
<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:
componentEntry 0..n
descriptiveNote 0..1
objectXMLWrap 0..1
May occur within:
alternativeSet
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.
Attribute usage:
Use @href to provide a general reference to alternative sets.
Attributes:
audience Optional
conventionDeclarationReference Optional
href Optional
id Optional
languageOfElement Optional
linkRole Optional
linkTitle Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Examples:
See <alternativeSet> encoding
Short Code  
<shortCode>
Summary:
An optional element for encoding the shortened form of the rule, code list, vocabulary, rights statement etc applied in creating and maintaining the EAS instance and captured in <conventionDeclaration>, <localTypeDeclaration> and <rightsDeclaration>.
May contain:
[text]
May occur within:
conventionDeclaration, localTypeDeclaration, rightsDeclaration
Description and Usage:
Use <shortCode> within <conventionDeclaration> or <localTypeDeclaration> to identify the shortened form, acronym, or code for a thesaurus, controlled vocabulary, or another standard used in creating the EAS 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 Field Index to Source Code Usage (http://www.loc.gov/marc/sourcelist/).
Attributes:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <control> encoding
Source  
<source>
Summary:
A required and repeatable child element of <sources> used to identify a particular source of evidence used for the establishment of the descriptive parts in an EAS instance.
Attribute usage:
In the case of online sources, use @href to provide a URL. In case an online source is identified via a persistent identifier (PID) such as a DOI or and ARK, use @valueURI instead and indicate the PID scheme in @vocabularySource and/or @vocabularySourceURI.
May contain:
citedRange 0..n
descriptiveNote 0..1
objectXMLWrap 0..1
reference 1..n
May occur within:
sources
Description and Usage:
Use <source> to cite a published resource used in creating the descriptive parts of the EAS instance. Use the required child element <reference>to include a textual identification of the source. 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 other namespace.
The prescribed order of all child elements (both required and optional) is:
<reference>
<citedRange>
<descriptiveNote>
<objectXMLWrap>
Attribute usage:
In the case of online sources, use @href to provide a URL. In case an online source is identified via a persistent identifier (PID) such as a DOI or and ARK, use @valueURI instead and indicate the PID scheme in @vocabularySource and/or @vocabularySourceURI.
Attributes:
audience Optional
id Optional
href Optional
languageOfElement Optional
linkRole Optional
linkTitle Optional
scriptOfElement Optional
target Optional
valueURI Optional
vocabularySource Optional
vocabularySourceURI Optional
Availability:
Required, repeatable
Examples:
See <control> encoding
Sources  
<sources>
Summary:
An optional child element of <control> that groups one or more <source>s of evidence used in the descriptive parts in the EAS instance.
May contain:
descriptiveNote 0..1
source 1..n
May occur within:
control
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:
audience Optional
id Optional
languageOfElement Optional
scriptOfElement Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <control> encoding
span  
<span>
Summary:
Specifies the beginning and the end of a span of text.
Attribute usage:
Use the optional @style attribute to specify an arbitrary stylistic difference.
May contain:
[text]
May occur within:
abstract, eventDescription, reference, p
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.
Attribute usage:
Use the optional @style attribute to specify an arbitrary stylistic difference.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
style Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <control> encoding
Structure or Genealogy  
<structureOrGenealogy>
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:
p or formattingExtension 0..n
May occur within:
description
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 <formattingExtention> element may be used to accommodate greater complexity in expressing or representing the structure(s) or genealogy being described. A simpler discursive expression of the structure(s) or genealogy may be encoded as one or more <p> elements.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
Term  
<term>
Summary:
An element used to encode a descriptive term in accordance with authorized vocabularies or local rules.
May contain:
[text]
May occur within:
demographicDescription, functionPerformed, legalStatus, localDescription, mandate, occupation, otherEntityType
Description and Usage:
<term> is a required child element of <demographicDescription>, <functionPerformed>, <legalStatus>, <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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Required, repeatable
Examples:
See <description> encoding
To Date  
<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 end 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:
dateRange
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.
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 end 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.
Attributes:
audience Optional
calendar Optional
certainty Optional
conventionDeclarationReference Optional
era Optional
id Optional
languageOfElement Optional
localType Optional
localTypeDeclarationReference Optional
maintenanceEventReference Optional
notAfter Optional
notBefore Optional
scriptOfElement Optional
standardDate Optional
status Optional
sourceReference Optional
target Optional
Availability:
Optional, not repeatable
Examples:
See <identity> encoding
Dates of Use  
<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 entity being described.
May contain:
date or dateRange or dateSet 1..1
May occur within:
nameEntry, nameEntrySet
Description and Usage:
Within <nameEntry>, <useDates> provides the dates during which the name was used for or by the entity being described. 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:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <identity> encoding
Writing System  
<writingSystem>
Summary:
An optional child element of <languageUsed> that identifies the writing script for a language used by the described entity.
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:
languageUsed
Description and Usage:
An optional element within <languageUsed> that gives the main script used by the entity being described.
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.
Attributes:
audience Optional
conventionDeclarationReference Optional
id Optional
languageOfElement Optional
maintenanceEventReference Optional
scriptCode Optional
scriptOfElement Optional
sourceReference Optional
target Optional
Availability:
Optional, repeatable
Examples:
See <description> encoding
  [toc]
Attributes
Introduction  [toc]
Attributes are associated with most of the elements contained in EAC-CPF. Attributes reflect named properties of an element and may take on different values, depending on the context in which they occur. In order to set one or more attributes, an encoder should include the name of the attribute(s) within the same angle brackets as the start tag, together with the value(s) to which the attribute(s) is/are to be set. That is,<[tag] [attribute]="[value]">or<[tag] [attribute1]="[value1]" [attribute2]="[value2]">
For example:<fromDate standardDate="1939">1939</fromDate>or<fromDate certainty="approximate" standardDate="1939">1939</fromDate>
Most attributes are optional, though some are required. The attribute description indicates whether an attribute is required. This information is also available in the Attributes section of each element description.
The value of attributes may be constrained by the schema using specific attribute type values. For example, the @id attribute is of type ID, which constrains its value to a string beginning with an alphabetic character. An id value must be unique within the EAC-CPF instance within which it occurs, that is, no other tag in the entire document can have the same id value. EAC-CPF attributes have the following data types (capitalization of data types follows the documentation found in the W3C Recommendation XML Schema Part 2: Datatypes Second Edition (http://www.w3.org/TR/xmlschema-2/):
anyURI:
A Uniform Resource Identifier. This may be a Uniform Resource Locator (URL) or a Uniform Resource Name (URN). Both relative and absolute URIs are allowed.
ID:
Unique identifier. For example, most elements have an id, so that a unique code can be established for and used to refer to that specific element. The content of the id is of the type called "ID". Parsers verify that the value of attributes of type "ID" are unique. The values of id must begin with an alpha, not numeric, character, either upper or lowercase, and may contain a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. See also attributes of type "IDREF."
IDREFS:
List of ID reference values; values must match an existing ID of another element in the document.
NMTOKEN:
A name token, which can consist of any alpha or numeric character, as well as a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. A number of attributes in EAC-CPF where a character string from a code list is to be used are of the type "NMTOKEN".
normalizedString:
The most general data type, a string can contain any sequence of characters allowed in XML. Certain characters may have to be represented with an entity reference, for example &lt; for <, and &amp; for &.
token:
A type of string that may not contain carriage return, line feed or tab characters, leading or trailing spaces, and any internal sequence of two or more spaces.
When the EAC-CPF schema limits attribute values to a few choices, those values are declared in the schema in what is known as a "closed list." For example, the values of @audience are limited to either "external" or "internal." Other attributes are associated with semi-closed lists. Such lists include those values believed to be the most useful in many contexts, but other values are allowed. For example, <language> defines several values for @languageEncoding, including "otherLanguageEncoding" which may be used to specify values that are not in the semi-closed list for @languageEncoding. The definitions for some values in the closed and semi-closed lists appear below.
The following is a complete list of all the attributes that occur in EAC-CPF, and some discussion of how they may be used. Further, context-specific information about the use of certain attributes may be found in the "Attribute usage" section of the element descriptions.
Address Line Type  
@addressLineType
Summary:
Used to specify the type of address line encoded in <addressLine>.
Description and Usage:
Use @addressLineType with <addressLine> to specify the type of address line, e.g. "street", "country" or "postalCode".
Use the attribute @addressLineTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @addressLineType.
Data Type:
token
Examples:
See <description> encoding
 
Address Line Type Encoding  
@addressLineTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of address line given as part of a physical address.
Description and Usage:
@addressLineTypeEncoding specifies the authoritative source or rules for values supplied in @addressLineType within <addressLine>. If the value "EASList" is selected, @addressLineType will be expected with the values "county", "country", "district", "municipality", "postBox", "postalCode", "region", or "street". If the value "otherAddressLineTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherAddressLineTypeEncoding
Examples:
See <control> encoding
 
Agent Type  
@agentType
Summary:
An optional attribute of <agent> that indicates the type of agent relevant in a specific context.
Description and Usage:
Use @agentType in <agent> to specify the type of agent responsible for the creation, modification, or deletion of an EAS instance, when used within <maintenanceEvent>, or the type of agent relevant in the context of a <narrativeEvent>.
Use the attribute @agentTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @agentType.
Data Type:
token
Examples:
See <control> encoding
 
Agent Type Encoding  
@agentTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of agent.
Description and Usage:
@agentTypeEncoding specifies the authoritative source or rules for values supplied in @agentType within <agent>. If the value "EASList" is selected, @agentType will be expected with the values "corporateBody", "family", "group", "human", "mechanism", "person", "position", or "unknown". If the value "otherAgentTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherAgentTypeEncoding
Examples:
See <control> encoding
 
Audience  
@audience
Summary:
An optional attribute that helps control whether the information contained in the element should be available to all viewers or only to repository staff.
Description and Usage:
Available as global attribute for all elements. The attribute can be set to "external" in e.g. <cpfDescription> in EAC-CPF, <archDesc> in EAD, or <functionsDescription> in EAF to allow access to all the information about the entity, materials, or functions being described, but specific elements within these sections can also be set to "internal" to reserve that information for repository access only. This feature is intended to assist application software in restricting access to particular information by explicitly identifying data that is potentially sensitive or may otherwise have a limited audience. Special software capability may be needed, however, to prevent the display or export of an element marked "internal" when a whole EAS instance is displayed in a networked environment.
Use the attribute @audienceEncoding in <control> to identify the list of terms to be used as values of @audience.
Data Type:
token
Examples:
See <eac> encoding
 
Audience Encoding  
@audienceEncoding
Summary:
Specifies the authoritative source or rules for values used to indicate whether information encoded in a specific element is available for all or only for a restricted audience.
Description and Usage:
@audienceEncoding specifies the authoritative source or rules for values supplied in @audience available in all elements. If the value "EASList" is selected, @audience will be expected with the values "external" or "internal". If the value "otherAudienceEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherAudienceEncoding
Examples:
See <control> encoding
 
Calendar  
@calendar
Summary:
System of reckoning time, such as Gregorian calendar or Julian calendar.
Description and Usage:
Suggested values include, but are not limited to, "gregorian" and "julian". Available in <date>, <fromDate>, <toDate>.
Data Type:
token
Examples:
See <description> encoding
 
Certainty  
@certainty
Summary:
The level of confidence for a date.
Description and Usage:
The optional attribute @certainty provides level of confidence for the information given in <date>, <fromDate>, or <toDate>, e.g., approximate or circa.
Data Type:
token
Examples:
See <description> encoding
 
Contact Line Type  
@contactLineType
Summary:
Used to specify the type of contact line encoded in <contactLine>.
Description and Usage:
An attribute used to specify the type of contact line encoded in <contactLine>, e.g. "email", "phoneNumber" or "homepage".
Data Type:
token
 
Contact Line Type Encoding  
@contactLineTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of contact line given as part of a digital address.
Description and Usage:
@contactLineTypeEncoding specifies the authoritative source or rules for values supplied in @contactLineType within <contactLine>. If the value "EASList" is selected, @contactLineType will be expected with the values "directions", "email", "fax", "homepage", "mobileNumber", or "phoneNumber". If the value "otherContactLineTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherContactLineTypeEncoding
Examples:
See <control> encoding
 
Convention Declaration Reference  
@conventionDeclarationReference
Summary:
Use @conventionDeclarationReference to provide a direct link to a <conventionDeclaration> element within <control>.
Description and Usage:
The attribute can be used to link to a convention or rule that prescribes a method for converting one script into another script (transliteration). It also can be used to link to a national, international, or other rule that governs the construction of a name.
This optional attribute is available in elements that can contain text.
Data Type:
IDREFS
Examples:
See <description> encoding
 
Coordinate System  
@coordinateSystem
Summary:
A code for a system used to express geographic coordinates.
Description and Usage:
A code for a system used to express geographic coordinates, for example WGS84, (World Geodetic System), OSGB36 (Ordnance Survey Great Britain), or ED50 (European Datum). Required in <geographicCoordinates>.
Data Type:
token
Examples:
See <description> encoding
 
Country Code  
@countryCode
Summary:
A unique code representing a country.
Description and Usage:
Content of the optional attribute should be a code taken from the part of ISO 3166 Country Codes or another controlled list specified in the @countryEncoding attribute in <control>. Available in <maintenanceAgency> and <placeName>.
Data Type:
token
 
Country Encoding  
@countryEncoding
Summary:
Specifies the authoritative source or rules for codes used to identify a country as part of the maintenance agency's location or of describing a geographic feature.
Description and Usage:
@countryEncoding specifies the authoritative source or rules for values supplied in @countryCode within <maintenanceAgency> and <placeName>.
This can either be a specific part of the ISO standard 3166 or an alternative code list. If the value "otherCountryEncoding" is selected, such an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso3166-1-alpha-2, iso3166-1-alpha-3, iso3166-1-numeric, iso3166-2, iso3166-3, otherCountryEncoding
Examples:
See <control> encoding
 
Date Encoding  
@dateEncoding
Summary:
Specifies the authoritative source or rules used to normalize date information.
Description and Usage:
@dateEncoding specifies the authoritative source or rules for normalized values supplied in @standardDate within <date>, <fromDate> and <toDate> as well as in @standardDateTime within <eventDateTime>.
This can either be the ISO standard 8601 or an alternative code list. If the value "otherDateEncoding" is selected, such an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso8601, otherDateEncoding
Examples:
See <control> encoding
 
Level of Detail  
@detailLevel
Summary:
Provides information about the level of detail of the description encoded within the EAS instance.
Description and Usage:
An optional attribute within <control>, used to provide information about the level of detail in accordance with relevant description guidelines and/or rules, e.g. "minimal" or "extended".
Use the attribute @detailLevelEncoding in <control> to identify the list of authoritative terms that can be used as values of @detailLevel.
Data Type:
token
 
Detail Level Encoding  
@detailLevelEncoding
Summary:
Specifies the authoritative source or rules for values used to indicate whether the EAS instance encodes minimal, basic, or extended information.
Description and Usage:
@detailLevelEncoding specifies the authoritative source or rules for values supplied in @detailLevel within <control>. If the value "EASList" is selected, @detailLevel will be expected with the values "basic", "extended" or "minimal". If the value "otherDetailLevelEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherDetailLevelEncoding
Examples:
See <control> encoding
 
Era  
@era
Summary:
Period during which years are numbered and dates reckoned.
Description and Usage:
Period during which years are numbered and dates reckoned, such as CE (Common Era) or BCE (Before Common Era). Suggested values include, but are not limited to, "ce" and "bce". This optional attribute is available in <date>, <fromDate>, and <toDate>.
Data Type:
token
Examples:
See <description> encoding
 
Hypertext Reference  
@href
Summary:
The address for a remote resource.
Description and Usage:
The optional @href attribute takes the form of a Uniform Resource Identifier (URI). Available in <contactLine>, <reference>, <setComponent> and <source>.
Being of type "anyURI", @href is meant to point to any dereferencable resource. The term resource is used in a general sense and includes, but is not limited to, electronic documents, images, services (e.g. an HTTP-to-SMS gateway), collections of other resources, etc. A resource is not necessarily accessible via the Internet, i.e. not every URI is a URL, and abstract concepts can be resources too, such as the operators and operands of a mathematical equation or numeric values (e.g., zero, one, and infinity). While the use of complete URIs is recommended, it is also possible to use relative references in @href, e.g. only consisting of a string of numbers.
Data Type:
anyURI
Examples:
See <alternativeSet> encoding
 
ID  
@id
Summary:
A unique identifier to name a specific element within an EAS instance.
Description and Usage:
An identifier that must be unique within the current EAS instance and is used to name the element so that it can be referred to from somewhere else in the EAS instance. This facilitates building links between the element and other elements within the same XML file, though it can also be used to point to a specific element from outside of the EAS instance.
Use @target, @conventionDeclarationReference, @localTypeDeclarationReference, @maintenanceEventReference, or @sourceReference to link to an @id attribute within the EAS instance.
Data Type:
ID
Examples:
See <control> encoding
 
Identity Type  
@identityType
Summary:
Indicates whether the identity is given or acquired. May be useful for processing when multiple identities are described in the same instance.
Description and Usage:
The @identityType may occur on <identity>. Though optional, it is recommended that it be used when multiple identities are described in the same EAS instance using <multipleIdentities>, for example when describing pseudonyms. It will enable processors to distinguish between the description of a person and one or more personae.
Use the attribute @identityTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @identityType.
Examples:
See <eac> encoding
 
Identity Type Encoding  
@identityTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of identity being used.
Description and Usage:
@identityTypeEncoding specifies the authoritative source or rules for values supplied in @identityType within <identity>. If the value "EASList" is selected, @identityType will be expected with the values "acquired" or "given". If the value "otherIdentityTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is on available in <control>.
Values:
EASList, otherIdentityTypeEncoding
Examples:
See <control> encoding
 
Language Code  
@languageCode
Summary:
The code for the language used in the EAS instance or by the records or entity being described.
Description and Usage:
Content of the attribute should be a code taken from ISO 639-1, ISO 639-2, ISO 639-2b, ISO 639-2t, ISO 639-3, ISO 639-5, IETF BCP 47 or another controlled list, as specified in the @languageEncoding attribute in <control>. Required in <languageDeclaration> and optionally available in <language>.
Data Type:
token
Examples:
See <description> encoding
 
Language Encoding  
@languageEncoding
Summary:
Specifies the authoritative source or rules for codes used to identify the language of the EAS instance as a whole, of a specific element, or represented in the creative work of the CPF entity being described.
Description and Usage:
@languageEncoding specifies the authoritative source or rules for values supplied in @languageCode within <languageDeclaration> and <language> and in @languageOfElement available in all non-empty elements.
This can either be one of the ISO standards 639-1, 639-2, 639-2b, 639-2t, 639-3, and 639-5, the IETF BCP 47 language tag or an alternative code list. If the value "otherLanguageEncoding" is selected, such an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso639-1, iso639-2, iso639-2b, iso639-2t, iso639-3, iso639-5, ietf-bcp-47, otherLanguageEncoding
Examples:
See <control> encoding
 
Language of Element  
@languageOfElement
Summary:
Indicates the language of the content of an element.
Description and Usage:
Content of the attribute should be a code taken from ISO 639-1, ISO 639-2, ISO 639-2b, ISO 639-2t, ISO 639-3, ISO 639-5, IETF BCP 47 or another controlled list, as specified in the @languageEncoding attribute in <control>. May be used consistently in a multi-lingual EAS instance to specify which elements are written in which language. Optionally available on all non-empty elements.
Data Type:
token
Examples:
See <eac> encoding
 
Link Role  
@linkRole
Summary:
A URI that characterizes the nature of the remote resource to which a linking element refers.
Description and Usage:
A URI that characterizes, next to @href, the nature of the remote resource to which a linking element refers. Optionally available in <contactLine>, <reference>, <setComponent>, and <source>.
Being of type "anyURI", @linkRole is meant to point to any dereferencable resource. The term resource is used in a general sense and includes, but is not limited to, electronic documents, images, services (e.g. an HTTP-to-SMS gateway), collections of other resources, etc. A resource is not necessarily accessible via the Internet, i.e. not every URI is a URL, and abstract concepts can be resources too, such as the operators and operands of a mathematical equation or numeric values (e.g., zero, one, and infinity). While the use of complete URIs is recommended, it is also possible to use relative references in @linkRole, e.g. only consisting of a string of numbers.
Data Type:
anyURI
 
Link Title  
@linkTitle
Summary:
Viewable caption of a link text.
Description and Usage:
Information that serves as a viewable caption which explains to users the part that a remote resource plays in a link. May be used alongside any @href attribute in order to support accessibilty guidelines, such as those defined within the W3C's Web Content Accessibility Guidelines (WCAG).
Optionally available in <contactLine>, <reference>, <setComponent>, and <source>.
Data Type:
token
Examples:
See <alternativeSet> encoding
 
Local Type  
@localType
Summary:
This optional attribute provides a means to narrow the semantics of an element, or provide semantics for elements that are primarily structural or semantically weak.
Description and Usage:
The value of @localType may be from a local or generally used external vocabulary. While the value of @localType may be any string, to facilitate exchange of data, it is recommended that the value be either the URI or the preferred label for a term defined in a formal vocabulary (e.g., SKOS), which is identified by an absolute URI, and is resolvable to a web resource that describes the semantic scope and use of the value. Local conventions or controlled vocabularies used in @localType may be declared in <localTypeDeclaration> within <control>. @localTypeDeclarationReference should always be used alongside @localType to provide a direct link to the <localTypeDeclaration>.
Data Type:
token
Examples:
See <description> and <identity> encoding
 
Local Type Declaration Reference  
@localTypeDeclarationReference
Summary:
Use @localTypeDeclarationReference to provide a direct link to a <localTypeDeclaration> element within <control> from another element within the EAS instance using @localType.
Description and Usage:
@localTypeDeclarationReference should always be used when @localType is used, in order to link to the local type declaration.
Data Type:
IDREFS
Examples:
See <description> encoding
 
Maintenance Event Reference  
@maintenanceEventReference
Summary:
Use @maintenanceEventReference to provide a direct link to a <maintenanceEvent> element within <maintenanceHistory>.
Description and Usage:
The attribute can be used to link to a maintenance event in order to verify any assertion added to the entity’s description.
The attribute is optionally available in all elements that can contain text and are available outside of <control>.
Data Type:
IDREFS
 
Maintenance Event Type  
@maintenanceEventType
Summary:
An optional attribute of <maintenanceEvent> that identifies the type of maintenance activity.
Description and Usage:
Identifies the type of maintenance event with values such as "created", "derived" or "updated".
Use the attribute @maintenanceEventTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @maintenanceEventType.
Data Type:
token
Examples:
See <eac> encoding
 
Maintenance Event Type Encoding  
@maintenanceEventTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of maintenance activity.
Description and Usage:
@maintenanceEventTypeEncoding specifies the authoritative source or rules for values supplied in @maintenanceEventType within <maintenanceEvent>. If the value "EASList" is selected, @maintenanceEventType will be expected with the values "cancelled", "created", "deleted", "derived", "revised", "unknown", or "updated". If the value "otherMaintenanceEventTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherMaintenanceEventTypeEncoding
Examples:
See <control> encoding
 
Maintenance Status  
@maintenanceStatus
Summary:
The current drafting status of the EAS instance.
Description and Usage:
The maintenance status may occur on <control>.
As an EAS instance is modified or other events happen to it (as recorded in the <maintenanceHistory> element), the maintenance status should also be updated to reflect the current drafting status. On first creation the status would e.g. be "new", which on revision could be changed to "revised".
Use the attribute @maintenanceStatusEncoding in <control> to identify the list of authoritative terms that can be used as values of @maintenanceStatus.
Data Type:
See <control> encoding
 
Maintenance Status Encoding  
@maintenanceStatusEncoding
Summary:
Specifies the authoritative source or rules for values used to indicate the current version status of the EAS instance.
Description and Usage:
@maintenanceStatusEncoding specifies the authoritative source or rules for values supplied in @maintenanceStatus within <control>. If the value "EASList" is selected, @maintenanceStatus will be expected with the values "cancelled", "deleted", "deletedMerged", "deletedReplaced", "deletedSplit", "derived", "new", or "revised". If the value "otherMaintenanceStatusEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherMaintenanceStatusEncoding
Examples:
See <control> encoding
 
Normalized Form  
@normalizedForm
Summary:
A standardized form of the content of <referringString> that is in uncontrolled or natural language.
Description and Usage:
Use @normalizedForm to provide a standardized form, usually from a controlled vocabulary list, of the content of <referringString> e.g. to facilitate retrieval.
Data Type:
token
 
Not After  
@notAfter
Summary:
A standard numerical form of an approximate date for which a latest possible date is known.
Description and Usage:
Optionally available in <date>, <fromDate>, and <toDate>. It is recommended that @notAfter values follow ISO 8601 or another standard date format as specified in @dateEncoding.
Data Type:
token
Examples:
See <description> encoding
 
Not Before  
@notBefore
Summary:
A standard numerical form of an approximate date for which an earliest possible date is known.
Description and Usage:
Optionally available in <date>, <fromDate>, and <toDate>. It is recommended that @notBefore values follow ISO 8601 or another standard date format as specified in @dateEncoding.
Data Type:
token
Examples:
See <description> encoding
 
Place Type  
@placeType
Summary:
An optional attribute of <place> that specifies the type of the geographic feature or location being described.
Description and Usage:
Use @placeType with <place> to specify the type of geographic feature or location being described.
Use the attribute @placeTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @placeType.
Data Type:
token
Examples:
See <description> encoding
 
Place Type Encoding  
@placeTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of geographic feature or location.
Description and Usage:
@placeTypeEncoding specifies the authoritative source or rules for values supplied in @placeType within <place>. If the value "EASList" is selected, @placeType will be expected with the values "administrativeDivision", "area", "bodyOfWater", "landElevation", "populatedPlace", "roadOrRailroad", "spot", "undersea", "vegetation". If the value "otherPlaceTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherPlaceTypeEncoding
Examples:
See <control> encoding
 
Preferred Form  
@preferredForm
Summary:
Attribute that specifies whether or not a name provides the preferred form of the entity's name for display purposes.
Description and Usage:
Attribute that specifies whether or not a <nameEntry> provides the preferred form of the name of the EAS entity for display or other purposes in a given context. Use the value "true" if the name entry is preferred for any display or other purposes.
This optional attribute is only available in <nameEntry>.
Values:
false, true
Examples:
See <identity> encoding
 
Publication Status  
@publicationStatus
Summary:
The current publication status of the EAS instance.
Description and Usage:
The publication status may occur on <control> to indicate the current publication status of the EAS instance, for example "inProcess", "approved" or "published". As an EAS instance is modified or other events happen to it (as recorded in the <maintenanceHistory> element), the publication status should also be updated.
Use the attribute @publicationStatusEncoding in <control> to identify the list of authoritative terms that can be used as values of @publicationStatus.
Data Type:
token
Examples:
See <control> encoding
 
Publication Status Encoding  
@publicationStatusEncoding
Summary:
Specifies the authoritative source or rules for values used to indicate the current publishing status of the EAS instance.
Description and Usage:
@publicationStatusEncoding specifies the authoritative source or rules for values supplied in @publicationStatus within <control>. If the value "EASList" is selected, @publicationStatus will be expected with the values "approved", "inProcess", or "published". If the value "otherPublicationStatusEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherPublicationStatusEncoding
Examples:
See <control> encoding
 
Referred Entity Relationship  
@referredEntityRelationship
Summary:
An optional attribute of <referringString> that specifies the relationship between the entity named in a narrative text and the entity being described in the EAS instance.
Description and Usage:
Use @referredEntityRelationship with <referringString> to specify the relationship between the entity named in a narrative text and the entity being described in the EAS instance.
While @referredEntityRelationship does not come with a set of predefined values, it is highly recommended to use terms from controlled vocabularies whenever possible.
Data Type:
token
 
Referrered Entity Type  
@referredEntityType
Summary:
An optional attribute of <referringString> that specifies the type of entity named in a narrative text.
Description and Usage:
Use @referredEntityType with <referringString> to specify the type of entity named in a narrative text.
Use the attribute @referredEntityTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @referredEntityType.
Data Type:
token
Examples:
See <relation> encoding
 
Referred Entity Type Encoding  
@referredEntityTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of entity that is being referred to in a narrative text.
Description and Usage:
@referredEntityTypeEncoding specifies the authoritative source or rules for values supplied in @referredEntityType within <referringString>. If the value "EASList" is selected, @referredEntityType will be expected with the values "corpName", "famName", "function", "genreForm", "geogName", "name", "occupation", "persName", "subject" or "title". If the value "otherReferreredEntityTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherReferredEntityTypeEncoding
Examples:
See <control> encoding
 
Relation Type  
@relationType
Summary:
An optional attribute of <relation> that specifies the type of relation between the related entity and the entity being described in the EAS instance.
Description and Usage:
Use @relationType with <relation> to specify the type of relation between the related entity and the entity being described in the EAS instance.
Use the attribute @relationTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @relationType.
Data Type:
token
Examples:
See <relation> encoding
 
Relation Type Encoding  
@relationTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of relation between between the related entity and the entity being described in the EAS instance.
Description and Usage:
@relationTypeEncoding specifies the authoritative source or rules for values supplied in @relationType within <relation>. If the value "EASList" is selected, @relationType will be expected with the values "...". If the value "otherRelationTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherRelationTypeEncoding
Examples:
See <control> encoding
 
Repository Encoding  
@repositoryEncoding
Summary:
Specifies the authoritative source or rules for codes used to identify the maintenance agency of an EAS instance.
Description and Usage:
@repositoryEncoding specifies the authoritative source or rules for values used within <agencyCode>.
This can either be the ISO standard 15511 or an alternative code list. If the value "otherRepositoryEncoding" is selected, such an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso15511, otherRepositoryEncoding
Examples:
See <control> encoding
 
Script Code  
@scriptCode
Summary:
The code for the writing system, or script, used in the EAS instance or by the described entity or records.
Description and Usage:
Content of the attribute should be a code taken from ISO 15924, or another controlled list, as specified in the @scriptEncoding attribute in <control>. Optionally available in <languageDeclaration> and <writingSystem>.
Data Type:
token
Examples:
See <description> encoding
 
Script Encoding  
@scriptEncoding
Summary:
Specifies the authoritative source or rules for codes used to identify the writing system of the EAS instance as a whole or, of a specific element, or represented in the creative work of the CPF entity being described.
Description and Usage:
@scriptEncoding specifies the authoritative source or rules for values supplied in @scriptCode within <languageDeclaration> and <writingSystem> and in @scriptOfElement available in all non-empty elements. This can either be the ISO standard 15924 or an alternative code list. If the value "otherScriptEncoding" is selected, such an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso15924, otherScriptEncoding
Examples:
See <control> encoding
 
Script of Element  
@scriptOfElement
Summary:
Indicates the writing script of the content of an element (e.g., Cyrillic, Katakana).
Description and Usage:
Content should be taken from ISO 15924, or another controlled list, as specified in the @scriptEncoding attribute in <control>. May be used consistently in a multi-lingual EAS instance to specify which elements are written in which script. Optionally available on all non-empty elements.
Data Type:
token
Examples:
See <control> encoding
 
Source Reference  
@sourceReference
Summary:
Use @sourceReference to provide a direct link to a <source> element within <sources> in <control> from an element within the EAS instance that uses the source.
Description and Usage:
The attribute can be used to link any detailed information about the described entity to a source.
The attribute is optionally available in elements which can contain text.
Data Type:
IDREFS
 
Standard Date  
@standardDate
Summary:
The standardized form of date.
Description and Usage:
The standardized form of date expressed in <date>, <fromDate>, and <toDate>. It is recommended that @standardDate values follow ISO 8601, for example, 2011-07-22, 1963, or 1912-11, or another standard date format as specified in @dateEncoding.
Data Type:
token
Examples:
See <description> encoding
 
Standard Date and Time  
@standardDateTime
Summary:
Standardized form of a date, or date and time in <eventDateTime>.
Description and Usage:
An ISO 8601 compliant form of the date, or date and time, of a specific maintenance event expressed in <eventDateTime>. For example, 2021-12-31, 2021, 2021-12, 2021-12-31T23:59:59. Optionally available only in <eventDateTime>. It is recommended to either have the date and time stated as a literal in <eventDateTime> or to provide a standardized date with @standardDateTime, if not using both options in parallel.
Note that the requirement of ISO 8601 compliance for @standardDateTime is different from the usage of the attribute @standardDate, which can also follow other date encoding rules as specified in @dateEncoding within <control>.
Data Type:
Constrained to the following patterns: YYYY-MM-DD, YYYY-MM, YYYY, or YYYY-MM-DDThh:mm:ss [with optional timezone offset from UTC in the form of [+|-][hh:mm], or "Z" to indicate the dateTime is UTC. No timezone implies the dateTime is UTC.]
Examples:
See <control> and <identity> encoding
 
Status  
@status
Summary:
Attribute that follows controlled terminology detailing the status of elements.
Description and Usage:
@status provides controlled terminology detailing the status of specific elements. The terms available for @status are defined in closed lists that can vary by element. Use @statusEncoding in <control> to identify lists of terms from EAS lists that can be used as values of @status. It is also possible to define one's own list by using the value "otherStatusEncoding". Optionally available in <agencyCode>, <otherAgencyCode>, <nameEntry>, <date>, <fromDate>, and <toDate>.
Data Type:
token
Examples:
See <identity> encoding
 
Status Encoding  
@statusEncoding
Summary:
The authoritative source or rules for values supplied in @status.
Summary:
Specifies the authoritative source or rules for values used to indicate the status and certainty of the information provided in various elements.
Description and Usage:
@statusEncoding specifies the authoritative source or rules for values supplied in @status within <agencyCode>, <otherAgencyCode>, <date>, <fromDate>, <toDate>, and <nameEntry>. If the value "EASList" is selected, @status will be expected with the values "authorized" and "alternative" (for agency codes and <nameEntry>), "unknown" or "ongoing" (for dates). If the value "otherStatusEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherStatusEncoding
Examples:
See <control> encoding
 
Style  
@style
Summary:
Used to specify a rendering style for a string. It is recommended that the value conforms to W3C CSS.
Description and Usage:
The @style attribute may occur on <span> to indicate rendering instructions. It is highly recommended that the value of @style be expressed as a W3C CSS style to facilitate interoperability.
Data Type:
normalizedString
Examples:
See <control> encoding
 
Target  
@target
Summary:
A pointer to the ID of another element.
Description and Usage:
Used to create internal links within an XML instance. Optionally available in all elements except the root element.
Data Type:
IDREFS
Examples:
See <relation> encoding
 
Target Type  
@targetType
Summary:
Identifies the type of entity related to the entity or records being described.
Description and Usage:
An optional attribute of <relation> that specifies the type of entity that is related to the entity or records being described.
Use the attribute @targetTypeEncoding in <control> to identify the list of authoritative terms that can be used as values of @targetType.
Data Type:
token
Examples:
See <relation> encoding
See <relation> encoding
 
Target Type Encoding  
@targetTypeEncoding
Summary:
Specifies the authoritative source or rules for values used to identify the type of related entity.
Description and Usage:
@targetTypeEncoding specifies the authoritative source or rules for values supplied in @targetType within <relation>. If the value "EASList" is selected, @targetType will be expected with the values "corporateBody", "family", "function", "group", "instantiation", "mechanism", "person", "place", "position", "record", "recordSet", "recordPart", or "resource". If the value "otherTargetTypeEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
EASList, otherTargetTypeEncoding
Examples:
See <control> encoding
 
Unit  
@unit
Summary:
Defines the format or unit specified in <citedRange>.
Description and Usage:
Use @unit to document the format or unit that is specified in <citedRange>, for example page number ("pageNumber") or volume number ("volumeNumber").
Data Type:
token
Examples:
See <control> encoding
 
Value  
@value
Summary:
Defines the type of entity described in the EAC-CPF instance.
Description and Usage:
Required attribute within the <entityType> element that defines the type of entity described in the EAC-CPF instance.
Values:
corporateBody, family, person
Examples:
See <identity> encoding
 
Value URI  
@valueURI
Summary:
An attribute for including a URI identifying the resource to be used as the element's value.
Description and Usage:
Use the optional @valueURI attribute to provide the URI identifying the authority resource to be used as the element's content. Available in all elements that can contain any type of entity.
Being of type "anyURI", @valueURI is meant to point to any dereferencable resource. The term resource is used in a general sense and includes, but is not limited to, electronic documents, images, services (e.g. an HTTP-to-SMS gateway), collections of other resources, etc. A resource is not necessarily accessible via the Internet, i.e. not every URI is a URL, and abstract concepts can be resources too, such as the operators and operands of a mathematical equation or numeric values (e.g., zero, one, and infinity). While the use of complete URIs is recommended, it is also possible to use relative references in @valueURI, e.g. only consisting of a string of numbers.
Data Type:
anyURI
Examples:
See <description> encoding
 
Vocabulary Source  
@vocabularySource
Summary:
An attribute for identifying a vocabulary that is the source of the element's value.
Description and Usage:
Use the optional @vocabularySource attribute to provide a name or title of the authority or vocabulary source of the element’s content. Available in all elements that can contain any type of entity.
Data Type:
token
Examples:
See <description> encoding
 
Vocabulary Source URI  
@vocabularySourceURI
Summary:
An optional attribute for including a URI identifying the vocabulary source for the element's value.
Description and Usage:
Use the optional attribute to provide the URI of the authority or vocabulary source given in @vocabularySource. Available in all elements that can contain any type of entity.
Being of type "anyURI", @vocabularySourceURI is meant to point to any dereferencable resource. The term resource is used in a general sense and includes, but is not limited to, electronic documents, images, services (e.g. an HTTP-to-SMS gateway), collections of other resources, etc. A resource is not necessarily accessible via the Internet, i.e. not every URI is a URL, and abstract concepts can be resources too, such as the operators and operands of a mathematical equation or numeric values (e.g., zero, one, and infinity). While the use of complete URIs is recommended, it is also possible to use relative references in @vocabularySourceURI, e.g. only consisting of a string of numbers.
Data Type:
anyURI
Examples:
See <description> encoding
 
  [toc]
Appendix   
Examples  [toc]
eac
<eac xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://standards.openpreservation.org/eac/v3 https://github.com/SAA-SDT/eas-schemas/tree/release_2026_07/xml-schemas/eac-cpf/eac.xsd" xmlns="https://standards.openpreservation.org/eac/v3">
	<control addressLineTypeEncoding="EASList" agentTypeEncoding="EASList" audienceEncoding="EASList" contactLineTypeEncoding="EASList" countryEncoding="iso3166-1-alpha-2" dateEncoding="iso8601" identityTypeEncoding="EASList" languageEncoding="iso639-2b" maintenanceStatus="revised" maintenanceEventTypeEncoding="EASList" maintenanceStatusEncoding="EASList" placeTypeEncoding="EASList" publicationStatus="published" publicationStatusEncoding="EASList" referredEntityTypeEncoding="EASList" relationTypeEncoding="EASList" repositoryEncoding="iso15511" scriptEncoding="iso15924" scriptOfElement="Latn" targetTypeEncoding="EASList" statusEncoding="EASList">
		<recordId>
			21159483
		</recordId>
		<maintenanceAgency>
			<agencyCode>
				NBuU-AR
			</agencyCode>
			<agencyName>
				University Archives
			</agencyName>
		</maintenanceAgency>
		<maintenanceHistory>
			<maintenanceEvent maintenanceEventType="revised">
				<agent agentType="human">
					<label>
						R. Elia
					</label>
				</agent>
			<eventDateTime standardDateTime="2025-10-15"/>
			</maintenanceEvent>
		</maintenanceHistory>
	</control>
	<cpfDescription>
		<identity>
			<entityType value="person"/>
			<nameEntry audience="external" languageOfElement="eng" scriptOfElement="latn" status="alternative">
				<part localType="surname">
					Solum
				</part>
				<part localType="forename">
					Sjanna
				</part>
			</nameEntry>
		</identity>
	</cpfDescription>
</eac>
                    
<eac xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://standards.openpreservation.org/eac/v3 https://github.com/SAA-SDT/eas-schemas/tree/release_2026_07/xml-schemas/eac-cpf/eac.xsd" xmlns="https://standards.openpreservation.org/eac/v3">
	<control addressLineTypeEncoding="EASList" agentTypeEncoding="EASList" audienceEncoding="EASList" contactLineTypeEncoding="EASList" countryEncoding="iso3166-1-alpha-2" dateEncoding="iso8601" identityTypeEncoding="EASList" languageEncoding="iso639-2b" maintenanceStatus="revised" maintenanceEventTypeEncoding="EASList" maintenanceStatusEncoding="EASList" placeTypeEncoding="EASList" publicationStatus="published" publicationStatusEncoding="EASList" referredEntityTypeEncoding="EASList" relationTypeEncoding="EASList" repositoryEncoding="iso15511" scriptEncoding="iso15924" scriptOfElement="Latn" targetTypeEncoding="EASList" statusEncoding="EASList">
		<recordId>
		   EACexampleMI
		</recordId>
		<maintenanceAgency>
			<agencyCode>
				NBuU-AR
			</agencyCode>
			<agencyName>
				University Archives
			</agencyName>
		</maintenanceAgency>
		<maintenanceHistory>
			<maintenanceEvent maintenanceEventType="revised">
				<agent agentType="human">
					<label>
						R. Elia
					</label>
				</agent>
				<eventDateTime standardDateTime="2025-08-28"/>
			</maintenanceEvent>
		</maintenanceHistory>
	</control>
	<multipleIdentities>
		<cpfDescription>
			<identity identityType="acquired">
				<entityType value="person"/>
				<nameEntry languageOfElement="ru" scriptOfElement="Latn">
					<part localType="élément d'entrée">
						Gorki
					</part>
					<part localType="autre élément">
						Maksim
					</part>
					<useDates>
						<dateRange>
							<fromDate standardDate="1892">
								1892
							</fromDate>
							<toDate standardDate="1936">
								1936
							</toDate>
						</dateRange>
					</useDates>
				</nameEntry>
			</identity>
			<description>
				<functionsPerformed>
					<functionPerformed>
						<term>
							Romancier
						</term>
					</functionPerformed>
				</functionsPerformed>
				<languagesUsed>
					<languageUsed>
						<language languageCode="rus">
							russe
						</language>
						<writingSystem scriptCode="Cyrl"/>
					</languageUsed>
				</languagesUsed>
				<existDates>
					<dateRange>
						<fromDate standardDate="1868">
							1868
						</fromDate>
						<toDate standardDate="1936">
							1936
						</toDate>
					</dateRange>
				</existDates>
			</description>
		</cpfDescription>
		<cpfDescription>
			<identity identityType="given">
				<entityType value="person"/>
				<nameEntry languageOfElement="rus" scriptOfElement="Latn">
					<part localType="élément d'entrée">
						Peškov
					</part>
					<part localType="autre élément">
						Aleksej Maksimovič
					</part>
				</nameEntry>
			</identity>
			<description>
				<places>
					<place>
						<label>
							Nijni-Novgorod (Russie)
						</label>
					</place>
					<place>
					   <label>
							Gorki (Russie)
					   </label>
					</place>
					<place>
						<label valueURI="http://vocab.getty.edu/page/tgn/6006211">
							Union Soviétique
						</label>
					</place>
				</places>
				<existDates>
					<dateRange>
						<fromDate standardDate="1868-03-28">
							28 mars 1868
						</fromDate>
						<toDate standardDate="1936-06-18">
							18 juin 1936
						</toDate>
					</dateRange>
				</existDates>
				<biogHist>
					<p>
						Élevé par son oncle maternel à Nijni-Novgorod. S'installe à Kazan en 1884. Autodidacte. Premiers contacts avec les milieux marxistes et populistes. Retour à Nijni-Novgorod en 1889 et première arrestation. Entame un premier voyage dans le sud de la Russie en 1891 et s'installe à Tiflis (1891-1892), avant de revenir à Nijni-Novgorod (1893-1895 puis 1898). Arrêté un deuixème fois à Tiflis en 1898. Il se rend pour la première fois à Saint-Pétersbourg en 1899. Arrêté une 3e fois à Nijni-Novgorod en 1901, ce qui provoque une campagne de protestations. Entretient des liens d'amitié avec Cehov et Tol'stoj. Il apporte son soutien financier au Parti social-démocrate et se rapproche des Bolcheviks après 1905. Il s'exile à Capri de 1906 à 1913. Rentré en Russie en 1913, il s'exile de nouveau en 1921 en Allemagne puis en Italie en 1923. Il retourne définitivement en URSS en 1932.
					</p>
				</biogHist>
			</description>
		</cpfDescription>
	</multipleIdentities>
</eac>
control
<control addressLineTypeEncoding="EASList" agentTypeEncoding="EASList" audienceEncoding="EASList" contactLineTypeEncoding="EASList" countryEncoding="iso3166-1-alpha-2" dateEncoding="iso8601" identityTypeEncoding="EASList" languageEncoding="iso639-2b" maintenanceStatus="revised" maintenanceEventTypeEncoding="EASList" maintenanceStatusEncoding="EASList" placeTypeEncoding="EASList" publicationStatus="published" publicationStatusEncoding="EASList" referredEntityTypeEncoding="EASList" relationTypeEncoding="EASList" repositoryEncoding="iso15511" scriptEncoding="iso15924" scriptOfElement="Latn" targetTypeEncoding="EASList" statusEncoding="EASList">
	<recordId>
		21159483
	</recordId>
	<maintenanceAgency>
	<agencyCode>
		NBuU-AR
	</agencyCode>
	<agencyName>
		University Archives
	</agencyName>
	</maintenanceAgency>
	<maintenanceHistory>
		<maintenanceEvent maintenanceEventType="revised">
			<agent agentType="machine">
			<label>
					CPF merge program
			</label>
			</agent>
			<eventDateTime standardDateTime="2015-09-18">
				2015-09-18
			</eventDateTime>
			<eventDescription>
				Merge v2.0
			</eventDescription>
		</maintenanceEvent>
		<maintenanceEvent maintenanceEventType="revised">
			<agent agentType="machine">
				<label>
						SNAC EAC-CPF Parser
				</label>
			</agent>
			<eventDateTime standardDateTime="2016-08-11T10:39:38">
				2016-08-11T10:39:38
			</eventDateTime>
			<eventDescription>
				Bulk ingest into SNAC Database
			</eventDescription>
		</maintenanceEvent>
		<maintenanceEvent maintenanceEventType="revised">
			<agent agentType="human">
				<label>
						R. Elia
				</label>
			</agent>
			<eventDateTime standardDateTime="2025-10-15"/>
		</maintenanceEvent>
	</maintenanceHistory>
	<sources>
		<source id="source1" href="http://search.worldcat.org/title/1181498130">
			<reference>
				Handley-Taylor, Geoffrey, <span style="font-style:italic">The International Who's Who in Poetry</span>, vol. 2, London, The Cranbrook Tower Press, 1958.
			</reference>
		</source>
		<source id="source2">
			<reference>
				"What Poetry Means to Me," manuscript in Sjanna Solum papers, dated 1952 May 16
			</reference>
		</source>
		<source id="source3" href="https://search.worldcat.org/title/25575262">
			<reference>
				"Who's Who Poet, Sjanna Solum Living At Kelsey Hill, Deep River," <span style="font-style:italic">The New Era</span>, Deep River, CT, 1959 April 30.
			</reference>
			<citedRange unit="page">
				11
			</citedRange>
		</source>
	</sources>
	<conventionDeclaration id="cd1">
		<reference href="https://viaf.org/">
			Virtual International Authority File
		</reference>
		<shortCode>
			VIAF
		</shortCode>
	</conventionDeclaration>
	<conventionDeclaration id="cd2">
		<reference href="https://www.ica.org/standards/RiC/RiC-O_1-1.html">
			Records in Contexts Ontology (ICA RiC-O) version 1.1
		</reference>
		<shortCode>
			RICO
		</shortCode>
	</conventionDeclaration>
	<conventionDeclaration id="cd3">
		<reference href="http://vocab.getty.edu/page/aat">
			Getty Art and Architecture Thesaurus
		</reference>
		<shortCode>
			AAT
		</shortCode>
	</conventionDeclaration>
	<conventionDeclaration id="cd4">
	<reference href="https://id.loc.gov/authorities/names.html">
		Library of Congress Name Authority Files
	</reference>
	<shortCode>
		lcnaf
	</shortCode>
	</conventionDeclaration>
	<otherRecordId localType="ARK">
		http://n2t.net/ark:/99166/w6dz099z
	</otherRecordId>
	<otherRecordId vocabularySource="VIAF" vocabularySourceURI="#cd1" valueURI="http://viaf.org/viaf/3162902797577782447">
		3162902797577782447
	</otherRecordId>
</control>
identity
<identity>
	<entityType value="person"/>
	<nameEntrySet>
		<nameEntry languageOfElement="de" 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" localType="translation">
			<part localType="surname">
				アーレント
			</part>
			<part localType="firstname">
				ハナ
			</part>
		</nameEntry>
		<nameEntry languageOfElement="en" preferredForm="false" status="authorized">
			<part localType="surname">
				Arendt
			</part>
			<part localType="firstname">
				Hannah
			</part>
		</nameEntry>
		<useDates>
			<dateRange>
				<fromDate standardDate="1906-10-14">
					14.10.1906
				</fromDate>
				<toDate standardDate="1975-12-04">
					04.12.1975
				</toDate>
			</dateRange>
		</useDates>
	</nameEntrySet>
</identity>
                    
<identity>
	<entityType value="corporateBody"/>
		<nameEntry status="authorized">
			<part>
				Society of American Archivists
			</part>
		</nameEntry>
	<otherEntityTypes>
		<otherEntityType>
			<term>
				Professional Association
			</term>
		</otherEntityType>
	</otherEntityTypes>
</identity>
description
<description>
	<demographicDescriptions>
		<demographicDescription localType="age" localTypeDeclarationReference="lTD_age">
			<term>
				Age 30 to 44
			</term>
		</demographicDescription>
		<demographicDescription localType="education" localTypeDeclarationReference="lTD_education">
			<term>
				Level 4 qualifications and above
			</term>
		</demographicDescription>
		<demographicDescription localType="income" localTypeDeclarationReference="lTD_maritalStatus">
			<term>
				In a registered same-sex civil partnership
			</term>
		</demographicDescription>
		<descriptiveNote>
			<p>
				As part of the Census 2011, various demographic variables have been evaluated. Among others, this included the age, the level of qualifications, and the marital status of the participants.
			</p>
		</descriptiveNote>
	</demographicDescriptions>
	<languagesUsed>
		<languageUsed>
			<language languageCode="eng">
				English
			</language>
			<writingSystem scriptCode="Latn">
				Latin
			</writingSystem>
		</languageUsed>
			<languageUsed>
			<language languageCode="gre">
				Greek, Modern (1453-)
			</language>
			<writingSystem scriptCode="Grek">
				Greek
			</writingSystem>
		</languageUsed>
	</languagesUsed>
	<occupations>
		<occupation valueURI="http://vocab.getty.edu/page/aat/300025529">
			<term>
				Teacher
			</term>
		</occupation>
		<occupation valueURI="http://vocab.getty.edu/page/aat/300025799">
			<term>
				Geologist
			</term>
		</occupation>
	</occupations>
	<places>
		<place>
			<label vocabularySource="local" id="IDPlaceName1">
				East Side (Buffalo, N.Y.)
			</label>
			<geographicCoordinates coordinateSystem="WGS84">
				N 42°53′48" W 78°50′2"
			</geographicCoordinates>
		</place>
		<place placeType="populatedPlace">
			<label>
				Hardeeville
			</label>
			<address>
				<addressLine addressLineType="state">
					South Carolina
				</addressLine>
			</address>
			<geographicCoordinates coordinateSystem="WGS84">
				-81.1, 32.2, -81.0, 32.3
			</geographicCoordinates>
		</place>
	</places>
	<biogHist>
		<abstact>
			Brief summary of biographical information about the person being described in the EAC-CPF instance.
		</abstract>
		<narrativeEvent>
			<date standardDate="1850?" certainty="uncertain" calendar="gregorian" era="ce">c.1850</date>
			<placeName>London, England</placeName>
			<eventDescription>Born in London circa 1850.</eventDescription>
		</narrativeEvent>
		<narrativeEvent>
			<date notBefore="1873">1873</date>
			<placeName>Edinburgh, Scotland</placeName>
			<eventDescription>Completed medical degree at the University of Edinburgh.</eventDescription>
		</narrativeEvent>
		<narrativeEvent>
			<date notAfter="1921">until 1921</date>
			<placeName>York, England</placeName>
			<eventDescription>Practiced medicine in York, England.</eventDescription>
		</narrativeEvent>
	</biogHist>
	<existDates>
		<dateRange>
			<fromDate standardDate="1850?" certainty="uncertain">
				c.1850
			</fromDate>
			<toDate status="unknown"/>
		</dateRange>
	</existDates>
</description>
                    
<description>
	<functionsPerformed>
		<functionPerformed valueURI="http://vocab.getty.edu/page/aat/300133011" conventionDeclarationReference="cd3">
			<term>
				administration
			</term>
			<placeName valueURI="http://id.loc.gov/authorities/names/n79075597" conventionDeclarationReference="cd1">
				Buffalo (N.Y.)
			</placeName>
			<descriptiveNote>
				<p></p>
			</descriptiveNote>
		</functionPerformed>
	</functionsPerformed>
	<legalStatuses>
		<legalStatus>
			<term>
				New York State Department of Education
			</term>
		</legalStatus>
	</legalStatuses>
	<mandates>
		<mandate id="mandate1">
			<term>
				New York State Education Law, Article 8, Section 356
			</term>
			<date standardDate="2014">
				2014
			</date>
			<placeName valueURI="http://vocab.getty.edu/page/tgn/7007568" vocabularySource="tgn" vocabularySourceURI="https://www.getty.edu/research/tools/vocabularies/tgn/">
				New York (state)
			</placeName>
		</mandate>
	</mandates>
	<biogHist>
		<p>
			The UB Council serves as the primary oversight and advisory body to the University at Buffalo and its president and senior officers. Established in accordance with New York State Education Law, the council consists of ten members, nine who are appointed to seven-year terms by the governor of the State of New York, and one student member who is elected to an annual term by the university’s students.
		</p>
		<p>
			Among the regular duties of the council are reviewing all major plans and activities of the university in the areas of academics, student life, finances, buildings and grounds, as well as making recommendations and regulations for the benefit of the university in matters of community and alumni relations. One of the council's foremost, albeit infrequent, responsibilities is to recommend candidates to the state university trustees to serve as campus president.
		</p>
		<p>
			See the <reference href="https://www.buffalo.edu/ubcouncil.html">UB Council website</reference> for more information.
		</p>
	</biogHist>
	<generalContext>
		<p>
			The University Council of the University of Buffalo was established in 1922; its name changed when the university joined the SUNY system in 1962. See <reference href="https://findingaids.lib.buffalo.edu/agents/corporate_entities/1566">UB Council</reference> for records associated with this body before 1962.
		</p>
	</generalContext>
</description>
relations
<relations>
	<relation id="relation1" relationType="https://www.ica.org/standards/RiC/ontology#AuthorshipRelation" targetType="resource" conventionDeclarationReference="cd2">
		<label valueURI="https://find.library.upenn.edu/catalog/9923566873503681">
			Foggy night They lie, they lie, by David Morton and Florence B. Price, Ms. Coll. 199: Marian Anderson Collection of Music Manuscripts, folder 1404
		</label>
		<dateRange>
			<fromDate standardDate="1949-02-05">
				February 5, 1949
			</fromDate>
			<toDate standardDate="1989">
				1989
			</toDate>
		</dateRange>
		<role>
			Lyricist
		</role>
	</relation>
	<relation id="relation2" relationType="https://www.ica.org/standards/RiC/ontology#MembershipRelation" targetType="corporateBody" conventionDeclarationReference="cd2">
		<label valueURI="http://id.loc.gov/authorities/names/n50065387" conventionDeclarationReference="cd4">
			Poetry Society of America
		</label>
	</relation>
	<relation id="relation3" relationType="https://www.ica.org/standards/RiC/ontology#MembershipRelation" targetType="corporateBody" conventionDeclarationReference="cd2">
		<label valueURI="http://id.loc.gov/authorities/names/no2003010198" conventionDeclarationReference="cd4">
			Pen and Brush, Inc.
		</label>
	</relation>
</relations>
                    
<relations>
	<relation targetType="function">
		<label valueURI="Example Function Description.xml">
			Function name (placeholder)
		</label>
	</relation>
	<relation targetType="corporateBody" relationType="https://www.ica.org/standards/RiC/ontology#AgentControlRelation">
		<label valueURI="https://lccn.loc.gov/n83167936" vocabularySource="LCNAF" vocabularySourceURI="https://lccn.loc.gov" conventionDeclarationReference="cd1">
			New York (State). Governor
		</label>
		<descriptiveNote>
			<p>
				Established in accordance with <referringString referredEntityType="name" target="mandate1">New York State Education Law</referringString>, the council consists of ten members, nine who are appointed to seven-year terms by the governor of the State of New York, and one student member who is elected to an annual term by the university’s students.
			</p>
		</descriptiveNote>
	</relation>
</relations>
alternativeSet
<alternativeSet>
	<setComponent href="http://www.womenaustralia.info/biogs/AWE0064b.htm" linkTitle="Hill, Dorothy - Woman - The Australian Women's Register">
		<componentEntry>
			The Australian Women's Register record.
		</componentEntry>
	</setComponent>
	<setComponent href="http://nla.gov.au/anbd.aut-an35995526" linkTitle="Hill, Dorothy, 1907-1997 - Full record view - Libraries Australia Search">
		<componentEntry>
			Libraries Australia record.
		</componentEntry>
	</setComponent>
	<setComponent href="https://www.eoas.info/biogs/P000494b.htm" linkTitle="Hill, Dorothy - Biographical entry - Encyclopedia of Australian Science">
		<componentEntry>
			Encyclopedia of Australian Science record.
		</componentEntry>
	</setComponent>
</alternativeSet>