Encoded Archival Context - Corporate Bodies, Persons, and Families (EAC-CPF) Tag Library Version EAC-CPF 2.0
2022 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  [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 2.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 second major revision of the standard EAC-CPF. It supersedes the standard version EAC-CPF 2010 edition 2018.
The release is reflecting comments received by the international community of professionals between 2018 and 2021.
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.
The latest version of the EAC-CPF schema and tag library was adopted in 2010 and updated in late 2018. This version is called EAC-CPF 2010 edition 2018. The process for a major revision started in 2017, following the 2015 merger of the Technical Subcommittees on EAD and EAC-CPF into the Technical Subcommittee on Encoded Archival Standards (TS-EAS). This major revision aims to modernise the schema in terms of:
- simplifying where possible,



- alignment with EAD where useful,



- implementing features and solutions upon users’ request,



- clearing up unused components.



All elements and attributes in EAC-CPF 2010 were evaluated. Bugs and slight changes were made in a minor update of the Schema in 2018. The present version, EAC-CPF 2.0, is the result of a major overhaul of the standard and a reconciliation with EAD.
Following ISAAR(CPF), the established structure of control area, identity area, description area, and relations is still available, as is the idea of encoding multiple identities in one EAC-CPF instance.
The user communities of EAD and EAC-CPF overlap; therefore, the alignment of both schemas, where possible, shall ease the standards’ maintenance, usage, teaching, and learning. Elements and attributes used in both standards are harmonized by name, description and technical definition.
With the goal of simplifying the schema and aligning it with EAD, some encoding concepts were modified:linking and referencing, formatting, date encoding, language encoding, transliteration, control area, identity area, description area, and relations, cf Revision notes.
Working in parallel with the ICA Experts Group on Archival Description (ICA EGAD), who is working on a 2nd draft of Records in Contexts (RiC) which is being designed as the next comprehensive description standard for archives, EAC-CPF 2.0 tries to include the ideas of RiC-CM where feasible, see also TS EAS statement on related standards.
Widely discussed was the question of spelling since the related standard, EAD, uses lower-case for element and attribute names. For easier reading and teaching it was agreed to keep the camel case spelling for element and attribute names and also for fixed values.
Tag Library Conventions  [toc]
The EAC-CPF Elements section of the Tag Library contains descriptions of 91 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 include a tagged 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  [toc]
Summary:
An optional element within <biogHist> that contains a brief summary of the information contained within the <biogHist> as a whole.
May contain:
May occur within:
Description and Usage:
The <abstract> is a brief synopsis of the identity's biography or history that is often based on the longer descriptions found in <biogHist>. Its purpose is to help readers quickly identify the identity described in the EAC-CPF instance. The content within this element may also be harvested by other systems to provide explanatory context for the <nameEntry> data when it appears in a set of search results.
<abstract> may include one or more <reference> elements to point to external resources that provide additional descriptive data.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<biogHist>
<abstract>Hubert H. Humphrey was born in Wallace, South Dakota (1911). He was elected Mayor of Minneapolis in 1945 and served until 1948. In November of 1948, he was elected to the United States Senate and he also served as the Senate Democratic Whip from 1961 to 1964 and in 1968, Humphrey was the Democratic Party's candidate for President, but he was defeated by Richard M. Nixon.</abstract>

<p>Hubert H. Humphrey was born in Wallace, South Dakota, on May 27, 1911. He left South Dakota to attend the University of Minnesota but returned to South Dakota to help manage his father's drug store early in the depression. He attended the Capitol College of Pharmacy in Denver, Colorado, and became a register pharmacist in 1933. On September 3, 1936, Humphrey married Muriel Fay Buck. He returned to the University of Minnesota and earned a B.A. degree in 1939. In 1940 he earned an M.A. in political science from Louisiana State University and returned to Minneapolis to teach and pursue further graduate study, he began working for the W.P.A. (Works Progress Administration). He moved on from there to a series of positions with wartime agencies. In 1943, he ran unsuccessfully for Mayor of Minneapolis and returned to teaching as a visiting professor at Macalester College in St. Paul. Between 1943 and 1945 Humphrey worked at a variety of jobs. In 1945, he was elected Mayor of Minneapolis and served until 1948. In 1948, at the Democratic National Convention, he gained national attention when he delivered a stirring speech in favor of a strong civil rights plank in the party's platform. In November of 1948, Humphrey was elected to the United States Senate. He served as the Senate Democratic Whip from 1961 to 1964.</p>

<p>In 1964, at the Democratic National Convention, President Lyndon B. Johnson asked the convention to select Humphrey as the Vice Presidential nominee. The ticket was elected in November in a Democratic landslide. In 1968, Humphrey was the Democratic Party's candidate for President, but he was defeated narrowly by Richard M. Nixon. After the defeat, Humphrey returned to Minnesota to teach at the University of Minnesota and Macalester College. He returned to the U.S. Senate in 1971, and he won re-election in 1976. He died January 13, 1978 of cancer.</p>

</biogHist>





<address>
Address  [toc]
Summary:
An optional child element of <place> that binds together one or more <addressLine> elements to encode a postal or other address.
See also:
Use <contact> to encode digital addresses and contact information.

May contain:
May occur within:
Description and Usage:
<address> is an optional wrapper element within <place> used to encode a physical or analog address.
Ideally <address> should be bundled with a <placeName> element within <place> to provide both the name and address of a location.
<address> must include one or more <addressLine> element(s) that provide full or sufficient information identifying a postal or other physical address related to the entity being described.
At least one of <address>, <placeName>, <placeRole>, <geographicCoordinates>, or <contact> is required within <place>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<address audience="external" id="IDAddress1">
<addressLine languageOfElement="se">Kungl. Hovstaterna</addressLine>

<addressLine languageOfElement="se">Kungl. Slottet</addressLine>

<addressLine addressLineType="postalCode">10770</addressLine>

<addressLine languageOfElement="se" addressLineType="municipality">Stockholm</addressLine>

<addressLine languageOfElement="se" addressLineType="country">Sverige</addressLine>

<addressLine languageOfElement="en" addressLineType="country">Sweden</addressLine>

</address>





<addressLine>
Address Line  [toc]
Summary:
A required child element of <address> used for recording one line of a postal or other address.
Attribute usage:
Use one of the set values in the optional @addressLineType attribute to encode the part of the address that the <addressLine> refers to, for example "street".

May contain:
[text]
May occur within:
Description and Usage:
<addressLine> is used to encode parts or lines of a physical address within a parent <address> element.
<addressLine> may be repeated as many times as necessary to enter all parts of an address.
Attributes:
 
Optional (values limited to: county, country, district, municipality, postBox, postalCode, region, street)
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<address>
<addressLine languageOfElement="se">Kungl. Hovstaterna</addressLine>

<addressLine languageOfElement="se">Kungl. Slottet</addressLine>

<addressLine addressLineType="postalCode">10770</addressLine>

<addressLine languageOfElement="se" addressLineType="municipality">Stockholm</addressLine>

<addressLine languageOfElement="se" addressLineType="country">Sverige</addressLine>

<addressLine languageOfElement="en" addressLineType="country">Sweden</addressLine>

</address>





<agencyCode>
Agency Code  [toc]
Summary:
A child element of <maintenanceAgency> that provides a code for the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance.
Attribute usage:
Use @status with the value "authorized" or "alternative" to declare whether the <agencyCode> is using an authorized value, e.g. a registered ISIL code, or an alternative one.

See also:
Use <agencyName> to record the name of the agency.

Use <otherAgencyCode> to record any alternative codes representing the agency.

Use <recordId> in combination with <agencyCode> to provide a globally unique identifier for the EAC-CPF instance.

May contain:
[text]
May occur within:
Description and Usage:
Use <agencyCode> to record a code indicating the institution or service responsible for the creation, maintenance and/or dissemination of the EAC-CPF instance. Use of <agencyCode> is recommended, as the combination of <agencyCode> and the required <recordId> provide a globally unique identifier for the instance.
<maintenanceAgency> must include one or both of <agencyCode> and <agencyName>.
It is recommended that the code 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>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: alternative, authorized)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Examples:
<maintenanceAgency>
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-ctybr</agencyCode>

<agencyName>Beinecke Rare Book and Manuscript Library</agencyName>

<otherAgencyCode status="authorized" valueURI="https://id.loc.gov/vocabulary/organizations/ctybr" vocabularySource="MARC Code List for Organizations" vocabularySourceURI="https://www.loc.gov/marc/organizations/">CtY-BR</otherAgencyCode>

<otherAgencyCode status="alternative" valueURI="https://www.wikidata.org/wiki/Q814779" vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org/">Q814779</otherAgencyCode>

</maintenanceAgency>



<maintenanceAgency>
<agencyCode status="alternative" vocabularySource="NAD" vocabularySourceURI="https://sok.riksarkivet.se/">SE/G066</agencyCode>

<agencyName>Kommunalförbundet Sydarkivera</agencyName>

</maintenanceAgency>



<maintenanceAgency countryCode="DE">
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="https://sigel.staatsbibliothek-berlin.de/de/suche/" valueURI="https://ld.zdb-services.de/resource/organisations/DE-611">DE-611</agencyCode>

<agencyName>Staatsbibliothek zu Berlin - Preußischer Kulturbesitz, Kalliope-Verbund</agencyName>

<agencyName languageOfElement="eng">Berlin State Library - Prussian Cultural Heritage, Kalliope Union Catalog</agencyName>

</maintenanceAgency>





<agencyName>
Agency Name  [toc]
Summary:
A child element of <maintenanceAgency> that provides the name of the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance.
See also:
Use <agencyCode> to record a code representing the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance.

May contain:
[text]
May occur within:
Description and Usage:
Use <agencyName> to record the name of the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance. Examples include the repository name or the name of an aggregation service.
<maintenanceAgency> must include one or both of <agencyName> and <agencyCode>.
It is recommended to use the form of the agency name that is authorized by an appropriate national or international agency or service.
<agencyName> may be repeated in order to provide the name of the institution or service responsible for the EAC-CPF instance in multiple languages. If <agencyName> is repeated it is recommended to indicate the language of each name using languageOfElement.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<maintenanceAgency countryCode="DE">
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="https://sigel.staatsbibliothek-berlin.de/de/suche/" valueURI="https://ld.zdb-services.de/resource/organisations/DE-611">DE-611</agencyCode>

<agencyName>Staatsbibliothek zu Berlin - Preußischer Kulturbesitz, Kalliope-Verbund</agencyName>

<agencyName languageOfElement="eng">Berlin State Library - Prussian Cultural Heritage, Kalliope Union Catalog</agencyName>

</maintenanceAgency>



<maintenanceAgency>
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-nnmnh</agencyCode>

<agencyName>American Museum of Natural History</agencyName>

</maintenanceAgency>





<agent>
Agent  [toc]
Summary:
A required child element of <maintenanceEvent> that provides the name of a person, institution, or system responsible for a specific event in the EAC-CPF instance's maintenance history, such as its creation, modification, or deletion.
Attribute usage:
Use the required @agentType attribute to specify whether the agent is "human", "machine", or "unknown".

May contain:
[text]
May occur within:
Description and Usage:
Use <agent> to indicate the person, institution, or system responsible for a maintenance event. Examples include the name of the author or encoder, the database responsible for creating the EAC-CPF instance, and the style sheet used to update an instance to a new version of EAC-CPF.
Each <maintenanceEvent> element must have a child <agent> element.
Attributes:
 
Required (values limited to: human, machine, unknown)
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Example:
<maintenanceHistory>
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>

<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"></eventDateTime>

<eventDescription>Derived from EAD instance.</eventDescription>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>

<eventDateTime>December 2021</eventDateTime>

</maintenanceEvent>

</maintenanceHistory>





<alternativeSet>
Alternative Set  [toc]
Summary:
A container for one or more authority records derived from one or more authority systems, expressed within a single EAC-CPF instance.
See also:
<alternativeSet> should not be confused with <sources>, wherein authority records are not intended to be displayed as alternative versions.

May contain:
May occur within:
Description and Usage:
<alternativeSet> is a container element for one or more authority records derived from one or more alternative systems. Authority record aggregation may be used in cooperative or consortial contexts that gather together records describing the same CPF entity in different languages, from different rules, or from different contexts, when it is desirable to provide users with alternative descriptions of the same entity. For example in the context of the European Union, an international cooperative project may want to provide users the option of storing descriptions in English, French, German, Italian, Spanish, and in other European languages.
Alternative authority records are contained within the required <setComponent> child elements. This approach allows different descriptions of the same CPF entity to be contained within a single EAC-CPF instance.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<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>





<biogHist>
Biography or History  [toc]
Summary:
A concise essay and/or chronology that provides biographical or historical information about the EAC-CPF entity.
May contain:
May occur within:
Description and Usage:
<biogHist> includes significant details about the life of an individual or family, or the administrative history of a corporate body.
The <biogHist> element may contain text in a series of paragraphs (<p>), and/or a chronology list (<chronList>) that matches dates and date ranges with associated events and/or places. The <abstract> element is intended to provide a very brief synopsis of the full <biogHist> content that could be extracted for inclusion in a remote source, such as a MARC record.
The optional <list> element is used to accommodate greater complexity in expressing or representing the biography or history of the CPF entity. A simpler discursive expression of the information may be encoded as one or more <p> elements. The optional <head> element can be used to add a title or caption to the text.
The prescribed order of all child elements (both required and optional) is:
<head>



<abstract>



One or more of <chronList>, <list>, or <p>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<biogHist>
<abstract>Established in 1961, the United States Peace Corps administered and coordinated Federal international volunteer and related domestic volunteer programs in areas of agricultural assistance, community development, education, environmental protection, and nation assistance.</abstract>

<p>The Peace Corps was established as an operating agency in the Department of State Delegation of Authority 85-11, effective March 3, 1961, pursuant to Executive Order (E.O.) 10924, March 1, 1961. It was recognized legislatively by the Peace Corps Act (75 Stat. 612), approved September 22, 1961. The Peace Corps was reassigned to the newly established ACTION by Reorganization Plan No. 1 of 1971, effective July 1, 1971. It was made autonomous within ACTION by E.O. 12137, May 16, 1979, and was made an independent agency by Title VI of the International Security and Development Corporation Act of 1981 (95 Stat. 1540), February 21, 1982. The Peace Corps administered and coordinated Federal international volunteer and related domestic volunteer programs including the areas of agricultural assistance, community development, education, environmental protection, and nation assistance.</p>

</biogHist>



<biogHist>
<p>Ilma Mary Brewer, nee Pidgeon, was Lecturer in Botany/Biology, University of Sydney 1963-70 and Senior Lecturer in Biological Sciences 1970-78. She developed new methods of teaching based on the recognition that a student learnt more by working at his/her own place and instruction him/her self. Her findings were published as a book, "Learning More and Teaching Less."</p>

<chronList>
<chronItem>
<date standardDate="1936">1936</date>

<event>Bachelor of Science (BSc) completed at the University of Sydney</event>

</chronItem>

<chronItem>
<date standardDate="1937">1937</date>

<event>Master of Science (MSc) completed at the University of Sydney</event>

</chronItem>

<chronItem>
<dateRange>
<fromDate standardDate="1937">1937</fromDate>

<toDate standardDate="1941">1941</toDate>

</dateRange>

<event>Linnean Macleay Fellow</event>

</chronItem>

</chronList>

</biogHist>





<chronItem>
Chronology Item  [toc]
Summary:
A required element within <chronList> that pairs a date with one or more events and zero or more places within a chronology list.
Attribute usage:
Use @localType, if local use requires specification of the type of chronological item.

May contain:
May occur within:
Description and Usage:
A required element within a chronology list, <chronItem> must contain <date>, <dateRange>, or <dateSet> followed by an <event> or <chronItemSet>. Use <dateRange> to record an inclusive pair of dates or <dateSet> to record multiple dates or date ranges.
An optional <place> element may be used alongside <event> to detail a place that is relevant to the chronology item.
<chronItemSet> can be used to record multiple events or places within a single <chronItem>.
The prescribed order of all child elements (both required and optional) is:
One of <date>, <dateRange>, or <dateSet>



Either <event> or <chronItemSet>



<place> (only when <event> is used)



<reference>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<chronList>
<chronItem>
<dateRange>
<fromDate standardDate="1944">1944</fromDate>

<toDate standardDate="1947">1947</toDate>

</dateRange>

<event>Summer employment at Minnesota Valley Canning Co.</event>

<place>
<placeName>Blue Earth (Minn.)</placeName>

</place>

</chronItem>

<chronItem>
<dateRange>
<fromDate standardDate="1946">1946</fromDate>

<toDate standardDate="1948">1948</toDate>

</dateRange>

<event>Macalester College</event>

<place>
<placeName>St. Paul (Minn.)</placeName>

</place>

</chronItem>

<chronItem>
<date standardDate="1948">1948</date>

<event>Campaign Manager, 2nd District, State Democratic-Farmer-Labor Central Committee. Report to Orville Freeman.</event>

</chronItem>

</chronList>





