EAD Revision Technical Considerations Terry Catapano EAD Roundtable

EAD Revision: Technical Considerations Terry Catapano EAD Roundtable Meeting 2011 -08 -24

Overview Schema Language Choices EAD as Vocabulary/Ontology EAD Subset Tools

Schema: Languages Options DTD W 3 C XML Schema Relax. NG Maintenance? Distribution?

Schema Languages: Features XML Documentation and “appinfo” Strong Datatyping Namespace Support External Internal Allow Any? Allow Some? (Xlink, EAC? , MODS? ) Maintenance/preservation implications Parsing, Validation, Processing

Vocabularies/Abstract Model Vocabulary for describing: Archival descriptions (records/documents) [Tag Library] Archival components (things) Establish URIs Formal Expression (SKOS? , RDFS? , OWL? ) Implemented in schemata, xml instances TEI, NISO JATS, Dublin Core, Darwin. Core. . .

Vocabularies, con't Enumerated values c/@level Complement, Incorporate others LOCAH Aaron Rubenstein/ http: //purl. org/archival/vocab/arch Dublin Core, others. . . ?

SKOS Straw Man <rdf: RDF xmlns: ead="http: //example. info/ead/vocabulary/" xmlns: rdf="http: //www. w 3. org/1999/02/22 -rdf-syntax-ns#" xmlns: skos="http: //www. w 3. org/2004/02/skos/core#"> <skos: Concept rdf: about="http: //www. example. info/ead/vocabulary/c/"> <skos: pref. Label>Component</skos: pref. Label> <skos: definition>A subordinate part of [described archival] materials. . . An intellectually logical section of. . . described [archival] materials. . . A stage within a hierarchical description of [archival materials]. </skos: definition> </skos: Concept> <skos: Concept rdf: about="http: //www. example. info/ead/vocabulary/unittitle/"> <skos: pref. Label>Unittitle</skos: pref. Label> <skos: definition>The name, either formal or supplied, of described [archival] materials. May consist of a word, phrase, character, or group of characters. . . The < unittitle> is comparable to ISAD(G) element 3. 1. 2 and MARC field 245</skos: definition> </skos: Concept> </rdf: RDF>

Profiling/Subsetting Base Schema + Subset(s) Endorsed/Official? Facilitate User created? Similar to approaches of other tagsets (TEI; JATS) Schematron – – Rules-based Validation XPATH Based

Schematron: Example <sch: pattern name="Co-Occurrence Constraints"> <sch: rule context="*[@level ='otherlevel']"> <sch: assert test="string-length(@otherlevel) > 1"> If the value of a level attribute is "otherlevel', then the otherlevel attribute must be used </sch: assert> </sch: rule> </sch: pattern> <sch: pattern name="Elements Removed"> <sch: rule context="ead: chronlist"> <sch: report test=". ">ERROR: <sch: name/> ELEMENT NOT ALLOWED</sch: report> </sch: rule> </sch: pattern> <sch: pattern name="No Mixed Content"> <sch: rule context="*"> <sch: report test="child: : ead: * and text()[string-length(normalize-space(. )) != 0]" >ERROR: Mixed content is not allowed</sch: report> </sch: rule> </sch: pattern>

Tools Migration – – DTD to Schema 2002 to EAD X Validation (e. g. , Schematron) Conversions? – – “EAD Tidy” EAD to RDF Pipelines (XProc) Packaging?