1. EAD Roundtable, SAA 2014, 2014-08-13 Mike Rush, TS-EAD Co-Chair EAD3 PROGRESS REPORT

3. SUPPORT Gladys Krieble Delmas Foundation National Endowment for the Humanities Nationaal Archief of the Netherlands Beinecke Rare Book and Manuscript Library, Yale University Institute for Advanced Technology in the Humanities (IATH), University of Virginia OCLC Research

4. TIMELINE TO DATE Comments October 2010 to February 2011 Revision Forum SAA 2011 TS-EAD Working Meeting March 2012 Schema Dev. Team Meeting October 2012 Alpha Release February 2013 Tag Library Editorial Team Meeting February 2013 Beta Release August 2013 Gamma Release February 2014

5. REMAINING WORKPLAN Finalize deprecation Finalize schema design Schema testing Validation Translation Finalize tag library Migration tools Submit to Standards Committee Submit to SAA Council for adoption Publish Winter 2015

6. BETA RELEASE

7. SUMMARY OF BETA RELEASE FEATURES EAD Revision Highlights Six summaries of changes to EAD as of the Beta release Posted to the EAD List, August – September 2013 Search for “EAD Revision Highlights” at http://listserv.loc.gov/cgi-bin/wa?S1=eadhttp://listserv.loc.gov/cgi-bin/wa?S1=ead

8. BETA / GAMMA FEEDBACK

9. Reinstate various elements Tweak mixed content options Modify enuerated value lists in Address migration concerns for specific elements and attributes Modifications to Additional changes to support multi-language description Bugs

10. POST BETA / GAMMA CHANGES

11. RELATIONS COMPROMISE Included in core EAD3 schema, but… Considered an “experimental” element What is an “experimental” element? TS-EAD could not reach consensus on Concerns about duplication of, complexity of model, etc. Need to see if and how it will be used Should you use if it’s experimental? YES!

12. RELATIONS COMPROMISE Tweaks to elements (persname, subject, function, etc.) to better support Linked Data applications Changed @role to @relator, applied to all access point elements Eliminates confusion with xlink-derived @role used on linking elements @source, @rules, and @identifier added to, which will allow for post- coordinated subject headings

13. DAOGRP / DAOSET Strong call to restore after Beta release Strong desire to eliminate extended links Solution: Create Wrapper element for two or more, with optional Lacks full extended link functionality, but will suffice for most identified uses of

14. DAO TWEAKS Replaced with to remove all block children except Added @coverage as optional attribute to Possible values: whole | part Indicates if is the whole or a part of the unit being described Added @identifier for non-resolving URIs Added @localtype, @label, and @encodinganalog for consistency with other children

15. TWEAKS Added @approximate to Possible values: yes | no The order of and is no longer enforced by the schema (and other access terms) restored to Removed @unit from Removed @rules from and

16. New child of Optional and repeatable @coordinatesystem indicates what coordinate system is used Accepts text only As generic and flexible a solution as possible for what can be very complicated data

17. SMALL CHANGES Added for inline tagging of language and script. Added to all mixed content nodes. Tweaked various mixed content models restored to Made elements repeatable to support multi-language description control/maintenanceagency/agencyname control/maintenancehistsory/maintenanceevent/eventdescription control/sources/source/sourceentry

18. SMALL CHANGES Moved ennumerated element values to @value attribute Added “published” as a value for Added “deletedmerged” as a value for

19. CHANGES NOT MADE not restored not restored as a child of remains a required child of not modified for born digital extents not restored to not given the same content model as not added as a child of

20. DELIVERABLES

21. Revised Schema Relax NG, W3C, and DTD versions Regular and undeprecated DTD will not support full tag set Tag Library Preface + Explanation of changes Element definitions Attribute definitions Examples Crosswalks Migration style sheets

22. DELIVERABLES External validation tools (Schematron) Validate ISO code lists, etc. Enforcing element or attribute co-occurrence Establishing subset profiles Encoding manipulation tools Stylesheet to change between numbered and unnumbered components Updated EAD Cookbook XSLT style sheets EAD3 to HTML EAD3 to PDF

23. GOVERNANCE

24. Single committee for EAD, EAC-CPF, and EAC-F Combine TS-EAD, TS-EAC, Schema Dev. Team Technical Subcommittee for Encoded Archival Standards? Continual revision cycle Accept comments via GitHub on an ongoing basis Release bug fixes and backwards compatible changes as needed Release new full versions when significant non-backwards compatible changes accrue Convergence of EAD and EAC Integration of separate schemas into an interrelated suite of schemas that repurpose elements Integration of documentation into a single site Integration of URIs for elements with URIs for documentation

25. HOW CAN YOU HELP?

26. Encode some EAD3 examples! Needed for testing the schemas and making sure we didn’t miss anything

27. MORE INFORMATION

28. MORE INFORMATION (VIA THE WEB!) TS-EAD Web Site http://www2.archivists.org/groups/technical-subcommittee-on-encoded-archival- description-ead/ead-revision SAA Standards Portal http://www2.archivists.org/groups/technical-subcommittee-on-encoded-archival- description-ead/encoded-archival-description-ead Schema Development Team Github Repository http://github.com/SAA-SDT/EAD-Revision Library of Congress EAD List and EAD Roundtable List

29. MORE INFORMATION (VIA POWERPOINT!) SAA Webinar “EAD3: What’s new?” October 23, 2014 http://www2.archivists.org/ DC 2014: Fonds and Bonds: Archival Tools, Metadata, Identity October 8, 2014, The Harry Ransom Center, UT Austin http://dcevents.dublincore.org/IntConf/index/pages/view/2014-archives

30. MORE INFORMATION (VIA ME!) Mike Rush michael.rush@yale.edu @mike_rush