<chronItemSet>
Chronology Item Set  [toc]
Summary:
An element for binding together one or more <event> elements and zero or more <place> elements within <chronItem>.
May contain:
May occur within:
Description and Usage:
Use <chronItemSet> within <chronItem> when it is necessary to associate multiple <event> elements and multiple <place> elements. Possible combinations include multiple events, a single event associated with multiple locations, multiple events associated with a single location, or multiple events associated with multiple locations. <chronItemSet> may be repeated within <chronItem> when necessary to associate multiple instances of such combinations with the date or dates recorded within <chronItem>.
The prescribed order of all child elements (both required and optional) is:
<event>



One or more of <place> or <reference>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<chronItem>
<date>2015</date>

<chronItemSet>
<event>Opens additional stores</event>

<place>
<placeName>Woodbury, Minnesota</placeName>

</place>

<place>
<placeName>Roseville, Minnesota</placeName>

</place>

</chronItemSet>

</chronItem>



<chronItem>
<date>1948</date>

<chronItemSet>
<event>Graduates from the University of Minnesota</event>

<event>Begins work as a receptionist for the Humphrey for Senator Committee</event>

<place>
<placeName>Minneapolis, Minnesota</placeName>

</place>

</chronItemSet>

</chronItem>



<chronItem>
<date>March 1957</date>

<chronItemSet>
<event>Dies</event>

<place>
<placeName>Biwabik, Minnesota</placeName>

</place>

</chronItemSet>

<chronItemSet>
<event>Buried in Lakewood Cemetery</event>

<place>
<placeName>Minneapolis, Minnesota</placeName>

</place>

</chronItemSet>

</chronItem>





<chronList>
Chronology List  [toc]
Summary:
An optional child element of <biogHist> used to document a structured chronological list of events, dates, and (optionally) places.
May contain:
May occur within:
Description and Usage:
<chronList> comprises a sequentially structured list of significant events in the life of the person or during the existence of the family or corporate body described in the EAC-CPF instance. Such events are associated with the date of occurrence and optionally with the name of a place.
Each <chronList> contains one or more <chronItem> elements, each associating a <date>, <dateRange>, or <dateSet> with an <event> and an optional <place>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<chronList>
<chronItem>
<date standardDate="1936">1936</date>

<event>Bachelor of Science (BSc) completed at the University of Sydney</event>

</chronItem>

<chronItem>
<date standardDate="1937">1937</date>

<event>Master of Science (MSc) completed at the University of Sydney</event>

</chronItem>

<chronItem>
<dateRange>
<fromDate standardDate="1937">1937</fromDate>

<toDate standardDate="1941">1941</toDate>

</dateRange>

<event>Linnean Macleay Fellow</event>

</chronItem>

<chronItem>
<dateRange>
<fromDate certainty="approximate" standardDate="1939">c. 1939</fromDate>

<toDate certainty="approximate" standardDate="1945">c. 1945</toDate>

</dateRange>

<event>Worked with Army Intelligence to map the vegetation (trees and undergrowth) in the coastal regions of New South Wales</event>

</chronItem>

</chronList>





<citedRange>
Cited Range  [toc]
Summary:
An optional child element of <source> that identifies precisely where supporting evidence was found within the source.
Attribute usage:
Use the optional @unit attribute to specify the format that the <citedRange> refers to, for example page number or volume number.

May contain:
[text]
May occur within:
Description and Usage:
The <citedRange> element can be used to refer to a specific location within a source where supporting evidence can be found. It may refer to a specific location such as a single page, or a broader location such as a range of pages.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<source id="source1" xlink:href="https://www.theguardian.com/books/2018/aug/10/langston-hughes-born-a-year-before-accepted-date-poet">
<citation>Flood, Alison
<span localType="http://id.loc.gov/ontologies/bibframe/title">"Langston Hughes 'born a year before accepted date', researcher finds,"</span>

The Guardian. Published 10 August 2018.</citation>

<citedRange unit="page">1</citedRange>

<descriptiveNote>
<p>Poet researching archives of local African American newspaper finds story reporting on 'little Langston' before his recorded birth date</p>

</descriptiveNote>

</source>





<componentEntry>
Component Entry  [toc]
Summary:
A child element of <setComponent> that can be used to provide identification and access to a linked resource.
May contain:
[text]
May occur within:
Description and Usage:
<componentEntry> is used within <setComponent> to provide a textual note about the alternative authority record that is being bundled together with others describing the same entity. The bundled alternative records for a given EAC-CPF entity may be in different languages or come from different authority systems. The bundling allows them to be transmitted or stored together. The <componentEntry> element provides a place where a particular alternative record can be described or explained in relation to the other authority records.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<alternativeSet>
<setComponent href="https://adb.anu.edu.au/biography/mawson-sir-douglas-7531" linkTitle="Biography - Sir Douglas Mawson - Australian Dictionary of Biography">
<componentEntry>Australian Dictionary of Biography record.</componentEntry>

</setComponent>

<setComponent href="http://nla.gov.au/anbd.aut-an35335937" linkTitle="Mawson, Douglas, Sir, 1882-1958 - Full record view - Libraries Australia Search">
<componentEntry>Libraries Australia record.</componentEntry>

</setComponent>

<setComponent href="https://www.eoas.info/biogs/P000631b.htm" linkTitle="Mawson, Douglas - Biographical entry - Encyclopedia of Australian Science">
<componentEntry>Encyclopedia of Australian Science record.</componentEntry>

</setComponent>

</alternativeSet>





<contact>
Contact  [toc]
Summary:
An optional child element of <place> that binds together one or more <contactLine> elements to encode contact details or digital addresses.
See also:
Use <address> to encode a physical or analog address.

May contain:
May occur within:
Description and Usage:
<contact> is an optional wrapper element within <place> used to encode digital addresses and contact information.
<contact> must include one or more <contactLine> element(s) that provide relevant contact details for the entity being described.
At least one of <contact>, <placeName>, <placeRole>, <geographicCoordinates>, or <address> is required within <place>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<contact audience="external" id="IDContact1">
<contactLine contactLineType="phoneNumber">08-402 60 00</contactLine>

<contactLine languageOfElement="se" contactLineType="homepage">https://www.kungahuset.se/2.1c3432a100d8991c5b80001816.html</contactLine>

<contactLine languageOfElement="en" contactLineType="homepage">https://www.kungahuset.se/royalcourt.4.367010ad11497db6cba800054503.html</contactLine>

</contact>





<contactLine>
Contact Line  [toc]
Summary:
A required child element of <contact> used for recording one line of contact details or digital addresses.
Attribute usage:
Use one of the set values in the optional @contactLineType attribute to encode the type of contact detail that the <contactLine> refers to, for example "phoneNumber".

May contain:
[text]
May occur within:
Description and Usage:
<contactLine> is used to encode separate details or lines of contact details or digital addresses within a parent <contact> element.
<contactLine> may be repeated as many times as necessary to enter all relevant contact details.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional (values limited to: directions, email, fax, homepage, mobileNumber, phoneNumber)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<contact>
<contactLine contactLineType="phoneNumber">08-402 60 00</contactLine>

<contactLine languageOfElement="se" contactLineType="homepage">https://www.kungahuset.se/2.1c3432a100d8991c5b80001816.html</contactLine>

<contactLine languageOfElement="en" contactLineType="homepage">https://www.kungahuset.se/royalcourt.4.367010ad11497db6cba800054503.html</contactLine>

</contact>





<control>
Control  [toc]
Summary:
A required child element of <eac> that contains information about the creation, maintenance, status and the rules and authorities used in the composition of the EAC-CPF instance.
Attribute usage:
Use the required @maintenanceStatus attribute to document the current version status of the EAC-CPF instance.

Use the optional @publicationStatus attribute to record the editorial status of the EAC-CPF instance.

May contain:
May occur within:
Description and Usage:
This required wrapper element within <eac> contains the information necessary to manage the instance. This includes information about its creation, maintenance and status as well as the languages, rules and authorities used in the composition of the description.
It must contain a unique identifier for the instance within the <recordId> element. Other associated identifiers may be given in <otherRecordId>. There must be a description of the agency responsible for its creation and maintenance in <maintenanceAgency> as well as statements about its current drafting status in maintenanceStatus and the creation, maintenance, and disposition of the instance in <maintenanceHistory>.
There are optional elements available to declare languages, rules, conventions and sources used in the EAC-CPF instance. Other control elements considered necessary but not otherwise included may be given in the <localControl> element. Similarly, local types for certain elements used throughout the EAC-CPF instance are recommended to be defined in the <localTypeDeclaration> element.
The available child elements (both required and optional), in their prescribed order, are:
<recordId> - Required. Contains the unique identifier for the EAC-CPF instance.



<maintenanceAgency> - Required. Contains the name and coded information about the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance.



<maintenanceHistory> - Required. Contains information about the date, type and events within the life cycle of an EAC-CPF instance.



<sources> - Optional. Contains information about the sources consulted in creating the description of the entity or entities in the EAC-CPF instance.



The following elements may appear in any order after the above elements:
<conventionDeclaration> - Optional. Contains information on the rules or conventions used to construct the EAC-CPF instance.



<languageDeclaration> - Optional. Contains coded and natural language information about the language or languages of the EAC-CPF instance.



<localControl> - Optional. Contains any administrative metadata necessary due to local practice that are not represented by the other elements in <control>.



<localTypeDeclaration> - Optional. Contains information about local conventions used in the @localType attribute.



<otherRecordId> - Optional. An element that allows the recording of additional identifiers that may be associated with the EAC-CPF instance.



<representation> - Optional. Used for recording a link to a transformed and deliverable version of the EAC-CPF instance.



<rightsDeclaration> - Optional. Contains information about the usage rights of the EAC-CPF instance.







Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional (values limited to: iso3166-1, otherCountryEncoding)
 
Optional (values limited to: iso8601, otherDateEncoding)
 
Optional (values limited to: basic, extended, minimal)
 
Optional
 
Optional (values limited to: ietf-bcp-47, iso639-1, iso639-2b, iso639-3, otherLanguageEncoding)
 
Optional
 
Required (values limited to: cancelled, deleted, deletedMerged, deletedReplaced, deletedSplit, derived, new, revised)
 
Optional (values limited to: approved, inProcess, published)
 
Optional (values limited to: iso15511, otherRepositoryEncoding)
 
Optional (values limited to: iso15924, otherScriptEncoding)
 
Optional
 
Optional
Availability:
Required, not repeatable
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" maintenanceStatus="new" publicationStatus="published" repositoryEncoding="iso15511" scriptEncoding="iso15924">
<recordId>https://kalliope-verbund.info/gnd/118584618</recordId>

<maintenanceAgency countryCode="DE">
<agencyCode status="authorized">DE-611</agencyCode>

<agencyName>Staatsbibliothek zu Berlin - Preußischer Kulturbesitz, Kalliope-Verbund</agencyName>

<agencyName languageOfElement="eng">Berlin State Library - Prussian Cultural Heritage, Kalliope Union Catalog</agencyName>

</maintenanceAgency>

<maintenanceHistory>
<maintenanceEvent maintenanceEventType="created">
<agent agentType="unknown">DE-101</agent>

<eventDateTime standardDateTime="1988-07-01"></eventDateTime>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown">1400</agent>

<eventDateTime standardDateTime="2015-10-15"></eventDateTime>

</maintenanceEvent>

</maintenanceHistory>

<sources>
<source>
<reference>Szb. Mozart-Lex.</reference>

</source>

</sources>

<conventionDeclaration>
<reference href="https://www.loc.gov/aba/rda/">Resource Description and Access</reference>

<shortCode>RDA</shortCode>

</conventionDeclaration>

<languageDeclaration languageCode="ger" scriptCode="Latn"></languageDeclaration>

<localTypeDeclaration>
<reference href="https://d-nb.info/standards/elementset/gnd_20191015">GNDO</reference>

<descriptiveNote>
<p>Gemeinsame Normdatei Ontologie</p>

<p languageOfElement="eng">Integrated Authority File Ontology</p>

<p>Version 2019-10-15</p>

</descriptiveNote>

</localTypeDeclaration>

<localTypeDeclaration>
<reference href="https://www.loc.gov/marc/authority/">MARC21</reference>

</localTypeDeclaration>

<otherRecordId localType="024$a" localTypeDeclarationReference="MARC21">http://d-nb.info/gnd/118584618"</otherRecordId>

<otherRecordId localType="035$a" localTypeDeclarationReference="MARC21">(DE-101)118584618</otherRecordId>

<otherRecordId localType="https://d-nb.info/standards/elementset/gnd#gndIdentifier" localTypeDeclarationReference="GNDO">(DE-588)118584618</otherRecordId>

<otherRecordId localType="https://d-nb.info/standards/elementset/gnd#oldAuthorityNumber" localTypeDeclarationReference="GNDO">(DE-588a)118584618</otherRecordId>

<otherRecordId localType="https://d-nb.info/standards/elementset/gnd#oldAuthorityNumber" localTypeDeclarationReference="GNDO">(DE-588c)4040426-2</otherRecordId>

<rightsDeclaration>
<reference href="https://creativecommons.org/publicdomain/zero/1.0/deed.de">CC0 1.0 Universell</reference>

</rightsDeclaration>

</control>





<conventionDeclaration>
Convention Declaration  [toc]
Summary:
An optional child element of <control>, used to declare the rules or conventions, including authorized controlled vocabularies and thesauri, applied in creating the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<conventionDeclaration> is used for declaring references to any rules and conventions, including authorized controlled vocabularies or thesauri, applied in the construction of the description. The element binds together the required <reference> element with optional <shortCode> and <descriptiveNote> elements that identify rules or conventions applied in compiling the EAC-CPF instance.
Each additional rule or set of rules, controlled vocabulary, or standard should be contained in a separate <conventionDeclaration>.
<shortCode> may be used to identify the standard or controlled vocabulary in a coded structure. Any notes relating to how these rules or conventions have been used may be given within <descriptiveNote>.
It may not be necessary to include <conventionDeclaration> in such cases where the above scenarios are addressed in local or consortial documentation.
The prescribed order of all child elements (both required and optional) is:
<reference>



<shortCode>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<conventionDeclaration id="cd1">
<reference href="https://www.legifrance.gouv.fr/loda/id/JORFTEXT000033553530/">Décret n° 2016-1689 du 8 décembre 2016 fixant le nom, la composition et le chef-lieu des circonscriptions administratives régionales - Légifrance</reference>

</conventionDeclaration>

<conventionDeclaration id="cd2">
<reference href="https://deliberation.maregionsud.fr/docs/ASSEMBLEEPLENIERE/2017/12/15/DELIBERATION/D0V0Q.pdf">DELIBERATION N° 17-1166, 15 DECEMBRE 2017</reference>

</conventionDeclaration>

<conventionDeclaration id="cd3">
<reference href="cnig.gouv.fr/wp-content/uploads/2015/03/CNT-site-collectivit%C3%A9s-fran%C3%A7aises.pdf">Commission nationale de toponymie: Collectivités territoriales françaises </reference>

</conventionDeclaration>





<cpfDescription>
CPF Description  [toc]
Summary:
A wrapper element that binds together the descriptive information of one CPF identity.
Attribute usage:
Use the @id attribute to identify individual <cpfDescription> elements when using the <multipleIdentities> structure.

May contain:
May occur within:
Description and Usage:
<cpfDescription> contains the description of one identity.
The <cpfDescription> includes a required <identity> element containing the entity type and authorized or alternative name entries. It also includes the optional <description> and <relations> elements that provide contextual information about the CPF entity being described, including the relations to other corporate bodies, persons, families, resources, and functions.
An optional <alternativeSet> element allows the incorporation of one or more authority records derived from one or more authority systems.
The prescribed order of all child elements (both required and optional) is:
<identity>



<description>



<relations>



<alternativeSet>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <eac>: one of <cpfDescription> or <multipleIdentities> required, not repeatable
Within <multipleIdentities>: two or more <cpfDescription> required, repeatable
Example:
<cpfDescription>
<identity>
<entityType value="person"></entityType>

<nameEntry>
<part localType="familyname">Hill</part>

<part localType="givenname">Dorothy</part>

</nameEntry>

</identity>

<description> [...] </description>

<relations> [...] </relations>

</cpfDescription>





<date>
Date  [toc]
Summary:
The single date of an event in the history of the person, family, or corporate body being described, or in their relationship to, e.g., a name entry, a place, an occupation, another CPF entity, a resource, or a function.
Attribute usage:
Use @certainty to indicate the degree of precision in the dating, for example, "uncertain" or "approximate".

Use @localType to supply a more specific characterization of the date.

Use @notAfter and @notBefore to capture the latest and earliest possible dates in machine-processable form in cases when the date is uncertain.

Use @standardDate to provide a machine-processable form of the date.

Use @status with the value "unknown" to indicate where a date is unknown.

May contain:
[text]
May occur within:
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. Uncertain or approximate dates can be encoded in standardDate using Extended Date/Time Format (EDTF).
If the event or relationship has inclusive dates use the <dateRange> element, while more complex dates (combining singles dates and date ranges) can be expressed in <dateSet>.
Dates of existence for the entity being described are encoded with the <existDates> element, while the dates of use of a particular name of an entity are encoded in <useDates>. The date and time of a maintenance event in the history of the EAC-CPF instance are given in the <eventDateTime> element.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: unknown)
 
Optional
 
Optional
Availability:
Within <demographicDescription>, <function>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <chronItem>, <existDates> and <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Within <dateSet>: at least two of <date> and/or <dateRange> required, repeatable
Within <localControl>: one of <date> or <dateRange> optional, not repeatable
Examples:
<date standardDate="1765-09-18">September 18, 1765</date>



