-
Notifications
You must be signed in to change notification settings - Fork 5
/
EAD3-TL-eng.xml
1782 lines (1782 loc) · 112 KB
/
EAD3-TL-eng.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"?><?xml-model href="../schema/TL-teiliteSchema.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:ead="http://ead3.archivists.org/schema/" xmlns:eg="http://www.tei-c.org/ns/Examples" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xi="http://www.w3.org/2001/XInclude">
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="eng" type="main">Encoded Archival Description <lb/>Tag Library </title>
<title xml:lang="eng" type="additional">Version EAD3 1.1.2</title>
<respStmt xml:lang="eng">
<resp>Prepared and maintained by the</resp>
<name>Technical Subcommittee for Encoded Archival Standards of the Society of American Archivists</name>
</respStmt>
</titleStmt>
<editionStmt>
<p xml:lang="eng">2023 Edition</p>
</editionStmt>
<publicationStmt>
<publisher xml:lang="eng">Society of American Archivists</publisher>
<address>
<addrLine>Society of American Archivists</addrLine>
<addrLine>17 North State Street, suite 1425</addrLine>
<addrLine>Chicago, IL 60602-3315</addrLine>
<addrLine>USA</addrLine>
<addrLine>312-606-0722</addrLine>
<addrLine>Fax: 312-606-0728</addrLine>
<addrLine>[email protected]</addrLine>
<addrLine>www.archivists.org</addrLine>
</address>
<date when="2015"/>
<availability>
<licence>This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). See <ref target="http://creativecommons.org/licenses/by/4.0/"
>http://creativecommons.org/licenses/by/4.0/</ref>. Some rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means,
electronic, mechanical or photocopying, recording, or otherwise without attribution.</licence>
</availability>
</publicationStmt>
<sourceDesc>
<p xml:lang="eng">Born digital.</p>
</sourceDesc>
</fileDesc>
<profileDesc>
<langUsage>
<language ident="eng">English</language>
</langUsage>
</profileDesc>
</teiHeader>
<text xml:lang="eng">
<front>
<titlePage>
<docTitle>
<titlePart type="main">Encoded Archival Description <lb/>Tag Library</titlePart>
<titlePart type="additional">Version EAD3 1.1.2</titlePart>
</docTitle>
<docEdition>Edition 2023</docEdition>
<note>
<p>This tag library represents version EAD3 1.1.2 of the Encoded Archival Description schemas, released in June 2023. It supersedes the Version EAD3 1.1.1 tag library published in 2019 and the 1.1.0 tag library published in 2018.</p>
<p>The SAA Technical Subcommittee for Encoded Archival Standards is responsible for updating and editing the EAD schemas and tag library.</p>
<p>The Network Development and MARC Standards Office of the Library of Congress serves as the host for online EAD documentation, including storage and delivery of electronic files and maintenance of the
EAD web site, located at <ref target="http://www.loc.gov/ead/">http://www.loc.gov/ead/</ref>. </p>
</note>
<docImprint>
<docDate>Document date</docDate>
</docImprint>
<byline>Prepared and maintained by</byline>
<docAuthor>the<lb/> Technical Subcommittee for Encoded Archival Standards <lb/>of the Society of American Archivists</docAuthor>
<figure>
<graphic url="SAA.png"/>
</figure>
</titlePage>
<div xml:lang="eng" type="EnglishIntroduction">
<div xml:id="preface">
<head>Preface</head>
<p>Encoded Archival Description (EAD) is the international metadata transmission standard for hierarchical descriptions of archival records. Developed by the EAD Working Group of the Society of American
Archivists and first published in 1998, EAD is an Extensible Markup Language (XML) format used by archivists around the globe. A second version with greater international alignment, EAD 2002, was
released as a DTD in 2002 and in 2007 as Relax NG and W3C schemas. The development of EAD made it possible to create electronic finding aids within a specifically archival data structure compliant with
General International Standard Archival Description (ISAD(G)). This innovation was a crucial impetus behind the swift migration of archival description to the internet, the acceptance of national
archival descriptive content standards like Describing Archives: A Content Standard (DACS), and the emergence of a professional consensus that archival description existed to be shared widely and shared
well.</p>
<p>This new version of Encoded Archival Description – EAD3 – exists thanks to the efforts and support of many people, but it exists because of the many archivists and repositories around the world that saw
the utility of EAD, used it in diverse and inspiring ways, and continue to recognize many ways in which it might work better. </p>
<p>In the years between the release of EAD 2002 and 2010, when the revision process that led to EAD3 began, the technological landscape surrounding archival description evolved enormously. Collection
management systems, such as the Archivists’ Toolkit, Archon, and ICA-AtoM, offered the robust advantages of modelling descriptive information in relational databases, but exposed the difficulty of
adapting the EAD document model in data-centric applications. Linked Open Data emerged as a viable methodology for creating a semantically meaningful Web, for which EAD was poorly prepared. New and
closely related metadata transmission standards were developed, most notably Encoded Archival Context – Corporate bodies, Persons, and Families (EAC-CPF), opening new frontiers in archival metadata.
Finally, over a decade of working with EAD gave archivists a general sense that it was too complex, too forgiving, and too flexible for its own good.</p>
<p>In 2010, following an update to its by-laws concerning standards maintenance, the SAA Standards Committee charged a new Technical Subcommittee for Encoded Archival Description (TS-EAD) to oversee the
maintenance of the standard. Recognizing that EAD needed an update, its charge instructed TS-EAD to complete a revision of the standard within five years. </p>
<p>TS-EAD completed the revision of EAD with the help of the SAA Schema Development Team and with many contributions, large and small, from the international EAD community. EAD3 is the result of four
public comment periods, countless feedback, three working meetings, numerous conference calls, regular presentations to the EAD Roundtable, and lots of careful analysis, spirited discussion, and
hard-won compromise. Notable milestones in the revision process include the initial comment period, which shaped our early agenda; a three-day TS-EAD working meeting at Yale University’s Beinecke Rare
Book and Manuscript Library, which established a clear direction; and the alpha, beta, and gamma schema releases, which gave the EAD community concrete examples to test and critique. </p>
<p>Early in the revision process TS-EAD published four points of emphasis to guide us as we weighed the benefits of changes to EAD. </p>
<list type="simple">
<item>Achieving greater conceptual and semantic consistency in the use of EAD.</item>
<item>Exploring mechanisms whereby EAD-encoded information might more seamlessly and effectively connect with, exchange, or incorporate data maintained according to other protocols.</item>
<item>Improving the functionality of EAD for representing descriptive information created in international and particularly in multilingual environments.</item>
<item>Being mindful that a new version will affect current users.</item>
</list>
<p>All of the changes made in EAD3 can be seen in the context of these four points. Throughout the revision process, the most difficult decisions concerned proposals that highlighted tensions between them,
especially between making EAD more consistent and aligned to other standards and mitigating impact on current users.</p>
<p>TS-EAD’s decision-making process focused on detailed analysis and consensus-building within the committee. As we received proposals from the community or fellow committee members, individuals or small
groups did additional work to better understand the request, clarify the specific impact on the schema, and make recommendations to the committee. Many issues were revisited multiple times as we
collectively came to understand better our goals and their impact. Although healthy differences of opinion persisted throughout the revision process, ultimately only one issue had to be decided by an
executive decision by the co-chairs. In the alpha schema element and attribute names were converted to camel case, as is the convention in EAC-CPF. This met our goals of conceptual consistency and
interoperability with EAC-CPF, but we received strong feedback from the community arguing against the change. Entrenched and opposing opinions – all with strong justifications from our points of
emphasis – remained within TS-EAD; ultimately the co-chairs decided to honor precedent and sensitivity to the impact on users and opted to remove camel case.</p>
<p>Of the changes made in EAD3, the most extensive departure from EAD 2002 is the replacement of <gi>eadheader</gi> with <gi>control</gi>. Borrowed from EAC-CPF with some enhancements, <gi>control</gi>
offers a better model for representing information about finding aids, including its identifiers, status, languages, conventions, maintenance history, and sources. One notable change to <gi>control</gi>
as modelled in EAC-CPF is the inclusion of <gi>filedesc</gi> from <gi>eadheader</gi>. As an aggregation of descriptions of all the material in an archival collection, finding aids have bibliographic
attributes, such as a title or a publication statement captured in <gi>filedesc</gi>, that are not necessary when documenting authority records.</p>
<p>The elements available within <gi>did</gi> (Descriptive Identification) were extensively updated in order to better support the exchange of key descriptive data between EAD3 and other systems. Some
<gi>did</gi> elements, including <gi>origination</gi>, <gi>repository</gi>, and <gi>langmaterial</gi>, were modified to remove mixed content and other ambiguities. The existing <gi>unitdate</gi> and
<gi>physdesc</gi> elements were felt to be too lax to constrain and still provide a forward migration path, so new <gi>unitdatestructured</gi> and <gi>physdescstructured</gi> elements were added.
These "structured" elements provide nuanced data models for capturing temporal and physical description, while the original elements remain in modified form as unstructured alternatives and to allow for
forward migration from EAD 2002. Whereas these new elements provided additional structure, the <gi>daogrp</gi> element, which allowed the creation of extended links to digital archival objects, was
simplified to <gi>daoset</gi>, which binds two or more simple <gi>dao</gi> elements.</p>
<p>The access point elements available within <gi>controlaccess</gi>, e.g. <gi>persname</gi>, <gi>subject</gi>, <gi>genreform</gi>, etc., were modified in several ways. Each must now contain one or more
<gi>part</gi> elements so that multi-part terms may be accurately represented in EAD, allowing, for example, the separate capture of an individual’s surname, forename, and life dates, etc. They also
now share a common set of attributes to improve interoperability with external vocabularies: <att>identifier</att>, for the code or URI associated with a term, <att>source</att>, for identifying the
originating vocabulary, and <att>rules</att>, for recording how terms are formulated. The <gi>geogname</gi> element now has an optional child <gi>geographiccoordinates</gi> for encoding longitude,
latitude, and altitude information.</p>
<p>Support for multilingual description was addressed by adding <att>lang</att> and <att>script</att> attributes to all non-empty elements in EAD3, making it possible to explicitly state what language or
script is used therein. Additionally, some elements were modified to allow them to repeat where previously they did not, thus enabling the inclusion of the same data in multiple languages.</p>
<p>Early in the revision process there were multiple requests to simplify EAD, and one suggested measure was reducing the number of elements. However, TS-EAD decided that consistency and semantic clarity
was a better measure of simplicity, not the number of elements in the schema. The <gi>note</gi> element is a useful case study. In EAD 2002 <gi>note</gi> was available in 8 distinct contexts, each
representing a subtly different usage; in EAD3 the <gi>note</gi> element has been replaced with context-specific elements, including <gi>didnote</gi>, <gi>controlnote</gi>, and <gi>footnote</gi>.</p>
<p>Many other changes can be categorized as supporting the drive for greater conceptual and sematic consistency in EAD. Major descriptive elements that previously could be contained in other descriptive
elements were removed in those contexts. For example, <gi>arrangement</gi> is no longer a permitted child of <gi>scopecontent</gi>, <gi>unitdate</gi> is no longer a permitted child of
<gi>unittitle</gi>, and <gi>dao</gi> is now only available within <gi>did</gi>. Block and formatting elements like <gi>list</gi>, <gi>blockquote</gi>, <gi>quote</gi>, were modified or created to more
closely resemble their HTML counterparts. The <gi>chronlist</gi> element was updated to incorporate <gi>geogname</gi> to convey the locations where events occur, more closely aligning it with its
namesake in EAC-CPF. Mixed content models were streamlined to three progressively inclusive sets of elements allowed to intermix with text. Attribute names were disambiguated throughout the schema:
<att>role</att> was changed to <att>relator</att> on access point elements and <att>linkrole</att> on linking elements, <att>type</att> was renamed through the schema to <att>localtype</att> where no
values are supplied by the schema, and to @elementnametype (e.g. <att>listtype</att> and <att>unitdatetype</att>) where specified values are supplied. Linking elements – of which there were many in EAD
2002 – were consolidated to a handful and limited to simple links, eliminating overly complicated extended links. The XLink model for linking attributes was preserved, but the XLink namespace, which had
been added to the schema versions of EAD 2002, was removed due to the onerous and needless complexity that namespaces introduce when processing XML. Elements that existed solely to support formatting
and presentation or were otherwise deemed out of scope for archival description were deprecated, including <gi>frontmatter</gi>, <gi>descgrp</gi>, <gi>runner</gi>, <gi>imprint</gi>, and
<gi>bibseries</gi>. </p>
<p>The feature of EAD3 that caused the most heated discussion within TS-EAD was the inclusion of the <gi>relations</gi> element. Introduced in EAC-CPF and added to EAD3 with some modifications,
<gi>relations</gi> is available at any level of description and contains one or more <gi>relation</gi> elements. A <gi>relation</gi> describes – in a Linked Open Data-friendly way – the relationship
between the records being described and a corporate body, person or family; an archival or bibliographic resource; a function; or another type of external entity. That relationship can be an actionable
link and may be qualified by supplying relevant dates or geographic names. XML describing the related entity may be embedded within the <gi>objectxmlwrap</gi> element.</p>
<p>TS-EAD could not reach a consensus regarding the inclusion of <gi>relations</gi>. Some members felt strongly that including <gi>relations</gi> was essential in order to support rich Linked Open Data
applications, align with EAC-CPF, and acknowledge draft guidelines on relationships in archival description published by the ICA Committee on Best Practices and Standards. Others felt that it duplicated
functionality present in <gi>controlaccess</gi> and other existing elements, added unnecessary complexity, and that incorporating robust support for Linked Open Data was premature. We ultimately
negotiated a compromise: <gi>relations</gi> would be included in EAD3 as an "experimental" element. As an experimental element, it is not guaranteed that <gi>relations</gi> will persist in the next
version of EAD in its current form. However, TS-EAD encourages its use so that the EAD community will learn more about how the <gi>relations</gi> model works within archival description. Put simply, a
consensus will require more data and experience, and including <gi>relations</gi> provisionally makes that possible.</p>
<p>The revision of EAD 1.0 to EAD 2002 established a precedent that elements to be removed from EAD would first be deprecated – suppressed but available if necessary – before being removed from subsequent
versions. All elements deprecated in EAD 2002 were removed from EAD3. TS-EAD endeavored to honor the commitment to deprecate removed elements, however the extent of the changes in EAD3 made
comprehensive deprecation impossible. Elements to be removed entirely from the standard remain available in undeprecated versions of EAD3. These include <gi>frontmatter</gi>, <gi>descgrp</gi>,
<gi>imprint</gi>, <gi>bibseries</gi>, and <gi>runner</gi>, as well as the <att>tpattern</att> attribute. Elements that were replaced by other elements offering commensurate functionality, or whose
availability within the standard changed are in most cases not supported in undeprecated EAD3. Two exceptions to that rule are the full EAD 2002 versions of <gi>physdesc</gi> and <gi>unitdate</gi>
within <gi>unittitle</gi>, both of which are available in undeprecated EAD3.</p>
<p>EAD3 replaces EAD 2002 as the current, official version of EAD. EAD 2002 was available as a DTD, Relax NG schema, and W3C schema. Additionally, the DTD could be edited to enable the inclusion of
deprecated elements. EAD3 continues to be available in DTD, Relax NG, and W3C versions. For repositories who choose to continue to use deprecated elements, an undeprecated version of EAD3 is available
in DTD, Relax NG, and W3C varieties. Due to differences between DTDs and schemas, the <gi>objectxmlwrap</gi> element is not available in the DTD versions of EAD3. A Schematron schema is also available
to provide further validation functionality for EAD instances, imposing data constraints that either cannot be expressed in DTD, Relax NG, and W3C, or were intentionally removed from the schemas by
TS-EAD due to challenges of maintaining code lists outside of our control or to allow alternative data sources or patterns.</p>
<p>All code related to EAD3, including the schemas and DTDs, Schematron schema, and migration style sheet, will be shared with a Creative Commons CC0 license, placing them in the public domain. This tag
library is published with a Creative Commons CC BY license, allowing others to distribute, remix, tweak, and build upon it, even commercially, as long as they credit SAA for the original tag
library.</p>
<p>EAD3 was possible because of the generous support of the Society of American Archivists, the Gladys Krieble Delmas Foundation, the National Endowment for the Humanities, the Nationaal Archief of the
Netherlands, the Beinecke Rare Book and Manuscript Library, the Institute for Advanced Technology in the Humanities at the University of Virginia, and OCLC Research. Each member of TS-EAD* made
invaluable contributions to EAD3, but two merit special mention: Terry Catapano, Schema Development Team chair, for leading the technical development of EAD3, and Kelcy Shepherd, for leading the
revision of the Tag Library.</p>
<p>Mike Rush</p>
<p>Bill Stockting</p>
<p>TS-EAD Co-Chairs</p>
<p>*TS-EAD members during the revision process included Mike Rush, co-chair, Yale University; Bill Stockting, co-chair, British Library (UK); Kerstin Arnold, Bundesarchiv (Germany); Michael Fox, Minnesota
Historical Society; Kris Kiesling, University of Minnesota; Angelika Menne-Haritz, Bundesarchiv (Germany); Kelcy Shepherd, University of Massachusetts and Amherst College; Claire Sibille, Direction
Générale des Patrimoines (France); Henny van Schie, Nationaal Archief / Bibliotheek (Netherlands); and Brad Westbrook, University of California, San Diego, and ArchivesSpace. Notable ex-officio
contributors included Jodi Allison-Bunnell, Orbis Cascade Alliance (EAD Roundtable); Anila Angjeli, Bibliothèque nationale de France (TS-EAC); Hillel Arnold, Rockefeller Archives Center (EAD
Roundtable); Mark Custer, Yale University (EAD Roundtable); Merrilee Proffitt, OCLC Research; Ruth Kitchin Tillman, Cadence Group (EAD Roundtable); and Katherine Wisser, Simmons College (TS-EAC). Schema
Development Team members included Terry Catapano, chair, Columbia University; Karin Bredenberg, Riksarkivet of Sweden; Florence Clavaud, National Archives of France; Michele Combs, Syracuse University;
María A. Matienzo, Yale University and DPLA; Daniel Pitti, University of Virginia; and Salvatore Vassallo, Università degli Studi di Pavia (Italy).</p>
</div>
<div xml:id="preface-1.1.0">
<head>Preface to Revision 1.1.0</head>
<p>EAD3 underwent its first revision from 2018 January 16 to 2018 February 28 in order to address schema errors and expand the standard's element set. This revision consisted of seven changes - one new
element (rightsdeclaration), two schema bugfixes, and four datatype/attribute extensions. These changes reflect feedback on the EAD3 1.0.0 release and accomodate requirements for data sharing set forth
by consortial members.</p>
<p>EAD3 Revision 1.1.0 sets a new policy for schema releases, in which smaller updates and fixes can be released on a regular basis. These changes will not invalidate existing records, nor will it break
existing interoperability - minor revisions will only be expansive.</p>
<p>This update was revised and implemented by the SAA Technical Subcommittee for Encoded Archival Standards (TS-EAS), following a period of feedback in January-February 2018.</p>
</div>
<div xml:id="preface-1.1.1">
<head>Preface to Revision 1.1.1</head>
<p>EAD3 underwent its first patch revision in 2019. This patch includes one change to the <gi>ref</gi> element, which now allows <gi>foreign</gi> as sub-element and two fixes to the XSD schema.</p>
<p>Furthermore, the updated EAD3 tag library includes additional as well as extended examples for certain elements.</p>
</div>
<div xml:id="preface-1.1.2">
<head>Preface to Revision 1.1.2</head>
<p>EAD3 underwent its second minor revision in 2023. This patch includes updates to external controlled vocabularies, a fix to the <att>parallel</att> attribute, and an example update to <att>linkrole</att>.</p>
</div>
<div xml:id="conventions">
<head>Tag Library Conventions</head>
<p>The EAD Elements section of the Tag Library contains descriptions of 165 elements, arranged alphabetically by element name. It presents information for each element as shown in Figure 1.</p>
<figure>
<graphic url="EAD_figure1.jpg"/>
<p>Figure 1. Layout of element descriptions.</p>
</figure>
<p>Entries in the Tag Library that have been updated in the latest revision will be marked with "(revised in [revision number])". Updates that predate the most recent revision will not be marked in the
text.</p>
<list type="gloss">
<label>Tag Name: </label>
<item>Short, mnemonic form of the element name that is used in the machine-readable encoded document. The tag name is the first word at the top of the page. Tag names appear between angle brackets,
e.g., <gi>archdesc</gi>, except in the listings under "May occur within" and "May contain," and are always in lowercase.</item>
<label>Element Name:</label>
<item>Expanded version of the tag name that more fully describes the element's meaning. The full name of the element is usually a word or phrase that identifies the element's purpose. In the Tag
Library, the element name follows the tag name on the page defining that element and appears with initial capital letters, e.g., <gi>archdesc</gi> Archival Description.</item>
<label>Summary:</label>
<item>A brief statement that provides a concise definition of the element, suitable for quick reference.</item>
<label>May Contain:</label>
<item>Identifies what child nodes (text or elements) may occur within the element being defined. Elements are listed in alphabetical order by tag name. Elements may be empty (e.g., an element which
allows no child text or element nodes), or they may contain text (listed as [text]), other elements, or a mixture of text and other elements.<lb/>Text content cannot include characters that would be
interpreted by a parser as action codes. For example, a left angle bracket has to be represented as the character entity reference &lt; so that it is not misinterpreted as the start of an element
name. </item>
<label>May Occur Within:</label>
<item>Identifies all of the parent elements within which the described element may appear, listed in alphabetical order by tag name. This information conveys information about where and how often an
element is available throughout the schema. The definitions for parent elements may provide additional information about an element's usage.</item>
<label>Attributes:</label>
<item>Identifies all attributes that can be associated with an element. Attributes are represented in lowercase letters in XML coding. The Tag Library uses the convention of preceding an attribute name
with an @ symbol (e.g., <att>identifier</att>), following XPath syntax. See the EAD Attributes section of the tag library for definitions and additional information.</item>
<label>Description and Usage:</label>
<item>This section begins with one or more paragraphs that provide a more thorough description of the element than that found in the Summary, which may be followed by guidance on use. The terms "parent"
and "child" are used to indicate hierarchical relationships between elements. Standard terminology is also used to suggest the kind of element being discussed. "Wrapper element" indicates an element
that cannot contain text directly; a second, nested element must be opened first. Wrapper elements designate sets of elements that comprise a distinctive section of a finding aid, for example, the
Descriptive Identification <gi>did</gi>. "Generic element" refers to elements common to many kinds of documents that contain information not specifically related to archival description, e.g.,
<gi>name</gi> and <gi>num</gi>. "Formatting element" indicates elements that can be used to invoke special text presentation, such as block quotes, chronologies, and emphasis. When the schema
enforces a specific sequence of child elements, that sequence is indicated.<lb/>If useful, context-specific guidance for the usage of an element’s attributes is given in an "Attribute usage" section.
A "See also" section may be provided to indicate additional elements that are similar, easily confused, or otherwise related to the element being described.</item>
<label>Availability:</label>
<item>Indicates, within the context of its parent(s), whether the element is required or optional, and whether or not it is repeatable. </item>
<label>References:</label>
<item>Identifies corresponding elements in other standards, schemas, and markup languages: ISAD(G), MARC, MODS, and HTML. Full crosswalks for ISAD(G), MARC21, and MODS are found in Appendix A. </item>
<label>Examples:</label>
<item>Most element descriptions include a tagged example to indicate how attributes and elements can be used together. Many of the examples are taken from real finding aids; others have been specially
constructed for the Tag Library. The examples illustrate any required sequences of elements, as in the case of children within <gi>control</gi>, or required attributes such as <att>level</att> in
<gi>archdesc</gi>. In other cases, the examples simply show what is possible. Some examples have ellipses, either between or within elements, indicating that other elements or text have been
omitted. Some elements have multiple examples—one may show very dense markup with numerous attributes while another may illustrate a minimalist approach to the markup. Either approach is valid in
EAD, and it is up to the repository to determine the optimal level of markup based on their specific purposes, functional requirements, resources, or consortial guidelines.</item>
</list>
</div>
</div>
</front>
<body>
<div type="attributes" xml:id="EADAttributes">
<div type="Introduction">
<head>Introduction</head>
<p>Attributes are associated with most of the elements contained in EAD. Attributes reflect named properties of an element and may take on different values, depending on the context in which they occur. In
order to set one or more attributes, an encoder should include the name of the attribute(s) within the same angle brackets as the start tag, together with the value(s) to which the attribute(s) is/are
to be set. That is,<lb/>
<code><[tag] [attribute]="[value]"></code>
<lb/> or<lb/>
<code><[tag] [attribute1]="[value1]" [attribute2]="[value2]"></code>
</p>
<p>For example: <lb/>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="eng" valid="true">
<ead:unitdate unitdatetype="inclusive">1937-1992</ead:unitdate>
</egXML>
<lb/> or<lb/>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="eng" valid="true">
<ead:unitdate unitdatetype="inclusive" normal="1937/1992">1937-1992 </ead:unitdate>
</egXML>
</p>
<p>Most attributes are optional, though some are required. The attribute description indicates whether an attribute is required. This information is also available in the Attributes section of each element
description.</p>
<p>The value of attributes may be constrained by the schema using specific attribute type values. For example, <att>id</att> attribute is of type ID, which constrains its value to a string beginning with
an alphabetic character. An <att>id</att> value must be unique within the EAD instance within which it occurs, that is, no other tag in the entire document can have the same <att>id</att> value. EAD
attributes have the following data types <note>(capitalization of data types follows the documentation found in the W3C Recommendation <title>XML Schema Part 2: Datatypes Second Edition</title> (<ref
target="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</ref>)</note>:</p>
<list type="gloss">
<label>anyURI:</label>
<item>A Uniform Resource Identifier. This may be a Uniform Resource Locator (URL) or a Uniform Resource Name (URN). Both relative and absolute URIs are allowed.</item>
<label>ENTITY:</label>
<item>The name of a nonparsed entity that has been declared in the declaration subset of the document. For example, <att>entityref</att> must contain the name of an entity that has been declared in the
declaration subset. Processing software can use the reference to the nonparsed entity to display the entity in the body of the text or in a new window.</item>
<label>ID:</label>
<item>Unique identifier. For example, most elements have an <att>id</att>, so that a unique code can be established for and used to refer to that specific element. The content of the <att>id</att> is of
the type called "ID". Parsers verify that the value of attributes of type "ID" are unique. The values of <att>id</att> must begin with an alpha, not numeric, character, either upper or lowercase, and
may contain a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. See also attributes of type "IDREF."</item>
<label>IDREF:</label>
<item>ID reference value; must match an existing ID of another element in the document. For example, the <gi>ptr</gi> element has a <att>target</att> attribute that can only be an "IDREF," which means
it has to reference a valid ID in another element.</item>
<label>IDREFS:</label>
<item>List of ID reference values.</item>
<label>NMTOKEN:</label>
<item>A name token, which can consist of any alpha or numeric character, as well as a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. A number of attributes in EAD where a
character string from a code list is to be used are of the type "NMTOKEN".</item>
<label>string:</label>
<item>The most general data type, a string can contain any sequence of characters allowed in XML. Certain characters may have to be represented with an entity reference, for example &lt; for <,
and &amp; for &.</item>
<label>token:</label>
<item>A type of string that may not contain carriage return, line feed or tab characters, leading or trailing spaces, and any internal sequence of two or more spaces.</item>
</list>
<p>The attribute value definitions in the DTD versions of EAD3 differ slightly from those of the Relax NG and W3C Schema versions. The DTD has a limited set of attribute types so the anyURI, token, and
string data types were converted to "CDATA" (i.e. Character Data).</p>
<p>When the EAD schema limits attribute values to a few choices, those values are declared in the schema in what is known as a "closed list." For example, the values of <att>audience</att> are limited to
either "external" or "internal." Other attributes are associated with semi-closed lists. Such lists include those values believed to be the most useful in many contexts, but other values are allowed.
For example, <gi>dsc</gi> defines several values for <att>dsctype</att>, including "otherdsctype" which may be used with <att>otherdsctype</att> to specify values that are not in the semi-closed list
for <att>dsctype</att>. The definitions for some values in the closed and semi-closed lists appear below.</p>
<p>The following is a complete list of all the attributes that occur in EAD, and some discussion of how they may be used. Further, context-specific information about the use of certain attributes may be
found in the "Attribute usage" section of the element descriptions.</p>
</div>
<xi:include href="ead3/en/attr-abbr.xml" parse="xml"/>
<xi:include href="ead3/en/attr-actuate.xml" parse="xml"/>
<xi:include href="ead3/en/attr-align.xml" parse="xml"/>
<xi:include href="ead3/en/attr-althead.xml" parse="xml"/>
<xi:include href="ead3/en/attr-altrender.xml" parse="xml"/>
<xi:include href="ead3/en/attr-approximate.xml" parse="xml"/>
<xi:include href="ead3/en/attr-arcrole.xml" parse="xml"/>
<xi:include href="ead3/en/attr-audience.xml" parse="xml"/>
<xi:include href="ead3/en/attr-base.xml" parse="xml"/>
<xi:include href="ead3/en/attr-calendar.xml" parse="xml"/>
<xi:include href="ead3/en/attr-certainty.xml" parse="xml"/>
<xi:include href="ead3/en/attr-char.xml" parse="xml"/>
<xi:include href="ead3/en/attr-charoff.xml" parse="xml"/>
<xi:include href="ead3/en/attr-colname.xml" parse="xml"/>
<xi:include href="ead3/en/attr-colnum.xml" parse="xml"/>
<xi:include href="ead3/en/attr-cols.xml" parse="xml"/>
<xi:include href="ead3/en/attr-colsep.xml" parse="xml"/>
<xi:include href="ead3/en/attr-colwidth.xml" parse="xml"/>
<xi:include href="ead3/en/attr-containerid.xml" parse="xml"/>
<xi:include href="ead3/en/attr-coordinatesystem.xml" parse="xml"/>
<xi:include href="ead3/en/attr-countrycode.xml" parse="xml"/>
<xi:include href="ead3/en/attr-countryencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-coverage.xml" parse="xml"/>
<xi:include href="ead3/en/attr-daotype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-datechar.xml" parse="xml"/>
<xi:include href="ead3/en/attr-dateencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-dsctype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-encodinganalog.xml" parse="xml"/>
<xi:include href="ead3/en/attr-entityref.xml" parse="xml"/>
<xi:include href="ead3/en/attr-era.xml" parse="xml"/>
<xi:include href="ead3/en/attr-expan.xml" parse="xml"/>
<xi:include href="ead3/en/attr-frame.xml" parse="xml"/>
<xi:include href="ead3/en/attr-href.xml" parse="xml"/>
<xi:include href="ead3/en/attr-id.xml" parse="xml"/>
<xi:include href="ead3/en/attr-identifier.xml" parse="xml"/>
<xi:include href="ead3/en/attr-instanceurl.xml" parse="xml"/>
<xi:include href="ead3/en/attr-label.xml" parse="xml"/>
<xi:include href="ead3/en/attr-lang.xml" parse="xml"/>
<xi:include href="ead3/en/attr-langcode.xml" parse="xml"/>
<xi:include href="ead3/en/attr-langencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-lastdatetimeverified.xml" parse="xml"/>
<xi:include href="ead3/en/attr-level.xml" parse="xml"/>
<xi:include href="ead3/en/attr-linkrole.xml" parse="xml"/>
<xi:include href="ead3/en/attr-linktitle.xml" parse="xml"/>
<xi:include href="ead3/en/attr-listtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-localtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-mark.xml" parse="xml"/>
<xi:include href="ead3/en/attr-morerows.xml" parse="xml"/>
<xi:include href="ead3/en/attr-nameend.xml" parse="xml"/>
<xi:include href="ead3/en/attr-namest.xml" parse="xml"/>
<xi:include href="ead3/en/attr-normal.xml" parse="xml"/>
<xi:include href="ead3/en/attr-notafter.xml" parse="xml"/>
<xi:include href="ead3/en/attr-notbefore.xml" parse="xml"/>
<xi:include href="ead3/en/attr-numeration.xml" parse="xml"/>
<xi:include href="ead3/en/attr-otherdaotype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-otherdsctype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-otherlevel.xml" parse="xml"/>
<xi:include href="ead3/en/attr-otherphysdescstructuredtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-otherrelationtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-parallel.xml" parse="xml"/>
<xi:include href="ead3/en/attr-parent.xml" parse="xml"/>
<xi:include href="ead3/en/attr-pgwide.xml" parse="xml"/>
<xi:include href="ead3/en/attr-physdescstructuredtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-relatedencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-relationtype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-relator.xml" parse="xml"/>
<xi:include href="ead3/en/attr-render.xml" parse="xml"/>
<xi:include href="ead3/en/attr-repositorycode.xml" parse="xml"/>
<xi:include href="ead3/en/attr-repositoryencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-rowsep.xml" parse="xml"/>
<xi:include href="ead3/en/attr-rules.xml" parse="xml"/>
<xi:include href="ead3/en/attr-script.xml" parse="xml"/>
<xi:include href="ead3/en/attr-scriptcode.xml" parse="xml"/>
<xi:include href="ead3/en/attr-scriptencoding.xml" parse="xml"/>
<xi:include href="ead3/en/attr-show.xml" parse="xml"/>
<xi:include href="ead3/en/attr-source.xml" parse="xml"/>
<xi:include href="ead3/en/attr-standarddate.xml" parse="xml"/>
<xi:include href="ead3/en/attr-standarddatetime.xml" parse="xml"/>
<xi:include href="ead3/en/attr-target.xml" parse="xml"/>
<xi:include href="ead3/en/attr-transliteration.xml" parse="xml"/>
<xi:include href="ead3/en/attr-unit.xml" parse="xml"/>
<xi:include href="ead3/en/attr-unitdatetype.xml" parse="xml"/>
<xi:include href="ead3/en/attr-valign.xml" parse="xml"/>
<xi:include href="ead3/en/attr-value.xml" parse="xml"/>
<xi:include href="ead3/en/attr-xpointer.xml" parse="xml"/>
</div>
<div type="elements" xml:id="EADElements">
<xi:include href="ead3/en/elem-abbr.xml" parse="xml"/>
<xi:include href="ead3/en/elem-abstract.xml" parse="xml"/>
<xi:include href="ead3/en/elem-accessrestrict.xml" parse="xml"/>
<xi:include href="ead3/en/elem-accruals.xml" parse="xml"/>
<xi:include href="ead3/en/elem-acqinfo.xml" parse="xml"/>
<xi:include href="ead3/en/elem-address.xml" parse="xml"/>
<xi:include href="ead3/en/elem-addressline.xml" parse="xml"/>
<xi:include href="ead3/en/elem-agencycode.xml" parse="xml"/>
<xi:include href="ead3/en/elem-agencyname.xml" parse="xml"/>
<xi:include href="ead3/en/elem-agent.xml" parse="xml"/>
<xi:include href="ead3/en/elem-agenttype.xml" parse="xml"/>
<xi:include href="ead3/en/elem-altformavail.xml" parse="xml"/>
<xi:include href="ead3/en/elem-appraisal.xml" parse="xml"/>
<xi:include href="ead3/en/elem-archdesc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-archref.xml" parse="xml"/>
<xi:include href="ead3/en/elem-arrangement.xml" parse="xml"/>
<xi:include href="ead3/en/elem-author.xml" parse="xml"/>
<xi:include href="ead3/en/elem-bibliography.xml" parse="xml"/>
<xi:include href="ead3/en/elem-bibref.xml" parse="xml"/>
<xi:include href="ead3/en/elem-bioghist.xml" parse="xml"/>
<xi:include href="ead3/en/elem-blockquote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c01.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c02.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c03.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c04.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c05.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c06.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c07.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c08.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c09.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c10.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c11.xml" parse="xml"/>
<xi:include href="ead3/en/elem-c12.xml" parse="xml"/>
<xi:include href="ead3/en/elem-chronitem.xml" parse="xml"/>
<xi:include href="ead3/en/elem-chronitemset.xml" parse="xml"/>
<xi:include href="ead3/en/elem-chronlist.xml" parse="xml"/>
<xi:include href="ead3/en/elem-citation.xml" parse="xml"/>
<xi:include href="ead3/en/elem-colspec.xml" parse="xml"/>
<xi:include href="ead3/en/elem-container.xml" parse="xml"/>
<xi:include href="ead3/en/elem-control.xml" parse="xml"/>
<xi:include href="ead3/en/elem-controlaccess.xml" parse="xml"/>
<xi:include href="ead3/en/elem-controlnote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-conventiondeclaration.xml" parse="xml"/>
<xi:include href="ead3/en/elem-corpname.xml" parse="xml"/>
<xi:include href="ead3/en/elem-custodhist.xml" parse="xml"/>
<xi:include href="ead3/en/elem-dao.xml" parse="xml"/>
<xi:include href="ead3/en/elem-daoset.xml" parse="xml"/>
<xi:include href="ead3/en/elem-date.xml" parse="xml"/>
<xi:include href="ead3/en/elem-daterange.xml" parse="xml"/>
<xi:include href="ead3/en/elem-dateset.xml" parse="xml"/>
<xi:include href="ead3/en/elem-datesingle.xml" parse="xml"/>
<xi:include href="ead3/en/elem-defitem.xml" parse="xml"/>
<xi:include href="ead3/en/elem-descriptivenote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-did.xml" parse="xml"/>
<xi:include href="ead3/en/elem-didnote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-dimensions.xml" parse="xml"/>
<xi:include href="ead3/en/elem-dsc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-ead.xml" parse="xml"/>
<xi:include href="ead3/en/elem-edition.xml" parse="xml"/>
<xi:include href="ead3/en/elem-editionstmt.xml" parse="xml"/>
<xi:include href="ead3/en/elem-emph.xml" parse="xml"/>
<xi:include href="ead3/en/elem-entry.xml" parse="xml"/>
<xi:include href="ead3/en/elem-event.xml" parse="xml"/>
<xi:include href="ead3/en/elem-eventdatetime.xml" parse="xml"/>
<xi:include href="ead3/en/elem-eventdescription.xml" parse="xml"/>
<xi:include href="ead3/en/elem-eventtype.xml" parse="xml"/>
<xi:include href="ead3/en/elem-expan.xml" parse="xml"/>
<xi:include href="ead3/en/elem-famname.xml" parse="xml"/>
<xi:include href="ead3/en/elem-filedesc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-fileplan.xml" parse="xml"/>
<xi:include href="ead3/en/elem-footnote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-foreign.xml" parse="xml"/>
<xi:include href="ead3/en/elem-fromdate.xml" parse="xml"/>
<xi:include href="ead3/en/elem-function.xml" parse="xml"/>
<xi:include href="ead3/en/elem-genreform.xml" parse="xml"/>
<xi:include href="ead3/en/elem-geogname.xml" parse="xml"/>
<xi:include href="ead3/en/elem-geographiccoordinates.xml" parse="xml"/>
<xi:include href="ead3/en/elem-head.xml" parse="xml"/>
<xi:include href="ead3/en/elem-head01.xml" parse="xml"/>
<xi:include href="ead3/en/elem-head02.xml" parse="xml"/>
<xi:include href="ead3/en/elem-head03.xml" parse="xml"/>
<xi:include href="ead3/en/elem-index.xml" parse="xml"/>
<xi:include href="ead3/en/elem-indexentry.xml" parse="xml"/>
<xi:include href="ead3/en/elem-item.xml" parse="xml"/>
<xi:include href="ead3/en/elem-label.xml" parse="xml"/>
<xi:include href="ead3/en/elem-langmaterial.xml" parse="xml"/>
<xi:include href="ead3/en/elem-language.xml" parse="xml"/>
<xi:include href="ead3/en/elem-languagedeclaration.xml" parse="xml"/>
<xi:include href="ead3/en/elem-languageset.xml" parse="xml"/>
<xi:include href="ead3/en/elem-lb.xml" parse="xml"/>
<xi:include href="ead3/en/elem-legalstatus.xml" parse="xml"/>
<xi:include href="ead3/en/elem-list.xml" parse="xml"/>
<xi:include href="ead3/en/elem-listhead.xml" parse="xml"/>
<xi:include href="ead3/en/elem-localcontrol.xml" parse="xml"/>
<xi:include href="ead3/en/elem-localtypedeclaration.xml" parse="xml"/>
<xi:include href="ead3/en/elem-maintenanceagency.xml" parse="xml"/>
<xi:include href="ead3/en/elem-maintenanceevent.xml" parse="xml"/>
<xi:include href="ead3/en/elem-maintenancehistory.xml" parse="xml"/>
<xi:include href="ead3/en/elem-maintenancestatus.xml" parse="xml"/>
<xi:include href="ead3/en/elem-materialspec.xml" parse="xml"/>
<xi:include href="ead3/en/elem-name.xml" parse="xml"/>
<xi:include href="ead3/en/elem-namegrp.xml" parse="xml"/>
<xi:include href="ead3/en/elem-notestmt.xml" parse="xml"/>
<xi:include href="ead3/en/elem-num.xml" parse="xml"/>
<xi:include href="ead3/en/elem-objectxmlwrap.xml" parse="xml"/>
<xi:include href="ead3/en/elem-occupation.xml" parse="xml"/>
<xi:include href="ead3/en/elem-odd.xml" parse="xml"/>
<xi:include href="ead3/en/elem-originalsloc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-origination.xml" parse="xml"/>
<xi:include href="ead3/en/elem-otheragencycode.xml" parse="xml"/>
<xi:include href="ead3/en/elem-otherfindaid.xml" parse="xml"/>
<xi:include href="ead3/en/elem-otherrecordid.xml" parse="xml"/>
<xi:include href="ead3/en/elem-p.xml" parse="xml"/>
<xi:include href="ead3/en/elem-part.xml" parse="xml"/>
<xi:include href="ead3/en/elem-persname.xml" parse="xml"/>
<xi:include href="ead3/en/elem-physdesc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-physdescset.xml" parse="xml"/>
<xi:include href="ead3/en/elem-physdescstructured.xml" parse="xml"/>
<xi:include href="ead3/en/elem-physfacet.xml" parse="xml"/>
<xi:include href="ead3/en/elem-physloc.xml" parse="xml"/>
<xi:include href="ead3/en/elem-phystech.xml" parse="xml"/>
<xi:include href="ead3/en/elem-prefercite.xml" parse="xml"/>
<xi:include href="ead3/en/elem-processinfo.xml" parse="xml"/>
<xi:include href="ead3/en/elem-ptr.xml" parse="xml"/>
<xi:include href="ead3/en/elem-ptrgrp.xml" parse="xml"/>
<xi:include href="ead3/en/elem-publicationstatus.xml" parse="xml"/>
<xi:include href="ead3/en/elem-publicationstmt.xml" parse="xml"/>
<xi:include href="ead3/en/elem-publisher.xml" parse="xml"/>
<xi:include href="ead3/en/elem-quantity.xml" parse="xml"/>
<xi:include href="ead3/en/elem-quote.xml" parse="xml"/>
<xi:include href="ead3/en/elem-recordid.xml" parse="xml"/>
<xi:include href="ead3/en/elem-ref.xml" parse="xml"/>
<xi:include href="ead3/en/elem-relatedmaterial.xml" parse="xml"/>
<xi:include href="ead3/en/elem-relation.xml" parse="xml"/>
<xi:include href="ead3/en/elem-relationentry.xml" parse="xml"/>
<xi:include href="ead3/en/elem-relations.xml" parse="xml"/>
<xi:include href="ead3/en/elem-repository.xml" parse="xml"/>
<xi:include href="ead3/en/elem-representation.xml" parse="xml"/>
<xi:include href="ead3/en/elem-rightsdeclaration.xml" parse="xml"/>
<xi:include href="ead3/en/elem-row.xml" parse="xml"/>
<xi:include href="ead3/en/elem-scopecontent.xml" parse="xml"/>
<xi:include href="ead3/en/elem-script.xml" parse="xml"/>
<xi:include href="ead3/en/elem-separatedmaterial.xml" parse="xml"/>
<xi:include href="ead3/en/elem-seriesstmt.xml" parse="xml"/>
<xi:include href="ead3/en/elem-source.xml" parse="xml"/>
<xi:include href="ead3/en/elem-sourceentry.xml" parse="xml"/>
<xi:include href="ead3/en/elem-sources.xml" parse="xml"/>
<xi:include href="ead3/en/elem-sponsor.xml" parse="xml"/>
<xi:include href="ead3/en/elem-subject.xml" parse="xml"/>
<xi:include href="ead3/en/elem-subtitle.xml" parse="xml"/>
<xi:include href="ead3/en/elem-table.xml" parse="xml"/>
<xi:include href="ead3/en/elem-tbody.xml" parse="xml"/>
<xi:include href="ead3/en/elem-term.xml" parse="xml"/>
<xi:include href="ead3/en/elem-tgroup.xml" parse="xml"/>
<xi:include href="ead3/en/elem-thead.xml" parse="xml"/>
<xi:include href="ead3/en/elem-title.xml" parse="xml"/>
<xi:include href="ead3/en/elem-titleproper.xml" parse="xml"/>
<xi:include href="ead3/en/elem-titlestmt.xml" parse="xml"/>
<xi:include href="ead3/en/elem-todate.xml" parse="xml"/>
<xi:include href="ead3/en/elem-unitdate.xml" parse="xml"/>
<xi:include href="ead3/en/elem-unitdatestructured.xml" parse="xml"/>
<xi:include href="ead3/en/elem-unitid.xml" parse="xml"/>
<xi:include href="ead3/en/elem-unittitle.xml" parse="xml"/>
<xi:include href="ead3/en/elem-unittype.xml" parse="xml"/>
<xi:include href="ead3/en/elem-userestrict.xml" parse="xml"/>
</div>
</body>
<back>
<div type="appendix" xml:id="appendixA">
<head>Appendix A : EAD Crosswalks</head>
<div>
<head>ISAD(G) to EAD3</head>
<list type="simple">
<label>ISAD(G)</label>
<item>EAD</item>
<label>3.1.1 Reference code(s)</label>
<item>
<gi>agencycode</gi> and <gi>recordid</gi> within <gi>control</gi>; <gi>unitid</gi> with <att>countrycode</att> and <att>repositorycode</att>
</item>
<label>3.1.2 Title</label>
<item>
<gi>unittitle</gi>
</item>
<label>3.1.3 Dates</label>
<item>
<gi>unitdate</gi>, <gi>unitdatestructured</gi>
</item>
<label>3.1.4 Level of description</label>
<item>
<gi>archdesc</gi> and <gi>c</gi>
<att>level</att>
</item>
<label>3.1.5 Extent and medium of the unit</label>
<item>
<gi>physdesc</gi>, <gi>physdescstructured</gi>
</item>
<label>3.2.1 Name of creator</label>
<item>
<gi>origination</gi>
</item>
<label>3.2.2 Administrative/Biographical history</label>
<item>
<gi>bioghist</gi>
</item>
<label>3.2.3 Archival history</label>
<item>
<gi>custodhist</gi>
</item>
<label>3.2.4 Immediate source of acquisition</label>
<item>
<gi>acqinfo</gi>
</item>
<label>3.3.1 Scope and content</label>
<item>
<gi>scopecontent</gi>
</item>
<label>3.3.2 Appraisal, destruction and scheduling</label>
<item>
<gi>appraisal</gi>
</item>
<label>3.3.3 Accruals</label>
<item>
<gi>accruals</gi>
</item>
<label>3.3.4 System of arrangement</label>
<item>
<gi>arrangement</gi>
</item>
<label>3.4.1 Conditions governing access</label>
<item>
<gi>accessrestrict</gi>
</item>
<label>3.4.2 Conditions governing reproduction</label>
<item>
<gi>userestrict</gi>
</item>
<label>3.4.3 Language/scripts of material</label>
<item>
<gi>langmaterial</gi>
</item>
<label>3.4.4 Physical characteristics and technical requirements</label>
<item>
<gi>phystech</gi>
</item>
<label>3.4.5 Finding aids</label>
<item>
<gi>otherfindaid</gi>
</item>
<label>3.5.1 Existence and location of originals</label>
<item>
<gi>originalsloc</gi>
</item>
<label>3.5.2 Existence and location of copies</label>
<item>
<gi>altformavail</gi>
</item>
<label>3.5.3 Related units of description</label>
<item>
<gi>relatedmaterial</gi>, <gi>separatedmaterial</gi>
</item>
<label>3.5.4 Publication note</label>
<item>
<gi>bibliography</gi>
</item>
<label>3.6.1 Note</label>
<item>
<gi>didnote</gi>, <gi>odd</gi>
</item>
<label>3.7.1 Archivist's note</label>
<item>
<gi>processinfo</gi>
</item>
<label>3.7.2 Rules or conventions</label>
<item>
<gi>conventiondeclaration</gi>
</item>
<label>3.7.3 Date(s) of descriptions</label>
<item>
<gi>maintenanceevent</gi>/<gi>eventdatetime</gi>
</item>
</list>
</div>
<div>
<head>MARC21 to EAD3</head>
<list type="simple">
<label>MARC</label>
<item>EAD</item>
<label>041 Language</label>
<item>
<gi>langmaterial</gi>/<gi>language</gi>
<att>langcode</att>
</item>
<label>100 Main entry--personal name</label>
<item>
<gi>origination</gi>
<gi>persname</gi>, <gi>origination</gi>
<gi>famname</gi>
</item>
<label>110 Main entry--corporate name</label>
<item>
<gi>origination</gi>
<gi>corpname</gi>
</item>
<label>111 Main entry--meeting name</label>
<item>
<gi>origination</gi>
<gi>corpname</gi>
</item>
<label>130 Main entry--uniform title OR 240 Uniform title</label>
<item>
<gi>unittitle</gi>
</item>
<label>245 Title statement</label>
<item>
<gi>unittitle</gi>
</item>
<label>245$f Title statement/inclusive dates</label>
<item><unitdate unitdatetype="inclusive">, <unitdatestructured unitdatetype="inclusive"> </item>
<label>245$g Title statement/bulk dates</label>
<item><unitdate unitdatetype="bulk">, <unitdatestructured unitdatetype="bulk"></item>
<label>254 Musical presentation statement</label>
<item>
<gi>materialspec</gi>
</item>
<label>255 Cartographic mathematical data</label>
<item>
<gi>materialspec</gi>
</item>
<label>255$c Cartographic mathematical data/statement of coordinates</label>
<item>
<gi>geographiccoordinates</gi>
</item>
<label>256 Computer file characteristics</label>
<item>
<gi>physdescstructured</gi>
<gi>quantity</gi> and <gi>physdescstructured</gi>
<gi>unittype</gi>
</item>
<label>260$c Date</label>
<item>
<gi>unitdate</gi>, <gi>unitdatestructured</gi>
</item>
<label>300 Physical description</label>
<item>
<gi>physdesc</gi>, <gi>physdescstructured</gi> subelements <gi>quantity</gi>, <gi>unittype</gi>, <gi>dimensions</gi>, <gi>physfacet</gi>
</item>
<label>340 Physical medium</label>
<item>
<gi>phystech</gi>
</item>
<label>351 Organization and arrangement</label>
<item>
<gi>arrangement</gi>
</item>
<label>351$c Hierarchical level</label>
<item>
<gi>archdesc</gi>
<att>level</att>
</item>
<label>355 Security classification control</label>
<item>
<gi>accessrestrict</gi>
</item>
<label>500 General note</label>
<item>
<gi>didnote</gi>, <gi>odd</gi>
</item>
<label>506 Restrictions on access note</label>
<item>
<gi>accessrestrict</gi>, <gi>legalstatus</gi>
</item>
<label>510 Citation/references</label>
<item>
<gi>bibliography</gi>
</item>
<label>520 Summary, etc.</label>
<item>
<gi>abstract</gi>, <gi>scopecontent</gi>
</item>
<label>524 Preferred citation of described materials</label>
<item>
<gi>prefercite</gi>
</item>
<label>530 Additional physical form available</label>
<item>
<gi>altformavail</gi>
</item>
<label>535 Location of Originals/Duplicates</label>
<item>
<gi>originalsloc</gi>
</item>
<label>536 Funding information</label>
<item>
<gi>sponsor</gi>
</item>
<label>538 System Details</label>
<item>
<gi>phystech</gi>
</item>
<label>540 Terms governing use and reproduction</label>
<item>
<gi>userestrict</gi>
</item>
<label>541 Immediate source of acquisition</label>
<item>
<gi>acqinfo</gi>
</item>
<label>544 Location of other archival materials</label>
<item>
<gi>relatedmaterial</gi>, <gi>separatedmaterial</gi>
</item>
<label>545 Biographical or historical data</label>
<item>
<gi>bioghist</gi>
</item>
<label>546 Language</label>
<item>
<gi>langmaterial</gi>
</item>
<label>555 Cumulative index/finding aids2 In a MARC21 record a note in the 55 field would mention the existence of the EAD-encoded finding aid, but no specific EAD element maps to this field. The
existence of other finding aids can be noted in <gi>otherfindaid</gi>.</label>
<item/>
<label>561 Ownership and custodial history</label>
<item>
<gi>custodhist</gi>
</item>
<label>581 Publications about described materials</label>
<item>
<gi>bibliography</gi>
</item>
<label>583 Action</label>
<item>
<gi>appraisal</gi>, <gi>processinfo</gi>
</item>
<label>584 Accumulation and frequency of use</label>
<item>
<gi>accruals</gi>
</item>
<label>600 Subject--personal name</label>
<item>
<gi>controlaccess</gi><persname relator="subject">, <gi>controlaccess</gi><famname relator="subject"></item>
<label>610 Subject--corporate name</label>
<item>
<gi>controlaccess</gi><corpname relator="subject"></item>
<label>611 Subject--meeting</label>
<item>
<gi>controlaccess</gi><corpname relator="subject"></item>
<label>630 Subject--uniform title</label>
<item>
<gi>controlaccess</gi><title relator="subject"></item>
<label>650 Subject--topical</label>
<item>
<gi>controlaccess</gi>
<gi>subject</gi>
</item>
<label>651 Subject--geographic name</label>
<item>
<gi>controlaccess</gi><geogname relator="subject"></item>
<label>655 Genre/form</label>
<item>
<gi>controlaccess</gi><gi>genreform</gi>
</item>
<label>656 Occupation</label>
<item>
<gi>controlaccess</gi><gi>occupation</gi>
</item>
<label>657 Function</label>
<item>
<gi>controlaccess</gi><gi>function</gi>
</item>
<label>69x Local subject access</label>
<item>
<gi>controlaccess</gi><subject source="local"></item>
<label>700 Added entry--personal name</label>
<item>
<gi>controlaccess</gi><gi>persname</gi>,<gi>controlaccess</gi><gi>famname</gi>
</item>
<label>710 Added entry--corporate name</label>
<item>
<gi>controlaccess</gi><gi>corpname</gi>
</item>
<label>711 Added entry--meeting name</label>
<item>
<gi>controlaccess</gi><gi>corpname</gi>
</item>
<label>720 Added entry--uncontrolled</label>
<item>
<gi>name</gi>
</item>
<label>730 Added entry--uniform title</label>
<item>
<gi>controlaccess</gi><gi>title</gi>
</item>
<label>740 Added entry--uncont./related anal. title</label>
<item>
<gi>title</gi>
</item>
<label>752 Added entry--hierarchical place name</label>
<item>
<gi>geogname</gi>
</item>
<label>852 Location</label>
<item>
<gi>repository</gi>, <gi>physloc</gi>
</item>
</list>
</div>
<div>
<head>MODS to EAD3</head>
<list type="simple">
<label>MODS</label>
<item>EAD</item>
<label>
<gi>abstract</gi>
</label>
<item>
<gi>abstract</gi>, <gi>scopecontent</gi>
</item>
<label>
<gi>accessCondition</gi>
</label>
<item>
<gi>accessrestrict</gi>
</item>
<label>
<gi>genre</gi>
</label>
<item>
<gi>controlaccess</gi><gi>genreform</gi>
</item>
<label>
<gi>identifier</gi>
</label>
<item>
<gi>unitid</gi>
</item>
<label>
<gi>language</gi><gi>languageTerm</gi>
</label>
<item>
<gi>langmaterial</gi><gi>language</gi>, <gi>langmaterial</gi><gi>languageset</gi><gi>language</gi>
</item>
<label>
<gi>location</gi><gi>physicalLocation</gi>
</label>
<item>
<gi>repository</gi>
</item>
<label>
<gi>location</gi><gi>url</gi>
</label>
<item>
<gi>dao</gi>, <gi>daoset</gi>
</item>
<label>
<gi>name</gi>
</label>
<item>
<gi>origination</gi>
</item>
<label>
<gi>note</gi>
</label>
<item>
<gi>didnote</gi>, <gi>odd</gi>
</item>
<label>
<gi>originInfo</gi><gi>dateCreated</gi>
</label>
<item>
<gi>unitdate</gi>, <gi>unitdatestructured</gi>
</item>
<label>
<gi>physicalDescription</gi><gi>extent</gi>
</label>
<item>
<gi>physdesc</gi>, <gi>physdescstructured</gi><gi>quantity</gi> and <gi>physdescstructured</gi><gi>unittype</gi>, <gi>physdescstructured</gi><gi>dimensions</gi>
</item>
<label>
<gi>recordInfo</gi><gi>recordContentSource</gi>
</label>
<item>
<gi>maintenanceagency</gi><gi>agencyname</gi>, <gi>maintenanceagency</gi><gi>agencycode</gi>, <gi>maintenanceagency</gi><gi>otheragencycode</gi>
</item>
<label>
<gi>recordInfo</gi><gi>recordCreationDate</gi>
</label>
<item>
<gi>maintenancehistory</gi><gi>maintenanceevent</gi><gi>eventdatetime</gi> (where <gi>eventtype</gi> @value='created')</item>
<label>
<gi>recordInfo</gi><gi>recordChangeDate</gi>
</label>
<item>
<gi>maintenancehistory</gi><gi>maintenanceevent</gi><gi>eventdatetime</gi>
</item>
<label>
<gi>recordInfo</gi><gi>recordIdentifier</gi>
</label>
<item>
<gi>recordid</gi>
</item>
<label>
<gi>recordInfo</gi><gi>recordOrigin</gi>
</label>
<item>
<gi>maintenancehistory</gi><gi>maintenanceevent</gi> (where eventtype/@value='created' or 'derived')</item>
<label>
<gi>recordInfo</gi><gi>languageOfCataloging</gi>
</label>