Embed Size (px)
Citation preview
How to standardize XML-encoding of medieval
and early modern charters and instruments?
TEI workshop “Putting the TEI to the test”
Berlin April 25th, 2007
Topics
• state of activities in medieval and early modern charters projects
• some examples of differences between CEI and TEI
state of activities
• 300 years of diplomatics
• 30 years of digital diplomatics
• 3 years of Charters Encoding Initiative
Charters on the web
• currently ca. 100 projects
• mainly in Europe
• ranging between – 94 (Critical Edition of the Charters of the
Arnulfinger)
and– 20,000+ (MOnasteriuM)
charters
Different approaches …
• archival description, finding aids, registers
• calendar / regesta
• retrospective digitization of printed charter editions
• ongoing work on new digital editions
=> different requirements
… but a common object
• „The Charter“• => cross-project object identification
– (charter0 in archive =) charter1 in medieval cartulair = charter2 in 17th cent. print = charter3 in a calendar = charter4 in finding aid = charter5 in a modern edition = charter6 as digital facsimile
• why not use TEI? – as all projects produce “text“ …
considerations
• some projects are older than the TEI and thus have other approaches (DEEDS)
• some are not aware of markup (using relational databases, pure html, pdf, etc.)
• some only want relatively flat encoding „quasi standard“ TEI sufficient (dMGH)
• some believe the TEI tag set meets their needs (EdC)• some consider the TEI inappropriate and develop their
own schema (CDLM)• many would like to use an extended TEI tag set (MOM,
CEI)
„Pur nel rispetto degli standard disponibili e riconosciuti (XML lo è), è parso utile rinunciare al modello TEI, e dar vita a un’autonoma e agile struttura di codifica dei dati testuali. Nella consapevolezza […] che il prodotto (il ‘modello’) andrà progressivamente perfezionato […] mi è capitato in altre circostanze di indicare nel Vocabulaire International de la Diplomatique lo strumento ideale per avviare una discussione e un confronto concreti all’interno della comunità dei diplomatisti, lo strumento da cui partire per fissare i requisiti di una Document Type Definition (DTD) da impiegare nell’edizione elettronica di testi documentari; che, in sostanza, sia per la comunità degli studiosi ed editori di fonti d’archivio medievali ciò che TEI è per filologi e letterati.”
Michele Ansani (http://cdlm.unipv.it/progetto/codifica-xml), Codice diplomatico della Lombardia medievale, Documentazione tecnica
CEI
• founded in 2004• diplomatists from Europe and North America• scholars, librarians, archivists, information
scientists• aims at making data exchange easier: standard?
controlled vocabulary? ontology? DTD/schema proposals?
• continuous meetings – mailing list ([email protected]) – experiments with the current version (editMOM, DS) that could be called CEI.0
Questions to the TEI
• possibilities for charter-specific elements?
• better encoding of material and visual aspects of charters?
• integration of the EAD-model?
What is a charter?
cei:authentication
• instruments/charters : legal value : authentication.
– tei:seal– cei:subscription– cei:signumManus / cei:monogram /
cei:notarialSign / cei:chrismon– cei:witness– cei:notary
Linguistic characteristics
of charters
Using TEI?
semantic encodings
• Like : tei:author, tei:publisher, tei:pubDate, tei:settlement …
• cei:issuer, cei:recipient, cei:addressee, cei:beneficiary, cei:witness, cei:notary …
• tei:seal/name=cei:sigillant, tei:seal/q=cei:legend
Typical structure of an „Urkundenbuch“ (charters edition)• number• charter header
– <cei:abstract>, <tei:creation>– <tei:textWitList>
• <cei:archIdentifier>, <cei:transmissionStatus>
– <tei:listBibl type=”facsimilia|prints|regesta|studies”>– <cei:diplomaticAnalysis>
• text with apparatuses
• charter (chDesc*, tenor*)
Archives
• EAD is dominant• LEADER as one attempt to bring EAD and TEI
together: – separate TEI transcription text linked to a standard
EAD description (http://leaders.sourceforge.net/)
• We would prefer:– make an archival description possible with TEI
• msDesc, fileDesc, idno … are good starting points
But …• msIdentifier: <settlement>Roma</settlement>
<institution>Biblioteca vaticana</institution> <repository>codices palatini latini</repository> <idno>1453</idno>
• EAD: <archdesc level="collection"> <did><repository>BayHStA</repository> </did><c><did>Hochstift Passau</did><desc><c><did>Urkunden</did><c level=“item”><did>35</did></c></c></desc></archDesc>
Archives (settlement, institution, respository)
Component (idno, content, desc)
Component (idno, content, desc)
Main differences between CEI and TEI
• CEI prefers explicit charter specific rather than generic TEI elements
• CEI adds some concepts to the TEI• CEI changes syntax and meaning of some
TEI elements slightly• CEI keeps nesting open=> CEI proposes encoding that is charter
specific and that is aware of the physical and visual charateristics of the charter.
But …
• It is our hope that the CEI will one day be a TEICharters-Module
• Thank you for your attention!
Georg Vogeler ([email protected])
Charters Encoding Initiative (http://www.cei.lmu.de)