<date certainty="uncertain" standardDate="1968?">c.1968</date>





<dateRange>
Date Range  [toc]
Summary:
A wrapper element for binding together <fromDate> and <toDate> in order to represent a range of dates. Either <fromDate> or <toDate> must be present within a <dateRange>, but it is recommended to use both child elements whenever possible.
Attribute usage:
Use @localType to supply a more specific characterization of the date range.

May contain:
May occur within:
Description and Usage:
An element that expresses inclusive dates of an event in the history of, or a relationship with, the person, family, or corporate body being described in the EAC-CPF instance.
<dateRange> contains <fromDate> and/or <toDate>, and therefore may express a range of dates as a starting point with no end point, a start and end point, or an end point with no starting point. Either <fromDate> or <toDate> must be present within a <dateRange>, but it is recommended to use both child elements whenever possible.
The content of the children of <dateRange> is intended to be a human-readable, natural language expression of the dates. If, however, indexing or other machine processing of dates is desired, standardDate should be used on the children of <dateRange> to record the date in machine-processable form as well.
Dates of existence for the identity being described are encoded with the <existDates> element, while the dates of use of a particular name of an identity are encoded in <useDates>. The date and time of a maintenance event in the history of the EAC-CPF instance are given in the <eventDateTime> element.
The prescribed order of all child elements (both required and optional) is:
<fromDate>



<toDate>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <demographicDescription>, <function>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <chronItem>, <existDates> and <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Within <dateSet>: at least two of <date> and/or <dateRange> required, repeatable
Within <localControl>: one of <date> or <dateRange> optional, not repeatable
Example:
<dateRange>
<fromDate standardDate="1765-08-18">September 18, 1765</fromDate>

<toDate standardDate="1846-06-01">June 1, 1846</toDate>

</dateRange>





<dateSet>
Date Set  [toc]
Summary:
A wrapper element for encoding complex dates that cannot be adequately represented in one <date> or <dateRange>.
May contain:
May occur within:
Description and Usage:
<dateSet> binds together single dates and date ranges, multiple single dates, or multiple date ranges. <dateSet> is used in situations where complex date information needs to be conveyed and requires at least two child elements. These can be any combination of <date> and <dateRange>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <demographicDescription>, <function>, <legalStatus>, <localDescription>, <mandate>, <occupation>, <otherEntityType>, <place>, <relation>: one of <date>, <dateRange>, or <dateSet> optional, not repeatable
Within <chronItem>, <existDates>, <useDates>: one of <date>, <dateRange>, or <dateSet> required, not repeatable
Example:
<dateSet>
<dateRange>
<fromDate standardDate="1928-09">1928 settembre</fromDate>

<toDate standardDate="1930-08">1930 autunno</toDate>

</dateRange>

<dateRange>
<fromDate standardDate="1947">1947</fromDate>

<toDate standardDate="1949">1949</toDate>

</dateRange>

<date>1950</date>

<date standardDate="1951-10-27">27 of October 1951</date>

</dateSet>





<demographicDescription>
Demographic Description  [toc]
Summary:
A required child element of <demographicDescriptions> that can be used to provide demographic information about the CPF entity being described.
May contain:
May occur within:
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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<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>





<demographicDescriptions>
Demographic Descriptions  [toc]
Summary:
An optional child element of <description> used to group together one or more <demographicDescription> elements.
May contain:
May occur within:
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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<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>





<description>
Description  [toc]
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:
May occur within:
Description and Usage:
The child elements that constitute <description> together permit descriptive information to be encoded in either structured or unstructured fashions, or in a combined approach. <description> accommodates the encoding of all the data elements that comprise the Description Area of ISAAR (CPF) including historical, biographical, and genealogical information; legal status and mandates; functions, occupations, and activities, and the dates and places that further constrain those elements.
The prescribed order of all child elements (both required and optional) is:
<demographicDescriptions>



<functions>



<languagesUsed>



<legalStatuses>



<localDescriptions>



<mandates>



<occupations>



<places>



Any of <biogHist>, <existDates>, <generalContext>, and <structureOrGenealogy>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<description>
<places>
<place>
<placeName vocabularySource="local" id="IDPlaceName1">East Side (Buffalo, N.Y.)</placeName>

<geographicCoordinates coordinateSystem="WGS84">N 42°53′48" W 78°50′2"</geographicCoordinates>

</place>

</places>

<functions>
<function>
<term valueURI="http://vocab.getty.edu/page/aat/300055433" vocabularySource="aat" vocabularySourceURI="https://www.getty.edu/research/tools/vocabularies/aat/">community development</term>

<placeName target="IDPlaceName1">East Side (Buffalo, N.Y.)</placeName>

<descriptiveNote>
<p>The organization’s mission is to create programs to improve the quality of residential housing and develop projects to improve the East Side of Buffalo and Western New York.</p>

</descriptiveNote>

</function>

</functions>

</description>





<descriptiveNote>
Descriptive Note  [toc]
Summary:
An element used to provide general descriptive information related to its parent element.
May contain:
May occur within:
Description and Usage:
<descriptiveNote> provides additional descriptive information about the element in which it is contained. <descriptiveNote> must contain one or more <p> elements.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<function>
<term valueURI="http://vocab.getty.edu/page/aat/300055433" vocabularySource="aat" vocabularySourceURI="https://www.getty.edu/research/tools/vocabularies/aat/">community development</term>

<placeName target="IDPlaceName1">East Side (Buffalo, N.Y.)</placeName>

<descriptiveNote>
<p>The organization’s mission is to create programs to improve the quality of residential housing and develop projects to improve the East Side of Buffalo and Western New York.</p>

</descriptiveNote>

</function>





<eac>
Encoded Archival Context - Corporate Bodies, Persons, and Families  [toc]
Summary:
The required root element of an EAC-CPF instance.
May contain:
Description and Usage:
<eac> wraps all other elements in a particular instance of an archival authority record encoded with the EAC-CPF XML Schema.
<eac> must contain <control> followed by either a <cpfDescription> or a <multipleIdentities> element.
In order to validate an EAC-CPF instance, it is highly recommended to include according information about the EAC-CPF namespace and the EAC-CPF schema location.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Examples:
<eac audience="external">
<control countryEncoding="iso3166-1" dateEncoding="iso8601" detailLevel="extended" languageEncoding="ietf-bcp-47" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>

<cpfDescription> [...] </cpfDescription>

</eac>



<eac>
<control countryEncoding="iso3166-1" dateEncoding="iso8601" detailLevel="basic" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>

<multipleIdentities>
<cpfDescription> [...] </cpfDescription>

<cpfDescription> [...] </cpfDescription>

</multipleIdentities>

</eac>





<entityType>
Entity Type  [toc]
Summary:
A required child element of <identity> encoding the type of CPF entity being described.
Attribute usage:
Use the required @value attribute with one of the values "corporateBody", "family", or "person" to identify the type of entity.

See also:
Use <otherEntityType> to encode additional or alternative entity types, such as a translation or a specification of the default entity types.

May contain:
[empty]
May occur within:
Description and Usage:
Within <identity> the required <entityType> element specifies the type of CPF entity being described in the EAC-CPF instance as being a corporate body, family or person.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Required (values limited to: corporateBody, family, person)
Availability:
Required, not repeatable
Examples:
<identity>
<entityType value="corporateBody"></entityType>

<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#preferredNameForTheCorporateBody" localTypeDeclarationReference="MARC21">Preußische Staatsbibliothek</part>

</nameEntry>

</identity>



<identity>
<entityType value="person"></entityType>

<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" localTypeDeclarationReference="GNDO">Arendt, Hannah</part>

<part localType="https://d-nb.info/standards/elementset/gnd#dateOfBirthAndDeath" localTypeDeclarationReference="GNDO">1906-1975</part>

</nameEntry>

</identity>



<identity>
<entityType value="family"></entityType>

<nameEntry status="authorized">
<part localType="100$a">Mozart</part>

<part localType="100$c">Familie : 17.-19. Jh.</part>

</nameEntry>

</identity>





<event>
Event  [toc]
Summary:
A child element of <chronItem> or <chronItemSet> that is used to encode an event associated with a date, and optionally a place, within a structured chronology.
May contain:
May occur within:
Description and Usage:
<event> contains discursive text identifying the event described by the <chronItem> or <chronItemSet>. <chronItem> must include one of either <event> or <chronItemSet>. <chronItemSet> must include one or more <event> elements.
Every <event> must have date(s) (<date>, <dateRange>, or <dateSet>) associated with it. It may also have optional <place> element associated with it.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <chronItem>: One of <chronItemSet> or <event> required, not repeatable.
Within <chronItemSet>: required, repeatable.
Example:
<chronList>
<chronItem>
<dateRange>
<fromDate standardDate="1944">1944</fromDate>

<toDate standardDate="1947">1947</toDate>

</dateRange>

<event>Summer employment at Minnesota Valley Canning Co.</event>

<place>
<placeName>Blue Earth (Minn.)</placeName>

</place>

</chronItem>

<chronItem>
<dateRange>
<fromDate standardDate="1946">1946</fromDate>

<toDate standardDate="1948">1948</toDate>

</dateRange>

<event>Macalester College</event>

<place>
<placeName>St. Paul (Minn.)</placeName>

</place>

</chronItem>

<chronItem>
<date standardDate="1948">1948</date>

<event>Campaign Manager, 2nd District, State Democratic-Farmer-Labor Central Committee. Report to Orville Freeman.</event>

</chronItem>

</chronList>





<eventDateTime>
Maintenance Event Date and Time  [toc]
Summary:
A required child element of <maintenanceEvent> that records the date and time of a specific maintenance action for an EAC-CPF instance.
Attribute usage:
Use @standardDateTime to provide a machine-processable expression of the date or date and time, formulated according to the ISO 8601 standard.

May contain:
[text]
May occur within:
Description and Usage:
A required child element of <maintenanceEvent>, <eventDateTime> is for recording the date and time that a maintenance event occurred. Examples of maintenance events include the creation, update, revision, or other modification to an EAC-CPF instance.
The date and time may be captured in natural language in the element. It is highly recommended to provide at least a human-readable date in <eventDateTime> directly or a machine-processable date in standardDateTime, in case it is not possible to provide both.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Examples:
<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>



<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>

<eventDateTime>December 2021</eventDateTime>

</maintenanceEvent>





<eventDescription>
Maintenance Event Description  [toc]
Summary:
An optional child element of <maintenanceEvent> that provides the description of a maintenance event in the life of the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A child element of <maintenanceEvent> used for describing the maintenance event. The element allows a full description of the maintenance event to be given alongside information about the maintenance agent, and the type, time and date of the maintenance event.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>

<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"></eventDateTime>

<eventDescription>Derived from EAD instance.</eventDescription>

</maintenanceEvent>





<existDates>
Dates of Existence  [toc]
Summary:
An optional element within <description> used for encoding the dates of existence of the CPF entity being described, such as dates of establishment and dissolution for corporate bodies and dates of birth and death or floruit for persons.
See also:
Do not confuse with <useDates>, which is a child element of <nameEntry> or <nameEntrySet> and represents the dates of use for a particular name or set of names.

May contain:
May occur within:
Description and Usage:
The dates of existence of the CPF entity being described, such as dates of establishment and dissolution for corporate bodies and dates of birth and death or floruit for persons.
<existDates> must contain one of <date>, <dateRange>, or <dateSet>. These child elements may contain actual or approximate dates. A <descriptiveNote> may be included if a fuller explanation of the dates of existence is needed.
Use the <date> element to record the date of a single event, such as a date of birth or date of incorporation. Use <dateRange> to encode a pair of inclusive dates. Use <dateSet> to encode more complex date expressions that intermix <date> and <dateRange> elements.
The prescribed order of all child elements (both required and optional) is:
One of <date>, <dateRange>, or <dateSet>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<existDates>
<dateRange>
<fromDate standardDate="1868">1868</fromDate>

<toDate standardDate="1936">1936</toDate>

</dateRange>

<descriptiveNote>
<p>The company was in business these years</p>

</descriptiveNote>

</existDates>





<fromDate>
From Date  [toc]
Summary:
A child element of <dateRange> that records the starting point in a range of dates.
Attribute usage:
Use @certainty to indicate the degree of precision in the dating, for example, "uncertain" or "approximate".

Use @localType to supply a more specific characterization of the start date.

Use @notAfter and @notBefore to capture the latest and earliest possible dates in machine-processable form in cases when the date is uncertain.

Use @standardDate to provide a machine-processable form of the date.

Use @status with the value "unknown" to indicate where the start of a date range is unknown.

See also:
Use <toDate> to record the ending point of a date range.

May contain:
[text]
May occur within:
Description and Usage:
Use <fromDate> to record the beginning date in a range of dates. <fromDate> may contain actual, approximate or unknown dates. The content of the element is intended to be a human-readable, natural language expression of the date. If, however, indexing or other machine processing of dates is desired, the standardDate should be used to record the date in machine-processable form as well. If the <fromDate> is not known, it may be omitted from <dateRange>, or the status attribute used.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: unknown)
 
Optional
 
Optional
Availability:
Optional, not repeatable
Examples:
<existDates>
<dateRange>
<fromDate standardDate="1868">1868</fromDate>

<toDate standardDate="1936">1936</toDate>

</dateRange>

</existDates>



<dateRange>
<fromDate status="unknown"></fromDate>

<toDate certainty="uncertain" standardDate="2010?">c.2010</toDate>

</dateRange>





<function>
Function  [toc]
Summary:
A required child element of <functions> that provides information about a function, activity, role, or purpose performed by the CPF entity being described.
See also:
Use <relation> with <targetEntity> having the @targetType "function" when describing the relationship between the function and the CPF entity being described in more detail.

May contain:
May occur within:
Description and Usage:
A <function> element is a wrapper element used to encode an index term, using the required child element <term>. Terms are used to identify the functions, processes, activities, tasks, or transactions performed by the CPF entity. They may be drawn from controlled vocabularies or may be natural language terms.
<function> must include at least one <term> element. <term> can be repeated within <function> to include translations of the same function. Use the languageOfElement attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and place(s) (<placeName>) may be included to further constrain the term's meaning. A <descriptiveNote> may be included if a fuller textual explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<term>



One of <date>, <dateRange>, or <dateSet>



<placeName>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<function>
<term>Estate ownership</term>

<descriptiveNote>
<p>Social, political, and cultural role typical of landed aristocracy in England. The first Viscount Campden amassed a large fortune in trade in London and purchased extensive estates, including Exton (Rutland), and Chipping Campden (Gloucestershire). The Barham Court (Kent) estate was the acquisition of the first Baron Barham, a successful admiral and naval administrator (First Lord of the Admiralty 1805).</p>

</descriptiveNote>

</function>





<functions>
Functions  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <function> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <functions> element to group together one or more occurrences of <function>. <functions> must include at least one <function> element.
The prescribed order of all child elements (both required and optional) is:
<function>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<functions>
<function>
<term>Industrial or Scientific Research</term>

</function>

<function>
<term>Analytical Services</term>

</function>

<function>
<term>Advisory or Regulatory Body</term>

</function>

</functions>





<generalContext>
General Context  [toc]
Summary:
An optional child element of <description> that encodes information about the general social and cultural context of the CPF entity being described.
May contain:
May occur within:
Description and Usage:
<generalContext> encodes information about the social, cultural, economic, political, and/or historical context in which the CPF entity being described existed. The general context provides wide latitude to record contextual information not specifically accommodated by other elements contained in <description>.
The optional <list> element may be used to accommodate greater complexity in expressing or representing the general context being described. The optional <head> element may be used to encode a title or caption. A simpler discursive expression of the general context may be encoded as one or more <p> elements.
The prescribed order of all child elements (both required and optional) is:
<head>



Any of <list> and <p>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<generalContext>
<p> In September 2017, the American Museum of Natural History announced a multi-year project to update, restore, and conserve the Northwest Coast Hall. In October 2018, renowned Nuu-chah-nulth artist and cultural historian Haa'yuups was named co-curator, along with AMNH Division of Anthropology Curator of North American Ethnology Curator Peter Whiteley, in the restoration of the hall.</p>

</generalContext>





<geographicCoordinates>
Geographic Coordinates  [toc]
Summary:
An optional child element of <place> that encodes a set of geographic coordinates.
Attribute usage:
Use the required @coordinateSystem attribute to provide a commonly used code for the system used to express the coordinates. Examples include WGS84, OSGB36, ED50.

May contain:
[text]
May occur within:
Description and Usage:
Use <geographicCoordinates> to express a set of geographic coordinates such as latitude, longitude, and altitude representing a point, line, or area on the surface of the earth.
It is recommended that the values included in <geographicCoordinates> are based on a commonly used system for expressing geographic coordinates.
At least one of <geographicCoordinates>, <placeName>, <placeRole>, <address>, or <contact> is required within <place>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Required
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<places>
<place>
<geographicCoordinates coordinateSystem="mgrs">33UUU9029819737</geographicCoordinates>

<placeName>Berlin, Germany</placeName>

</place>

<place>
<placeName localType="place">Clear Spring</placeName>

<placeName localType="state">Maryland</placeName>

<geographicCoordinates coordinateSystem="UTM">18S 248556mE 4393694mN</geographicCoordinates>

