From ed99fd9f98d66958bdb739bf6fda79acc1ef23df Mon Sep 17 00:00:00 2001 From: SJagodzinski Date: Wed, 16 Oct 2019 08:55:34 +0200 Subject: [PATCH] Fixed typo in rights declaration Corrected element name 'abbreviation' for '', cf [EAC-CPF issue #62](https://github.com/SAA-SDT/eac-cpf-schema)/issues/62 --- tei/EAC-CPF-TL-eng.xml | 3860 +++++++++++++++++++++++----------------- 1 file changed, 2243 insertions(+), 1617 deletions(-) diff --git a/tei/EAC-CPF-TL-eng.xml b/tei/EAC-CPF-TL-eng.xml index f4bd26b8..ec8adac3 100644 --- a/tei/EAC-CPF-TL-eng.xml +++ b/tei/EAC-CPF-TL-eng.xml @@ -1,22 +1,27 @@ - + - Encoded Archival Context—Corporate Bodies, Persons, and Families (EAC-CPF) + Encoded Archival Context—Corporate Bodies, Persons, and Families + (EAC-CPF) Tag Library Version 2010 Revised Prepared and maintained by the - Technical Subcommittee for Encoded Archival Context of the Society of American Archivists and the Staatsbibliothek zu Berlin + Technical Subcommittee for Encoded Archival Context of the Society of American + Archivists and the Staatsbibliothek zu Berlin

2018 Edition

 - Society of American Archivists in collaboration with Staatsbibliothek zu Berlin. + Society of American Archivists in collaboration with + Staatsbibliothek zu Berlin.
Society of American Archivists 17 North State Street, suite 1425 @@ -31,10 +36,11 @@ ISBN Number This work is licensed under a Creative Commons Attribution 4.0 International - License (CC BY 4.0). See http://creativecommons.org/licenses/by/4.0/. Some rights reserved. No - part of this publication may be reproduced, stored in a retrieval system or - transmitted in any form or by any means, electronic, mechanical or photocopying, - recording, or otherwise without attribution. + License (CC BY 4.0). See http://creativecommons.org/licenses/by/4.0/. Some rights reserved. No part of + this publication may be reproduced, stored in a retrieval system or transmitted in any + form or by any means, electronic, mechanical or photocopying, recording, or otherwise + without attribution. @@ -46,12 +52,14 @@ - Encoded Archival Context—Corporate Bodies, Persons, and Families (EAC-CPF) Tag Library + Encoded Archival Context—Corporate Bodies, Persons, and Families + (EAC-CPF) Tag Library Version 2010 Revised Edition 2018 Prepared and maintained by the - Technical Subcommittee for Encoded Archival Context of the Society of American Archivists + Technical Subcommittee for Encoded Archival Context of the Society of American + Archivists and the Staatsbibliothek zu Berlin Document date @@ -60,92 +68,256 @@
Dedication -

The Encoded Archival Context Working Group dedicates the 2010 EAC-CPF Schema and Tag Library to the memory of Per-Gunnar Ottosson. P-G, as he was known to his many friends around the world, played a key role in the development - of many international archival standards. He played a critical role in the early development of EAC, but illness and his death in 2008 prevented him from seeing the EAC-CPF work completed. He will be remembered for his - keen intelligence, collaborative skills, and wonderful wit. Above all, he will be fondly remembered as a friend.

+

The Encoded Archival Context Working Group dedicates the 2010 EAC-CPF Schema and Tag + Library to the memory of Per-Gunnar Ottosson. P-G, as he was known to his many friends + around the world, played a key role in the development of many international archival + standards. He played a critical role in the early development of EAC, but illness and + his death in 2008 prevented him from seeing the EAC-CPF work completed. He will be + remembered for his keen intelligence, collaborative skills, and wonderful wit. Above + all, he will be fondly remembered as a friend.

Release and Revision Notes -

This is the final release of the Tag Library for EAC-CPF 2010. The current release includes changes and updates in the schema undertaken by the Technical Subcommittee on Encoded Archival Standards reflecting comments received by the international community of professionals.

-

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 Technical Subcommittee for Encoded Archival Standards (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 EAC-CPF subgroup lead, Silke Jagodzinski (s.jagodzinski[at]bundesarchiv.de). 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.

+

This is the final release of the Tag Library for EAC-CPF 2010. The current release + includes changes and updates in the schema undertaken by the Technical Subcommittee on + Encoded Archival Standards reflecting comments received by the international community + of professionals.

+

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 Technical Subcommittee + for Encoded Archival Standards (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 EAC-CPF subgroup lead, Silke Jagodzinski (s.jagodzinski[at]bundesarchiv.de). + 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.

Background -

EAC began with a 1998 effort by Richard Szary, Wendy Duff, and Daniel Pitti to envision a standard for encoding and exchanging authoritative information about the context of archival materials. This standard would provide a communication standard for the exchange of authority records based on the International Standard for Archival Authority Records—Corporate Bodies, Persons, Families (ISAAR(CPF)) and would parallel the standard for encoding archival record finding aids that was found in Encoded Archival Description (EAD). As EAD enabled the practical expression of the General International Standard Archival Description (ISAD(G)), the new standard would enable the expression of ISAAR(CPF). A parallel standard would preserve and strengthen the essential duality that characterizes archival description when it is presented in archival finding aids.

-

A separate standard would pave the way to eliminating some practical problems found in the use of EAD, which had been developed as a comprehensive solution for encoding standalone finding aids—the dominant presentation model—which held all forms of descriptive data about archival records. Since materials by or about a single entity might be found in many fonds or many repositories, there is much redundant effort in recording information about the same entity. In addition, these duplicative efforts can result in great inconsistency, which bedevils both users, in finding and interpreting materials, and archivists, in creating accurate and complete references to such entities.

-

Yale University hosted an international meeting in 1998. The meeting was organized by Richard Szary and funded by the Digital Library Federation. The goals of the meeting were to plan the funding and development of an encoding standard based on ISAAR(CPF).

-

In 2001, with financial assistance from the Gladys Krieble Delmas Foundation, a second international working group met in Toronto. This meeting produced the Toronto Tenets, the principles that gave shape to the proposed standard. The group also established goals for the standard, mapped out the broader parameters of the Document Type Definition (DTD), and established a working group to create a fully formed syntax. The DTD achieved its Beta distribution in 2004, beginning a long testing phase as it was applied in several European and U.S. projects. Informed by the results that emerged from this testbed, the Society of American Archivists' Encoded Archival Context Working Group was formed in 2007 to carry this work forward to the creation of a standard version, and expression in a schema and Tag Library. With the support of the Gladys Krieble Delmas Foundation, the IBC (Instituto per I beni artistici culturali e naturali) of the Regione Emilia-Romagna, the Archivio di Stato di Bologna, OCLC Research, and the National Library of Australia, the EAC Working Group met for three days in Bologna, Italy in May 2008 to lay the foundation of the existing EAC-CPF standard. On-going work via electronic mail and conference calls continued the work started in Bologna. A review period of the final draft was offered between August and November 2009, and the completed schema was released in March 2010. The Working Group is indebted to archivists, librarians and other information professionals throughout the international community for their input, review, and testing of the schema during its development phase. In 2011, the Working Group was disbanded and SAA Council approved a charge to form the Technical Subcommittee for Encoded Archival Context (TS-EAC). 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.

-

Archival description includes information about the content, intellectual and physical attributes of the archival material, as well as information about the context of their creation and use. The contextual information of the creation and use of material is often complex and multi-layered and may involve individuals, families, organizations, societies, functions, activities, business processes, geographic places, events, and other entities. Primary among these entities are the corporate bodies, persons and families (CPF entities) responsible for the creation or use of material, usually organizations or persons. With information about these CPF entities, users can understand and interpret the records more fully since they will know the context within which the CPF entities operated and created and/or used the material. Information about these CPF entities can be used either as a component within descriptive approaches that fully integrate contextual information into descriptive products, as archives have traditionally done, or as an independent system that is linked to other descriptive systems and products that focus on content.

-

Encoded Archival Context – Corporate Bodies, Persons, and Families (EAC-CPF) primarily addresses the description of individuals, families and corporate bodies that create, preserve, use, and are responsible for and/or associated with records in a variety of ways. Over time, other types of contextual entities may evolve under the larger EAC umbrella, but currently its primary purpose is to standardize the encoding of descriptions about CPF entities to enable the sharing, discovery and display of this information in an electronic environment. It supports the linking of information about one CPF entities to other CPF entities to show/discover the relationships amongst record-creating entities and the linking to descriptions of records and other contextual Entities.

-

EAC-CPF is a communication structure for archival contextual information for individuals, corporate bodies and families and thereby supports the exchange of ISAAR(CPF) compliant authority records. ISAAR(CPF) "determines the types of information that could be included in an archival authority record and provides guidance on how such records may be deployed in an archival descriptive system." ISAAR(CPF) also notes that "[s]uccessful automated exchange of archival authority information over computer networks is dependent upon the adoption of a suitable communication format by the repositories involved in the exchange. Encoded Archival Context (EAC) is one such communication format which supports the exchange of ISAAR(CPF) compliant archival authority data over the World Wide Web" (ISAAR(CPF), 2004, p. 12). EAC-CPF provides a mechanism for enabling the full expression of ISAAR(CPF), however it may also contain some additional elements or technical content not contained within ISAAR(CPF).

-

Based upon the Toronto Tenets, established in 2001, the following have informed the development of the schema: Definitions and UsesArchival context information consists of information describing the circumstances under which archival materials have been created, maintained and used. This context includes, but is not limited to, the identification and characteristics of corporate bodies, persons, and families (CPF entities) who have been the creators, users, or subjects of records, as well as the relationships amongst them.Context information about CPF entities is not data that describes other information resources, but rather data that describes entities that are part of the environment in which those information resources (e.g., records) have existed.The recording of context information about CPF entities in archival information systems directly supports a more complete description and understanding of records, as well as a provenance-based approach to retrieval of these records across time and domains.Context information about CPF entities can also have value as an independent information resource, separate from its use in supporting the description, retrieval, and interpretation of records.This model is also intended to support the exchange and sharing of context information about CPF entities, especially in those instances where repositories have holdings or interests that have context information in common. - Structure and ContentEach instance of context information about CPF entities describes a single corporate body, person or family.The model provides a framework within which the full range and depth of context information about agents can be recorded but suggests a minimum set of elements for describing an entity. The model defers recommendations for the appropriate use of other elements toguidelines developed for specific implementations.The model defines a set of elements used to describe CPF entities and the structure of relationships between those elements. This structure supports the discovery, navigation and presentation of context information about CPF entitiesand the linking of that information to descriptions of resources or to other contextual entities, such as those encoded according to EAD, MARC, and similar standards.The model supports the linking of descriptions of contextual entities to digital or other surrogate representations of those entities. - Technical IssuesThe model is expressed as an XML language to encourage platform independence and portability of information. The model may also be implemented using other approaches. -

+

EAC began with a 1998 effort by Richard Szary, Wendy Duff, and Daniel Pitti to envision + a standard for encoding and exchanging authoritative information about the context of + archival materials. This standard would provide a communication standard for the + exchange of authority records based on the International Standard for Archival Authority + Records—Corporate Bodies, Persons, Families (ISAAR(CPF)) and would parallel the standard + for encoding archival record finding aids that was found in Encoded Archival Description + (EAD). As EAD enabled the practical expression of the General International Standard + Archival Description (ISAD(G)), the new standard would enable the expression of + ISAAR(CPF). A parallel standard would preserve and strengthen the essential duality that + characterizes archival description when it is presented in archival finding aids.

+

A separate standard would pave the way to eliminating some practical problems found in + the use of EAD, which had been developed as a comprehensive solution for encoding + standalone finding aids—the dominant presentation model—which held all forms of + descriptive data about archival records. Since materials by or about a single entity + might be found in many fonds or many repositories, there is much redundant effort in + recording information about the same entity. In addition, these duplicative efforts can + result in great inconsistency, which bedevils both users, in finding and interpreting + materials, and archivists, in creating accurate and complete references to such + entities.

+

Yale University hosted an international meeting in 1998. The meeting was organized by + Richard Szary and funded by the Digital Library Federation. The goals of the meeting + were to plan the funding and development of an encoding standard based on + ISAAR(CPF).

+

In 2001, with financial assistance from the Gladys Krieble Delmas Foundation, a second + international working group met in Toronto. This meeting produced the Toronto Tenets, + the principles that gave shape to the proposed standard. The group also established + goals for the standard, mapped out the broader parameters of the Document Type + Definition (DTD), and established a working group to create a fully formed syntax. The + DTD achieved its Beta distribution in 2004, beginning a long testing phase as it was + applied in several European and U.S. projects. Informed by the results that emerged from + this testbed, the Society of American Archivists' Encoded Archival Context Working Group + was formed in 2007 to carry this work forward to the creation of a standard version, and + expression in a schema and Tag Library. With the support of the Gladys Krieble Delmas + Foundation, the IBC (Instituto per I beni artistici culturali e naturali) of the Regione + Emilia-Romagna, the Archivio di Stato di Bologna, OCLC Research, and the National + Library of Australia, the EAC Working Group met for three days in Bologna, Italy in May + 2008 to lay the foundation of the existing EAC-CPF standard. On-going work via + electronic mail and conference calls continued the work started in Bologna. A review + period of the final draft was offered between August and November 2009, and the + completed schema was released in March 2010. The Working Group is indebted to + archivists, librarians and other information professionals throughout the international + community for their input, review, and testing of the schema during its development + phase. In 2011, the Working Group was disbanded and SAA Council approved a charge to + form the Technical Subcommittee for Encoded Archival Context (TS-EAC). 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.

+

Archival description includes information about the content, intellectual and physical + attributes of the archival material, as well as information about the context of their + creation and use. The contextual information of the creation and use of material is + often complex and multi-layered and may involve individuals, families, organizations, + societies, functions, activities, business processes, geographic places, events, and + other entities. Primary among these entities are the corporate bodies, persons and + families (CPF entities) responsible for the creation or use of material, usually + organizations or persons. With information about these CPF entities, users can + understand and interpret the records more fully since they will know the context within + which the CPF entities operated and created and/or used the material. Information about + these CPF entities can be used either as a component within descriptive approaches that + fully integrate contextual information into descriptive products, as archives have + traditionally done, or as an independent system that is linked to other descriptive + systems and products that focus on content.

+

Encoded Archival Context – Corporate Bodies, Persons, and Families (EAC-CPF) primarily + addresses the description of individuals, families and corporate bodies that create, + preserve, use, and are responsible for and/or associated with records in a variety of + ways. Over time, other types of contextual entities may evolve under the larger EAC + umbrella, but currently its primary purpose is to standardize the encoding of + descriptions about CPF entities to enable the sharing, discovery and display of this + information in an electronic environment. It supports the linking of information about + one CPF entities to other CPF entities to show/discover the relationships amongst + record-creating entities and the linking to descriptions of records and other contextual + Entities.

+

EAC-CPF is a communication structure for archival contextual information for + individuals, corporate bodies and families and thereby supports the exchange of + ISAAR(CPF) compliant authority records. ISAAR(CPF) "determines the types of information + that could be included in an archival authority record and provides guidance on how such + records may be deployed in an archival descriptive system." ISAAR(CPF) also notes that + "[s]uccessful automated exchange of archival authority information over computer + networks is dependent upon the adoption of a suitable communication format by the + repositories involved in the exchange. Encoded Archival Context (EAC) is one such + communication format which supports the exchange of ISAAR(CPF) compliant archival + authority data over the World Wide Web" (ISAAR(CPF), 2004, p. 12). EAC-CPF provides a + mechanism for enabling the full expression of ISAAR(CPF), however it may also contain + some additional elements or technical content not contained within ISAAR(CPF).

+

Based upon the Toronto Tenets, established in 2001, the following have informed the + development of the schema: Definitions and UsesArchival context information consists of information describing the circumstances + under which archival materials have been created, maintained and used. This context + includes, but is not limited to, the identification and characteristics of corporate + bodies, persons, and families (CPF entities) who have been the creators, users, or + subjects of records, as well as the relationships amongst them.Context information about CPF entities is not data that describes other information + resources, but rather data that describes entities that are part of the environment in + which those information resources (e.g., records) have existed.The + recording of context information about CPF entities in archival information systems + directly supports a more complete description and understanding of records, as well as a + provenance-based approach to retrieval of these records across time and + domains.Context information about CPF entities can also have value as + an independent information resource, separate from its use in supporting the + description, retrieval, and interpretation of records.This model is + also intended to support the exchange and sharing of context information about CPF + entities, especially in those instances where repositories have holdings or interests + that have context information in common. Structure and ContentEach instance of context information + about CPF entities describes a single corporate body, person or family.The model provides a framework within which the full range and depth of context + information about agents can be recorded but suggests a minimum set of elements for + describing an entity. The model defers recommendations for the appropriate use of other + elements toguidelines developed for specific implementations.The + model defines a set of elements used to describe CPF entities and the structure of + relationships between those elements. This structure supports the discovery, navigation + and presentation of context information about CPF entitiesand the linking of that + information to descriptions of resources or to other contextual entities, such as those + encoded according to EAD, MARC, and similar standards.The model + supports the linking of descriptions of contextual entities to digital or other + surrogate representations of those entities. Technical IssuesThe model is expressed as an XML language to + encourage platform independence and portability of information. The model may also be + implemented using other approaches.

EAC-CPF Concepts -

CPF Entities are complex. For example, one CPF entity can represent multiple identities, or a single identity can be associated with several different CPF entities. This fact necessitates the structure of a standard to account for the various ways in which CPF entities can be expressed. In order to accommodate the variety of CPF entities, EAC-CPF has adopted the following definitions:

+

CPF Entities are complex. For example, one CPF entity can represent multiple + identities, or a single identity can be associated with several different CPF entities. + This fact necessitates the structure of a standard to account for the various ways in + which CPF entities can be expressed. In order to accommodate the variety of CPF + entities, EAC-CPF has adopted the following definitions:

- SINGLE IDENTITY: one person (or corporate body or family) with a single identity represented in one EAC-CPF instance. This is the most common identity type. - MULTIPLE IDENTITY-MANY IN ONE: two or more identities (including official identities) with each represented by distinct descriptions within one EAC-CPF instance. Can be programmatically converted into Multiple Identity-One in Many. - MULTIPLE IDENTITY-ONE IN MANY: two or more identities (including official identities) each represented in two or more interrelated EAC-CPF instances. Can be programmatically converted into Multiple Identity-Many in One. - COLLABORATIVE IDENTITY: a single identity shared by two or more persons (e.g. a shared pseudonym used in creation of a collaborative work). Use Multiple Identity-One in Many. - ALTERNATIVE SET: derived EAC-CPF instance that is based on and incorporates two or more alternative EAC-CPF instances for the same entity. To be used by a consortia or a utility providing union access to authority records maintained in two or more systems by two or more agencies. Alternative EAC-CPF instances may be in different languages or in the same language. + SINGLE IDENTITY: one person (or corporate body or family) with a single identity + represented in one EAC-CPF instance. This is the most common identity type. + MULTIPLE IDENTITY-MANY IN ONE: two or more identities (including official + identities) with each represented by distinct descriptions within one EAC-CPF + instance. Can be programmatically converted into Multiple Identity-One in Many. + MULTIPLE IDENTITY-ONE IN MANY: two or more identities (including official + identities) each represented in two or more interrelated EAC-CPF instances. Can be + programmatically converted into Multiple Identity-Many in One. + COLLABORATIVE IDENTITY: a single identity shared by two or more persons (e.g. a + shared pseudonym used in creation of a collaborative work). Use Multiple Identity-One + in Many. + ALTERNATIVE SET: derived EAC-CPF instance that is based on and incorporates two or + more alternative EAC-CPF instances for the same entity. To be used by a consortia or a + utility providing union access to authority records maintained in two or more systems + by two or more agencies. Alternative EAC-CPF instances may be in different languages + or in the same language. -

EAC-CPF has been created to accommodate this variety of identities, and includes a number of ways to express complexities based on individual repository or aggregator preferences. These options reflect a design principle that underscores increased opportunity for repositories or aggregators to customize the standard for specific needs while at the same time ensuring future aggregation. These flexibilities also reflect an acknowledgement that some fundamental philosophical differences with regard to the processing of information related to separate identities of the same CPF entity exist in the international community. EAC-CPF maintains a neutral stance on those philosophical differences and instead has accommodated the various options without precluding aggregation in the future.

-

For purposes of this tag library, agents refer to repositories or services creating or maintaining EAC-CPF records, while entities refer to those for which the records are about.

+

EAC-CPF has been created to accommodate this variety of identities, and includes a + number of ways to express complexities based on individual repository or aggregator + preferences. These options reflect a design principle that underscores increased + opportunity for repositories or aggregators to customize the standard for specific needs + while at the same time ensuring future aggregation. These flexibilities also reflect an + acknowledgement that some fundamental philosophical differences with regard to the + processing of information related to separate identities of the same CPF entity exist in + the international community. EAC-CPF maintains a neutral stance on those philosophical + differences and instead has accommodated the various options without precluding + aggregation in the future.

+

For purposes of this tag library, agents refer to repositories or services creating or + maintaining EAC-CPF records, while entities refer to those for which the records are + about.

Glossary - Agent: Within the framework of the EAC-CPF schema and Tag Library, agent refers to a repository where records are managed or to individuals performing maintenance activities in the repositories. For example, agent is an element of the EAC-CPF schema within maintenanceEvent. - CPF entity: A shortcut within the framework of this Tag Library to generically designate the type of entities that are the object of a description in an EAC-CPF instance. In other words, it stands for “the corporate body, person or family being described in an EAC-CPF instance.” - Grouping: In the EAC-CPF Tag Library, the term “grouping” is used as a specialized type of wrapper for those pluralized description elements, e.g., legalStatuses, functions, etc. - Identity: Though most commonly individuals are known by their real name (the name they were given at birth), it happens that, in the course of their life, they might acquire names other than their real name. In cases where an individual has separate lines of activity, each under a different name, it might be of interest to distinguish between these names and consider them as distinct identities. From the information management standpoint, according to the policy of the repository, each of these distinct identities, though belonging to the same physical person, might either be described separately in distinct EAC-CPF instances (see EAC-CPF concepts, case of MULTIPLE IDENTITY – ONE IN MANY) or might co-exist in one EAC-CPF instance (see EAC-CPF concepts, case MULTIPLE IDENTITY – MANY IN ONE). Another case is that of a collaborative identity where several individuals chose to make themselves publicly known under a personal name (see EAC-CPF concepts, case COLLABORATIVE IDENTITY), justifying their being described in one single EAC-CPF instance. - Resource: Materials, other than CPF entities and functions’ descriptions, to which CPF instances are related. - Wrapper: In the EAC-CPF Tag Library, the term “wrapper” is used as a descriptive function for elements that can contain other elements only, e.g., legalStatus, function, and cpfDescription, etc. + Agent: Within the framework of the EAC-CPF schema and Tag Library, agent refers to + a repository where records are managed or to individuals performing maintenance + activities in the repositories. For example, agent is an element of the + EAC-CPF schema within maintenanceEvent. + CPF entity: A shortcut within the framework of this Tag Library to generically + designate the type of entities that are the object of a description in an EAC-CPF + instance. In other words, it stands for “the corporate body, person or family being + described in an EAC-CPF instance.” + Grouping: In the EAC-CPF Tag Library, the term “grouping” is used as a specialized + type of wrapper for those pluralized description elements, e.g., + legalStatuses, functions, etc. + Identity: Though most commonly individuals are known by their real name (the name + they were given at birth), it happens that, in the course of their life, they might + acquire names other than their real name. In cases where an individual has separate + lines of activity, each under a different name, it might be of interest to distinguish + between these names and consider them as distinct identities. From the information + management standpoint, according to the policy of the repository, each of these + distinct identities, though belonging to the same physical person, might either be + described separately in distinct EAC-CPF instances (see EAC-CPF concepts, case of + MULTIPLE IDENTITY – ONE IN MANY) or might co-exist in one EAC-CPF instance (see + EAC-CPF concepts, case MULTIPLE IDENTITY – MANY IN ONE). Another case is that of a + collaborative identity where several individuals chose to make themselves publicly + known under a personal name (see EAC-CPF concepts, case COLLABORATIVE IDENTITY), + justifying their being described in one single EAC-CPF instance. + Resource: Materials, other than CPF entities and functions’ descriptions, to which + CPF instances are related. + Wrapper: In the EAC-CPF Tag Library, the term “wrapper” is used as a descriptive + function for elements that can contain other elements only, e.g., + legalStatus, function, and cpfDescription, + etc. -

The section “Availability” informs about the conditions of the occurrence of an element within its parent element.

+

The section “Availability” informs about the conditions of the occurrence of an element + within its parent element.

Overview of EAC-CPF Structure and Semantics
Introduction -

Each EAC-CPF instance contains two mandatory elements, the control element and - either the element cpfDescription or multipleIdentities. The - control element contains data used in management of the EAC-CPF instance by providing administrative metadata for the description it contains. cpfDescription contains information on the - name structures, descriptive elements, and relationships. multipleIdentities is - used when there is more than one cpfDescription. These two wrapper elements contain - specific elements to support the functional intentions of the parent or containing - element.

+

Each EAC-CPF instance contains two mandatory elements, the control element + and either the element cpfDescription or multipleIdentities. The + control element contains data used in management of the EAC-CPF instance by + providing administrative metadata for the description it contains. + cpfDescription contains information on the name structures, descriptive + elements, and relationships. multipleIdentities is used when there is more + than one cpfDescription. These two wrapper elements contain specific elements + to support the functional intentions of the parent or containing element.

- - [control elements] - - - [description elements] - + [control elements] + [description elements]

OR

- - [control elements] - + [control elements] - - [description elements] - - - [description elements] - - - [description elements] - + [description elements] + [description elements] + [description elements] @@ -154,49 +326,68 @@ control -

The control element contains the following subelements; they are presented in the prescribed order in the EAC-CPF schema:

+

The control element contains the following subelements; they are presented + in the prescribed order in the EAC-CPF schema:

- recordId - Required. Contains the one or more unique identifiers for the - EAC-CPF instance. - otherRecordId - Optional. An element that allows the recording of additional identifiers that may be associated with the EAC-CPF instance. - - maintenanceStatus - Required. Contains the current drafting status of the EAC-CPF instance. Values include: new, revised, deleted, cancelled, deletedSplit, or deletedReplaced. - - publicationStatus - Optional. Contains information about the editorial status of 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. - - languageDeclaration - Optional. Contains coded and natural language information about the language or languages of the EAC-CPF instance. - - conventionDeclaration - Optional. Contains information on the rules used to construct the EAC-CPF instance, in particular the names formed in identity and the controlled vocabularies and thesauri used in the EAC-CPF instance. - - localTypeDeclaration - Optional. An element used to declare local conventions used in the @localType attribute. - - localControl - Optional. An element in which to record any administrative metadata necessary due to local practice that are not represented by the other elements in control. - - maintenanceHistory - Required. Contains information about the date, type and events within the life cycle of an EAC-CPF instance. Contains one or more maintenanceEvent elements that document creating, importing, updating, and deletion of the description. Each maintenance event contains an agent, the type of agent (human or machine), the type of event, a description of the event, and the date of the event. - - sources - Optional. Contains information about the sources consulted in creating the description of the CPF entity or entities in the EAC-CPF instance. Contains one or more source element. - + recordId - Required. Contains the one or more unique identifiers for + the EAC-CPF instance. + otherRecordId - Optional. An element that allows the recording of + additional identifiers that may be associated with the EAC-CPF instance. + maintenanceStatus - Required. Contains the current drafting status of + the EAC-CPF instance. Values include: new, revised, deleted, cancelled, + deletedSplit, or deletedReplaced. + publicationStatus - Optional. Contains information about the editorial + status of 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. + languageDeclaration - Optional. Contains coded and natural language + information about the language or languages of the EAC-CPF instance. + conventionDeclaration - Optional. Contains information on the rules + used to construct the EAC-CPF instance, in particular the names formed in + identity and the controlled vocabularies and thesauri used in the EAC-CPF + instance. + localTypeDeclaration - Optional. An element used to declare local + conventions used in the @localType attribute. + localControl - Optional. An element in which to record any + administrative metadata necessary due to local practice that are not represented by + the other elements in control. + maintenanceHistory - Required. Contains information about the date, + type and events within the life cycle of an EAC-CPF instance. Contains one or more + maintenanceEvent elements that document creating, importing, updating, and + deletion of the description. Each maintenance event contains an agent, the type of + agent (human or machine), the type of event, a description of the event, and the + date of the event. + sources - Optional. Contains information about the sources consulted in + creating the description of the CPF entity or entities in the EAC-CPF instance. + Contains one or more source element.
cpfDescription -

The cpfDescription - Corporate body, person or family description, comprises the - description of the entity. Similar to the control element, - cpfDescription has four complex subelements used to describe different features - of the entity:

+

The cpfDescription - Corporate body, person or family description, comprises + the description of the entity. Similar to the control element, + cpfDescription has four complex subelements used to describe different + features of the entity:

- identity - Required. Complex structure containing the name or names used by the CPF entity over the course of the entity’s existence. Contains a repeatable nameEntry element for different names, and a repeatable nameEntryParallel element for more than one nameEntry expressed in different languages. - - description - Optional. Contains formal description elements parallel to those in ISAAR (CPF) for the description of the CPF entity. An additional localDescription allows for local implementation of additional descriptive information not included in the other description elements. - - relations - Optional. Contains one or more references to or descriptions of related corporate bodies, persons or families cpfRelation, functions functionRelation, or resources resourceRelation. - - alternativeSet - Optional. Contains two or more descriptions for the same CPF entity derived from two or more systems, expressed within a single EAC-CPF instance. The alternativeSet consists of two or more setComponent elements for the descriptions. - + identity - Required. Complex structure containing the name or names + used by the CPF entity over the course of the entity’s existence. Contains a + repeatable nameEntry element for different names, and a repeatable + nameEntryParallel element for more than one nameEntry expressed in + different languages. + description - Optional. Contains formal description elements parallel + to those in ISAAR (CPF) for the description of the CPF entity. An additional + localDescription allows for local implementation of additional descriptive + information not included in the other description elements. + relations - Optional. Contains one or more references to or + descriptions of related corporate bodies, persons or families cpfRelation, + functions functionRelation, or resources resourceRelation. + alternativeSet - Optional. Contains two or more descriptions for the + same CPF entity derived from two or more systems, expressed within a single EAC-CPF + instance. The alternativeSet consists of two or more setComponent + elements for the descriptions.
@@ -204,147 +395,268 @@ identity

The most complex element in the EAC-CPF schema is the identity element. In - addition to needing to accommodate one or more names used for or by the CPF entity, - identity must accommodate two or more parallel names in different languages and/or - scripts. In countries where there is more than one official language, such as Canada, names of - corporate bodies have more than one language. The identity contains a required - entityType and one or more nameEntry and/or - nameEntryParallel elements. It also includes an optional entityId and - descriptiveNote. The nameEntry element is constructed of one or more - part elements and contains the attributes scriptCode, - xml:lang, transliteration, and localType to provide - precision about the language and script of the names if desired. It includes an optional - useDates element to identify dates of use of a name. nameEntryParallel, - which is intended for use when the same name is expressed in different languages, contains one - or more nameEntry elements and an optional useDates element. For - example, within the context of the Archive of Ontario, parallel French and English headings - can be designated through two parallel - nameEntry elements, with the two different headings being distinguished by the - values in the xml:lang.

-

Within identity, names represented through nameEntry or nameEntryParallel may be selected as authorized or variant names. The authorizedForm and alternativeForm elements are - available within nameEntry and nameEntryParallel elements to identify the status of the name according to a particular set of rules. The content of the element is the identification of those rules. - Additionally, within nameEntryParallel, a single nameEntry may be preferred over others. A preferredForm element is available in that instance to identify the preferred form of the name - according to a particular set of rules. The content of the element identifies those rules.

+ addition to needing to accommodate one or more names used for or by the CPF entity, + identity must accommodate two or more parallel names in different languages + and/or scripts. In countries where there is more than one official language, such as + Canada, names of corporate bodies have more than one language. The identity + contains a required entityType and one or more nameEntry and/or + nameEntryParallel elements. It also includes an optional entityId + and descriptiveNote. The nameEntry element is constructed of one or + more part elements and contains the attributes scriptCode, + xml:lang, transliteration, and localType to provide + precision about the language and script of the names if desired. It includes an + optional useDates element to identify dates of use of a name. + nameEntryParallel, which is intended for use when the same name is expressed + in different languages, contains one or more nameEntry elements and an + optional useDates element. For example, within the context of the Archive of + Ontario, parallel French and English headings can be designated through two parallel + nameEntry elements, with the two different headings being distinguished by + the values in the xml:lang.

+

Within identity, names represented through nameEntry or + nameEntryParallel may be selected as authorized or variant names. The + authorizedForm and alternativeForm elements are available within + nameEntry and nameEntryParallel elements to identify the status of + the name according to a particular set of rules. The content of the element is the + identification of those rules. Additionally, within nameEntryParallel, a + single nameEntry may be preferred over others. A preferredForm + element is available in that instance to identify the preferred form of the name + according to a particular set of rules. The content of the element identifies those + rules.

description -

The description accommodates a variety of both controlled and prose descriptions of CPF entities. The contained elements closely reflect the descriptive categories outlined in ISAAR (CPF). Descriptive elements - generally have a singular and plural form, the latter being used for those cases of multiple instances of a descriptive category or less formal prose description. For example, function would be used for a - single function term, functions will bundle more than one function descriptor or alternatively, it will allow a discursive description. Most elements within description include an optional - descriptiveNote element to provide explanatory text. Elements for description include:

+

The description accommodates a variety of both controlled and prose + descriptions of CPF entities. The contained elements closely reflect the descriptive + categories outlined in ISAAR (CPF). Descriptive elements generally have a singular and + plural form, the latter being used for those cases of multiple instances of a + descriptive category or less formal prose description. For example, function + would be used for a single function term, functions will bundle more than one + function descriptor or alternatively, it will allow a discursive description. Most + elements within description include an optional descriptiveNote + element to provide explanatory text. Elements for description include:

- existDates — Optional. Dates of existence of the CPF entity being described. Can include actual or approximate dates, using either date, dateRange, or dateSet. - - place — Optional. Includes relevant location information, optionally paired with related date information. Includes elements placeEntry and placeRole and the range of possibilities with date information: date, dateRange, dateSet. - - localDescription — Optional. An element intended to extend the descriptive categories available in a local system. Includes a term element and the range of possibilities with date information: date, dateRange, dateSet. - - legalStatus — Optional. Includes the legal status of a corporate body, typically defined by authorities and granted by either a government or an authorized agency. Includes a term element and the range of possibilities with date information: date, dateRange, dateSet. - - function — Optional. Includes relevant functions, processes, activities, tasks, or transactions performed by the CPF entity being described. Includes a term element and the range of possibilities with date information: date, dateRange, dateSet. - - occupation — Optional. Includes relevant occupations held by the CPF entity being described. Includes a term element and the range of possibilities with date information: date, dateRange, dateSet. - - mandate — Optional. Includes relevant mandates for corporate bodies being described. Includes a term element and the range of possibilities with date information: date, dateRange, dateSet. - - structureOrGenealogy — Optional. Includes information about the structure of a corporate body or the genealogy of a person or family. Includes elements outline, list, and p to assist in structuring the text. - - generalContext — Optional. Includes information about the general social and cultural context of the entity being described. Includes list, outline, p elements to assist in structuring the text. - - biogHist — Optional. Includes discursive text providing biographical and/or historical information about the CPF entity being described. Includes an abstract element for a brief synopsis of the full content; a chronList element allows for structured date, event and optional place information. Includes list, outline, p elements to assist in structuring the text. - + existDates — Optional. Dates of existence of the CPF entity being + described. Can include actual or approximate dates, using either date, + dateRange, or dateSet. + place — Optional. Includes relevant location information, optionally + paired with related date information. Includes elements placeEntry and + placeRole and the range of possibilities with date information: + date, dateRange, dateSet. + localDescription — Optional. An element intended to extend the + descriptive categories available in a local system. Includes a term element + and the range of possibilities with date information: date, + dateRange, dateSet. + legalStatus — Optional. Includes the legal status of a corporate body, + typically defined by authorities and granted by either a government or an authorized + agency. Includes a term element and the range of possibilities with date + information: date, dateRange, dateSet. + function — Optional. Includes relevant functions, processes, + activities, tasks, or transactions performed by the CPF entity being described. + Includes a term element and the range of possibilities with date + information: date, dateRange, dateSet. + occupation — Optional. Includes relevant occupations held by the CPF + entity being described. Includes a term element and the range of + possibilities with date information: date, dateRange, + dateSet. + mandate — Optional. Includes relevant mandates for corporate bodies + being described. Includes a term element and the range of possibilities + with date information: date, dateRange, dateSet. + structureOrGenealogy — Optional. Includes information about the + structure of a corporate body or the genealogy of a person or family. Includes + elements outline, list, and p to assist in structuring + the text. + generalContext — Optional. Includes information about the general + social and cultural context of the entity being described. Includes list, + outline, p elements to assist in structuring the text. + biogHist — Optional. Includes discursive text providing biographical + and/or historical information about the CPF entity being described. Includes an + abstract element for a brief synopsis of the full content; a + chronList element allows for structured date, event and optional place + information. Includes list, outline, p elements to assist + in structuring the text. -

All elements in description provide a localType attribute to provide semantic specificity to the term being used. With the exception of existDates, structureOrGenealogy, - generalContext, and biogHist, plural form grouping elements are available to bundle multiple occurrences of these elements. These grouping elements also include elements citation, - list, outline, and p to accommodate greater complexity in representing the description being created.

+

All elements in description provide a localType attribute to + provide semantic specificity to the term being used. With the exception of + existDates, structureOrGenealogy, generalContext, and + biogHist, plural form grouping elements are available to bundle multiple + occurrences of these elements. These grouping elements also include elements + citation, list, outline, and p to accommodate + greater complexity in representing the description being created.

relations -

One of the core design principles of EAC-CPF is to avoid describing relationships in a linear fashion, but instead to leverage a distributed descriptive environment.

-

As a component of archival description, the description of corporate bodies, persons and families must be brought into relation with the other descriptive components. Such CPF entity descriptions must be dynamically related to the record descriptions for which they provide context, and the functions and activities in which they engage and that the records document. With the exception of unique relations, it is the nature of relations that they take place among entities and not within them. Corporate bodies, persons and families are related to other entities, to functions and activities, and to records. Similarly, functions and activitiesare related to other functions and activities, to creators, and to records; and records are related to other records, to CPF entities, and to functions and activities. Each CPF entity, record, or function/activity description can thus act as a node in a set of relations.

-

Because relations occur between the descriptive nodes, they are most efficiently created and maintained outside of each node. A person, for example, can be related to one or more persons, organizations or families; to - one or more archival records, books, journals, and museum objects; and to various functions and activities. Each of the related entities can be related to one or more other entities. To record all of these relations - in the description of each node is inefficient, as correction of an error would require updating two or more descriptions.

-

While maintaining relations independent of descriptions is efficient, when communicating descriptions between systems or to users it will be necessary to assemble or gather and represent the related descriptions using descriptive surrogates. Each surrogate for a related description will optimally include both human- and machine-readable information. The human-readable information provides succinct descriptions of the related CPF entity, records, or function/activity sufficient to enable identification and a relevancy judgment. The machine-readable information supports a traversable link to the related description.

-

There are three elements for describing relations with other descriptions included in the relations element: cpfRelation, functionRelation, resourceRelation. Within - each of these relations elements, there are relationEntry, objectXMLWrap, objectBinWrap, date, dateRange, dateSet, placeEntry and descriptiveNote - elements. Individual relations include the following optional attributes related to the type of relation that is being described:

+

One of the core design principles of EAC-CPF is to avoid describing relationships in + a linear fashion, but instead to leverage a distributed descriptive environment.

+

As a component of archival description, the description of corporate bodies, persons + and families must be brought into relation with the other descriptive components. Such + CPF entity descriptions must be dynamically related to the record descriptions for + which they provide context, and the functions and activities in which they engage and + that the records document. With the exception of unique relations, it is the nature of + relations that they take place among entities and not within them. Corporate bodies, + persons and families are related to other entities, to functions and activities, and + to records. Similarly, functions and activitiesare related to other functions and + activities, to creators, and to records; and records are related to other records, to + CPF entities, and to functions and activities. Each CPF entity, record, or + function/activity description can thus act as a node in a set of relations.

+

Because relations occur between the descriptive nodes, they are most efficiently + created and maintained outside of each node. A person, for example, can be related to + one or more persons, organizations or families; to one or more archival records, + books, journals, and museum objects; and to various functions and activities. Each of + the related entities can be related to one or more other entities. To record all of + these relations in the description of each node is inefficient, as correction of an + error would require updating two or more descriptions.

+

While maintaining relations independent of descriptions is efficient, when + communicating descriptions between systems or to users it will be necessary to + assemble or gather and represent the related descriptions using descriptive + surrogates. Each surrogate for a related description will optimally include both + human- and machine-readable information. The human-readable information provides + succinct descriptions of the related CPF entity, records, or function/activity + sufficient to enable identification and a relevancy judgment. The machine-readable + information supports a traversable link to the related description.

+

There are three elements for describing relations with other descriptions included in + the relations element: cpfRelation, functionRelation, + resourceRelation. Within each of these relations elements, there are + relationEntry, objectXMLWrap, objectBinWrap, date, + dateRange, dateSet, placeEntry and descriptiveNote + elements. Individual relations include the following optional attributes related to + the type of relation that is being described:

- cpfRelation — includes an attribute cpfRelationType; values are identity, hierarchical, hierarchical-parent, hierarchical-child, temporal, temporal-earlier, temporal-later, family, - associative. - functionRelation — includes an attribute functionRelationType; values are controls, owns, performs. - resourceRelation — includes an attribute resourceRelationType; values are creatorOf, subjectOf, other. + cpfRelation — includes an attribute cpfRelationType; values + are identity, hierarchical, hierarchical-parent, hierarchical-child, temporal, + temporal-earlier, temporal-later, family, associative. + functionRelation — includes an attribute + functionRelationType; values are controls, owns, performs. + resourceRelation — includes an attribute + resourceRelationType; values are creatorOf, subjectOf, other. -

Other attributes available for the relation elements include lastDateTimeVerified, and the suite of simple Xlink attributes.

-

There are two principal rationales behind the simple typing of relations. First, there is general interest in enabling coherent expression and navigation of relations as well as creation of graphic displays of organizational charts, family trees, and time lines. The simple relationships are an experimental attempt to provide the data necessary to construct such displays. At this point, there has been no attempt to test the utility of the structures with graphic displays. Second, basic information about the nature of relations is necessary in order to make the relationship intelligible to users. Given cultural and institutional differences, the number of possible relation types is, in principle, unlimited. EAC-CPF designers decided, though, that to achieve a minimum level of functionality there needed to be consensus on a set of basic or primitive relation types.

+

Other attributes available for the relation elements include + lastDateTimeVerified, and the suite of simple Xlink attributes.

+

There are two principal rationales behind the simple typing of relations. First, + there is general interest in enabling coherent expression and navigation of relations + as well as creation of graphic displays of organizational charts, family trees, and + time lines. The simple relationships are an experimental attempt to provide the data + necessary to construct such displays. At this point, there has been no attempt to test + the utility of the structures with graphic displays. Second, basic information about + the nature of relations is necessary in order to make the relationship intelligible to + users. Given cultural and institutional differences, the number of possible relation + types is, in principle, unlimited. EAC-CPF designers decided, though, that to achieve + a minimum level of functionality there needed to be consensus on a set of basic or + primitive relation types.

Integrating XLink into EAC-CPF -

The EAC-CPF schema includes support for linking to external resources using a limited subset of the xlink standard, which is defined at http://www.w3.org/TR/xlink/. The - xlink attributes can be used to create and describe links between resources. In particular they can be used to reference a richer set of relationships than those that are supported by @cpfRelationType, - @functionRelationType, and @resourceRelationtype. The xlink attributes are available on the following elements: citation, cpfRelation, functionRelation, resourceRelation, - setComponent, and source.

-

A more complete description of these attributes is provided in the attributes section of the tag library, but the following information is intended to summarize how they might be used in conjunction with each - other.

+

The EAC-CPF schema includes support for linking to external resources using a limited + subset of the xlink standard, which is defined at http://www.w3.org/TR/xlink/. The xlink + attributes can be used to create and describe links between resources. In particular + they can be used to reference a richer set of relationships than those that are + supported by @cpfRelationType, @functionRelationType, and @resourceRelationtype. The + xlink attributes are available on the following elements: citation, + cpfRelation, functionRelation, resourceRelation, + setComponent, and source.

+

A more complete description of these attributes is provided in the attributes section + of the tag library, but the following information is intended to summarize how they + might be used in conjunction with each other.

Xlink Type Attribute - xlink:type — This attribute is required if any of the other xlink attributes are used on the parent element. It takes the fixed value of 'simple' since EAC-CPF's implementation of xlink only supports - outbound links to one resource. If multiple outbound links are required, each link should be represented in a new parent element. + xlink:type — This attribute is required if any of the other xlink + attributes are used on the parent element. It takes the fixed value of 'simple' + since EAC-CPF's implementation of xlink only supports outbound links to one + resource. If multiple outbound links are required, each link should be represented + in a new parent element. Locator Attribute - xlink:href — This optional attribute may be used to provide the location of the resource that is being linked to. The link must be a valid URI. + xlink:href — This optional attribute may be used to provide the + location of the resource that is being linked to. The link must be a valid + URI. Semantic Attributes - xlink:arcrole — This optional attribute may be used on cpfRelation, functionRelation, and resourceRelation to provide a precise description of the relationship between the CPF entity - described in the EAC-CPF instance and the description to which it is linked. When used on citation, setComponent, andsource, it provides an explicit and perhaps more precise description of the - relationship that is implied by the context of use. The value must be a valid URI. - xlink:role — This optional attribute is used to provide a reference to the nature of the linked remote resource. It specifically provides a means to specify the nature of a linked resource in - resourceRelation, as described in ISAAR (CPF) 6.2. The value provided must be a valid URI. + xlink:arcrole — This optional attribute may be used on + cpfRelation, functionRelation, and resourceRelation to + provide a precise description of the relationship between the CPF entity described + in the EAC-CPF instance and the description to which it is linked. When used on + citation, setComponent, andsource, it provides an + explicit and perhaps more precise description of the relationship that is implied by + the context of use. The value must be a valid URI. + xlink:role — This optional attribute is used to provide a reference + to the nature of the linked remote resource. It specifically provides a means to + specify the nature of a linked resource in resourceRelation, as described + in ISAAR (CPF) 6.2. The value provided must be a valid URI. Link Behavior Attributes - xlink:actuate — This optional attribute may be used in conjunction with xlink: show to instruct an external application as to the circumstances under which the linked resource should be resolved. For - example, an application can be instructed to load the resource when the parent xml document is loaded or only when the page is requested by a user or application. - xlink:show — This optional attribute may be used in conjunction with xlink:actuate to instruct an external application as to the manner in which the linked resource should be shown to the user when it is - resolved. For example, the application can be instructed to replace the current xml document when loading the resource or to load it in a new window or tab. - xlink:title — This optional attribute may be used to provide a caption or title that an external system or application may use when presenting a link to the user. + xlink:actuate — This optional attribute may be used in conjunction + with xlink: show to instruct an external application as to the circumstances under + which the linked resource should be resolved. For example, an application can be + instructed to load the resource when the parent xml document is loaded or only when + the page is requested by a user or application. + xlink:show — This optional attribute may be used in conjunction with + xlink:actuate to instruct an external application as to the manner in which the + linked resource should be shown to the user when it is resolved. For example, the + application can be instructed to replace the current xml document when loading the + resource or to load it in a new window or tab. + xlink:title — This optional attribute may be used to provide a + caption or title that an external system or application may use when presenting a + link to the user. -

Implementers of EAC-CPF will need to provide for the full - implementation of the xlink attributes using server-side instructions. One implementation example, demonstrating the intended effects of xlink usage, is provided at http://www.snee.com/xml/xlink/sxlinkdemo.xml.

-

The following excerpt provides one example of how xlink might be implemented in reference to an external vocabulary, to indicate that the information at the related URL describes the spouse of the person described in - the EAC-CPF record:

+

Implementers of EAC-CPF will need to provide for the full implementation of the xlink + attributes using server-side instructions. One implementation example, demonstrating + the intended effects of xlink usage, is provided at http://www.snee.com/xml/xlink/sxlinkdemo.xml.

+

The following excerpt provides one example of how xlink might be implemented in + reference to an external vocabulary, to indicate that the information at the related + URL describes the spouse of the person described in the EAC-CPF record:

- + Gregory, John Milton - John Milton Gregory was the husband of Louisa Allen Gregory. + John Milton Gregory was the husband of Louisa Allen + Gregory. - - Collezione Fortunato Depero (Polo culturale e Galleria Museum Depero, Roverto + + Collezione Fortunato Depero (Polo culturale e Galleria Museum + Depero, Roverto - ITA MART, Collezione Depero, Collezione d'arte, 1919-1959, Creatore della collezione, + ITA MART, Collezione Depero, Collezione d'arte, 1919-1959, Creatore + della collezione, -

The vocabulary at purl.org referenced above is not intended to be normative and is provided for illustrative purposes only. Over time it is hoped that communities will develop and maintain controlled - vocabularies to describe the nature of the relationships to the people, families, corporate bodies, resources, and functions that are described in the cpfRelation, resourceRelation, and - functionRelation elements. Such vocabularies could be maintained locally, nationally, or even internationally, perhaps as a continuation of the work of the Technical Subcommittee – Encoded Archival Context (TS-EAC).

+

The vocabulary at purl.org referenced above is not intended to be normative and is + provided for illustrative purposes only. Over time it is hoped that communities will + develop and maintain controlled vocabularies to describe the nature of the + relationships to the people, families, corporate bodies, resources, and functions that + are described in the cpfRelation, resourceRelation, and + functionRelation elements. Such vocabularies could be maintained locally, + nationally, or even internationally, perhaps as a continuation of the work of the + Technical Subcommittee – Encoded Archival Context (TS-EAC).

localType -

As an international effort, the designers of EAC-CPF are attempting to agree on as much as possible while accommodating cultural and institutional differences. The semantics and structure described above represents the - current semantic and structural consensus and is tied closely to ISAAR(CPF).

-

In addition to the element localDescription, described above, many elements may also be qualified with localType. This attribute is intended to enable EAC-CPF to be adapted for use in national, - regional, and local environments where semantics more specific than those provided in EAC-CPF may be necessary, or where descriptive categories not specifically addressed in EAC-CPF are necessary.

+

As an international effort, the designers of EAC-CPF are attempting to agree on as + much as possible while accommodating cultural and institutional differences. The + semantics and structure described above represents the current semantic and structural + consensus and is tied closely to ISAAR(CPF).

+

In addition to the element localDescription, described above, many elements + may also be qualified with localType. This attribute is intended to enable + EAC-CPF to be adapted for use in national, regional, and local environments where + semantics more specific than those provided in EAC-CPF may be necessary, or where + descriptive categories not specifically addressed in EAC-CPF are necessary.

@@ -352,7 +664,8 @@
-
+
abbreviation @@ -361,20 +674,22 @@

The abbreviation element contains an abbreviation or code for - identifying a thesaurus, controlled vocabulary, or other standard used in formulating and - compiling the EAC-CPF description.

+ identifying a thesaurus, controlled vocabulary, or other standard used in formulating + and compiling the EAC-CPF description.

The abbreviation element contains an abbreviation or code for identifying a - thesaurus, controlled vocabulary, or other standard used in formulating and compiling the - EAC-CPF description. It is recommended that the value be selected from an authorized list of - codes. An example of such a list may be the MARC Code List (http://www.loc.gov/marc/sourcelist/).

+ thesaurus, controlled vocabulary, or other standard used in formulating and compiling + the EAC-CPF description. It is recommended that the value be selected from an + authorized list of codes. An example of such a list may be the MARC Code List + (http://www.loc.gov/marc/sourcelist/).

[token]

-

conventionDeclaration, localTypeDeclaration, rightsDeclaration (revised in 2010 Revised)

+

conventionDeclaration, localTypeDeclaration, rightsDeclaration (revised in 2010 + Revised)

@@ -396,7 +711,8 @@ RICA - RICA (Regole italiane di catalogazione per autore) + RICA (Regole italiane di catalogazione per + autore)

@@ -410,16 +726,16 @@

Abstract

-

An element that contains a brief summary of the information contained within - the biogHist as a whole.

+

An element that contains a brief summary of the information contained + within the biogHist as a whole.

-

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.

+

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.

[text], span

@@ -450,39 +766,36 @@
- 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. - 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. + 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. + 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. 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. + 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.
@@ -500,8 +813,8 @@

address is a wrapper element within place. It contains one or more - addressLine elements that together comprise full or sufficient information - identifying a postal or other address related to the entity being described.

+ addressLine elements that together comprise full or sufficient information + identifying a postal or other address related to the entity being described.

addressLine

@@ -556,7 +869,8 @@
-
+
addressLine @@ -567,8 +881,9 @@

One line of a postal or other address

-

A required element in address, the addressLine element is used to encode - one line of a postal or other address. addressLine may be repeated for each line of the address.

+

A required element in address, the addressLine element is used to + encode one line of a postal or other address. addressLine may be repeated for + each line of the address.

[text]

@@ -625,7 +940,8 @@
-
+
agencyCode @@ -633,23 +949,24 @@

Agency Code

-

The code that represents the institution or service responsible for the - creation, maintenance and/or dissemination of the EAC-CPF instance.

+

The code that represents the institution or service responsible for + the creation, maintenance and/or dissemination of the EAC-CPF instance.

An element of maintenanceAgency within control providing a code - representing the institution or service responsible for the creation, maintenance and/or - dissemination of the EAC-CPF instance. The name of the agency is given in - agencyName. The code is used in combination with the content of the required - recordId to provide a globally unique identifier for the instance.

-

The format of the code is constrained to that of the International Standard Identifier for - Libraries and Related Organizations (ISIL: ISO 15511): a prefix, a dash, and an identifier. - The code is alphanumeric (A-Z, 0-9, solidus, hyphen-minus, and colon only) with a maximum of - 16 characters. If appropriate to local or national convention insert a valid ISIL for an - institution, whether provided by a national authority (usually the national library) or a - service (such as OCLC). 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 - the agencyCode element.

+ representing the institution or service responsible for the creation, maintenance + and/or dissemination of the EAC-CPF instance. The name of the agency is given in + agencyName. The code is used in combination with the content of the required + recordId to provide a globally unique identifier for the instance.

+

The format of the code is constrained to that of the International Standard + Identifier for Libraries and Related Organizations (ISIL: ISO 15511): a prefix, a + dash, and an identifier. The code is alphanumeric (A-Z, 0-9, solidus, hyphen-minus, + and colon only) with a maximum of 16 characters. If appropriate to local or national + convention insert a valid ISIL for an institution, whether provided by a national + authority (usually the national library) or a service (such as OCLC). 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 the agencyCode + element.

[text]

@@ -686,7 +1003,8 @@
-
+
agencyName @@ -694,15 +1012,15 @@

Agency Name

-

The name or names of the institution or service responsible for the creation, - maintenance, and/or dissemination of the EAC-CPF instance.

+

The name or names of the institution or service responsible for the + creation, maintenance, and/or dissemination of the EAC-CPF instance.

A mandatory element of maintenanceAgency within control that - provides the name or names of the institution or service responsible for the creation, maintenance - and/or dissemination of the EAC-CPF instance.

+ provides the name or names of the institution or service responsible for the creation, + maintenance and/or dissemination of the EAC-CPF instance.

It is recommended that one uses the form of the agency name that is authorized by an - appropriate national or international agency or service.

+ appropriate national or international agency or service.

[text]

@@ -756,14 +1074,14 @@

Agent

-

The agent (human or machine) responsible for an event in the maintenance of - the EAC instance.

+

The agent (human or machine) responsible for an event in the + maintenance of the EAC instance.

-

For each maintenance event described in a maintenanceEvent element, the name of - the agent responsible for the maintenance event must be given. This might be a person or - institution in which case the agentType should be set as "human," or the name of - a system, in which case set the agentType to "machine."

+

For each maintenance event described in a maintenanceEvent element, the name + of the agent responsible for the maintenance event must be given. This might be a + person or institution in which case the agentType should be set as "human," + or the name of a system, in which case set the agentType to "machine."

[text]

@@ -802,7 +1120,8 @@ updated - June 1, 2012 + June 1, + 2012 human Ionian University Library, Catalog Division @@ -816,7 +1135,8 @@
-
+
agentType @@ -825,12 +1145,12 @@

The type of agent responsible for a maintenance event of the EAC-CPF - instance.

+ instance.

-

For each maintenance event described in a maintenanceEvent element, the type of - agent given in the agent element must be given as "human", - "machine", or "unknown."

+

For each maintenance event described in a maintenanceEvent element, the type + of agent given in the agent element must be given as "human", "machine", or + "unknown."

"human" or "machine" or "unknown" (revised in 2010 Revised)

@@ -867,7 +1187,8 @@ updated - June 1, 2012 + June 1, + 2012 human Ionian University Library, Catalog Division @@ -881,7 +1202,8 @@
-
+
alternativeForm @@ -890,37 +1212,38 @@

Qualifies the name contained in nameEntry or set of names - contained in nameEntryParallel as alternative or variant forms.

+ contained in nameEntryParallel as alternative or variant forms.

The name of an EAC-CPF entity, as formed within the nameEntry or - nameEntryParallel elements, may be the authorized form of the name according to - a particular set of rules or conventions, or it may be an alternative or unauthorized form - according to a different set of rules. This optional element provides the opportunity to - indicate one or more sets of rules or conventions under which the form of the name expressed - in nameEntry or nameEntryParallel would be regarded as an alternative - or unauthorized form.

+ nameEntryParallel elements, may be the authorized form of the name according + to a particular set of rules or conventions, or it may be an alternative or + unauthorized form according to a different set of rules. This optional element + provides the opportunity to indicate one or more sets of rules or conventions under + which the form of the name expressed in nameEntry or + nameEntryParallel would be regarded as an alternative or unauthorized + form.

The eac-cpf schema offers two possibilities:

1. alternativeForm is used within nameEntry only when - nameEntry is not included within nameEntryParallel. In this case, it - qualifies the form of the name recorded within the precise nameEntry element as a - variant form of the name, as compared to other nameEntry elements which are deemed as - authorized ones.

+ nameEntry is not included within nameEntryParallel. In this case, it + qualifies the form of the name recorded within the precise nameEntry element + as a variant form of the name, as compared to other nameEntry elements which + are deemed as authorized ones.

2. alternativeForm may be used within nameEntryParallel to indicate - that the set of parallel names recorded in separate nameEntry elements within - nameEntryParallel are deemed as variant forms of the name.

-

The content of the alternativeForm is an abbreviation selected from a constrained set of values, - each of which represents a set of national, international or other rules that govern the - construction of EAC-CPF names in those environments. The abbreviations expressed in - alternativeForm must be declared within the conventionDeclaration - element in control.

+ that the set of parallel names recorded in separate nameEntry elements within + nameEntryParallel are deemed as variant forms of the name.

+

The content of the alternativeForm is an abbreviation selected from a + constrained set of values, each of which represents a set of national, international + or other rules that govern the construction of EAC-CPF names in those environments. + The abbreviations expressed in alternativeForm must be declared within the + conventionDeclaration element in control.

The parallel element authorizedForm permits one to indicate rules or - conventions according to which the name is the authorized form. The element - preferredForm permits one to indicate that the name as expressed is the - preferred form in the encoder's local context, regardless of its authorized status in any - other name authority environment.

+ conventions according to which the name is the authorized form. The element + preferredForm permits one to indicate that the name as expressed is the + preferred form in the encoder's local context, regardless of its authorized status in + any other name authority environment.

alternativeForm may be repeated in case a single or a set of - nameEntry element(s) may conform to more than one rule.

+ nameEntry element(s) may conform to more than one rule.

[NMTOKEN]

@@ -963,7 +1286,8 @@
-
+
alternativeSet @@ -971,22 +1295,24 @@

Alternative Set

-

A container element for two or more authority records derived from two or - more authority systems, expressed within a single EAC-CPF instance.

+

A container element for two or more authority records derived from two + or more authority systems, expressed within a single EAC-CPF instance.

-

Alternative Set is a container element for two or more authority records derived from two - or more authority systems. Alternative authority records are contained with - alternativeSet in setComponent elements. This approach allows different - descriptions of the same CPF entity to be contained within a single EAC-CPF instance.

-

Authority record aggregation may be used in cooperative or consortial contexts that gather - together records describing the same CPF entity in different languages, or from different rules - when it is desirable to provide users with alternative descriptions of the same entity. For - example, in the context of the European Union, an international cooperative project may want - to provide users the option of storing descriptions in Italian, French, German, English, Spanish, - and in other European languages.

-

alternativeSet should not be confused with sources, wherein authority - records referenced are not intended to be displayed as alternative versions.

+

Alternative Set is a container element for two or more authority records derived from + two or more authority systems. Alternative authority records are contained with + alternativeSet in setComponent elements. This approach allows + different descriptions of the same CPF entity to be contained within a single EAC-CPF + instance.

+

Authority record aggregation may be used in cooperative or consortial contexts that + gather together records describing the same CPF entity in different languages, or from + different rules when it is desirable to provide users with alternative descriptions of + the same entity. For example, in the context of the European Union, an international + cooperative project may want to provide users the option of storing descriptions in + Italian, French, German, English, Spanish, and in other European languages.

+

alternativeSet should not be confused with sources, wherein + authority records referenced are not intended to be displayed as alternative + versions.

setComponent

@@ -1017,15 +1343,20 @@
- + Bright Sparcs Record - + NLA record. - + [...] [...] @@ -1038,7 +1369,8 @@ Bright Sparcs Record - + NLA record. @@ -1046,7 +1378,8 @@
-
+
authorizedForm @@ -1055,36 +1388,36 @@

Qualifies the name contained in nameEntry or the set of names - contained in nameEntryParallel as authorized access points.

+ contained in nameEntryParallel as authorized access points.

The name of an EAC-CPF entity, as formed within the nameEntry or - nameEntryParallel elements, may be the authorized form of the name according to - a particular set of rules or conventions, or it may be an alternative or unauthorized form - according to a different set of rules. This optional element provides the opportunity to - indicate one or more sets of rules or conventions under which the form of the name expressed - in nameEntry or nameEntryParallel would be regarded as an authorized - form.

+ nameEntryParallel elements, may be the authorized form of the name according + to a particular set of rules or conventions, or it may be an alternative or + unauthorized form according to a different set of rules. This optional element + provides the opportunity to indicate one or more sets of rules or conventions under + which the form of the name expressed in nameEntry or + nameEntryParallel would be regarded as an authorized form.

The eac-cpf schema offers two possibilities:

1. authorizedForm is used within nameEntry only when - nameEntry is not included within nameEntryParallel. In this case, it - qualifies the form of the name recorded within the precise nameEntry element as - an authorized access point.

+ nameEntry is not included within nameEntryParallel. In this case, it + qualifies the form of the name recorded within the precise nameEntry element + as an authorized access point.

2. authorizedForm may be used within nameEntryParallel to indicate - that the set of parallel names recorded in separate nameEntry elements within - nameEntryParallel are deemed as authorized access points.

-

The content of the element is an abbreviation selected from a constrained set of values, - each of which represents a set of national, international or other rules that govern the - construction of EAC-CPF names in those environments. The abbreviations expressed in - authorizedForm must be declared within the conventionDeclaration - element in control.

+ that the set of parallel names recorded in separate nameEntry elements within + nameEntryParallel are deemed as authorized access points.

+

The content of the element is an abbreviation selected from a constrained set of + values, each of which represents a set of national, international or other rules that + govern the construction of EAC-CPF names in those environments. The abbreviations + expressed in authorizedForm must be declared within the + conventionDeclaration element in control.

The parallel element alternativeForm permits one to indicate rules or - conventions according to which the name is the authorized form. The element - preferredForm permits one to indicate that the name as expressed is the - preferred form in the encoder's local context, regardless of its authorized status in any - other name authority environment.

+ conventions according to which the name is the authorized form. The element + preferredForm permits one to indicate that the name as expressed is the + preferred form in the encoder's local context, regardless of its authorized status in + any other name authority environment.

authorizedForm may be repeated in case a single or a set of - nameEntry element(s) may conform to more than one rule.

+ nameEntry element(s) may conform to more than one rule.

[NMTOKEN]

@@ -1132,21 +1465,21 @@

Biography or History

-

A concise essay and/or chronology that provides biographical or historical - information about the EAC-CPF entity.

+

A concise essay and/or chronology that provides biographical or + historical information about the EAC-CPF entity.

The biogHist includes significant details about the life of an individual or - family, or the administrative history of a corporate body. The biogHist may - contain just text in a series of Paragraphs p, and/or a Chronology List - chronList that matches dates and date ranges with associated events and/or - places. The abstract element is intended to provide a very brief synopsis of the - full biogHist content that could be extracted for inclusion in a remote source, - such as a MARC record.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the biography or - history of the CPF entity being described. A simpler discursive expression of the information may be encoded - as one or more p elements.

+ family, or the administrative history of a corporate body. The biogHist may + contain just text in a series of Paragraphs p, and/or a Chronology List + chronList that matches dates and date ranges with associated events and/or + places. The abstract element is intended to provide a very brief synopsis of + the full biogHist content that could be extracted for inclusion in a remote + source, such as a MARC record.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the biography or + history of the CPF entity being described. A simpler discursive expression of the + information may be encoded as one or more p elements.

abstract, chronList, citation, list, outline, p

@@ -1180,38 +1513,39 @@
- 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. - 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. + 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. + 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. - 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." + 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." 1936 Bachelor of Science (BSc) completed at the University of - Sydney + Sydney 1937 Master of Science (MSc) completed at the University of - Sydney + Sydney @@ -1226,7 +1560,8 @@
-
+
chronItem @@ -1235,13 +1570,14 @@

A container element that keeps a date or a date range paired with an - associated event and an optional place within a Chronology List chronList.

+ associated event and an optional place within a Chronology List + chronList.

Each chronItem contains a date (a single date) or a - dateRange (an inclusive date span) coupled with an event. A - placeEntry element is optionally available to ground the event in a particular - location.

+ dateRange (an inclusive date span) coupled with an event. A + placeEntry element is optionally available to ground the event in a + particular location.

date, dateRange, event, placeEntry

@@ -1277,7 +1613,7 @@ 1957 Left Mer and moved to the mainland. Worked at various jobs including - canecutter and railway labourer. + canecutter and railway labourer. @@ -1285,13 +1621,14 @@ 1961 Union representative, Townsville-Mount Isa rail construction - project. + project.
-
+
chronList @@ -1299,16 +1636,16 @@

Chronology List

-

A structured chronological list of events, dates, and (optionally) places - that may be used within the biogHist element.

+

A structured chronological list of events, dates, and (optionally) + places that may be used within the biogHist element.

-

Chronology List comprises a sequentially structured list of significant events in the life - of the person or during the existence of the family or corporate body described in the - EAC-CPF instance. Such events are associated with the date of occurrence and optionally with - the name of a place. Each chronList contains a series of chronItem - elements, each associating a date or dateRange with an - event and an optional placeEntry.

+

Chronology List comprises a sequentially structured list of significant events in the + life of the person or during the existence of the family or corporate body described + in the EAC-CPF instance. Such events are associated with the date of occurrence and + optionally with the name of a place. Each chronList contains a series of + chronItem elements, each associating a date or dateRange + with an event and an optional placeEntry.

chronItem

@@ -1345,12 +1682,12 @@ 1936 Bachelor of Science (BSc) completed at the University of - Sydney + Sydney 1937 Master of Science (MSc) completed at the University of - Sydney + Sydney @@ -1364,8 +1701,8 @@ c. 1939 c. 1945 - Worked with Army Intelligence to map the vegetation (trees and undergrowth) - in the coastal regions of New South Wales + Worked with Army Intelligence to map the vegetation (trees and + undergrowth) in the coastal regions of New South Wales @@ -1383,25 +1720,29 @@

An element that cites an external resource.

-

citation is a generic element available within a number of descriptive elements that cites an external resource in machine and / or human readable form. - The purpose of the citation element is to point to a resource that provides - descriptive data which is not otherwise given in the EAC-CPF instance, such as an original - document that sets out the mandate for a corporate body; it should not be confused with the - source element which is used to declare a particular resource used in the - composition of the EAC-CPF instance. In most contexts it is optional, but a - citation element must be given within conventionDeclaration, - localTypeDeclaration, and rightsDeclaration elements in control (revised in 2010 Revised). Provide the formal title or - name of the resource, using the span element to indicate any formatting (such as - italic or bold etc) thought necessary. The user experience can be controlled by use of the - available XML linking Language (Xlink) attributes for which consult the specification at - http://www.w3.org/TR/xlink/.

+

citation is a generic element available within a number of descriptive + elements that cites an external resource in machine and / or human readable form. The + purpose of the citation element is to point to a resource that provides + descriptive data which is not otherwise given in the EAC-CPF instance, such as an + original document that sets out the mandate for a corporate body; it should not be + confused with the source element which is used to declare a particular + resource used in the composition of the EAC-CPF instance. In most contexts it is + optional, but a citation element must be given within + conventionDeclaration, localTypeDeclaration, and + rightsDeclaration elements in control (revised in 2010 Revised). + Provide the formal title or name of the resource, using the span element to + indicate any formatting (such as italic or bold etc) thought necessary. The user + experience can be controlled by use of the available XML linking Language (Xlink) + attributes for which consult the specification at http://www.w3.org/TR/xlink/.

[text], span

-

biogHist, conventionDeclaration, function, functions, legalStatus, legalStatuses, localDescription, localDescriptions, - localTypeDeclaration, mandate, mandates, occupation, occupations, place, places, rightsDeclaration (revised in 2010 Revised)

+

biogHist, conventionDeclaration, function, functions, legalStatus, legalStatuses, + localDescription, localDescriptions, localTypeDeclaration, mandate, mandates, + occupation, occupations, place, places, rightsDeclaration (revised in 2010 + Revised)

@@ -1431,7 +1772,8 @@

- Within conventionDeclaration, localTypeDeclaration and rightsDeclaration (revised in 2010 Revised) + Within conventionDeclaration, localTypeDeclaration and rightsDeclaration + (revised in 2010 Revised)

Mandatory

@@ -1440,7 +1782,8 @@
- Within function, legalStatus, localDescription, mandate, occupation, place + Within function, legalStatus, localDescription, mandate, occupation, + place

Optional

@@ -1449,7 +1792,8 @@
- Within functions, legalStatuses, localDescriptions, mandates, occupations, places + Within functions, legalStatuses, localDescriptions, mandates, occupations, + places

Optional

@@ -1462,28 +1806,33 @@ AFNOR - Indexation conforme à la norme: AFNOR. " AFNOR NF Z44-060 Documentation - Catalogage d'auteurs - et d'anonymes: formes et structures des vedettes de collectivités - auteurs." Décembre 1996. - + Indexation conforme à la norme: AFNOR. " AFNOR NF Z44-060 + Documentation - Catalogage d'auteurs et d'anonymes: formes et structures des + vedettes de collectivités - auteurs." Décembre 1996. USNARA-LDRG U.S. National Archives and Records Administration. "Lifecycle Data - Requirements Guide". March 2012. (for creating the authorized form of the - name). + Requirements Guide". March 2012. (for creating the authorized form of the + name). - FR ANOM COL C11D 1 Fo179-179 vo: concession de pêche en Acadie par le - Roi à Bergier, Gaultier, Boucher et autres daté du 3 mars 1684. + FR ANOM COL C11D 1 Fo179-179 vo: concession de pêche en Acadie par + le Roi à Bergier, Gaultier, Boucher et autres daté du 3 mars + 1684. - The full biography is presented in "Vasari, Giorgio. "Part 3, Paolo Uccello." In The lives of the artists, by Giorgio Vasari, translated by P. Bondanella and J.C. Bondanella. Oxford: Oxford University Press, 1991." + The full biography is presented in "Vasari, Giorgio. "Part 3, + Paolo Uccello." In The lives of the + artists, by Giorgio Vasari, translated by P. Bondanella and J.C. + Bondanella. Oxford: Oxford University Press, 1991."
-
+
componentEntry @@ -1491,17 +1840,18 @@

Component Entry

-

A caption that can be used to provide identification and access to a linked - resource.

+

A caption that can be used to provide identification and access to a + linked resource.

-

A componentEntry occurs within setComponent to provide a - textual note about the EAC-CPF instance that is being bundled together with other authority - records for the same entity within an alternativeSet wrapper. The bundled - alternate records for a given EAC-CPF entity may be in different languages or may come from - different authority systems. The bundling allows them to be transmitted or stored together. - The componentEntry element provides a place where a particular alternate record - can be described or explained in relation to the other authority records.

+

A componentEntry occurs within setComponent to provide a textual + note about the EAC-CPF instance that is being bundled together with other authority + records for the same entity within an alternativeSet wrapper. The bundled + alternate records for a given EAC-CPF entity may be in different languages or may come + from different authority systems. The bundling allows them to be transmitted or stored + together. The componentEntry element provides a place where a particular + alternate record can be described or explained in relation to the other authority + records.

[text]

@@ -1536,12 +1886,18 @@
- + Bright Sparcs Record - + - [...] + [...] + @@ -1557,38 +1913,38 @@

Control

-

The element of the instance that contains control information about its - identity, creation, maintenance, status, and the rules and authorities used in the - composition of the description.

+

The element of the instance that contains control information about + its identity, creation, maintenance, status, and the rules and authorities used in the + composition of the description.

-

This required wrapper element within eac-cpf contains the information necessary - to manage the instance. This includes information about its identity, creation, - maintenance, and status as well the languages, rules and authorities used in the composition - of the description.

+

This required wrapper element within eac-cpf contains the information + necessary to manage the instance. This includes information about its identity, + creation, maintenance, and status as well the languages, rules and authorities used in + the composition of the description.

It must contain a unique identifier for the instance within the recordId - element. 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.

+ 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.

Three elements are available to declare languages, rules and conventions used in the - EAC-CPF instance. The languageDeclaration element provides information on the - language and script used in the description. The conventionDeclaration element - provides information on the authorities or controlled vocabularies used in the instance. - localTypeDeclaration declares the local conventions and controlled - vocabularies used within the localType.

+ EAC-CPF instance. The languageDeclaration element provides information on the + language and script used in the description. The conventionDeclaration + element provides information on the authorities or controlled vocabularies used in the + instance. localTypeDeclaration declares the local conventions and controlled + vocabularies used within the localType.

Other optional elements available in control include a sources - element to provide information about the documentary sources used in the composition of the - description and a publicationStatus element to indicate the editorial status of - the EAC-CPF instance.

-

Other control elements considered necessary but not otherwise included may be given in the - localControl element.

+ element to provide information about the documentary sources used in the composition + of the description and a publicationStatus element to indicate the editorial + status of the EAC-CPF instance.

+

Other control elements considered necessary but not otherwise included may be given + in the localControl element.

-

conventionDeclaration, languageDeclaration, localControl, - localTypeDeclaration, maintenanceAgency, maintenanceHistory, maintenanceStatus, - otherRecordId, publicationStatus, recordId, rightsDeclaration, sources (revised in 2010 Revised)

+

conventionDeclaration, languageDeclaration, localControl, localTypeDeclaration, + maintenanceAgency, maintenanceHistory, maintenanceStatus, otherRecordId, + publicationStatus, recordId, rightsDeclaration, sources (revised in 2010 Revised)

eac-cpf

@@ -1637,13 +1993,15 @@ created - 2009-06-26T05:33:41Z + 2009-06-26T05:33:41Z human bdewhurs - + ISAAR(CPF) Record created based on ISAAR(CPF) 2nd ed Example 5 - Person @@ -1659,7 +2017,8 @@ new GR-ΤΕΙΑ - Technological Educational Institute of Athens + Technological Educational Institute of + Athens Greek language, Modern. @@ -1667,25 +2026,29 @@ ISAAR (CPF) - Committee on Descriptive Standards Canberra. International Standard - Archival Authority Description for Corporate Bodies, Persons and Families (ISAAR - CPF). Australia, Second Edition, October (2003). + Committee on Descriptive Standards Canberra. International + Standard Archival Authority Description for Corporate Bodies, Persons and + Families (ISAAR CPF). Australia, Second Edition, October + (2003). NLG Authorities - Maniati, Ioanna (ed.) (1991). National Library of Greece: Greek Subject Headings Catalog. Athens. + Maniati, Ioanna (ed.) (1991). National Library of Greece: Greek + Subject Headings Catalog. Athens. created 2011-05-20 human - Department of Library Science and Information Systems, Technological Educational Institute of Athens + Department of Library Science and Information Systems, + Technological Educational Institute of Athens - Archives of the Secondary Education Division(Ministry of National Education and Religion). + Archives of the Secondary Education Division(Ministry of + National Education and Religion). @@ -1693,7 +2056,8 @@
-
+
conventionDeclaration @@ -1701,19 +2065,21 @@

Convention Declaration

-

A declaration of the rules or conventions, including authorized controlled - vocabularies and thesauri, applied in creating the EAC-CPF instance.

+

A declaration of the rules or conventions, including authorized + controlled vocabularies and thesauri, applied in creating the EAC-CPF instance.

An optional element of control, used for declaring references in the - citation element to any rules and conventions, including authorized controlled - vocabularies or thesauri, applied in the construction of the description. For example, - conventionDeclaration should be used to identify any controlled vocabularies - the terms of which appear as values of the attribute vocabularySource for term, - placeEntry, and placeRole elements. Any notes relating to how these - rules or conventions have been used may be given within a descriptiveNote - element. The abbreviation element may be used to identify the standard or - controlled vocabulary in a coded structure. Each new rule / set of rules should be contained in a separate conventionDeclaration element.

+ citation element to any rules and conventions, including authorized + controlled vocabularies or thesauri, applied in the construction of the description. + For example, conventionDeclaration should be used to identify any controlled + vocabularies the terms of which appear as values of the attribute + vocabularySource for term, placeEntry, and + placeRole elements. Any notes relating to how these rules or conventions have + been used may be given within a descriptiveNote element. The + abbreviation element may be used to identify the standard or controlled + vocabulary in a coded structure. Each new rule / set of rules should be contained in a + separate conventionDeclaration element.

abbreviation, citation, descriptiveNote

@@ -1748,22 +2114,23 @@ AFNOR AFNOR NFZ 44-060 (decembre 1986) - Indexation conforme à la norme AFNOR NFZ 44-060 (Décembre - 1986) Catalogage: forme et structure des vedettes de collectivités-auteurs - Notice encodee conformement à la norme internationale de description - archivistique contextuelle informatisée EAC 2004 + Indexation conforme à la norme AFNOR NFZ 44-060 (Décembre 1986) + Catalogage: forme et structure des vedettes de collectivités-auteurs Notice + encodee conformement à la norme internationale de description archivistique + contextuelle informatisée EAC 2004 - International Standards Organization. "ISO 8601 - Data elements and - interchange formats - Information interchange - Representation of dates and times." - Geneva: International Standards Organization, 2000. + International Standards Organization. "ISO 8601 - Data elements + and interchange formats - Information interchange - Representation of dates and + times." Geneva: International Standards Organization, 2000.
-
+
cpfDescription @@ -1772,21 +2139,22 @@

The cpfDescription contains the description of one identity. - Commonly one CPF entity has one identity, but when it has more than one, use either - multipleIdentities or multiple interrelated EAC-CPF instances.

+ Commonly one CPF entity has one identity, but when it has more than one, use either + multipleIdentities or multiple interrelated EAC-CPF instances.

-

The cpfDescription contains the description of one identity. Each description - contains the name or names by which the identity is known, and optionally may contain - a description of historical context to facilitate understanding of the identity. The - cpfDescription includes a required identity element containing - authorized or parallel name entries and optional description and - relations to provide contextual information for the CPF entity being described, - including the relations to other corporate bodies, persons, families, resources, and functions.

+

The cpfDescription contains the description of one identity. Each + description contains the name or names by which the identity is known, and optionally + may contain a description of historical context to facilitate understanding of the + identity. The cpfDescription includes a required identity element + containing authorized or parallel name entries and optional description and + relations to provide contextual information for 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 two or more - authority records derived from two or more authority systems. The xml:id - attribute allows individual cpfDescription elements to be individually identified - when using the multipleIdentities structure.

+ authority records derived from two or more authority systems. The xml:id + attribute allows individual cpfDescription elements to be individually + identified when using the multipleIdentities structure.

alternativeSet, description, identity, relations

@@ -1840,7 +2208,8 @@
-
+
cpfRelation @@ -1848,26 +2217,28 @@

Corporate Body, Person, or Family Relation

-

An element designed to encode a relationship between a corporate body, person, or family and the CPF entity described in the EAC-CPF instance

+

An element designed to encode a relationship between a corporate body, + person, or family and the CPF entity described in the EAC-CPF instance

-

The cpfRelation element contains the description of a corporate body, person, - or family related to the described CPF entity. Such related entities are typically described in - another EAC-CPF instance or other encoding language such as MARC. Use the - objectXMLWrap to incorporate XML elements from any XML namespace or - objectBinWrap for base64-encoded binary data. A relationEntry element - is provided for textual identification of the related entity.

+

The cpfRelation element contains the description of a corporate body, + person, or family related to the described CPF entity. Such related entities are + typically described in another EAC-CPF instance or other encoding language such as + MARC. Use the objectXMLWrap to incorporate XML elements from any XML + namespace or objectBinWrap for base64-encoded binary data. A + relationEntry element is provided for textual identification of the related + entity.

Use the date, dateRange, or dateSet elements for - specifying the time period of the relationship and the - placeEntry element for recording relevant location information. A - descriptiveNote element may be included for a more detailed explanation of the relationship.

+ specifying the time period of the relationship and the placeEntry element for + recording relevant location information. A descriptiveNote element may be + included for a more detailed explanation of the relationship.

The cpfRelationType attribute may be used to specify the nature of the - cpfRelation entity's relationship to the entity described in the - EAC-CPF instance. Values are chosen from a closed list.

+ cpfRelation entity's relationship to the entity described in the EAC-CPF + instance. Values are chosen from a closed list.

-

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, - placeEntry, relationEntry

+

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, placeEntry, + relationEntry

relations

@@ -1913,7 +2284,8 @@
- + Étude notariale CX 4 juillet 1609 @@ -1932,32 +2304,34 @@

Date

-

The single date of an event in the history of, or a relationship with, the - person, family, or corporate body being described in the EAC-CPF instance.

+

The single date of an event in the history of, or a relationship with, + the person, family, or corporate body being described in the EAC-CPF instance.

A generic element expressing the single date of an event in the history of, or a - relationship with, the person, family, or corporate body being described in the EAC-CPF - instance. If the event or relationship has inclusive dates use the dateRange - element, while more complex dates (combining singles dates and date ranges) can be expressed - in dateSet.

-

The content of the element is intended to be a human-readable natural language date with a - machine-readable date provided as the value of the standardDate attribute, - formulated according to ISO 8601. Other attributes include notBefore and - notAfter for dates of uncertainty. The localType attribute can be - used to supply a more specific characterization of the date.

-

Dates of existence for the entity being described in the EAC-CPF instance are 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.

+ relationship with, the person, family, or corporate body being described in the + EAC-CPF instance. If the event or relationship has inclusive dates use the + dateRange element, while more complex dates (combining singles dates and date + ranges) can be expressed in dateSet.

+

The content of the element is intended to be a human-readable natural language date + with a machine-readable date provided as the value of the standardDate + attribute, formulated according to ISO 8601. Other attributes include + notBefore and notAfter for dates of uncertainty. The + localType attribute can be used to supply a more specific characterization + of the date.

+

Dates of existence for the entity being described in the EAC-CPF instance are 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.

[text]

-

chronItem, cpfRelation, dateSet, existDates, function, functionRelation, - legalStatus, localControl, localDescription, mandate, occupation, place, resourceRelation, - useDates

+

chronItem, cpfRelation, dateSet, existDates, function, functionRelation, legalStatus, + localControl, localDescription, mandate, occupation, place, resourceRelation, + useDates

@@ -1990,12 +2364,14 @@ September 18, 1765 - September 12, 2000 + September 12, + 2000

-
+
dateRange @@ -2003,30 +2379,32 @@

Date Range

-

The date range of an event in the history of, or a relationship with, the - person, family, or corporate body being described in the EAC-CPF instance. It contains fromDate and toDate child elements.

+

The date range of an event in the history of, or a relationship with, + the person, family, or corporate body being described in the EAC-CPF instance. It + contains fromDate and toDate child elements.

A generic element that expresses inclusive dates of an event in the history of, or a - relationship with, the person, family, or corporate body being described in the EAC-CPF - instance. dateRange contains fromDate and toDate - child elements. If the event or relationship has a single date use the date - element, while more complex dates (combining single dates and date ranges) can be expressed - in dateSet.

-

The localType attribute can be used to supply a more specific characterization - of the date.

-

Dates of existence for the identity being described in the EAC-CPF instance are 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.

+ relationship with, the person, family, or corporate body being described in the + EAC-CPF instance. dateRange contains fromDate and toDate + child elements. If the event or relationship has a single date use the date + element, while more complex dates (combining single dates and date ranges) can be + expressed in dateSet.

+

The localType attribute can be used to supply a more specific + characterization of the date.

+

Dates of existence for the identity being described in the EAC-CPF instance are + 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.

fromDate, toDate

-

chronItem, cpfRelation, dateSet, existDates, function, functionRelation, - legalStatus, localControl, localDescription, mandate, occupation, place, resourceRelation, - useDates

+

chronItem, cpfRelation, dateSet, existDates, function, functionRelation, legalStatus, + localControl, localDescription, mandate, occupation, place, resourceRelation, + useDates

@@ -2066,19 +2444,23 @@

Date Set

-

A grouping element that facilitates complex date expressions by being able to combine single dates and date ranges, multiple single dates, or multiple date ranges.

+

A grouping element that facilitates complex date expressions by being + able to combine single dates and date ranges, multiple single dates, or multiple date + ranges.

-

A grouping element used for combining single dates and date ranges, multiple single dates, or multiple date ranges. The dateSet element is used in situations where complex - date information needs to be conveyed and requires at least two child elements. These can be - a combination of date and dateRange elements.

+

A grouping element used for combining single dates and date ranges, multiple single + dates, or multiple date ranges. The dateSet element is used in situations + where complex date information needs to be conveyed and requires at least two child + elements. These can be a combination of date and dateRange + elements.

date, dateRange

-

cpfRelation, existDates, function, functionRelation, legalStatus, - localDescription, mandate, occupation, place, resourceRelation, useDates

+

cpfRelation, existDates, function, functionRelation, legalStatus, localDescription, + mandate, occupation, place, resourceRelation, useDates

@@ -2118,7 +2500,8 @@

-
+
description @@ -2126,20 +2509,22 @@

Description

-

A wrapper for all of the content elements comprising description of the CPF entity described in the EAC-CPF instance.

+

A wrapper for all of the content elements comprising description of + the CPF entity described in the EAC-CPF instance.

The elements that constitute description together permit descriptive - information to be encoded in either structured or unstructured fashions, or in a combined - approach. description accommodates 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.

+ 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.

biogHist, existDates, function, functions, generalContext, languageUsed, - languagesUsed, legalStatus, legalStatuses, localDescription, localDescriptions, mandate, - mandates, occupation, occupations, place, places, structureOrGenealogy

+ languagesUsed, legalStatus, legalStatuses, localDescription, localDescriptions, + mandate, mandates, occupation, occupations, place, places, structureOrGenealogy

cpfDescription

@@ -2172,27 +2557,31 @@ - September 18, 1765 + September 18, + 1765 June 1, 1846 - Belluno + Belluno Birthplace September 18, 1765 - Cappellari was born at Belluno on 18 September 1765 to a noble family. At an - early age he joined the order of the Camaldolese (part of the Benedictine monastic - family) and entered the Monastery of San Michele di Murano, near Venice. As a Camaldolese - monk, Cappellari rapidly gained distinction for his theological and linguistic skills. - His first appearance before a wider public was in 1799, when he published against the - Italian Jansenists a controversial work entitled II Trionfo della Santa Sede, which besides - passing through several editions in Italy, has been translated into several European - languages. In 1800, he became a member of the Academy of the Catholic Religion, founded - by Pope Pius VII (1800-1823), to which he contributed a number of memoirs on theological - and philosophical questions, and in 1805 was made abbot of San Gregorio on the Caelian - Hill. + Cappellari was born at Belluno on 18 September 1765 to a noble family. + At an early age he joined the order of the Camaldolese (part of the Benedictine + monastic family) and entered the Monastery of San Michele di Murano, near + Venice. As a Camaldolese monk, Cappellari rapidly gained distinction for his + theological and linguistic skills. His first appearance before a wider public + was in 1799, when he published against the Italian Jansenists a controversial + work entitled II + Trionfo della Santa Sede, which besides passing through several + editions in Italy, has been translated into several European languages. In 1800, + he became a member of the Academy of the Catholic Religion, founded by Pope Pius + VII (1800-1823), to which he contributed a number of memoirs on theological and + philosophical questions, and in 1805 was made abbot of San Gregorio on the + Caelian Hill. @@ -2224,7 +2613,8 @@
-
+
descriptiveNote @@ -2232,24 +2622,26 @@

Descriptive Note

-

A generic element that provides additional information and specifications, - in textual form, concerning the descriptive element in which it is contained.

+

A generic element that provides additional information and + specifications, in textual form, concerning the descriptive element in which it is + contained.

A generic element available in a number of descriptive elements that can be used to - provide any additional descriptive notes that might be appropriate. Notes must be contained - in paragraphs (p) and any necessary formatting may be indicated by use of the - span element within p.

+ provide any additional descriptive notes that might be appropriate. Notes must be + contained in paragraphs (p) and any necessary formatting may be indicated by + use of the span element within p.

p

-

conventionDeclaration, cpfRelation, existDates, function, - functionRelation, functions, identity, languageDeclaration, languageUsed, languagesUsed, - legalStatus, legalStatuses, localDescription, localDescriptions, localTypeDeclaration, - maintenanceAgency, mandate, mandates, occupation, occupations, place, places, - resourceRelation, rightsDeclaration, setComponent, source (revised in 2010 Revised)

+

conventionDeclaration, cpfRelation, existDates, function, functionRelation, + functions, identity, languageDeclaration, languageUsed, languagesUsed, legalStatus, + legalStatuses, localDescription, localDescriptions, localTypeDeclaration, + maintenanceAgency, mandate, mandates, occupation, occupations, place, places, + resourceRelation, rightsDeclaration, setComponent, source (revised in 2010 + Revised)

@@ -2271,11 +2663,12 @@

- + ISAAAR(CPF) Record created based on ISAAR(CPF) 2nd ed Example 5 - Person - description + description @@ -2290,15 +2683,16 @@

Encoded Archival Context - Corporate Bodies, Persons, and Families

-

The eac-cpf is the root element and as such contains contains the - entire EAC-CPF description of the person, corporate body, or family. It contains a required - control followed by either a cpfDescription or a - multipleIdentities element.

+

The eac-cpf is the root element and as such contains contains + the entire EAC-CPF description of the person, corporate body, or family. It contains a + required control followed by either a cpfDescription or a + multipleIdentities element.

-

The outermost wrapper element that defines a particular instance of an archival authority - record encoded with the EAC-CPF XML Schema. It contains a required control and - either a cpfDescription or a multipleIndentities element.

+

The outermost wrapper element that defines a particular instance of an archival + authority record encoded with the EAC-CPF XML Schema. It contains a required + control and either a cpfDescription or a + multipleIndentities element.

control, cpfDescription, multipleIdentities

@@ -2325,7 +2719,9 @@
- + [...] [...] @@ -2351,15 +2747,16 @@

Entity Identifier

-

Any formal identifier used to designate the entity being described.

+

Any formal identifier used to designate the entity being + described.

An optional element of identity that 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.

+ 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.

Do not confuse with recordId within control, which refers to an - identifier for the EAC-CPF instance rather than the entity it describes.

+ identifier for the EAC-CPF instance rather than the entity it describes.

[text]

@@ -2424,7 +2821,8 @@
-
+
entityType @@ -2433,12 +2831,12 @@

The type of CPF entity being described. Values available are: person, - corporateBody, or family.

+ corporateBody, or family.

-

Within identity this mandatory element specifies the type of CPF entity being - described in the EAC-CPF instance. Values available are: person, corporateBody, or - family.

+

Within identity this mandatory element specifies the type of CPF entity + being described in the EAC-CPF instance. Values available are: person, corporateBody, + or family.

"person" or "corporateBody" or "family"

@@ -2520,13 +2918,13 @@

Event

-

An element used to encode an event associated with a date and, optionally, a - place within a structured chronology.

+

An element used to encode an event associated with a date and, + optionally, a place within a structured chronology.

The element contains discursive text identifying the event described by the - chronItem. Every event must have an associated date - element, and it may also have an optional placeEntry element.

+ chronItem. Every event must have an associated date + element, and it may also have an optional placeEntry element.

[text]

@@ -2575,15 +2973,16 @@ 1948 - Campaign Manager, 2nd District, State Democratic-Farmer-Labor Central - Committee. Report to Orville Freeman. + Campaign Manager, 2nd District, State Democratic-Farmer-Labor + Central Committee. Report to Orville Freeman.
-
+
eventDateTime @@ -2595,9 +2994,9 @@

A required element within the maintenanceEvent, eventDateTime gives - the date and time of a maintenance event for the EAC-CPF instance. The date and time may be - recorded manually or machine generated in natural language as well as in machine-readable - format by use of the standardDateTime attribute.

+ the date and time of a maintenance event for the EAC-CPF instance. The date and time + may be recorded manually or machine generated in natural language as well as in + machine-readable format by use of the standardDateTime attribute.

[text]

@@ -2635,7 +3034,7 @@ human Bill Stockting - Created from original in ISAAR (CPF), 2nd edition: example + Created from original in ISAAR (CPF), 2nd edition: example 10 @@ -2649,7 +3048,8 @@
-
+
eventDescription @@ -2657,11 +3057,13 @@

Maintenance Event Description

-

The description of a maintenance event in the life of the EAC-CPF instance.

+

The description of a maintenance event in the life of the EAC-CPF + instance.

-

An element of maintenanceEvent used for describing the maintenance event. The element allows a full description of the maintenance event to be given alongside the basic definition of the event in the - eventType element.

+

An element of maintenanceEvent used for describing the maintenance event. + The element allows a full description of the maintenance event to be given alongside + the basic definition of the event in the eventType element.

[text]

@@ -2697,13 +3099,15 @@ human Bill Stockting - Created from original in ISAAR (CPF), 2nd edition: example 10 + Created from original in ISAAR (CPF), 2nd edition: example + 10
-
+
eventType @@ -2714,22 +3118,22 @@

The type of maintenance event for the EAC-CPF instance.

-

A required element within maintenanceEvent that identifies the type of maintenance event. - The available values are: "created", "revised", "updated", "deleted", "derived", - "cancelled", or "unknown." A discursive description of the event may be given in the optional - eventDescription element.

-

On first creation, the event type would be "created". A "derived" event type is available - to indicate that the record was derived from another descriptive system. If revisions were - made to an existing EAC-CPF instance, the event type would be "revised". Updating a record, - as a specific type of revision, may be indicated with the value "updated". Because it is - important to be clear what has happened to records particularly when sharing and making - links between them, other event types include "deleted" for records that are deleted from a - system or "cancelled" for records that are marked as not current (obsolete or rejected) but - kept for reference.

+

A required element within maintenanceEvent that identifies the type of + maintenance event. The available values are: "created", "revised", "updated", + "deleted", "derived", "cancelled", or "unknown." A discursive description of the event + may be given in the optional eventDescription element.

+

On first creation, the event type would be "created". A "derived" event type is + available to indicate that the record was derived from another descriptive system. If + revisions were made to an existing EAC-CPF instance, the event type would be + "revised". Updating a record, as a specific type of revision, may be indicated with + the value "updated". Because it is important to be clear what has happened to records + particularly when sharing and making links between them, other event types include + "deleted" for records that are deleted from a system or "cancelled" for records that + are marked as not current (obsolete or rejected) but kept for reference.

-

"cancelled" or "created" or "deleted" or "derived" or "revised" or - "unknown" (revised in 2010 Revised) or "updated"

+

"cancelled" or "created" or "deleted" or "derived" or "revised" or "unknown" (revised + in 2010 Revised) or "updated"

maintenanceEvent

@@ -2761,13 +3165,14 @@ human Bill Stockting Created from original in ISAAR (CPF), 2nd edition: example - 10 + 10
-
+
existDates @@ -2776,23 +3181,23 @@

The dates of existence of the entity being described, such as dates of - establishment and dissolution for corporate bodies and dates of birth and death or floruit - for persons.

+ establishment and dissolution for corporate bodies and dates of birth and death or + floruit for persons.

-

The dates of existence of the entity being described, such as dates of establishment and - dissolution for corporate bodies and dates of birth and death or floruit for persons. - existDates may contain actual or approximate dates expressed through its - elements date, dateRange, or dateSet. A - descriptiveNote may be included if a fuller explanation of the dates of - existence is needed.

+

The dates of existence of the entity being described, such as dates of establishment + and dissolution for corporate bodies and dates of birth and death or floruit for + persons. existDates may contain actual or approximate dates expressed through + its elements date, dateRange, or dateSet. A + descriptiveNote may be included if a fuller explanation of the dates of + existence is needed.

Use the date element to record the date of a single event, such as a date of - birth or date of incorporation. Use dateRange to encode a pair of inclusive - dates. Use dateSet to encode more complex date expressions that intermix - date and dateRange elements.

+ 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.

Do not confuse with useDates, which is a child element of nameEntry - or nameEntryParallel and represents the dates of use for a particular name or set - of names.

+ or nameEntryParallel and represents the dates of use for a particular name or + set of names.

date, dateRange, dateSet, descriptiveNote

@@ -2849,11 +3254,12 @@

The beginning date in a date range.

-

The beginning date in a date range, fromDate may contain actual or approximate - dates expressed as a month, day, or year in any format. A standard numerical form of the - date (YYYYMMDD, etc.) may be specified with the standardDate attribute. The - notBefore and notAfter attributes may be used to indicate - uncertainty. If the fromDate is not known, it may be omitted.

+

The beginning date in a date range, fromDate may contain actual or + approximate dates expressed as a month, day, or year in any format. A standard + numerical form of the date (YYYYMMDD, etc.) may be specified with the + standardDate attribute. The notBefore and notAfter + attributes may be used to indicate uncertainty. If the fromDate is not known, + it may be omitted.

[text]

@@ -2907,31 +3313,34 @@

Function

-

An element that provides information about a function, activity, role, or - purpose performed or manifested by the CPF entity being described.

+

An element that provides information about a function, activity, role, + or purpose performed or manifested by the CPF entity being described.

-

A function element is a wrapper element used to encode an index term, using the - child element term. Terms are used to identify the functions, processes, - activities, tasks, or transactions performed by the CPF entity described in the EAC-CPF instance. They may be drawn from - controlled vocabularies or may be natural language terms. Associated date or date range - (date, dateRange or dateSet) and place(s) - (placeEntry) may be included to further constrain the term's meaning. A - descriptiveNote may be included if a textual explanation is needed.

+

A function element is a wrapper element used to encode an index term, using + the child element term. Terms are used to identify the functions, processes, + activities, tasks, or transactions performed by the CPF entity described in the + EAC-CPF instance. They may be drawn from controlled vocabularies or may be natural + language terms. Associated date or date range (date, dateRange or + dateSet) and place(s) (placeEntry) may be included to further + constrain the term's meaning. A descriptiveNote may be included if a textual + explanation is needed.

A single function element may be encoded directly within - description. Alternatively, multiple function elements may be grouped - within a functions element that facilitates manipulating them as a group.

-

Functions may alternatively be described in discursive form in biogHist. The function element should be used whenever separate - semantic processing of information about functions is required.

-

As a further alternative, descriptions of functions may form discrete components in an - archival descriptive system. Such descriptions should be compiled in accordance with the - International Standard for Describing Functions (ISDF) and will typically be described in - another encoding language. In such a system, use functionRelation to point from - the EAC-CPF entity to the related function description.

+ description. Alternatively, multiple function elements may be + grouped within a functions element that facilitates manipulating them as a + group.

+

Functions may alternatively be described in discursive form in biogHist. The + function element should be used whenever separate semantic processing of + information about functions is required.

+

As a further alternative, descriptions of functions may form discrete components in + an archival descriptive system. Such descriptions should be compiled in accordance + with the International Standard for Describing Functions (ISDF) and will typically be + described in another encoding language. In such a system, use + functionRelation to point from the EAC-CPF entity to the related function + description.

-

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - term

+

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, term

description, functions

@@ -2963,18 +3372,19 @@ Estate ownership - 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). + 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).
-
+
functionRelation @@ -2982,24 +3392,27 @@

Function Relation

-

An element designed to encode a relationship between a function and the CPF entity described in the EAC-CPF instance.

+

An element designed to encode a relationship between a function and + the CPF entity described in the EAC-CPF instance.

-

The functionRelation element contains the description of a function related to - the described CPF entity. Such related functions are typically described in another encoding - language. Use objectXMLWrap to incorporate XML elements from any XML namespace or - objectBinWrap for base64-encoded binary data. A relationEntry element - is provided for textual identification of the related function.

+

The functionRelation element contains the description of a function related + to the described CPF entity. Such related functions are typically described in another + encoding language. Use objectXMLWrap to incorporate XML elements from any XML + namespace or objectBinWrap for base64-encoded binary data. A + relationEntry element is provided for textual identification of the related + function.

Use the date, dateRange, or dateSet elements for - specifying when the relation applied and the placeEntry element for relevant - location information. A descriptiveNote element may be included for a more detailed explanation of the relationship.

+ specifying when the relation applied and the placeEntry element for relevant + location information. A descriptiveNote element may be included for a more + detailed explanation of the relationship.

The functionRelationType attribute is used to specify the nature of the - relationship that exists between the function and the CPF entity described in the EAC-CPF instance. - Values are chosen from a closed list.

+ relationship that exists between the function and the CPF entity described in + the EAC-CPF instance. Values are chosen from a closed list.

-

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, - placeEntry, relationEntry

+

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, placeEntry, + relationEntry

relations

@@ -3047,23 +3460,26 @@ Alumni communication management, University of - Glasgow + Glasgow The management of the University's communication with its - alumni. + alumni. - Εstablishment and abolishment of schools + Εstablishment and abolishment of + schools - The second responsibility of the Department is to control the establishment and abolishment of schools. + The second responsibility of the Department is to control the + establishment and abolishment of schools.
-
+
functions @@ -3071,17 +3487,18 @@

Functions

-

A grouping element used to bundle together individual function - elements.

+

A grouping element used to bundle together individual + function elements.

-

Use the optional functions element to group together one or more occurrences of - function so that they can be manipulated as a package. A single - function element may stand alone or may be wrapped within functions.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the functions, - processes, activities, tasks, or transactions being described. A simpler discursive - expression of the functions may be encoded in one or more p elements.

+

Use the optional functions element to group together one or more occurrences + of function so that they can be manipulated as a package. A single + function element may stand alone or may be wrapped within + functions.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the functions, + processes, activities, tasks, or transactions being described. A simpler discursive + expression of the functions may be encoded in one or more p elements.

citation, descriptiveNote, function, list, outline, p

@@ -3126,7 +3543,8 @@
-
+
generalContext @@ -3134,17 +3552,19 @@

General Context

-

An element that encodes information about the general social and cultural - context of the CPF entity being described.

+

An element that encodes information about the general social and + cultural context of the CPF entity being described.

-

The element generalContext may contain a list, outline, - or p element to format information about the social, cultural, economic, - political, and/or historical milieu in which the CPF entity being described existed. The general context provides wide latitude to record contextual information not specifically accommodated by other elements container in description.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the general context - being described. A simpler discursive expression of the general context may be encoded as - one or more p elements.

+

The element generalContext may contain a list, outline, or + p element to format information about the social, cultural, economic, + political, and/or historical milieu in which the CPF entity being described existed. + The general context provides wide latitude to record contextual information not + specifically accommodated by other elements container in description.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the general context + being described. A simpler discursive expression of the general context may be encoded + as one or more p elements.

citation, list, outline, p

@@ -3178,13 +3598,14 @@
- Edward Koiko Mabo was born in 1936 on the island of Mer, one of the Murray - Islands, which are located at the eastern extremity of Torres Strait. In June 1992, six - months after his death, Mabo achieved national prominence as the successful principal - plaintiff in the landmark High Court ruling on native land title. The High Court ruling, - for the first time, gave legal recognition to the fact that indigenous land ownership - existed in Australia before European settlement and that, in some cases, this land tenure - was not subsequently extinguished by the Crown. + Edward Koiko Mabo was born in 1936 on the island of Mer, one of the + Murray Islands, which are located at the eastern extremity of Torres Strait. In + June 1992, six months after his death, Mabo achieved national prominence as the + successful principal plaintiff in the landmark High Court ruling on native land + title. The High Court ruling, for the first time, gave legal recognition to the + fact that indigenous land ownership existed in Australia before European + settlement and that, in some cases, this land tenure was not subsequently + extinguished by the Crown.
@@ -3198,25 +3619,40 @@

Identity

-

A wrapper element for the name or names related to the identity being described within the cpfDescription element in the EAC-CPF instance. In case of multiple identities, a separate identity element is contained in each of the cpfDescription elements of instance.

+

A wrapper element for the name or names related to the identity being + described within the cpfDescription element in the EAC-CPF instance. In case + of multiple identities, a separate identity element is contained in each of + the cpfDescription elements of instance.

-

identity is a container 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. Within this element the entityType element is required and specifies the type of entity (i.e., corporateBody, family, or person). One or more nameEntry elements and / or one or more nameEntryParallel elements specifying names by which the identity is known is also required. An optional entityId is available for any identifiers associated with the CPF entity.

-

All names by which the identity, being described within one cpfDescription element in the EAC-CPF instance is known are provided within this element. Within identity, each of the names, whether authorized or alternatives, should be recorded in a separate nameEntry element.

-

In addition to needing to accommodate one or more names used for or by the CPF entity, - identity may accommodate two or more parallel names in different languages or - scripts. In countries where there is more than one official language, such as Canada or - Switzerland, names of CPF entities are frequently provided in more than one language. Within - identity, a nameEntryParallel element should be used to group two or - more nameEntry elements that represent parallel forms of the name of the CPF entity - being described.

+

identity is a container 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. Within this element the entityType element + is required and specifies the type of entity (i.e., corporateBody, family, or person). + One or more nameEntry elements and / or one or more + nameEntryParallel elements specifying names by which the identity is known is + also required. An optional entityId is available for any identifiers + associated with the CPF entity.

+

All names by which the identity, being described within one cpfDescription + element in the EAC-CPF instance is known are provided within this element. Within + identity, each of the names, whether authorized or alternatives, should be + recorded in a separate nameEntry element.

+

In addition to needing to accommodate one or more names used for or by the CPF + entity, identity may accommodate two or more parallel names in different + languages or scripts. In countries where there is more than one official language, + such as Canada or Switzerland, names of CPF entities are frequently provided in more + than one language. Within identity, a nameEntryParallel element + should be used to group two or more nameEntry elements that represent + parallel forms of the name of the CPF entity being described.

Within identity, a descriptiveNote element may be used to record - other information in a textual form that assists in the identification of the CPF entity.

-

In case of multiple identities of the same entity in one EAC-CPF instance, a separate identity element is contained in each of the cpfDescription elements of the EAC-CPF instance.

+ other information in a textual form that assists in the identification of the CPF + entity.

+

In case of multiple identities of the same entity in one EAC-CPF instance, a separate + identity element is contained in each of the cpfDescription elements + of the EAC-CPF instance.

-

descriptiveNote, entityId, entityType, nameEntry, - nameEntryParallel

+

descriptiveNote, entityId, entityType, nameEntry, nameEntryParallel

cpfDescription

@@ -3286,12 +3722,13 @@

Item

-

A formatting element that encodes the individual entries in a list.

+

A formatting element that encodes the individual entries in a + list.

The item element is used for general lists within descriptive elements and - within levels in an outline. Do not confuse with chronItem, which encodes entries - within a structured chronology, chronList.

+ within levels in an outline. Do not confuse with chronItem, which encodes + entries within a structured chronology, chronList.

[text], span

@@ -3335,17 +3772,18 @@ 1450-1950 - (1929) + (1929) Globe Gliding - (1930) + (1930) Gems (1931) Words - (1931) - Demonics (1931) - Can We Co-operate - (1942) - Amazing Amazon (1942) - + (1931) + Demonics + (1931) + Can We + Co-operate (1942) + Amazing Amazon + (1942) @@ -3381,16 +3819,16 @@

Language

-

The specification of a particular language used in the EAC-CPF instance or - in the creative work of the CPF entity being described.

+

The specification of a particular language used in the EAC-CPF + instance or in the creative work of the CPF entity being described.

-

A required element within languageDeclaration that gives the main language in - which the EAC-CPF instance is written.

+

A required element within languageDeclaration that gives the main language + in which the EAC-CPF instance is written.

A required element within languageUsed that gives the language or languages - used by the CPF entity being described.

-

The content of the languageCode attribute must be given in the form of valid - code from ISO 639-2b.

+ used by the CPF entity being described.

+

The content of the languageCode attribute must be given in the form of + valid code from ISO 639-2b.

[text]

@@ -3431,7 +3869,8 @@
-
+
languageDeclaration @@ -3439,14 +3878,15 @@

Language Declaration

-

The declaration of the languages and scripts used in the EAC-CPF instance.

+

The declaration of the languages and scripts used in the EAC-CPF + instance.

-

A wrapper element within control that declares the languages and scripts - in which an EAC-CPF instance is written in the required language and - script elements. Any comments about the languages and scripts in which the - EAC-CPF instance is written may be included in the optional descriptiveNote - element.

+

A wrapper element within control that declares the languages and scripts in + which an EAC-CPF instance is written in the required language and + script elements. Any comments about the languages and scripts in which the + EAC-CPF instance is written may be included in the optional descriptiveNote + element.

descriptiveNote, language, script

@@ -3491,7 +3931,8 @@
-
+
languagesUsed @@ -3500,13 +3941,13 @@

A grouping element used to bundle together individual - languageUsed elements.

+ languageUsed elements.

Use the optional languagesUsed element to group together one or more - occurrences of languageUsed so that they can be manipulated as a package. A - single languageUsed may be alone or may be wrapped within - languagesUsed.

+ occurrences of languageUsed so that they can be manipulated as a package. A + single languageUsed may be alone or may be wrapped within + languagesUsed.

descriptiveNote, languageUsed

@@ -3553,7 +3994,8 @@
-
+
languageUsed @@ -3565,11 +4007,11 @@

languageUsed is an element within description used to indicate the - language and script in which the CPF entity being described was creative or productive. Use the - language element to specify the language and a corresponding - script element for the script.

-

Do not confuse with languageDeclaration which refers to the language and script - of the EAC-CPF instance.

+ language and script in which the CPF entity being described was creative or + productive. Use the language element to specify the language and a + corresponding script element for the script.

+

Do not confuse with languageDeclaration which refers to the language and + script of the EAC-CPF instance.

descriptiveNote, language, script

@@ -3613,7 +4055,8 @@
-
+
legalStatus @@ -3621,26 +4064,28 @@

Legal Status

-

An element used to encode information about the legal status of a corporate - body.

+

An element used to encode information about the legal status of a + corporate body.

-

A legalStatus element is a wrapper element used to encode an index term, using the element term. 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.

-

Associated date or date range (date, dateRange or - dateSet) and place(s) (placeEntry) may be included to further - constrain the term's meaning. A descriptiveNote element may be included if fuller - textual explanation is needed.

+

A legalStatus element is a wrapper element used to encode an index term, + using the element term. 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.

+

Associated date or date range (date, dateRange or dateSet) + and place(s) (placeEntry) may be included to further constrain the term's + meaning. A descriptiveNote element may be included if fuller textual + explanation is needed.

A single legalStatus may be encoded directly within description. - Alternatively, multiple legalStatus elements may be grouped within a - legalStatuses element that facilitates manipulating them as a group.

-

Legal statuses may alternatively be described in discursive form in the biogHist. The legalStatus element should be used whenever separate semantic processing of information about legal statuses is required.

+ Alternatively, multiple legalStatus elements may be grouped within a + legalStatuses element that facilitates manipulating them as a group.

+

Legal statuses may alternatively be described in discursive form in the + biogHist. The legalStatus element should be used whenever separate + semantic processing of information about legal statuses is required.

-

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - term

+

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, term

description, legalStatuses

@@ -3681,7 +4126,8 @@
-
+
legalStatuses @@ -3689,18 +4135,18 @@

Legal Statuses

-

A grouping element used to bundle together individual legalStatus - elements.

+

A grouping element used to bundle together individual + legalStatus elements.

Use the optional legalStatuses to group together one or more occurrences of - legalStatus so that they can be manipulated as a package. A single - legalStatus may stand alone or may be wrapped within - legalStatuses.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the legal statuses - being described. A simpler discursive expression of the legal statuses may be encoded as one - or more p elements.

+ legalStatus so that they can be manipulated as a package. A single + legalStatus may stand alone or may be wrapped within + legalStatuses.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the legal statuses + being described. A simpler discursive expression of the legal statuses may be encoded + as one or more p elements.

citation, descriptiveNote, legalStatus, list, outline, p

@@ -3793,15 +4239,15 @@

A required element within outline that delineates the outline - format.

+ format.

Within an outline, multiple level elements are used to indicate the - hierarchical levels of information that comprise the outline. When more than one - hierarchical level exists, successive level exists, successive level - elements are nested recursively to identify the layers of content. Each level, in - turn, contains one item element that convey the information content of - the outline.

+ hierarchical levels of information that comprise the outline. When more than one + hierarchical level exists, successive level exists, successive level + elements are nested recursively to identify the layers of content. Each + level, in turn, contains one item element that convey the + information content of the outline.

item, level

@@ -3864,19 +4310,20 @@

A wrapper element to encode a simple list consisting of one or more - item elements.

+ item elements.

The list element is used for general lists that can be embedded with a large - number of descriptive elements. Lists are comprised of one or more item elements. - Do not confuse with chronList, which encodes a structured chronology.

+ number of descriptive elements. Lists are comprised of one or more item + elements. Do not confuse with chronList, which encodes a structured + chronology.

item

biogHist, functions, generalContext, legalStatuses, localDescriptions, mandates, - occupations, places, structureOrGenealogy

+ occupations, places, structureOrGenealogy

@@ -3902,22 +4349,25 @@ 1450-1950 - (1929) + (1929) Globe Gliding - (1930) + (1930) Gems (1931) - Words (1931) - Demonics (1931) - Can We Co-operate - (1942) - Amazing Amazon (1942) - + Words + (1931) + Demonics + (1931) + Can We + Co-operate (1942) + Amazing Amazon + (1942)

-
+
localControl @@ -3925,14 +4375,15 @@

Local Control

-

Any additional control entry necessary to accommodate local practice.

+

Any additional control entry necessary to accommodate local + practice.

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 should be given in a term element and an - associated date can be given either as a single date (date) or a date range - (dateRange).

+ local practice, in addition to the elements otherwise made available within + control. The value of the entry should be given in a term element + and an associated date can be given either as a single date (date) or a date + range (dateRange).

The type of entry may be defined using the localType attribute.

@@ -3970,7 +4421,8 @@
-
+
localDescription @@ -3978,24 +4430,24 @@

Local Description

-

Used to extend the descriptive categories to others available - in a local system. Its meaning will depend on the context in which it occurs.

+

Used to extend the descriptive categories to others available in a + local system. Its meaning will depend on the context in which it occurs.

localDescription provides a means to extend the list of description elements - defined by ISAAR (CPF) and specified in the EAC-CPF schema. It should be used to record - structured index terms rather than discursive text. It contains a child element - term, which may be drawn from controlled vocabularies or may be natural language - terms. Associate date or date range (date, dateRange or - dateSet) and place(s) (placeEntry) may be included to further - constrain the term's meaning. A descriptiveNote may be included if a fuller - textual explanation is needed.

-

The localDescription element should be used whenever in a local system a separate semantic process - of the descriptive information is required that cannot be accommodated by the existing categories available in EAC-CPF.

+ defined by ISAAR (CPF) and specified in the EAC-CPF schema. It should be used to + record structured index terms rather than discursive text. It contains a child element + term, which may be drawn from controlled vocabularies or may be natural + language terms. Associate date or date range (date, dateRange or + dateSet) and place(s) (placeEntry) may be included to further + constrain the term's meaning. A descriptiveNote may be included if a fuller + textual explanation is needed.

+

The localDescription element should be used whenever in a local system a + separate semantic process of the descriptive information is required that cannot be + accommodated by the existing categories available in EAC-CPF.

-

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - term

+

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, term

description, localDescriptions

@@ -4023,14 +4475,18 @@
- French - France + French + France
-
+
localDescriptions @@ -4039,16 +4495,17 @@

A grouping element used to bundle together individual - localDescription elements.

+ localDescription elements.

Use the optional localDescriptions element to group together one or more - occurrences of localDescription so that they can be manipulated as a package. A - single localDescription may stand alone or may be wrapped within - localDescriptions.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the information being - described. A simpler discursive expression may be encoded as one or more p elements.

+ occurrences of localDescription so that they can be manipulated as a package. + A single localDescription may stand alone or may be wrapped within + localDescriptions.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the information being + described. A simpler discursive expression may be encoded as one or more p + elements.

citation, descriptiveNote, list, localDescription, outline, p

@@ -4080,23 +4537,36 @@ - French - France + French + France - French - France + French + France - Brazil - Brazil + Brazil + Brazil
-
+
localTypeDeclaration @@ -4104,17 +4574,17 @@

Local Type Declaration

-

localTypeDeclaration is used to declare any local conventions used in - localType in the EAC-CPF instance.

+

localTypeDeclaration is used to declare any local conventions + used in localType in the EAC-CPF instance.

The localTypeDeclaration is available to declare the local conventions and - controlled vocabularies used in localType in the EAC-CPF instance. The - citation element must be used to cite the resource that lists the used values - (semantic scope and intention). Any notes relating to how rules or conventions that have been - used may be given within a descriptiveNote element. The abbreviation - element may be used to identify the standard or controlled vocabulary in a coded - structure.

+ controlled vocabularies used in localType in the EAC-CPF instance. The + citation element must be used to cite the resource that lists the used values + (semantic scope and intention). Any notes relating to how rules or conventions that + have been used may be given within a descriptiveNote element. The + abbreviation element may be used to identify the standard or controlled + vocabulary in a coded structure.

abbreviation, citation, descriptiveNote

@@ -4144,18 +4614,21 @@ Categorycodes - The categorycodes used in Swedish NAD (http://nad.ra.se). To be used in - element function + The categorycodes used in Swedish NAD (http://nad.ra.se). To + be used in element function Codes for categorizing different types of authority records through - organizational form, operation, function, archivalorganization etcetera. + organizational form, operation, function, archivalorganization etcetera. +
-
+
maintenanceAgency @@ -4163,19 +4636,19 @@

Maintenance Agency

-

The institution or service responsible for the creation, maintenance, and/or - dissemination of the EAC-CPF instance.

+

The institution or service responsible for the creation, maintenance, + and/or dissemination of the EAC-CPF instance.

A required element within control for wrapping information about the - institution or service responsible for the creation, maintenance, and/or dissemination of - the EAC-CPF instance.

-

This must include the agencyName element and it is recommended to include the - optional agencyCode and / or otherAgencyCode elements as well to - unambiguously identify the institution or service. Additional local institutional codes are - given in otherAgencyCode. Any general information about the institution in - relation to the EAC-CPF instance may also be given in a descriptiveNote - element.

+ institution or service responsible for the creation, maintenance, and/or dissemination + of the EAC-CPF instance.

+

This must include the agencyName element and it is recommended to include + the optional agencyCode and / or otherAgencyCode elements as well to + unambiguously identify the institution or service. Additional local institutional + codes are given in otherAgencyCode. Any general information about the + institution in relation to the EAC-CPF instance may also be given in a + descriptiveNote element.

agencyCode, agencyName, descriptiveNote, otherAgencyCode

@@ -4218,7 +4691,8 @@
-
+
maintenanceEvent @@ -4229,14 +4703,14 @@

A maintenance event in the life of the EAC-CPF instance.

-

An element within maintenanceHistory to record information about - particular maintenance events in the history of the EAC-CPF instance. There will always be - at least one maintenance event for each instance, usually its creation, and the type of each event must - be defined in the eventType element. Information must also be given about who or - what carried out, or was otherwise responsible for, the work on the EAC-CPF instance in the - agent and agentType elements and when the event took place in the - eventDateTime element. The event may also be described in the - eventDescription element.

+

An element within maintenanceHistory to record information about particular + maintenance events in the history of the EAC-CPF instance. There will always be at + least one maintenance event for each instance, usually its creation, and the type of + each event must be defined in the eventType element. Information must also be + given about who or what carried out, or was otherwise responsible for, the work on the + EAC-CPF instance in the agent and agentType elements and when the + event took place in the eventDateTime element. The event may also be + described in the eventDescription element.

agent, agentType, eventDateTime, eventDescription, eventType

@@ -4276,14 +4750,17 @@ revised - 2009-07-08 10:45 + 2009-07-08 + 10:45 human Claire Sibille - Notice convertie en EAC-CPF avec l' éditeur oXygen + Notice convertie en EAC-CPF avec l' éditeur + oXygen created - 2001-11/03 12:00 + 2001-11/03 + 12:00 human Lina Bountouri @@ -4291,7 +4768,8 @@
-
+
maintenanceHistory @@ -4299,14 +4777,15 @@

Maintenance History

-

The history of the creation and maintenance of the EAC-CPF instance.

+

The history of the creation and maintenance of the EAC-CPF + instance.

-

A required wrapper element within control to record the history of the creation and maintenance of - the EAC-CPF instance. There must be at least one maintenanceEvent element, - usually recording the creation of the instance, but there may be many other - maintenanceEvent elements documenting the milestone events or activities in the - maintenance of the instance.

+

A required wrapper element within control to record the history of the + creation and maintenance of the EAC-CPF instance. There must be at least one + maintenanceEvent element, usually recording the creation of the instance, but + there may be many other maintenanceEvent elements documenting the milestone + events or activities in the maintenance of the instance.

maintenanceEvent

@@ -4340,24 +4819,29 @@ created - 29 giugno 2009 + 29 giugno + 2009 human Salvatore Vassallo - Prima codifica dell'espempio in italiano presente nelle ISAAR(CPF) + Prima codifica dell'espempio in italiano presente nelle + ISAAR(CPF) revised - 29 giugno 2009 + 29 giugno + 2009 human Salvatore Vassallo - Aggiunte fonti, regole usate e campi di controllo + Aggiunte fonti, regole usate e campi di + controllo
-
+
maintenanceStatus @@ -4368,26 +4852,26 @@

The current drafting status of the EAC-CPF instance.

-

A required element within control that records the current drafting status of an - EAC-CPF instance: as an EAC-CPF instance is modified or other events happen to it (as - recorded in the maintenanceHistory element), the maintenance status should also be - 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.

+

A required element within control that records the current drafting status + of an EAC-CPF instance: as an EAC-CPF instance is modified or other events happen to + it (as recorded in the maintenanceHistory element), the maintenance status + should also be 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.

-

"cancelled" or "deleted" or "deletedMerged" (revised in 2010 Revised) or "deletedReplaced" or "deletedSplit" or - "derived" or "new" or "revised"

+

"cancelled" or "deleted" or "deletedMerged" (revised in 2010 Revised) or + "deletedReplaced" or "deletedSplit" or "derived" or "new" or "revised"

control

@@ -4426,27 +4910,26 @@

Mandate

-

The source of authority or mandate for the corporate body in terms of its - powers, functions, responsibilities or sphere of activities, such as a law, directive, or - charter.

+

The source of authority or mandate for the corporate body in terms of + its powers, functions, responsibilities or sphere of activities, such as a law, + directive, or charter.

-

A mandate element is a wrapper element used to encode an index term, using the - element, term. Terms are used to identify the source of authority or - mandate for the corporate body in terms of its powers, functions, responsibilities or sphere - of activities, such as a law, directive or charter. Terms may be drawn from controlled - vocabularies or may be natural language terms. Associated date or date range - (date, dateRange or dateSet) and place(s) - (placeEntry) may be included to further constrain the term's meaning. A - descriptiveNote element may be included if a fuller explanation is - needed.

-

A single mandate element may be encoded directly within description. - Alternatively, multiple mandate elements may be grouped within - mandates.

+

A mandate element is a wrapper element used to encode an index term, using + the element, term. Terms are used to identify the source of authority or + mandate for the corporate body in terms of its powers, functions, responsibilities or + sphere of activities, such as a law, directive or charter. Terms may be drawn from + controlled vocabularies or may be natural language terms. Associated date or date + range (date, dateRange or dateSet) and place(s) + (placeEntry) may be included to further constrain the term's meaning. A + descriptiveNote element may be included if a fuller explanation is + needed.

+

A single mandate element may be encoded directly within + description. Alternatively, multiple mandate elements may be grouped + within mandates.

-

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - term

+

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, term

description, mandates

@@ -4483,8 +4966,8 @@ Minnesota. Executive Session Laws 1919 c49 - Board created in 1919 to receive and examine applications for - bonuses from Minnesota soldiers. + Board created in 1919 to receive and examine applications for bonuses + from Minnesota soldiers. @@ -4500,16 +4983,16 @@

A grouping element used to bundle together individual mandate - elements.

+ elements.

-

Use the optional mandates element to group together one or more occurrences of - mandate so that they can be manipulated as a package. A single - mandate may stand alone or may be wrapped within mandates.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the mandates being - described. A simpler discursive expression of the mandates may be encoded as one or more - p elements.

+

Use the optional mandates element to group together one or more occurrences + of mandate so that they can be manipulated as a package. A single + mandate may stand alone or may be wrapped within mandates.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the mandates being + described. A simpler discursive expression of the mandates may be encoded as one or + more p elements.

citation, descriptiveNote, list, mandate, outline, p

@@ -4545,42 +5028,49 @@ Instrucciones de 13-VI-1586 por las que se crean y definen las - secretarias de Tierra y Mar. + secretarias de Tierra y Mar. Real Decreto de Nueva Planta para el consejo de Guerra de - 23-IV-1714. + 23-IV-1714. Real Decreto de Nueva Planta para el consejo de Guerra de - 23-VIII-1715. + 23-VIII-1715. - Law 380/1914, "The Establishment of the Greek State Archiving Service" + Law 380/1914, "The Establishment of the Greek State Archiving + Service" 1914 - The General State Archives of Greece were established thanks the efforts - of the Professor Spyridon Lambrou and the historian-researcher Yiannis Vlachogiannis with the purpose of "collecting and monitoring documents included in all public archives dating 50 years back". - Their efforts conluded to the production of a law by the Prime Minister Eleftherios Venizelos. + The General State Archives of Greece were established thanks the + efforts of the Professor Spyridon Lambrou and the historian-researcher Yiannis + Vlachogiannis with the purpose of "collecting and monitoring documents + included in all public archives dating 50 years back". Their efforts conluded + to the production of a law by the Prime Minister Eleftherios + Venizelos. Law 2027/1939 1939 - Law 2027/1939 determines the "Reorganization of the General State Archives". + Law 2027/1939 determines the "Reorganization of the General State + Archives". Law 1946/1991 1991 - 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. - + 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. @@ -4588,7 +5078,8 @@
-
+
multipleIdentities @@ -4597,15 +5088,16 @@

A wrapper element used to group together more than one - cpfDescription within a single EAC-CPF instance.

+ cpfDescription within a single EAC-CPF instance.

A grouping element used to encode more than one cpfDescription in a single - EAC-CPF instance. The use of the multipleIdentities element can resolve two - identity circumstances. First, it can be used to represent more than one identity (including - official identities) of the same CPF entity each with a separate cpfDescription. - Second, it can be used to represent a collaborative identity that includes multiple - individuals operating under a shared identity (such as a shared pseudonym).

+ EAC-CPF instance. The use of the multipleIdentities element can resolve two + identity circumstances. First, it can be used to represent more than one identity + (including official identities) of the same CPF entity each with a separate + cpfDescription. Second, it can be used to represent a collaborative identity + that includes multiple individuals operating under a shared identity (such as a shared + pseudonym).

cpfDescription

@@ -4696,18 +5188,19 @@ - É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. + É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. @@ -4716,7 +5209,8 @@
-
+
nameEntry @@ -4724,37 +5218,37 @@

Name Entry

-

An element containing a name entry for a corporate body, person, or family. - nameEntry is made up of one or more part elements so that the CPF entity - can be identified with certainty and distinguished from others bearing the same or similar - names.

+

An element containing a name entry for a corporate body, person, or + family. nameEntry is made up of one or more part elements so that + the CPF entity can be identified with certainty and distinguished from others bearing + the same or similar names.

Within identity, the element nameEntry is used to record a name by - which the corporate body, the person, or the family described in the EAC-CPF instance is - known.

+ which the corporate body, the person, or the family described in the EAC-CPF instance + is known.

When nameEntry occurs within nameEntryParallel it is used to record - two or more parallel forms (e.g., official forms of the name in different languages and/or - scripts or transliterated forms of the name). When nameEntry is not included within - nameEntryParallel it is used to record the authorized or alternative forms, - whether standardized or not.

+ two or more parallel forms (e.g., official forms of the name in different languages + and/or scripts or transliterated forms of the name). When nameEntry is not + included within nameEntryParallel it is used to record the authorized or + alternative forms, whether standardized or not.

Each form of the name is recorded in a separate nameEntry element.

Each nameEntry should contain at least one part element. Within - nameEntry each of the component parts of a name may be recorded in a separate - part element.

+ nameEntry each of the component parts of a name may be recorded in a separate + part element.

When nameEntry does not occur within nameEntryParallel, it may - include two optional elements, authorizedForm and alternativeForm, to - account more precisely for the status of the form of the name contained in the - nameEntry element, as compared to other possible forms of the name contained in - other nameEntry elements.

+ include two optional elements, authorizedForm and alternativeForm, + to account more precisely for the status of the form of the name contained in the + nameEntry element, as compared to other possible forms of the name contained + in other nameEntry elements.

The nameEntry element may also contain a useDates element to - indicate the dates the name was used but only when nameEntry is not included within - nameEntryParallel.

+ indicate the dates the name was used but only when nameEntry is not included + within nameEntryParallel.

The attributes scriptCode and xml:lang are used to specify the - script and the language of each of the names recorded in nameEntry.

+ script and the language of each of the names recorded in nameEntry.

If the form of the name recorded in nameEntry is a transliterated one, the - attribute transliteration is used to record the conventions or rules applied to - transliterate this form of the name.

+ attribute transliteration is used to record the conventions or rules + applied to transliterate this form of the name.

alternativeForm, authorizedForm, part, preferredForm, useDates

@@ -4815,7 +5309,8 @@
-
+
nameEntryParallel @@ -4824,20 +5319,21 @@

A wrapper element for two or more nameEntry elements that - represent parallel forms of the name (e.g., official forms of the name in - different languages and/or scripts, transliterated forms of the name).

+ represent parallel forms of the name (e.g., official forms of the name in different + languages and/or scripts, transliterated forms of the name).

A wrapper element used to group two or more nameEntry elements representing - parallel forms of the name for the same CPF entity which are used at the same time (e.g., official forms of the name in - different languages and/or scripts, transliterated forms of the name). All those forms - should have the same status, either authorized or alternative. Two optional elements, - authorizedForm or alternativeForm may be used to account more - precisely for the status of the set of parallel name forms contained in - nameEntryParallel. Do not use for pairing authorized and unauthorized forms of - the same name (e.g., an authorized form with see references).

+ parallel forms of the name for the same CPF entity which are used at the same time + (e.g., official forms of the name in different languages and/or scripts, + transliterated forms of the name). All those forms should have the same status, either + authorized or alternative. Two optional elements, authorizedForm or + alternativeForm may be used to account more precisely for the status of the + set of parallel name forms contained in nameEntryParallel. Do not use for + pairing authorized and unauthorized forms of the same name (e.g., an authorized form + with see references).

The nameEntryParallel element may contain a useDates element to - indicate the dates the set of parallel name forms was used.

+ indicate the dates the set of parallel name forms was used.

alternativeForm, authorizedForm, nameEntry, useDates

@@ -4888,10 +5384,12 @@ Bundeskanzleramt - Federal Chancellery of Germany + Federal Chancellery of + Germany - Chancellerie fédérale d'Allemagne + Chancellerie fédérale + d'Allemagne BK @@ -4907,7 +5405,8 @@
-
+
objectBinWrap @@ -4915,19 +5414,20 @@

Object Bin Wrap

-

This element provides a place for a base64-encoded binary representation of - a resource.

+

This element provides a place for a base64-encoded binary + representation of a resource.

-

This element provides a place for a base64-encoded binary representation of a resource. - The datatype of base64-encoded binary is based on the W3C Schema Part 2: Datatypes. (for which consult the specification at http://www.w3.org/TR/xmlschema-2/)

+

This element provides a place for a base64-encoded binary representation of a + resource. The datatype of base64-encoded binary is based on the W3C Schema Part 2: + Datatypes. (for which consult the specification at + http://www.w3.org/TR/xmlschema-2/)

base64Binary

-

cpfRelation, functionRelation, resourceRelation, setComponent, - source

+

cpfRelation, functionRelation, resourceRelation, setComponent, source

@@ -4952,7 +5452,8 @@

-
+
objectXMLWrap @@ -4963,17 +5464,17 @@

A place for incorporating XML elements from any XML namespace.

-

This element provides a place to express data in another XML encoding language. While the - element is not restricted with respect to namespace, to facilitate interoperability, the XML - should conform to an open, standard XML schema and a namespace attribute should be present - on the root element referencing the namespace of the standard.

+

This element provides a place to express data in another XML encoding language. While + the element is not restricted with respect to namespace, to facilitate + interoperability, the XML should conform to an open, standard XML schema and a + namespace attribute should be present on the root element referencing the namespace of + the standard.

any element from any namespace

-

cpfRelation, functionRelation, resourceRelation, setComponent, - source

+

cpfRelation, functionRelation, resourceRelation, setComponent, source

@@ -4994,7 +5495,10 @@

- + Artisti trentini tra le due guerre @@ -5021,7 +5525,9 @@ Yann Arthus-Bertrand --> - + Paris d'hier et d'aujourd'hui @@ -5036,7 +5542,8 @@
-
+
occupation @@ -5044,27 +5551,27 @@

Occupation

-

An element that provides information about the occupation of the CPF entity - being described.

+

An element that provides information about the occupation of the CPF + entity being described.

-

An occupation element is a wrapper element used to encode an index term, using - the element term. Terms are used to identify an occupation held by the - CPF entity. Terms may be drawn from controlled vocabularies or may be natural language - terms. Associated date or date range (date, dateRange or - dateSet) and place(s) (placeEntry) may be included to further - constrain the term's meaning. A descriptiveNote element may be included if a - textual explanation needed.

+

An occupation element is a wrapper element used to encode an index term, + using the element term. Terms are used to identify an occupation held by the + CPF entity. Terms may be drawn from controlled vocabularies or may be natural language + terms. Associated date or date range (date, dateRange or + dateSet) and place(s) (placeEntry) may be included to further + constrain the term's meaning. A descriptiveNote element may be included if a + textual explanation needed.

A single occupation element may be encoded directly within - description. Alternatively, multiple occupation elements may be - grouped within a occupations wrapper that facilitates manipulating them as a - group.

-

Occupations may alternatively be described in discursive form in biogHist. The occupation element should be used whenever - separate semantic processing of information about occupations is required.

+ description. Alternatively, multiple occupation elements may be + grouped within a occupations wrapper that facilitates manipulating them as a + group.

+

Occupations may alternatively be described in discursive form in biogHist. + The occupation element should be used whenever separate semantic processing + of information about occupations is required.

-

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - term

+

citation, date, dateRange, dateSet, descriptiveNote, placeEntry, term

description, occupations

@@ -5122,7 +5629,7 @@ Vice Consul at the General Consulate of the Hellenic Republic in - London + London 1931 1934 @@ -5136,7 +5643,8 @@ - Head of the Foreign Press Departement (Sub ministry of Press and Information) in Athens + Head of the Foreign Press Departement (Sub ministry of Press and + Information) in Athens 1938 1941 @@ -5150,8 +5658,8 @@ - Director of the political office of Viceroy Archbishop Damaskinos and - director of the National Theatre + Director of the political office of Viceroy Archbishop Damaskinos + and director of the National Theatre 1945 @@ -5169,14 +5677,16 @@ - Appointed as minister to Lebanon (with responsibilities for Libanon, Syria, Jordan, and Iraq + Appointed as minister to Lebanon (with responsibilities for + Libanon, Syria, Jordan, and Iraq 1952 1956 - Head of the Second Department of Politics (Ministry of Foreign Affairs) in Athens + Head of the Second Department of Politics (Ministry of Foreign + Affairs) in Athens 1956 @@ -5188,16 +5698,18 @@ - The complete biography of George Seferis can be found in - "Beaton, Roderick . George Seferis: Waiting for the Angel – A Biography. New Haven: Yale University Press, 2003." - + The complete biography of George Seferis can be found in + "Beaton, Roderick . George Seferis: Waiting for + the Angel – A Biography. New Haven: Yale University Press, 2003." +
-
+
occupations @@ -5205,17 +5717,18 @@

Occupations

-

A grouping element used to bundle together individual occupation - elements.

+

A grouping element used to bundle together individual + occupation elements.

-

Use the optional occupations element to group together one or more occurrences - of occupation so that they can be manipulated as a package. A single - occupation may stand alone or may be wrapped within occupations.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the occupations being - described. A simpler discursive expression of the occupations may be encoded as one or more - p elements.

+

Use the optional occupations element to group together one or more + occurrences of occupation so that they can be manipulated as a package. A + single occupation may stand alone or may be wrapped within + occupations.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the occupations being + described. A simpler discursive expression of the occupations may be encoded as one or + more p elements.

citation, descriptiveNote, list, occupation, outline, p

@@ -5276,7 +5789,7 @@ Vice Consul at the General Consulate of the Hellenic Republic in - London + London 1931 1934 @@ -5290,7 +5803,8 @@ - Head of the Foreign Press Departement (Sub ministry of Press and Information) in Athens + Head of the Foreign Press Departement (Sub ministry of Press and + Information) in Athens 1938 1941 @@ -5304,8 +5818,8 @@ - Director of the political office of Viceroy Archbishop Damaskinos and - director of the National Theatre + Director of the political office of Viceroy Archbishop Damaskinos + and director of the National Theatre 1945 @@ -5323,14 +5837,16 @@ - Appointed as minister to Lebanon (with responsibilities for Libanon, Syria, Jordan, and Iraq + Appointed as minister to Lebanon (with responsibilities for + Libanon, Syria, Jordan, and Iraq 1952 1956 - Head of the Second Department of Politics (Ministry of Foreign Affairs) in Athens + Head of the Second Department of Politics (Ministry of Foreign + Affairs) in Athens 1956 @@ -5342,16 +5858,18 @@ - The complete biography of George Seferis can be found in - "Beaton, Roderick . George Seferis: Waiting for the Angel – A Biography. New Haven: Yale University Press, 2003." - + The complete biography of George Seferis can be found in + "Beaton, Roderick . George Seferis: Waiting for + the Angel – A Biography. New Haven: Yale University Press, 2003." +
-
+
otherAgencyCode @@ -5359,17 +5877,18 @@

Other Agency Code

-

Alternate code representing the institution or service responsible for the - creation, maintenance, and/or dissemination of the EAC-CPF instance.

+

Alternate code representing the institution or service responsible for + the creation, maintenance, and/or dissemination of the EAC-CPF instance.

An element of maintenanceAgency within control providing an - alternative and/or local institution code representing the institution or service - responsible for the creation, maintenance, and/or dissemination of the EAC-CPF instance to - that given in the agencyCode element preferably in the format of the International Standard - Identifier for Libraries and Related Organizations (ISIL: ISO 15511). The name of the agency - is given in agencyName. The addition of an ISO 3166-1 alpha-2 country code as the - prefix is recommended to ensure international uniqueness.

+ alternative and/or local institution code representing the institution or service + responsible for the creation, maintenance, and/or dissemination of the EAC-CPF + instance to that given in the agencyCode element preferably in the format of + the International Standard Identifier for Libraries and Related Organizations (ISIL: + ISO 15511). The name of the agency is given in agencyName. The addition of an + ISO 3166-1 alpha-2 country code as the prefix is recommended to ensure international + uniqueness.

[text] (revised in 2010 Revised)

@@ -5412,7 +5931,8 @@
-
+
otherRecordId @@ -5421,15 +5941,17 @@

Alternative record identifiers that may be associated with the EAC-CPF - instance.

+ instance.

-

An element in control used to encode record identifiers that are alternatives to the mandatory identifier 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.

+

An element in control used to encode record identifiers that are + alternatives to the mandatory identifier 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.

The localType attribute can be used to identify the kind of institution or - service responsible for each associated record identifier if not the same as that given in - the maintenanceAgency element for this EAC-CPF instance.

+ service responsible for each associated record identifier if not the same as that + given in the maintenanceAgency element for this EAC-CPF instance.

[text]

@@ -5471,19 +5993,20 @@

Outline

-

An element used within other elements of description to encode information in an - outline format.

+

An element used within other elements of description to + encode information in an outline format.

-

outline contains one or more level elements, which contain an item element or further level elements in a hierarchical - fashion.

+

outline contains one or more level elements, which contain an + item element or further level elements in a hierarchical + fashion.

level

-

biogHist, functions, generalContext, legalStatuses, localDescriptions, - mandates, occupations, places, structureOrGenealogy

+

biogHist, functions, generalContext, legalStatuses, localDescriptions, mandates, + occupations, places, structureOrGenealogy

@@ -5539,25 +6062,27 @@

Paragraph

-

A generic element used within other elements of description that marks one or more sentences that form a logical prose passage.

+

A generic element used within other elements of description + that marks one or more sentences that form a logical prose passage.

-

A paragraph may be a subdivision of a larger composition, or it may exist alone. It is - usually typographically distinct. A line space is often left blank before it; the text - begins on a new line; and the first letter of the first word is often indented, enlarged, or - both.

+

A paragraph may be a subdivision of a larger composition, or it may exist alone. It + is usually typographically distinct. A line space is often left blank before it; the + text begins on a new line; and the first letter of the first word is often indented, + enlarged, or both.

The p element is an important textual feature, which must be used as part of - any general description within a descriptiveNote element and may be used inside - many of the descriptive elements within description. While it generally contains - discursive text, it may also contain a span element to further stress or style - specific character strings by particular formatting (such as italic or bold, etc.).

+ any general description within a descriptiveNote element and may be used + inside many of the descriptive elements within description. While it + generally contains discursive text, it may also contain a span element to + further stress or style specific character strings by particular formatting (such as + italic or bold, etc.).

[text], span

biogHist, descriptiveNote, functions, generalContext, legalStatuses, - localDescriptions, mandates, occupations, places, structureOrGenealogy

+ localDescriptions, mandates, occupations, places, structureOrGenealogy

@@ -5580,19 +6105,22 @@

- 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, What - Happened to Mary and The - Remarkable Adventures of Christopher Poe (1913), and one volume of poetry, - My Marjonary (1916). - 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 Brazilian American, a weekly magazine that ran - until 1929. With Brown's mother, Cora, the Browns also established magazines in Mexico - City and London: Mexican American - (1924-1929) and British American - (1926-1929). + 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, What Happened to Mary and The Remarkable Adventures of Christopher + Poe (1913), and one volume of poetry, My Marjonary (1916). + 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 + Brazilian American, a + weekly magazine that ran until 1929. With Brown's mother, Cora, the Browns also + established magazines in Mexico City and London: Mexican American (1924-1929) and + British American + (1926-1929).
@@ -5606,16 +6134,17 @@

Part

-

part is used to distinguish components of the name of the CPF entity's name within nameEntry.

+

part is used to distinguish components of the name of the CPF + entity's name within nameEntry.

Within nameEntry each of the component parts 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 component parts of the name. The useDates element - should be used for any date information related to the use of the name.

+ 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 component parts of the name. The useDates element + should be used for any date information related to the use of the name.

The designation of the information contained in the part can be specified by - the attribute localType.

+ the attribute localType.

[text]

@@ -5673,30 +6202,34 @@

Place

-

An element that provides information about a place or jurisdiction where the - CPF entity was based, lived, or with which it had some other significant - connection.

+

An element that provides information about a place or jurisdiction + where the CPF entity was based, lived, or with which it had some other significant + connection.

-

A place element is a wrapper element used to encode an index term placed within the element placeEntry. Terms are used to identify the places or jurisdictions - where the CPF entity was based, lived, or with which it had some other significant - connection. 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 placeEntry and placeRole may be drawn from - controlled vocabularies or may be natural language terms. These controlled vocabularies can - be identified with the vocabularySource attribute. Associated date or date range - (date, dateRange or dateSet) information may be included - to further constrain the term's meaning. A descriptiveNote may be included if a fuller explanation of the relation between the values is needed. An address element is also available for - specifying a postal or other address.

+

A place element is a wrapper element used to encode an index term placed + within the element placeEntry. Terms are used to identify the places or + jurisdictions where the CPF entity was based, lived, or with which it had some other + significant connection. 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 placeEntry and placeRole may be + drawn from controlled vocabularies or may be natural language terms. These controlled + vocabularies can be identified with the vocabularySource attribute. + Associated date or date range (date, dateRange or dateSet) + information may be included to further constrain the term's meaning. A + descriptiveNote may be included if a fuller explanation of the relation + between the values is needed. An address element is also available for + specifying a postal or other address.

A single place element may be encoded directly within description. - Alternatively, multiple place elements may be grouped within a places - wrapper that facilitates manipulating them as a group.

-

Places may alternatively be described in discursive form in biogHist. The place element should be used whenever separate semantic - processing of information about places is required.

+ Alternatively, multiple place elements may be grouped within a + places wrapper that facilitates manipulating them as a group.

+

Places may alternatively be described in discursive form in biogHist. The + place element should be used whenever separate semantic processing of + information about places is required.

address, citation, date, dateRange, dateSet, descriptiveNote, placeEntry, - placeRole

+ placeRole

description, places

@@ -5734,7 +6267,8 @@
-
+
placeEntry @@ -5742,28 +6276,32 @@

Place Entry

-

An element used to encode information about the place or jurisdiction where the CPF entity described in the EAC-CPF instance was based, lived, or with which it had some other significant connection.

+

An element used to encode information about the place or jurisdiction + where the CPF entity described in the EAC-CPF instance was based, lived, or with which + it had some other significant connection.

-

Places 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 place to the - entity.

+

Places 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 place to the entity.

latitude, longitude, and altitude attributes are - available for specific geographical data. The accuracy attribute may be used to - indicate uncertainty. The vocabularySource attribute may be used to indicate the - controlled vocabulary from which the placeEntry term is derived.

+ available for specific geographical data. The accuracy attribute may be + used to indicate uncertainty. The vocabularySource attribute may be used to + indicate the controlled vocabulary from which the placeEntry term is + derived.

The placeEntry element is repeatable. It is strongly recommended that within - place, the placeEntry element be repeated only to represent the same - place name in various languages, with an accompanying xml:lang attribute.

+ place, the placeEntry element be repeated only to represent the same + place name in various languages, with an accompanying xml:lang + attribute.

[text]

-

chronItem, cpfRelation, function, functionRelation, legalStatus, - localDescription, mandate, occupation, place, resourceRelation

+

chronItem, cpfRelation, function, functionRelation, legalStatus, localDescription, + mandate, occupation, place, resourceRelation

@@ -5811,12 +6349,13 @@ Birthplace - Strängnäs + Strängnäs Family seat - Auchinleck - (Scotland) + Auchinleck (Scotland) 1504 1986 @@ -5826,7 +6365,8 @@

-
+
placeRole @@ -5834,16 +6374,18 @@

Place Role

-

An element to identify the contextual role a place or jurisdiction encoded in place elements has in relation to the CPF entity.

+

An element to identify the contextual role a place or jurisdiction + encoded in place elements has in relation to the CPF entity.

placeRole provides a contextual role for a placeEntry within - place. Places should be identified in placeEntry by the proper noun that commonly designates - the place, natural feature, or political jurisdiction. It is strongly recommended that each - place name is accompanied by a placeRole element in order to describe the nature - of the association of the place to the CPF entity.

+ place. Places should be identified in placeEntry by the proper noun + that commonly designates the place, natural feature, or political jurisdiction. It is + strongly recommended that each place name is accompanied by a placeRole + element in order to describe the nature of the association of the place to the CPF + entity.

The vocabularySource attribute may be used to indicate the controlled - vocabulary form which the placeRole term is derived.

+ vocabulary form which the placeRole term is derived.

[text]

@@ -5889,7 +6431,8 @@ Residence - Greece + Greece
@@ -5904,16 +6447,16 @@

A grouping element used to bundle together individual place - elements.

+ elements.

Use the optional places element to group together one or more occurrences of - place so that they can be manipulated as a package. A single place - may stand alone or may be wrapped within places.

-

The optional citation, list, and outline elements are - used to accommodate greater complexity in expressing or representing the places and dates - being described. A simpler discursive expression of the places may be encoded as one or more - p elements.

+ place so that they can be manipulated as a package. A single place + may stand alone or may be wrapped within places.

+

The optional citation, list, and outline elements are used + to accommodate greater complexity in expressing or representing the places and dates + being described. A simpler discursive expression of the places may be encoded as one + or more p elements.

citation, descriptiveNote, list, outline, p, place

@@ -5982,7 +6525,8 @@
-
+
preferredForm @@ -5990,28 +6534,28 @@

Preferred Form of Name

-

An element used to indicate which of the parallel names recorded within - nameEntryParallel, is the preferred one for display purposes in a given - context.

+

An element used to indicate which of the parallel names recorded + within nameEntryParallel, is the preferred one for display purposes in a + given context.

-

In cases where parallel names are encoded as multiple nameEntry elements within - nameEntryParallel, a nameEntry may be chosen as preferred in a given - context. The preferredForm element is used only when nameEntry occurs - within nameEntryParallel. It is used only to distinguish the preferred form of - the name to be displayed, as compared to the other authorized parallel names recorded in - other nameEntry elements.

+

In cases where parallel names are encoded as multiple nameEntry elements + within nameEntryParallel, a nameEntry may be chosen as preferred in + a given context. The preferredForm element is used only when + nameEntry occurs within nameEntryParallel. It is used only to + distinguish the preferred form of the name to be displayed, as compared to the other + authorized parallel names recorded in other nameEntry elements.

The preferredForm element contains an abbreviation of the relevant national, - international or other convention or rule applied by a given agency and according to which - the name thus qualified is deemed as preferred to the others. The abbreviations expressed in - preferredForm must be declared within the conventionDeclaration - element in control.

+ international or other convention or rule applied by a given agency and according to + which the name thus qualified is deemed as preferred to the others. The abbreviations + expressed in preferredForm must be declared within the + conventionDeclaration element in control.

Within nameEntryParallel, preferredForm may occur simultaneously - with authorizedForm elements. While the authorizedForm, when used - within nameEntryParallel, qualifies collectively the set of the parallel forms - recorded in the separate nameEntry elements, the preferredForm element - is used specifically within the nameEntry elements to qualify the preferred - form(s) of the name that an agency chooses to display.

+ with authorizedForm elements. While the authorizedForm, when used + within nameEntryParallel, qualifies collectively the set of the parallel + forms recorded in the separate nameEntry elements, the preferredForm + element is used specifically within the nameEntry elements to qualify the + preferred form(s) of the name that an agency chooses to display.

[text] (revised in 2010 Revised)

@@ -6057,7 +6601,8 @@
-
+
publicationStatus @@ -6069,7 +6614,7 @@

The current publication status of the EAC-CPF instance may be specified in the - publicationStatus element.

+ publicationStatus element.

"inProcess" or "approved" or "published" (revised in 2010 Revised)

@@ -6114,11 +6659,12 @@

The unique identifier for a particular instance.

-

A required element within control that designates a unique identifier for the - EAC-CPF instance. The assigning owner ensures the uniqueness of the recordId within the EAC-CPF - descriptive system under its control. The recordId, when used in combination with - the content of the required agencyCode element within - maintenanceAgency, will provide a globally unique identifier.

+

A required element within control that designates a unique identifier for + the EAC-CPF instance. The assigning owner ensures the uniqueness of the + recordId within the EAC-CPF descriptive system under its control. The + recordId, when used in combination with the content of the required + agencyCode element within maintenanceAgency, will provide a globally + unique identifier.

Record alternate record identifiers if desired in otherRecordId.

@@ -6153,7 +6699,8 @@
-
+
relationEntry @@ -6161,10 +6708,13 @@

Relation Entry

-

A descriptive element for relations that identifies the relationship in a textual form.

+

A descriptive element for relations that identifies the relationship + in a textual form.

-

A descriptive element for relations that provides discursive text identifying a related CPF entity, a resource created by or otherwise related to the named CPF entity (e.g., archival records), or the name of a related function.

+

A descriptive element for relations that provides discursive text identifying a + related CPF entity, a resource created by or otherwise related to the named CPF entity + (e.g., archival records), or the name of a related function.

[text]

@@ -6200,24 +6750,27 @@ Alumni communication management, University of - Glasgow + Glasgow - The management of the University's communication with its alumni. + The management of the University's communication with its + alumni. - Supreme Education Council, Ministry of Education + Supreme Education Council, Ministry of + Education 1967 1981 Together with the Minister of Education, has the task of management and - supervision over the General Education. + supervision over the General Education. - Department of Romance Languages records + Department of Romance Languages + records @@ -6233,7 +6786,8 @@
-
+
relations @@ -6241,15 +6795,17 @@

Relations

-

A wrapper element for grouping one or more specific relations, each of them expressed by cpfRelation, resourceRelation, or functionRelation.

+

A wrapper element for grouping one or more specific relations, each of + them expressed by cpfRelation, resourceRelation, or + functionRelation.

A wrapper element that groups together one or more relation elements, each of which - encodes a specific relationship. CPF entities may have relationships with other corporate - bodies, persons or families, which may be expressed using cpfRelation; functions, - which may be expressed using functionRelation; or resources such as archival - collections, bibliographic resources, or artifacts, which may be expressed using - resourceRelation.

+ encodes a specific relationship. CPF entities may have relationships with other + corporate bodies, persons or families, which may be expressed using + cpfRelation; functions, which may be expressed using + functionRelation; or resources such as archival collections, bibliographic + resources, or artifacts, which may be expressed using resourceRelation.

cpfRelation, functionRelation, resourceRelation

@@ -6270,11 +6826,12 @@

-

The general concept of providing connections from archival authority - records to other related resources is stated in ISAAR(CPF) 6.0: "Archival authority records - are created primarily to document the context of records creation. To make this documentation - useful it is necessary to link the authority records to descriptions of records. Archival - authority records can also be linked to other relevant information resources."

+

The general concept of providing connections from archival authority records to other + related resources is stated in ISAAR(CPF) 6.0: "Archival authority records are created + primarily to document the context of records creation. To make this documentation + useful it is necessary to link the authority records to descriptions of records. + Archival authority records can also be linked to other relevant information + resources."

@@ -6295,7 +6852,8 @@
-
+
resourceRelation @@ -6303,23 +6861,26 @@

Resource Relation

-

An element for encoding a relation between a resource and the CPF entity.

+

An element for encoding a relation between a resource and the CPF + entity.

-

The resourceRelation element contains the description of a resource related to - the described entity. Use objectXMLWrap to incorporate XML elements from any XML - namespaces or objectBinWrap for base64-encoded binary data. A - relationEntry element is provided for a textual description of the related resource.

+

The resourceRelation element contains the description of a resource related + to the described entity. Use objectXMLWrap to incorporate XML elements from + any XML namespaces or objectBinWrap for base64-encoded binary data. A + relationEntry element is provided for a textual description of the related + resource.

Use the date, dateRange, or dateSet elements for - specifying the time period of the relationship and the placeEntry element for relevant - location information. A descriptiveNote element may be included for a more - detailed specifications or explanations of the relationship.

+ specifying the time period of the relationship and the placeEntry element for + relevant location information. A descriptiveNote element may be included for + a more detailed specifications or explanations of the relationship.

The resourceRelationType attribute is used to specify the nature of the - relationship between the resource and the entity described in the EAC-CPF instance.

+ relationship between the resource and the entity described in the EAC-CPF + instance.

-

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, - placeEntry, relationEntry

+

date, dateRange, dateSet, descriptiveNote, objectBinWrap, objectXMLWrap, placeEntry, + relationEntry

relations

@@ -6367,7 +6928,9 @@ - + @@ -6390,9 +6953,12 @@ - Department of Romance Languages records + Department of Romance Languages + records - + Department of Romance Languages records @@ -6406,7 +6972,8 @@
-
+
rightsDeclaration @@ -6414,18 +6981,24 @@

Rights Declaration (revised in 2010 Revised)

-

An optional child element of control that indicates a standard rights statement associated with the EAC-CPF instance.

+

An optional child element of control that indicates a + standard rights statement associated with the EAC-CPF instance.

-

Use rightsDeclaration to provide structured information about the usage rights of the EAC-CPF instance. rightsDeclaration should only be used to reference shared published licenses, - such as Creative Commons, RightsStatements.org, and published locally-defined licenses.

-

abbr may be used to provide the abbreviated name for the rights statement. The value of abbr should align with the rights statements referenced by citation and - descriptiveNote.

-

citation must be used to provide a machine-readable reference to a license statement (for example, a dereferenceable URI).

-

descriptiveNote may be used to provide a human-readable description of the license statement.

+

Use rightsDeclaration to provide structured information about the usage + rights of the EAC-CPF instance. rightsDeclaration should only be used to + reference shared published licenses, such as Creative Commons, RightsStatements.org, + and published locally-defined licenses.

+

abbr may be used to provide the abbreviated name for the rights statement. + The value of abbr should align with the rights statements referenced by + citation and descriptiveNote.

+

citation must be used to provide a machine-readable reference to a license + statement (for example, a dereferenceable URI).

+

descriptiveNote may be used to provide a human-readable description of the + license statement.

-

abbr, citation, descriptiveNote

+

abbreviation, citation, descriptiveNote

control

@@ -6469,16 +7042,16 @@

Script

-

The specification of a particular script used in the EAC-CPF instance or in - the creative work of the CPF entity being described.

+

The specification of a particular script used in the EAC-CPF instance + or in the creative work of the CPF entity being described.

A required element within languageDeclaration that gives the main script in - which the EAC-CPF instance is written.

-

A required element within languageUsed that gives the main script used by the - CPF entity being described in his/her creative or productive work.

-

The content of the scriptCode attribute must be given in the form of a valid - code from ISO 15924.

+ which the EAC-CPF instance is written.

+

A required element within languageUsed that gives the main script used by + the CPF entity being described in his/her creative or productive work.

+

The content of the scriptCode attribute must be given in the form of a + valid code from ISO 15924.

[text]

@@ -6531,7 +7104,8 @@
-
+
setComponent @@ -6539,18 +7113,19 @@

Set Component

-

A wrapper element within alternativeSet that contains the EAC-CPF - encoding for one entire authority record, thereby permitting the bundling of authority - records from multiple authority systems within a single cpfDescription.

+

A wrapper element within alternativeSet that contains the + EAC-CPF encoding for one entire authority record, thereby permitting the bundling of + authority records from multiple authority systems within a single + cpfDescription.

-

setComponent provides a wrapper to contain an entire authority record, - so that multiple records for the same identity from separate authority systems or in - different languages, may be combined together within a single EAC-CPF instance. The - mandatory componentEntry element encodes the link to the authority record in the - external authority system. An optional descriptiveNote may be used for a textual - note providing further information about the record referenced in - setComponent.

+

setComponent provides a wrapper to contain an entire authority record, so + that multiple records for the same identity from separate authority systems or in + different languages, may be combined together within a single EAC-CPF instance. The + mandatory componentEntry element encodes the link to the authority record in + the external authority system. An optional descriptiveNote may be used for a + textual note providing further information about the record referenced in + setComponent.

componentEntry, descriptiveNote, objectBinWrap, objectXMLWrap

@@ -6598,7 +7173,8 @@ Bright Sparcs Record - + NLA record. @@ -6614,18 +7190,22 @@

Source

-

A source used for the establishment of the description of the CPF entity in the EAC-CPF instance.

+

A source used for the establishment of the description of the CPF + entity in the EAC-CPF instance.

-

An element for identifying a particular source of evidence used in describing the CPF entity. A record for the source must be included in either objectXMLWrap or - objectBinWrap; or as a textual description in the sourceEntry - element. Use the optional descriptiveNote for any additional notes about the - source. A source in this context should not be confused with the - citation element which is used in a number of descriptive elements to point to a - resource that provides descriptive data which is not otherwise given in the EAC-CPF - instance.

-

A link to the source may be made using the XML Linking Language (Xlink) attributes (consult the specification at http://www.w3.org/TR/xlink/) and the last date and time that the source was verified - can be given in the lastDateTimeVerified attribute.

+

An element for identifying a particular source of evidence used in describing the CPF + entity. A record for the source must be included in either objectXMLWrap or + objectBinWrap; or as a textual description in the sourceEntry + element. Use the optional descriptiveNote for any additional notes about the + source. A source in this context should not be confused with the + citation element which is used in a number of descriptive elements to point + to a resource that provides descriptive data which is not otherwise given in the + EAC-CPF instance.

+

A link to the source may be made using the XML Linking Language (Xlink) attributes + (consult the specification at http://www.w3.org/TR/xlink/) and the last date and time + that the source was verified can be given in the lastDateTimeVerified + attribute.

descriptiveNote, objectBinWrap, objectXMLWrap, sourceEntry

@@ -6672,8 +7252,8 @@ - HMC, Principal Family and Estate Collections: Family Names L-W, - 1999 + HMC, Principal Family and Estate Collections: Family Names + L-W, 1999 HMC, Complete Peerage, 1936 @@ -6684,18 +7264,19 @@ Union Lists of Artist Names, The Getty Research - Institute + Institute Cultural Objects Name Authority Online, The Getty Research - Institute + Institute
-
+
sourceEntry @@ -6703,13 +7284,15 @@

Source Entry

-

A textual identification, such as a title, for a particular source of evidence used to establish the description of the CPF entity in the EAC-CPF instance.

+

A textual identification, such as a title, for a particular source of + evidence used to establish the description of the CPF entity in the EAC-CPF instance. +

The sourceEntry element may be used within the source element to - identify a source used in the construction of the EAC-CPF instance directly rather than - using other content in objectBinWrap or objectXMLWrap. The - sourceEntry element generally contains free text.

+ identify a source used in the construction of the EAC-CPF instance directly rather + than using other content in objectBinWrap or objectXMLWrap. The + sourceEntry element generally contains free text.

[text]

@@ -6746,12 +7329,15 @@ - Cape Breton Development Corporation fonds - Fonds de la Société de développement du Cap-Breton + Cape Breton Development Corporation + fonds + Fonds de la Société de développement du + Cap-Breton Royal Commission on Coal fonds - Fonds de la Commission royale d'enquête sur la houille + Fonds de la Commission royale d'enquête sur la + houille @@ -6759,11 +7345,11 @@ Union Lists of Artist Names, The Getty Research - Institute + Institute Cultural Objects Name Authority Online, The Getty Research - Institute + Institute @@ -6778,10 +7364,12 @@

Sources

-

A grouping element to record the sources used for the description of the CPF entity in the EAC-CPF instance.

+

A grouping element to record the sources used for the description of + the CPF entity in the EAC-CPF instance.

-

A grouping element within control used to group one or more sources consulted in creating the description of the CPF entityin the EAC-CPF instance.

+

A grouping element within control used to group one or more sources + consulted in creating the description of the CPF entityin the EAC-CPF instance.

source

@@ -6816,8 +7404,8 @@ - HMC, Principal Family and Estate Collections: Family Names L-W, - 1999 + HMC, Principal Family and Estate Collections: Family Names + L-W, 1999 HMC, Complete Peerage, 1936 @@ -6828,11 +7416,11 @@ Union Lists of Artist Names, The Getty Research - Institute + Institute Cultural Objects Name Authority Online, The Getty Research - Institute + Institute @@ -6850,9 +7438,11 @@

Specifies the beginning and the end of a span of text.

-

A formatting element for distinguishingwords or phrases that are intentionally stressed or emphasized for linguistic effect or identifying some qualities of the words or phrases. Use - the style attribute to affect an arbitrary stylistic difference. Use the - localType attribute to assign other characteristics.

+

A formatting element for distinguishingwords or phrases that are intentionally + stressed or emphasized for linguistic effect or identifying some qualities of the + words or phrases. Use the style attribute to affect an arbitrary stylistic + difference. Use the localType attribute to assign other + characteristics.

[text]

@@ -6885,25 +7475,29 @@
- 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, What - Happened to Mary and The - Remarkable Adventures of Christopher Poe (1913), and one volume of poetry, - My Marjonary (1916). - 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 Brazilian American, a weekly magazine that ran - until 1929. With Brown's mother, Cora, the Browns also established magazines in Mexico - City and London: Mexican American - (1924-1929) and British American - (1926-1929). + 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, What Happened to Mary and The Remarkable Adventures of Christopher + Poe (1913), and one volume of poetry, My Marjonary (1916). + 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 + Brazilian American, a + weekly magazine that ran until 1929. With Brown's mother, Cora, the Browns also + established magazines in Mexico City and London: Mexican American (1924-1929) and + British American + (1926-1929).
-
+
structureOrGenealogy @@ -6911,26 +7505,26 @@

Structure or Genealogy

-

A description of the internal administrative structure(s) of a corporate - body or the genealogy of a family.

+

A description of the internal administrative structure(s) of a + corporate body or the genealogy of a family.

-

structureOrGenealogy encodes information within the description area, information expressing - the internal administrative structure(s) of a corporate body and the dates of any changes to - that structure that are significant to understanding the way that corporate body conducted - affairs (such as dated organization charts), or the genealogy of a family (such as a family - tree) in a way that demonstrates the interrelationships of its members with relevant - dates.

+

structureOrGenealogy encodes information within the description area, + information expressing the internal administrative structure(s) of a corporate body + and the dates of any changes to that structure that are significant to understanding + the way that corporate body conducted affairs (such as dated organization charts), 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 and outline elements are used to accommodate - greater complexity in expressing or representing the structure(s) or genealogy being described. - citation may be used to provide a link to external documents like organizational - charts and family trees. A simpler discursive expression of the structure(s) or genealogy may be encoded as - one or more p elements.

-

Genealogical and administrative structure information may alternatively be described in - discursive form in the biogHist element (ISAAR (CPF) 5.2.2 History) and/or with - cpfRelation elements (ISAAR (CPF) 5.3). The structureOrGenealogy - element should be used whenever separate semantic processing of information about structures - or genealogies is required.

+ greater complexity in expressing or representing the structure(s) or genealogy being + described. citation may be used to provide a link to external documents like + organizational charts and family trees. A simpler discursive expression of the + structure(s) or genealogy may be encoded as one or more p elements.

+

Genealogical and administrative structure information may alternatively be described + in discursive form in the biogHist element (ISAAR (CPF) 5.2.2 History) and/or + with cpfRelation elements (ISAAR (CPF) 5.3). The + structureOrGenealogy element should be used whenever separate semantic + processing of information about structures or genealogies is required.

citation, list, outline, p

@@ -6964,27 +7558,30 @@
- 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. + 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. - The organogram of the Ministry of Culture and Tourism before its incorporation with the Ministry of Education and Religious Affairs, was the following: + The organogram of the Ministry of + Culture and Tourism before its incorporation with the Ministry of + Education and Religious Affairs, was the following: Minister of Culture and Tourism @@ -7002,7 +7599,8 @@ General Secretary of Culture - General Secretary for Culture and Tourism Infrastructure + General Secretary for Culture and Tourism + Infrastructure @@ -7018,20 +7616,20 @@

Term

-

A generic element used to encode a descriptive term in accordance with local - descriptive rules.

+

A generic element used to encode a descriptive term in accordance with + local descriptive rules.

-

A generic element used to encode a descriptive term in accordance with local descriptive - rules. The local authority – thesaurus or local controlled vocabulary – should be declared - in the localTypeDeclaration element within the control section.

+

A generic element used to encode a descriptive term in accordance with local + descriptive rules. The local authority – thesaurus or local controlled vocabulary – + should be declared in the localTypeDeclaration element within the + control section.

[text]

-

function, legalStatus, localControl, localDescription, mandate, - occupation

+

function, legalStatus, localControl, localDescription, mandate, occupation

@@ -7064,13 +7662,12 @@ Estate ownership - 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). + 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). @@ -7086,20 +7683,22 @@ - Organismo de la Administracion Central del Estado + Organismo de la Administracion Central del + Estado 1769 - Minnesota. Executive Session Laws 1919 c49 + Minnesota. Executive + Session Laws 1919 c49 1919 1925 - Board created in 1919 to receive and examine applications for - bonuses from Minnesota soldiers. + Board created in 1919 to receive and examine applications for bonuses + from Minnesota soldiers. @@ -7122,10 +7721,11 @@

The ending date in a date range.

-

May contain actual or approximate dates expressed as a month, day, or year in any format. - A standard numerical form of the date (YYYYMMDD, etc.) can be specified with the - standardDate attribute. The notBefore and notAfter - attributes may be used to indicate uncertainty. If the toDate is not known, it may be omitted.

+

May contain actual or approximate dates expressed as a month, day, or year in any + format. A standard numerical form of the date (YYYYMMDD, etc.) can be specified with + the standardDate attribute. The notBefore and + notAfter attributes may be used to indicate uncertainty. If the + toDate is not known, it may be omitted.

[text]

@@ -7179,13 +7779,15 @@

Date of Use

-

The dates when the name or names were used for or by the CPF entity being described.

+

The dates when the name or names were used for or by the CPF entity + being described.

-

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, transliterated forms of the name), useDates may occur in nameEntryParallel - rather than in the individual nameEntry elements contained in - nameEntryParallel.

+

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, transliterated forms of the name), + useDates may occur in nameEntryParallel rather than in the + individual nameEntry elements contained in nameEntryParallel.

date, dateRange, dateSet

@@ -7246,7 +7848,8 @@
-
+
accuracy @@ -7257,15 +7860,16 @@

The accuracy specification for a place statement.

-

Within the placeEntry element, this attribute allows for an - accuracy specification.

+

Within the placeEntry element, this attribute allows for an accuracy + specification.

string

-
+
altitude @@ -7276,15 +7880,18 @@

The altitude or elevation of the geographic place.

-

The altitude may occur on placeEntry (revised in 2010 Revised). The value of the attribute is the altitude or elevation of the geographic place named. altitude should be used in conjunction with longitude and - latitude.

+

The altitude may occur on placeEntry (revised in 2010 Revised). + The value of the attribute is the altitude or elevation of the geographic place named. + altitude should be used in conjunction with longitude and + latitude.

NMTOKEN

-
+
countryCode @@ -7295,19 +7902,20 @@

Two letter ISO 3166-1 standard code representing a country.

-

The countryCode may occur on placeEntry or - address. The countryCode attribute may be used to provide the ISO - 3166-1 standard code designating a country. The values are to be taken from the list of ISO 3166-1 Codes for the Representation - of Names of Countries, which can be downloaded from the website of ISO 3166 Maintenance - Agency http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm

+

The countryCode may occur on placeEntry or address. The + countryCode attribute may be used to provide the ISO 3166-1 standard code + designating a country. The values are to be taken from the list of ISO 3166-1 Codes + for the Representation of Names of Countries, which can be downloaded from the website + of ISO 3166 Maintenance Agency + http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm

-

ISO 3166-1 Codes for the Representation of Names of Countries, column - A2.

+

ISO 3166-1 Codes for the Representation of Names of Countries, column A2.

-
+
cpfRelationType @@ -7315,24 +7923,24 @@

Corporate Body, Person, or Family Relation Type

-

The type of relation that the corporate body, person, or family has to the - entity being described.

+

The type of relation that the corporate body, person, or family has to + the entity being described.

-

The cpfRelationType may occur on cpfRelation. The - value designates the type of relation that a corporate body, person, or family has to the - entity being described in the EAC-CPF instance. If the nature of the relation is more - specific than one of the values given below, the Xlink attributes can be used in addition to - cpfRelationType.

+

The cpfRelationType may occur on cpfRelation. The value + designates the type of relation that a corporate body, person, or family has to the + entity being described in the EAC-CPF instance. If the nature of the relation is more + specific than one of the values given below, the Xlink attributes can be used in + addition to cpfRelationType.

-

"identity" or "hierarchical" or "hierarchical-parent" or - "hierarchical-child" or "temporal" or "temporal-earlier" or "temporal-later" or "family" or - "associative"

+

"identity" or "hierarchical" or "hierarchical-parent" or "hierarchical-child" or + "temporal" or "temporal-earlier" or "temporal-later" or "family" or "associative"

-
+
functionRelationType @@ -7340,22 +7948,22 @@

Function Relation Type

-

The type of relation that the entity being described has to the related - function.

+

The type of relation that the entity being described has to the + related function.

-

The functionRelationType may occur on - functionRelation. The value designates the type of relation that the entity being - described has to the related function. If the type of relation is more specific than one of - the values given below, Xlink attributes may be used in addition to - functionRelationType.

+

The functionRelationType may occur on functionRelation. The value + designates the type of relation that the entity being described has to the related + function. If the type of relation is more specific than one of the values given below, + Xlink attributes may be used in addition to functionRelationType.

"controls" or "owns" or "performs"

-
+
identityType @@ -7364,20 +7972,21 @@

Indicates whether the identity is given or acquired. May be useful for - processing when multiple identities are described in the same instance.

+ processing when multiple identities are described in the same instance.

-

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.

+

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.

"given" or "acquired"

-
+
languageCode @@ -7386,21 +7995,23 @@

Three-letter ISO 639-2 language code. Must occur on - language.

+ language.

-

The languageCode must occur on language. The - Language Code is used to provide the ISO 639-2 standard code representing the language of the - EAC-CPF instance. The values are to be taken from the list of ISO 639-2 Codes for the - representation of Names of Languages, which can be downloaded from the website of the - Library of Congress which is the registration agency of the standard (http://www.loc.gov/standards/iso639-2/langhome.html).

+

The languageCode must occur on language. The Language Code is + used to provide the ISO 639-2 standard code representing the language of the EAC-CPF + instance. The values are to be taken from the list of ISO 639-2 Codes for the + representation of Names of Languages, which can be downloaded from the website of the + Library of Congress which is the registration agency of the standard + (http://www.loc.gov/standards/iso639-2/langhome.html).

ISO 639-2 Codes for the Representation of Names of Languages

-
+
lastDateTimeVerified @@ -7412,18 +8023,20 @@

The lastDateTimeVerified may occur on citation, - cpfRelation, functionRelation, resourceRelation, - setComponent, or term. The value of the attribute provides the last - date or last date and time when a related (or linked) object was verified. Verification may - include link resolution as well as verification of the version of the linked object.

+ cpfRelation, functionRelation, resourceRelation, + setComponent, or term. The value of the attribute provides the last + date or last date and time when a related (or linked) object was verified. + Verification may include link resolution as well as verification of the version of the + linked object.

-

Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime. - The following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.

+

Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime. The + following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.

-
+
latitude @@ -7434,16 +8047,17 @@

The geographic latitude of the place.

-

The latitude may occur on placeEntry. The value of the - attribute is the geographic latitude of the place named. latitude should be used - in conjunction with longitude and altitude.

+

The latitude may occur on placeEntry. The value of the attribute + is the geographic latitude of the place named. latitude should be used in + conjunction with longitude and altitude.

NMTOKEN

-
+
localType @@ -7452,24 +8066,25 @@

Used to make the semantics of the element more specific or to provide - semantic specificity to elements that are semantically weak. Value should be an absolute - URI.

+ semantic specificity to elements that are semantically weak. Value should be an + absolute URI.

-

The localType is broadly available on many descriptive and a - few control elements. It is intended to provide a means to narrow the semantics of some - elements or provide semantics for elements that are primarily structural or that are - semantically weak. The value of the localType must conform to W3C Schema Part 2: - Datatypes, anyURI. To facilitate exchange of EAC-CPF instances, it is highly recommend that - the URI be absolute and resolvable to a local resource that describes the semantic scope and - use of the value.

+

The localType is broadly available on many descriptive and a few control + elements. It is intended to provide a means to narrow the semantics of some elements + or provide semantics for elements that are primarily structural or that are + semantically weak. The value of the localType must conform to W3C Schema + Part 2: Datatypes, anyURI. To facilitate exchange of EAC-CPF instances, it is highly + recommend that the URI be absolute and resolvable to a local resource that describes + the semantic scope and use of the value.

anyURI

-
+
longitude @@ -7480,16 +8095,18 @@

The longitude of the place.

-

The longitude may occur on placeEntry (revised in 2010 Revised). The value of the - attribute is the geographic longitude of the place named. longitude should be used - in conjunction with latitude and altitude.

+

The longitude may occur on placeEntry (revised in 2010 Revised). + The value of the attribute is the geographic longitude of the place named. + longitude should be used in conjunction with latitude and + altitude.

NMTOKEN

-
+
notAfter @@ -7500,18 +8117,19 @@

The latest date possible for an uncertain date.

-

The notAfter may occur on date, - fromDate, and toDate. For uncertain dates, used in conjunction with - standardDate, the value of notAfter is the latest date possible. See - also notBefore.

+

The notAfter may occur on date, fromDate, and + toDate. For uncertain dates, used in conjunction with + standardDate, the value of notAfter is the latest date possible. + See also notBefore.

-

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The - following are all valid patterns: 2009-12-31, 2009, 2009-12.

+

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The following are all + valid patterns: 2009-12-31, 2009, 2009-12.

-
+
notBefore @@ -7522,18 +8140,19 @@

The earliest date possible for an uncertain date.

-

The notBefore may occur on date, - fromDate, and toDate. For uncertain dates, used in conjunction with - standardDate, the value of notBefore is the earliest date possible. - See also notAfter.

+

The notBefore may occur on date, fromDate, and + toDate. For uncertain dates, used in conjunction with + standardDate, the value of notBefore is the earliest date + possible. See also notAfter.

-

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The - following are all valid patterns: 2009-12-31, 2009, 2009-12.

+

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The following are all + valid patterns: 2009-12-31, 2009, 2009-12.

-
+
resourceRelationType @@ -7544,18 +8163,19 @@

The type of relation of entity being described to the resource.

-

The resourceRelationType may occur on - resourceRelation. The value designates the type of relation that the entity - described in the EAC-CPF instance has to the resource. If the nature of the relation is more - specific than one of the available values, the Xlink attributes may be used in addition to - resourceRelationType.

+

The resourceRelationType may occur on resourceRelation. The value + designates the type of relation that the entity described in the EAC-CPF instance has + to the resource. If the nature of the relation is more specific than one of the + available values, the Xlink attributes may be used in addition to + resourceRelationType.

"creatorOf" or "subjectOf" or "other"

-
+
scriptCode @@ -7566,16 +8186,17 @@

The ISO 15924 four-letter code for the writing script used.

-

A standard four-letter code for the writing script used with a given - language. The scriptCode attribute is required for the script element, - and is available on other elements where language designations may be used.

+

A standard four-letter code for the writing script used with a given language. The + scriptCode attribute is required for the script element, and is + available on other elements where language designations may be used.

ISO 15924 Code for the Representation of Names and Scripts

-
+
standardDate @@ -7586,18 +8207,19 @@

The date represented in a standard form for computer processing.

-

The standardDate may occur on date, - fromDate, and toDate. The value of standardDate provides a - standard form of the date expressed in date, fromDate, or - toDate that can be used in computer processing, such as searching.

+

The standardDate may occur on date, fromDate, and + toDate. The value of standardDate provides a standard form of the + date expressed in date, fromDate, or toDate that can be + used in computer processing, such as searching.

-

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The - following are all valid patterns: 2009-12-31, 2009, 2009-12.

+

Union of the XML Schema Datatypes date, gYear, and gYearMonth. The following are all + valid patterns: 2009-12-31, 2009, 2009-12.

-
+
standardDateTime @@ -7606,18 +8228,18 @@

The date or date and time represented in a standard form for computer - processing.

+ processing.

-

The standardDateTime may occur on eventDateTime. - The value of standardDateTime provides a standard form of the date or date and - time expressed in the eventDateTime that can be used in computer processing. For - example, using both the value in eventType and standardDateTime, all - EAC-CPF instances "revised" on a particular date can be identified.

+

The standardDateTime may occur on eventDateTime. The value of + standardDateTime provides a standard form of the date or date and time + expressed in the eventDateTime that can be used in computer processing. For + example, using both the value in eventType and standardDateTime, + all EAC-CPF instances "revised" on a particular date can be identified.

-

Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime. - The following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.

+

Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime. The + following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.

@@ -7629,22 +8251,23 @@

Style

-

Used to specify a rendering style for string. It is recommended that the - value conforms to W3C CSS.

+

Used to specify a rendering style for string. It is recommended that + the value conforms to W3C CSS.

-

The style may occur on span. In a limited number - of contexts that accommodate discursive description, span with style - may be used to identify an arbitrary string that is intended to be rendered in a specific - style. It is highly recommended that the value of style be expressed as a W3C CSS - style to facilitate interoperability.

+

The style may occur on span. In a limited number of contexts that + accommodate discursive description, span with style may be used to + identify an arbitrary string that is intended to be rendered in a specific style. It + is highly recommended that the value of style be expressed as a W3C CSS + style to facilitate interoperability.

string

-
+
transliteration @@ -7653,18 +8276,19 @@

A value designating the transliteration scheme used in representing - converting one script into another script.

+ converting one script into another script.

-

The conventions or rules that prescribe a method for converting one - script into another script.

+

The conventions or rules that prescribe a method for converting one script into + another script.

NMTOKEN

-
+
vocabularySource @@ -7673,19 +8297,20 @@

A value designating the source of the vocabulary from which terms are - derived.

+ derived.

The controlled vocabulary used to derive terms for the term, - placeEntry, and placeRole elements. Controlled vocabularies should be - declared in the conventionDeclaration element within control.

+ placeEntry, and placeRole elements. Controlled vocabularies should + be declared in the conventionDeclaration element within control.

anyURI

-
+
xlink:actuate @@ -7693,24 +8318,25 @@

Xlink: Actuate

-

Used to signal intended behavior with respect to whether the remote resource - link is resolved when the containing resource is rendered, or when the user requests the - resource.

+

Used to signal intended behavior with respect to whether the remote + resource link is resolved when the containing resource is rendered, or when the user + requests the resource.

-

The xlink:actuate should be used with the - xlink:show to indicate intended behavior. The xlink:actuate is used to - signal intended behavior with respect to when the remote resource is to appear. The values - indicate whether the resource is to appear automatically when the containing resource is - rendered ("onLoad"), or only after the user requests the resource ("onRequest"). "None" or - "other" are also valid values.

+

The xlink:actuate should be used with the xlink:show to + indicate intended behavior. The xlink:actuate is used to signal intended + behavior with respect to when the remote resource is to appear. The values indicate + whether the resource is to appear automatically when the containing resource is + rendered ("onLoad"), or only after the user requests the resource ("onRequest"). + "None" or "other" are also valid values.

"onLoad" or "onRequest" or "other" or "none"

-
+
xlink:arcrole @@ -7721,20 +8347,21 @@

URI defining the purpose of the link.

-

An absolute URI that describes the nature of the relation between the - entity being described in the EAC-CPF instance and a remote resource (cpfRelation, - resourceRelation, or functionRelation) or the nature of the relation - between the EAC-CPF instance description (or component of description) and the remote - resource (citation, setComponent, andsource). The value of - the attribute should indicate the direction of the relation. It is recommended that the - direction of the relation be from local resource to remote resource.

+

An absolute URI that describes the nature of the relation between the entity being + described in the EAC-CPF instance and a remote resource (cpfRelation, + resourceRelation, or functionRelation) or the nature of the relation + between the EAC-CPF instance description (or component of description) and the remote + resource (citation, setComponent, andsource). The value of + the attribute should indicate the direction of the relation. It is recommended that + the direction of the relation be from local resource to remote resource.

string

-
+
xlink:href @@ -7742,19 +8369,21 @@

Xlink: HREF

-

Contains a URI, possibly relative, pointing to the related resource

+

Contains a URI, possibly relative, pointing to the related + resource

-

The address for a remote resource. The xlink:href takes the - form of a Uniform Resource Identifier (URI). While it is permissible to use a relative URI, - and an absolute URI is recommended.

+

The address for a remote resource. The xlink:href takes the form of a + Uniform Resource Identifier (URI). While it is permissible to use a relative URI, and + an absolute URI is recommended.

anyURI

-
+
xlink:role @@ -7763,18 +8392,18 @@

Identifies the type or nature of the remote resource with an absolute - URI.

+ URI.

-

Identifies the type or nature of the remote resource with an absolute - URI.

+

Identifies the type or nature of the remote resource with an absolute URI.

string

-
+
xlink:show @@ -7782,23 +8411,24 @@

Xlink: Show

-

Used to signal intended behavior with respect to where the remote resource - is to appear when the link is resolved.

+

Used to signal intended behavior with respect to where the remote + resource is to appear when the link is resolved.

-

The xlink:show should be used with the - xlink:actuate to indicate intended behavior. The xlink:show is used to - signal intended behavior with respect to where the remote resource is to appear when the link - is resolved. The values indicate whether the resource is to appear embedded at the point of - the link ("embed"), replace the resource in which it appears ("replace"), or in a new window - ("new"). "None" or "other" are also valid values.

+

The xlink:show should be used with the xlink:actuate to + indicate intended behavior. The xlink:show is used to signal intended + behavior with respect to where the remote resource is to appear when the link is + resolved. The values indicate whether the resource is to appear embedded at the point + of the link ("embed"), replace the resource in which it appears ("replace"), or in a + new window ("new"). "None" or "other" are also valid values.

"embed" or "new" or "replace" or "none" or "other"

-
+
xlink:title @@ -7807,18 +8437,19 @@

Information that may be used as a viewable caption for the remote - resource.

+ resource.

-

Information that serves as a viewable caption that indicates the name or - type of the linked remote source.

+

Information that serves as a viewable caption that indicates the name or type of the + linked remote source.

string

-
+
xlink:type @@ -7826,16 +8457,16 @@

Xlink: Type

-

A fixed value that identifies an XLINK compliant element of a particular - type.

+

A fixed value that identifies an XLINK compliant element of a + particular type.

-

A fixed value that identifies an XLINK compliant element of a particular - type. Only one XLINK type is used in EAC-CPF, "simple." While the attribute is optional in - instances validated against the W3C Schema version of EAC-CPF, the Relax NG version of - EAC-CPF requires it. To support exchange of EAC-CPF instances, it is recommended that the - xlink:type be present in the instance whenever any of the other XLINK attributes - are used.

+

A fixed value that identifies an XLINK compliant element of a particular type. Only + one XLINK type is used in EAC-CPF, "simple." While the attribute is optional in + instances validated against the W3C Schema version of EAC-CPF, the Relax NG version of + EAC-CPF requires it. To support exchange of EAC-CPF instances, it is recommended that + the xlink:type be present in the instance whenever any of the other XLINK + attributes are used.

Fixed value: "simple"

@@ -7851,14 +8482,14 @@

Used to specify a base URI other than the base URI of the EAC-CPF - instance.

+ instance.

-

xml:base is used to specify the base URI other than the base - URI of the EAC-CPF instance, for the purpose of resolving any relative URIs used with - elements that contain one or more descendants that use an attribute of type anyURI. - xml:base makes it possible to declare an absolute base URI to facilitate the use - of relative URIs on the descendants.

+

xml:base is used to specify the base URI other than the base URI of the + EAC-CPF instance, for the purpose of resolving any relative URIs used with elements + that contain one or more descendants that use an attribute of type anyURI. + xml:base makes it possible to declare an absolute base URI to facilitate + the use of relative URIs on the descendants.

NMTOKEN

@@ -7873,19 +8504,19 @@

XML Identifier

-

A unique identifier available on most elements that can be used to name - specific elements in the EAC-CPF instance.

+

A unique identifier available on most elements that can be used to + name specific elements in the EAC-CPF instance.

-

An identifier used to name the element so that it can be referred to, or - referenced from, somewhere else. Each xml:id within a document must have a unique - value. The xml:id attribute regularizes the naming of the element and thus - facilitates building links between it and other resources. For example, the xml:id - may be used to uniquely identify two or more cpfDescription within - multipleIdentities. Uniquely identifying or distinguishing two or more - cpfDescription may be essential or useful in maintenance environments when - relating resources, functions, or corporate bodies, persons, or families to one among two or - more identities represented in one EAC-CPF instance.

+

An identifier used to name the element so that it can be referred to, or referenced + from, somewhere else. Each xml:id within a document must have a unique + value. The xml:id attribute regularizes the naming of the element and thus + facilitates building links between it and other resources. For example, the + xml:id may be used to uniquely identify two or more cpfDescription + within multipleIdentities. Uniquely identifying or distinguishing two or more + cpfDescription may be essential or useful in maintenance environments when + relating resources, functions, or corporate bodies, persons, or families to one among + two or more identities represented in one EAC-CPF instance.

NMTOKEN

@@ -7900,15 +8531,19 @@

XML Language

-

Two-letter language code from the IANA registry as dictated by the W3C specification.

+

Two-letter language code from the IANA registry as dictated by the W3C + specification.

-

The xml:lang may occur on any element intended to contain - natural language content whenever information about the language of the content of this - element and its children are needed. xml:lang should be used when the language of - the element differs from the Language Code declared in the languageCode attribute - on the element language within the control element. The values in the list are taken - from the IANA Registry (http://www.iana.org/assignments/language-subtag-registry). The use of the IANA Registry code for languages in this context is outlined in the W3C specification. The syntax is specified at: http://www.w3.org/International/articles/language-tags/.

+

The xml:lang may occur on any element intended to contain natural language + content whenever information about the language of the content of this element and its + children are needed. xml:lang should be used when the language of the + element differs from the Language Code declared in the languageCode + attribute on the element language within the control element. The + values in the list are taken from the IANA Registry + (http://www.iana.org/assignments/language-subtag-registry). The use of the IANA + Registry code for languages in this context is outlined in the W3C specification. The + syntax is specified at: http://www.w3.org/International/articles/language-tags/.

IANA Registry for language codes.

@@ -7931,18 +8566,15 @@ entityType - nameEntry or nameEntryParallel with authorizedForm - + nameEntry or nameEntryParallel with authorizedForm nameEntryParallel - nameEntry or nameEntryParallel with authorizedForm - + nameEntry or nameEntryParallel with authorizedForm - nameEntry or nameEntryParallel with alternativeForm - + nameEntry or nameEntryParallel with alternativeForm entityId @@ -7960,17 +8592,13 @@ biogHist - place or places - + place or places - legalStatus or legalStatuses - + legalStatus or legalStatuses - function or functions, occupation or occupations - + function or functions, occupation or occupations - mandate or mandates - + mandate or mandates structureOrGenealogy @@ -7984,18 +8612,17 @@ cpfRelation - cpfRelation/objectXMLWrap or objectBinWrap or relationEntry - + cpfRelation/objectXMLWrap or objectBinWrap or + relationEntry cpfRelation cpfRelationType="[value]" - cpfRelation/objectXMLWrap or objectBinWrap or relationEntry - + cpfRelation/objectXMLWrap or objectBinWrap or + relationEntry - cpfRelation/date or dateRange or dateSet - + cpfRelation/date or dateRange or dateSet control @@ -8005,15 +8632,13 @@ recordId - maintenanceAgency/agencyCode and/or agencyName - + maintenanceAgency/agencyCode and/or agencyName conventionDeclaration - maintenanceStatus and publicationStatus - + maintenanceStatus and publicationStatus localControl @@ -8029,15 +8654,16 @@ sources - maintenanceEvent/agent, agentType, eventDescription and eventType - - + maintenanceEvent/agent, agentType, + eventDescription and eventType + resourceRelation - resourceRelation/objectXMLWrap or objectBinWrap or relationEntry - + resourceRelation/objectXMLWrap or objectBinWrap or + relationEntry resourceRelation xlink:role="[value]" @@ -8048,7 +8674,7 @@ resourceRelation/date or dateRange or dateSet - +