Welcome to the EAC-CPF Homepage
Encoded Archival Context for Corporate Bodies, Persons, and Families - EAC-CPF - is an XML-Schema. It provides a grammar for encoding names of creators of archival materials and related information.
EAC-CPF is based on the International Standard Archival Authority Record for Corporate Bodies, Persons and Families, 2nd Edition, 2003. It is used closely in association with Encoded Archival Description (EAD), an XML-Schema for encoding archival finding aids, but not limited to it.
In 2011 EAC became an adopted standard of the Society of American Archivists (SAA). A Technical Subcommittee (TS-EAC-CPF) was established under the SAA's Standards Committee. In 2015 the Technical Subcommittees on EAD and EAC-CPF were merged to form the Technical Subcommittee on Encoded Archival Standards (TS-EAS), responsible for the ongoing maintenance of EAD and EAC-CPF.
Since August 2016 a subgroup within TS-EAS has been discussing questions and issues regarding EAC-CPF which came up in different projects implementing the standard and during the revision process of EAD 2002 to EAD3. Feedback came from partners and institutions all over the world. In summer 2017 a decision about an update or a full revision of the standard is planned.
This website informs about the EAC-CPF Schema, its background, context, and use. Questions or remarks concerning this standard can be send to the EAD-Mailinglist.
Attention! At the annual meeting in Portland, Oregon in 2017, the Technical Subcommittee on Encoded Archival Description (TS-EAS) of the Society of American Archivists agreed to undertake a revision of the standard EAC-CPF. The subcommittee is calling for proposed changes to the current version of EAC-CPF. To ensure the greatest possible input from users of EAC-CPF and other relevant standards, the deadline for change proposals is 11 December 2017. At that time, all proposals will be made publicly available through the EAC-CPF GitHub portal (https://github.com/SAA-SDT/eac-cpf-schema/issues).
Please send feedback and comments by e-mail to Silke Jagodzinski (email@example.com). To ensure that the revision process is as open as possible, all comments must be attributable to named individuals and affiliated organisations where appropriate. Anonymous responses will not be considered. All change proposals will be made publicly available, with attribution, through the GitHub Portal as established during the EAD revision process. E-mail addresses are asked for so that we may contact respondents for clarification, but will not be shared.
Attention! Take part in survey about EAD3 Implementation