</place>

<place>
<placeName localType="place">Hardeeville</placeName>

<placeName localType="state">South Carolina></placeName>

<geographicCoordinates coordinateSystem="WGS84">-81.1, 32.2, -81.0, 32.3</geographicCoordinates>

</place>

</places>





<head>
Heading  [toc]
Summary:
An element that encodes a title or caption for a section of text.
May contain:
[text], span (0..n)
May occur within:
Description and Usage:
<head> is used for supplying title-like statements to a section of text or a list. When <head> is used, it must be the first child element, followed by one or more other elements.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<list listType="unordered">
<head>List of ministers of May Memorial Unitarian Universalist Church</head>

<item>John Storer, Minister 1839-1844</item>

<item>Samuel Joseph May, Minister 1845-1868</item>

<item>Samuel R. Calthrop, Minister 1868-1911</item>

<item>John H. Applebee, Minister 1911-1929</item>

<item>Waldemar W. Argow, Minister 1930-1941</item>

<item>Robert E. Romig, Minister 1941-1946</item>

<item>Glenn O. Canfield, Minister 1946-1952</item>

<item>John Fuller, Minister, 1961-1973</item>

</list>





<identity>
Identity  [toc]
Summary:
A required child element of <cpfDescription> used to encode the name or names related to the identity being described within the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<identity> is a wrapper element used to group the elements necessary to encode the name or names related to the identity of the CPF entity within the <cpfDescription> element.
The required child element <entityType> specifies the type of entity (i.e., corporate body, family, or person). The optional <otherEntityTypes> element can be used to encode other entity types used in the local context. An optional <identityId> is available for any identifiers associated with the CPF entity.
One or more <nameEntry> elements and/or one or more <nameEntrySet> elements must be included. All names by which the identity being described within one <cpfDescription> element is known are provided within <identity>. Each of the names, whether authorized or alternatives, should be recorded in a separate <nameEntry> element.
<identity> may accommodate two or more parallel names in different languages or scripts. In countries where there is more than one official language, such as Canada or Switzerland, names of CPF entities are frequently provided in more than one language. Within <identity>, a <nameEntrySet> element should be used to group two or more <nameEntry> elements that represent parallel forms of the name of the CPF entity being described.
Within <identity>, a <descriptiveNote> element may be used to record other information in a textual form that assists in the identification of the CPF entity.
In case of multiple identities of the same entity in one EAC-CPF instance, 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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: acquired, given)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Example:
<identity>
<entityType value="person"></entityType>

<nameEntry>
<part localType="familyname">Hill</part>

<part localType="givenname">Dorothy</part>

</nameEntry>

</identity>





<identityId>
Identity Identifier  [toc]
Summary:
An optional child element of <identity> used to record any identifier associated with the CPF entity being described.
See also:
Do not confuse with <recordId> within <control>, which refers to an identifier for the EAC-CPF instance rather than the entity it describes.

May contain:
[text]
May occur within:
Description and Usage:
<identityId> may be used to record any identifier associated with the CPF entity being described in the EAC-CPF instance. Identifiers such as legal identifiers, typically assigned by an authoritative agency, may be recorded in this element. If multiple identifiers are recorded, each should be in its own <identityID>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<localTypeDeclaration id="localTypeDeclaration1" vocabularySource="SwedishRegistrationCodeVocabulary">
<reference href="https://link.to.source">The Swedish vocabulary for identification codes</reference>

</localTypeDeclaration>

<identityId localType="RegistrationCode" localTypeDeclarationReference="localTypeDeclaration1">222000-3103</identityId>

<identityId localType="VATRegistrationCode" localTypeDeclarationReference="localTypeDeclaration1">SE222000310301</identityId>

<identityId localType="EInvoiceID" localTypeDeclarationReference="localTypeDeclaration1">2220003103</identityId>





<item>
Item  [toc]
Summary:
A child element of <list> that encodes the individual items in a list.
See also:
Do not confuse with <chronItem>, which encodes entries within a structured chronology (<chronList>).

May contain:
May occur within:
Description and Usage:
The <item> element is used for general lists within descriptive elements.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<list>
<item>
<span style="font-style:italic">1450-1950</span>

(1929)</item>

<item>
<span style="font-style:italic">Globe Gliding</span>

(1930)</item>

<item>
<span style="font-style:italic">Gems</span>

(1931) </item>

<item>
<span style="font-style:italic">Words</span>

(1931)</item>

<item>
<span style="font-style:italic">Demonics</span>

(1931)</item>

<item>
<span style="font-style:italic">Can We Co-operate</span>

(1942)</item>

<item>
<span style="font-style:italic">Amazing Amazon</span>

(1942) </item>

</list>





<language>
Language  [toc]
Summary:
An optional child element of <languageUsed> that identifies a particular language used in the creative work of the CPF entity being described.
Attribute usage:
Use @languageCode to provide a code for the language itself.

Use @languageOfElement to provide a code for the language in which the element is given.

May contain:
[text]
May occur within:
Description and Usage:
An optional element within <languageUsed> that gives the language or languages used by the CPF entity being described.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<languageUsed>
<language languageCode="eng">English</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>





<languageDeclaration>
Language Declaration  [toc]
Summary:
An optional child element of <control> that indicates the language and script in which an EAC-CPF instance is written.
Attribute usage:
Use the required @languageCode to provide a code for the language used in the EAC-CPF instance.

Use @languageOfElement to provide a code for the language in which the <languageDeclaration> element is given.

Use @scriptCode to provide a code for the writing system used in the EAC-CPF instance.

Use @scriptOfElement to provide a code for the writing system in which the <languageDeclaration> element is given.

May contain:
May occur within:
Description and Usage:
An optional child element of <control> that declares the languages and scripts in which an EAC-CPF instance is written in the languageCode and scriptCode attributes. Any comments about the languages and scripts in which the EAC-CPF instance is written may be included in the optional <descriptiveNote> element.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Required
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<languageDeclaration languageCode="ger" scriptCode="Latn"></languageDeclaration>





<languageUsed>
Language Used  [toc]
Summary:
A required child element of <languagesUsed> describing the language and writing system used by the CPF entity being described.
See also:
Do not confuse with <languageDeclaration> which refers to the language and script of the EAC-CPF instance.

May contain:
May occur within:
Description and Usage:
<languageUsed> is an element used to indicate the language and writing system, or script, in which the CPF entity being described was creative or productive. Use the <language> element to specify the language and a corresponding <writingSystem> element for the writing system.
The prescribed order of all child elements (both required and optional) is:
<language> and/or <writingSystem>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<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>





<languagesUsed>
Languages Used  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <languageUsed> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <languagesUsed> element to group together one or more occurrences of <languageUsed>. <languagesUsed> must include at least one <languageUsed> element.
The prescribed order of all child elements (both required and optional) is:
<languageUsed>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<languagesUsed>
<languageUsed>
<language languageCode="eng">English</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

<languageUsed>
<language languageCode="spa">Spanish</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

</languagesUsed>





<legalStatus>
Legal Status  [toc]
Summary:
A required child element of <legalStatuses> used to encode information about the legal status of a corporate body.
May contain:
May occur within:
Description and Usage:
The legal status of a corporate body is typically defined and granted by authorities or through authorized agencies. Enter terms in accordance with provisions of the controlling legislation. Terms may be drawn from controlled vocabularies or may be natural language terms.
<legalStatus> must include at least one <term> element, where the legal status of the corporate body is encoded. <term> can be repeated within <legalStatus> to include translations of the same term. Use the languageOfElement attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and place(s) (<placeName>) may be included to further constrain the term's meaning. A <descriptiveNote> element may be included if a fuller textual explanation is needed.
Multiple <legalStatus> elements may be grouped within a <legalStatuses> element.
The prescribed order of all child elements (both required and optional) is:
<term>



One of <date>, <dateRange>, or <dateSet>



<placeName>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Examples:
<legalStatus>
<term>Department of State</term>

</legalStatus>



<legalStatus>
<term>Organismo de la Administracion Central del Estado</term>

<date standardDate="1769">1769</date>

</legalStatus>





<legalStatuses>
Legal Statuses  [toc]
Summary:
An optional child element of <description> used to bundle together one or more <legalStatus> element.
May contain:
May occur within:
Description and Usage:
<legalStatuses> groups together one or more occurrences of <legalStatus>. <legalStatuses> must include at least one <legalStatus> element.
The prescribed order of all child elements (both required and optional) is:
<legalStatus>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Examples:
<legalStatuses>
<legalStatus>
<term>Private limited liability company</term>

<dateRange>
<fromDate standardDate="1941">1941</fromDate>

<toDate standardDate="1948">1948</toDate>

</dateRange>

</legalStatus>

<legalStatus>
<term>Public limited liability company</term>

<dateRange>
<fromDate standardDate="1948">1948</fromDate>

<toDate standardDate="2006">2006</toDate>

</dateRange>

</legalStatus>

<legalStatus>
<term>Private limited liability company</term>

<dateRange>
<fromDate standardDate="2006">2006</fromDate>

<toDate standardDate="2008">2008</toDate>

</dateRange>

</legalStatus>

</legalStatuses>



<legalStatuses>
<legalStatus>
<term>EPIC</term>

<dateRange>
<fromDate notBefore="1946-04">avril 1946</fromDate>

<toDate notAfter="2004-11">novembre 2004</toDate>

</dateRange>

<descriptiveNote>
<p>Établissement public à caractère industriel et commercial</p>

</descriptiveNote>

</legalStatus>

<legalStatus>
<term>SA</term>

<dateRange>
<fromDate notBefore="2004-11">novembre 2004</fromDate>

</dateRange>

<descriptiveNote>
<p>Société anonyme à capitaux publics</p>

</descriptiveNote>

</legalStatus>

</legalStatuses>





<list>
List  [toc]
Summary:
A wrapper element used to encode a simple list consisting of one or more <item> elements, or a complex list with one or more child <list> elements.
Attribute usage:
Use @listType to identify and format the list as a particular type. The choices are: "ordered," and "unordered."

Use @style to define the list type by entering a CSS list-style-type.

See also:
Do not confuse with <chronList>, which encodes a structured chronology.

May contain:
May occur within:
Description and Usage:
The <list> element is used for general lists that can be embedded with a large number of descriptive elements.
To encode a simple list, include one or more <item> elements within <list>. To encode more complex lists, such as hierarchies, additional <list> elements can be nested within <list>. <head> can be used to encode a title or caption within a <list>.
The prescribed order of all child elements (both required and optional) is:
<head>



One or both of <list> and <item>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: ordered, unordered)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<list listType="unordered" style="list-style-type: circle">
<head>List of ministers of May Memorial Unitarian Universalist Church</head>

<item>John Storer, Minister 1839-1844</item>

<item>Samuel Joseph May, Minister 1845-1868</item>

<item>Samuel R. Calthrop, Minister 1868-1911</item>

<item>John H. Applebee, Minister 1911-1929</item>

<item>Waldemar W. Argow, Minister 1930-1941</item>

<item>Robert E. Romig, Minister 1941-1946</item>

<item>Glenn O. Canfield, Minister 1946-1952</item>

<item>John Fuller, Minister, 1961-1973</item>

</list>





<localControl>
Local Control  [toc]
Summary:
An optional child element of <control>, used to specify any control information necessary to accommodate local practice.
Attribute usage:
Use @localType if local practice requires recording the type of entry.

May contain:
May occur within:
Description and Usage:
An element used to record and define any control information necessary to accommodate local practice, in addition to the elements otherwise made available within <control>.
The value of the entry must be given in a child <term> element and an associated date or range of dates can be given as either <date> or <dateRange>.
The prescribed order of all child elements (both required and optional) is:
<term>



<date> or <dateRange>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
No example has been provided for localControl. If you have any examples or use cases, please send them to TS-EAS.



<localDescription>
Local Description  [toc]
Summary:
A required child element of <localDescriptions> used to extend the descriptive categories to others available in a local system.
May contain:
May occur within:
Description and Usage:
<localDescription> provides a means to extend the list of description elements specified in the EAC-CPF schema. It should be used to record structured index terms rather than discursive text. The <localDescription> element should be used whenever a separate semantic process of the descriptive information is required in a local system that cannot be accommodated by the existing categories available in EAC-CPF.
<localDescription> must contain at least one <term> child element. Terms may be drawn from controlled vocabularies or may be natural language terms. Associated date(s) (<date>, <dateRange>, or <dateSet>) and place(s) (<placeName>) may be included to further constrain the term's meaning. A <descriptiveNote> may be included if a fuller textual explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<term>



One of <date>, <dateRange>, or <dateSet>



<placeName>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<localDescriptions>
<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#academicDegree" localTypeDeclarationReference="GNDO">Prof. Dr.</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#gndSubjectCategory" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#4.7p" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#">Personen zu Philosophie</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#gndSubjectCategory" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#8.1p" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#">Personen (Politologen, Staatstheoretiker)</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#gndSubjectCategory" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#9.5p" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#">Personen zu Soziologie, Gesellschaft, Arbeit, Sozialgeschichte</term>

</localDescription>

</localDescriptions>





<localDescriptions>
Local Descriptions  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <localDescription> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <localDescriptions> element to group together one or more occurrences of <localDescription>. <localDescriptions> must include at least one <localDescription> element.
The prescribed order of all child elements (both required and optional) is:
<localDescription>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<localDescriptions>
<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#geographicAreaCode" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/geographic-area-code#XA-DXDE" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/geographic-area-code#">Deutsches Reich</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#geographicAreaCode" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/geographic-area-code#XA-DE-BE" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/geographic-area-code#">Berlin</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#broaderTermInstantial" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/gnd/4066573-2" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Wissenschaftliche Bibliothek</term>

</localDescription>

<localDescription>
<term localType="https://d-nb.info/standards/elementset/gnd#gndSubjectCategory" localTypeDeclarationReference="GNDO" valueURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#6.7" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/standards/vocab/gnd/gnd-sc.html#">Bibliothek, Information und Dokumentation</term>

</localDescription>

</localDescriptions>





<localTypeDeclaration>
Local Type Declaration  [toc]
Summary:
An optional child element of <control> used to declare any local conventions or controlled vocabularies used in localType in the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
<localTypeDeclaration> specifies the local conventions and controlled vocabularies used in localType attributes in the EAC-CPF instance.
The child <reference> must be used to cite the resource that lists the local rules or controlled terms. Any notes relating to how these rules or conventions have been used may be given in <descriptiveNote>. The child <shortCode> may be used to identify any abbreviation or code representing the local convention or controlled vocabulary.
The prescribed order of all child elements (both required and optional) is:
<reference>



<shortCode>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<localTypeDeclaration>
<reference href="https://d-nb.info/standards/elementset/gnd_20191015">GNDO</reference>

<descriptiveNote>
<p>Gemeinsame Normdatei Ontologie</p>

<p languageOfElement="eng">Integrated Authority File Ontology</p>

<p>Version 2019-10-15</p>

</descriptiveNote>

</localTypeDeclaration>

<localTypeDeclaration>
<reference href="https://www.loc.gov/marc/authority/">MARC21</reference>

</localTypeDeclaration>





<maintenanceAgency>
Maintenance Agency  [toc]
Summary:
A required child element of <control> that identifies the institution or service responsible for the EAC-CPF instance.
Attribute usage:
Use @countryCode to indicate a unique code for the country of the maintenance agency.

May contain:
May occur within:
Description and Usage:
<maintenanceAgency> encodes information about the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance.
<maintenanceAgency> must include one or both of <agencyCode> or <agencyName> to provide the name of the institution or service. It may also include the optional child element <otherAgencyCode> to provide any additional identifiers. Any general information about the institution in relation to the EAC-CPF instance may be given in <descriptiveNote>.
The prescribed order of all child elements (both required and optional) is:
<agencyCode>



<agencyName>



<otherAgencyCode>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not Repeatable
Examples:
<maintenanceAgency>
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-ctybr</agencyCode>

<agencyName>Beinecke Rare Book and Manuscript Library</agencyName>

<otherAgencyCode status="authorized" valueURI="https://id.loc.gov/vocabulary/organizations/ctybr" vocabularySource="MARC Code List for Organizations" vocabularySourceURI="https://www.loc.gov/marc/organizations/">CtY-BR</otherAgencyCode>

<otherAgencyCode status="alternative" valueURI="https://www.wikidata.org/wiki/Q814779" vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org/">Q814779</otherAgencyCode>

</maintenanceAgency>



<maintenanceAgency>
<agencyCode status="alternative" vocabularySource="NAD" vocabularySourceURI="https://sok.riksarkivet.se/">SE/G066</agencyCode>

<agencyName>Kommunalförbundet Sydarkivera</agencyName>

</maintenanceAgency>





<maintenanceEvent>
Maintenance Event  [toc]
Summary:
A required child element of <maintenanceHistory> used to record information about maintenance activities in the history of the EAC-CPF instance.
Attribute usage:
Use the required @maintenanceEventType to document the type of maintenance activity that the <maintenanceEvent> is recording, using one of the values from the available controlled list.

May contain:
May occur within:
Description and Usage:
A required child element of <maintenanceHistory>, <maintenanceEvent> is used to record an activity in the creation and ongoing maintenance of an EAC-CPF instance, including revisions, updates, and deletions. There will always be at least one maintenance event for each instance, which will typically be its creation.
<maintenanceEvent> must include <agent> and <eventDateTime> child elements to record the agent that carried out the maintenance event, and the date and time the maintenance event occurred.
The prescribed order of all child elements (both required and optional) is:
<agent>



