forked from SAA-SDT/eac-cpf-taglibrary
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcpfTagLibrary_FO.xml
5885 lines (5885 loc) · 281 KB
/
cpfTagLibrary_FO.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?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:xlink="http://www.w3c.org/1999/xlink" xmlns:example="example">
<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>
<docTitle>
<titlePart type="main">Encoded Archival Context—Corporate Bodies, Persons, and Families
(EAC-CPF) Tag Library</titlePart>
</docTitle>
<docEdition>Version 2010 (initial release)</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>
</titlePage>
<div xml:id="dedication">
<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="releaseandrevisionnotes">
<head>Release and Revision Notes</head>
<p>The EAC-CPF Tag Library should be considered a living document. As such, it will continue to
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:[email protected]">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="background">
<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, 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 completed schema was
released in February 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) primarily
addresses the description of individuals, families and corporate bodies that create, preserve,
use and are responsible for and/or associated with records in a variety of ways. Over time,
other types of contextual entities may evolve under the larger EAC umbrella, but currently its
primary purpose is to standardize the encoding of descriptions about 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="concepts">
<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="overview">
<head>Overview of EAC-CPF Structure and Semantics</head>
<div xml:id="overviewintroduction">
<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="overviewcontrol">
<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="overviewcpfDescription">
<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.</item>
</list>
</div>
<div xml:id="overviewidentity">
<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 code 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="overviewdescription">
<head>
<tag>description</tag>
</head>
<p>The <tag>description</tag> 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. Elements for
description include:</p>
<list type="simple">
<item>
<tag>existDates</tag> — 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> — 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> — 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> — 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> — 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>occupation</tag> — 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> — 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> — 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> — 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> — 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="overviewrelations">
<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="overviewxlink">
<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 attributed 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&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="overviewlocalType">
<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>
</front>
<body>
<div type="elements" xml:id="elements">
<div type="element" xml:id="abbreviation">
<head type="tag">
<tag>abbreviation</tag>
</head>
<head type="name">Abbreviation</head>
<list xml:lang="eng">
<item n="summary">The <tag>abbreviation</tag> element contains an abbreviation or code for
identifying a thesauri, controlled vocabularies, or other standard used in formulating and
compiling the EAC-CPF description.</item>
<item n="description">
<p>The <tag>abbreviation</tag> element contains an abbreviation or code for identifying a
thesauri, controlled vocabularies, or other standard used in formulating and compiling the
EAC-CPF description. It is recommended that the value be selected from an authorized list of
codes. An example of such a list may be the MARC Code List (<ref
target="http://www.loc.gov/marc/relators/reladesc.html"
>http://www.loc.gov/marc/relators/reladesc.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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="abstract">
<head type="tag">
<tag>abstract</tag>
</head>
<head type="name">Abstract</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="address">
<head type="tag">
<tag>address</tag>
</head>
<head type="name">Address</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="addressLine">
<head type="tag">
<tag>addressLine</tag>
</head>
<head type="name">Address Line</head>
<list xml:lang="eng">
<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) </item>
<item n="occurrence">1...∞</item>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="agencyCode">
<head type="tag">
<tag>agencyCode</tag>
</head>
<head type="name">Agency Code</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="agencyName">
<head type="tag">
<tag>agencyName</tag>
</head>
<head type="name">Agency Name</head>
<list xml:lang="eng">
<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">0...1</item>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="agent">
<head type="tag">
<tag>agent</tag>
</head>
<head type="name">Agent</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="agentType">
<head type="tag">
<tag>agentType</tag>
</head>
<head type="name">Agent Type</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="alternativeForm">
<head type="tag">
<tag>alternativeForm</tag>
</head>
<head type="name">Alternative Form</head>
<list xml:lang="eng">
<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>
<item>
<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>
</item>
</list>
</div>
<div type="element" xml:id="alternativeSet">
<head type="tag">
<tag>alternativeSet</tag>
</head>
<head type="name">Alternative Set</head>
<list xml:lang="eng">
<item n="summary">A container element for two or more authority records derived from two or