cpfTagLibrarySampleWithItalian_FO.xml

<?xml version="1.0" encoding="UTF-8"?>
<?oxygen RNGSchema="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng"
					type="xml"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:eac-cpf="urn:isbn:1-931666-33-4"
	xmlns:exml="http://workaround for xml namespace restriction/namespace"
	xmlns:example="example"
	xmlns:xlink="http://www.w3c.org/1999/xlink">
	<teiHeader>
		<fileDesc>
			<titleStmt>
				<title>Encoded Archival Context—Corporate Bodies, Persons, and Families (EAC-CPF)
					Tag Library</title>
				<respStmt>
					<resp>Prepared and maintained by the </resp>
					<name>Encoded Archival Context Working Group (EACWG) of the Society of American
						Archivists</name>
				</respStmt>
			</titleStmt>
			<editionStmt>
				<edition>Draft</edition>
			</editionStmt>
			<publicationStmt>
				<publisher>Society of American Archivists in collaboration with Staatsbibliothek zu
					Berlin.</publisher>
				<date when="2010"/>
			</publicationStmt>
			<sourceDesc>
				<p>Born digital.</p>
			</sourceDesc>
		</fileDesc>
	</teiHeader>
	<text>
		<front>
			<titlePage xml:lang="eng">
				<!-- one language block -->
				<docTitle>
					<titlePart type="main">Encoded Archival Context—Corporate Bodies, Persons, and
						Families (EAC-CPF) Tag Library</titlePart>
				</docTitle>
				<docEdition>Version 2010 (revised 2010 August)</docEdition>
				<byline>Prepared and maintained by the</byline>
				<docAuthor>Encoded Archival Context Working Group of the Society of American
					Archivists and the</docAuthor>
				<docAuthor>Staatsbibliothek zu Berlin</docAuthor>
				<docImprint>
					<docDate>1 March 2010</docDate>
				</docImprint>
				<note>
					<ref
						target="http://eac.staatsbibliothek-berlin.de/eac-cpf-schema/schema diagram.html"
						>Diagram of W3C Schema</ref>
				</note>
			</titlePage>
			<titlePage xml:lang="ita">
				<!-- one language block -->
				<docTitle>
					<titlePart type="main">Encoded Archival Context—Corporate Bodies, Persons, and
						Families (EAC-CPF): dizionario dei marcatori</titlePart>
				</docTitle>
				<docEdition>Versione 2010 (rivista nell'agosto 2010)</docEdition>
				<byline>Redatta e mantenuta dal</byline>
				<docAuthor>gruppo di lavoro Encoded Archival Context Working Group della Society of
					American Archivists e dalla</docAuthor>
				<docAuthor>Staatsbibliothek zu Berlin</docAuthor>
				<docImprint>
					<docDate>1 marzo 2010</docDate>
				</docImprint>
				<note>
					<ref
						target="http://eac.staatsbibliothek-berlin.de/eac-cpf-schema/schema diagram.html"
						>Diagramma dello Schema W3c</ref>
				</note>
			</titlePage>
			<div xml:lang="eng" xml:id="eng">
				<!-- one language block -->
				<div xml:id="DedicationEng">
					<head>Dedication</head>
					<p>The Encoded Archival Context Working 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. </p>
				</div>
				<div xml:id="RRNeng">
					<head>Release and Revision Notes</head>
					<p>The EAC-CPF Tag Library should be considered a living document. As such, it
						will continue to be developed as users suggest areas in need of
						clarification or expansion. The EAC Working Group 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 Chair of the EAC
						Working Group, Katherine M. Wisser (<ref target="mailto:wisser@simmons.edu"
							>wisser [at] simmons.edu</ref>).</p>
					<p>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.</p>
					<p>A PDF version of the Tag Library will also be released at a later date.</p>
				</div>
				<div xml:id="backeng">
					<head>Background</head>
					<p>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
						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 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.</p>
					<p>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.</p>
					<p>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).</p>
					<p>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 (<ref
							target="http://www.library.yale.edu/eac/torontotenets.htm"
							>http://www.library.yale.edu/eac/torontotenets.htm</ref>), 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 in August to November 2009, and the
						completed schema was released in March 2010. The Working Group is indebted
						to archivists throughout the international community for their input,
						review, and testing of the schema during its development phase.</p>
					<p>Archival description includes information about the content, intellectual and
						physical attributes of the material, as well as information about the
						context of their creation and use. The context of the creation and use of
						material is 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 agents responsible for the creation or use of material, usually
						organizations or persons. With information about these agents, users can
						understand and interpret the records more fully since they will know the
						context within which the agents operated and created and/or used the
						material. Contextual information about these agents 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.</p>
					<p>Encoded Archival Context – Corporate Bodies, Persons, and Families (EAC-CPF)
						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 agents to enable the
						sharing, discovery and display of this information in an electronic
						environment. It supports the linking of information about one agent to other
						agents to show/discover the relationships amongst record-creating entities
						and the linking to descriptions of records and other contextual
						entities.</p>
					<p>EAC-CPF is a communication structure for archival contextual information for
						individuals, corporate bodies and families. It 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),
						2003, 15). 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).</p>
					<p>Based upon the Toronto Tenets, established in 2001, the following have
						informed the development of the schema: <list type="ordered">
							<head>Definitions and Uses</head>
							<item n="1">Archival 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 the persons,
								organizations, and families (agents) who have been the creators,
								users, or subjects of records, as well as the relationships amongst
								them.</item>
							<item n="2">Context information about agents 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.</item>
							<item n="3">The recording of context information about agents in
								archival information systems directly supports a more complete
								description and understanding of records, as well as the provenance
								approach to retrieval of these records across time and
								domains.</item>
							<item n="4">Context information about agents can also have value as an
								independent information resource, separate from its use in
								supporting the description, retrieval, and interpretation of
								records.</item>
							<item n="5">This model is also intended to support the exchange and
								sharing of context information about agents, especially in those
								instances where repositories have holdings or interests that have
								context information in common.</item>
						</list>
						<list type="ordered">
							<head>Structure and Content</head>
							<item n="6">Each instance of context information about agents describes
								a single entity.</item>
							<item n="7">The model provides a framework within which the full range
								and depth of context information about agents can be recorded and
								suggests a minimum set of elements for describing an entity, but
								defers recommendations for the appropriate use of other elements to
								application guidelines developed for specific
								implementations.</item>
							<item n="8">The model defines a universe of elements used to describe
								agents and the structure of interrelationships amongst those
								elements. These elements and structure support the discovery,
								navigation and presentation of context information about agents and
								the linking of that information to descriptions of archival material
								or to other contextual entities, especially those encoded according
								to EAD, MARC, and similar standards.</item>
							<item n="9">The model supports the linking of descriptions of contextual
								entities to digital or other surrogate representations of those
								entities.</item>
						</list>
						<list type="ordered">
							<head>Technical Issues</head>
							<item n="10">The model is expressed as an XML language to encourage
								platform independence and portability of information. The model may
								also be implemented using other approaches.</item>
						</list>
					</p>
				</div>
				<div xml:id="concepteng">
					<head>EAC-CPF Concepts</head>
					<p>Agents are complex. For example, one agent can consist of multiple
						identities, or a single identity can be associated with several different
						agents. This fact necessitates the structure of this standard to account for
						the various ways in which agents can be expressed. In order to accommodate
						the variety of agents, several concepts are defined:</p>
					<list type="simple">
						<item>SINGLE IDENTITY: one person (or corporate body or family) with a
							single identity represented in one EAC-CPF instance. (Most
							common)</item>
						<item>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. (Less common though not rare).</item>
						<item>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. (Less common though not rare).</item>
						<item>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.</item>
						<item>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. (Rare).</item>
					</list>
					<p>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 description of identity 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.</p>
					<p>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.</p>
				</div>
				<div xml:id="overvieweng">
					<head>Overview of EAC-CPF Structure and Semantics</head>
					<div xml:id="oengintro">
						<head>Introduction</head>
						<p>Each EAC-CPF document contains two mandatory elements, the
								<tag>control</tag> element and either the element
								<tag>cpfDescription</tag> or <tag>multipleIdentities</tag>. The
								<tag>control</tag> element contains data used in the control of the
							entity description, and to provide context for that description.
								<tag>cpfDescription</tag> contains information on the name
							structures, descriptive elements, and relationships.
								<tag>multipleIdentities</tag> is used when there is more than one
								<tag>cpfDescription</tag>. These two wrapper elements contain
							specific elements to support the functional intentions of the parent or
							containing element.</p>
					</div>
					<div xml:id="controleng">
						<head>
							<tag>control</tag>
						</head>
						<p>The <tag>control</tag> element contains the following subelements:</p>
						<list type="simple">
							<item>
								<tag>recordId</tag> - EAC-CPF Identifier. Contains one or more
								unique identifiers for the EAC-CPF instance. Required.</item>
							<item>
								<tag>maintenanceAgency</tag> - Maintenance Agency. Name and coded
								information about the institution or service responsible for the
								creation, maintenance, and/or dissemination of the EAC-CPF instance.
								Required.</item>
							<item>
								<tag>maintenanceStatus</tag> - Maintenance Status. Contains the
								current drafting status of the EAC-CPF instance. Values include:
								new, revised, deleted, cancelled, deletedSplit, or deletedReplaced.
								Required.</item>
							<item>
								<tag>maintenanceHistory</tag> - Maintenance History. Contains
								information about the date, type and events within the life cycle of
								an EAC-CPF instance. Contains one or more
									<tag>maintenanceEvent</tag> 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. Required.</item>
							<item>
								<tag>publicationStatus</tag> - Publication Status. Contains
								information about the editorial status of the EAC-CPF instance.
								Optional. </item>
							<item>
								<tag>languageDeclaration</tag> - Language Declaration. Contains
								coded and natural language information about the language of the
								EAC-CPF instance. Required.</item>
							<item>
								<tag>sources</tag> - Sources. Contains information about the sources
								consulted in creating the description of the entity or entities in
								the EAC-CPF instance. Contains one or more <tag>source</tag>
								element. Required.</item>
							<item>
								<tag>conventionDeclaration</tag> - Convention Declaration. Contains
								information on the rules used to construct the EAC-CPF instance, in
								particular the names formed in <tag>identity</tag> and the
								controlled vocabularies and thesauri used in the EAC-CPF instance.
								Optional.</item>
							<item>
								<tag>otherRecordId</tag> - Other Record Identifier. An element that
								allows the recording of additional identifiers that may be
								associated with the EAC-CPF instance. Optional.</item>
							<item>
								<tag>localControl</tag> - Local Control. An element in which to
								record any control entries necessary due to local practice that are
								not represented by the other elements in <tag>control</tag>.
								Optional.</item>
							<item>
								<tag>localTypeDeclaration</tag> - Local Type Declaration. An element
								used to declare local conventions used in the <att>localType</att>
								attribute. </item>
						</list>
					</div>
					<div xml:id="desceng">
						<head>
							<tag>cpfDescription</tag>
						</head>
						<p>The <tag>cpfDescription</tag>-Corporate body, person or family
							description, comprises the description of the entity. Similar to the
								<tag>control</tag> element, <tag>cpfDescription</tag> has several
							complex subelements used to describe different features of the
							entity:</p>
						<list type="simple">
							<item>
								<tag>identity</tag> - Identity. Complex structure containing the
								name or names used by the entity over the course of the entity’s
								existence. Contains a repeatable <tag>nameEntry</tag> element for
								different names, and a repeatable <tag>nameEntryParallel</tag>
								element for more than one <tag>nameEntry</tag> expressed in
								different languages. Required.</item>
							<item>
								<tag>description</tag> - Description. Contains formal description
								elements parallel to those in ISAAR (CPF) for the description of the
								entity. An additional <tag>localDescription</tag> allows for local
								implementation of additional descriptive information not included in
								the other <tag>description</tag> elements. Optional.</item>
							<item>
								<tag>relations</tag> - Relations. Contains one or more references to
								or descriptions of related corporate bodies, persons or families
									<tag>cpfRelation</tag>, functions <tag>functionRelation</tag>,
								or resources <tag>resourceRelation</tag>. Optional.</item>
							<item>
								<tag>alternativeSet</tag> - Alternative set. Contains two or more
								authority records for the same entity derived from two or more
								authority systems, expressed within a single EAC-CPF instance. The
									<tag>alternativeSet</tag> consists of two or more
									<tag>setComponent</tag> elements for the authority records.
								Optional.</item>
						</list>
					</div>
					<div xml:id="identityeng">
						<head>
							<tag>identity</tag>
						</head>
						<p>The most complex element in the EAC-CPF schema is the <tag>identity</tag>
							element. In addition to needing to accommodate one or more names used
							for or by the entity, <tag>identity</tag> must accommodate two or more
							parallel names in different languages 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 <tag>identity</tag>
							contains a required <tag>entityType</tag> and one or more
								<tag>nameEntry</tag> and/or <tag>nameEntryParallel</tag> elements.
							It also includes an optional <tag>entityId</tag> and
								<tag>descriptiveNote</tag>. The <tag>nameEntry</tag> element is
							constructed of one or more <tag>part</tag> elements and contains the
							attributes <att>scriptCode</att>, <att>xml:lang</att>,
								<att>transliteration</att>, and <att>localType</att> to provide
							precision about the language and script of the names if desired. It
							includes an optional <tag>useDates</tag> element to identify dates of
							use of a name. <tag>nameEntryParallel</tag>, which is intended for use
							when the same name is expressed in different languages, contains one or
							more <tag>nameEntry</tag> elements and an optional <tag>useDates</tag>
							element. For example, within the context of the Archive of Ontario,
							parallel French and English headings can be designated by placing the
							repository name of the Archive in two parallel <tag>nameEntry</tag>
							elements, with the two different headings being distinguished by the
							values in the <att>xml:lang</att>.</p>
						<p>Within <tag>identity</tag>, names represented through
								<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> may be selected
							as authorized or variant names. The <tag>authorizedForm</tag> and
								<tag>alternativeForm</tag> elements are available within
								<tag>nameEntry</tag> and <tag>nameEntryParallel</tag> 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 <tag>nameEntryParallel</tag>, a single
								<tag>nameEntry</tag> may be preferred over others. A
								<tag>preferredForm</tag> 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.</p>
					</div>
					<div xml:id="descreng">
						<head>
							<tag>description</tag>
						</head>
						<p>The <tag>description</tag> element accommodates a variety of both
							controlled and prose descriptions of 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,
								<tag>function</tag> would be used for a single function term,
								<tag>functions</tag> will bundle more than one function descriptor
							or alternatively, it will allow a discursive description. Most elements
							within <tag>description</tag> include an optional
								<tag>descriptiveNote</tag> element to provide explanatory text. All
							elements within <tag>description</tag> are optional. Elements for
							description include:</p>
						<list type="simple">
							<item>
								<tag>existDates</tag> — Dates of Existence. Contains dates of
								existence of the entity being described. Can include actual or
								approximate dates, using either <tag>date</tag>,
									<tag>dateRange</tag>, or <tag>dateSet</tag>.</item>
							<item>
								<tag>place</tag> — Place. Includes relevant location information,
								optionally paired with related date information. Includes elements
									<tag>placeEntry</tag> and <tag>placeRole</tag> and the range of
								possibilities with date information: <tag>date</tag>,
									<tag>dateRange</tag>, <tag>dateSet</tag>.</item>
							<item>
								<tag>localDescription</tag> — Local Description. An element intended
								to extend the descriptive categories available in a local system.
								Includes a <tag>term</tag> element and the range of possibilities
								with date information: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>legalStatus</tag> — Legal Status. Includes the legal status of
								a corporate body, typically defined by authorities and granted by
								either a government or an authorized agency. Includes a
									<tag>term</tag> element and the range of possibilities with date
								information: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>function</tag> — Function. Includes relevant functions,
								processes, activities, tasks, or transactions performed by the
								entity being described. Includes a <tag>term</tag> element and the
								range of possibilities with date information: <tag>date</tag>,
									<tag>dateRange</tag>, <tag>dateSet</tag>.</item>
							<item>
								<tag>languageUsed</tag> — Language Used. Indicates the language and
								script in which the entity being described was creative or
								productive. Includes elements <tag>language</tag> and
									<tag>script</tag>. </item>
							<item>
								<tag>occupation</tag> — Occupation. Includes relevant occupations
								held by the entity being described. Includes a <tag>term</tag>
								element and the range of possibilities with date information:
									<tag>date</tag>, <tag>dateRange</tag>,
								<tag>dateSet</tag>.</item>
							<item>
								<tag>mandate</tag> — Mandate. Includes relevant mandates for
								corporate bodies being described. Includes a <tag>term</tag> element
								and the range of possibilities with date information:
									<tag>date</tag>, <tag>dateRange</tag>,
								<tag>dateSet</tag>.</item>
							<item>
								<tag>structureOrGenealogy</tag> — Structure or Genealogy. Includes
								information about the structure of a corporate body or the genealogy
								of a person or family. Includes elements <tag>outline</tag>,
									<tag>list</tag>, and <tag>p</tag> to assist in structuring the
								text.</item>
							<item>
								<tag>generalContext</tag> — General Context. Includes information
								about the general social and cultural context of the entity being
								described. Includes a <tag>term</tag> element and the range of
								possibilities with date information: <tag>date</tag>,
									<tag>dateRange</tag>, <tag>dateSet</tag>.</item>
							<item>
								<tag>biogHist</tag> — Biographical or Historical Note. Includes
								discursive text providing biographical and/or historical information
								about the entity being described. Includes an <tag>abstract</tag>
								element for a brief synopsis of the full content; a
									<tag>chronList</tag> element allows for structured date, event
								and optional place information. Includes <tag>list</tag>,
									<tag>outline</tag>, <tag>p</tag> elements to assist in
								structuring the text.</item>
						</list>
						<p> All elements in <tag>description</tag> provide a <att>localType</att>
							attribute to provide semantic specificity to the term being used. With
							the exception of <tag>existDates</tag>, <tag>structureOrGenealogy</tag>,
								<tag>generalContext</tag>, and <tag>biogHist</tag>, plural form
							wrapper elements are available to bundle multiple occurrences of these
							elements. These wrapper elements also include elements
								<tag>citation</tag>, <tag>list</tag>, <tag>outline</tag>, and
								<tag>p</tag> to accommodate greater complexity in representing the
							description being created.</p>
					</div>
					<div xml:id="relationeng">
						<head>
							<tag>relations</tag>
						</head>
						<p>As a component of archival description, entity description must be
							brought into relation with the other descriptive components. Entity
							descriptions must be dynamically related to the record descriptions for
							which they provide context, and the functions and activities in which
							the entities 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. Entities are related to other
							entities, to activities and functions, and to records. Similarly,
							activities and functions are related to other functions and activities,
							to creators, and to records; and records are related to other records,
							to entities, and to functions and activities. Each entity, record, or
							function/activity description can thus function as a node in a set of
							relations.</p>
						<p>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 occupations 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.</p>
						<p>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
							entity, 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.</p>
						<p>There are three elements for describing relations with other descriptive
							entities that are included in the <tag>relations</tag> element:
								<tag>cpfRelation</tag>, <tag>functionRelation</tag>,
								<tag>resourceRelation</tag>. Within each of these relations
							elements, there are: <tag>relationEntry</tag>, <tag>objectXMLWrap</tag>,
								<tag>objectBinWrap</tag>, <tag>date</tag>, <tag>dateRange</tag>,
								<tag>dateSet</tag>, <tag>placeEntry</tag> and
								<tag>descriptiveNote</tag> elements. Individual relations include
							optional attributes related to the type of relation that is being
							described. These include:</p>
						<list type="simple">
							<item>
								<tag>cpfRelation</tag> — includes an attribute
									<att>cpfRelationType</att>; values are identity, hierarchical,
								hierarchical-parent, hierarchical-child, temporal, temporal-earlier,
								temporal-later, family, associative.</item>
							<item>
								<tag>functionRelation</tag> — includes an attribute
									<att>functionRelationType</att>; values include controls, owns,
								performs.</item>
							<item>
								<tag>resourceRelation</tag> — includes an attribute
									<att>resourceRelationType</att>; values include creatorOf,
								subjectOf, other.</item>
						</list>
						<p>Other attributes available for the relation elements include
								<att>lastDateTimeVerified</att>, and the suite of simple Xlink
							attributes.</p>
						<p>There are two principal rationales behind the primitive or basic 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
							primitives 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.</p>
					</div>
					<div xml:id="xlinkeng">
						<head>xlink</head>
						<p>The EAC-CPF schema includes support for linking to external resources
							using a limited subset of the xlink standard, which is defined at <ref
								target="http://www.w3.org/TR/xlink/"
								>http://www.w3.org/TR/xlink/</ref>. 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 which are
							supported by @cpfRelationType, @functionRelationType, and
							@resourceRelationtype. The xlink attributes are available on the
							following elements: <tag>citation</tag>, <tag>cpfRelation</tag>,
								<tag>functionRelation</tag>, <tag>resourceRelation</tag>,
								<tag>setComponent</tag>, and <tag>source</tag>.</p>
						<p>A more complete description of each 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.</p>
						<list type="simple">
							<head>Xlink Type Attribute</head>
							<item>
								<att>xlink:type</att> — 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.</item>
						</list>
						<list type="simple">
							<head>Locator Attribute</head>
							<item>
								<att>xlink:href</att> — This optional element may be used to provide
								the location of the resource that is being linked to. The link must
								be a valid URI.</item>
						</list>
						<list type="simple">
							<head>Semantic Attributes</head>
							<item>
								<att>xlink:arcrole</att> — This optional element may be used on
									<tag>cpfRelation</tag>, <tag>functionRelation</tag>, and
									<tag>resourceRelation</tag> to provide a precise description of
								the relationship between the entity described in the EAC-CPF
								resource and the resource to which it is linked. When used on
									<tag>citation</tag>, <tag>setComponent</tag>,
									and<tag>source</tag>, 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.</item>
							<item>
								<att>xlink:role</att> — This optional element 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 <tag>resourceRelation</tag>, as described in ISAAR (CPF)
								6.2. The value provided must be a valid URI.</item>
						</list>
						<list type="simple">
							<head>Link Behavior Attributes </head>
							<item>
								<att>xlink:actuate</att> — 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.</item>
							<item>
								<att>xlink:show</att> — 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.</item>
							<item>
								<att>xlink:title</att> — This optional element may be used to
								provide a caption or title that an external system or application
								may use when presenting a link to the user.</item>
						</list>
						<p>Mozilla-based browsers such as Firefox are the only common client
							application which include native support for a limited range of xlink
							attributes. As a result, 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 <ref
								target="http://www.snee.com/xml/xlink/sxlinkdemo.xml"
								>http://www.snee.com/xml/xlink/sxlinkdemo.xml</ref>.</p>
						<p>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:</p>
						<egXML xmlns="http://www.tei-c.org/ns/Examples">
							<eac-cpf:cpfRelation cpfRelationType="family" xlink:actuate="onRequest"
								xlink:arcrole="http://library.illinois.edu/archives/eac-cpfRelations.html#spouseOf"
								xlink:href="http://library.illinois.edu/archives/archon/index.php?p=creators/creator&amp;id=546"
								xlink:show="new" xlink:type="simple">
								<eac-cpf:relationEntry>Gregory, John Milton</eac-cpf:relationEntry>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>John Milton Gregory was the husband of Louisa Allen
										Gregory.</eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:cpfRelation>
							<eac-cpf:resourceRelation resourceRelationType="creatorOf"
								xlink:role="http://library.illinois.edu/archives/eac-cpfRelations.html#collector"
								xlink:type="simple">
								<eac-cpf:relationEntry>Collezione Fortunato Depero (Polo culturale e
									Galleria Museum Depero, Roverto</eac-cpf:relationEntry>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>ITA MART, Collezione Depero, Collezione d'arte,
										1919-1959, Creatore della collezione, </eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:resourceRelation>
						</egXML>
						<!-- perhaps an example of xlink:role on <resourceRelation> would be good. -->
						<!-- Added, but don't think that it's right; I was thinking of the distinction that might want to be made between an author, a collector, an editor, etc. all under the umbrella of resourceRelationtype="creatorOf" -->
						<p>The vocabulary at purl.org which is 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 <tag>cpfRelation</tag>, <tag>resourceRelation</tag>, and
								<tag>functionRelation</tag> elements. Such vocabularies could be
							maintained locally, nationally, or even internationally, perhaps as a
							continuation of the work of the EAC working group.</p>
					</div>
					<div xml:id="localtypeeng">
						<head>
							<att>localType</att>
						</head>
						<p>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).</p>
						<p>In addition to the element <tag>localDescription</tag>, described above,
							many elements may also be qualified with <att>localType</att>. 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.</p>
					</div>
				</div>
				<div xml:id="resourceeng">
					<head>Resources</head>
					<list type="simple">
						<item>International Council on Archives. International Standard Archival
							Authority Record for Corporate bodies, Persons, and Families. 2nd
							Edition. 2003. <ref
								target="http://www.icacds.org.uk/eng/ISAAR(CPF)2ed.pdf"
								>http://www.icacds.org.uk/eng/ISAAR(CPF)2ed.pdf</ref>.</item>
						<item>International Council on Archives. General International Standard
							Archival Description. 2nd Edition. 1999. <ref
								target="http://www.ica.org/sites/default/files/isad_g_2e.pdf"
								>http://www.ica.org/sites/default/files/isad_g_2e.pdf</ref>.</item>
					</list>
				</div>
			</div>
			<div xml:lang="ita" xml:id="ita">
				<!-- one language block -->
				<div xml:id="dedica">
					<head>Dedica</head>
					<p>Il gruppo di lavoro su Encoded Archival Context dedica lo Schema e il
						dizionario dei marcatori di EAC-CPF 2010 alla memoria di Per-Gunnar
						Ottosson. P-G (come era noto ai suoi molti amici sparsi nel mondo), ha avuto
						un ruolo chiave nella messa a punto di molti standard archivistici
						internazionali. Ha svolto un ruolo cruciale nei primissimi passi di EAC, ma
						la sua malattia e la conseguente morte nel 2008 gli hanno impedito di vedere
						la conclusione del lavoro su EAC-CPF. Sarà ricordato per la sua acuta
						intelligenza, la sua abilità di collaborare e il suo splendido spirito. Ma,
						soprattutto, sarà affettuosamente ricordato come amico. </p>
				</div>
				<div xml:id="nrr">
					<head>Note di rilascio e revisione</head>
					<p>Il dizionario dei marcatori di EAC-CPF deve essere considerato un documento
						dinamico. In questo senso, continuerà a essere sviluppato in risposta ai
						suggerimenti degli utenti di chiarificazione o integrazione. Il gruppo di
						lavoro su EAC incoraggia gli implementatori a riportare qualsiasi domanda,
						commento o suggerimento sul dizionario dei marcatori e sul suo contenuto.
						Inoltre è fortemente incentivato il contributo con esempi. Domande, commenti
						o esempi possono essere indirizzati al presidente del gruppo di lavoro su
						EAC, Katherine M. Wisser (wisser [at] simmons.edu).</p>
					<p>Il dizionario dei marcatori è codificato in TEI P5, la codifica è strutturata
						per facilitare l'inclusione della documentazione nello Schema XML, in modo
						da fornire una guida contestuale negli editor XML. Sebbene il rilascio
						iniziale del dizionario dei marcatori sia solo in inglese, la codifica è
						disegnata per facilitare la messa a disposizione in parallelo di dizionari
						dei marcatori in altre lingue, eventualmente tradotti successivamente.</p>
					<p>Una versione PDF del dizionario dei marcatori sarà rilasciata in seguito.</p>
				</div>
				<div xml:id="contesto">
					<head>Contesto</head>
					<p>La storia di EAC iniziò nel 1998 con lo sforzo di Richard Szary, Wendy Duff e
						Daniel Pitti di immaginarsi uno standard per codificare e scambiare
						informazioni autorevoli sul contesto dei materiali archivistici. Il
						risultato della ricerca avrebbe fornito uno standard di comunicazione per
						scambiare record di autorità basati sullo Standard internazionale per i
						record d'autorità archivistici di enti, persone, famiglie (ISAAR(CPF)) e
						sarebbe stata speculare allo standard per codificare record di strumenti di
						corredo archivistici, che era stato fissato precedentemente con Encoded
						Archival Description (EAD). Come EAD aveva consentito l'espressione pratica
						dello standard generale internazionale per la descrizione archivistica
						(ISAD(G)), il nuovo standard avrebbe permesso l'espressione di ISAAR(CPF).
						Questo standard parallelo avrebbe così preservato e rafforzato il dualismo
						essenziale che caratterizza la descrizione archivistica quando è presentata
						in uno strumento di corredo archivistico.</p>
					<p>Uno standard separato avrebbe inoltre aperto la strada all'eliminazione di
						qualche problema pratico riscontrato nell'uso di EAD, che era stato
						sviluppato come una soluzione onnicomprensiva per codificare strumenti di
						corredo standalone (cartacei) che includevano la totalità dei dati
						descrittivi sui record archivistici, seguendo il modello di presentazione
						allora predominante. Poiché il materiale di una singola entità o su una
						singola entità può essere trovato in diversi fondi o in molti archivi, si
						rischia di incorrere in un enorme sforzo ridondante nel registrare
						informazioni sulla stessa entità. Inoltre questo lavoro duplicato può
						sfociare in gravi inconsistenze che intralciano sia gli utenti, nella
						ricerca e nell'interpretazione dei materiali, sia gli archivisti, nella
						creazione di riferimenti accurati e completi su queste entità.</p>
					<p>L'Università di Yale ospitò un incontro internazionale nel 1998. L'incontro
						fu organizzato da Richard Szary e finanziato dalla Digital Library
						Federation. Gli obiettivi dell'incontro erano quelli di pianificare il
						finanziamento e lo sviluppo di uno standard per la codifica basato su
						ISAAR(CPF)</p>
					<p>Nel 2001, con l'assistenza finanziaria della Gladys Krieble Delmas
						Foundation, un secondo gruppo internazionale di lavoro si incontrò a
						Toronto. Questo incontro produsse i Principi di Toronto (Toronto Tenets, si
						veda <ref target="http://www.library.yale.edu/eac/torontotenets.htm"
							>http://www.library.yale.edu/eac/torontotenets.htm</ref>), , principi
						che diedero forma allo standard proposto. Il gruppo stabilì inoltre gli
						obiettivi dello standard, programmò a grandi linee i parametri della
						Document Type Definition (DTD) e stabilì un gruppo di lavoro per creare una
						sintassi completa. La DTD raggiunse lo stato di Beta nel 2004, iniziando
						così una lunga fase di test mentre veniva applicata in diversi progetti
						europei e americani. Sulla base dei risultati provenienti da questi banchi
						di prova, nel 2007 fu formato il gruppo di lavoro sull'Encoded Archival
						Context della Society of American Archivists con lo scopo di portare avanti
						il lavoro verso la creazione di una versione standardizzata espressa in uno
						schema e in un dizionario dei marcatori. Grazie al supporto della Gladys
						Krieble Delmas Foundation, dell'IBC (Istituto per i Beni artistici culturali
						e naturali) della Regione Emilia-Romagna, dell'Archivio di Stato di Bologna,
						di OCLC Research e della National Library of Australia, il gruppo di lavoro
						su EAC si incontrò per tre giorni a Bologna (Italia) nel maggio 2008 per
						gettare le fondamenta dell'attuale standard EAC-CPF. Il lavoro iniziato a
						Bologna proseguì con un continuo scambio di e-mail e attraverso chiamate in
						conferenza telefonica. La bozza conclusiva fu sottoposta a commenti pubblici
						dall'agosto al novembre 2009 e lo schema completo è stato rilasciato nel
						marzo 2010. Il gruppo di lavoro è grato agli archivisti di tutta la comunità
						internazionale per i loro suggerimenti, commenti e test effettuati sullo
						schema durante la fase di sviluppo.</p>
					<p>La descrizione archivistica include parallelamente sia informazioni sul
						contenuto e sugli elementi fisici e intellettuali della documentazione, sia
						informazioni sul contesto della loro produzione e uso. Questo contesto di
						produzione e uso dei materiali è complesso e a molti livelli e può
						coinvolgere individui, famiglie, organizzazioni, società, funzioni,
						attività, operazioni commerciali, luoghi geografici, eventi e altre entità.
						Primi, fra tutte queste entità, sono gli agenti responsabili della
						produzione o dell'uso della documentazione: generalmente organizzazioni e
						persone. Con le informazioni su questi agenti gli utenti possono comprendere
						e interpretare i record descrittivi nella loro pienezza, visto che possono
						conoscere il contesto entro cui questi agenti hanno operato, prodotto o
						usato la documentazione. Le informazioni di contesto su questi agenti
						possono essere utilizzate sia come componenti all'interno di un approccio
						descrittivo che integri completamente le informazioni di contesto
						all'interno dei prodotti descrittivi, come è stato tradizionalmente fatto
						negli archivi, sia in un sistema indipendente che sia collegato agli altri
						sistemi e prodotti descrittivi focalizzati sul contenuto.</p>
					<p>Encoded Archival Context – Corporate Bodies, Persons, and Families (EAC-CPF)
						(Il contesto archivistico codificato – Enti, persone e famiglie) affronta la
						descrizione degli individui, delle famiglie e degli enti che producono,
						conservano, usano, sono responsabili o sono associati con i record
						descrittivi in una varietà di modi. Nel tempo, altre tipologie di entità di
						contesto potrebbero svilupparsi sotto l'ampio ombrello di EAC, ma al momento
						lo scopo è in primo luogo standardizzare la codifica delle descrizioni sugli
						agenti per permettere lo scambio, la ricerca e la visualizzazione di queste
						informazioni all'interno di sistemi informativi. EAC supporta sia il
						collegamento delle informazioni relative a un agente con altri agenti per
						evidenziare/ricercare le relazioni tra le entità produttrici di
						documentazione, sia il collegamento con le descrizioni dei materiali
						archivistici o di altre entità di contesto. </p>
					<p>EAC-CPF è uno schema per la trasmissione di informazioni sul contesto
						archivistico di individui, enti e famiglie. Facilita lo scambio di record di
						autorità conformi a ISAAR(CPF). ISAAR(CPF) "stabilisce la tipologia di
						informazioni che possono essere incluse in un record d’autorità archivistico
						e fornisce una guida su come tali record possano essere disposti all’interno
						di un sistema di descrizioni archivistiche." ISAAR(CPF) sottolinea inoltre
						che "[u]n efficace scambio automatico di informazioni d’autorità relative ad
						archivi attraverso le reti telematiche dipende dall’adozione, da parte delle
						istituzioni archivistiche coinvolte, di un adeguato formato di
						comunicazione. L’Encoded Archival Context (EAC) è un formato di
						comunicazione che rende possibile lo scambio di record d’autorità
						archivistici conformi ad ISAAR (CPF) attraverso il World Wide Web" (ISAAR
						(CPF), 2003, 15). EAC-CPF fornisce uno strumento che permette la piena
						espressione di ISAAR (CPF), ma, in ogni caso, può contenere anche qualche
						elemento aggiuntivo o accorgimento tecnico non previsto all'interno di ISAAR
						(CPF). </p>
					<p>Sulla base dei Principi di Toronto, stabiliti nel 2001, i seguenti
						presupposti hanno guidato lo sviluppo dello schema: <list type="ordered">
							<head>Definizioni e usi</head>
							<item n="1">Le informazioni archivistiche di contesto consistono in
								informazioni che descrivono le circostanze sotto cui il materiale
								archivistico è stato prodotto, mantenuto e utilizzato. Questo
								contesto include, ma non si limita esclusivamente a questo, sia
								l'identificazione e le caratteristiche delle persone, organizzazioni
								e famiglie (agenti) che sono stati produttori, utilizzatori o
								soggetti dei documenti archivistici, sia le relazioni che
								intercorrono fra di loro.</item>
							<item n="2">Le informazioni di contesto sugli agenti non sono dati che
								descrivono altre risorse informative, piuttosto sono i dati che
								descrivono le entità che sono parte dell'ambiente in cui queste
								risorse informative (i.e. i documenti archivistici) sono
								esistiti.</item>
							<item n="3">La registrazione delle informazioni di contesto sugli agenti
								nei sistemi informativi archivistici favorisce direttamente una
								descrizione e comprensione maggiormente completa della
								documentazione archivistica, favorendo allo stesso tempo un
								approccio basato sulla provenienza per reperire questi documenti
								contestualizzati nel tempo e dominio di produzione. </item>
							<item n="4">Le informazioni di contesto sugli agenti possono inoltre
								aver valore come risorse informative indipendenti, scisse dall'uso
								per supportare e completare la descrizione, il reperimento e
								l'interpretazione della documentazione archivistica.</item>
							<item n="5">Questo modello è inoltre volto a supportare lo scambio e la
								condivisione di informazione di contesto sugli agenti, soprattutto
								nei casi di repository che abbiano informazioni di contesto in
								comune.</item>
						</list>
						<list type="ordered">
							<head>Structure and Content</head>
							<item n="6">Ogni istanza delle informazioni di contesto sugli agenti
								descrive una singola entità.</item>
							<item n="7">Il modello fornisce una struttura entro cui l'intera gamma
								delle informazioni di contesto sugli agenti può essere registrata e
								indica un set minimo di elementi per descrivere un'entità, ma rinvia
								le raccomandazioni sull'appropriato uso di altri elementi a linee
								guida applicative sviluppate per specifiche realizzazioni. </item>
							<item n="8">Il modello definisce un universo di elementi usati per
								descrivere gli agenti e la struttura delle relazioni fra questi
								elementi. Questi sono volti a favorire la ricerca, navigazione e
								presentazione delle informazioni di contesto sugli agenti e il
								collegamento di queste informazioni con le descrizioni dei materiali
								archivistici o con altre informazioni di contesto, in modo
								particolare con quelle codificate in EAD, MARC o altri standard
								simili. </item>
							<item n="9">Il modello supporta il collegamento delle descrizioni delle
								entità di contesto con le rappresentazioni digitali o altri
								surrogati di queste entità.</item>
						</list>
						<list type="ordered">
							<head>Questioni tecniche</head>
							<item n="10">Questo modello è espresso come linguaggio di marcatura XML
								per favorire l'indipendenza da piattaforme e la portabilità delle
								informazioni. Il modello potrebbe comunque essere implementato
								utilizzando altri approcci.</item>
						</list>
					</p>
				</div>
				<div xml:id="conceptsita">
					<head>EAC-CPF Concepts</head>
					<p>Gli agenti sono oggetti complessi. Ad esempio, un agente può essere composto
						da identità multiple o una singola identità può essere associata a diversi
						agenti. Questa esigenza impone che la struttura dello standard renda conto
						dei modi diversi in cui gli agenti possono essere espressi. Allo scopo di
						gestire la varietà di agenti, sono definiti alcuni concetti:</p>
					<list type="simple">
						<item>IDENTITÀ SINGOLA (SINGLE IDENTITY): una persona (o ente o famiglia)
							con una singola identità rappresentata in un singolo documento EAC-CPF.
							(Caso più comune). </item>
						<item>IDENTITÀ MULTIPLA - MOLTI IN UNO (MULTIPLE IDENTITY-MANY IN ONE): due
							o più identità (includendo identità ufficiali) ognuna rappresentata da
							una distinta descrizione archivistica all'interno di un singolo
							documento EAC-CPF. Può essere convertita informaticamente in un'identità
							multipla - una in molti. (Caso meno comune del precedente, ma non raro). </item>
						<item>IDENTITÀ MULTIPLA - UNA IN MOLTI (MULTIPLE IDENTITY-ONE IN MANY): due
							o più identità (includendo identità ufficiali) ognuna rappresentata da
							una o più documenti EAC-CPF collegati. Può essere convertita
							informaticamente in un'identità multipla - molti in uno. (Caso meno
							comune dell'identità singola, ma non raro). </item>
						<item>GRUPPO DI ALTERNATIVE (ALTERNATIVE SET): un documento EAC-CPF derivato
							che è basato, incorporandole, su due o più istanze EAC-CPF alternative
							per la stessa entità. Può essere usato da consorzi o come strumento per
							fornire un unico accesso a record di autorità mantenuti in due o più
							sistemi da due o più differenti agenzie. Le istanze alternative EAC-CPF
							possono essere sia in lingue differenti sia nella stessa lingua. </item>
						<item>IDENTITÀ COLLABORATIVE (IDENTITY COLLABORATIVE: una singola identità
							condivisa da due o più persone (i.e. pseudonimi condivisi usati nella
							creazione di lavoro collaborativi). In questo caso si utilizza
							l'identità multipla una in molti. (Caso raro).</item>
					</list>
					<p>EAC-CPF è stato creato per gestire questa varietà di identità e, per
						esprimere la complessità, include diverse soluzioni basate sia su repository
						singoli sia su aggregatori. Queste opzioni riflettono il disegno principale
						che sottolinea le accresciute opportunità per repository o per aggregatori
						di modellare lo standard sui bisogni specifici, garantendo allo stesso tempo
						aggregazioni future. Questa flessibilità riflette inoltre il riconoscimento
						che, all'interno della comunità internazionale, esistono alcune fondamentali
						differenze filosofiche per ciò che concerne la descrizione di identità.
						EAC-CPF mantiene una posizione neutra rispetto a queste differenze
						filosofiche e, al contrario, ha recepito le differenti opzioni senza
						precludere aggregazioni in futuro.</p>
					<p>Nell'ambito di questo dizionario dei marcatori, con agenti si intendono i
						repository o servizi che creano o mantengono record EAC-CPF, mentre con
						entità si intendono ciò che viene descritto da quei record. </p>
				</div>
				<div xml:id="vddsds">
					<head>Visione d'insieme della struttura e della semantica di EAC-CPF</head>
					<div xml:id="introita">
						<head>Introduzione</head>
						<p> Ogni documento EAC-CPF contiene due elementi obbligatori: l'elemento
								<tag>control</tag> e uno fra l'elemento <tag>cpfDescription</tag> e
								<tag>multipleIdentities</tag>. L'elemento <tag>control</tag>
							contiene dati usati per il controllo della descrizione dell'entità e
							fornisce il contesto della descrizione. <tag>cpfDescription</tag>
							contiene informazioni sulla struttura del nome, gli elementi descrittivi
							e le relazioni. <tag>multipleIdentities</tag> è utilizzato quando c'è
							necessità di usare più <tag>cpfDescription</tag>. Questi due elementi
							contenitori includono elementi specifici per supportare le intenzioni
							funzionali dell'elemento padre o degli elementi contenuti.</p>
					</div>
					<div xml:id="controlita">
						<head>
							<tag>control</tag>
						</head>
						<p>L'elemento <tag>control</tag> contiene i seguenti sotto-elementi:</p>
						<list type="simple">
							<item>
								<tag>recordId</tag> - Identificativo EAC-CPF. Contiene uno o più
								identificativi univoci per l'istanza EAC-CPF. Obbligatorio..</item>
							<item>
								<tag>maintenanceAgency</tag> - Agenzia responsabile. Nome e codici
								dell'istituzione o del servizio responsabile della creazione,
								mantenimento e disseminazione dell'istanza EAC-CPF.
								Obbligatorio.</item>
							<item>
								<tag>maintenanceStatus</tag> - Stato di manutenzione. Contiene lo
								stato corrente di stesura dell'istanza EAC-CPF. I valori possibili
								sono: new (nuovo), revised (rivisto), deleted (eliminato), cancelled
								(cancellato), deletedSplit (eliminato perché separato in più
								documenti), deletedReplaced (eliminato perché sostituito).
								Obbligatorio.</item>
							<item>
								<tag>maintenanceHistory</tag> - Storia di mantenimento. Contiene le
								informazioni sulle date, sulla tipologia di intervento e sugli
								eventi all'interno del ciclo di vita di un'istanza EAC-CPF. Contiene
								uno o più elementi <tag>maintenanceEvent</tag> che documentano
								creazione, importazione, aggiornamento e cancellazione della
								descrizione. Ogni intervento di manutenzione contiene un agente, un
								tipo di agente (umano o macchina), il tipo di intervento e una
								descrizione dell'intervento. Obbligatorio.</item>
							<item>
								<tag>publicationStatus</tag> - Stato di pubblicazione. Contiene
								informazioni sullo stato editoriale dell'istanza EAC-CPF. Opzionale. </item>
							<item>
								<tag>languageDeclaration</tag> - Dichiarazione del linguaggio della
								descrizione. Contiene codice e informazioni in linguaggio naturale
								sui linguaggi usati nell'istanza EAC-CPF. Obbligatorio.</item>
							<item>
								<tag>sources</tag> - Fonti. Contiene informazioni sulle fonti
								consultate nella creazione della descrizione dell'entità o delle
								entità nell'istanza EAC-CPF. Contiene uno o più elementi
									<tag>source</tag>. Obbligatorio.</item>
							<item>
								<tag>conventionDeclaration</tag> - Dichiarazione delle convenzioni.
								Contiene informazioni sulle regole utilizzate per costruire
								l'istanza EAC-CPF, in particolare per quelle usate per i nomi
								formali in <tag>identity</tag> e i vocabolari controllati e i
								tesauri impiegati nell'istanza EAC-CPF. Opzionale.</item>
							<item>
								<tag>otherRecordId</tag> - Altri identificativi del record. Un
								elemento che permette di registrare identificativi addizionali che
								possono essere associati all'istanza EAC-CPF. Opzionale.</item>
							<item>
								<tag>localControl</tag> - Elementi di controllo locali. Un elemento
								in cui registrare ogni elemento di controllo necessario per usi
								locali che non siano inseribili negli altri elementi di
									<tag>control</tag>. Opzionale.</item>
							<item>
								<tag>localTypeDeclaration</tag> - Dichiarazione delle convenzioni
								locali. Un elemento usato per dichiarare le convenzioni locali,
								usate all'interno dell'attributo <att>localType</att>. </item>
						</list>
					</div>
					<div xml:id="descita">
						<head>
							<tag>cpfDescription</tag>
						</head>
						<p>The <tag>cpfDescription</tag>- Descrizione di ente, persona o famiglia.
							Include la descrizione dell'entità. Allo stesso modo dell'elemento
								<tag>control</tag>, <tag>cpfDescription</tag> ha diversi
							sotto-elementi complessi utilizzati per descrivere differenti
							caratteristiche dell'entità:</p>
						<list type="simple">
							<item>
								<tag>identity</tag> - Identità. Struttura complessa che contiene il
								nome o i nomi usati dall'entità nel corso della sua esistenza.
								Contiene un elemento ripetibile <tag>nameEntry</tag> per i
								differenti nomi e un elemento ripetibile
									<tag>nameEntryParallel</tag> per raggruppare più
									<tag>nameEntry</tag> espressi in linguaggi differenti.
								Obbligatorio.</item>
							<item>
								<tag>description</tag> - Descrizione. Contiene gli elementi per una
								descrizione formale paralleli a quelli previsti in ISAAR (CPF) per
								la descrizione dell'entità. Un elemento <tag>localDescription</tag>
								aggiuntivo permette, per i singoli casi locali, l'aggiunta di
								informazioni descrittive non incluse negli altri elementi di
									<tag>description</tag>. Opzionale.</item>
							<item>
								<tag>relations</tag> - Relazioni. Contiene uno o più riferimenti sia
								a descrizioni di enti, persone o famiglie collegati (in
									<tag>cpfRelation</tag>), sia a funzioni (in
									<tag>functionRelation</tag>), sia a risorse (in
									<tag>resourceRelation</tag>). Opzionale.</item>
							<item>
								<tag>alternativeSet</tag> - Gruppo di alternative. Contiene due o
								più record di autorità per la stessa entità derivata da due o più
								differenti sistemi, espressi all'interno di una singola istanza
								EAC-CPF. <tag>alternativeSet</tag> consiste di due o più elementi
									<tag>setComponent</tag> che contengono i diversi record di
								autorità. Opzionale.</item>
						</list>
					</div>
					<div xml:id="identityita">
						<head>
							<tag>identity</tag>
						</head>
						<p>L'elemento maggiormente complesso nello schema EAC-CPF è l'elemento
								<tag>identity</tag>. In aggiunta alla necessità di gestire uno o più
							nomi usati per o dall'entità, l'elemento <tag>identity</tag> deve
							gestire anche due o più nomi paralleli in differenti linguaggi o
							scritture. In nazioni in cui ci sono più di una lingua ufficiale, come
							in Canada, i nomi di enti sono espressi in più linguaggi.
								<tag>identity</tag> contiene un obbligatorio <tag>entityType</tag> e
							uno o più elementi <tag>nameEntry</tag> o <tag>nameEntryParallel</tag>.
							Inoltre include opzionalmente <tag>entityId</tag> e
								<tag>descriptiveNote</tag>. L'elemento <tag>nameEntry</tag> è
							costituito da uno o più elementi <tag>part</tag> e contiene gli
							attributi <att>scriptCode</att>, <att>xml:lang</att>,
								<att>transliteration</att> e <att>localType</att> per informazioni
							precise, laddove desiderato, sui linguaggi e le scritture dei nomi.
							Include anche un elemento opzionale <tag>useDates</tag> per specificare
							le date di utilizzo di un nome. <tag>nameEntryParallel</tag>, che è
							inteso per essere utilizzato nei casi in cui lo stesso nome è espresso
							in differenti linguaggi, contiene uno o più elementi
								<tag>nameEntry</tag> e un opzionale <tag>useDates</tag>. Ad esempio,
							nel contesto dell'Archivio dell'Ontario, intestazioni parallele in
							francese e in inglese possono essere gestite inserendo il codice del
							repository dell'Archivio in due elementi paralleli <tag>nameEntry</tag>,
							con le due differenti intestazioni distinte dal valore nell'attributo
								<att>xml:lang</att>.</p>
						<p>All'interno di <tag>identity</tag>, i nomi rappresentati attraverso
								<tag>nameEntry</tag> o <tag>nameEntryParallel</tag> possono essere
							selezionati come autorizzati o come varianti alternative. Gli elementi
								<tag>authorizedForm</tag> e <tag>alternativeForm</tag> sono
							disponibili all'interno degli elementi <tag>nameEntry</tag> e
								<tag>nameEntryParallel</tag> per identificare lo status del nome
							secondo un determinato gruppo di regole. Il contenuto degli elementi
								<tag>authorizedForm</tag> e <tag>alternativeForm</tag> è
							l'identificativo di queste regole. In aggiunta, all'interno di
								<tag>nameEntryParallel</tag> è possibile preferire un singolo
								<tag>nameEntry</tag> rispetto agli altri. A tale scopo è disponibile
							un elemento <tag>preferredForm</tag> per identificare la forma preferita
							del nome in accordo a uno specifico gruppo di regole. Il contenuto
							dell'elemento <tag>preferedForm</tag> rappresenta l'identificazione di
							queste regole.</p>
					</div>
					<div xml:id="descrita">
						<head>
							<tag>description</tag>
						</head>
						<p>L'elemento <tag>description</tag> raccoglie una pluralità di elementi
							descrittivi dell'entità sia controllati, sia a testo libero. Gli
							elementi contenuti riflettono strettamente le categorie evidenziate in
							ISAAR (CPF). Gli elementi descrittivi hanno nella maggioranza di casi
							sia una forma singolare sia una plurale: quest'ultima viene utilizzata
							nei casi di istanze multiple di una categoria descrittiva o per i casi
							di descrizioni discorsive meno strutturate. Ad esempio,
								<tag>function</tag> verrà usato per un singolo termine di funzione,
								<tag>functions</tag> raggrupperà invece più di un descrittore di
							funzioni o, in alternativa, permetterà una descrizione discorsiva delle
							funzioni. Infatti molti elementi all'interno di <tag>description</tag>
							includono un elemento opzionale <tag>descriptiveNote</tag> per fornire
							una spiegazione testuale. Tutti gli elementi all'interno di
								<tag>description</tag> sono opzionali. Gli elementi per la
							descrizione includono:</p>
						<list type="simple">
							<item>
								<tag>existDates</tag> — Date di esistenza. Contiene le date di
								esistenza dell'entità che si sta descrivendo. Può includere date
								reali o approssimate, utilizzando o <tag>date</tag> o
									<tag>dateRange</tag> o <tag>dateSet</tag>.</item>
							<item>
								<tag>place</tag> — Luogo. Include le informazioni rilevanti sulla
								localizzazione, opzionalmente accoppiate con le informazioni sulle
								date collegate. Comprende gli elementi <tag>placeEntry</tag> e
									<tag>placeRole</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>localDescription</tag> — <tag>localDescription</tag> - Elemento
								di descrizione locale. Un elemento inteso per estendere in un
								sistema locale le categorie descrittive disponibili. Include un
								elemento <tag>term</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>legalStatus</tag> — Condizione giuridica. Include la condizione
								giuridica di un ente, generalmente definita da un authority e
								concessa o dal governo o da un'agenzia autorizzata. Comprende un
								elemento <tag>term</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>function</tag> — Funzione. Include le informazioni pertinenti
								su funzioni, processi, attività, operazioni e transizioni eseguite
								dall'entità che si sta descrivendo. Comprende un elemento
									<tag>term</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>languageUsed</tag> — Linguaggio utilizzato. Indica la lingua e
								la scrittura utilizzate nella produzione o creazione dall'entità
								descritta. Comprende gli elementi <tag>language</tag> e
									<tag>script</tag>. </item>
							<item>
								<tag>occupation</tag> — Occupazione. Include le occupazioni
								pertinenti svolte dall'entità che si sta descrivendo. Comprende un
								elemento <tag>term</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>mandate</tag> — Mandato. Include i mandati pertinenti per gli
								enti che si stanno descrivendo. Comprende un elemento
									<tag>term</tag> e il gruppo di possibilità per esprimere le
								informazioni sulle date: <tag>date</tag>, <tag>dateRange</tag>,
									<tag>dateSet</tag>.</item>
							<item>
								<tag>structureOrGenealogy</tag> — Struttura o genealogia. Include
								informazioni sulla struttura dell'ente o sulla genealogia di una
								persona o di una famiglia. Comprende gli elementi
								<tag>outline</tag>, <tag>list</tag> e <tag>p</tag> per favorire la
								strutturazione del testo.</item>
							<item>
								<tag>generalContext</tag> — Contesto generale. Include le
								informazioni sul contesto generale sociale e culturale dell'entità
								che si sta descrivendo. Comprende un elemento <tag>term</tag> e il
								gruppo di possibilità per esprimere le informazioni sulle date:
									<tag>date</tag>, <tag>dateRange</tag>,
								<tag>dateSet</tag>.</item>
							<item>
								<tag>biogHist</tag> — Biografia o Note storiche. Permette di di
								fornire informazioni biografiche e storiche sull'entità che si sta
								descrivendo, attraverso un testo discorsivo. Comprende un elemento
									<tag>abstract</tag> per una breve sinossi dell'intero contenuto;
								è previsto un elemento <tag>chronList</tag> per informazioni
								strutturate su date, eventi e, opzionalmente, luoghi. Comprende gli
								elementi <tag>list</tag>, <tag>outline</tag> e <tag>p</tag> per
								favorire la strutturazione del testo.</item>
						</list>
						<p>Tutti gli elementi in <tag>description</tag> includono un attributo
								<att>localType</att> per indicare specificazioni semantiche del
							termine che si sta utilizzando. Con l'eccezione di
							<tag>existDates</tag>, <tag>structureOrGenealogy</tag>,
								<tag>generalContext</tag> e <tag>biogHist</tag>, sono disponibili
							elementi contenitori in forma plurale per raggruppare occorrenze
							multiple di questi elementi. Questi elementi contenitori includono
							inoltre gli elementi <tag>citation</tag>, <tag>list</tag>,
								<tag>outline</tag> e <tag>p</tag> per gestire una complessità
							maggiore nella rappresentazione della descrizione che si sta
							creando.</p>
					</div>
					<div xml:id="realtionsita">
						<head>
							<tag>relations</tag>
						</head>
						<p>La descrizione dell'entità, essendo un tassello della descrizione
							archivista, deve dare luogo a relazioni con gli altri componenti
							descrittivi. Le descrizioni delle entità devono essere collegate
							dinamicamente alle descrizioni dei documenti per i quali esse forniscono
							il contesto e alle funzioni e attività in cui le entità sono impegnate e
							che la documentazione archivistica documenta. A eccezione delle
							relazioni univoche, è nella natura stessa delle relazioni che queste si
							sviluppino fra le entità e non all'interno di esse. Le entità sono
							dunque collegate ad altre entità, a attività e funzioni e alla
							documentazione. In maniera simile, le attività e le funzioni sono
							collegate ad altre funzioni e attività, ai soggetti produttori e alla
							documentazione; infine i documenti archivistici sono collegati ad altra
							documentazione, alle entità e alle funzioni e alle attività. Ogni
							descrizione di entità, documentazione o funzione/attività può così
							svolgere il ruolo di nodo in un gruppo di relazioni.</p>
						<p>Poiché le relazioni si verificano tra nodi descrittivi, è di gran lunga
							più efficiente crearle e mantenerle all'esterno di ciascun nodo. Una
							persona, per esempio, può essere collegata a una o più persone,
							organizzazioni o famiglie, a uno o più documenti archivistici, libri,
							riviste e oggetti di museo; e può essere collegata a varie occupazioni e
							attività. Ognuna delle entità collegate può a sua volta essere collegata
							con una o più entità. Registrare tutte queste relazioni nella
							descrizione di ogni nodo è inefficiente poiché la correzione di un
							errore richiederebbe l'aggiornamento di due o più descrizioni.</p>
						<p>Se da un lato mantenere le relazioni indipendenti dalle descrizioni è
							efficiente, dall'altro, nell'interscambio delle descrizioni tra sistemi
							o fra utenti, sarà necessario, per assemblarle o riunirle, rappresentare
							le descrizioni collegate usando surrogati descrittivi. Ogni surrogato
							per la descrizione collegata dovrebbe includere informazioni leggibili
							in modo ottimale sia per l'uomo sia per la macchina. Le informazioni
							leggibili per l'uomo forniscono descrizioni stringate dell'entità,
							documentazioni o funzione/attività collegata sufficienti a permettere
							l'identificazione e a giudicarne la pertinenza. Le informazioni
							leggibili per la macchina mantengono collegamenti trasversali con le
							descrizioni collegate.</p>
						<p>Sono previsti tre elementi per descrivere le relazioni con altre entità
							descrittive che sono inclusi all'interno dell'elemento
								<tag>relations</tag>: <tag>cpfRelation</tag>,
								<tag>functionRelation</tag> e <tag>resourceRelation</tag>.
							All'interno di ciascuno di questi elementi di collegamento, sono
							presenti gli elementi <tag>relationEntry</tag>,
							<tag>objectXMLWrap</tag>, <tag>objectBinWrap</tag>, <tag>date</tag>,
								<tag>dateRange</tag>, <tag>dateSet</tag>, <tag>placeEntry</tag> e
								<tag>descriptiveNote</tag>. Le relazioni individuali includono
							attributi opzionali relativi al tipo di relazioni che si sta
							descrivendo. Questi includono:</p>
						<list type="simple">
							<item>
								<tag>cpfRelation</tag> — includes un attributo
									<att>cpfRelationType</att>; i valori possibili sono identity
								(identità), hierarchical (gerarchica), hierarchical-parent
								(gerarchica-padre), hierarchical-child (gerarchica-figlio), temporal
								(temporale), temporal-earlier (temporale-precedente), temporal-later
								(temporale-successivo), family (familiare), associative
								(associativa).</item>
							<item>
								<tag>functionRelation</tag> — include un attributo
									<att>functionRelationType</att>; i valori possibili sono:
								controls (controlla), owns (possiede), performs (esegue).</item>
							<item>
								<tag>resourceRelation</tag> — includee un attributo
									<att>resourceRelationType</att>; i valori possibili sono:
								creatorOf (soggetto produttore di), subjectOf (soggetto di), other
								(altro).</item>
						</list>
						<p>Altri attributi disponibili per gli elementi di collegamento sono
								<att>lastDateTimeVerified</att> e il gruppo degli attributi semplici
							di Xlink.</p>
						<p>Ci sono due principi razionali alla base di questo primo tentativo di
							tipizzare le relazioni. In primo luogo, c'è l'interesse generale nel
							permettere l'espressione, la navigazione coerente delle relazioni nonché
							la creazione di visualizzazioni grafiche di organigrammi, alberi
							genealogici e linee del tempo. Queste prime ipotesi sono un tentativo
							sperimentale di fornire i dati necessari per costruire simili
							visualizzazioni. In secondo luogo, le informazioni di base sulla natura
							delle relazioni sono necessarie per rendere le relazioni intelligibili
							agli utenti. Viste le differenze culturali e istituzionali, il numero
							delle possibili tipologie di relazioni è, in teoria, illimitato. I
							progettisti di EAC-CPF hanno stabilito, tuttavia, che per raggiungere un
							livello minimo di funzionalità c'era bisogno di un consenso su un gruppo
							di base o iniziale di tipologie di relazioni.</p>
					</div>
					<div xml:id="xlinkita">
						<head>xlink</head>
						<p>Lo schema EAC-CPF include il supporto per i collegamenti a risorse
							esterne usando un sotto-insieme limitato dello standard Xlink, definito
							all'indirizzo <ref target="http://www.w3.org/TR/xlink/"
								>http://www.w3.org/TR/xlink/</ref>. Gli attributi xlink posso essere
							usati per creare e descrivere collegamenti tra risorse. In modo
							particolare possono essere usati per indicare un gruppo di relazioni
							maggiormente ricco rispetto a quelle che sono supportate
							da@cpfRelationType, @functionRelationType e @resourceRelationtype. Gli
							attributi xlink sono disponibili per i seguenti elementi:
								<tag>citation</tag>, <tag>cpfRelation</tag>,
								<tag>functionRelation</tag>, <tag>resourceRelation</tag>,
								<tag>setComponent</tag> e <tag>source</tag>.</p>
						<p>Una descrizione maggiormente completa di questi attributi è fornita
							all'interno della sezione attributi del dizionario dei marcatori, ma le
							informazioni seguenti sono volte a riassumere come questi attributi
							possano essere usati in congiunzione fra di loro.</p>
						<list type="simple">
							<head>Xlink Type Attribute (Attributo tipologia di xlink)</head>
							<item>
								<att>xlink:type</att> — Questo attributo è obbligatorio qualora si
								utilizzi nell'elemento genitore uno qualsiasi degli altri attributi
								xlink. In questo caso assume un valore fissato a “simple” poiché
								l'implementazione di xlink in EAC-CPF supporta solo collegamenti in
								uscita verso una singola risorsa. Se è necessario gestire
								collegamenti molteplici, ogni collegamento dovrebbe essere
								rappresentato in un nuovo elemento genitore.</item>
						</list>
						<list type="simple">
							<head>Locator Attribute (Attributo localizzatore)</head>
							<item>
								<att>xlink:href</att> — Questo elemento opzionale può essere
								utilizzato per fornire l'indirizzo della risorsa che si sta
								collegando. Il link deve essere un URI valido.</item>
						</list>
						<list type="simple">
							<head>Semantic Attributes (Attributi semantici)</head>
							<item>
								<att>xlink:arcrole</att> — Questo elemento opzionale può essere
								usato con <tag>cpfRelation</tag>, <tag>functionRelation</tag> e
									<tag>resourceRelation</tag> per fornire con precisione la
								descrizione della relazione tra le entità descritte nella risorsa
								EAC-CPF e la risorsa con cui è collegata. Quando è usato all'interno
								di <tag>citation</tag>, <tag>setComponent</tag> e <tag>source</tag>,
								fornisce un'esplicita e forse più precisa descrizione della
								relazione che è implicitamente derivata dal contesto di utilizzo. Il
								valore deve essere un URI valido.</item>
							<item>
								<att>xlink:role</att> — Questo elemento opzionale è usato per
								fornire un riferimento alla natura della risorsa remota collegata.
								Nello specifico fornisce un mezzo per specificare la natura della
								risorsa collegata in <tag>resourceRelation</tag>, come descritto in
								ISAAR (CPF) 6.2. Il valore indicato deve essere un URI valido.
							</item>
						</list>
						<list type="simple">
							<head>Link Behavior Attributes (Attributi sul comportamento del
								collegamento) </head>
							<item>
								<att>xlink:actuate</att> — Questo attributo opzionale può essere
								usato in congiunzione con xlink:show per istruire un'applicazione
								esterna sulle circostanze in cui la risorsa collegata dovrebbe
								essere risolta. Per esempio, un'applicazione può essere istruita
								affinché carichi la risorsa quando il documento xml genitore viene
								letto o solo quando la pagina è esplicitamente richiesta da un
								utente o dall'applicazione.</item>
							<item>
								<att>xlink:show</att> — Questo attributo opzionale può essere usato
								in congiunzione con xlink:actuate per istruire un'applicazione
								esterna sui modi in cui la risorsa collegata dovrebbe essere
								mostrata all'utente quando è risolta. Per esempio, l'applicazione
								può essere istruita affinché sostituisca il documento xml corrente
								al caricamento della risorsa collegata o affinché la carichi in una
								nuova finestra o in una nuova scheda.</item>
							<item>
								<att>xlink:title</att> — Questo elemento opzionale può essere usato
								per fornire una didascalia o un titolo che un sistema esterno o
								un'applicazione potrebbero usare per presentare il collegamento agli
								utenti.</item>
						</list>
						<p>I browser della famiglia Mozilla, come Firefox sono tipici applicativi
							che includono un supporto nativo soltanto per un gruppo limitato degli
							attributi xlink. Come risultato, gli implementatori di EAC-CPF avranno
							bisogno di utilizzare istruzioni lato server, per una piena
							implementazione degli attributi xlink. Un esempio di implementazione,
							che dimostra l'effetto atteso nell'uso di xlink, è disponibile
							all'indirizzo <ref target="http://www.snee.com/xml/xlink/sxlinkdemo.xml"
								>http://www.snee.com/xml/xlink/sxlinkdemo.xml</ref>.</p>
						<p>L'estratto di codice seguente mostra un esempio di come xlink possa
							essere utilizzato per collegarsi a un vocabolario esterno con lo scopo
							di indicare che l'informazione dell'URL collegato descrive il coniuge
							della persona descritta nel record EAC-CPF:</p>
						<egXML xmlns="http://www.tei-c.org/ns/Examples">
							<eac-cpf:cpfRelation cpfRelationType="family" xlink:actuate="onRequest"
								xlink:arcrole="http://library.illinois.edu/archives/eac-cpfRelations.html#spouseOf"
								xlink:href="http://library.illinois.edu/archives/archon/index.php?p=creators/creator&amp;id=546"
								xlink:show="new" xlink:type="simple">
								<eac-cpf:relationEntry>Gregory, John Milton</eac-cpf:relationEntry>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>John Milton Gregory was the husband of Louisa Allen
										Gregory.</eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:cpfRelation>
							<eac-cpf:resourceRelation resourceRelationType="creatorOf"
								xlink:role="http://library.illinois.edu/archives/eac-cpfRelations.html#collector"
								xlink:type="simple">
								<eac-cpf:relationEntry>Collezione Fortunato Depero (Polo culturale e
									Galleria Museum Depero, Roverto</eac-cpf:relationEntry>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>ITA MART, Collezione Depero, Collezione d'arte,
										1919-1959, Creatore della collezione, </eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:resourceRelation>
						</egXML>
						<!-- perhaps an example of xlink:role on <resourceRelation> would be good. -->
						<!-- Added, but don't think that it's right; I was thinking of the distinction that might want to be made between an author, a collector, an editor, etc. all under the umbrella of resourceRelationtype="creatorOf" -->
						<p>Il vocabolario di purl.org che è richiamato nell'esempio precedente non è
							inteso per essere normativo, ma è indicato esclusivamente per scopi
							esemplificativi. Nel corso del tempo si auspica che le comunità
							sviluppino e mantengano vocabolari controllati per descrivere la natura
							delle relazioni tra persone, famiglie, enti, risorse e funzioni che sono
							descritte all'interno degli elementi <tag>cpfRelation</tag>,
								<tag>resourceRelation</tag> e <tag>functionRelation</tag>. Questi
							vocabolari potranno essere mantenuti localmente, a livello nazionale o
							anche internazionale, forse come continuazione delle attività del gruppo
							di lavoro su EAC.</p>
					</div>
					<div xml:id="localtypeita">
						<head>
							<att>localType</att>
						</head>
						<p>Poiché questo rappresenta uno sforzo internazionale, I progettisti di
							EAC-CPF stanno tentando di concordare il più possibile per gestire le
							differenze culturali e istituzionali. La semantica e le strutture
							descritte in precedenza rappresentano il consenso attuale sulla
							semantica e la struttura e sono strettamente legate a ISAAR (CPF).</p>
						<p>In aggiunta all'elemento <tag>localDescription</tag>, descritto in
							precedenza, molti elementi possono anche essere qualificati con un
							attributo @localType. Questo attributo è inteso per permettere di
							adattare EAC-CPF all'uso in contesti nazionali, regionali e locali dove
							possono essere necessari elementi semantici maggiormente specifici di
							quelli previsti in EAC-CPF o dove sono necessarie categorie descrittive
							non specificatamente affrontate da EAC-CPF.</p>
					</div>
				</div>
				<div xml:id="resourcesita">
					<head>Resources</head>
					<list type="simple">
						<item>International Council on Archives. International Standard Archival
							Authority Record for Corporate bodies, Persons, and Families. Seconda
							edizione. 2003. <ref
								target="http://www.icacds.org.uk/eng/ISAAR(CPF)2ed.pdf"
								>http://www.icacds.org.uk/eng/ISAAR(CPF)2ed.pdf</ref>. (Disponibile
							anche nella traduzione italiana a cura di Stefano Vitali all'indirizzo
								<ref
								target="http://www.anai.org/attivita/N_isad/Isad%20-%20traduzione%20vitali.pdf"
								>http://www.anai.org/attivita/N_isad/Isad%20-%20traduzione%20vitali.pdf</ref>)</item>
						<item>International Council on Archives. General International Standard
							Archival Description. Seconda edizione. 1999. <ref
								target="http://www.ica.org/sites/default/files/isad_g_2e.pdf"
								>http://www.ica.org/sites/default/files/isad_g_2e.pdf</ref>.
							(Disponibile anche nella traduzione italiana a cura di Stefano Vitali
							all'indirizzo
							<ref
								target="http://www.ica.org/sites/default/files/ISAAR2-IT.pdf">http://www.ica.org/sites/default/files/ISAAR2-IT.pdf</ref>).</item>
					</list>
				</div>
			</div>
		</front>
		<body>
			<div type="elements" xml:id="elements">
				<div type="element" xml:id="abbreviation">
					<head type="tag">
						<tag>abbreviation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Abbreviation</head>
						<item n="summary">The <tag>abbreviation</tag> element is used to provide
							authorized codes for the identification of thesauri, controlled
							vocabularies, and standards used in the construction of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>The <tag>abbreviation</tag> element is used to provide authorized
								codes for the identification of thesauri, controlled vocabularies,
								and standards used in the construction of the EAC-CPF instance.
								Values should be derived from an authorized list of codes. An
								example of such a list may be the MARC Code List (<ref
									target="http://www.loc.gov/standards/sourcelist/descriptive-conventions.html"
									>http://www.loc.gov/standards/sourcelist/descriptive-conventions.html</ref>).</p>
						</item>
						<item n="mayContain">[token]</item>
						<item n="mayOccurIn">conventionDeclaration, localTypeDeclaration</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<list xml:lang="ita">
						<head type="name">Abbreviazione</head>
						<item n="summary">L'elemento <tag>abbreviation</tag> è utilizzato per
							fornire identificativi autorizzati per indicare tesauri, vocabolari
							controllati o altri standard usati per la compilazione di un'istanza
							EAC-CPF. </item>
						<item n="description">
							<p>L'elemento <tag>abbreviation</tag> è utilizzato per fornire
								identificativi autorizzati per indicare tesauri, vocabolari
								controllati o altri standard usati per la compilazione di un'istanza
								EAC-CPF. I valori dovrebbero essere derivati da una lista
								autorizzata di codici. Un esempio di simili liste potrebbe essere
								l'elenco dei codici MARC disponibile all'indirizzo (<ref
									target="http://www.loc.gov/standards/sourcelist/descriptive-conventions.html"
									>http://www.loc.gov/standards/sourcelist/descriptive-conventions.html</ref>).</p>
						</item>
						<item n="mayContain">[token]</item>
						<item n="mayOccurIn">conventionDeclaration, localTypeDeclaration</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Opzionale</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:conventionDeclaration>
							<eac-cpf:abbreviation>RICA</eac-cpf:abbreviation>
							<eac-cpf:citation>RICA (Regole italiane di catalogazione per
								autore)</eac-cpf:citation>
						</eac-cpf:conventionDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="abstract">
					<head type="tag">
						<tag>abstract</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Abstract</head>
						<item n="summary">An element that encodes a brief summary of the information
							contained within the <tag>biogHist</tag> as a whole. </item>
						<item n="description">
							<p>The <tag>abstract</tag> is a 1-2 sentence synopsis of the identity’s
								biography or history that is often extracted from the longer
								descriptions found in <tag>biogHist</tag>. Its purpose is to help
								readers quickly identify the entity described in the EAC-CPF
								instance. The content within this element may also be harvested by
								other systems to provide explanatory context for the
									<tag>nameEntry</tag> data when it appears in a set of search
								results.</p>
						</item>
						<item n="mayContain">[text], span</item>
						<item n="mayOccurIn">biogHist</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0…1</item>
					</list>
					<list xml:lang="ita">
						<head type="name">Riassunto</head>
						<item n="summary">Un elemento utilizzato per codificare un breve riassunto
							delle informazioni contenute nella loro interezza in
							<tag>biogHist</tag>. </item>
						<item n="description">
							<p><tag>abstract</tag> è un compendio di 1 o 2 frasi della biografia o
								storia dell'identità, spesso estratto dalla descrizione più estesa
								che si trova in <tag>biogHist</tag>. Il suo scopo è quello di
								aiutare i lettori a identificare rapidamente l'entità descritta in
								un'istanza EAC-CPF. Il contenuto all'interno di questo elemento può
								inoltre essere recuperato (tramite harvesting) da altri sistemi per
								fornire una spiegazione contestuale ai dati contenuti in
									<tag>nameEntry</tag> che appaiano, ad esempio, in una lista di
								risultati di una ricerca.</p>
						</item>
						<item n="mayContain">[text], span</item>
						<item n="mayOccurIn">biogHist</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Opzionale</item>
								<label>xml:id</label>
								<item>Opzionale</item>
								<label>xml:lang</label>
								<item>Opzionale</item>
							</list>
						</item>
						<item n="occurrence">0…1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:biogHist>
							<eac-cpf:abstract>Established in 1961, the United States Peace Corps
								administered and coordinated Federal international volunteer and
								related domestic volunteer programs in areas of agricultural
								assistance, community development, education, environmental
								protection, and nation assistance.</eac-cpf:abstract>
							<eac-cpf:p>The Peace Corps was established as an operating agency in the
								Department of State Delegation of Authority 85-11, effective March
								3, 1961, pursuant to Executive Order (E.O.) 10924, March 1, 1961. It
								was recognized legislatively by the Peace Corps Act (75 Stat. 612),
								approved September 22, 1961. The Peace Corps was reassigned to the
								newly established ACTION by Reorganization Plan No. 1 of 1971,
								effective July 1, 1971. It was made autonomous within ACTION by E.O.
								12137, May 16, 1979, and was made an independent agency by Title VI
								of the International Security and Development Corporation Act of
								1981 (95 Stat. 1540), February 21, 1982. The Peace Corps
								administered and coordinated Federal international volunteer and
								related domestic volunteer programs including the areas of
								agricultural assistance, community development, education,
								environmental protection, and nation assistance.</eac-cpf:p>
						</eac-cpf:biogHist>
					</egXML>
				</div>
				<div type="element" xml:id="address">
					<head type="tag">
						<tag>address</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Address</head>
						<item n="summary">A postal or other address.</item>
						<item n="description">
							<p>
								<tag>address</tag> is a wrapper element within <tag>place</tag>. It
								contains one or more <tag>addressLine</tag> elements that together
								comprise full or sufficient information identifying a postal or
								other address related to the entity being described.</p>
						</item>
						<item n="mayContain">addressLine</item>
						<item n="mayOccurIn">place</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<list xml:lang="ita">
						<head type="name">Indirizzo</head>
						<item n="summary">Un indirizzo postale o altro tipo di indirizzo.</item>
						<item n="description">
							<p>
								<tag>address</tag> è un elemento contenitore all'interno di
									<tag>place</tag>. Contiene uno o più elementi
									<tag>addressLine</tag> eche nell'insieme costituiscono le
								informazioni complete o comunque sufficienti a identificare un
								indirizzo postale o altro tipo di indirizzo relativo all'entità
								descritta.</p>
						</item>
						<item n="mayContain">addressLine</item>
						<item n="mayOccurIn">place</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Opzionale</item>
								<label>xml:id</label>
								<item>Opzionale</item>
								<label>xml:lang</label>
								<item>Opzionale</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:place>
							<eac-cpf:placeRole>siege social</eac-cpf:placeRole>
							<eac-cpf:address>
								<eac-cpf:addressLine localType="voie">2 rue
									Corneille</eac-cpf:addressLine>
								<eac-cpf:addressLine localType="city">Paris</eac-cpf:addressLine>
								<eac-cpf:addressLine localType="postalcode"
									>75006</eac-cpf:addressLine>
								<eac-cpf:addressLine>France</eac-cpf:addressLine>
							</eac-cpf:address>
						</eac-cpf:place>
					</egXML>
				</div>
				<div type="element" xml:id="addressLine">
					<head type="tag">
						<tag>addressLine</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Address Line</head>
						<item n="summary">One line of a postal or other address</item>
						<item n="description">
							<p>A required element in <tag>address</tag>, <tag>addressLine</tag>
								element is used to encode one line of a postal or other address.
									<tag>addressLine</tag> may be repeated as many times as
								necessary to encompass all available lines of an address related to
								the entity being described.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">address</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.3</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:place>
							<eac-cpf:placeRole>siege social</eac-cpf:placeRole>
							<eac-cpf:address>
								<eac-cpf:addressLine localType="voie">2 rue
									Corneille</eac-cpf:addressLine>
								<eac-cpf:addressLine localType="city">Paris</eac-cpf:addressLine>
								<eac-cpf:addressLine localType="postalcode"
									>75006</eac-cpf:addressLine>
								<eac-cpf:addressLine>France</eac-cpf:addressLine>
							</eac-cpf:address>
						</eac-cpf:place>
					</egXML>
				</div>
				<div type="element" xml:id="agencyCode">
					<head type="tag">
						<tag>agencyCode</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Agency Code</head>
						<item n="summary">The code that represents the institution or service
							responsible for the creation, maintenance and/or dissemination of the
							EAC-CPF instance.</item>
						<item n="description">
							<p>An element of <tag>maintenanceAgency</tag> within <tag>control</tag>
								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 <tag>agencyName</tag>.
								The code is used in combination with the content of the required
									<tag>recordId</tag> to provide a globally unique identifier for
								the instance.</p>
							<p>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 <tag>otherAgencyCode</tag>
								element.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">maintenanceAgency</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.2</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceAgency>
							<eac-cpf:agencyCode>AU-ANL:PEAU</eac-cpf:agencyCode>
							<eac-cpf:agencyName>National Library of Australia</eac-cpf:agencyName>
						</eac-cpf:maintenanceAgency>
					</egXML>
				</div>
				<div type="element" xml:id="agencyName">
					<head type="tag">
						<tag>agencyName</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Agency Name</head>
						<item n="summary">The name of the institution or service responsible for the
							creation, maintenance, and/or dissemination of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A mandatory element of <tag>maintenanceAgency</tag> within
									<tag>control</tag> that provides the name of the institution or
								service responsible for the creation, maintenance and/or
								dissemination of the EAC-CPF instance.</p>
							<p>It is recommended that one uses the form of the agency name that is
								authorized by an appropriate national or international agency or
								service.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">maintenanceAgency</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.2</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceAgency>
							<eac-cpf:agencyCode>AU-ANL:PEAU</eac-cpf:agencyCode>
							<eac-cpf:agencyName>National Library of Australia</eac-cpf:agencyName>
						</eac-cpf:maintenanceAgency>
					</egXML>
				</div>
				<div type="element" xml:id="agent">
					<head type="tag">
						<tag>agent</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Agent</head>
						<item n="summary">The agent (human or machine) responsible for an event in
							the maintenance of the EAC instance.</item>
						<item n="description">
							<p>For each maintenance event described in a <tag>maintenanceEvent</tag>
								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 <tag>agentType</tag> should be set as "human," or the name of a
								system, in which case set the <tag>agentType</tag> to "machine."</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">maintenanceEvent</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.9</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime>1993-10-20</eac-cpf:eventDateTime>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>McCarthy, G.J.</eac-cpf:agent>
						</eac-cpf:maintenanceEvent>
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>revised</eac-cpf:eventType>
							<eac-cpf:eventDateTime>2006-08-01</eac-cpf:eventDateTime>
							<eac-cpf:agentType>machine</eac-cpf:agentType>
							<eac-cpf:agent>BSConverta</eac-cpf:agent>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="agentType">
					<head type="tag">
						<tag>agentType</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Agent Type</head>
						<item n="summary">The type of agent responsible for a maintenance event of
							the EAC-CPF instance.</item>
						<item n="description">
							<p>For each maintenance event described in a <tag>maintenanceEvent</tag>
								element, the type of agent given in the <tag>agent</tag> element
								must be given as either "human" or "machine."</p>
						</item>
						<item n="mayContain">"human" or "machine"</item>
						<item n="mayOccurIn">maintenanceEvent</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.9</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime>1993-10-20</eac-cpf:eventDateTime>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>McCarthy, G.J.</eac-cpf:agent>
						</eac-cpf:maintenanceEvent>
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>revised</eac-cpf:eventType>
							<eac-cpf:eventDateTime>2006-08-01</eac-cpf:eventDateTime>
							<eac-cpf:agentType>machine</eac-cpf:agentType>
							<eac-cpf:agent>BSConverta</eac-cpf:agent>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="alternativeForm">
					<head type="tag">
						<tag>alternativeForm</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Alternative Form</head>
						<item n="summary">Qualifies the name contained in <tag>nameEntry</tag> or
							set of names contained in <tag>nameEntryParallel</tag> as alternative or
							variant forms.</item>
						<item n="description">
							<p>The name of an EAC-CPF entity, as formed within the
									<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> 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
									<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> would be
								regarded as an alternative or unauthorized form.</p>
							<p>The eac-cpf schema offers two possibilities:</p>
							<p>1. <tag>alternativeForm</tag> is used within <tag>nameEntry</tag>
								only when <tag>nameEntry</tag> is not included within
									<tag>nameEntryParallel</tag>. In this case, it qualifies the
								form of the name recorded within the precise <tag>nameEntry</tag>
								element as a variant access point, as compared to other
									<tag>nameEntry</tag> elements which are deemed as authorized
								ones.</p>
							<p>2. <tag>alternativeForm</tag> may be used within
									<tag>nameEntryParallel</tag> to indicate that the set of
								parallel names recorded in separate <tag>nameEntry</tag> elements
								within <tag>nameEntryParallel</tag> are deemed as variant access
								points.</p>
							<p>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 <tag>alternativeForm</tag> must be declared within the
									<tag>conventionDeclaration</tag> element in
								<tag>control</tag>.</p>
							<p>The parallel element <tag>authorizedForm</tag> permits one to
								indicate rules or conventions according to which the name is the
								authorized form. The element <tag>preferredForm</tag> 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.</p>
							<p>
								<tag>alternativeForm</tag> may be repeated in case a single or a set
								of <tag>nameEntry</tag> element(s) may conform to more than one
								rule.</p>
						</item>
						<item n="mayContain">NMTOKEN</item>
						<item n="mayOccurIn">nameEntry, nameEntryParallel</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.5</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Bob, 1886-1959</eac-cpf:part>
							<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
							<eac-cpf:alternativeForm>ncafnor</eac-cpf:alternativeForm>
						</eac-cpf:nameEntry>
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Robert Carlton (1886-1959)</eac-cpf:part>
							<eac-cpf:authorizedForm>ncafnor</eac-cpf:authorizedForm>
							<eac-cpf:alternativeForm>AACR2</eac-cpf:alternativeForm>
						</eac-cpf:nameEntry>
					</egXML>
				</div>
				<div type="element" xml:id="alternativeSet">
					<head type="tag">
						<tag>alternativeSet</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Alternative Set</head>
						<item n="summary">A container element for two or more authority records
							derived from two or more authority systems, expressed within a single
							EAC-CPF instance.</item>
						<item n="description">
							<p>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 <tag>alternativeSet</tag> in
									<tag>setComponent</tag> elements. This device allows different
								descriptions of the same entity to be contained within a single
								EAC-CPF instance.</p>
							<p>Authority record aggregation may be used in cooperative or consortial
								contexts that gather together records describing the same entity in
								different languages, or from different rules when it is desirable to
								provide users with alternative descriptions of the same entity. For
								example, in the context of the European Union, an international
								cooperative project may want to provide users the option of
								descriptions in Italian, French, German, English, Spanish, and in
								other European languages.</p>
							<p>
								<tag>alternativeSet</tag> should not be confused with
									<tag>sources</tag>, wherein authority records referenced are not
								intended to be displayed as alternative versions.</p>
						</item>
						<item n="mayContain">setComponent</item>
						<item n="mayOccurIn">cpfDescription</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:alternativeSet>
							<eac-cpf:setComponent xlink:href="http://authorities.loc.gov/"
								xlink:type="simple">
								<eac-cpf:componentEntry>Bright Sparcs
									Record</eac-cpf:componentEntry>
							</eac-cpf:setComponent>
							<eac-cpf:setComponent xlink:href="http://nla.gov.au/anbd.aut-an35335937"
								xlink:type="simple">
								<eac-cpf:componentEntry>NLA record.</eac-cpf:componentEntry>
							</eac-cpf:setComponent>
							<eac-cpf:setComponent lastDateTimeVerified="2009-08-02"
								xlink:href="mawsonBS.xml" xlink:type="simple">
								<eac-cpf:objectXMLWrap>
									<eac-cpf xmlns="http://eac.staatsbibliothek-berlin.de"
										xmlns:xlink="http://www.w3.org/1999/xlink"/>
								</eac-cpf:objectXMLWrap>
							</eac-cpf:setComponent>
						</eac-cpf:alternativeSet>
					</egXML>
				</div>
				<div type="element" xml:id="authorizedForm">
					<head type="tag">
						<tag>authorizedForm</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Authorized Form</head>
						<item n="summary">Qualifies the name contained in <tag>nameEntry</tag> or
							the set of names contained in <tag>nameEntryParallel</tag> as authorized
							access points.</item>
						<item n="description">
							<p>The name of an EAC-CPF entity, as formed within the
									<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> 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
									<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> would be
								regard as an authorized form.</p>
							<p>The eac-cpf schema offers two possibilities:</p>
							<p>1. <tag>authorizedForm</tag> is used within <tag>nameEntry</tag> only
								when <tag>nameEntry</tag> is not included within
									<tag>nameEntryParallel</tag>. In this case, it qualifies the
								form of the name recorded within the precise <tag>nameEntry</tag>
								element as an authorized access point.</p>
							<p>2. <tag>authorizedForm</tag> may be used within
									<tag>nameEntryParallel</tag> to indicate that the set of
								parallel names recorded in separate <tag>nameEntry</tag> elements
								within <tag>nameEntryParallel</tag> are deemed as authorized access
								points.</p>
							<p>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 <tag>authorizedForm</tag> must be declared within the
									<tag>conventionDeclaration</tag> element in
								<tag>control</tag>.</p>
							<p>The parallel element <tag>alternativeForm</tag> permits one to
								indicate rules or conventions according to which the name is the
								authorized form. The element <tag>preferredForm</tag> 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.</p>
							<p>
								<tag>authorizedForm</tag> may be repeated in case a single or a set
								of <tag>nameEntry</tag> element(s) may conform to more than one
								rule.</p>
						</item>
						<item n="mayContain">NMTOKEN</item>
						<item n="mayOccurIn">nameEntry, nameEntryParallel</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Bob, 1886-1959</eac-cpf:part>
							<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
							<eac-cpf:alternativeForm>ncafnor</eac-cpf:alternativeForm>
						</eac-cpf:nameEntry>
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Robert Carlton (1886-1959)</eac-cpf:part>
							<eac-cpf:authorizedForm>ncafnor</eac-cpf:authorizedForm>
							<eac-cpf:alternativeForm>AACR2</eac-cpf:alternativeForm>
						</eac-cpf:nameEntry>
					</egXML>
				</div>
				<div type="element" xml:id="biogHist">
					<head type="tag">
						<tag>biogHist</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Biographical or Historical Note</head>
						<item n="summary">A concise essay and/or chronology that provides
							biographical or historical information about the EAC-CPF entity.</item>
						<item n="description">
							<p>The <tag>biogHist</tag> includes significant details about the life
								of an individual or family, or the administrative history of a
								corporate body. The <tag>biogHist</tag> may contain just text in a
								series of Paragraphs <tag>p</tag>, and/or a Chronology List
									<tag>chronList</tag> that matches dates and date ranges with
								associated events and/or places. The <tag>abstract</tag> element is
								intended to provide a very brief synopsis of the full
									<tag>biogHist</tag> content that could be extracted for
								inclusion in a remote source, such as a MARC record.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> elements are used to accommodate greater
								complexity in expressing or representing the biography or history
								being described. A simpler discursive expression of the information
								may be encoded as one or more <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">abstract, chronList, citation, list, outline, p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference"> ISAAR 5.2.2</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:biogHist>
							<eac-cpf:abstract>Established in 1961, the United States Peace Corps
								administered and coordinated Federal international volunteer and
								related domestic volunteer programs in areas of agricultural
								assistance, community development, education, environmental
								protection, and nation assistance.</eac-cpf:abstract>
							<eac-cpf:p>The Peace Corps was established as an operating agency in the
								Department of State Delegation of Authority 85-11, effective March
								3, 1961, pursuant to Executive Order (E.O.) 10924, March 1, 1961. It
								was recognized legislatively by the Peace Corps Act (75 Stat. 612),
								approved September 22, 1961. The Peace Corps was reassigned to the
								newly established ACTION by Reorganization Plan No. 1 of 1971,
								effective July 1, 1971. It was made autonomous within ACTION by E.O.
								12137, May 16, 1979, and was made an independent agency by Title VI
								of the International Security and Development Corporation Act of
								1981 (95 Stat. 1540), February 21, 1982. The Peace Corps
								administered and coordinated Federal international volunteer and
								related domestic volunteer programs including the areas of
								agricultural assistance, community development, education,
								environmental protection, and nation assistance.</eac-cpf:p>
						</eac-cpf:biogHist>
						<eac-cpf:biogHist>
							<eac-cpf:p>Ilma Mary Brewer, nee Pidgeon, was Lecturer in
								Botany/Biology, University of Sydney 1963-70 and Senior Lecturer in
								Biological Sciences 1970-78. She developed new methods of teaching
								based on the recognition that a student learnt more by working at
								his/her own place and instruction him/her self. Her findings were
								published as a book, "Learning More and Teaching Less."</eac-cpf:p>
							<eac-cpf:chronList>
								<eac-cpf:chronItem>
									<eac-cpf:date standardDate="1936">1936</eac-cpf:date>
									<eac-cpf:event>Bachelor of Science (BSc) completed at the
										University of Sydney</eac-cpf:event>
								</eac-cpf:chronItem>
								<eac-cpf:chronItem>
									<eac-cpf:date standardDate="1937">1937</eac-cpf:date>
									<eac-cpf:event>Master of Science (MSc) completed at the
										University of Sydney</eac-cpf:event>
								</eac-cpf:chronItem>
								<eac-cpf:chronItem>
									<eac-cpf:dateRange>
										<eac-cpf:fromDate standardDate="1937"
											>1937</eac-cpf:fromDate>
										<eac-cpf:toDate standardDate="1941">1941</eac-cpf:toDate>
									</eac-cpf:dateRange>
									<eac-cpf:event>Linnean Macleay Fellow</eac-cpf:event>
								</eac-cpf:chronItem>
							</eac-cpf:chronList>
						</eac-cpf:biogHist>
					</egXML>
				</div>
				<div type="element" xml:id="chronItem">
					<head type="tag">
						<tag>chronItem</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Chronological Item</head>
						<item n="summary">A container element that keeps a date or a date range
							paired with an associated event and an optional place within a
							Chronology List <tag>chronList</tag>.</item>
						<item n="description">
							<p>Each <tag>chronItem</tag> contains a <tag>date</tag> (a single date)
								or a <tag>dateRange</tag> (an inclusive date span) coupled with an
									<tag>event</tag>. A <tag>placeEntry</tag> element is optionally
								available to ground the event in a particular location.</p>
						</item>
						<item n="mayContain">date, dateRange, event, placeEntry</item>
						<item n="mayOccurIn">chronList</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.2</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:chronItem>
							<eac-cpf:date standardDate="1957">1957</eac-cpf:date>
							<eac-cpf:event>Left Mer and moved to the mainland. Worked at various
								jobs including canecutter and railway labourer.</eac-cpf:event>
						</eac-cpf:chronItem>
						<eac-cpf:chronItem>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1960">1960</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1961">1961</eac-cpf:toDate>
							</eac-cpf:dateRange>
							<eac-cpf:event>Union representative, Townsville-Mount Isa rail
								construction project.</eac-cpf:event>
						</eac-cpf:chronItem>
					</egXML>
				</div>
				<div type="element" xml:id="chronList">
					<head type="tag">
						<tag>chronList</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Chronological List</head>
						<item n="summary">A structured chronological list of events, dates, and
							(optionally) places that may be used within the <tag>biogHist</tag>
							element.</item>
						<item n="description">
							<p>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 <tag>chronList</tag>
								contains a series of <tag>chronItem</tag> elements, each associating
								a <tag>date</tag> or <tag>dateRange</tag> with an <tag>event</tag>
								and an optional <tag>placeEntry</tag>.</p>
						</item>
						<item n="mayContain">chronItem</item>
						<item n="mayOccurIn">biogHist</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.2</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:chronList>
							<eac-cpf:chronItem>
								<eac-cpf:date standardDate="1936">1936</eac-cpf:date>
								<eac-cpf:event>Bachelor of Science (BSc) completed at the University
									of Sydney</eac-cpf:event>
							</eac-cpf:chronItem>
							<eac-cpf:chronItem>
								<eac-cpf:date standardDate="1937">1937</eac-cpf:date>
								<eac-cpf:event>Master of Science (MSc) completed at the University
									of Sydney</eac-cpf:event>
							</eac-cpf:chronItem>
							<eac-cpf:chronItem>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1937">1937</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1941">1941</eac-cpf:toDate>
								</eac-cpf:dateRange>
								<eac-cpf:event>Linnean Macleay Fellow</eac-cpf:event>
							</eac-cpf:chronItem>
							<eac-cpf:chronItem>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1939">c. 1939</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1945">c. 1945</eac-cpf:toDate>
								</eac-cpf:dateRange>
								<eac-cpf:event>Worked with Army Intelligence to map the vegetation
									(trees and undergrowth) in the coastal regions of New South
									Wales</eac-cpf:event>
							</eac-cpf:chronItem>
						</eac-cpf:chronList>
					</egXML>
				</div>
				<div type="element" xml:id="citation">
					<head type="tag">
						<tag>citation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Citation</head>
						<item n="summary">A linking element that cites an external resource.</item>
						<item n="description">
							<p>
								<tag>citation</tag> is a generic linking element that cites an
								external resource in machine and / or human readable form, which is
								available within a number of descriptive elements. The purpose of
								the <tag>citation</tag> 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
									<tag>source</tag> 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 <tag>citation</tag> element must be
								given within <tag>conventionDeclaration</tag> and
									<tag>localTypeDeclaration</tag> elements in <tag>control</tag>.
								Provide the formal title or name of the resource, using the
									<tag>span</tag> 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/.</p>
						</item>
						<item n="mayContain">[text], span</item>
						<item n="mayOccurIn">biogHist, conventionDeclaration, function, legalStatus,
							localDescription, localTypeDeclaration, mandate, occupation,
							place</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞ or 1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:conventionDeclaration>
							<eac-cpf:abbreviation>AFNOR</eac-cpf:abbreviation>
							<eac-cpf:citation>Indexation conforme à la norme AFNOR NF Z44-060
								(decembre 1996) Documentation - Catalogue d'auteurs et
								d'anonymes-formes et structures des vedettes de collectivites -
								auteurs</eac-cpf:citation>
						</eac-cpf:conventionDeclaration>
						<eac-cpf:conventionDeclaration>
							<eac-cpf:abbreviation>USNARA-LDRG</eac-cpf:abbreviation>
							<eac-cpf:citation>U.S. National Archives and Records Administration,
								Lifecycle Data Requirements Guide (for creating the authorized form
								of the name).</eac-cpf:citation>
						</eac-cpf:conventionDeclaration>
						<eac-cpf:mandate>
							<eac-cpf:citation>FR ANOM COL C11D 1 Fo 179-179vo : concession de peche
								en Acadie par le Roi à Bergier, Gaultier, Boucher et autres date du
								3 mars 1684.</eac-cpf:citation>
						</eac-cpf:mandate>
					</egXML>
				</div>
				<div type="element" xml:id="componentEntry">
					<head type="tag">
						<tag>componentEntry</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Component Entry</head>
						<item n="summary">A caption that can be used to provide identification and
							access to a linked resource.</item>
						<item n="description">
							<p>A <tag>componentEntry</tag> always occurs within
									<tag>setComponent</tag> 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 <tag>alternativeSet</tag>
								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 <tag>componentEntry</tag> element provides a place
								where a particular alternate record can be described or explained in
								relation to the other authority records.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">setComponent</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:alternativeSet>
							<eac-cpf:setComponent xlink:href="http://nla.gov.au/anbd.aut-an35335937"
								xlink:type="simple">
								<eac-cpf:componentEntry>Bright Sparcs
									Record</eac-cpf:componentEntry>
							</eac-cpf:setComponent>
							<eac-cpf:setComponent lastDateTimeVerified="2009-08-02"
								xlink:href="mawsonBS.xml" xlink:type="simple">
								<eac-cpf:objectXMLWrap>
									<eac-cpf:eac-cpf xmlns="http://eac/staatsbibliothek-berlin.de">
										[...] </eac-cpf:eac-cpf>
								</eac-cpf:objectXMLWrap>
							</eac-cpf:setComponent>
						</eac-cpf:alternativeSet>
					</egXML>
				</div>
				<div type="element" xml:id="control">
					<head type="tag">
						<tag>control</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Control</head>
						<item n="summary">The area of the instance that contains control information
							about its identity, creation, maintenance, status, and the rules and
							authorities used in the composition of the description.</item>
						<item n="description">
							<p>This required wrapper element within <tag>eac-cpf</tag> contains the
								information necessary to control the instance. This includes
								information about its identity, creation, maintenance, and status as
								well the languages, rules and authorities used in the composition of
								the description.</p>
							<p>It must contain a unique identifier for the instance within the
									<tag>recordId</tag> element and other associated identifiers may
								be given in <tag>otherRecordId</tag>. There must be a description of
								the agency responsible for its creation and maintenance in
									<tag>maintenanceAgency</tag> as well as statements about its
								current drafting status in <tag>maintenanceStatus</tag> and the
								creation, maintenance, and disposition of the instance in
									<tag>maintenanceHistory</tag>.</p>
							<p>Three elements are available to declare languages, rules and
								conventions used in the EAC-CPF instance. The
									<tag>languageDeclaration</tag> element provides information on
								the language and script used in the description. The
									<tag>conventionDeclaration</tag> element provides information on
								the authorities or controlled vocabularies used in the instance.
									<tag>localTypeDeclaration</tag> is used to declare the local
								conventions and controlled vocabularies used within the
									<att>localType</att> in the instance.</p>
							<p>Other optional elements available in <tag>control</tag> include a
									<tag>sources</tag> element to provide information about the
								documentary sources used in the composition of the description and a
									<tag>publicationStatus</tag> element to indicate the editorial
								status of the eac-cpf instance.</p>
							<p>Other control elements considered necessary but not otherwise
								included may be given in <tag>localControl</tag> element.</p>
						</item>
						<item n="mayContain">conventionDeclaration, languageDeclaration,
							localControl, localTypeDeclaration, maintenanceAgency,
							maintenanceHistory, maintenanceStatus, otherRecordId, publicationStatus,
							recordId, sources</item>
						<item n="mayOccurIn">eac-cpf</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:control>
							<eac-cpf:recordId>nla.party-521122</eac-cpf:recordId>
							<eac-cpf:maintenanceStatus>revised</eac-cpf:maintenanceStatus>
							<eac-cpf:publicationStatus>approved</eac-cpf:publicationStatus>
							<eac-cpf:maintenanceAgency>
								<eac-cpf:agencyCode>AU-ANL:PEAU</eac-cpf:agencyCode>
								<eac-cpf:agencyName>National Library of
									Australia</eac-cpf:agencyName>
							</eac-cpf:maintenanceAgency>
							<eac-cpf:languageDeclaration>
								<eac-cpf:language languageCode="eng"/>
								<eac-cpf:script scriptCode="Latn"/>
							</eac-cpf:languageDeclaration>
							<eac-cpf:conventionDeclaration>
								<eac-cpf:abbreviation>AACR2</eac-cpf:abbreviation>
								<eac-cpf:citation>Anglo-American Cataloging Rules,
									Revised</eac-cpf:citation>
							</eac-cpf:conventionDeclaration>
							<eac-cpf:maintenanceHistory>
								<eac-cpf:maintenanceEvent>
									<eac-cpf:eventType>created</eac-cpf:eventType>
									<eac-cpf:eventDateTime standardDateTime="2009-06-26T05:33:41Z"
										>2009-06-26T05:33:41Z</eac-cpf:eventDateTime>
									<eac-cpf:agentType>human</eac-cpf:agentType>
									<eac-cpf:agent>bdewhurs</eac-cpf:agent>
								</eac-cpf:maintenanceEvent>
							</eac-cpf:maintenanceHistory>
							<eac-cpf:sources>
								<eac-cpf:source
									xlink:href="http://www.icacds.org.uk/eng/ISAAAR(CPF)2ed.pdf"
									xlink:type="simple">
									<eac-cpf:sourceEntry>ISAAR(CPF)</eac-cpf:sourceEntry>
									<eac-cpf:descriptiveNote>
										<eac-cpf:p>Record created based on ISAAR(CPF) 2nd ed Example
											5 - Person description</eac-cpf:p>
									</eac-cpf:descriptiveNote>
								</eac-cpf:source>
							</eac-cpf:sources>
						</eac-cpf:control>
					</egXML>
				</div>
				<div type="element" xml:id="conventionDeclaration">
					<head type="tag">
						<tag>conventionDeclaration</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Convention Declaration</head>
						<item n="summary">A declaration of the rules or conventions, including
							authorized controlled vocabularies and thesauri, applied in creating the
							EAC-CPF instance.</item>
						<item n="description">
							<p>An optional element of <tag>control</tag> for declaring references in
								the <tag>citation</tag> element to any rules and conventions,
								including authorized controlled vocabularies or thesauri, applied in
								the construction of the description. For example,
									<tag>conventionDeclaration</tag> should be used to identify any
								controlled vocabularies appearing in the <att>vocabularySource</att>
								attribute for <tag>term</tag>, <tag>placeEntry</tag>, and
									<tag>placeRole</tag> elements. Any notes relating to how these
								rules or conventions have been used may be given within a
									<tag>descriptiveNote</tag> element. The <tag>abbreviation</tag>
								element may be used to identify the standard or controlled
								vocabulary in a coded structure.</p>
						</item>
						<item n="mayContain">abbreviation, citation, descriptiveNote</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:conventionDeclaration>
							<eac-cpf:abbreviation>AFNOR</eac-cpf:abbreviation>
							<eac-cpf:citation>AFNOR NFZ 44-060 (decembre 1986)</eac-cpf:citation>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Indexation conforme à la norme AFNOR NFZ 44-060 (decembre
									1986) Catalogage : forme et structure des vedettes de
									collectivites-auteurs Notice encodee conformement à la norme
									internationale de description archivistique contextuelle
									informatisee EAC 2004</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:conventionDeclaration>
						<eac-cpf:conventionDeclaration>
							<eac-cpf:citation>ISO 8601 - Data elements and interchange formats -
								Information interchange - Representation of dates and times, 2nd
								ed., Geneva: International Standards Organization,
								2000</eac-cpf:citation>
						</eac-cpf:conventionDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="cpfDescription">
					<head type="tag">
						<tag>cpfDescription</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Corporate Body, Person, or Family Description</head>
						<item n="summary">The broad area of the instance that describes the identity
							and context of the entity being described.</item>
						<item n="description">
							<p>This required wrapper element, which contains the bulk of the EAC-CPF
								instance, describes the identity and context of the entity being
								described. The <tag>cpfDescription</tag> includes a required
									<tag>identity</tag> element containing authorized and parallel
								name forms and optional <tag>description</tag> and
									<tag>relations</tag> sections to provide contextual information
								for the entity being described.</p>
							<p>An optional <tag>alternativeSet</tag> element allows the
								incorporation of two or more authority records derived from two or
								more authority systems. The <att>xml:id</att> attribute allows
								individual <tag>cpfDescription</tag> elements to be individually
								identified when using the <tag>multipleIdentities</tag>
								structure.</p>
						</item>
						<item n="mayContain">alternativeSet, description, identity, relations</item>
						<item n="mayOccurIn">eac-cpf, multipleIdentities</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1, 5.2, 5.3</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:cpfDescription>
							<eac-cpf:identity>[...] </eac-cpf:identity>
							<eac-cpf:description>[...] </eac-cpf:description>
							<eac-cpf:relations>[...]</eac-cpf:relations>
						</eac-cpf:cpfDescription>
					</egXML>
				</div>
				<div type="element" xml:id="cpfRelation">
					<head type="tag">
						<tag>cpfRelation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Corporate Body, Person, or Family Relation</head>
						<item n="summary">A corporate body, person, or family related to the
							described entity.</item>
						<item n="description">
							<p>The <tag>cpfRelation</tag> element contains the description of a
								corporate body, person, or family related to the described entity.
								Such related entities are typically described in another EAC-CPF
								instance or other encoding language such as MARC. Use the
									<tag>objectXMLWrap</tag> to incorporate XML elements from any
								XML namespace or <tag>objectBinWrap</tag> for base64-encoded binary
								data. A <tag>relationEntry</tag> element is provided for textual
								identification of the related entity.</p>
							<p>Use the <tag>date</tag>, <tag>dateRange</tag>, or <tag>dateSet</tag>
								elements for specifying the time period during which the
								relationship applied and the <tag>placeEntry</tag> element for
								recording relevant locative information. A
									<tag>descriptiveNote</tag> element may be included for a more
								detailed specification or explanation of the relationship.</p>
							<p>The <att>cpfRelationType</att> attribute may be used to specify the
								nature of the <tag>cpfRelation</tag> entity’s relationship to the
								entity described in the <tag>eac-cpf</tag> instance. Values are
								chosen from a closed list.</p>
						</item>
						<item n="mayContain">date, dateRange, dateSet, descriptiveNote,
							objectBinWrap, objectXMLWrap, placeEntry, relationEntry</item>
						<item n="mayOccurIn">relations</item>
						<item n="attributes">
							<list>
								<label>cpfRelationType</label>
								<item>Optional</item>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:cpfRelation cpfRelationType="hierarchical-parent"
							xlink:href="FRDAFANCH00MC_NAETUDE_110" xlink:type="simple">
							<eac-cpf:relationEntry>Etude notariale CX</eac-cpf:relationEntry>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1609-07-04">4 juillet
									1609</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1640-07-07">7 juillet
									1640</eac-cpf:toDate>
							</eac-cpf:dateRange>
						</eac-cpf:cpfRelation>
					</egXML>
				</div>
				<div type="element" xml:id="date">
					<head type="tag">
						<tag>date</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Date</head>
						<item n="summary">The single date of an event in the history of, or a
							relationship with, the person, family, or corporate body being described
							in the EAC-CPF instance.</item>
						<item n="description">
							<p>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 <tag>dateRange</tag>
								element, while more complex dates (combining singles dates and date
								ranges) can be expressed in <tag>dateSet</tag>.</p>
							<p>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 <att>standardDate</att> attribute, formulated according to ISO
								8601. Other attributes include <att>notBefore</att> and
									<att>notAfter</att> for dates of uncertainty. The
									<att>localType</att> attribute can be used to supply a more
								specific characterization of the date.</p>
							<p>Dates of existence for the entity being described in the EAC-CPF
								instance are encoded with the <tag>existDates</tag> element, while
								the dates of use of a particular name of an entity are encoded in
									<tag>useDates</tag>. The date and time of a maintenance event in
								the history of the EAC-CPF instance are given in the
									<tag>eventDateTime</tag> element.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">chronItem, cpfRelation, dateSet, existDates, function,
							functionRelation, legalStatus, localControl, localDescription, mandate,
							occupation, place, resourceRelation, useDates</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>notAfter</label>
								<item>Optional</item>
								<label>notBefore</label>
								<item>Optional</item>
								<label>standardDate</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:date standardDate="1765-09-18">September 18, 1765</eac-cpf:date>
					</egXML>
				</div>
				<div type="element" xml:id="dateRange">
					<head type="tag">
						<tag>dateRange</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Date Range</head>
						<item n="summary">The date range of an event in the history of, or a
							relationship with, the person, family, or corporate body being described
							in the EAC-CPF instance.</item>
						<item n="description">
							<p>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. <tag>dateRange</tag>
								contains mandatory <tag>fromDate</tag> and <tag>toDate</tag> child
								elements. If the event or relationship has a single date use the
									<tag>date</tag> element, while more complex dates (combining
								single dates and date ranges) can be expressed in
								<tag>dateSet</tag>.</p>
							<p>The <att>localType</att> attribute can be used to supply a more
								specific characterization of the date.</p>
							<p>Dates of existence for the identity being described in the EAC-CPF
								instance are encoded with the <tag>existDates</tag> element, while
								the dates of use of a particular name of an identity are encoded in
									<tag>useDates</tag>. The date and time of a maintenance event in
								the history of the EAC-CPF instance are given in the
									<tag>eventDateTime</tag> element.</p>
						</item>
						<item n="mayContain">fromDate, toDate</item>
						<item n="mayOccurIn">chronItem, cpfRelation, dateSet, existDates, function,
							functionRelation, legalStatus, localControl, localDescription, mandate,
							occupation, place, resourceRelation, useDates</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:dateRange>
							<eac-cpf:fromDate standardDate="1765-09-18">September 18,
								1765</eac-cpf:fromDate>
							<eac-cpf:toDate standardDate="1846-06-01">June 1, 1846</eac-cpf:toDate>
						</eac-cpf:dateRange>
					</egXML>
				</div>
				<div type="element" xml:id="dateSet">
					<head type="tag">
						<tag>dateSet</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Date Set</head>
						<item n="summary">A grouping element that facilitates complex date
							expressions by being able to combine a set comprising single dates and
							date ranges, multiple single dates, or multiple date ranges.</item>
						<item n="description">
							<p>A grouping element to combine single dates and date ranges, multiple
								single dates, or multiple date ranges. The <tag>dateSet</tag>
								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 <tag>date</tag> and <tag>dateRange</tag>
								elements.</p>
						</item>
						<item n="mayContain">date, dateRange</item>
						<item n="mayOccurIn">cpfRelation, existDates, function, functionRelation,
							legalStatus, localDescription, mandate, occupation, place,
							resourceRelation, useDates</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:dateSet>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1928-09">1928
									settembre</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1930-08">1930 autunno</eac-cpf:toDate>
							</eac-cpf:dateRange>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1947">1947</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1949">1949</eac-cpf:toDate>
							</eac-cpf:dateRange>
						</eac-cpf:dateSet>
					</egXML>
				</div>
				<div type="element" xml:id="description">
					<head type="tag">
						<tag>description</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Description</head>
						<item n="summary">A wrapper for all of the content elements comprising
							description (as specified in the ISAAR (CPF) Description Area) of the
							entity described in the EAC-CPF instance.</item>
						<item n="description">
							<p>The elements that constitute <tag>description</tag> together permit
								descriptive information to be encoded in either structured or
								unstructured fashions, or in a combined approach.
									<tag>description</tag> accommodates encoding all of the data
								elements that comprise the Description Area of ISAAR (CPF) including
								historical, biographical, and genealogical information; legal status
								and mandates; functions, occupations, and activities, and the dates
								and places that further constrain those elements.</p>
						</item>
						<item n="mayContain">biogHist, existDates, function, functions,
							generalContext, languageUsed, languagesUsed, legalStatus, legalStatuses,
							localDescription, localDescriptions, mandate, mandates, occupation,
							occupations, place, places, structureOrGenealogy</item>
						<item n="mayOccurIn">cpfDescription</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:description>
							<eac-cpf:existDates>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1765-09-18">September 18,
										1765</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1846-06-01">June 1,
										1846</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:existDates>
							<eac-cpf:place>
								<eac-cpf:placeEntry altitude="389" latitude="46.140833"
									longitude="12.215556">Belluno</eac-cpf:placeEntry>
								<eac-cpf:placeRole>Birthplace</eac-cpf:placeRole>
								<eac-cpf:date standardDate="1765-09-18">September 18,
									1765</eac-cpf:date>
							</eac-cpf:place>
							<eac-cpf:biogHist>
								<eac-cpf:p>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 <eac-cpf:span
										localType="title" style="font-style:italic">II Trionfo della
										Santa Sede</eac-cpf:span>, 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.</eac-cpf:p>
							</eac-cpf:biogHist>
						</eac-cpf:description>
					</egXML>
				</div>
				<div type="element" xml:id="descriptiveNote">
					<head type="tag">
						<tag>descriptiveNote</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Descriptive Note</head>
						<item n="summary">A generic element that provides additional information and
							specifications, in textual form, concerning the descriptive element in
							which it is contained.</item>
						<item n="description">
							<p>A generic element available in a number of descriptive elements which
								can be used to provide any additional descriptive notes that might
								be appropriate. Notes must be contained in paragraphs (<tag>p</tag>)
								and any necessary formatting may be indicated by use of the
									<tag>span</tag> element within <tag>p</tag>.</p>
						</item>
						<item n="mayContain">p</item>
						<item n="mayOccurIn">conventionDeclaration, cpfRelation, existDates,
							function, functionRelation, functions, identity, languageDeclaration,
							languageUsed, languagesUsed, legalStatus, legalStatuses,
							localDescription, localDescriptions, localTypeDeclaration,
							maintenanceAgency, mandate, mandates, occupation, occupations, place,
							places, resourceRelation, setComponent, source</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:source xlink:href="http://www.icacds.org.uk/eng/ISAAAR(CPF)2ed.pdf"
							xlink:type="simple">
							<eac-cpf:sourceEntry>ISAAAR(CPF)</eac-cpf:sourceEntry>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Record created based on ISAAR(CPF) 2nd ed Example 5 -
									Person description</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:source>
					</egXML>
				</div>
				<div type="element" xml:id="eac-cpf">
					<head type="tag">
						<tag>eac-cpf</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Encoded Archival Context - Corporate Bodies, Persons, and
							Families</head>
						<item n="summary">The <tag>eac-cpf</tag> element defines a particular
							instance of a document encoded with the EAC-CPF XML Schema. It contains
							a required <tag>control</tag> and either a <tag>cpfDescription</tag> or
							a <tag>multipleIdentities</tag> element.</item>
						<item n="description">
							<p>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 <tag>control</tag> and either a
									<tag>cpfDescription</tag> or a <tag>multipleIndentities</tag>
								element.</p>
						</item>
						<item n="mayContain">control, cpfDescription, multipleIdentities</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:eac-cpf>
							<eac-cpf:control>[...]</eac-cpf:control>
							<eac-cpf:cpfDescription>[...]</eac-cpf:cpfDescription>
						</eac-cpf:eac-cpf>
						<eac-cpf:eac-cpf>
							<eac-cpf:control>[...]</eac-cpf:control>
							<eac-cpf:multipleIdentities>
								<eac-cpf:cpfDescription>[...]</eac-cpf:cpfDescription>
								<eac-cpf:cpfDescription>[...]</eac-cpf:cpfDescription>
							</eac-cpf:multipleIdentities>
						</eac-cpf:eac-cpf>
					</egXML>
				</div>
				<div type="element" xml:id="entityId">
					<head type="tag">
						<tag>entityId</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Entity Identifier</head>
						<item n="summary">Any formal identifier used to designate the entity being
							described.</item>
						<item n="description">
							<p>An optional element of <tag>identity</tag> which may be used to
								record any identifier associated with the entity being described in
								the EAC-CPF instance. Identifiers such as legal identifiers,
								typically assigned by an authoritative agency, may be recorded in
								this element.</p>
							<p>Do not confuse with <tag>recordId</tag> within <tag>control</tag>,
								which refers to an identifier for the EAC-CPF instance rather than
								the entity it describes.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">identity</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.6</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:identity>
							<eac-cpf:entityId>CLU-SC-000008</eac-cpf:entityId>
							<eac-cpf:entityType>person</eac-cpf:entityType>
							<eac-cpf:nameEntry>
								<eac-cpf:part>Brown, Bob, 1886-1959</eac-cpf:part>
								<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
								<eac-cpf:alternativeForm>ncafnor</eac-cpf:alternativeForm>
							</eac-cpf:nameEntry>
							<eac-cpf:nameEntry>
								<eac-cpf:part>Brown, Robert Carlton (1886-1959)</eac-cpf:part>
								<eac-cpf:authorizedForm>ncafnor</eac-cpf:authorizedForm>
								<eac-cpf:alternativeForm>AACR2</eac-cpf:alternativeForm>
							</eac-cpf:nameEntry>
						</eac-cpf:identity>
					</egXML>
				</div>
				<div type="element" xml:id="entityType">
					<head type="tag">
						<tag>entityType</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Entity Type</head>
						<item n="summary">The type of entity being described. Values available are:
							person, corporateBody, or family.</item>
						<item n="description">
							<p>Within <tag>identity</tag> this mandatory element specifies the type
								of entity being described in the EAC-CPF instance. Values available
								are: person, corporateBody, or family.</p>
						</item>
						<item n="mayContain">"person" or "corporateBody" or "family"</item>
						<item n="mayOccurIn">identity</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.1</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:entityType>corporateBody</eac-cpf:entityType>
						<eac-cpf:entityType>person</eac-cpf:entityType>
						<eac-cpf:entityType>family</eac-cpf:entityType>
					</egXML>
				</div>
				<div type="element" xml:id="event">
					<head type="tag">
						<tag>event</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Event</head>
						<item n="summary">An element used to encode an event associated with a date
							and, optionally, a place within a structured chronology.</item>
						<item n="description">
							<p>The element contains discursive text identifying the event described
								by the <tag>chronItem</tag>. Every <tag>event</tag> must have an
								associated <tag>date</tag> element, and it may also have an optional
									<tag>placeEntry</tag> element, all wrapped within a
									<tag>chronItem</tag> describing the event in a chronology.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">chronItem</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:chronList>
							<eac-cpf:chronItem>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1944">1944</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1947">1947</eac-cpf:toDate>
								</eac-cpf:dateRange>
								<eac-cpf:event>Summer employment at Minnesota Valley Canning
									Co.</eac-cpf:event>
								<eac-cpf:placeEntry>Blue Earth (Minn.)</eac-cpf:placeEntry>
							</eac-cpf:chronItem>
							<eac-cpf:chronItem>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1946">1946</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1948">1948</eac-cpf:toDate>
								</eac-cpf:dateRange>
								<eac-cpf:event>Macalester College</eac-cpf:event>
								<eac-cpf:placeEntry>St. Paul (Minn.)</eac-cpf:placeEntry>
							</eac-cpf:chronItem>
							<eac-cpf:chronItem>
								<eac-cpf:date standardDate="1948">1948</eac-cpf:date>
								<eac-cpf:event>Campaign Manager, 2nd District, State
									Democratic-Farmer-Labor Central Committee. Report to Orville
									Freeman.</eac-cpf:event>
							</eac-cpf:chronItem>
						</eac-cpf:chronList>
					</egXML>
				</div>
				<div type="element" xml:id="eventDateTime">
					<head type="tag">
						<tag>eventDateTime</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Event Date and Time</head>
						<item n="summary">The date and time of a maintenance event for the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A required element within the <tag>maintenanceEvent</tag>,
									<tag>eventDateTime</tag> 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
									<att>standardDateTime</att> attribute.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">maintenanceEvent</item>
						<item n="attributes">
							<list>
								<label>standardDateTime</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.6</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2009-11-30"/>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>Bill Stockting</eac-cpf:agent>
							<eac-cpf:eventDescription>Created from original in ISAAR (CPF), 2nd
								edition: example 10</eac-cpf:eventDescription>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="eventDesccription">
					<head type="tag">
						<tag>eventDescription</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Event Description</head>
						<item n="summary">The description of a maintenance event in the life of the
							EAC-CPF instance.</item>
						<item n="description">
							<p>An element within the <tag>maintenanceEvent</tag> element for
								describing the maintenance event. The element allows a full
								description of the maintenance event to be given alongside the basic
								definition of the event in the <tag>eventType</tag> element.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">maintenanceEvent</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.9</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2009-11-30"/>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>Bill Stockting</eac-cpf:agent>
							<eac-cpf:eventDescription>Created from original in ISAAR (CPF), 2nd
								edition: example 10</eac-cpf:eventDescription>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="eventType">
					<head type="tag">
						<tag>eventType</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Event Type</head>
						<item n="summary">The type of maintenance event for the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A required element within <tag>maintenanceEvent</tag> that identifies
								the type of event. The available values are: "created", "revised",
								"updated", "deleted", "derived", or "cancelled". A fuller discursive
								description of the event may be given in the optional
									<tag>eventDescription</tag> element.</p>
							<p>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 are 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.</p>
						</item>
						<item n="mayContain">"cancelled" or "created" or "deleted" or "derived" or
							"revised" or "updated"</item>
						<item n="mayOccurIn">maintenanceEvent</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.9</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2009-11-30"/>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>Bill Stockting</eac-cpf:agent>
							<eac-cpf:eventDescription>Created from original in ISAAR (CPF), 2nd
								edition: example 10</eac-cpf:eventDescription>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="existDates">
					<head type="tag">
						<tag>existDates</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Dates of Existence</head>
						<item n="summary">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.</item>
						<item n="description">
							<p>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 flourit for persons. <tag>existDates</tag> may
								contain actual or approximate dates expressed through its elements
									<tag>date</tag>, <tag>dateRange</tag>, or <tag>dateSet</tag>. A
									<tag>descriptiveNote</tag> may be included if a fuller
								explanation of the dates of existence is needed.</p>
							<p>Use the <tag>date</tag> element to record the date of a single event,
								such as a date of birth or date of incorporation. Use
									<tag>dateRange</tag> to encode a pair of inclusive dates. Use
									<tag>dateSet</tag> to encode more complex date expressions that
								intermix <tag>date</tag> and <tag>dateRange</tag> elements.</p>
							<p>Do not confuse with <tag>useDates</tag>, which is a child element of
									<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> and
								represents the dates of use for a particular name or set of
								names.</p>
						</item>
						<item n="mayContain">date, dateRange, dateSet, descriptiveNote</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.1</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:existDates>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1868">1868</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1936">1936</eac-cpf:toDate>
							</eac-cpf:dateRange>
						</eac-cpf:existDates>
					</egXML>
				</div>
				<div type="element" xml:id="fromDate">
					<head type="tag">
						<tag>fromDate</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">From Date</head>
						<item n="summary">The beginning date in a date range.</item>
						<item n="description">
							<p>The beginning date in a date range, <tag>fromDate</tag> 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 <att>standardDate</att> attribute. The
									<att>notBefore</att> and <att>notAfter</att> attributes may be
								used to indicate uncertainty.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">dateRange</item>
						<item n="attributes">
							<list>
								<label>notAfter</label>
								<item>Optional</item>
								<label>notBefore</label>
								<item>Optional</item>
								<label>standardDate</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:existDates>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1868">1868</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1936">1936</eac-cpf:toDate>
							</eac-cpf:dateRange>
						</eac-cpf:existDates>
					</egXML>
				</div>
				<div type="element" xml:id="function">
					<head type="tag">
						<tag>function</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Function</head>
						<item n="summary">An element that provides information about a function,
							activity, role, or purpose performed or manifested by the entity being
							described.</item>
						<item n="description">
							<p>A <tag>function</tag> element is a wrapper element used to encode an
								index term, using the child element <tag>term</tag>. Terms are used
								to identify the functions, processes, activities, tasks, or
								transactions performed by the EAC-CPF entity. They may be drawn from
								controlled vocabularies or may be natural language terms. Associated
								date or date range (<tag>date</tag>, <tag>dateRange</tag> or
									<tag>dateSet</tag>) and place(s) (<tag>placeEntry</tag>) may be
								included to further constrain the term’s meaning. A
									<tag>descriptiveNote</tag> may be included if a fuller textual
								explanation is needed.</p>
							<p>A single <tag>function</tag> element may be encoded directly within
									<tag>description</tag>. Alternatively, multiple
									<tag>function</tag> elements may be grouped within a
									<tag>functions</tag> wrapper that facilitates manipulating them
								as a group.</p>
							<p>Functions may alternatively be described in discursive form in
									<tag>biogHist</tag> (ISAAR (CPF) History 5.2.2). The
									<tag>function</tag> element should be used whenever separate
								semantic processing of information about functions is required.</p>
							<p>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
									<tag>functionRelation</tag> to point from the EAC-CPF entity to
								the related function description. In these systems, the
									<tag>function</tag> element will probably become redundant.</p>
						</item>
						<item n="mayContain">citation, date, dateRange, dateSet, descriptiveNote,
							placeEntry, term</item>
						<item n="mayOccurIn">description, functions</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.5</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:function>
							<eac-cpf:term>Estate ownership</eac-cpf:term>
							<eac-cpf:descriptiveNote>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).</eac-cpf:descriptiveNote>
						</eac-cpf:function>
					</egXML>
				</div>
				<div type="element" xml:id="functionRelation">
					<head type="tag">
						<tag>functionRelation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Function Relation</head>
						<item n="summary">A function related to the described entity.</item>
						<item n="description">
							<p>The <tag>functionRelation</tag> element contains the description of a
								function related to the described entity. Such related functions are
								typically described in another encoding language. Use
									<tag>objectXMLWrap</tag> to incorporate XML elements from any
								XML namespace or <tag>objectBinWrap</tag> for base64-encoded binary
								data. A <tag>relationEntry</tag> element is provided for textual
								identification of the related function.</p>
							<p>Use the <tag>date</tag>, <tag>dateRange</tag>, or <tag>dateSet</tag>
								elements for specifying when the relation applied and the
									<tag>placeEntry</tag> element for relevant locative information.
								A <tag>descriptiveNote</tag> element may be included for a more
								detailed specification or explanation of the relationship.</p>
							<p>The <att>functionRelationType</att> attribute is used to specify the
								nature of the relationship that exists between the function and the
									<tag>eac-cpf</tag> entity. Values are chosen from a closed
								list.</p>
						</item>
						<item n="mayContain">date, dateRange, dateSet, descriptiveNote,
							objectBinWrap, objectXMLWrap, placeEntry, relationEntry</item>
						<item n="mayOccurIn">relations</item>
						<item n="attributes">
							<list>
								<label>functionRelationType</label>
								<item>Optional</item>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISDF Chapter 6</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:functionRelation functionRelationType="performs">
							<eac-cpf:relationEntry>Alumni communication management, University of
								Glasgow</eac-cpf:relationEntry>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>The management of the University's communication with its
									alumni.</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:functionRelation>
					</egXML>
				</div>
				<div type="element" xml:id="functions">
					<head type="tag">
						<tag>functions</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Functions</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>function</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>functions</tag> element to group together one
								or more occurrences of <tag>function</tag> so that they can be
								manipulated as a package. A single <tag>function</tag> may stand
								alone or may be wrapped within <tag>functions</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 as one or more
									<tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, descriptiveNote, function, list, outline,
							p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.5</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:functions>
							<eac-cpf:function>
								<eac-cpf:term>Indigenous land rights plaintiff</eac-cpf:term>
							</eac-cpf:function>
							<eac-cpf:function>
								<eac-cpf:term>Indigenous arts administrator</eac-cpf:term>
							</eac-cpf:function>
						</eac-cpf:functions>
					</egXML>
				</div>
				<div type="element" xml:id="generalContext">
					<head type="tag">
						<tag>generalContext</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">General Context</head>
						<item n="summary">An element that encodes information about the general
							social and cultural context of the entity being described.</item>
						<item n="description">
							<p>The element <tag>generalContext</tag> may contain a <tag>list</tag>,
									<tag>outline</tag>, or <tag>p</tag> element to format
								information about the social, cultural, economic, political, and/or
								historical milieu in which the entity being described existed. The
								general context provides wide latitude to record contextual
								information not specifically accommodated by other
									<tag>description</tag> elements.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, list, outline, p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.8</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:generalContext>
							<eac-cpf:p>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.</eac-cpf:p>
						</eac-cpf:generalContext>
					</egXML>
				</div>
				<div type="element" xml:id="identity">
					<head type="tag">
						<tag>identity</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Identity</head>
						<item n="summary">A wrapper element for the name portion of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>
								<tag>identity</tag> is a container element grouping all the
								necessary elements to the name identification of the EAC-CPF
								instance. Within this element the <tag>entityType</tag> element is
								required and specifies the type of entity being described (i.e.,
								corporateBody, family, or person), and one or more
									<tag>nameEntry</tag> elements and / or one or more
									<tag>nameEntryParallel</tag> elements specifying names by which
								the entity is known. An optional <tag>entityId</tag> is available
								for any identifiers associated with the entity.</p>
							<p>All the names by which the entity being described in the EAC-CPF
								instance is known are provided within this element. Within
									<tag>identity</tag>, the names of the entity, whether authorized
								or alternatives, should be recorded in a <tag>nameEntry</tag>
								element. If there is more than one name for the entity, each of them
								should be recorded in a separate <tag>nameEntry</tag> element.</p>
							<p>In addition to needing to accommodate one or more names used for or
								by the entity, <tag>identity</tag> may accommodate two or more
								parallel names in different languages or scripts. In countries where
								there is more than one official language, such as Canada or
								Switzerland, names of entities are frequently provided in more than
								one language. Within <tag>identity</tag>, a
									<tag>nameEntryParallel</tag> element should be used to group two
								or more <tag>nameEntry</tag> elements that represent parallel forms
								of the name of the entity being described.</p>
							<p>Within <tag>identity</tag>, a <tag>descriptiveNote</tag> element may
								be used to record other information in a textual form that assists
								in the identification of the entity.</p>
						</item>
						<item n="mayContain">descriptiveNote, entityId, entityType, nameEntry,
							nameEntryParallel</item>
						<item n="mayOccurIn">cpfDescription</item>
						<item n="attributes">
							<list>
								<label>identityType</label>
								<item>Optional</item>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:identity>
							<eac-cpf:entityId>CLU-SC-000008</eac-cpf:entityId>
							<eac-cpf:entityType>person</eac-cpf:entityType>
							<eac-cpf:nameEntry>
								<eac-cpf:part>Brown, Bob</eac-cpf:part>
								<eac-cpf:useDates>
									<eac-cpf:dateRange>
										<eac-cpf:fromDate standardDate="1886"
											>1886</eac-cpf:fromDate>
										<eac-cpf:toDate standardDate="1959">1959</eac-cpf:toDate>
									</eac-cpf:dateRange>
								</eac-cpf:useDates>
								<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
							</eac-cpf:nameEntry>
							<eac-cpf:nameEntry>
								<eac-cpf:part>Brown, Robert Carlton</eac-cpf:part>
								<eac-cpf:useDates>
									<eac-cpf:dateRange>
										<eac-cpf:fromDate standardDate="1886"
											>1886</eac-cpf:fromDate>
										<eac-cpf:toDate standardDate="1959">1959</eac-cpf:toDate>
									</eac-cpf:dateRange>
								</eac-cpf:useDates>
								<eac-cpf:alternativeForm>AACR2</eac-cpf:alternativeForm>
							</eac-cpf:nameEntry>
						</eac-cpf:identity>
					</egXML>
				</div>
				<div type="element" xml:id="item">
					<head type="tag">
						<tag>item</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Item</head>
						<item n="summary">A formatting element that encodes the individual entries
							comprising lists.</item>
						<item n="description">
							<p>The <tag>item</tag> element is used for general lists within
								descriptive elements and within levels in an outline. Do not confuse
								with <tag>chronItem</tag>, which encodes entries within a structured
								chronology, <tag>chronList</tag>.</p>
						</item>
						<item n="mayContain">[text], span</item>
						<item n="mayOccurIn">level, list</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:list>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">1450-1950</eac-cpf:span>
								(1929)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Globe Gliding</eac-cpf:span>
								(1930)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Gems</eac-cpf:span> (1931) </eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Words</eac-cpf:span>
								(1931)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Demonics</eac-cpf:span>
								(1931)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Can We
									Co-operate</eac-cpf:span> (1942)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Amazing
									Amazon</eac-cpf:span> (1942) </eac-cpf:item>
						</eac-cpf:list>
						<eac-cpf:outline>
							<eac-cpf:level>
								<eac-cpf:item>I.</eac-cpf:item>
							</eac-cpf:level>
							<eac-cpf:level>
								<eac-cpf:item>II.</eac-cpf:item>
								<eac-cpf:level>
									<eac-cpf:item>A.</eac-cpf:item>
								</eac-cpf:level>
								<eac-cpf:level>
									<eac-cpf:item>B.</eac-cpf:item>
									<eac-cpf:level>
										<eac-cpf:item>1.</eac-cpf:item>
									</eac-cpf:level>
									<eac-cpf:level>
										<eac-cpf:item>2.</eac-cpf:item>
									</eac-cpf:level>
								</eac-cpf:level>
							</eac-cpf:level>
						</eac-cpf:outline>
					</egXML>
				</div>
				<div type="element" xml:id="language">
					<head type="tag">
						<tag>language</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Language</head>
						<item n="summary">The specification of a particular language used in the
							EAC-CPF instance or in the creative work of the entity being
							described.</item>
						<item n="description">
							<p>A required element within <tag>languageDeclaration</tag> that gives
								the main language in which the EAC-CPF instance is written.</p>
							<p>A required element within <tag>languageUsed</tag> that gives the
								language or languages used by the entity being described.</p>
							<p>The content of the <att>languageCode</att> attribute must be given in
								the form of valid code from ISO 639-2b.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">languageDeclaration, languageUsed</item>
						<item n="attributes">
							<list>
								<label>languageCode</label>
								<item>Required</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.7</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:languageDeclaration>
							<eac-cpf:language languageCode="eng">English</eac-cpf:language>
							<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
						</eac-cpf:languageDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="languageDeclaration">
					<head type="tag">
						<tag>languageDeclaration</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Language Declaration</head>
						<item n="summary">The declaration of the predominant language and script
							used in the EAC-CPF instance.</item>
						<item n="description">
							<p>A wrapper element within <tag>control</tag> that declares the primary
								language and script in which an EAC-CPF instance is written in the
								required <tag>language</tag> and <tag>script</tag> elements. Any
								comments about the languages and scripts in which the EAC-CPF
								instance is written may be included in the optional
									<tag>descriptiveNote</tag> element.</p>
						</item>
						<item n="mayContain">descriptiveNote, language, script</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.7</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:languageDeclaration>
							<eac-cpf:language languageCode="eng">English</eac-cpf:language>
							<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
						</eac-cpf:languageDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="languageUsed">
					<head type="tag">
						<tag>languageUsed</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Language Used</head>
						<item n="summary">The language and script used by the entity being
							described.</item>
						<item n="description">
							<p>
								<tag>languageUsed</tag> is an element within <tag>description</tag>
								used to indicate the language and script in which the entity being
								described was creative or productive. A <tag>language</tag> element
								should be used to specify the language and a corresponding
									<tag>script</tag> element for the script.</p>
							<p>Do not confuse with <tag>languageDeclaration</tag> which refers to
								the language and script of the EAC-CPF instance.</p>
						</item>
						<item n="mayContain">descriptiveNote, language, script</item>
						<item n="mayOccurIn">description, languagesUsed</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:languageUsed>
							<eac-cpf:language languageCode="eng">English</eac-cpf:language>
							<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
						</eac-cpf:languageUsed>
					</egXML>
				</div>
				<div type="element" xml:id="languagesUsed">
					<head type="tag">
						<tag>languagesUsed</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Languages Used</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>languageUsed</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>languagesUsed</tag> element to group together
								one or more occurrences of <tag>languageUsed</tag> so that they can
								be manipulated as a package. A single <tag>languageUsed</tag> may be
								alone or may be wrapped within <tag>languagesUsed</tag>.</p>
						</item>
						<item n="mayContain">descriptiveNote, languageUsed</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:languagesUsed>
							<eac-cpf:languageUsed>
								<eac-cpf:language languageCode="eng">English</eac-cpf:language>
								<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
							</eac-cpf:languageUsed>
							<eac-cpf:languageUsed>
								<eac-cpf:language languageCode="spa">Spanish</eac-cpf:language>
								<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
							</eac-cpf:languageUsed>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Published works in English and Spanish.</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:languagesUsed>
					</egXML>
				</div>
				<div type="element" xml:id="legalStatus">
					<head type="tag">
						<tag>legalStatus</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Legal Status</head>
						<item n="summary"> An element used to encode information about the legal
							status of a corporate body.</item>
						<item n="description">
							<p>A <tag>legalStatus</tag> element is a wrapper element used to encode
								an index term, using the child element <tag>term</tag>. 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.</p>
							<p>Associated date or date range (<tag>date</tag>, <tag>dateRange</tag>
								or <tag>dateSet</tag>) and place(s) (<tag>placeEntry</tag>) may be
								included to further constrain the term's meaning. A
									<tag>descriptiveNote</tag> element may be included if fuller
								textual explanation is needed.</p>
							<p> A single <tag>legalStatus</tag> may be encoded directly within
									<tag>description</tag>. Alternatively, multiple
									<tag>legalStatus</tag> elements may be grouped within a
									<tag>legalStatuses</tag> wrapper that facilitates manipulating
								them as a group.</p>
							<p>Legal statuses may alternatively be described in discursive form in
								the <tag>biogHist</tag> (ISAAR (CPF) History 5.2.2). The
									<tag>legalStatus</tag> element should be used whenever separate
								semantic processing of information about legal statuses is
								required.</p>
						</item>
						<item n="mayContain">citation, date, dateRange, dateSet, descriptiveNote,
							placeEntry, term</item>
						<item n="mayOccurIn">description, legalStatuses</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.4</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:legalStatus>
							<eac-cpf:term>Department of State</eac-cpf:term>
						</eac-cpf:legalStatus>
						<eac-cpf:legalStatus>
							<eac-cpf:term>Organismo de la Administracion Central del
								Estado</eac-cpf:term>
							<eac-cpf:date standardDate="1769">1769</eac-cpf:date>
						</eac-cpf:legalStatus>
					</egXML>
				</div>
				<div type="element" xml:id="legalStatuses">
					<head type="tag">
						<tag>legalStatuses</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Legal Statuses</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>legalStatus</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>legalStatuses</tag> to group together one or
								more occurrences of <tag>legalStatus</tag> so that they can be
								manipulated as a package. A single <tag>legalStatus</tag> may stand
								alone or may be wrapped within <tag>legalStatuses</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, descriptiveNote, legalStatus, list, outline,
							p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.4</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:legalStatuses>
							<eac-cpf:legalStatus>
								<eac-cpf:term>Private limited liability company</eac-cpf:term>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1941">1941</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1948">1948</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:legalStatus>
							<eac-cpf:legalStatus>
								<eac-cpf:term>Public limited liability company</eac-cpf:term>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1948">1948</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="2006">2006</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:legalStatus>
							<eac-cpf:legalStatus>
								<eac-cpf:term>Private limited liability company</eac-cpf:term>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="2006">2006</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="2008">2008</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:legalStatus>
						</eac-cpf:legalStatuses>
						<eac-cpf:legalStatuses>
							<eac-cpf:legalStatus>
								<eac-cpf:term>EPIC</eac-cpf:term>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate notBefore="1946-04">avril
										1946</eac-cpf:fromDate>
									<eac-cpf:toDate notAfter="2004-11">novembre
										2004</eac-cpf:toDate>
								</eac-cpf:dateRange>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>Établissement public à caractère industriel et
										commercial</eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:legalStatus>
							<eac-cpf:legalStatus>
								<eac-cpf:term>SA</eac-cpf:term>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate notBefore="2004-11">novembre
										2004</eac-cpf:fromDate>
									<eac-cpf:toDate/>
								</eac-cpf:dateRange>
								<eac-cpf:descriptiveNote>
									<eac-cpf:p>Société anonyme à capitaux publics</eac-cpf:p>
								</eac-cpf:descriptiveNote>
							</eac-cpf:legalStatus>
						</eac-cpf:legalStatuses>
					</egXML>
				</div>
				<div type="element" xml:id="level">
					<head type="tag">
						<tag>level</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Level</head>
						<item n="summary">A required element for <tag>outline</tag> which delineates
							the outline format.</item>
						<item n="description">
							<p>Within an <tag>outline</tag>, multiple <tag>level</tag> elements are
								used to indicate the hierarchical levels of information that
								comprise the outline. When more than one hierarchical level exists,
								successive <tag>level</tag> exists, successive <tag>level</tag>
								elements are nested recursively to identify the layers of content.
								Each <tag>level</tag>, in turn, contains one ore more
									<tag>item</tag> elements that convey the information content of
								the outline.</p>
						</item>
						<item n="mayContain">item, level</item>
						<item n="mayOccurIn">level, outline</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:outline>
							<eac-cpf:level>
								<eac-cpf:item>I.</eac-cpf:item>
							</eac-cpf:level>
							<eac-cpf:level>
								<eac-cpf:item>II.</eac-cpf:item>
								<eac-cpf:level>
									<eac-cpf:item>A.</eac-cpf:item>
								</eac-cpf:level>
								<eac-cpf:level>
									<eac-cpf:item>B.</eac-cpf:item>
									<eac-cpf:level>
										<eac-cpf:item>1.</eac-cpf:item>
									</eac-cpf:level>
									<eac-cpf:level>
										<eac-cpf:item>2.</eac-cpf:item>
									</eac-cpf:level>
								</eac-cpf:level>
							</eac-cpf:level>
						</eac-cpf:outline>
					</egXML>
				</div>
				<div type="element" xml:id="list">
					<head type="tag">
						<tag>list</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">List</head>
						<item n="summary">A wrapper element to encode a simple list consisting of
							one or more <tag>item</tag> elements.</item>
						<item n="description">
							<p>The <tag>list</tag> element is used for general lists that can be
								embedded with a large number of descriptive elements. Lists are
								comprised of one or more <tag>item</tag> elements. Do not confuse
								with <tag>chronList</tag>, which encodes a structured
								chronology.</p>
						</item>
						<item n="mayContain">item</item>
						<item n="mayOccurIn">biogHist, functions, generalContext, legalStatuses,
							localDescriptions, mandates, occupations, places,
							structureOrGenealogy</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:list>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">1450-1950</eac-cpf:span>
								(1929)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Globe Gliding</eac-cpf:span>
								(1930)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Gems</eac-cpf:span> (1931) </eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Words</eac-cpf:span>
								(1931)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Demonics</eac-cpf:span>
								(1931)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Can We
									Co-operate</eac-cpf:span> (1942)</eac-cpf:item>
							<eac-cpf:item>
								<eac-cpf:span style="font-style:italic">Amazing
									Amazon</eac-cpf:span> (1942) </eac-cpf:item>
						</eac-cpf:list>
					</egXML>
				</div>
				<div type="element" xml:id="localControl">
					<head type="tag">
						<tag>localControl</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Local Control</head>
						<item n="summary">Any additional control entry necessary to accommodate
							local practice.</item>
						<item n="description">
							<p>An element used to record and define any control information
								necessary to accommodate local practice, in addition to the elements
								otherwise made available within <tag>control</tag>. The value of the
								entry may be given in a <tag>term</tag> element and an associated
								date can be given either as a single date (<tag>date</tag>) or a
								date range (<tag>dateRange</tag>).</p>
							<p>The type of entry must be defined using the <att>localType</att>
								attribute.</p>
						</item>
						<item n="mayContain">date, dateRange, term</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Required</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:localControl localType="detailLevel">
							<eac-cpf:term>minimal</eac-cpf:term>
						</eac-cpf:localControl>
					</egXML>
				</div>
				<div type="element" xml:id="localDescription">
					<head type="tag">
						<tag>localDescription</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Local Description</head>
						<item n="summary">A means, within description, to extend the descriptive
							categories available in a local system. Its meaning will depend on the
							context in which it occurs.</item>
						<item n="description">
							<p>
								<tag>localDescription</tag> 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
									<tag>term</tag>, which may be drawn from controlled vocabularies
								or may be natural language terms. Associate date or date range
									(<tag>date</tag>, <tag>dateRange</tag> or <tag>dateSet</tag>)
								and place(s) (<tag>placeEntry</tag>) may be included to further
								constrain the term's meaning. A <tag>descriptiveNote</tag> may be
								included if a fuller textual explanation is needed.</p>
							<p>The <tag>localDescription</tag> element should be used whenever
								separate semantic process of the descriptive information is
								required. The type of entry must be defined using the
									<att>localType</att> attribute.</p>
						</item>
						<item n="mayContain">citation, date, dateRange, dateSet, descriptiveNote,
							placeEntry, term</item>
						<item n="mayOccurIn">description, localDescriptions</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Required</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:localDescription
							localType="http://....fr/eac-cpf/localType/nationalité">
							<eac-cpf:term
								vocabularySource="http://....fr/eac-cpf/localType/nationalité#French"
								>French</eac-cpf:term>
							<eac-cpf:placeEntry countryCode="FR"
								vocabularySource="http://....fr/registerOfFrenchPlaceNames#France"
								>France</eac-cpf:placeEntry>
						</eac-cpf:localDescription>
					</egXML>
				</div>
				<div type="element" xml:id="localDescriptions">
					<head type="tag">
						<tag>localDescriptions</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Local Descriptions</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>localDescription</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>localDescriptions</tag> element to group
								together one or more occurrences of <tag>localDescription</tag> so
								that they can be manipulated as a package. A single
									<tag>localDescription</tag> may stand alone or may be wrapped
								within <tag>localDescriptions</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> elements are used to accommodate greater
								complexity in expressing or representing the information being
								described. A simpler discursive may be encoded as one or more
									<tag>p</tag> elements.</p>
							<p>The type of entry must be defined using the <att>localType</att>
								attribute.</p>
						</item>
						<item n="mayContain">citation, list, localDescription, outline, p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Required</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:localDescriptions>
							<eac-cpf:localDescription
								localType="http://....fr/eac-cpf/localType/nationalité">
								<eac-cpf:term
									vocabularySource="http://....fr/eac-cpf/localType/nationalité#French"
									>French</eac-cpf:term>
								<eac-cpf:placeEntry countryCode="FR"
									vocabularySource="http://....fr/registerOfFrenchPlaceNames#France"
									>France</eac-cpf:placeEntry>
							</eac-cpf:localDescription>
							<eac-cpf:localDescription
								localType="http://....fr/eac-cpf/localType/citoyenneté">
								<eac-cpf:term
									vocabularySource="http://....fr/eac-cpf/localType/citoyenneté#French"
									>French</eac-cpf:term>
								<eac-cpf:placeEntry countryCode="FR"
									vocabularySource="http://....fr/registerOfFrenchPlaceNames#France"
									>France</eac-cpf:placeEntry>
							</eac-cpf:localDescription>
							<eac-cpf:localDescription
								localType="http://....fr/eac-cpf/localType/citoyenneté">
								<eac-cpf:term
									vocabularySource="http://....fr/eac-cpf/localType/citoyenneté#Brazil"
									>Brazil</eac-cpf:term>
								<eac-cpf:placeEntry countryCode="BR"
									vocabularySource="http://....fr/registerOfFrenchPlaceNames#France"
									>Brazil</eac-cpf:placeEntry>
							</eac-cpf:localDescription>
						</eac-cpf:localDescriptions>
					</egXML>
				</div>
				<div type="element" xml:id="localTypeDeclaration">
					<head type="tag">
						<tag>localTypeDeclaration</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Local Type Declaration</head>
						<item n="summary">
							<tag>localTypeDeclaration</tag> is used to declare any local conventions
							used in <att>localType</att> in the EAC-CPF instance.</item>
						<item n="description">
							<p>The <tag>localTypeDeclaration</tag> is available to declare the local
								conventions and controlled vocabularies used in <att>localType</att>
								in the EAC-CPF instance. The <tag>citation</tag> element must be
								used to site the resource that lists the used values (semantic scope
								and intention). Any notes relating to how rules or conventions have
								been used may be given within a <tag>descriptiveNote</tag> element.
								The <tag>abbreviation</tag> element may be used to identify the
								standard or controlled vocabulary in a coded structure.</p>
						</item>
						<item n="mayContain">abbreviation, citation, descriptiveNote</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:localTypeDeclaration>
							<eac-cpf:abbreviation>Categorycodes</eac-cpf:abbreviation>
							<eac-cpf:citation
								xlink:href="http://nad.ra.se/static/termlistor/Kategorikoder.htm"
								xlink:type="simple">The categorycodes used in Swedish NAD
								(http://nad.ra.se). Used in element function</eac-cpf:citation>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Codes for categorizing different types of authority
									records through organizational form, operation, function,
									archivalorganization etcetera. </eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:localTypeDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="maintenanceAgency">
					<head type="tag">
						<tag>maintenanceAgency</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Agency</head>
						<item n="summary">The institution or service responsible for the creation,
							maintenance, and/or dissemination of the EAC-CPF instance.</item>
						<item n="description">
							<p>A required element within <tag>control</tag> for wrapping information
								about the institution or service responsible for the creation,
								maintenance, and/or dissemination of the EAC-CPF instance.</p>
							<p>This must include the <tag>agencyName</tag> element and it is
								recommended to include the optional <tag>agencyCode</tag> and / or
									<tag>otherAgencyCode</tag> elements as well to unambiguously
								identify the institution or service. Additional local institutional
								codes are given in <tag>otherAgencyCode</tag>. Any general
								information about the institution in relation to the EAC-CPF
								instance may also be given in a <tag>descriptiveNote</tag>
								element.</p>
						</item>
						<item n="mayContain">agencyCode, agencyName, descriptiveNote,
							otherAgencyCode</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.2</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceAgency>
							<eac-cpf:agencyCode>FR-DAF</eac-cpf:agencyCode>
							<eac-cpf:agencyName>Archives nationales (Paris)</eac-cpf:agencyName>
						</eac-cpf:maintenanceAgency>
						<eac-cpf:maintenanceAgency>
							<eac-cpf:otherAgencyCode>GB-058</eac-cpf:otherAgencyCode>
							<eac-cpf:agencyName>The British Library: Manuscript
								Collections</eac-cpf:agencyName>
						</eac-cpf:maintenanceAgency>
					</egXML>
				</div>
				<div type="element" xml:id="maintenanceEvent">
					<head type="tag">
						<tag>maintenanceEvent</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Event</head>
						<item n="summary">A maintenance event in the life of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A wrapper element within <tag>maintenanceHistory</tag> 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 each event must
								be defined in the <tag>eventType</tag> 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
									<tag>agent</tag> and <tag>agentType</tag> elements and when the
								event took place in the <tag>eventDateTime</tag> element. The event
								may also be described in the <tag>eventDescription</tag>
								element.</p>
						</item>
						<item n="mayContain">agent, agentType, eventDateTime, eventDescription,
							eventType</item>
						<item n="mayOccurIn">maintenanceHistory</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.6 and 5.4.9</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>derived</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2009-06-30T09:37:17.029-04:00"/>
							<eac-cpf:agentType>machine</eac-cpf:agentType>
							<eac-cpf:agent>XSLT ead2cpf.xsl/Saxon B9</eac-cpf:agent>
							<eac-cpf:eventDescription>Derived from EAD
								instance.</eac-cpf:eventDescription>
						</eac-cpf:maintenanceEvent>
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>revised</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2009-07-08"
								>2009-07-08</eac-cpf:eventDateTime>
							<eac-cpf:agentyType>human</eac-cpf:agentyType>
							<eac-cpf:agent>Claire Sibille</eac-cpf:agent>
							<eac-cpf:eventDescription>Notice convertie en EAC-CPF avec l'editeur
								oXygen</eac-cpf:eventDescription>
						</eac-cpf:maintenanceEvent>
						<eac-cpf:maintenanceEvent>
							<eac-cpf:eventType>created</eac-cpf:eventType>
							<eac-cpf:eventDateTime standardDateTime="2001-11-03"
								>2001-11/03</eac-cpf:eventDateTime>
							<eac-cpf:agentType>human</eac-cpf:agentType>
							<eac-cpf:agent>Lina Bountouri</eac-cpf:agent>
						</eac-cpf:maintenanceEvent>
					</egXML>
				</div>
				<div type="element" xml:id="maintenanceHistory">
					<head type="tag">
						<tag>maintenanceHistory</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance History</head>
						<item n="summary">The history of the creation and maintenance of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A required wrapper element within <tag>control</tag> to record the
								history and creation of the EAC-CPF instance. There must be at least
								one <tag>maintenanceEvent</tag> element, usually recording the
								creation of the instance, but there may be many other
									<tag>maintenanceEvent</tag> elements documenting the milestone
								events or activities in the maintenance of the instance.</p>
						</item>
						<item n="mayContain">maintenanceEvent</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.6, 5.4.9</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceHistory>
							<eac-cpf:maintenanceEvent>
								<eac-cpf:eventType>created</eac-cpf:eventType>
								<eac-cpf:eventDateTime
									standardDateTime="2009-06-29T00:20:00.000-00:00">29 giugno
									2009</eac-cpf:eventDateTime>
								<eac-cpf:agentType>human</eac-cpf:agentType>
								<eac-cpf:agent>Salvatore Vassallo</eac-cpf:agent>
								<eac-cpf:eventDescription>Prima codifica dell'espempio in italiano
									presente nelle ISAAR(CPF)</eac-cpf:eventDescription>
							</eac-cpf:maintenanceEvent>
							<eac-cpf:maintenanceEvent>
								<eac-cpf:eventType>revised</eac-cpf:eventType>
								<eac-cpf:eventDateTime
									standardDateTime="2009-06-29T17:16:00.000-00:00">29 giugno
									2009</eac-cpf:eventDateTime>
								<eac-cpf:agentType>human</eac-cpf:agentType>
								<eac-cpf:agent>Salvatore Vassallo</eac-cpf:agent>
								<eac-cpf:eventDescription>Aggiunte fonti, regole usate e campi di
									controllo</eac-cpf:eventDescription>
							</eac-cpf:maintenanceEvent>
						</eac-cpf:maintenanceHistory>
					</egXML>
				</div>
				<div type="element" xml:id="maintenanceStatus">
					<head type="tag">
						<tag>maintenanceStatus</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Maintenance Status</head>
						<item n="summary">The current drafting status of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>A required element within <tag>control</tag> 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
									<tag>maintenanceHistory</tag> element), the maintenance status
								should also be amended to reflect the current drafting status.</p>
							<p>On first creation the status would be "new", which on revision can be
								changed to "revised". Because it is important to be clear what has
								happened to records particularly when sharing and making links
								between them, a number of status values are available for records
								that are no longer current. A record that is simply deleted from a
								system can be given the status "deleted", but in cases where a
								record is marked as not current (obsolete or rejected) but kept for
								reference then it should be given the status "cancelled". If a
								record is deleted though because it has become superseded by two or
								more records then its status should be given as "deletedSplit",
								while if it has simply been replaced by a new record then
								"deletedReplaced" is the appropriate status value. A "derived"
								status value is available to indicate that the record was derived
								from another descriptive system.</p>
						</item>
						<item n="mayContain">"cancelled" or "deleted" or "deletedReplaced" or
							"deletedSplit" or "derived" or "new" or "revised"</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.4</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceStatus>new</eac-cpf:maintenanceStatus>
					</egXML>
				</div>
				<div type="element" xml:id="mandate">
					<head type="tag">
						<tag>mandate</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Mandate</head>
						<item n="summary">The source of authority or mandate for the corporate body
							in terms of its powers, functions, responsibilities or sphere of
							activities, such as a law, directive, or charter.</item>
						<item n="description">
							<p>A <tag>mandate</tag> element is a wrapper element used to encode an
								index term, using the child element, <tag>term</tag>. 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 (<tag>date</tag>, <tag>dateRange</tag>
								or <tag>dateSet</tag>) and place(s) (<tag>placeEntry</tag>) may be
								included to further constrain the term's meaning. A
									<tag>descriptiveNote</tag> element may be included if a fuller
								textual explanation is needed.</p>
							<p>A single <tag>mandate</tag> element may be encoded directly within
									<tag>description</tag>. Alternatively, multiple
									<tag>mandate</tag> elements may be grouped within
									<tag>mandates</tag>.</p>
						</item>
						<item n="mayContain">citation, date, dateRange, dateSet, descriptiveNote,
							placeEntry, term</item>
						<item n="mayOccurIn">description, mandates</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.6</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:mandate>
							<eac-cpf:term>Minnesota. Executive Session Laws 1919 c49</eac-cpf:term>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1919">1919</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1952">1925</eac-cpf:toDate>
							</eac-cpf:dateRange>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Board created in 1919 to receive and examine applications
									for bonuses from Minnesota soldiers.</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:mandate>
					</egXML>
				</div>
				<div type="element" xml:id="mandates">
					<head type="tag">
						<tag>mandates</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Mandates</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>mandate</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>mandates</tag> element to group together one or
								more occurrences of <tag>mandate</tag> so that they can be
								manipulated as a package. A single <tag>mandate</tag> may stand
								alone or may be wrapped within <tag>mandates</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, descriptiveNote, list, mandate, outline,
							p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.6</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:mandates>
							<eac-cpf:mandate>
								<eac-cpf:term>Instrucciones de 13-VI-1586 por las que se crean y
									definen las secretarias de Tierra y Mar.</eac-cpf:term>
							</eac-cpf:mandate>
							<eac-cpf:mandate>
								<eac-cpf:term>Real Decreto de Nueva Planta para el consejo de Guerra
									de 23-IV-1714.</eac-cpf:term>
							</eac-cpf:mandate>
							<eac-cpf:mandate>
								<eac-cpf:term>Real Decreto de Nueva Planta para el consejo de Guerra
									de 23-VIII-1715.</eac-cpf:term>
							</eac-cpf:mandate>
						</eac-cpf:mandates>
					</egXML>
				</div>
				<div type="element" xml:id="multipleIdentities">
					<head type="tag">
						<tag>multipleIdentities</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Multiple Identities</head>
						<item n="summary">A wrapper element used to group together more than one
								<tag>cpfDescription</tag> within a single EAC-CPF instance.</item>
						<item n="description">
							<p>A wrapper element used to encode more than one
									<tag>cpfDescription</tag> in a single EAC-CPF instance. The use
								of the <tag>multipleIdentities</tag> element can resolve two
								identity circumstances. First, it can be used to represent more than
								one identity (including official identities) of the same entity each
								with a separate <tag>cpfDescription</tag>. Second, it can be used to
								represent a collaborative identity which includes multiple
								individuals operating under a shared identity (such as a shared
								pseudonym).</p>
						</item>
						<item n="mayContain">cpfDescription</item>
						<item n="mayOccurIn">eac-cpf</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:multipleIdentities>
							<eac-cpf:cpfDescription>
								<eac-cpf:identity identityType="acquired" localType="pseudonyme">
									<eac-cpf:entityType>person</eac-cpf:entityType>
									<eac-cpf:nameEntry exml:lang="rus" scriptCode="Latn"
										transliteration="ISO9:1995">
										<eac-cpf:part localType="élément d'entrée"
											>Gorki</eac-cpf:part>
										<eac-cpf:part localType="autre élément"
											>Maksim</eac-cpf:part>
										<eac-cpf:useDates>
											<eac-cpf:dateRange>
												<eac-cpf:fromDate standardDate="1892"
												>1892</eac-cpf:fromDate>
												<eac-cpf:toDate standardDate="1936"
												>1936</eac-cpf:toDate>
											</eac-cpf:dateRange>
										</eac-cpf:useDates>
									</eac-cpf:nameEntry>
								</eac-cpf:identity>
								<eac-cpf:description>
									<eac-cpf:existDates>
										<eac-cpf:dateRange>
											<eac-cpf:fromDate standardDate="1868"
												>1868</eac-cpf:fromDate>
											<eac-cpf:toDate standardDate="1936"
												>1936</eac-cpf:toDate>
										</eac-cpf:dateRange>
									</eac-cpf:existDates>
									<eac-cpf:function>
										<eac-cpf:term>Romancier</eac-cpf:term>
									</eac-cpf:function>
									<eac-cpf:languageUsed>
										<eac-cpf:language languageCode="rus"
											>russe</eac-cpf:language>
										<eac-cpf:script scriptCode="Cyrl"/>
									</eac-cpf:languageUsed>
								</eac-cpf:description>
							</eac-cpf:cpfDescription>
							<eac-cpf:cpfDescription>
								<eac-cpf:identity identityType="given" localType="état civil">
									<eac-cpf:entityType>person</eac-cpf:entityType>
									<eac-cpf:nameEntry exml:lang="rus" scriptCode="Latn"
										transliteration="ISO9:1995">
										<eac-cpf:part localType="élément d'entrée"
											>Peškov</eac-cpf:part>
										<eac-cpf:part localType="autre élément">Aleksej
											Maksimovič</eac-cpf:part>
									</eac-cpf:nameEntry>
								</eac-cpf:identity>
								<eac-cpf:description>
									<eac-cpf:existDates>
										<eac-cpf:dateRange>
											<eac-cpf:fromDate standardDate="1868-03-28">28 mars
												1868</eac-cpf:fromDate>
											<eac-cpf:toDate standardDate="1936-06-18">18 juin
												1936</eac-cpf:toDate>
										</eac-cpf:dateRange>
									</eac-cpf:existDates>
									<eac-cpf:places>
										<eac-cpf:place>
											<eac-cpf:placeRole>naissance</eac-cpf:placeRole>
											<eac-cpf:placeEntry>Nijni-Novgorod
												(Russie)</eac-cpf:placeEntry>
										</eac-cpf:place>
										<eac-cpf:place>
											<eac-cpf:placeRole>déces</eac-cpf:placeRole>
											<eac-cpf:placeEntry>Gorki (Russie)</eac-cpf:placeEntry>
										</eac-cpf:place>
										<eac-cpf:place>
											<eac-cpf:placeRole>nationalité</eac-cpf:placeRole>
											<eac-cpf:placeEntry countryCode="SU">Union
												Soviétique</eac-cpf:placeEntry>
										</eac-cpf:place>
									</eac-cpf:places>
									<eac-cpf:biogHist>
										<eac-cpf:p>Élevé par son oncle maternel à Nijni-Novgorod.
											S'installe à Kazan en 1884. Autodidacte. Premiers
											contacts avec les milieux marxistes et populistes.
											Retour à Nijni-Novgorod en 1889 et première arrestation.
											Entame un premier voyage dans le sud de la Russie en
											1891 et s'installe à Tiflis (1891-1892), avant de
											revenir à Nijni-Novgorod (1893-1895 puis 1898). Arrêté
											un deuixème fois à Tiflis en 1898. Il se rend pour la
											première fois à Saint-Pétersbourg en 1899. Arrêté une 3e
											fois à Nijni-Novgorod en 1901, ce qui provoque une
											campagne de protestations. Entretient des liens d'amitié
											avec Cehov et Tol'stoj. Il apporte son soutien financier
											au Parti social-démocrate et se rapproche des Bolcheviks
											après 1905. Il s'exile à Capri de 1906 à 1913. Rentré en
											Russie en 1913, il s'exile de nouveau en 1921 en
											Allemagne puis en Italie en 1923. Il retourne
											définitivement en URSS en 1932.</eac-cpf:p>
									</eac-cpf:biogHist>
								</eac-cpf:description>
							</eac-cpf:cpfDescription>
						</eac-cpf:multipleIdentities>
					</egXML>
				</div>
				<div type="element" xml:id="nameEntry">
					<head type="tag">
						<tag>nameEntry</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Name Entry</head>
						<item n="summary">An element containing a name entry for a corporate body,
							person, or family. <tag>nameEntry</tag> is made up of one or more
								<tag>part</tag> elements so that the entity can be identified with
							certainty and distinguished from others bearing the same or similar
							names.</item>
						<item n="description">
							<p>Within <tag>identity</tag>, the element <tag>nameEntry</tag> is used
								to record a name by which the corporate body, the person, or the
								family described in the EAC-CPF instance is known.</p>
							<p>When <tag>nameEntry</tag> occurs within <tag>nameEntryParallel</tag>
								it is used to record two or more parallel forms (e.g., official
								forms of the name in different languages and/or scripts,
								transliterated forms of the name). When <tag>nameEntry</tag> is not
								included within <tag>nameEntryParallel</tag> it is used to record
								the authorized or alternative forms, whether standardized or
								not.</p>
							<p>Each form of the name is recorded in a separate <tag>nameEntry</tag>
								element.</p>
							<p>Each <tag>nameEntry</tag> should contain at least one <tag>part</tag>
								element. Within <tag>nameEntry</tag> each of the component parts of
								a name may be recorded in a separate <tag>part</tag> element.</p>
							<p>When <tag>nameEntry</tag> does not occur within
									<tag>nameEntryParallel</tag>, it may include two optional
								elements, <tag>authorizedForm</tag> and <tag>alternativeForm</tag>,
								to account more precisely for the status of the form of the name
								contained in the <tag>nameEntry</tag> element, as compared to other
								possible forms of the name contained in other <tag>nameEntry</tag>
								elements.</p>
							<p>The <tag>nameEntry</tag> element may also contain a
									<tag>useDates</tag> element to indicate the dates of use of the
								name, only when <tag>nameEntry</tag> is not included within
									<tag>nameEntryParallel</tag>.</p>
							<p>The attributes <att>scriptCode</att> and <att>xml:lang</att> are used
								to specify the script and the language of each of the names recorded
								in <tag>nameEntry</tag>.</p>
							<p>If the form of the name recorded in <tag>nameEntry</tag> is a
								transliterated one, the attribute <att>transliteration</att> is used
								to record the conventions or rules applied to transliterate this
								form of the name.</p>
						</item>
						<item n="mayContain">alternativeForm, authorizedForm, part, preferredForm,
							useDates</item>
						<item n="mayOccurIn">identity, nameEntryParallel</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.2, 5.1.3, 5.1.4, 5.1.5</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntry>
							<eac-cpf:part localType="surname">Lemoyne</eac-cpf:part>
							<eac-cpf:part localType="forename">Francois</eac-cpf:part>
							<eac-cpf:authorizedForm>AFNOR</eac-cpf:authorizedForm>
						</eac-cpf:nameEntry>
						<eac-cpf:nameEntry>
							<eac-cpf:part localType="surname">Lemoine</eac-cpf:part>
							<eac-cpf:part localType="forename">Francois</eac-cpf:part>
							<eac-cpf:alternativeForm>AFNOR</eac-cpf:alternativeForm>
						</eac-cpf:nameEntry>
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Bob</eac-cpf:part>
							<eac-cpf:useDates>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1886">1886</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1959">1959</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:useDates>
							<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
						</eac-cpf:nameEntry>
					</egXML>
				</div>
				<div type="element" xml:id="nameEntryParallel">
					<head type="tag">
						<tag>nameEntryParallel</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Name Entry Parallel</head>
						<item n="summary">A wrapper element for two or more <tag>nameEntry</tag>
							elements that represent parallel forms of the name.</item>
						<item n="description">
							<p>A container element used to group two or more <tag>nameEntry</tag>
								elements representing parallel forms of the name for the same entity
								(e.g., official forms of the name in different languages and/or
								scripts, transliterated forms of the name). All those forms should
								have the same status, either authorized or alternative. Two optional
								elements, <tag>authorizedForm</tag> or <tag>alternativeForm</tag>
								may be used to account more precisely for the status of the set of
								parallel name forms contained in <tag>nameEntryParallel</tag>. Do
								not use for pairing authorized and unauthorized forms of the same
								name (e.g., an authorized form with see references).</p>
							<p>The <tag>nameEntryParallel</tag> element may contain a
									<tag>useDates</tag> element to indicate the dates of use of the
								set of parallel name forms.</p>
						</item>
						<item n="mayContain">alternativeForm, authorizedForm, nameEntry,
							useDates</item>
						<item n="mayOccurIn">identity</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntryParallel>
							<eac-cpf:nameEntry exml:lang="fre" scriptCode="Latn">
								<eac-cpf:part>Institut international des droits de
									l'homme</eac-cpf:part>
								<eac-cpf:preferredForm>AFNOR_Z44-060</eac-cpf:preferredForm>
							</eac-cpf:nameEntry>
							<eac-cpf:nameEntry exml:lang="eng" scriptCode="Latn">International
								institute of human rights</eac-cpf:nameEntry>
							<eac-cpf:nameEntry exml:lang="spa" scriptCode="Latn">
								<eac-cpf:part>Instituto internacional de derechos
									humanos</eac-cpf:part>
							</eac-cpf:nameEntry>
							<eac-cpf:authorizedForm>AFNOR_Z44-060</eac-cpf:authorizedForm>
						</eac-cpf:nameEntryParallel>
					</egXML>
				</div>
				<div type="element" xml:id="objectBinWrap">
					<head type="tag">
						<tag>objectBinWrap</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Object Bin Wrap</head>
						<item n="summary">This element provides a place for a base64-encoded binary
							representation of a resource.</item>
						<item n="description">
							<p>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.</p>
						</item>
						<item n="mayContain">base64Binary</item>
						<item n="mayOccurIn">cpfRelation, functionRelation, resourceRelation,
							setComponent, source</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:objectBinWrap> [Base64 Binary code] </eac-cpf:objectBinWrap>
					</egXML>
				</div>
				<div type="element" xml:id="objectXMLWrap">
					<head type="tag">
						<tag>objectXMLWrap</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Object XML Wrap</head>
						<item n="summary">A place for incorporating XML elements from any XML
							namespace.</item>
						<item n="description">
							<p>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.</p>
						</item>
						<item n="mayContain">any element from any namespace</item>
						<item n="mayOccurIn">cpfRelation, functionRelation, resourceRelation,
							setComponent, source</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:objectXMLWrap>
							<mods:mods xmlns:mods="http://www.loc.gov/mods/v3"
								xmlns:xsi="http://www..w3.org/2001/XMLSchema-instance"
								xsi:schemaLocation="http://www.loc.gov/mods/v3/mods-3-3.xsd">
								<mods:titleInfo>
									<mods:title>Artisti trentini tra le due guerre</mods:title>
								</mods:titleInfo>
								<mods:name>
									<mods:namePart type="given">Nicoletta</mods:namePart>
									<mods:namePart type="family">Boschiero</mods:namePart>
									<mods:role>
										<mods:roleTerm type="text">autore</mods:roleTerm>
									</mods:role>
								</mods:name>
							</mods:mods>
						</eac-cpf:objectXMLWrap>
					</egXML>
				</div>
				<div type="element" xml:id="occupation">
					<head type="tag">
						<tag>occupation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Occupation</head>
						<item n="summary">An element that provides information about the occupation
							of the entity being described.</item>
						<item n="description">
							<p>An <tag>occupation</tag> element is a wrapper element used to encode
								an index term, using the child element <tag>term</tag>. Terms are
								used to identify an occupation held by the EAC-CPF entity. Terms may
								be drawn from controlled vocabularies or may be natural language
								terms. Associated date or date range (<tag>date</tag>,
									<tag>dateRange</tag> or <tag>dateSet</tag>) and place(s)
									(<tag>placeEntry</tag>) may be included to further constrain the
								term's meaning. A <tag>descriptiveNote</tag> element may be included
								if a fuller textual explanation needed.</p>
							<p>A single <tag>occupation</tag> element may be encoded directly within
									<tag>description</tag>. Alternatively, multiple
									<tag>occupation</tag> elements may be grouped within a
									<tag>occupations</tag> wrapper that facilitates manipulating
								them as a group.</p>
							<p>Occupations may alternatively be described in discursive form in
									<tag>biogHist</tag> (ISAAR (CPF) History 5.2.2). The
									<tag>occupation</tag> element should be used whenever separate
								semantic processing of information about occupations is
								required.</p>
						</item>
						<item n="mayContain">citation, date, dateRange, dateSet, descriptiveNote,
							placeEntry, term</item>
						<item n="mayOccurIn">description, occupations</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.5</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:occupation>
							<eac-cpf:term>Teacher</eac-cpf:term>
						</eac-cpf:occupation>
					</egXML>
				</div>
				<div type="element" xml:id="occupations">
					<head type="tag">
						<tag>occupations</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Occupations</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>occupation</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>occupations</tag> element to group together one
								or more occurrences of <tag>occupation</tag> so that they can be
								manipulated as a package. A single <tag>occupation</tag> may stand
								alone or may be wrapped within <tag>occupations</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, descriptiveNote, list, occupation, outline,
							p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.5</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:occupations>
							<eac-cpf:occupation>
								<eac-cpf:term>Teacher</eac-cpf:term>
							</eac-cpf:occupation>
							<eac-cpf:occupation>
								<eac-cpf:term>Railway labourer</eac-cpf:term>
							</eac-cpf:occupation>
						</eac-cpf:occupations>
					</egXML>
				</div>
				<div type="element" xml:id="otherAgencyCode">
					<head type="tag">
						<tag>otherAgencyCode</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Other Agency Code</head>
						<item n="summary">Alternate code representing the instituion or service
							responsible for the creation, maintenance, and/or dissemination of the
							EAC-CPF instance.</item>
						<item n="description">
							<p>An element of <tag>maintenanceAgency</tag> within <tag>control</tag>
								providing an alternative and/or local institution code representing
								the institution or service responsible for the creation, maintenace,
								and/or dissemination of the EAC-CPF instance to that given in the
									<tag>agencyCode</tag> element in the format of the International
								Standard identifier for Libraries and Related Organizations (ISIL:
								ISO 15511). The name of the agency is given in
								<tag>agencyName</tag>. The addition of an ISO 3166-1 alpha-2 country
								code as the prefix is recommended to ensure international
								uniqueness.</p>
						</item>
						<item n="mayContain">NMTOKEN</item>
						<item n="mayOccurIn">maintenanceAgency</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:maintenanceAgency>
							<eac-cpf:otherAgencyCode>GB-058</eac-cpf:otherAgencyCode>
							<eac-cpf:agencyName>The British Library: Manuscript
								Collections</eac-cpf:agencyName>
						</eac-cpf:maintenanceAgency>
					</egXML>
				</div>
				<div type="element" xml:id="otherRecordId">
					<head type="tag">
						<tag>otherRecordId</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Other Record Identifier</head>
						<item n="summary">Alternative record identifiers that may be associated with
							the EAC-CPF instance.</item>
						<item n="description">
							<p>An element in <tag>control</tag> for the provision of alternative
								record identifiers to the mandatory identifier in
									<tag>recordId</tag> that may be associated with the EAC-CPF
								instance. These might include the identifiers of merged EAC-CPF
								instances representing the same entity or those of records that are
								no longer current but had some part in the history and maintenance
								of the EAC-CPF instance.</p>
							<p>The <att>localType</att> 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
									<tag>maintenanceAgency</tag> element for this EAC-CPF
								instance.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:otherRecordId>ARC-ID-976172</eac-cpf:otherRecordId>
					</egXML>
				</div>
				<div type="element" xml:id="outline">
					<head type="tag">
						<tag>outline</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Outline</head>
						<item n="summary">An element used within the description area to encode
							information in an outline format.</item>
						<item n="description">
							<p>
								<tag>outline</tag> contains one or more <tag>level</tag> elements,
								which contain either <tag>item</tag> elements or further
									<tag>level</tag> elements in a hierarchical fashion.</p>
						</item>
						<item n="mayContain">level</item>
						<item n="mayOccurIn">biogHist, functions, generalContext, legalStatuses,
							localDescriptions, mandates, occupations, places,
							structureOrGenealogy</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:outline>
							<eac-cpf:level>
								<eac-cpf:item>I.</eac-cpf:item>
							</eac-cpf:level>
							<eac-cpf:level>
								<eac-cpf:item>II.</eac-cpf:item>
								<eac-cpf:level>
									<eac-cpf:item>A.</eac-cpf:item>
								</eac-cpf:level>
								<eac-cpf:level>
									<eac-cpf:item>B.</eac-cpf:item>
									<eac-cpf:level>
										<eac-cpf:item>1.</eac-cpf:item>
									</eac-cpf:level>
									<eac-cpf:level>
										<eac-cpf:item>2.</eac-cpf:item>
									</eac-cpf:level>
								</eac-cpf:level>
							</eac-cpf:level>
						</eac-cpf:outline>
					</egXML>
				</div>
				<div type="element" xml:id="p">
					<head type="tag">
						<tag>p</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Paragraph</head>
						<item n="summary">A generic element in the description area which marks one
							or more sentences that form a logical prose passage.</item>
						<item n="description">
							<p>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.</p>
							<p>The <tag>p</tag> element is an important textual feature, which must
								be used as part of any general description within a
									<tag>descriptiveNote</tag> element and may be used inside many
								of the descriptive elements within the description area. While it
								generally contains discursive text, it may also contain a
									<tag>span</tag> element to further stress or style specific
								character strings by particular formatting (such as italic or bold,
								etc.).</p>
						</item>
						<item n="mayContain">[text], span</item>
						<item n="mayOccurIn">biogHist, descriptiveNote, functions, generalContext,
							legalStatuses, localDescriptions, mandates, occupations, places,
							structureOrGenealogy</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:biogHist>
							<eac-cpf:p>Robert Carlton Brown (1886-1959) was a writer, editor,
								publisher, and traveler. From 1908 to 1917, he wrote poetry and
								prose for numerous magazines and newspapers in New York City,
								publishing two pulp novels, <eac-cpf:span style="font-style:italic"
									>What Happened to Mary</eac-cpf:span> and <eac-cpf:span
									style="font-style:italic">The Remarkable Adventures of
									Christopher Poe</eac-cpf:span> (1913), and one volume of poetry,
									<eac-cpf:span style="font-style:italic">My
									Marjonary</eac-cpf:span> (1916).</eac-cpf:p>
							<eac-cpf:p>During 1918, he traveled extensively in Mexico and Central
								America, writing for the U.S. Committee of Public Information in
								Santiago de Chile. In 1919, he moved with his wife, Rose Brown, to
								Rio de Janeiro, where they founded <eac-cpf:span
									style="font-style:italic">Brazilian American</eac-cpf:span>, a
								weekly magazine that ran until 1929. With Brown's mother, Cora, the
								Browns also established magazines in Mexico City and London:
									<eac-cpf:span style="font-style:italic">Mexican
									American</eac-cpf:span> (1924-1929) and <eac-cpf:span
									style="font-style:italic">British American</eac-cpf:span>
								(1926-1929).</eac-cpf:p>
						</eac-cpf:biogHist>
					</egXML>
				</div>
				<div type="element" xml:id="part">
					<head type="tag">
						<tag>part</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Part</head>
						<item n="summary">
							<tag>part</tag> is used to distinguish components of the name of the
							entity.</item>
						<item n="description">
							<p>Within <tag>nameEntry</tag> each of the component parts of a name,
								such as forename, surname, honorific title, may be recorded in a
								separate <tag>part</tag> element. <tag>part</tag> may also contain
								the full name of the entity when it is not possible to distinguish
								the different component parts of the name. The <tag>useDates</tag>
								element should be used for any date information associated with the
								name.</p>
							<p>The designation of the information contained in the <tag>part</tag>
								can be specified by the attribute <att>localType</att>.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">nameEntry</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntry>
							<eac-cpf:part localType="surname">Lemoyne</eac-cpf:part>
							<eac-cpf:part localType="forename">Francois</eac-cpf:part>
							<eac-cpf:authorizedForm>AFNOR</eac-cpf:authorizedForm>
						</eac-cpf:nameEntry>
					</egXML>
				</div>
				<div type="element" xml:id="place">
					<head type="tag">
						<tag>place</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Place</head>
						<item n="summary">An element that provides information about a place or
							jurisdiction where the EAC-CPF entity was based, lived, or with which it
							had some other significant connection.</item>
						<item n="description">
							<p>A <tag>place</tag> element is a wrapper element used to encode an
								index term, using the child element <tag>placeEntry</tag>. Terms are
								used to identify the places or jurisdictions where the EAC-CPF
								entity was based, lived, or with which it had some other significant
								connection. The <tag>placeRole</tag> element is available to specify
								the nature of the connection of the place with the entity being
								described, and its use is strongly recommended. Terms in
									<tag>placeEntry</tag> and <tag>placeRole</tag> may be drawn from
								controlled vocabularies or may be natural language terms. These
								controlled vocabularies can be identified with the
									<att>vocabularySource</att> attribute. Associated date or date
								range (<tag>date</tag>, <tag>dateRange</tag> or <tag>dateSet</tag>)
								information may be included to further constrain the term's meaning.
								An <tag>address</tag> element is also available for specifying a
								postal or other address. A <tag>descriptiveNote</tag> element may be
								included for more detailed specifications or explanation of the
								relation between the values.</p>
							<p>A single <tag>place</tag> element may be encoded directly within
									<tag>description</tag>. Alternatively, multiple <tag>place</tag>
								elements may be grouped within a <tag>places</tag> wrapper that
								facilitates manipulating them as a group.</p>
							<p>Places may alternatively be described in discursive form in
									<tag>biogHist</tag> (ISAAR (CPF) History 5.2.2). The
									<tag>place</tag> element should be used whenever separate
								semantic processing of information about places is required.</p>
						</item>
						<item n="mayContain">address, citation, date, dateRange, dateSet,
							descriptiveNote, placeEntry, placeRole</item>
						<item n="mayOccurIn">description, places</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:place>
							<eac-cpf:placeEntry>Paris, France</eac-cpf:placeEntry>
							<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
						</eac-cpf:place>
					</egXML>
				</div>
				<div type="element" xml:id="placeEntry">
					<head type="tag">
						<tag>placeEntry</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Place Entry</head>
						<item n="summary">An element used in both the description and relations
							areas to encode information about the place or jurisdiction where the
							EAC-CPF entity was based, lived, or with which it had some other
							significant connection.</item>
						<item n="description">
							<p>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 <tag>place</tag>, a companion
									<tag>placeRole</tag> is strongly recommended to describe the
								nature of the association of the place to the entity.</p>
							<p>
								<att>latitude</att>, <att>longitude</att>, and <att>altitude</att>
								attributes are available for specific geographical data. The
									<att>accuracy</att> attribute may be used to indicate
								uncertainty. The <att>vocabularySource</att> attribute may be used
								to indicate the controlled vocabulary from which the
									<tag>placeEntry</tag> term is derived.</p>
							<p>The <tag>placeEntry</tag> element is repeatable. It is strongly
								recommended that within <tag>place</tag>, the <tag>placeEntry</tag>
								element be repeated only to represent the same place name in various
								languages, with an accompanying <att>xml:lang</att> attribute.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">chronItem, cpfRelation, function, functionRelation,
							legalStatus, localDescription, mandate, occupation, place,
							resourceRelation</item>
						<item n="attributes">
							<list>
								<label>accuracy</label>
								<item>Optional</item>
								<label>altitude</label>
								<item>Optional</item>
								<label>countryCode</label>
								<item>Optional</item>
								<label>latitude</label>
								<item>Optional</item>
								<label>localType</label>
								<item>Optional</item>
								<label>longitude</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>vocabularySource</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:place>
							<eac-cpf:placeEntry>Paris, France</eac-cpf:placeEntry>
							<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
						</eac-cpf:place>
					</egXML>
				</div>
				<div type="element" xml:id="placeRole">
					<head type="tag">
						<tag>placeRole</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Place Role</head>
						<item n="summary">An element to identify the contextual role a place or
							jurisdiction has in relation to the EAC-CPF entity in <tag>place</tag>
							elements.</item>
						<item n="description">
							<p>
								<tag>placeRole</tag> provides a contextual role for a
									<tag>placeEntry</tag> within <tag>place</tag>. Places should be
								identified 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
									<tag>placeRole</tag> element in order to describe the nature of
								the association of the place to the entity.</p>
							<p>The <att>vocabularySource</att> attribute may be used to indicate the
								controlled vocabulary form which the <tag>placeRole</tag> term is
								derived.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">place</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>vocabularySource</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:place>
							<eac-cpf:placeEntry>Paris, France</eac-cpf:placeEntry>
							<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
						</eac-cpf:place>
					</egXML>
				</div>
				<div type="element" xml:id="places">
					<head type="tag">
						<tag>places</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Places</head>
						<item n="summary">A grouping element used to bundle together individual
								<tag>place</tag> elements.</item>
						<item n="description">
							<p>Use the optional <tag>places</tag> element to group together one or
								more occurrences of <tag>place</tag> so that they can be manipulated
								as a package. A single <tag>place</tag> may stand alone or may be
								wrapped within <tag>places</tag>.</p>
							<p>The optional <tag>citation</tag>, <tag>list</tag>, and
									<tag>outline</tag> 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 <tag>p</tag> elements.</p>
						</item>
						<item n="mayContain">citation, descriptiveNote, list, outline, p,
							place</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:places>
							<eac-cpf:place>
								<eac-cpf:placeEntry>Paris, France</eac-cpf:placeEntry>
								<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
							</eac-cpf:place>
							<eac-cpf:place>
								<eac-cpf:placeEntry>New York, N.Y.</eac-cpf:placeEntry>
								<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
							</eac-cpf:place>
							<eac-cpf:place>
								<eac-cpf:placeEntry>Riode Janeiro, Brazil</eac-cpf:placeEntry>
								<eac-cpf:placeRole>Residence</eac-cpf:placeRole>
							</eac-cpf:place>
						</eac-cpf:places>
						<eac-cpf:places>
							<eac-cpf:place>
								<eac-cpf:placeRole>naissance</eac-cpf:placeRole>
								<eac-cpf:placeEntry>Nijni-Novgorod (Russie)</eac-cpf:placeEntry>
							</eac-cpf:place>
							<eac-cpf:place>
								<eac-cpf:placeRole>déces</eac-cpf:placeRole>
								<eac-cpf:placeEntry>Gorki (Russie)</eac-cpf:placeEntry>
							</eac-cpf:place>
							<eac-cpf:place>
								<eac-cpf:placeRole>nationalité</eac-cpf:placeRole>
								<eac-cpf:placeEntry countryCode="SU">Union
									Soviétique</eac-cpf:placeEntry>
							</eac-cpf:place>
						</eac-cpf:places>
					</egXML>
				</div>
				<div type="element" xml:id="preferredForm">
					<head type="tag">
						<tag>preferredForm</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Preferred Form of Name</head>
						<item n="summary">An element used to indicate which of the parallel names
							recorded within <tag>nameEntryParallel</tag>, is the preferred one for
							display purposes in a given context.</item>
						<item n="description">
							<p>In cases where parallel names are encoded as multiple
									<tag>nameEntry</tag> elements within
									<tag>nameEntryParallel</tag>, a <tag>nameEntry</tag> may be
								chosen as preferred in a given context. The <tag>preferredForm</tag>
								element is used only when <tag>nameEntry</tag> occurs within
									<tag>nameEntryParallel</tag>. 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 <tag>nameEntry</tag>
								elements.</p>
							<p>The <tag>preferredForm</tag> 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
									<tag>preferredForm</tag> must be declared within the
									<tag>conventionDeclaration</tag> element in
								<tag>control</tag>.</p>
							<p>Within <tag>nameEntryParallel</tag>, <tag>preferredForm</tag> may
								occur simultaneously with <tag>authorizedForm</tag> elements. While
								the <tag>authorizedForm</tag>, when used within
									<tag>nameEntryParallel</tag>, qualifies collectively the set of
								the parallel forms recorded in the separate <tag>nameEntry</tag>
								elements, the <tag>preferredForm</tag> element is used specifically
								within the <tag>nameEntry</tag> elements to qualify the preferred
								form(s) of the name that an agency chooses to display.</p>
						</item>
						<item n="mayContain">NMTOKEN</item>
						<item n="mayOccurIn">nameEntry (only when it occurs within
							nameEntryParallel)</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.3</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntryParallel>
							<eac-cpf:nameEntry exml:lang="fre" scriptCode="Latn">
								<eac-cpf:part>Institut international des droits de
									l'homme</eac-cpf:part>
								<eac-cpf:preferredForm>AFNOR_Z44-060</eac-cpf:preferredForm>
							</eac-cpf:nameEntry>
							<eac-cpf:nameEntry exml:lang="eng" scriptCode="Latn">International
								institute of human rights</eac-cpf:nameEntry>
							<eac-cpf:nameEntry exml:lang="spa" scriptCode="Latn">
								<eac-cpf:part>Instituto internacional de derechos
									humanos</eac-cpf:part>
							</eac-cpf:nameEntry>
							<eac-cpf:authorizedForm>AFNOR_Z44-060</eac-cpf:authorizedForm>
						</eac-cpf:nameEntryParallel>
					</egXML>
				</div>
				<div type="element" xml:id="publicationStatus">
					<head type="tag">
						<tag>publicationStatus</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Publication Status</head>
						<item n="summary">The current publication status of the EAC-CPF
							instance.</item>
						<item n="description">
							<p>The current publication status of the EAC-CPF instance may be
								specified in the <tag>publicationStatus</tag> element. If according
								to local practice the instance is still in the process of being
								approved for publication, the value should be "inProcess," while if
								approved for publication, the value should be "approved."</p>
						</item>
						<item n="mayContain">"inProcess" or "approved"</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.4</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:publicationStatus>inProcess</eac-cpf:publicationStatus>
					</egXML>
				</div>
				<div type="element" xml:id="recordId">
					<head type="tag">
						<tag>recordId</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Record Identifier</head>
						<item n="summary">The unique identifier for a particular instance.</item>
						<item n="description">
							<p>A required element within <tag>control</tag> that designates a unique
								identifier for the EAC-CPF instance. The assigning owner ensures the
								uniqueness of the value within the EAC-CPF descriptive system under
								its control. The <tag>recordId</tag>, when used in combination with
								the content of the required <tag>agencyCode</tag> element within
									<tag>maintenanceAgency</tag>, will provide a globally unique
								identifier.</p>
							<p>Record alternate record identifiers if desired in
									<tag>otherRecordId</tag>.</p>
						</item>
						<item n="mayContain">NMTOKEN</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.1</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:recordId>F10219</eac-cpf:recordId>
					</egXML>
				</div>
				<div type="element" xml:id="relationEntry">
					<head type="tag">
						<tag>relationEntry</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Relation Entry</head>
						<item n="summary">A descriptive element for relations that provides
							discursive text.</item>
						<item n="description">
							<p>A descriptive element for relations that provides discursive text
								identifying a related entity, which may be either another name (CPF)
								entity, a resource created by or otherwise related to the named
								entity (e.g., archival records), or the name of a related
								function.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">cpfRelation, functionRelation, resourceRelation</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:functionRelation functionRelationType="performs">
							<eac-cpf:relationEntry>Alumni communication management, University of
								Glasgow</eac-cpf:relationEntry>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>The management of the University's communication with its
									alumni.</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:functionRelation>
					</egXML>
				</div>
				<div type="element" xml:id="relations">
					<head type="tag">
						<tag>relations</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Relations</head>
						<item n="summary">A wrapper element for grouping one or more specific
							relations.</item>
						<item n="description">
							<p>A wrapper element that groups together one or more relation elements,
								each of which denotes a specific relationship. Entities may have
								relationships with other corporate bodies, persons or families,
								which may be expressed using <tag>cpfRelation</tag>; functions,
								which may be expressed using <tag>functionRelation</tag>; or
								resources such as archival collections, bibliographic resources, or
								artifacts, which may be expressed using
								<tag>resourceRelation</tag>.</p>
						</item>
						<item n="mayContain">cpfRelation, functionRelation, resourceRelation</item>
						<item n="mayOccurIn">cpfDescription</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">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."</item>
						<item n="occurrence">0…1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:relations>
							<eac-cpf:cpfRelation>[...]</eac-cpf:cpfRelation>
							<eac-cpf:functionRelation>[...]</eac-cpf:functionRelation>
							<eac-cpf:resourceRelation>[...]</eac-cpf:resourceRelation>
						</eac-cpf:relations>
					</egXML>
				</div>
				<div type="element" xml:id="resourceRelation">
					<head type="tag">
						<tag>resourceRelation</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Resource Relation</head>
						<item n="summary">A resource related to the described entity.</item>
						<item n="description">
							<p>The <tag>resourceRelation</tag> element contains the description of a
								resource related to the described entity. Use
									<tag>objectXMLWrap</tag> to incorporate XML elements from any
								XML namespaces or <tag>objectBinWrap</tag> for base64-encoded binary
								data. A <tag>relationEntry</tag> element is provided for textual
								identification of the related resource.</p>
							<p>Use the <tag>date</tag>, <tag>dateRange</tag>, or <tag>dateSet</tag>
								elements for specifying when the relationship applied and the
									<tag>placeEntry</tag> element for relevant locative information.
								A <tag>descriptiveNote</tag> element may be included for a more
								detailed specifications or explanations of the relationship.</p>
							<p>The <att>resourceRelationType</att> attribute is used to specify the
								nature of the relationship between the resource and the entity
								described in the EAC-CPF instance.</p>
						</item>
						<item n="mayContain">date, dateRange, dateSet, descriptiveNote,
							objectBinWrap, objectXMLWrap, placeEntry, relationEntry</item>
						<item n="mayOccurIn">relations</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>resourceRelationType</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 6</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:resourceRelation resourceRelationType="creatorOf">
							<eac-cpf:objectXMLWrap>
								<example:ead xmlns:xsi="http://www.w3c.org/2001/XMLSchema-instance" xsi="urn:isbn:1-931666-22-9"
									xsi:schemaLocation="http://www.loc.gov/ead/ead.xsd">
									<example:eadheader>
										<example:eadid identifier="e4012531" mainagencycode="GB-0066"/>
										<example:filedesc>
											<example:titlestmt>
												<example:titleproper/>
											</example:titlestmt>
										</example:filedesc>
									</example:eadheader>
									<example:archdesc level="file">
										<example:did>
											<example:unitid repositorycode="GB-0066">E 40/12531</example:unitid>
											<example:unittitle>Attached seal, Andrew Noel</example:unittitle>
											<example:unitdate>1551-1552</example:unitdate>
											<example:physdesc>
												<example:genreform type="materialType">Seals</example:genreform>
											</example:physdesc>
										</example:did>
									</example:archdesc>
								</example:ead>
							</eac-cpf:objectXMLWrap>
						</eac-cpf:resourceRelation>
					</egXML>
				</div>
				<div type="element" xml:id="script">
					<head type="tag">
						<tag>script</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Script</head>
						<item n="summary">The specification of a particular script used in the
							EAC-CPF instance or in the creative work of the entity being
							described.</item>
						<item n="description">
							<p>A required element within <tag>languageDeclaration</tag> that gives
								the main script in which the EAC-CPF instance is written.</p>
							<p>A required element within <tag>languageUsed</tag> that gives the main
								script used by the entity being described in their creative or
								productive work.</p>
							<p>The content of the <att>scriptCode</att> attribute must be given in
								the form of a valid code from ISO 15924.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">languageDeclaration, languageUsed</item>
						<item n="attributes">
							<list>
								<label>scriptCode</label>
								<item>Required</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.7</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:languageDeclaration>
							<eac-cpf:language languageCode="eng">English</eac-cpf:language>
							<eac-cpf:script scriptCode="Latn">Latin</eac-cpf:script>
						</eac-cpf:languageDeclaration>
					</egXML>
				</div>
				<div type="element" xml:id="setComponent">
					<head type="tag">
						<tag>setComponent</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Set Component</head>
						<item n="summary">A wrapper element within <tag>alternativeSet</tag> 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 <tag>cpfDescription</tag>.</item>
						<item n="description">
							<p>
								<tag>setComponent</tag> provides an encoding wrapper to contain an
								entire authority record, so that multiple records for the same
								identity from separate authority systems or in different languages,
								may be combined together within a single EAC-CPF instance. The
								mandatory <tag>componentEntry</tag> element encodes the link to the
								authority record in the external authority system. An optional
									<tag>descriptiveNote</tag> may be used for a textual note
								providing further information about the record referenced in
									<tag>setComponent</tag>.</p>
						</item>
						<item n="mayContain">componentEntry, descriptiveNote, objectBinWrap,
							objectXMLWrap</item>
						<item n="mayOccurIn">alternativeSet</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:alternativeSet>
							<eac-cpf:setComponent xlink:href="http://authorities.loc.gov"
								xlink:type="simple">
								<eac-cpf:componentEntry>Bright Sparcs
									Record</eac-cpf:componentEntry>
							</eac-cpf:setComponent>
							<eac-cpf:setComponent xlink:href="http://nla.gov.au/anbd.aut-an35335937"
								xlink:type="simple">
								<eac-cpf:componentEntry>NLA record.</eac-cpf:componentEntry>
							</eac-cpf:setComponent>
						</eac-cpf:alternativeSet>
					</egXML>
				</div>
				<div type="element" xml:id="source">
					<head type="tag">
						<tag>source</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Source</head>
						<item n="summary">A source of evidence used in describing the entity or
							entities in the EAC-CPF instance.</item>
						<item n="description">
							<p>An element for identifying a particular source of evidence used in
								describing the entity or entities. A record for the source must be
								included in either <tag>objectXMLWrap</tag> or
									<tag>objectBinWrap</tag>; or as a textual description in the
									<tag>sourceEntry</tag> element. Use the optional
									<tag>descriptiveNote</tag> for any additional notes about the
								source. A <tag>source</tag> in this context should not be confused
								with the <tag>citation</tag> 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.</p>
							<p>A link to the source may be made using the XML Linking Language
								(Xlink) attributes (for which consult the specification at <ref
									target="http://www.w3.org/TR/xlink/"
									>http://www.w3.org/TR/xlink/</ref>) and the last date and time
								that the source was verified can be given in the
									<att>lastDateTimeVerified</att> attribute.</p>
						</item>
						<item n="mayContain">descriptiveNote, objectBinWrap, objectXMLWrap,
							sourceEntry</item>
						<item n="mayOccurIn">sources</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>xlink:actuate</label>
								<item>Optional</item>
								<label>xlink:arcrole</label>
								<item>Optional</item>
								<label>xlink:href</label>
								<item>Optional</item>
								<label>xlink:role</label>
								<item>Optional</item>
								<label>xlink:show</label>
								<item>Optional</item>
								<label>xlink:title</label>
								<item>Optional</item>
								<label>xlink:type</label>
								<item>Required (if any XLINK attributes used)</item>
								<label>xml:id</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.8</item>
						<item n="occurrence">1...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:sources>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Principal Family and Estate Collections:
									Family Names L-W, 1999</eac-cpf:sourceEntry>
							</eac-cpf:source>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Complete Peerage,
									1936</eac-cpf:sourceEntry>
							</eac-cpf:source>
						</eac-cpf:sources>
					</egXML>
				</div>
				<div type="element" xml:id="sourceEntry">
					<head type="tag">
						<tag>sourceEntry</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Source Entry</head>
						<item n="summary">A textual identification of a particular source of
							evidence used in describing the entity in the EAC-CPF instance.</item>
						<item n="description">
							<p>The <tag>sourceEntry</tag> element may be used within the
									<tag>source</tag> element to identify a source used in the
								construction of the EAC-CPF instance directly rather than using
								other content in <tag>objectBinWrap</tag> or
									<tag>objectXMLWrap</tag>. The <tag>sourceEntry</tag> element
								generally contains discursive text.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">source</item>
						<item n="attributes">
							<list>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:sources>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Principal Family and Estate Collections:
									Family Names L-W, 1999</eac-cpf:sourceEntry>
							</eac-cpf:source>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Complete Peerage,
									1936</eac-cpf:sourceEntry>
							</eac-cpf:source>
						</eac-cpf:sources>
					</egXML>
				</div>
				<div type="element" xml:id="sources">
					<head type="tag">
						<tag>sources</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Sources</head>
						<item n="summary">A record of the sources used for the description of the
							entity or entities in the EAC-CPF instance.</item>
						<item n="description">
							<p>A wrapper element within <tag>control</tag> used to record one or
								more sources consulted in creating the description of the entity or
								entities in the EAC-CPF instance.</p>
						</item>
						<item n="mayContain">source</item>
						<item n="mayOccurIn">control</item>
						<item n="attributes">
							<list>
								<label>xml:base</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.4.8</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:sources>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Principal Family and Estate Collections:
									Family Names L-W, 1999</eac-cpf:sourceEntry>
							</eac-cpf:source>
							<eac-cpf:source>
								<eac-cpf:sourceEntry>HMC, Complete Peerage,
									1936</eac-cpf:sourceEntry>
							</eac-cpf:source>
						</eac-cpf:sources>
					</egXML>
				</div>
				<div type="element" xml:id="span">
					<head type="tag">
						<tag>span</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Span</head>
						<item n="summary">Specifies the beginning and the end of a span of
							text.</item>
						<item n="description">
							<p>A formatting element for marking arbitrary words or phrases that are
								stressed or emphasized for linguistic effect or identifying some
								qualities of the words or phrases. Use the <att>style</att>
								attribute to affect an arbitrary stylistic difference. Use the
									<att>localType</att> attribute to assign other
								characteristics.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">abstract, citation, componentEntry, item, p,
							sourceEntry</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>style</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:biogHist>
							<eac-cpf:p>Robert Carlton Brown (1886-1959) was a writer, editor,
								publisher, and traveler. From 1908 to 1917, he wrote poetry and
								prose for numerous magazines and newspapers in New York City,
								publishing two pulp novels, <eac-cpf:span style="font-style:italic"
									>What Happened to Mary</eac-cpf:span> and <eac-cpf:span
									style="font-style:italic">The Remarkable Adventures of
									Christopher Poe</eac-cpf:span> (1913), and one volume of poetry,
									<eac-cpf:span style="font-style:italic">My
									Marjonary</eac-cpf:span> (1916).</eac-cpf:p>
							<eac-cpf:p>During 1918, he traveled extensively in Mexico and Central
								America, writing for the U.S. Committee of Public Information in
								Santiago de Chile. In 1919, he moved with his wife, Rose Brown, to
								Rio de Janeiro, where they founded <eac-cpf:span
									style="font-style:italic">Brazilian American</eac-cpf:span>, a
								weekly magazine that ran until 1929. With Brown's mother, Cora, the
								Browns also established magazines in Mexico City and London:
									<eac-cpf:span style="font-style:italic">Mexican
									American</eac-cpf:span> (1924-1929) and <eac-cpf:span
									style="font-style:italic">British American</eac-cpf:span>
								(1926-1929).</eac-cpf:p>
						</eac-cpf:biogHist>
					</egXML>
				</div>
				<div type="element" xml:id="structureOrGenealogy">
					<head type="tag">
						<tag>structureOrGenealogy</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Structure or Genealogy</head>
						<item n="summary">A description of the internal administrative structure(s)
							of a corporate body or the genealogy of a family.</item>
						<item n="description">
							<p>
								<tag>structureOrGenealogy</tag> encodes within the description area,
								information expressing the internal administrative structure(s) of a
								corporate body and the dates of any changes to that structure that
								are significant to understanding the way that corporate body
								conducted affairs (such as dated organization charts), and the
								genealogy of a family (such as a family tree) in a way that
								demonstrates the interrelationships of its members with covering
								dates.</p>
							<p>The optional <tag>list</tag> and <tag>outline</tag> elements are used
								to accommodate greater complexity in expressing or representing the
								activities being described. <tag>citation</tag> may be used to
								provide a link to external documents like organizational charts and
								family trees. A simpler discursive expression of the activities may
								be encoded as one or more <tag>p</tag> elements.</p>
							<p>Genealogical and administrative structure information may
								alternatively be described in discursive form in the
									<tag>biogHist</tag> element (ISAAR (CPF) 5.2.2 History) and/or
								with <tag>cpfRelation</tag> elements (ISAAR (CPF) 5.3). The
									<tag>structureOrGenealogy</tag> element should be used whenever
								separate semantic processing of information about structure or
								genealogies is required.</p>
						</item>
						<item n="mayContain">citation, list, outline, p</item>
						<item n="mayOccurIn">description</item>
						<item n="attributes">
							<list>
								<label>localType</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.2.7</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:structureOrGenealogy>
							<eac-cpf:p>Sir Edward Noel (d 1643) married Julian, daughter and co-heir
								of Baptists Hicks (d 1629), Viscount Campden, and succeeded to the
								viscouty of Campden and a portion of his father-in-law's estates.
								The third Viscount Campden (1612-82) married Hester Wotton, daughter
								of the second Baron Wotton. The fourth Viscount Campden (1641-1689,
								created Earl of Gainsborough, 1682) married Elizabeth Wriothesley,
								elder daughter of the fourth Earl of Southampton. Jane Noel (d
								1811), sister of the fifth and sixth Earls of Gainsborough, married
								Gerard Anne Edwards of Welham Grove (Leicetershire) and had issue
								Gerard Noel Edwards (1759-1838). He married in 1780 Diana Middleton
								(1762-1823 suo jure Baroness Barham), daughter of Charles Middleton
								(1726-1813), created first Baronet of Barham Court (Kent) in 1781
								and first Baron Barham in 1805. GN Edwards assumed the surname Noel
								in 1798 on inheriting the sixth Earl of Gainborough's Rutland and
								Gloucestershire estates (though not the Earl's honours, which were
								extinguished); and he later inherited his father-in-law's baronetcy.
								His eldest son John Noel (1781-1866) succeeded to the estates of his
								mother and his father, to his mother's barony and his father's
								baronetcy, and was created Viscount Campden and Earl of Gainsborough
								in 1841.</eac-cpf:p>
						</eac-cpf:structureOrGenealogy>
					</egXML>
				</div>
				<div type="element" xml:id="term">
					<head type="tag">
						<tag>term</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Term</head>
						<item n="summary">A generic element used to encode a descriptive term in
							accordance with local descriptive rules.</item>
						<item n="description">
							<p>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
									<tag>localTypeDeclaration</tag> element within the
									<tag>control</tag> section.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">function, legalStatus, localControl, localDescription,
							mandate, occupation, place</item>
						<item n="attributes">
							<list>
								<label>lastDateTimeVerified</label>
								<item>Optional</item>
								<label>scriptCode</label>
								<item>Optional</item>
								<label>transliteration</label>
								<item>Optional</item>
								<label>vocabularySource</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">0...∞</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:function>
							<eac-cpf:term>Estate ownership</eac-cpf:term>
							<eac-cpf:descriptiveNote>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).</eac-cpf:descriptiveNote>
						</eac-cpf:function>
						<eac-cpf:legalStatus>
							<eac-cpf:term>Organismo de la Administracion Central del
								Estado</eac-cpf:term>
							<eac-cpf:date standardDate="1769">1769</eac-cpf:date>
						</eac-cpf:legalStatus>
						<eac-cpf:mandate>
							<eac-cpf:term>Minnesota. Executive Session Laws 1919 c49</eac-cpf:term>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate>1919</eac-cpf:fromDate>
								<eac-cpf:toDate>1925</eac-cpf:toDate>
							</eac-cpf:dateRange>
							<eac-cpf:descriptiveNote>
								<eac-cpf:p>Board created in 1919 to receive and examine applications
									for bonuses from Minnesota soldiers.</eac-cpf:p>
							</eac-cpf:descriptiveNote>
						</eac-cpf:mandate>
						<eac-cpf:occupation>
							<eac-cpf:term>Teacher</eac-cpf:term>
						</eac-cpf:occupation>
						<eac-cpf:localControl localType="detailLevel">
							<eac-cpf:term>minimal</eac-cpf:term>
						</eac-cpf:localControl>
					</egXML>
				</div>
				<div type="element" xml:id="toDate">
					<head type="tag">
						<tag>toDate</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">To Date</head>
						<item n="summary">The ending date in a date range.</item>
						<item n="description">
							<p>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 <att>standardDate</att> attribute.
								The <att>notBefore</att> and <att>notAfter</att> attributes may be
								used to indicate uncertainty.</p>
						</item>
						<item n="mayContain">[text]</item>
						<item n="mayOccurIn">dateRange</item>
						<item n="attributes">
							<list>
								<label>notAfter</label>
								<item>Optional</item>
								<label>notBefore</label>
								<item>Optional</item>
								<label>standardDate</label>
								<item>Optional</item>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="occurrence">1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:existDates>
							<eac-cpf:dateRange>
								<eac-cpf:fromDate standardDate="1868">1868</eac-cpf:fromDate>
								<eac-cpf:toDate standardDate="1936">1936</eac-cpf:toDate>
							</eac-cpf:dateRange>
						</eac-cpf:existDates>
					</egXML>
				</div>
				<div type="element" xml:id="useDates">
					<head type="tag">
						<tag>useDates</tag>
					</head>
					<list xml:lang="eng">
						<head type="name">Date of Use</head>
						<item n="summary">The dates when the name or names were used by the entity
							being described. </item>
						<item n="description">
							<p>Within <tag>nameEntry</tag>, <tag>useDates</tag> provides the dates
								when the name was used. For parallel names, <tag>useDates</tag> may
								occur in <tag>nameEntryParallel</tag> rather than in the individual
									<tag>nameEntry</tag> elements contained in
									<tag>nameEntryParallel</tag>.</p>
						</item>
						<item n="mayContain">date, dateRange, dateSet</item>
						<item n="mayOccurIn">nameEntry, nameEntryParallel</item>
						<item n="attributes">
							<list>
								<label>xml:id</label>
								<item>Optional</item>
								<label>xml:lang</label>
								<item>Optional</item>
							</list>
						</item>
						<item n="reference">ISAAR (CPF) 5.1.2 and 5.1.3</item>
						<item n="occurrence">0...1</item>
					</list>
					<egXML xmlns="http://www.tei-c.org/ns/Examples">
						<eac-cpf:nameEntry>
							<eac-cpf:part>Brown, Bob</eac-cpf:part>
							<eac-cpf:useDates>
								<eac-cpf:dateRange>
									<eac-cpf:fromDate standardDate="1886">1886</eac-cpf:fromDate>
									<eac-cpf:toDate standardDate="1959">1959</eac-cpf:toDate>
								</eac-cpf:dateRange>
							</eac-cpf:useDates>
							<eac-cpf:authorizedForm>AACR2</eac-cpf:authorizedForm>
						</eac-cpf:nameEntry>
					</egXML>
				</div>
			</div>
			<div type="attributes" xml:id="attributes">
				<div type="attribute" xml:id="accuracy">
					<head type="attribute">
						<att>accuracy</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Accuracy</head>
						<item n="summary">The accuracy specification for a place statement.</item>
						<item n="description">Within the <tag>placeEntry</tag> element, this
							attribute allows for an accuracy specification.</item>
						<item n="datatype">[text]</item>
					</list>
				</div>
				<div type="attribute" xml:id="altitude">
					<head type="attribute">
						<att>altitude</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Altitude</head>
						<item n="summary">The altitude or elevation of the geographic place.</item>
						<item n="description">The <att>altitude</att> may occur on <tag>place</tag>.
							The value of the attribute is the altitude or elevation of the
							geographic place named. <att>altitude</att> should be used in
							conjunction with <att>longitude</att> and <att>latitude</att>.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="countryCode">
					<head type="attribute">
						<att>countryCode</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Country Code</head>
						<item n="summary">Two letter ISO 3166-1 standard code representing a
							country.</item>
						<item n="description">The <att>countryCode</att> may occur on
								<tag>placeEntry</tag> or <tag>address</tag>. The
								<att>countryCode</att> attribute may be used to provide the ISO
							3166-1 standard code designating the country placed named is a country,
							the code for that country. The values are to be taken from the list of
							ISO 3166-1 Codes for the Representation of Names of Countries. The list
							can be downloaded from the website of ISO 3166 Maintenance Agency <ref
								target="http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm"
								>http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm</ref>
						</item>
						<item n="datatype">ISO 3166-1 Codes for the Representation of Names of
							Countries, column A2.</item>
					</list>
				</div>
				<div type="attribute" xml:id="cpfRelationType">
					<head type="attribute">
						<att>cpfRelationType</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Corporate Body, Person, or Family Relation Type</head>
						<item n="summary">The type of relation that the corporate body, person, or
							family has to the entity being described.</item>
						<item n="description">The <att>cpfRelationType</att> may occur on
								<tag>cpfRelation</tag>. 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 <att>cpfRelationType</att>.</item>
						<item n="datatype">"identity" or "hierarchical" or "hierarchical-parent" or
							"hierarchical-child" or "temporal" or "temporal-earlier" or
							"temporal-later" or "family" or "associative"</item>
					</list>
				</div>
				<div type="attribute" xml:id="functionRelationType">
					<head type="attribute">
						<att>functionRelationType</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Function Relation Type</head>
						<item n="summary">The type of relation that the entity being described has
							to the related function.</item>
						<item n="description">The <att>functionRelationType</att> may occur on
								<tag>functionRelation</tag>. 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
								<att>functionRelationType</att>.</item>
						<item n="datatype">"controls" or "owns" or "performs"</item>
					</list>
				</div>
				<div type="attribute" xml:id="identityType">
					<head type="attribute">
						<att>identityType</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Identity Type</head>
						<item n="summary">Indicates whether the identity is given or acquired. May
							be useful for processing when multiple identities are described in the
							same instance.</item>
						<item n="description">The <att>identityType</att> may occur on
								<tag>identity</tag>. Though optional, it is recommended that it be
							used when multiple identities are described in the same EAC-CPF instance
							using <tag>multipleIdentities</tag>. It will enable processors to
							distinguish between the description of a person and one or more
							personae. </item>
						<item n="datatype">"given" or "acquired"</item>
					</list>
				</div>
				<div type="attribute" xml:id="languageCode">
					<head type="attribute">
						<att>languageCode</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Language Code</head>
						<item n="summary">Three-letter ISO 639-2 language code. Must occur on
								<tag>language</tag>.</item>
						<item n="description">The <att>languageCode</att> must occur on
								<tag>language</tag>. 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. The list can be downloaded from
							the website of the Library of Congress which is the registration agency
							of the standard (<ref
								target="http://www.loc.gov/standards/iso639-2/langhome.html"
								>http://www.loc.gov/standards/iso639-2/langhome.html</ref>).</item>
						<item n="datatype">ISO 639-2 Codes for the Representation of Names of
							Languages</item>
					</list>
				</div>
				<div type="attribute" xml:id="lastDateTimeVerified">
					<head type="attribute">
						<att>lastDateTimeVerified</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Last Date and Time Verified</head>
						<item n="summary">Last date or date and time the linked resource was
							verified.</item>
						<item n="description">The <att>lastDateTimeVerified</att> may occur on
								<tag>citation</tag>, <tag>cpfRelation</tag>,
								<tag>functionRelation</tag>, <tag>resourceRelation</tag>,
								<tag>setComponent</tag>, or <tag>term</tag>. 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.</item>
						<item n="datatype">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.</item>
					</list>
				</div>
				<div type="attribute" xml:id="latitude">
					<head type="attribute">
						<att>latitude</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Latitude</head>
						<item n="summary">The geographic latitude of the place.</item>
						<item n="description">The <att>latitude</att> may occur on <tag>place</tag>.
							The value of the attribute is the geographic latitude of the place
							named. <att>latitude</att> should be used in conjunction with
								<att>longitude</att> and <att>altitude</att>.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="localType">
					<head type="attribute">
						<att>localType</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Local Type</head>
						<item n="summary">Used to make the semantics of the element more specific or
							to provide semantic specificity to elements that are semantically weak.
							Value should be an absolute URI.</item>
						<item n="description">The <att>localType</att> 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 <att>localType</att> 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.</item>
						<item n="datatype">anyURI</item>
					</list>
				</div>
				<div type="attribute" xml:id="longitude">
					<head type="attribute">
						<att>longitude</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Longitude</head>
						<item n="summary">The longitude of the place.</item>
						<item n="description">The <att>longitude</att> may occur on
							<tag>place</tag>. The value of the attribute is the geographic longitude
							of the place named. <att>longitude</att> should be used in conjunction
							with <att>latitude</att> and <att>altitude</att>.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="notAfter">
					<head type="attribute">
						<att>notAfter</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Not After</head>
						<item n="summary">The latest date possible for an uncertain date.</item>
						<item n="description">The <att>notAfter</att> may occur on <tag>date</tag>,
								<tag>fromDate</tag>, and <tag>toDate</tag>. For uncertain dates,
							used in conjunction with <att>standardDate</att>, the value of
								<att>notAfter</att> is the latest date possible. See also
								<att>notBefore</att>.</item>
						<item n="datatype">Union of the XML Schema Datatypes date, gYear, and
							gYearMonth. The following are all valid patterns: 2009-12-31, 2009,
							2009-12.</item>
					</list>
				</div>
				<div type="attribute" xml:id="notBefore">
					<head type="attribute">
						<att>notBefore</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Not Before</head>
						<item n="summary">The earliest date possible for an uncertain date.</item>
						<item n="description">The <att>notBefore</att> may occur on <tag>date</tag>,
								<tag>fromDate</tag>, and <tag>toDate</tag>. For uncertain dates,
							used in conjunction with <att>standardDate</att>, the value of
								<att>notBefore</att> is the earliest date possible. See also
								<att>notAfter</att>.</item>
						<item n="datatype">Union of the XML Schema Datatypes date, gYear, and
							gYearMonth. The following are all valid patterns: 2009-12-31, 2009,
							2009-12.</item>
					</list>
				</div>
				<div type="attribute" xml:id="resourceRelationType">
					<head type="attribute">
						<att>resourceRelationType</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Resource Relation Type</head>
						<item n="summary">The type of relation of entity being described to the
							resource.</item>
						<item n="description">The <att>resourceRelationType</att> may occur on
								<tag>resourceRelation</tag>. 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
								<att>resourceRelationType</att>.</item>
						<item n="datatype">"creatorOf" or "subjectOf" or "other"</item>
					</list>
				</div>
				<div type="attribute" xml:id="scriptCode">
					<head type="attribute">
						<att>scriptCode</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Script Code</head>
						<item n="summary">The ISO 15924 four-letter code for the writing script
							used.</item>
						<item n="description">A standard four-letter code for the writing script
							used with a given language. The <att>scriptCode</att> attribute is
							required for the <tag>script</tag> element, and is available on other
							elements where language designations may be used.</item>
						<item n="datatype">ISO 15924 Code for the Representation of Names and
							Scripts</item>
					</list>
				</div>
				<div type="attribute" xml:id="standardDate">
					<head type="attribute">
						<att>standardDate</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Standard Date</head>
						<item n="summary">The date represented in a standard form for computer
							processing.</item>
						<item n="description">The <att>standardDate</att> may occur on
								<tag>date</tag>, <tag>fromDate</tag>, and <tag>toDate</tag>. The
							value of <att>standardDate</att> provides a standard form of the date
							expressed in <tag>date</tag>, <tag>fromDate</tag>, or <tag>toDate</tag>
							that can be used in computer processing, such as searching.</item>
						<item n="datatype">Union of the XML Schema Datatypes date, gYear, and
							gYearMonth. The following are all valid patterns: 2009-12-31, 2009,
							2009-12.</item>
					</list>
				</div>
				<div type="attribute" xml:id="standardDateTime">
					<head type="attribute">
						<att>standardDateTime</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Standard Date and Time</head>
						<item n="summary">The date or date and time represented in a standard form
							for computer processing.</item>
						<item n="description">The <att>standardDateTime</att> may occur on
								<tag>eventDateTime</tag>. The value of <att>standardDateTime</att>
							provides a standard form of the date or date and time expressed in the
								<tag>eventDateTime</tag> that can be used in computer processing.
							For example, using both the value in <tag>eventType</tag> and
								<att>standardDateTime</att>, all EAC-CPF instances "revised" on a
							particular date can be identified.</item>
						<item n="datatype">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.</item>
					</list>
				</div>
				<div type="attribute" xml:id="style">
					<head type="attribute">
						<att>style</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Style</head>
						<item n="summary">Used to specify a rendering style for string. It is
							recommended that the value conforms to W3C CSS.</item>
						<item n="description">The <att>style</att> may occur on <tag>span</tag>. In
							a limited number of contexts that accommodate discursive description,
								<tag>span</tag> with <att>style</att> 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 <att>style</att> be expressed as
							a W3C CSS style to facilitate interoperability.</item>
						<item n="datatype">string</item>
					</list>
				</div>
				<div type="attribute" xml:id="transliteration">
					<head type="attribute">
						<att>transliteration</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Transliteration</head>
						<item n="summary">A value designating the transliteration scheme used in
							representing converting one script into another script.</item>
						<item n="description">The conventions or rules that prescribe a method for
							converting one script into another script.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="vocabularySource">
					<head type="attribute">
						<att>vocabularySource</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Source of Vocabulary</head>
						<item n="summary">A value designating the source of the vocabulary from
							which terms are derived.</item>
						<item n="description">The controlled vocabulary used to derive terms for the
								<tag>term</tag>, <tag>placeEntry</tag>, and <tag>placeRole</tag>
							elements. Controlled vocabularies should be declared in the
								<tag>conventionDeclaration</tag> element within
							<tag>control</tag>.</item>
						<item n="datatype">anyURI</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkActuate">
					<head type="attribute">
						<att>xlink:actuate</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Actuate</head>
						<item n="summary">Used to signal intended behavior with respect to whether
							the remote resource link is resolved when the containing resource is
							rendered, or when the user requests the resource.</item>
						<item n="description">The <att>xlink:actuate</att> should be used with the
								<att>xlink:show</att> to indicate intended behavior. The
								<att>xlink:actuate</att> 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.</item>
						<item n="datatype">"onLoad" or "onRequest" or "other" or "none"</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkArcrole">
					<head type="attribute">
						<att>xlink:arcrole</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Arc role</head>
						<item n="summary">URI defining the purpose of the link.</item>
						<item n="description">An absolute URI that describes the nature of the
							relation between the entity being described in the EAC-CPF instance and
							a remote resource (<tag>cpfRelation</tag>, <tag>resourceRelation</tag>,
							or <tag>functionRelation</tag>) or the nature of the relation between
							the EAC-CPF instance description (or component of description) and the
							remote resource (<tag>citation</tag>, <tag>setComponent</tag>,
								and<tag>source</tag>). 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.</item>
						<item n="datatype">anyURI</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkHref">
					<head type="attribute">
						<att>xlink:href</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: HREF</head>
						<item n="summary">Contains a URI, possibly absolute, pointing to the related
							resource</item>
						<item n="description">The address for a remote resource. The
								<att>xlink:href</att> takes the form of a Uniform Resource
							Identifier (URI). While it is permissible to use a relative URI, and an
							absolute URI is recommended.</item>
						<item n="datatype">anyURI</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkRole">
					<head type="attribute">
						<att>xlink:role</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Role</head>
						<item n="summary">Identifies the type or nature of the remote resource with
							an absolute URI.</item>
						<item n="description">Identifies the type or nature of the remote resource
							with an absolute URI. </item>
						<item n="datatype">anyURI</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkShow">
					<head type="attribute">
						<att>xlink:show</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Show</head>
						<item n="summary">Used to signal intended behavior with respect to where the
							remote resource is to appear when the link is resolved.</item>
						<item n="description">The <att>xlink:show</att> should be used with the
								<att>xlink:actuate</att> to indicate intended behavior. The
								<att>xlink:show</att> 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.</item>
						<item n="datatype">"embed" or "new" or "replace" or "none" or "other"</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkTitle">
					<head type="attribute">
						<att>xlink:title</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Title</head>
						<item n="summary">Information that may be used as a viewable caption for the
							remote resource.</item>
						<item n="description">Information that serves as a viewable caption that
							indicates the name or type of the linked remote source.</item>
						<item n="datatype">string</item>
					</list>
				</div>
				<div type="attribute" xml:id="xlinkType">
					<head type="attribute">
						<att>xlink:type</att>
					</head>
					<list xml:lang="eng">
						<head type="name">Xlink: Type</head>
						<item n="summary">A fixed value that identifies an XLINK compliant element
							of a particular type.</item>
						<item n="description">A fixed value that identifies an XLINK compliant
							element of a particular type. Only one XLINK type is used in EAC-CPF,
							"simple." While the attribute is optional in instances validated against
							the W3C Schema version of EAC-CPF, the Relax NG version of EAC-CPF
							requires it. To support exchange of EAC-CPF instances, it is recommended
							that the <att>xlink:type</att> be present in the instance whenever any
							of the other XLINK attributes are used.</item>
						<item n="datatype">Fixed value: "simple"</item>
					</list>
				</div>
				<div type="attribute" xml:id="xmlbase">
					<head type="attribute">
						<att>xml:base</att>
					</head>
					<list xml:lang="eng">
						<head type="name">XML Base</head>
						<item n="summary">Used to specify a base URI other than the base URI of the
							EAC-CPF instance.</item>
						<item n="description">
							<att>xml:base</att> 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. <att>xml:base</att> makes it possible to
							declare an absolute base URI to facilitate the use of relative URIs on
							the descendants.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="xmlid">
					<head type="attribute">
						<att>xml:id</att>
					</head>
					<list xml:lang="eng">
						<head type="name">XML Identifier</head>
						<item n="summary">A unique identifier available on most elements that can be
							used to name specific elements in the EAC-CPF instance.</item>
						<item n="description">An identifier used to name the element so that it can
							be referred to, or referenced from, somewhere else. Each
								<att>xml:id</att> within a document must have a unique value. The
								<att>xml:id</att> attribute regularizes the naming of the element
							and thus facilitates building links between it and other resources. For
							example, the <att>xml:id</att> may be used to uniquely identify two or
							more <tag>cpfDescription</tag> within <tag>multipleIdentities</tag>.
							Uniquely identifying or distinguishing two or more
								<tag>cpfDescription</tag> 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.</item>
						<item n="datatype">NMTOKEN</item>
					</list>
				</div>
				<div type="attribute" xml:id="xmllang">
					<head type="attribute">
						<att>xml:lang</att>
					</head>
					<list xml:lang="eng">
						<head type="name">XML Language</head>
						<item n="summary">Three-letter ISO 639-2 language code.</item>
						<item n="description">The <att>xml:lang</att> 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.
								<att>xml:lang</att> should be used when the language of the element
							differs from the Language Code declared in the <att>languageCode</att>
							attribute on the element <tag>language</tag> in the control section. The
							values in the list are taken from ISO 639-2 Codes for the Representation
							of Names of Languages. The list can be downloaded from the website of
							the Library of Congress which is the registration agency of the standard
								(<ref target="http://www.loc.gov/standards/iso639-2/langhome.html"
								>http://www.loc.gov/standards/iso639-2/langhome.html</ref>).</item>
						<item n="datatype">IS0 639-2 Codes for the Representation of Names of
							Languages.</item>
					</list>
				</div>
			</div>
		</body>
		<back>
			<div type="appendix" xml:id="crosswalk" n="1">
				<head>ISAAR(CPF) Crosswalk</head>
				<list>
					<label>ISAAR (CPF)</label>
					<item>EAC-CPF</item>
					<label>5.1 Identity area</label>
					<item>
						<tag>identity</tag>
					</item>
					<label>5.1.1 Type of entity</label>
					<item>
						<tag>entityType</tag>
					</item>
					<label>5.1.2 Authorized form(s) of name</label>
					<item>
						<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> with
							<tag>authorizedForm</tag>
					</item>
					<label>5.1.3 Parallel forms of name</label>
					<item>
						<tag>nameEntryParallel</tag>
					</item>
					<label>5.1.4 Standardized forms of name according to other rules</label>
					<item>
						<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> with
							<tag>authorizedForm</tag>
					</item>
					<label>5.1.5 Other forms of name</label>
					<item>
						<tag>nameEntry</tag> or <tag>nameEntryParallel</tag> with
							<tag>alternativeForm</tag>
					</item>
					<label>5.1.6 Identifiers for corporate bodies</label>
					<item>
						<tag>entityId</tag>
					</item>
					<label>5.2 Description area</label>
					<item>
						<tag>description</tag>
					</item>
					<label>5.2.1 Dates of existence</label>
					<item>
						<tag>existDates</tag>
					</item>
					<label>5.2.2 History</label>
					<item>
						<tag>biogHist</tag>
					</item>
					<label>5.2.3 Places</label>
					<item>
						<tag>place</tag> or <tag>places</tag>
					</item>
					<label>5.2.4 Legal status</label>
					<item>
						<tag>legalStatus</tag> or <tag>legalStatuses</tag>
					</item>
					<label>5.2.5 Functions, occupations and activities</label>
					<item>
						<tag>function</tag> or <tag>functions</tag>, <tag>occupation</tag> or
							<tag>occupations</tag>
					</item>
					<label>5.2.6 Mandates/Sources of authority</label>
					<item>
						<tag>mandate</tag> or <tag>mandates</tag>
					</item>
					<label>5.2.7 Internal structures/Genealogy</label>
					<item>
						<tag>structureOrGenealogy</tag>
					</item>
					<label>5.2.8 General context</label>
					<item>
						<tag>generalContext</tag>
					</item>
					<label>5.3 Relationships area</label>
					<item>
						<tag>relations</tag>
					</item>
					<label>5.3.1 Names/Identifiers of related corporate bodies, persons or
						families</label>
					<item>
						<tag>cpfRelation</tag>
					</item>
					<label>5.3.2 Category of relationship</label>
					<item>
						<tag>cpfRelation cpfRelationType="[value]"</tag>
					</item>
					<label>5.3.3 Description of relationship</label>
					<item>
						<tag>objectXMLWrap</tag> or <tag>objectBinWrap</tag> or
							<tag>relationEntry</tag>
					</item>
					<label>5.3.4 Dates of the relationship</label>
					<item>
						<tag>cpfRelation</tag>/<tag>date</tag> or <tag>dateRange</tag> or
							<tag>dateSet</tag>
					</item>
					<label>5.4 Control area</label>
					<item>
						<tag>control</tag>
					</item>
					<label>5.4.1 Authority record identifier</label>
					<item>
						<tag>recordId</tag>
					</item>
					<label>5.4.2 Institution identifiers</label>
					<item>
						<tag>maintenanceAgency/agencyCode and/or agencyName</tag>
					</item>
					<label>5.4.3 Rules and/or conventions</label>
					<item>
						<tag>conventionDeclaration</tag>
					</item>
					<label>5.4.4 Status</label>
					<item>
						<tag>maintenanceStatus</tag>
					</item>
					<label>5.4.5 Level of detail</label>
					<item>
						<tag>localControl</tag>
					</item>
					<label>5.4.6 Dates of creation, revision or deletion</label>
					<item>
						<tag>maintenanceEvent</tag>/<tag>eventDateTime</tag>
					</item>
					<label>5.4.7 Languages and scripts</label>
					<item>
						<tag>languageDeclaration</tag>
					</item>
					<label>5.4.8 Sources</label>
					<item>
						<tag>sources</tag>
					</item>
					<label>5.4.9 Maintenance notes</label>
					<item>
						<tag>maintenanceEvent</tag>/<tag>maintenanceDescription</tag>
					</item>
					<label>6. Relating corporate bodies, persons, and families to archival materials
						and other resources</label>
					<item>
						<tag>resourceRelation</tag>
					</item>
					<label>6.1 Identifiers and titles of related resources</label>
					<item>
						<tag>objectXMLWrap</tag> or <tag>objectBinWrap</tag> or
							<tag>relationEntry</tag>
					</item>
					<label>6.2 Types of related resources</label>
					<item>
						<tag>resourceRelation xlink:role="[value]"</tag>
					</item>
					<label>6.3 Nature of relationships</label>
					<item>
						<tag>resourceRelation resourceRelationType="[value]"</tag>
					</item>
					<label>6.4 Dates of related resources and/or relationships</label>
					<item>
						<tag>resourceRelation</tag>/<tag>date</tag> or <tag>dateRange</tag> or
							<tag>dateSet</tag>
					</item>
				</list>
			</div>
		</back>
	</text>
</TEI>