<eventDateTime>



<eventDescription>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Required (values limited to: cancelled, created, deleted, derived, revised, unknown, updated)
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<maintenanceHistory>
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>

<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"></eventDateTime>

<eventDescription>Derived from EAD instance.</eventDescription>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>

<eventDateTime>December 2021</eventDateTime>

</maintenanceEvent>

</maintenanceHistory>





<maintenanceHistory>
Maintenance History  [toc]
Summary:
A required child element of <control> that captures the history of the creation and maintenance of the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A required child element of <control>, <maintenanceHistory> is for recording the history of the creation, revisions, updates, and other modifications to the EAC-CPF instance.
There must be at least one child <maintenanceEvent> in <maintenanceHistory>, which usually will be a record of the creation of the instance. There may be many other <maintenanceEvent> elements documenting the milestone changes or activities in the maintenance of the instance.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Example:
<maintenanceHistory>
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>

<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"></eventDateTime>

<eventDescription>Derived from EAD instance.</eventDescription>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>

<eventDateTime>December 2021</eventDateTime>

</maintenanceEvent>

</maintenanceHistory>





<mandate>
Mandate  [toc]
Summary:
A required child element of <mandates> used for identifying the source of authority or mandate for the corporate body in terms of its powers, functions, responsibilities or activities, such as a law, directive, or charter.
May contain:
May occur within:
Description and Usage:
<mandate> is used to identify the source of authority or mandate for the 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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<mandate>
<term>Law 1946/1991</term>

<date standardDate="1991">1991</date>

<descriptiveNote>
<p>Law 1946/1991 determines a new legislative frame, which regulates the operation of the General State Archives to this day. The Central Service is structured into departments and Archives are established in prefectures which did not exist till then.</p>

</descriptiveNote>

</mandate>





<mandates>
Mandates  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <mandate> elements.
May contain:
May occur within:
Description and Usage:
<mandates> groups together one or more occurrences of <mandate>. <mandates> must include at least one <mandate> element.
The prescribed order of all child elements (both required and optional) is:
<mandate>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<mandates>
<mandate>
<term>Instrucciones de 13-VI-1586 por las que se crean y definen las secretarias de Tierra y Mar.</term>

</mandate>

<mandate>
<term>Real Decreto de Nueva Planta para el consejo de Guerra de 23-IV-1714.</term>

</mandate>

<mandate>
<term>Real Decreto de Nueva Planta para el consejo de Guerra de 23-VIII-1715.</term>

</mandate>

</mandates>





<multipleIdentities>
Multiple Identities  [toc]
Summary:
A child element of <eac> used to group together more than one <cpfDescription> within a single EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
A grouping element used to encode more than one <cpfDescription> in a single EAC-CPF instance.
The <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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
Availability:
Within <eac>: one of <cpfDescription> or <multipleIdentities> required, not repeatable
Example:
<multipleIdentities>
<cpfDescription>
<identity identityType="acquired" localType="pseudonyme">
<entityType>person</entityType>

<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>
<functions>
<function>
<term>Romancier</term>

</function>

</functions>

<languagesUsed>
<languageUsed>
<language languageCode="rus">russe</language>

<writingSystem scriptCode="Cyrl"></writingSystem>

</languageUsed>

</languagesUsed>

<existDates>
<dateRange>
<fromDate standardDate="1868">1868</fromDate>

<toDate standardDate="1936">1936</toDate>

</dateRange>

</existDates>

</description>

</cpfDescription>

<cpfDescription>
<identity identityType="given" localType="état civil">
<entityType>person</entityType>

<nameEntry languageOfElement="rus" scriptOfElemebt="Latn">
<part localType="élément d'entrée">Peškov</part>

<part localType="autre élément">Aleksej Maksimovič</part>

</nameEntry>

</identity>

<description>
<places>
<place>
<placeRole>naissance</placeRole>

<placeName>Nijni-Novgorod (Russie)</placeName>

</place>

<place>
<placeRole>décès</placeRole>

<placeRole>Gorki (Russie)</placeRole>

</place>

<place>
<placeRole>nationalité</placeRole>

<placeName countryCode="SU">Union Soviétique</placeName>

</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>





<nameEntry>
Name Entry  [toc]
Summary:
An element containing a name entry for a corporate body, person, or family.
Attribute usage:
The @status attribute may be used to indicate whether the <nameEntry> is an authorized or alternative form of the name.

The @scriptOfElement and @languageOfElement attributes can be used to specify the script and language of each name recorded in <nameEntry>.

May contain:
May occur within:
Description and Usage:
Within <identity>, the element <nameEntry> is used to record a name by which the corporate body, person, or family described in the EAC-CPF instance is known.
When <nameEntry> occurs within <nameEntrySet> it is used to record two or more 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>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: false, true)
 
Optional
 
Optional
 
Optional (values limited to: alternative, authorized)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet> required, repeatable
Within <nameEntrySet>: two or more <nameEntry> required, repeatable
Example:
<nameEntrySet languageOfElement="fre">
<nameEntry conventionDeclarationReference="cd1" preferredForm="true">
<part>Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd2">
<part>Région Sud Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd3">
<part>Provence-Alpes-Côte-d'Azur</part>

</nameEntry>

</nameEntrySet>





<nameEntrySet>
Name Entry Set  [toc]
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:
May occur within:
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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <identity>: one of <nameEntry> or <nameEntrySet> required, repeatable
Example:
<nameEntrySet localType="parallel">
<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>

</nameEntrySet>





<objectXMLWrap>
Object XML Wrap  [toc]
Summary:
An optional child element of <relation>, <setComponent>, and <source> that allows for the inclusion of an XML element from any XML namespace other than EAC-CPF.
May contain:
[any element from any namespace]
May occur within:
Description and Usage:
A wrapper element that provides a place to express data in any XML encoding language.
To facilitate interoperability the XML should conform to an open, standard XML schema and a namespace attribute should be present on the root element referencing the namespace of the standard.
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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
Availability:
Optional, not repeatable
Examples:
<objectXMLWrap>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/mods/v3/mods-3-3.xsd">
<titleInfo>
<title>Artisti trentini tra le due guerre</title>

</titleInfo>

<name>
<namePart type="given">Nicoletta</namePart>

<namePart type="family">Boschiero</namePart>

<role>
<roleTerm type="text">autore</roleTerm>

</role>

</name>

</mods>

</objectXMLWrap>



<objectXMLWrap>
<bibl xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.tei.org/ns/1.0 tei.xsd" default="false">
<title>
<emph rend="italic">Paris d'hier et d'aujourd'hui</emph>

</title>

<respStmt>
<resp>photographes</resp>

<name>Roger Henrard</name>

<name>Yann Arthus-Bertrand</name>

</respStmt>

</bibl>

</objectXMLWrap>



<objectXMLWrap>
<note>
<to>Tove</to>

<from>Jani</from>

<heading>Reminder</heading>

<body>Don't forget me this weekend!</body>

</note>

</objectXMLWrap>





<occupation>
Occupation  [toc]
Summary:
A required child element of <occupations> that provides information about an occupation of the CPF entity being described.
May contain:
May occur within:
Description and Usage:
<occupation> is a wrapper element that uses the child element <term> to identify an occupation held by the CPF entity. Terms may be drawn from controlled vocabularies or may be natural language terms.
<occupation> must include at least one <term> element. <term> can be repeated within <occupation> to include translations of the same function. Use the languageOfElement attribute to identify the language used in each <term>.
Associated date(s) (<date>, <dateRange>, or <dateSet>) and place(s) (<placeName>) may be included to further constrain the term's meaning. A <descriptiveNote> element may be included if a textual explanation needed.
The prescribed order of all child elements (both required and optional) is:
<term>



One of <date>, <dateRange>, or <dateSet>



<placeName>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<occupations>
<occupation>
<term>Geologist</term>

</occupation>

<occupation>
<term>Palaeontologist</term>

</occupation>

</occupations>





<occupations>
Occupations  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <occupation> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <occupations> element to group together one or more occurrences of <occupation>. <occupations> must include at least one <occupation> element.
The prescribed order of all child elements (both required and optional) is:
<occupation>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<occupations>
<occupation>
<term>Teacher</term>

</occupation>

<occupation>
<term>Railway labourer</term>

</occupation>

</occupations>





<otherAgencyCode>
Other Agency Code  [toc]
Summary:
An optional child element of <maintenanceAgency> that provides an alternative code for the institution or service responsible for the EAC-CPF instance.
Attribute usage:
Use @localType to specify the type of code being provided.

Use @status to encode whether the <otherAgencyCode> is an authorized or alternative code.

May contain:
[text]
May occur within:
Description and Usage:
Use <otherAgencyCode> to provide an alternative and/or local code that represents the institution or service responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance. Any code other than that given in <agencyCode> may be provided in <otherAgencyCode>. The addition of an ISO 3166-1 alpha-2 country code as the prefix to a local code is recommended to ensure international uniqueness.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: alternative, authorized)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<maintenanceAgency>
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-nbuuar</agencyCode>

<agencyName>State University of New York at Buffalo, Archives</agencyName>

<otherAgencyCode status="authorized" valueURI="http://id.loc.gov/vocabulary/organizations/nbuuar" vocabularySource="MARC Code List for Organizations" vocabularySourceURI="https://www.loc.gov/marc/organizations/">NBuU-AR</otherAgencyCode>

</maintenanceAgency>



<maintenanceAgency>
<agencyCode status="authorized" vocabularySource="ISIL" vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-ctybr</agencyCode>

<agencyName>Beinecke Rare Book and Manuscript Library</agencyName>

<otherAgencyCode status="authorized" valueURI="https://id.loc.gov/vocabulary/organizations/ctybr" vocabularySource="MARC Code List for Organizations" vocabularySourceURI="https://www.loc.gov/marc/organizations/">CtY-BR</otherAgencyCode>

<otherAgencyCode status="alternative" valueURI="https://www.wikidata.org/wiki/Q814779" vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org/">Q814779</otherAgencyCode>

</maintenanceAgency>





<otherEntityType>
Other Entity Type  [toc]
Summary:
A required and repeatable child element of <otherEntityTypes> used to encode additional or alternative entity types.
May contain:
May occur within:
Description and Usage:
<otherEntityType> is a required child element of <otherEntityTypes> used to encode any additional or alternative entity types used for the CPF instance in addition to the required <entityType> element with values of corporateBody, person, or family. For example, in a local context "organization" might be used as an entity type instead of "corporateBody". <otherEntityType> allows "organization" to be encoded.
<otherEntityType> must include one <term> element containing the term for the other entity type.
Each CPF instance may include more than one <otherEntityType> element within the <otherEntityTypes> wrapper element.
The prescribed order of all child elements (both required and optional) is:
<term>



One of <date>, <dateRange>, or <dateSet>



<placeName>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<identity>
<entityType>corporateBody</entityType>

<nameEntry status="authorized">
<part>Ballarat Orphanage</part>

</nameEntry>

<otherEntityTypes>
<otherEntityType>
<term>Organisation</term>

</otherEntityType>

</otherEntityTypes>

</identity>





<otherEntityTypes>
Other Entity Types  [toc]
Summary:
An optional child element of <identity> used for grouping one or more <otherEntityType> elements.
May contain:
May occur within:
Description and Usage:
A wrapper element used to group one or more <otherEntityType> elements. These elements are used to encode any additional or alternative entity types used for the CPF instance in addition to the required <entityType> element with values of corporateBody, person or family.
<otherEntityTypes> must include at least one <otherEntityType> element.
<descriptiveNote> can be used to add any additional descriptive information to the <otherEntityTypes>.
The prescribed order of all child elements (both required and optional) is:
<otherEntityType>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<otherEntityTypes>
<otherEntityType>
<term>Non-governmental organization</term>

</otherEntityType>

<otherEntityType>
<term>Organization</term>

</otherEntityType>

</otherEntityTypes>





<otherRecordId>
Other Record Identifier  [toc]
Summary:
An optional child element of <control> that encodes any local identifier for the EAC-CPF instance.
Attribute usage:
Use @localType to identify the institution or service responsible for providing the associated record identifier, if not the same as that given in <maintenanceAgency>.

May contain:
[text]
May occur within:
Description and Usage:
<otherRecordId> can be used to record an identifier that is an alternative to the mandatory identifier provided in <recordId>. These might include the identifiers of merged EAC-CPF instances representing the same CPF entity or those of records that are no longer current but had some part in the history and maintenance of the EAC-CPF instance.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<otherRecordId localType="PARES" localTypeDeclarationReference="lTD1">140149</otherRecordId>



<otherRecordId localType="original">AUBT-ISAAR-C-002</otherRecordId>





<p>
Paragraph  [toc]
Summary:
A general purpose element used to encode blocks of text.
May contain:
May occur within:
Description and Usage:
Use <p> for blocks of text. A paragraph may be a subdivision of a larger composition or it may exist alone. It is usually typographically distinguished: A line space is often left blank before it; the text begins on a new line; and the first letter of the first word may be indented, enlarged, or both.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <descriptiveNote>: required, repeatable.
Within all other parents: optional, repeatable.
Example:
<biogHist>
<p>Robert Carlton Brown (1886-1959) was a writer, editor, publisher, and traveler. From 1908 to 1917, he wrote poetry and prose for numerous magazines and newspapers in New York City, publishing two pulp novels,
<span style="font-style:italic">What Happened to Mary</span>

and
<span style="font-style:italic">The Remarkable Adventures of Christopher Poe</span>

(1913), and one volume of poetry,
<span style="font-style:italic">My Marjonary</span>

(1916).</p>

<p>During 1918, he traveled extensively in Mexico and Central America, writing for the U.S. Committee of Public Information in Santiago de Chile. In 1919, he moved with his wife, Rose Brown, to Rio de Janeiro, where they founded
<span style="font-style:italic">Brazilian American</span>

, a weekly magazine that ran until 1929. With Brown's mother, Cora, the Browns also established magazines in Mexico City and London:
<span style="font-style:italic">Mexican American</span>

(1924-1929) and
<span style="font-style:italic">British American</span>

(1926-1929).</p>

</biogHist>





<part>
Part  [toc]
Summary:
A required and repeatable child of <nameEntry> and <targetEntity> used to distinguish components of the CPF entity's name, or the name of a related entity, respectively.
Attribute usage:
The designation of the information contained in the <part> can be specified by the attribute @localType.

May contain:
[text]
May occur within:
Description and Usage:
Within <nameEntry> each of the components of a name, such as forename, surname or honorific title, may be recorded in a separate <part> element. <part> may also contain the full name of the entity when it is not possible to distinguish the different components of the name.
<part> cannot be empty and requires at least one non-whitespace character, such as a hyphen, if no actual name can be given.
Within <targetEntity> the name or term for the related entity is encoded within <part> elements.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Examples:
<nameEntry languageOfElement="de" preferredForm="true" status="authorized" localType="native">
<part localType="surname">Arendt</part>

<part localType="firstname">Hannah</part>

</nameEntry>



<nameEntry conventionDeclarationReference="cd1" preferredForm="true">
<part>Provence-Alpes-Côte d'Azur</part>

</nameEntry>





<place>
Place  [toc]
Summary:
An element that provides information about a place or jurisdiction, including places where the CPF entity was based, lived, or with which it had some other significant connection.
May contain:
May occur within:
Description and Usage:
A <place> element is a wrapper element used to encode information about a place or jurisdiction. This includes identifying the places or jurisdictions where the CPF entity was based, lived, or with which it had some other significant connection. It can also be used to encode address and contact information.
<place> must include at least one of <address>, <contact>, <geographicCoordinates>, <placeName> or <placeRole>.
<placeName> may be used to encode the name of a place that is related to the CPF entity described. The <placeRole> element is available to specify the nature of the connection of the place with the CPF entity being described, and its use is strongly recommended. Terms in <placeName> and <placeRole> may be drawn from controlled vocabularies or may be natural language terms. These controlled vocabularies can be identified with the vocabularySource and vocabularySourceURI attributes.
The <address> element is available for specifying a postal or other address. The <contact> element is available for specifying a digital address or other contact information.
Associated date or date range (<date>, <dateRange>, or <dateSet>) information may be included to further constrain the place's meaning. A <descriptiveNote> may be included if a fuller explanation of the significance of the place to the CPF entity described is needed.
The prescribed order of all child elements (both required and optional) is:
One or more of <address>, <contact>, <geographicCoordinates>, <placeName>, and <placeRole>



One of <date>, <dateRange>, or <dateSet>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <chronItem>: optional, not repeatable.
Within <chronItemSet>, <relation>: optional, repeatable.
Within <places>: required, repeatable.
Examples:
<place>
<placeRole>Residence</placeRole>

<placeName valueURI="http://vocab.getty.edu/page/tgn/7008153" vocabularySource="tgn" vocabularySourceURI="https://www.getty.edu/research/tools/vocabularies/tgn/index.html" id="IDPlaceName01">Kent (county)</placeName>

</place>



<place>
<placeName vocabularySource="local" id="IDPlaceName1">East Side (Buffalo, N.Y.)</placeName>

