1. EAD REVISION PROGRESS REPORT EAD Roundtable, SAA 2012, 2012-08-08

2. THE LONG AND WINDING ROAD

3. TIMELINE TO DATE Comments 2010-10 to 2011- 02 Funding Spring 2011 Revision Forum SAA 2011 Share Essential Documentation Winter 2012 TS-EAD Working Meeting March 2012 Conference calls Spring/Summer 2012

4. WITH A LITTLE HELP FROM MY FRIENDS

5. SUPPORT  Gladys Krieble Delmas Foundation  National Endowment for the Humanities  Nationaal Archief of the Netherlands  Beinecke Rare Book and Manuscript Library, Yale University

6. GET BACK

7. POINTS OF EMPHASIS  Achieving greater conceptual and semantic consistency in the use of EAD.  Exploring mechanisms whereby EAD-encoded information might more seamlessly and effectively connect with, exchange, or incorporate data maintained according to other protocols.

8. POINTS OF EMPHASIS  Improving the functionality of EAD for representing descriptive information created in international and particularly in multilingual environments.  Being mindful that a new version will affect current users.

9. DRIVE MY CAR

10. COMMUNITY COMMENTS  Non-Descriptive  Schema and documentation  General nature and purpose  Relationships to related resources and entities  EAD Header

11. COMMUNITY COMMENTS  Descriptive  Hierarchy elements  Wrapper elements  Controlled terms  Digital Archival Objects  Date encoding  Languages and scripts  Other elements

12. HELLO GOODBYE

13. GENERAL PROCEDURES  Elimination of elements deprecated in EAD2002   @langmaterial, @legalstatus, @otherlegalstatus  Deprecation as a blanket rule for new removals

14. 2011 QUALIFIERS Preliminary Provisional Contingent Possible Potential

15. 2012 QUALIFIERS Likely Highly Likely But nothing is final.

16. HELTER SKELTER

17. DISENTANGLE DESCRIPTIVE ELEMENTS  Remove from  Remove from [and promote it to a sibling]  Remove from  Eliminate recursion  bioghist/bioghist  controlaccess/controlaccess  Provide alternative using

18. REDUCE SEMANTIC OVERLOAD   8 distinct uses in EAD: or [in sibling Within siblings [as a block element] Recursively within Within block elements like [as mixed content]

19. UPDATE ACCESS TERMS  Split mixed content and block uses of access term elements into separate elements  Separate semantics of the following: Includes correspondence from John Lennon. Lennon, John.

20. UPDATE ACCESS TERMS  Enable  Lennon, John, 1940-1980

21. ALIGN WITH XHTML  Minor tweaks to  Remove,, and from within  Limit to a block element, add for inline use.

22. SIMPLIFY LINKS  Consolidate,,, and to just  Remove linking attributes from assorted elements, e.g.  Deprecate extended links   Remove XLINK namespace, but implement linking attributes isomorphic with XLINK

23. SUPPORT MULTIPLE LANGUAGES  Add language code and script code attributes to each non-empty element

24. REDUCE MIXED CONTENT  Reduce mixed content by more carefully considering what elements are appropriate within a given element  Examples:  Limit available children of to and  Limit available children of to,, and

25. COME TOGETHER

26. RECONCILIATION WITH EAC-CPF  Replace with  Keeping but replacing the rest  Add at all levels *  Improve data model for dates *  Improve * * Pending discussion

27. ELEANOR RIGBY

28. DEPRECATED ELEMENTS  ,,   +   +  * 

29. SHE CAME IN THROUGH THE BATHROOM WINDOW

30. ADDITIONS  Structured   container/@containerId   unittitle/@normal 

31. STRUCTURED PHYSDESC  will remain  Unstructured and textual  Provides migration path  [provisional name] will be added  Fully encoded  Machine actionable

32. STRUCTURED PHYSDESC   @physdesctype carrier space [space occupied] matttype [material type]  Specified Materials  Physical Type  Physical Details

33. STRUCTURED PHYSDESC Diaries 52 volumes 25 cm.

34. STRUCTURED PHYSDESC Collection 39 linear feet

35. STRUCTURED PHYSDESC 27 architectural drawings blueprints 28 x 36 inches

36. FORMS AVAILABLE Photograph 1

37. CONTAINER ID 1 represents the same container as 1

38. CONTAINER ID 1 represents a different container from 1

39. DID NOTE   Contain PCDATA, mixed content elements (,, etc.)  Will not contain,, Mean Mr. Mustard sleeps in the park.

40. ADDITIONS  Structured   container/@containerId   unittitle/@normal 

41. LET IT BE

42. REJECTED PROPOSALS  Eliminate  Eliminate numbered components  Make a wrapper tag for components alone  Make @level required for all components

43. I WANT TO HOLD YOUR HAND

44. RELATED TOOLS  Migration stylesheet(s)  External validation tools to  Validate ISO code lists, etc.  Establishing subset profiles  Encoding manipulation tools  Stylesheet to change between numbered and unnumbered components

45. MAXWELL’S SILVER HAMMER

46. TESTING AND COMMENTS Github Testing Comments Review Changes

47. SDT GITHUB REPOSITORY http://github.com/SAA-SDT/EAD-Revision

48. REVISED SCHEMA  Currently pre-Alpha  Hacked version of existing schema  Comprehensive re-write pending  http://github.com/SAA-SDT/EAD- Revision/blob/master/ead_revised.rng

49. MIGRATION STYLESHEET  Draft conversion of existing EAD 2002 instances to new EAD  Intended to be developed alonside schema, but lagging behind  http://github.com/SAA-SDT/EAD- Revision/blob/master/ead2002toEADx.xsl

50. ISSUE TRACKER  Three tags for issues  “Bugs”  (TS-EAD) “Feature Requests”  “Comments”  http://github.com/SAA-SDT/EAD- Revision/issues

51. TOMORROW NEVER KNOWS

52. REMAINING TIMELINE Progress Report 2012 EAD Roundtable Alpha Schema Release Fall 2012 Comments begin Schema Development Team Meeting October 2012 Beta Schema Release 15 January 2013 Final comments begin Final comment period ends 15 February 2013

53. REMAINING TIMELINE Tag Library Editorial Meeting March 2013 Finalize schema requirements and tag library 1 April 2013 Schema and tag library release 1 July 2013

54. YOU KNOW MY NAME (LOOK UP THE NUMBER)

55. FURTHER INFORMATION  SAA Standards Portal  http://www2.archivists.org/standards  Schema Development Team Github Repository  http://github.com/SAA-SDT/EAD-Revision  Library of Congress EAD List  EAD Roundtable List

56. CONTACT Michael Rush michael.rush@yale.edu twitter.com/mike_rush