EAD3 Progress Report 2014-08-13

340 views
247 views

Published on

Progress report on the revision of Encoded Archival Description. EAD3 should be ready by Winter 2015.

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
340
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

EAD3 Progress Report 2014-08-13

  1. 1. EAD Roundtable, SAA 2014, 2014-08-13 Mike Rush, TS-EAD Co-Chair EAD3 PROGRESS REPORT
  2. 2. 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
  3. 3. 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
  4. 4. 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
  5. 5. BETA RELEASE
  6. 6. 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=ead
  7. 7. BETA / GAMMA FEEDBACK
  8. 8. BETA / GAMMA FEEDBACK • Reinstate various elements • Tweak mixed content options • Modify enuerated value lists in <control> • Address migration concerns for specific elements and attributes • Modifications to <physdescstructured> • Additional changes to support multi-language description • Bugs
  9. 9. POST BETA / GAMMA CHANGES
  10. 10. RELATIONS COMPROMISE • <relations> • Included in core EAD3 schema, but… • Considered an “experimental” element • What is an “experimental” element? • TS-EAD could not reach consensus on <relations> • Concerns about duplication of <controlaccess>, complexity of model, etc. • Need to see if and how it will be used • Should you use <relations> if it’s experimental? • YES!
  11. 11. RELATIONS COMPROMISE • Tweaks to <controlaccess> 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 <part>, which will allow for post- coordinated subject headings
  12. 12. DAOGRP / DAOSET • Strong call to restore <daogrp> after Beta release • Strong desire to eliminate extended links • Solution: Create <daoset> • Wrapper element for two or more <dao>, with optional <descriptivenote> • Lacks full extended link functionality, but will suffice for most identified uses of <daogrp>
  13. 13. DAO TWEAKS • Replaced <daodesc> with <descriptivenote> to remove all block children except <p> • Added @coverage as optional attribute to <dao> • Possible values: whole | part • Indicates if <dao> 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 <did> children
  14. 14. <PHYSDESCSTRUCTURED> TWEAKS • Added @approximate to <quantity> • Possible values: yes | no • The order of <dimensions> and <physfacet> is no longer enforced by the schema • <genreform> (and other access terms) restored to <physfacet> • Removed @unit from <physfacet> • Removed @rules from <physdesc> and <physdescstructured>
  15. 15. <GEOGRAPHICCOORDINATES> • New child of <geogname> • 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
  16. 16. SMALL CHANGES • Added <foreign> for inline tagging of language and script. • Added to all mixed content nodes. • Tweaked various mixed content models • <title> restored to <abstract> • Made elements repeatable to support multi-language description • control/maintenanceagency/agencyname • control/maintenancehistsory/maintenanceevent/eventdescription • control/sources/source/sourceentry
  17. 17. SMALL CHANGES • Moved ennumerated element values to @value attribute • <agenttype> • <eventtype> • <maintenancestatus> • <publicationstatus> • Added “published” as a value for <publicationstatus> • Added “deletedmerged” as a value for <maintenancestatus>
  18. 18. CHANGES NOT MADE • <descgrp> not restored • <unitdate> not restored as a child of <unittitle> • <quantity> remains a required child of <physdescstructured> • <physdescstructured> not modified for born digital extents • <genreform> not restored to <physdesc> • <author> not given the same content model as <persname> • <bibref> not added as a child of <source>
  19. 19. DELIVERABLES
  20. 20. DELIVERABLES • 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
  21. 21. 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
  22. 22. GOVERNANCE
  23. 23. GOVERNANCE • 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
  24. 24. HOW CAN YOU HELP?
  25. 25. HOW CAN YOU HELP? • Encode some EAD3 examples! • Needed for testing the schemas and making sure we didn’t miss anything
  26. 26. MORE INFORMATION
  27. 27. 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
  28. 28. 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
  29. 29. MORE INFORMATION (VIA ME!) Mike Rush michael.rush@yale.edu @mike_rush

×