<geographicCoordinates coordinateSystem="WGS84">N 42°53′48" W 78°50′2"</geographicCoordinates>

</place>





<placeName>
Place Name  [toc]
Summary:
An optional child element of <place> used to encode the name of a place or geographic feature that is related to the CPF entity described.
Attribute usage:
The @vocabularySource attribute may be used to indicate the controlled vocabulary from which the <placeName> term is derived.

May contain:
[text]
May occur within:
Description and Usage:
<placeName> should be identified by the proper noun that commonly designates the place, natural feature, or political jurisdiction. It is recommended that place names be taken from authorized vocabularies.
Within <place>, a companion <placeRole> is strongly recommended to describe the nature of the association of the <placeName> to the entity. Furthermore a companion <geographicCoordinates> is available beside <placeName>, when used within <place>, to encode latitude, longitude and altitude information.
At least one of <placeName>, <placeRole>, <geographicCoordinates>, <address>, or <contact> is required within <place>.
The <placeName> element is repeatable. It is strongly recommended that within <place>, the <placeName> element be repeated only to represent the same place name in various languages, with an accompanying languageOfElement attribute.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<place>
<placeName vocabularySource="local" id="IDPlaceName1">East Side (Buffalo, N.Y.)</placeName>

<geographicCoordinates coordinateSystem="WGS84">N 42°53′48" W 78°50′2"</geographicCoordinates>

</place>



<place>
<placeName localType="place">Clear Spring</placeName>

<placeName localType="state">Maryland</placeName>

<geographicCoordinates coordinateSystem="UTM">18S 248556mE 4393694mN</geographicCoordinates>

</place>





<placeRole>
Place Role  [toc]
Summary:
An optional child element of <place> used to identify the contextual role the place or jurisdiction has in relation to the CPF entity described.
Attribute usage:
The @vocabularySource attribute may be used to indicate the controlled vocabulary from which the <placeRole> is derived.

May contain:
[text]
May occur within:
Description and Usage:
<placeRole> provides a contextual role for a <placeName> within <place>. Places should be identified in <placeName> by the proper noun that commonly designates the place, natural feature, or political jurisdiction. It is strongly recommended that each <placeName> is accompanied by a <placeRole> element in order to describe the nature of the association of the place to the CPF entity.
At least one of <placeRole>, <placeName>, <geographicCoordinates>, <address>, or <contact> is required within <place>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<place>
<placeName valueURI="https://d-nb.info/gnd/4057648-6" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Stockholm</placeName>

<placeRole valueURI="https://d-nb.info/standards/elementset/gnd#placeOfBirth" vocabularySource="GNDO" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#">Geburtsort</placeRole>

</place>



<place>
<placeRole>Residence</placeRole>

<placeName valueURI="http://vocab.getty.edu/page/tgn/7008153" vocabularySource="tgn" vocabularySourceURI="https://www.getty.edu/research/tools/vocabularies/tgn/index.html" id="IDPlaceName01">Kent (county)</placeName>

</place>





<places>
Places  [toc]
Summary:
An optional child element of <description> used for grouping together one or more <place> elements.
May contain:
May occur within:
Description and Usage:
Use the optional <places> element to group together one or more occurrences of <place>. <places> must include at least one <place> element. A <descriptiveNote> element may be included if a fuller textual explanation is needed.
The prescribed order of all child elements (both required and optional) is:
<place>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<places>
<place>
<placeName valueURI="https://d-nb.info/gnd/4057648-6" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Stockholm</placeName>

<placeRole valueURI="https://d-nb.info/standards/elementset/gnd#placeOfBirth" vocabularySource="GNDO" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#">Geburtsort</placeRole>

</place>

<place>
<placeName valueURI="https://d-nb.info/gnd/4051594-1" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Sankt Gallen</placeName>

Sterbeort</place>

</places>





<recordId>
Record Identifier  [toc]
Summary:
A required child element of <control> that designates a unique identifier for the EAC-CPF instance.
See also:
Use <agencyCode> in combination with <recordId> to provide a globally unique identifier for the EAC-CPF instance.

May contain:
[text]
May occur within:
Description and Usage:
<recordId> is used for recording a unique identifier for the EAC-CPF instance. The institution assigning the identifier ensures uniqueness of the <recordId> value within the archival descriptions under its control. A globally unique identifier may be constructed within <recordId> according to various external protocols (i.e. HTTP URI, DOI, PURL, or UUID), or in combination with <agencyCode>, which is an optional element within <maintenanceAgency>.
<recordId> cannot be empty. Any alternative or additional record identifiers may be recorded in <otherRecordId>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Examples:
<recordId>F10219</recordId>



<recordId>ES-28079-PARES-AUT-140149</recordId>



<recordId>DE-1981_EAC-CPF_C002</recordId>





<reference>
Reference  [toc]
Summary:
An element that cites an external resource.
Attribute usage:
Use @href to link to the cited resource.

See also:
<reference> is used for external linking only. If any internal linking is required within the EAC-CPF instance, use the @target attribute.

May contain:
[text], span (0..n)
May occur within:
Description and Usage:
An element used for referencing external resources that have been used to compile the EAC-CPF instance, that provide additional context to the EAC-CPF instance, or that identify rules or conventions that have been applied.
<reference> is a required child element of <conventionDeclaration>, <localTypeDeclaration>, and <rightsDeclaration> for identifying any rules and conventions applied in the compilation of the description. It is also a required child element of <source>, used to identify any sources used in compiling the description. <source> may include multiple child <reference> elements.
<reference> is an optional child element of <abstract>, <chronItem>, <chronItemSet>, <event>, <eventDescription>, <item>, and <p> where it is used to reference any external resources that provide additional context to the content of that element.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Within <conventionDeclaration>, <localTypeDeclaration>, <rightsDeclaration>: required, not repeatable
Within <source>: required, repeatable
Within <abstract>, <chronItem>, <chronItemSet>, <event>, <eventDescription>, <item>, <p>: optional, repeatable
Examples:
<source>
<reference href="https://de.wikipedia.org/wiki/Gustav_IV._Adolf_(Schweden)">Wikipedia</reference>

</source>



<conventionDeclaration>
<reference href="https://www.loc.gov/aba/rda/">Resource Description and Access</reference>

<shortCode>RDA</shortCode>

</conventionDeclaration>





<relation>
Relation  [toc]
Summary:
A required child element of <relations> for describing a relationship between the entity described in the EAC-CPF instance and a related entity.
May contain:
May occur within:
Description and Usage:
<relation> records descriptive information about a relationship between the entity being described and a related entity, such as: a corporate body, person, or family; a function; or an archival, bibliographic, or other resource.
Use the required child element <targetEntity> to provide a textual identification of the related entity, such as a name or a title. Use the optional child element <relationType> to specify the type of relation. Use the optional child element <targetRole> to specify the role of the related entity. It is recommended that the terms used in <relationType>, <targetEntity>, and <targetRole> be taken from an authorized vocabulary.
Use <objectXMLWrap> to embed XML documenting the related entity from any namespace. Use <date>, <dateRange>, or <dateSet> for specifying the time period of the relationship and <place> for relevant location information. <descriptiveNote> may be included for more detailed specifications or explanations of the relationship.
The prescribed order of all child elements (both required and optional) is:
<targetEntity>



One of <date>, <dateRange>, or <dateSet>



One or more of <place>, <relationType>, and <targetRole>



<descriptiveNote>



<objectXMLWrap>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Examples:
<relation>
<targetEntity targetType="resource">
<part>Mémorial du colonel Gustafsson. - 1829</part>

</targetEntity>

<relationType>creation</relationType>

<targetRole>Publication</targetRole>

</relation>



<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/120636123" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Sophie</part>

<part>Baden, Großherzogin</part>

<part>1801-1865</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>daughter</targetRole>

</relation>





<relations>
Relations  [toc]
Summary:
An optional child element of <cpfDescription> that groups one or more <relation> elements, which identify external entities and characterize the nature of their relationships to the entity being described.
May contain:
May occur within:
Description and Usage:
A wrapper element that groups together one or more <relation> elements, each of which encodes a specific relationship.
The prescribed order of all child elements (both required and optional) is:
<relation>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<relations>
<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/119067159X" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Arendt, Max</part>

<part>1843-1913</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>grandfather</targetRole>

</relation>

<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/1190672170" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Arendt-Beerwald, Martha</part>

<part>1874-1948</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>mother</targetRole>

</relation>

<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/1190671301" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Arendt, Paul</part>

<part>1873-1913</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>father</targetRole>

</relation>

</relations>





<relationType>
Relation Type  [toc]
Summary:
A child element of <relation> used to specify the type of relation that the entity being described within the EAC-CPF instance has to the <targetEntity>.
May contain:
[text]
May occur within:
Description and Usage:
Use <relationType> within <relation> to specify the type of relation that the entity being described has to the <targetEntity>.
The <relationType> element contains a textual description of the relation. It is recommended that values used in <relationType> be taken from an authorized vocabulary.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/120636123" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Sophie</part>

<part>Baden, Großherzogin</part>

<part>1801-1865</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>daughter</targetRole>

</relation>



<relation>
<targetEntity targetType="corporateBody" valueURI="https://d-nb.info/gnd/37101-4" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Königliche Bibliothek zu Berlin</part>

</targetEntity>

<relationType>has ancestor</relationType>

</relation>





<representation>
Representation  [toc]
Summary:
An optional child element of <control> for recording a link to a deliverable version of the EAC-CPF instance or to the XML version of the EAC-CPF instance itself.
Attribute usage:
Use @href to specify a link to a deliverable version of the EAC-CPF instance.

Use @localType to differentiate between multiple <representation> elements.

See also:
Use <otherRecordId> to provide any local identifier for the EAC-CPF instance that does not link to a deliverable version.

May contain:
[text]
May occur within:
Description and Usage:
Use <representation> to record a link to a deliverable version of an EAC-CPF instance, for example an HTML or PDF version, or to the XML version of the EAC-CPF instance itself.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" maintenanceStatus="new" publicationStatus="published" repositoryEncoding="iso15511" scriptEncoding="iso15924">
<recordId>122651634</recordId>

[...]
<representation href="https://kalliope-verbund.info/gnd/122651634"></representation>

</control>



<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" maintenanceStatus="revised" publicationStatus="published" repositoryEncoding="iso15511" scriptEncoding="iso15924">
<recordId>738070</recordId>

[...]
<representation href="https://trove.nla.gov.au/people/738070?c=people">Osburn, Lucy (1835-1891) - People and organisations - Trove</representation>

</control>





<rightsDeclaration>
Rights Declaration  [toc]
Summary:
An optional child element of <control> that indicates a standard rights statement associated with the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
Use <rightsDeclaration> to provide structured information about the usage rights of the EAC-CPF instance. <rightsDeclaration> should only be used to reference shared published licenses, such as Creative Commons, RightsStatements.org, or published locally-defined licenses.
<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:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<rightsDeclaration>
<reference href="https://creativecommons.org/publicdomain/zero/1.0/deed.de">Creative Commons CC0 1.0 Universal (CC0 1.0) Public Domain Dedication</reference>

<shortCode>CC0 1.0</shortCode>

</rightsDeclaration>





<setComponent>
Set Component  [toc]
Summary:
A required child element of <alternativeSet> that allows an alternative authority record of the EAC-CPF instance being described to be referenced and described, as well as allowing the inclusion of the entire encoding of such alternative authority record in any XML format.
Attribute usage:
Use @href to provide a general reference to alternative sets.

May contain:
May occur within:
Description and Usage:
<setComponent> provides a wrapper to link to, describe, or contain one or more alternative authority record, so that multiple records for the same entity from separate authority systems, or in different languages, may be combined together within a single EAC-CPF instance.
The <componentEntry> child element allows for the provision of a name or title for the alternative authority record and the inclusion of a link to the record in an external system, if using a vocabulary or similar.
Use the optional <descriptiveNote> for a textual note providing further information about the record referenced in <setComponent>.
Use the optional <objectXMLWrap> child element when including the entire authority record within the EAC-CPF instance.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<alternativeSet>
<setComponent href="http://nla.gov.au/anbd.aut-an35824899" linkTitle="Law, P. G. (Phillip Garth), 1912-2010 - Full record view - Libraries Australia Search">
<componentEntry>Libraries Australia record.</componentEntry>

</setComponent>

<setComponent href="https://www.eoas.info/biogs/P001333b.htm" linkTitle="Law, Phillip Garth - Biographical entry - Encyclopedia of Australian Science">
<componentEntry>Encyclopedia of Australian Science record.</componentEntry>

</setComponent>

<setComponent>
<objectXMLWrap>
<eac-cpf xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:isbn:1-931666-33-4 http://eac.staatsbibliothek-berlin.de/schema/cpf.xsd"> [...] </eac-cpf>

</objectXMLWrap>

</setComponent>

</alternativeSet>





