Your SlideShare is downloading. ×
EAD Revision Progress Report, SAA 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

EAD Revision Progress Report, SAA 2013

115
views

Published on

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
115
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. EAD Roundtable, SAA 2013, 2013-08-16 Mike Rush, TS-EAD Co-Chair
  • 2.       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. Comments Funding Revision Forum • 2010-10 to 2011-02 • Spring 2011 • SAA 2011 Schema Dev. Team Meeting Conference calls TS-EAD Working Meeting • October 2012 Alpha Release • February 2013 • Spring 2012 to Summer 2013 Tag Library Editorial Team Meeting • February 2013 • March 2012 Beta Release • 2 August 2013
  • 4. Beta comment period Schema and migration testing Finalize schema and tag library • 2August to 1 October 2013 • August to November 2013 • 1 October to 1 December 2013 Publish Submit to SAA Council for adoption Submit to Standards Committee • Winter 2014 • Winter 2013 • 1 December 2013
  • 5. EAD 2014 EAD 3D 3AD EAD III
  • 6. EAD3
  • 7.     Documentation Concern about migration Concern about updating existing tools Reconsider extent of changes  Changing of names  Alignment with EAC-CPF  Increase in number of elements   Feature requests Bugs
  • 8.  No camel case  All element and attribute names will continue to be all lower case  No name changes  Existing element names will not be changed, but new element names will have longer, more natural language forms  No <formsAvailable>  Had bundled <container> and <dao> in alpha.
  • 9.   Restored recursion in <did> sibling elements No split access elements  Alpha included <persName> and <persNameEntry>  Collapsed in the Beta to just <persname>   Moved <materialspec> back into the <did> Restored some elements deprecated in alpha     <fileplan> <abbr> + <expan> <dsc> <ptr>
  • 10. Preliminary Provisional Contingent Possible Potential
  • 11. Likely Highly Likely But nothing is final.
  • 12. Oobleck
  • 13. Oobleck A non-Newtonian fluid that will exhibit solid behaviors if enough stress is applied CC BY-NC-SA, Jean-Christophe, Flickr
  • 14. Still fluid, but starting to solidify (Stress has been applied)
  • 15.  Completely re-written schema  Relax NG  W3C  No DTD yet  Draft Tag Library  Element definitions  Attribute definitions
  • 16.       Remove <arrangement> from <scopecontent> Remove <acqinfo> from <custodhist> Remove <legalstatus> from <accessrestrict> [and promote it to a sibling] Remove <unitdate> from <unittitle> Limit <dao> to the <did> Limit <archref> and <bibref> to block contexts in appropriate elements
  • 17.  8 distinct uses for <note> in EAD 2002:         <notestmt> <titlepage> or <div> [in <frontmatter> <did> <did> sibling Within <did> siblings [as a block element] Recursively within <note> Within block elements like <p> [as mixed content] <namegrp>
  • 18.   Eliminate generic <note> Create context-appropriate note elements  <didnote>  <footnote>  <controlnote>  <descriptivenote>  Improve documentation for <odd>
  • 19.  Enable <part>  <persname> <part> Armstrong, Louis, </part> <part> 1901-1971</part> </persname>
  • 20.     Minor tweaks to <table> Minor tweaks to <list> Remove <blockquote>, <table>, and <chronlist> from within <p> Limit <blockquote> to a block element, add <quote> for inline use.
  • 21.    Consolidate <extref>, <extptr>, <ref>, and <ptr> to just <ref> and <ptr> Remove linking attributes from assorted elements, e.g. <title>, <archref> Deprecate extended links  <daogrp>  <linkgrp>  Remove XLINK namespace, but implement linking attributes isomorphic with XLINK
  • 22.  Add language code and script code attributes to all non-empty elements  <unittitle lang=“eng” script=“Latn”>Corresondence</unittitle>  <unittitle lang=“jpn” script=“Kana”> 対応 </unittitle>  Make sure appropriate elements can repeat to support multi-language description
  • 23.   Reduce mixed content by more carefully considering what elements are appropriate within a given element Balance that impulse against desire for reasonably simple schema design
  • 24.  3 Mixed Content models  Core : <abbr>, <emph>, <expan>, <lb/>, <ptr>, <ref>  Expanded Core : Core + access point elements, <date>, <footnote>, <num>, and <quote>  Expanded Core + <list>
  • 25.  Replace <eadheader> with <control>  Keeping <filedesc> but replacing the rest   Update <chronlist> Add <relations> at all levels *
  • 26.        <frontmatter> <eadgrp>, <archdescgrp>, <dscgrp> <descgrp> <runner> <daogrp> + <linkgrp> <note> Children of <bibref>  <bibseries>  <imprint>
  • 27.      <unitdatestructured> <physdescstructured> <origination> <repository> <langmaterial>
  • 28.  Choice of one of the following:  <datesingle>  <daterange> ▪ <todate> ▪ <fromdate>  <dateset> ▪ Some combination of <datesingle> and <daterange>  <unitdate> will remain as an unstructured option
  • 29.  Attributes:  @coverage = whole or part  @physdescstructuredtype = carrier, materialtype, or spaceoccupied  Elements      <quantity> [Required] <unittype> [Required] <dimensions> [Optional] <physfacet> [Optional] <descriptivenote> [Optional]
  • 30.  <parallelphysdescset>  Wrapper element for two or more <physdescstructured> elements that are parallel extent statements.
  • 31.   <physdesc> will remain as an unstructured option But:  No <extent>  No <dimensions>  No <physfacet>
  • 32.  One or more of the following:  <language>  <languageset> ▪ <language> ▪ <script>  <descriptivenote>
  • 33.  One or more of the following:  <corpname>  <famname>  <name>  <persname>  Optional  <address> [repository only]  <descriptivenote>
  • 34.    container/@containerid recordid/@instanceurl <representation>  <representation href="http://hdl.handle.net/10079/fa/beinecke.hay ward" role=“text/html">HTML version of finding aid</representation>
  • 35.  Revised Schema  Relax NG, W3C, and DTD versions  Tag Library       Preface + Explanation Element definitions Attribute definitions Crosswalks Examples Migration stylesheet
  • 36.  External validation tools (Schematron)  Validate ISO code lists, etc.  Establishing subset profiles  Encoding manipulation tools  Stylesheet to change between numbered and unnumbered components  Updated EAD Cookbook  XSLT style sheets for transforming EAD into HTML
  • 37.  SAA Standards Portal  http://www2.archivists.org/groups/technical- subcommittee-on-encoded-archival-descriptionead/encoded-archival-description-ead  TS-EAD Web Site  http://www2.archivists.org/groups/technical- subcommittee-on-encoded-archival-descriptionead/ead-revision  Schema Development Team Github Repository  http://github.com/SAA-SDT/EAD-Revision   Library of Congress EAD List EAD Roundtable List
  • 38. Mike Rush michael.rush@yale.edu @mike_rush