1 / 10

Technical Considerations for EAD Schema Language and Tools

This overview discusses schema language choices, EAD as vocabulary/ontology, EAD subset, and tools for schema languages, including DTD, W3C XML Schema, RelaxNG. It also explores maintenance and distribution of schema, vocabulary for describing archival descriptions, vocabularies for Archival components, and implementation in different schemata and XML instances.

meller
Download Presentation

Technical Considerations for EAD Schema Language and Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Overview • Schema Language Choices • EAD as Vocabulary/Ontology • EAD Subset • Tools

  3. Schema: Languages • Options • DTD • W3C XML Schema • RelaxNG • Maintenance? • Distribution?

  4. 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

  5. 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, DarwinCore...

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

  7. SKOS Straw Man <rdf:RDFxmlns:ead="http://example.info/ead/vocabulary/"xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"xmlns:skos="http://www.w3.org/2004/02/skos/core#"><skos:Concept rdf:about="http://www.example.info/ead/vocabulary/c/"><skos:prefLabel>Component</skos:prefLabel><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:prefLabel>Unittitle</skos:prefLabel><skos:definition>The name, either formal or supplied, of described [archival] materials. May consist of a word, phrase, character, or group of characters...The &lt;unittitle&gt; is comparable to ISAD(G) element 3.1.2 and MARC field 245</skos:definition></skos:Concept></rdf:RDF>

  8. 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

  9. Schematron: Example <sch:pattern name="Co-Occurrence Constraints"><sch:rule context="*[@level ='otherlevel']"><sch:assert test="string-length(@otherlevel) &gt; 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>

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

More Related