<shortCode>
Short Code  [toc]
Summary:
An optional element for encoding the shortened form of a word or phrase.
May contain:
[text]
May occur within:
Description and Usage:
Used to record the shortened form of a word or phrase, for example, an acronym.
Use <shortCode> within <conventionDeclaration> or <localTypeDeclaration> to identify the code for a thesaurus, controlled vocabulary, or another standard used in creating the EAC-CPF description. Use within <rightsDeclaration> to provide an abbreviated name for the rights statement.
To improve interoperability, it is recommended that the value be selected from an authorized list of codes such as the MARC Code List (http://www.loc.gov/marc/sourcelist/).
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<conventionDeclaration id="conventiondeclaration1">
<reference>Anglo-American Cataloging Rules, Revised</reference>

<shortCode>AACR2</shortCode>

</conventionDeclaration>





<source>
Source  [toc]
Summary:
A required child element of <sources> used to identify a particular source of evidence used for the establishment of the description of the CPF entity in the EAC-CPF instance.
May contain:
May occur within:
Description and Usage:
Use <source> to cite a published resource used in describing the CPF entity. Use the required child element <reference>to include a textual identification of the reference. In the case of online sources, use href with <reference> to provide a URI.
Use the optional child element <citedRange> to point to a specific location within a source.
Use the optional <descriptiveNote> for any additional notes about the source. Use the optional <objectXMLWrap> to embed XML documenting the source from any namespace.
The prescribed order of all child elements (both required and optional) is:
<reference>



<citedRange>



<descriptiveNote>



<objectXMLWrap>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Example:
<sources>
<source>
<reference href="https://de.wikipedia.org/wiki/Gustav_IV._Adolf_(Schweden)">Wikipedia</reference>

</source>

<source>
<reference href="https://sok.riksarkivet.se/sbl/Presentation.aspx?id=13318">Svenskt biografiskt lexikon</reference>

<descriptiveNote>
<p>Stand: 03.12.2020</p>

</descriptiveNote>

</source>

</sources>





<sources>
Sources  [toc]
Summary:
An optional child element of <control> that groups one or more <source>s of evidence used in the description of the CPF entity in the EAC-CPF instance.
Attribute usage:
Use @base to specify a URI (other than the base URI of the EAC-CPF instance) to be used for resolving relative URIs within <sources> or descendant elements.

May contain:
May occur within:
Description and Usage:
Use <sources> to bind together one or more <source> elements. <sources> must include at least one <source> element.
The prescribed order of all child elements (both required and optional) is:
<source>



<descriptiveNote>



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, not repeatable
Example:
<sources>
<source>
<reference>Provenienzmerkmal</reference>

</source>

<source>
<reference href="http://staatsbibliothek-berlin.de/die-staatsbibliothek/geschichte/">
<descriptiveNote>
<p>Stand: 31.07.2018</p>

</descriptiveNote>

</reference>

</source>

</sources>





<span>
span  [toc]
Summary:
Specifies the beginning and the end of a span of text.
Attribute usage:
Use the optional @style attribute to affect an arbitrary stylistic difference.

Use the optional @localType attribute to identify qualities of words or phrases.

May contain:
[text]
May occur within:
Description and Usage:
<span> is an optional formatting element for distinguishing words or phrases that are intentionally stressed or emphasized for linguistic effect or identifying some qualities of the words or phrases.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<biogHist>
<p>Robert Carlton Brown (1886-1959) was a writer, editor, publisher, and traveler. From 1908 to 1917, he wrote poetry and prose for numerous magazines and newspapers in New York City, publishing two pulp novels,
<span style="font-style:italic">What Happened to Mary</span>

and
<span style="font-style:italic">The Remarkable Adventures of Christopher Poe</span>

(1913), and one volume of poetry,
<span style="font-style:italic">My Marjonary</span>

(1916).</p>

<p>During 1918, he traveled extensively in Mexico and Central America, writing for the U.S. Committee of Public Information in Santiago de Chile. In 1919, he moved with his wife, Rose Brown, to Rio de Janeiro, where they founded
<span style="font-style:italic">Brazilian American</span>

, a weekly magazine that ran until 1929. With Brown's mother, Cora, the Browns also established magazines in Mexico City and London:
<span style="font-style:italic">Mexican American</span>

(1924-1929) and
<span style="font-style:italic">British American</span>

(1926-1929).</p>

</biogHist>





<structureOrGenealogy>
Structure or Genealogy  [toc]
Summary:
An optional child element of <description> used to describe internal administrative structure(s) of a corporate body or the genealogy of a family.
May contain:
May occur within:
Description and Usage:
<structureOrGenealogy> encodes information expressing the internal administrative structure(s) of a corporate body and the dates of any changes to that structure that are significant to understanding the way that corporate body conducted affairs (such as dated organization charts), or the genealogy of a family (such as a family tree) in a way that demonstrates the interrelationships of its members with relevant dates.
The optional <list> element may be used to accommodate greater complexity in expressing or representing the structure(s) or genealogy being described. <head> may be used to encode a title or caption. A simpler discursive expression of the structure(s) or genealogy may be encoded as one or more <p> elements.
The prescribed order of all child elements (both required and optional) is:
<head>



One or both of <list> or <p>.



Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Examples:
<structureOrGenealogy>
<p>Sir Edward Noel (d 1643) married Julian, daughter and co-heir of Baptists Hicks (d 1629), Viscount Campden, and succeeded to the viscouty of Campden and a portion of his father-in-law's estates. The third Viscount Campden (1612-82) married Hester Wotton, daughter of the second Baron Wotton. The fourth Viscount Campden (1641-1689, created Earl of Gainsborough, 1682) married Elizabeth Wriothesley, elder daughter of the fourth Earl of Southampton. Jane Noel (d 1811), sister of the fifth and sixth Earls of Gainsborough, married Gerard Anne Edwards of Welham Grove (Leicetershire) and had issue Gerard Noel Edwards (1759-1838). He married in 1780 Diana Middleton (1762-1823 suo jure Baroness Barham), daughter of Charles Middleton (1726-1813), created first Baronet of Barham Court (Kent) in 1781 and first Baron Barham in 1805. GN Edwards assumed the surname Noel in 1798 on inheriting the sixth Earl of Gainborough's Rutland and Gloucestershire estates (though not the Earl's honours, which were extinguished); and he later inherited his father-in-law's baronetcy. His eldest son John Noel (1781-1866) succeeded to the estates of his mother and his father, to his mother's barony and his father's baronetcy, and was created Viscount Campden and Earl of Gainsborough in 1841.</p>

</structureOrGenealogy>



<structureOrGenealogy>
<p>The organogram of the
<span style="font-style:italic">Ministry of Culture and Tourism</span>

before its incorporation with the Ministry of Education and Religious Affairs, was the following:</p>

<list>
<item>Minister of Culture and Tourism</item>

<list>
<item>Deputy Minister of Culture and Tourism</item>

<list>
<item>General Secretary of Tourism</item>

<item>General Secretary of Sports</item>

<item>General Secretary of Culture</item>

<item>General Secretary for Culture and Tourism Infrastructure</item>

</list>

</list>

</list>

</structureOrGenealogy>





<targetEntity>
Target Entity  [toc]
Summary:
A required child element of <relation> used to identify the entity that is being targeted by the relation.
Attribute usage:
Use the required @targetType, to identity the type of entity related to in <targetEntity>, using one of the following values: "agent", "corporateBody", "family", "function", "person", or "resource".

May contain:
May occur within:
Description and Usage:
<targetEntity> is used within <relation> to identify an entity that is related to the subject of the EAC-CPF instance.
<targetEntity> must include at least one <part> element, encoding the name or term for the related entity.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Required (values limited to: agent, corporateBody, family, function, person, resource)
 
Optional
 
Optional
 
Optional
Availability:
Required, not repeatable
Examples:
<relation>
<targetEntity targetType="resource">
<part>La journée du treize mars. - 1835</part>

</targetEntity>

</relation>



<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/117145971" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Wasa, Gustav</part>

<part>Prinz von</part>

<part>1799-1877</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>son</targetRole>

</relation>





<targetRole>
Target Role  [toc]
Summary:
An optional child element of <relation> used to specify the role of a related entity with respect to the CPF entity being described.
May contain:
[text]
May occur within:
Description and Usage:
<targetRole> is used with <relation> to specify the role of a related entity with respect to the CPF entity being described.
The <targetRole> element contains a textual description of the relation. It is recommended that the terms in <targetRole> be taken from authorized vocabularies.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/119067159X" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Arendt, Max</part>

<part>1843-1913</part>

</targetEntity>

<relationType>family</relationType>

<targetRole>grandfather</targetRole>

</relation>





<term>
Term  [toc]
Summary:
An element used to encode a descriptive term in accordance with authorized vocabularies or local rules.
May contain:
[text]
May occur within:
Description and Usage:
<term> is a required child element of <function>, <legalStatus>, <localControl>, <localDescription>, <mandate>, <occupation>, and <otherEntityType>, used to specify a descriptive term in accordance with authorized vocabularies or local rules.
<term> can be repeated within its parent element to include translations of the same term. Use the languageOfElement attribute to identify the language used in each <term> grouped within a single parent element.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Required, repeatable
Examples:
<function>
<term>Estate ownership</term>

<descriptiveNote>
<p>Social, political, and cultural role typical of landed aristocracy in England. The first Viscount Campden amassed a large fortune in trade in London and purchased extensive estates, including Exton (Rutland), and Chipping Campden (Gloucestershire). The Barham Court (Kent) estate was the acquisition of the first Baron Barham, a successful admiral and naval administrator (First Lord of the Admiralty 1805).</p>

</descriptiveNote>

</function>



<function>
<term vocabularySource="AGIFT">Education and training</term>

</function>



<legalStatus>
<term scriptCode="Latn">Organismo de la Administracion Central del Estado</term>

<date standardDate="1769">1769</date>

</legalStatus>



<mandate>
<term>Minnesota. Executive Session Laws 1919 c49</term>

<dateRange>
<fromDate standardDate="1919">1919</fromDate>

<toDate standardDate="1925">1925</toDate>

</dateRange>

<descriptiveNote>
<p>Board created in 1919 to receive and examine applications for bonuses from Minnesota soldiers.</p>

</descriptiveNote>

</mandate>



<occupation>
<term>Teacher</term>

</occupation>





<toDate>
To Date  [toc]
Summary:
A child element of <dateRange> that records the end point in a range of dates.
Attribute usage:
Use @certainty to indicate the degree of precision in the dating, for example, "uncertain" or "approximate".

Use @localType to supply a more specific characterization of the start date.

Use @notAfter and @notBefore to capture the latest and earliest possible dates in machine-processable form in cases when the date is uncertain.

Use @standardDate to provide a machine-processable form of the date.

Use @status with the values "unknown" or "ongoing" to indicate where part of a date range is unknown, or the date range is ongoing.

See also:
Use <fromDate> to record the starting point of a date range.

May contain:
[text]
May occur within:
Description and Usage:
Use <toDate> to record the end date in a range of dates, whether they be known, approximate or unknown. The content of the element is intended to be a human-readable, natural language expression of the date. If, however, indexing or other machine processing of dates is desired, the standardDate should be used to record the date in machine-processable form as well. <toDate> may be omitted from <dateRange>, or the status attribute used, if the date span is ongoing or the <toDate> is unknown.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional (values limited to: ongoing, unknown)
 
Optional
 
Optional
Availability:
Optional, not repeatable
Examples:
<existDates>
<dateRange>
<fromDate standardDate="1868">1868</fromDate>

<toDate standardDate="1936">1936</toDate>

</dateRange>

</existDates>



<dateRange>
<fromDate status="unknown"></fromDate>

<todate certainty="uncertain" standardDate="2010?">c.2010</todate>

</dateRange>



<dateRange>
<fromDate standardDate="2016-09">September 2016</fromDate>

<toDate status="ongoing"></toDate>

</dateRange>





<useDates>
Dates of Use  [toc]
Summary:
An optional child element of <nameEntry> and <nameEntrySet> that provides the dates when the name or names were used for or by the CPF entity being described.
May contain:
May occur within:
Description and Usage:
Within <nameEntry>, <useDates> provides the dates during which the name was used for or by the CPF entity. For parallel names (e.g., official forms of the name in different languages and/or scripts), <useDates> may occur in <nameEntrySet> rather than in the individual <nameEntry> elements contained in <nameEntrySet>.
<useDates> must include one of <date>, <dateRange>, or <dateSet>.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<nameEntry status="authorized">
<part>Technical Subcommittee for Encoded Archival Standards</part>

<useDates>
<dateRange>
<fromDate>2015</fromDate>

<toDate status="ongoing"></toDate>

</dateRange>

</useDates>

</nameEntry>





<writingSystem>
Writing System  [toc]
Summary:
An optional child element of <languageUsed> that identifies the writing script for a language in which the CPF entity being described was creative or productive.
Attribute usage:
Use @scriptCode to provide a code for the writing system itself.

Use @scriptOfElement to provide a code for the writing system in which the element is given.

May contain:
[text]
May occur within:
Description and Usage:
An optional element within <languageUsed> that gives the main script used by the CPF entity being described in his/her creative or productive work.
Attributes:
 
Optional (values limited to: external, internal)
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
 
Optional
Availability:
Optional, repeatable
Example:
<languageUsed>
<language languageCode="eng">English</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>





  [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.
@addressLineType
 Address Line Type  [toc]
Summary:
Used to specify the type of address line encoded in <addressLine>.
Description and Usage:
Use one of the set values to specify the type of address line encoded in <addressLine>. Use the attribute localType in order to encode a local type of address line.
Values:
county, country, district, municipality, postBox, postalCode, region, street
Example:
<address>
<addressLine languageOfElement="se">Kungl. Hovstaterna</addressLine>

<addressLine languageOfElement="se">Kungl. Slottet</addressLine>

<addressLine addressLineType="postalCode">10770</addressLine>

<addressLine languageOfElement="se" addressLineType="municipality">Stockholm</addressLine>

<addressLine languageOfElement="se" addressLineType="country">Sverige</addressLine>

<addressLine languageOfElement="en" addressLineType="country">Sweden</addressLine>

</address>





 
@agentType
 Agent Type  [toc]
Summary:
A required attribute of <agent> that indicates the type of agent responsible for the creation, modification, or deletion of an EAC-CPF instance.
Description and Usage:
The attribute's value must be set to "human," "machine," or "unknown," and should correspond to the information recorded in <agent>. For example, if the <agent> is Jane Marshall, the value of agentType should be set to "human." If the <agent> is a database, style sheet, or other system, the value of agentType should be set to "machine." The value of agentType may also be set to "unknown" if the agent and/or type of agent cannot be determined.
Values:
human, machine, unknown
Example:
<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">A. Smith</agent>

<eventDateTime standardDateTime="2021-12">December 2021</eventDateTime>

</maintenanceEvent>





 
@audience
 Audience  [toc]
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 <cpfDescription> to allow access to all the information about the entity being described, but specific elements within <cpfDescription> 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 EAC-CPF instance is displayed in a networked environment.
Values:
external, internal
Example:
<eac audience="external"> [...] </eac>





 
@base
 Base  [toc]
Summary:
Optional attribute used to specify a base URI that is different to the base URI of the EAC-CPF instance.
Description and Usage:
Using the optional attribute base allows any relative URIs provided on attributes of a specific element, or its descendants, to be resolved using the URI provided in that element's or its parent element's base.
Available on <alternativeSet>, <control>, <cpfDescription>, <description>, <eac>, <identity>, <multipleIdentities>, <relations>, and <sources>.
Data Type:
anyURI
Example:
<description base="https://d-nb.info/gnd/">
<occupations>
<occupation vocabularySource="GND" valueURI="4393865-6">
<term languageOfElement="de">Soziologin</term>

</occupation>

<occupation vocabularySource="GND" valueURI="4629643-8">
<term languageOfElement="de">Politologin</term>

</occupation>

<occupation vocabularySource="GND" valueURI="4174285-0">
<term languageOfElement="de">Philosophin</term>

</occupation>

<occupation vocabularySource="GND" valueURI="4333423-4">
<term languageOfElement="de">Historikerin</term>

</occupation>

<occupation vocabularySource="GND" valueURI="4053311-6">
<term languageOfElement="de">Schriftstellerin</term>

</occupation>

</occupations>

<places>
<place vocabularySource="GND" valueURI="4099668-2">
<placeName>Linden (Hannover)</placeName>

</place>

<place vocabularySource="GND" valueURI="4042011-5">
<placeName>New York, NY</placeName>

</place>

<place vocabularySource="GND" valueURI="4537442-9">
<placeName>Tegna</placeName>

</place>

</places>

</description>





 
@calendar
 Calendar  [toc]
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>, and <toDate>.
Data Type:
NMTOKEN
Example:
<dateRange>
<fromDate calendar="gregorian" certainty="approximate" era="ce" standardDate="1950">1950</fromDate>

<toDate calendar="gregorian" certainty="approximate" era="ce" standardDate="2000">2000</toDate>

</dateRange>





 
@certainty
 Certainty  [toc]
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:
NMTOKEN
Example:
<date certainty="uncertain" standardDate="1968?">c.1968</date>





 
@contactLineType
 Contact Line Type  [toc]
Summary:
Used to specify the type of contact line encoded in <contactLine>.
Description and Usage:
Use one of the set values to specify the type of contact line encoded in <contactLine>. Use the attribute localType to encode a local type of contact line.
Values:
directions, email, fax, homepage, mobileNumber, phoneNumber
Example:
<contact>
<contactLine contactLineType="phoneNumber">08-402 60 00</contactLine>

<contactLine languageOfElement="se" contactLineType="homepage">https://www.kungahuset.se/2.1c3432a100d8991c5b80001816.html</contactLine>

<contactLine languageOfElement="en" contactLineType="homepage">https://www.kungahuset.se/royalcourt.4.367010ad11497db6cba800054503.html</contactLine>

</contact>





 
@conventionDeclarationReference
 Convention Declaration Reference  [toc]
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 an EAC-CPF name.
This optional attribute is available in all elements in the identity area (except <entityType>), in the description area and in relations.
Data Type:
IDREFS
Example:
<nameEntrySet languageOfElement="fre">
<nameEntry conventionDeclarationReference="cd1" preferredForm="true">
<part>Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd2">
<part>Région Sud Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd3">
<part>Provence-Alpes-Côte-d'Azur</part>

</nameEntry>

</nameEntrySet>





 
@coordinateSystem
 Coordinate System  [toc]
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:
<geographicCoordinates coordinateSystem="mgrs">33UUU9029819737</geographicCoordinates>



<geographicCoordinates coordinateSystem="WGS84">-81.1, 32.2, -81.0, 32.3</geographicCoordinates>





 
@countryCode
 Country Code  [toc]
Summary:
A unique code representing a country.
Description and Usage:
Content of the optional attribute should be a code taken from ISO 3166-1 Codes for the Representation of Names of Countries and their Subdivisions, column A2, or another controlled list, as specified in the countryEncoding attribute in <control>. Available in <maintenanceAgency> and <placeName>.
Data Type:
NMTOKEN
Examples:
<maintenanceAgency countrycode="IE">
<agencyCode>IE-NAI</agencyCode>

<agencyName>National Archives of Ireland</agencyName>

</maintenanceAgency>



<place>
<placeRole>Residence</placeRole>

<placeName countryCode="GR" vocabularySource="ISO3166-2">Greece</placeName>

</place>





 
@countryEncoding
 Country Encoding  [toc]
Summary:
The authoritative source or rules for values supplied in countryCode.
Description and Usage:
The authoritative source or rules for values supplied in countryCode in <maintenanceAgency> and <placeName>. If the value "otherCountryEncoding" is selected an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso3166-1, otherCountryEncoding
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@dateEncoding
 Date Encoding  [toc]
Summary:
The authoritative source or rules for values provided in standardDate.
Description and Usage:
The authoritative source or rules for values provided in standardDate in <date>, <fromDate> and <toDate>. If the value "otherDateEncoding" is selected an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
iso8601, otherDateEncoding
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@detailLevel
 Level of Detail  [toc]
Summary:
Provides information about the level of detail of the entity’s description within the EAC-CPF 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 of the entity's description, from a fixed set of values.
Values:
basic, extended, minimal
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" detailLevel="basic" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@era
 Era  [toc]
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 "ce" and "bce". This optional attribute is available in <date>, <fromDate>, and <toDate>.
Data Type:
NMTOKEN
Example:
<dateRange>
<fromDate calendar="gregorian" certainty="approximate" era="ce" standardDate="1950">1950</fromDate>

<toDate calendar="gregorian" certainty="approximate" era="ce" standardDate="2000">2000</toDate>

</dateRange>





 
@href
 Hypertext Reference  [toc]
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>, <representation>, <setComponent> and <source>.
Data Type:
anyURI
Example:
<conventionDeclaration id="cd1">
<reference href="https://www.legifrance.gouv.fr/loda/id/JORFTEXT000033553530/">Décret n° 2016-1689 du 8 décembre 2016 fixant le nom, la composition et le chef-lieu des circonscriptions administratives régionales - Légifrance</reference>

</conventionDeclaration>





 
@id
 ID  [toc]
Summary:
A unique identifier to name the element.
Description and Usage:
An identifier that must be unique within the current document and is used to name the element so that it can be referred to, or referenced from, somewhere else. This facilitates building links between the element and other resources.
Use target, conventionDeclarationReference, localTypeDeclarationReference, maintenanceEventReference, or sourceReference to link to an id attribute within the EAC-CPF instance.
Data Type:
ID
Example:
<occupations>
<occupation>
<term>Assistant examiner - level III</term>

<placeName target="#place1">Bern</placeName>

</occupation>

</occupations>

<places>
<place id="place1">
<placeName>Bern</placeName>

<placeRole>Place of work</placeRole>

</place>

</places>





 
@identityType
 Identity Type  [toc]
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 EAC-CPF instance using <multipleIdentities>. It will enable processors to distinguish between the description of a person and one or more personae.
Values:
acquired, given
Example:
<identity identityType="acquired" localType="pseudonym" localTypeDeclarationReference="LT001"> [...] </identity>





 
@languageCode
 Language Code  [toc]
Summary:
The code for the language used in the EAC-CPF instance or in the creative work of the CPF entity being described.
Description and Usage:
Content of the attribute should be a code taken from ISO 639-1, ISO 639-2b, ISO 639-3, or another controlled list, as specified in the languageEncoding attribute in <control>. Required in <languageDeclaration> and optionally available in <language>.
Data Type:
NMTOKEN
Example:
<languagesUsed>
<languageUsed>
<language languageCode="eng">English</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

<languageUsed>
<language languageCode="spa">Spanish</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

<descriptiveNote>
<p>Published works in English and Spanish.</p>

</descriptiveNote>

</languagesUsed>





 
@languageEncoding
 Language Encoding  [toc]
Summary:
Specifies which standard list of codes is used to identify the language of the EAC-CPF instance and languages represented in the creative work of the CPF entity being described.
Description and Usage:
The codes themselves are specified in languageCode in <language> and languageOfElement in all non-empty elements. Available in <control>. If the value "otherLanguageEncoding" is selected an alternate code list should be specified in <conventionDeclaration>. This optional attribute is available only in <control>.
Values:
ietf-bcp-47, iso639-1, iso639-2b, iso639-3, otherLanguageEncoding
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@languageOfElement
 Language of Element  [toc]
Summary:
Indicates the language of the content of an element.
Description and Usage:
Content of the attribute should be a code taken from ietf-bcp-47, ISO 639-1, ISO 639-2b, ISO 639-3, or another controlled list, as specified in the languageEncoding attribute in <control>. May be used consistently in a multi-lingual EAC-CPF instance to specify which elements are written in which language. Optionally available on all non-empty elements.
Data Type:
NMTOKEN
Example:
<agencyName languageOfElement="eng">Berlin State Library - Prussian Cultural Heritage, Kalliope Union Catalog</agencyName>





 
@linkRole
 Link Role  [toc]
Summary:
A URI that characterizes the nature of the remote resource to which a linking element refers.
Description and Usage:
A URI that characterizes the nature of the remote resource to which a linking element refers. Optionally available in <contactLine>, <reference>, <representation>, <setComponent>, and <source>.
Data Type:
anyURI
Example:
<reference href="https://deliberation.maregionsud.fr/docs/ASSEMBLEEPLENIERE/2017/12/15/DELIBERATION/D0V0Q.pdf" linkRole="document/pdf">DELIBERATION N° 17-1166, 15 DECEMBRE 2017</reference>





 
@linkTitle
 Link Title  [toc]
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 useful for meeting accessibility requirements when rendering content in a web browser. Optionally available next to href in <contactLine>, <reference>, <representation>, <setComponent>, and <source>.
Data Type:
token
Example:
<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>





 
@listType
 List Type  [toc]
Summary:
Specifies the type of list.
Description and Usage:
An ordered list is a numbered or lettered list; an unordered list is one in which sequence is not critical (e.g., a bulleted list). Optionally available only on <list>.
Values:
ordered, unordered
Example:
<list listType="unordered">
<head>List of ministers of May Memorial Unitarian Universalist Church</head>

<item>John Storer, Minister 1839-1844</item>

<item>Samuel Joseph May, Minister 1845-1868</item>

<item>Samuel R. Calthrop, Minister 1868-1911</item>

<item>John H. Applebee, Minister 1911-1929</item>

<item>Waldemar W. Argow, Minister 1930-1941</item>

<item>Robert E. Romig, Minister 1941-1946</item>

<item>Glenn O. Canfield, Minister 1946-1952</item>

<item>John Fuller, Minister, 1961-1973</item>

</list>





 
@localType
 Local Type  [toc]
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
Example:
<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" localTypeDeclarationReference="GNDO">Arendt, Hannah</part>

<part localType="https://d-nb.info/standards/elementset/gnd#dateOfBirthAndDeath" localTypeDeclarationReference="GNDO">1906-1975</part>

</nameEntry>





 
@localTypeDeclarationReference
 Local Type Declaration Reference  [toc]
Summary:
Use localTypeDeclarationReference to provide a direct link to a <localTypeDeclaration> element within <control> from another element using localType within the EAC-CPF instance.
Description and Usage:
localTypeDeclarationReference should always be used when localType is used, in order to link to the local type declaration.
Data Type:
IDREFS
Example:
<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" localTypeDeclarationReference="GNDO">Arendt, Hannah</part>

<part localType="https://d-nb.info/standards/elementset/gnd#dateOfBirthAndDeath" localTypeDeclarationReference="GNDO">1906-1975</part>

</nameEntry>





 
@maintenanceEventReference
 Maintenance Event Reference  [toc]
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 in the identity area (except <entityType>), in the description area, and in the relations.
Data Type:
IDREFS
Example:
<relation sourceReference="source1" maintenanceEventReference="me2">
<targetEntity targetType="corporateBody" valueURI="https://snaccooperative.org/ark:/99166/w63z1x39" vocabularySourceURI="https://snaccooperative.org">
<part>Princeton University</part>

</targetEntity>

<relationType valueURI="https://www.wikidata.org/wiki/Property:P69" vocabularySourceURI="https://www.wikidata.org/">educated at</relationType>

</relation>





 
@maintenanceEventType
 Maintenance Event Type  [toc]
Summary:
A required attribute of <maintenanceEvent> that provides a controlled list of values for recording the type of maintenance activity.
Description and Usage:
cancelled: marks an instance as not current (obsolete or rejected), but retained for reference



created: the initial creation of the EAC-CPF instance



deleted: indication that the instance has been deleted from the system



derived: indicates that the instance was derived from another descriptive system



revised: any type of general modification to the EAC-CPF instance



unknown: when the type of event is not known



updated: when an instance has been brought up to date with significant changes to the materials being described or to the version of EAC-CPF used



Values:
cancelled, created, deleted, derived, revised, unknown, updated
Example:
<maintenanceHistory>
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>

<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"></eventDateTime>

<eventDescription>Derived from EAD instance.</eventDescription>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>

<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>

<eventDateTime>December 2021</eventDateTime>

</maintenanceEvent>

</maintenanceHistory>





 
@maintenanceStatus
 Maintenance Status  [toc]
Summary:
The current drafting status of the EAC-CPF instance.
Description and Usage:
The maintenance status must occur on <control>. As an EAC-CPF instance is modified or other events happen to it (as recorded in the <maintenanceHistory> element), the maintenance status should also be updated to reflect the current drafting status.
On first creation the status would be "new", which on revision can be changed to "revised". Because it is important to be clear about what has happened to records, particularly when sharing and making links between them, a number of status values are available for records that are no longer current. A record that is simply deleted from a system can be given the status "deleted", but in cases where a record is marked as not current (obsolete or rejected) but kept for reference then it should be given the status "cancelled". If a record is deleted because it has become superseded by two or more records then its status should be given as "deletedSplit", while if it has simply been replaced by a new record then "deletedReplaced" is the appropriate status value. If a record is deleted because it has been merged with another record, its status should be given as "deletedMerged". A "derived" status value is available to indicate that the record was derived from another descriptive system.
Values:
cancelled, deleted, deletedMerged, deletedReplaced, deletedSplit, derived, new, revised
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" maintenanceStatus="new" publicationStatus="published" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@notAfter
 Not After  [toc]
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
Example:
<dateRange>
<fromDate notBefore="1971" notAfter="1975">around 1973</fromDate>

<toDate standardDate="1992">1992</toDate>

</dateRange>





 
@notBefore
 Not Before  [toc]
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
Example:
<dateRange>
<fromDate notBefore="1971" notAfter="1975">around 1973</fromDate>

<toDate standardDate="1992">1992</toDate>

</dateRange>





 
@preferredForm
 Preferred Form  [toc]
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 EAC-CPF entity for display purposes in a given context. Use the value "true" if the name entry is preferred for any display purposed.
This optional attribute is only available in <nameEntry>.
Values:
false, true
Example:
<nameEntrySet languageOfElement="fre">
<nameEntry conventionDeclarationReference="cd1" preferredForm="true">
<part>Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd2">
<part>Région Sud Provence-Alpes-Côte d'Azur</part>

</nameEntry>

<nameEntry conventionDeclarationReference="cd3">
<part>Provence-Alpes-Côte-d'Azur</part>

</nameEntry>

</nameEntrySet>





 
@publicationStatus
 Publication Status  [toc]
Summary:
The current publication status of the EAC-CPF instance.
Description and Usage:
The publication status may occur on <control> to indicate the current publication status of the EAC-CPF instance, whether in process, approved or final. As an EAC-CPF instance is modified or other events happen to it (as recorded in the <maintenanceHistory> element), the publication status should also be updated.
A newly created EAC-CPF instance will usually start with a publication status of "inProcess". This partial and preliminary status will be applicable as long as the author or the creating agency is working on the document. Depending on the context, the document might first reach a pre-publication level, awaiting approval e.g. by a higher level manager or an authorizing agency. Once such approval has been given, the status "approved" could be assigned for internal purposes while the EAC-CPF instance is not publicly available yet. When the EAC-CPF instance has been published on the institution’s own website or via the authorizing agency, the status "published" can be assigned.
Values:
approved, inProcess, published
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" maintenanceStatus="new" publicationStatus="published" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@repositoryEncoding
 Repository Encoding  [toc]
Summary:
The authoritative source or rules for values supplied in <agencyCode>.
Description and Usage:
The authoritative source or rules for values supplied in <agencyCode>. If the value "otherRepositoryEncoding" is selected an alternate code list should be specified in <conventionDeclaration>. Optionally available only in <control>.
Values:
iso15511, otherRepositoryEncoding
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@scriptCode
 Script Code  [toc]
Summary:
The code for the writing system, or script, used in the EAC-CPF instance or in which the CPF entity being described was creative or productive.
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:
NMTOKEN
Example:
<languagesUsed>
<languageUsed>
<language languageCode="eng">English</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

<languageUsed>
<language languageCode="spa">Spanish</language>

<writingSystem scriptCode="Latn">Latin</writingSystem>

</languageUsed>

<descriptiveNote>
<p>Published works in English and Spanish.</p>

</descriptiveNote>

</languagesUsed>





 
@scriptEncoding
 Script Encoding  [toc]
Summary:
The authoritative source or rules for values supplied in scriptOfElement and scriptCode.
Description and Usage:
The authoritative source or rules for values supplied in scriptOfElement and scriptCode. If the value "otherScriptEncoding" is selected, an alternate code list should be specified in <conventionDeclaration>. Optionally available only in <control>.
Values:
iso15924, otherScriptEncoding
Example:
<control countryEncoding="iso3166-1" dateEncoding="iso8601" languageEncoding="iso639-2b" repositoryEncoding="iso15511" scriptEncoding="iso15924"> [...] </control>





 
@scriptOfElement
 Script of Element  [toc]
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 EAC-CPF instance to specify which elements are written in which script. Optionally available on all non-empty elements.
Data Type:
NMTOKEN
Example:
<nameEntry status="alternative">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" localTypeDeclarationReference="GNDO" scriptOfElement="Hans">阿伦特, 汉娜</part>

</nameEntry>





 
@sourceReference
 Source Reference  [toc]
Summary:
Use sourceReference to provide a direct link to a <source> element within <sources> in <control> from an element within the EAC-CPF instance that uses the source.
Description and Usage:
The attribute can be used to reference any detailed information about the described entity with a source.
The attribute is optionally available in all elements in the identity area (except <entityType>), in the description area, and in the relations.
Data Type:
IDREFS
Example:
<relation sourceReference="source1" maintenanceEventReference="me2">
<targetEntity targetType="corporateBody" valueURI="https://snaccooperative.org/ark:/99166/w63z1x39" vocabularySourceURI="https://snaccooperative.org">
<part>Princeton University</part>

</targetEntity>

<relationType valueURI="https://www.wikidata.org/wiki/Property:P69" vocabularySourceURI="https://www.wikidata.org/">educated at</relationType>

</relation>





 
@standardDate
 Standard Date  [toc]
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
Example:
<dateRange>
<fromDate standardDate="1609-07-04">4 juillet 1609</fromDate>

<toDate standardDate="1640-07-07">7 juillet 1640</toDate>

</dateRange>





 
@standardDateTime
 Standard Date and Time  [toc]
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>.
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.]
Example:
<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"></agent>

<eventDateTime standardDateTime="2021-11-27"></eventDateTime>

</maintenanceEvent>





 
@status
 Status  [toc]
Summary:
Attribute that provides 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 vary by element. Optionally available only in <agencyCode>, <fromDate>, <nameEntry>, <otherAgencyCode>, and <toDate>.
Values:
Values in <agencyCode>, <nameEntry>, <otherAgencyCode>: alternative, authorized
Values in <date>, <fromDate>: unknown
Values in <toDate>: unknown, ongoing
Examples:
<nameEntry languageOfElement="de" preferredForm="true" status="authorized" localType="native">
<part localType="surname">Arendt</part>

<part localType="firstname">Hannah</part>

</nameEntry>



<dateRange>
<fromDate standardDate="2016-09">September 2016</fromDate>

<toDate status="ongoing"></toDate>

</dateRange>



<date status="unknown"></date>





 
@style
 Style  [toc]
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> and <list>. In a limited number of contexts that accommodate discursive description, <span> with style may be used to identify an arbitrary string that is intended to be rendered in a specific style. style may be used within <list> to specify the style of a list. It is highly recommended that the value of style be expressed as a W3C CSS style to facilitate interoperability.
Data Type:
normalizedString
Example:
<biogHist>
<p>Robert Carlton Brown (1886-1959) was a writer, editor, publisher, and traveler. From 1908 to 1917, he wrote poetry and prose for numerous magazines and newspapers in New York City, publishing two pulp novels,
<span style="font-style:italic">What Happened to Mary</span>

and
<span style="font-style:italic">The Remarkable Adventures of Christopher Poe</span>

(1913), and one volume of poetry,
<span style="font-style:italic">My Marjonary</span>

(1916).</p>

<p>During 1918, he traveled extensively in Mexico and Central America, writing for the U.S. Committee of Public Information in Santiago de Chile. In 1919, he moved with his wife, Rose Brown, to Rio de Janeiro, where they founded
<span style="font-style:italic">Brazilian American</span>

, a weekly magazine that ran until 1929. With Brown's mother, Cora, the Browns also established magazines in Mexico City and London:
<span style="font-style:italic">Mexican American</span>

(1924-1929) and
<span style="font-style:italic">British American</span>

(1926-1929).</p>

</biogHist>





 
@target
 Target  [toc]
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 <eac>.
Data Type:
IDREFS
Example:
<occupations>
<occupation>
<term>Assistant examiner - level III</term>

<placeName target="#place1">Bern</placeName>

</occupation>

</occupations>

<places>
<place id="place1">
<placeName>Bern</placeName>

<placeRole>Place of work</placeRole>

</place>

</places>





 
@targetType
 Target Type  [toc]
Summary:
Identifies the type of entity that is relate to the CPF entity being described.
Description and Usage:
Required attribute within <targetEntity> which identifies the type of entity that is related to the CPF entity being described. Use the value "agent" only for migration from EAC-CPF 2010 to EAC 2.0.
Values:
agent, corporateBody, family, function, person, resource
Examples:
<targetEntity targetType="resource">
<part>Mémorial du colonel Gustafsson. - 1829</part>

</targetEntity>



<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/120636123" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Sophie</part>

<part>Baden, Großherzogin</part>

<part>1801-1865</part>

</targetEntity>





 
@unit
 Unit  [toc]
Summary:
Defines the format or unit that is 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
Example:
<citedRange unit="page">1</citedRange>





 
@value
 Value  [toc]
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
Example:
<entityType value="person"></entityType>





 
@valueURI
 Value URI  [toc]
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.
Data Type:
anyURI
Example:
<place>
<placeName valueURI="https://d-nb.info/gnd/4076982-3" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Salzburg</placeName>

<placeRole valueURI="https://d-nb.info/standards/elementset/gnd#characteristicPlace" vocabularySource="GNDO" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#">Charakteristischer Ort</placeRole>

</place>





 
@vocabularySource
 Vocabulary Source  [toc]
Summary:
An attribute for identifying a vocabulary that is the source of the element's value.
Description and Usage:
Use the optional attribute to provide a name or title of the authority or vocabulary source of the element’s content given in valueURI. Available in all elements that can contain any type of entity.
Data Type:
token
Example:
<occupation>
<term valueURI="https://d-nb.info/gnd/4053311-6" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Schriftstellerin</term>

</occupation>





 
@vocabularySourceURI
 Vocabulary Source URI  [toc]
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.
Data Type:
anyURI
Example:
<place>
<placeName valueURI="https://d-nb.info/gnd/4005728-8" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Berlin</placeName>

<placeRole valueURI="https://d-nb.info/standards/elementset/gnd#placeOfBusiness" vocabularySource="GNDO" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#">Sitz</placeRole>

</place>





 
  [toc]