Your browser doesn't support the features required by impress.mod.js, so you are presented with a simplified version of this presentation.

For the best experience please use the latest Chrome, Safari or Firefox browser.

2019-09-03 | Berlin Themenkonferenz Epigraphik
Perspektiven der Epigraphik

EpiDoc

Epigraphische Dokumente in TEI XML

Thomas Kollatz, Akademie Mainz @kol_t Twitter digicademy | CC-BY 4.0

Was ist EpiDoc

EpiDoc TEI XML
Epigraphic Documents in TEI XML
XML text markup for ancient documents
EpiDoc is an international, collaborative effort that provides guidelines and tools for encoding scholarly and educational editions of ancient documents. It uses a subset of the Text Encoding Initiative's standard for the representation of texts in digital form, which focuses on the history and materiality of the texts. EpiDoc was developed for the publication of digital editions of ancient inscriptions, but its domain has expanded to include the publication of papyri and manuscripts, including those beyond the Greco-Roman world.

https://sourceforge.net/p/epidoc/wiki/About/

Entwicklungsgeschichte

Quelle: http://www.stoa.org/epidoc/

  • Subset der TEI
  • seit 1999 kollaborativ (und in transkontinentaler Zusammenarbeit) entwickelt
  • im Dezember 2017 Release von Schema und Guidelines Version 9.0
  • Mittlerweile wird das TEI-Subset EpiDoc von zahlreichen (nicht nur) epigraphischen  Projekten verwendet
  • mehr zur Geschichte https://sourceforge.net/p/epidoc/wiki/About/

Digitale Epigraphik

1960er John Jory: University of Western Australia in Perth: 40.000 Texte (CIL VI) KWIC
1968 David Packard entwickelt Markup-System Beta Code
1987ff Packard Humanities Institute PHI CDs
1989 Lausanne: Internationales Kolloquium zu epigraphy and information technology
u.a. Initiativen aus Bordeaux, Graz, Freiburg, Heidelberg, Rom, North America, at Ithaca (New Yorþ and Columbus (Ohio), Palo Alto		 Actes du Colloque Épigraphie et Informatique
1995 Tom Elliot et al. University of North Carolina: maschinenlesbares Leidener Klammersystem XML-based
1997ff AIEGL Kongress Rom: Electronic Archive(s) of Greek and Latin Epigraphy – Förderation von drei epigraphischen Datenbanken: Heidelberg 1986ff, Rome 2004ff, Bari 2006ff EAGLE
2001ff EpiDoc 1.0-9.0

siehe: Bodel 2012: Latin Epigraphy and the IT Revolution; Roueché 2015: Byzantine Epigraphy for the 21th century;

Struktur

Metadaten – Bilddaten – Textdaten

<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:space="preserve" xml:lang="en">
   <teiHeader>
     <!-- Metadaten -->
   </teiHeader>

   <facsimile>
      <!-- Informationen zu Bilddaten-->
   </facsimile>

   <text>
       <!-- Textdaten: Edition, Kommentar, Übersetzung, etc. -->
   </text>
</TEI>

EpiDoc offers a template file ex-epidoctemplate.xml
see EpiDoc Guidelines: Structure Of An EpiDoc Edition

Edition nach Leiden 2.0

Letters ambiguous outside of their context
<unclear>אβc</unclear>
letters corrected by the editor
<choice>
    <corr>εγ</corr>
    <sic>γε</sic>
</choice>ο
lacuna, approximate extend, omitted letters added by editor
L<gap agent="damage" reason="lost"
unit="character" quantity="2"/>
<supplied reason="lost">üc</supplied>ke

cheatsheet

Implizites explizit machen

Thus, for the traditionally trained epigrapher (classicist, humanist) an EpiDoc or a more general DH training leaves the sense of a distinct change of methodology. This change, however, is usually perceived as an improvement, the ‘scientific’ methodology adding more detail and nuances to the publication, though sometimes it can leave an uncomfortable feeling of not being allowed any fuzziness.

Bodard and Stoyanova 2016

Metadaten: Personen und Daten 

<person xml:id="ffb-80-1" sex="1">
 <persName ref="http://d-nb.info/gnd/11879132X">Meir Rothschild ben Anschel Rothschild</persName>
 <death when="1812-09-19" calendar="#Jewish">13. Tischri 5573<death>
</person>

Metadaten: Lage, Standort

<history>
 <origin>
  <origDate>
   <date notBefore="1812-09-19">1812-09-19</date>
  </origDate>
  <origPlace>
   <country type="ISO_3166" key="XA-DE-HE">Germany
     <region>Hesse</region>
   </country>
   <settlement type="city" key="tgn:7005293" ref="http://vocab.getty.edu/tgn/7005293">
     Frankfurt am Main, Battonnstraße
    <geogName ref="http://d-nb.info/gnd/4331943-9">Jüdischer Friedhof
     <geo decls="#WGS">50.1119 8.689675</geo>
    </geogName>
   </settlement>
  </origPlace>
 </origin>
</history>

Normdaten, Thesauri, Ontologien

EpiDoc Community

https://sourceforge.net/p/epidoc/wiki/Home/

EpiDoc Projekte

http://www.stoa.org/epidoc/gl/latest/app-bibliography.html

EPIDAT

Forschungsplattform jüdische Grabsteinepigraphik

2002 initiiert; seit 2006 online

historische Friedhöfe 202
Grabmale 35,859
Bilddigitalisate 71,368
Personendaten 40,301
Datierungen 24,948
Länder 4

start page of beta version (2019-06)

headstones as source for cultural and religious history

Mainz – Gedenkfriedhof: mz1-2203
foto: LDA Mainz

‎‏זה קבר של הרב ר׳ מאיר בר אברהם הכהן הזקן הנהרג על יחוד השם במ״א לפרט כ״ז בסיון ביום שנשרף בית הכנסת ונקרעו סיפרי תורה מנוחתו כבוד‏‎
place of burial
Mainz
date of death | date of event
1281-06-15 | 27. Sivan 5041
name
Meir b. Awraham HaCohen
event
destruction of the synagogue and the torascrolls:
ביום שנשרף בית הכנסת ונקרעו סיפרי תורה
concept
הנהרג על יחוד השם
dislocation
headstone was found by workers on June 5, 1899 in the cellar of the inn Zur Stadt Mainz in the street Große Bleiche

headstones as source for history of literature

‎‏גם חסידה בשמים‏‎
‎‏פה שוכבת הדרת הנשים‏‎
‎‏אף גם עדים וצבי תפארתם‏‎
‎‏גמלה חסד עם הרשים‏‎
‎‏לזמנה היתה כתר מכתם‏‎
‎‏בת פו״מ כהר״ר יוסף‏‎
‎‏פופרט אשת כ״ה משה‏‎
‎‏אפינהיי׳ הגובה באלטונא‏‎
‎‏נפטר׳ ונקבר׳ יום ב׳ ך״ז טבת‏‎
‎‏שנת כצפור נודדת מקנה‏‎
‎‏תנצב״ה ‏‎
place of burial
Hamburg
name(s)
Vogel (in acrostic)
father Josef Popert
husband Moshe Oppenheim
task
הגובה באלטונא‏‎ charity administrator
date_of_death
03.01.1791 | 27. Tewet 5551
symbol
bird
style
rhyme, meter, acrostic, chronostic, play on words
id
hha-1678





Forschungsdaten

fair principle

 Findable Accesible Interoperable Re-usable

Lizenz

 online veröffentlicht unter offener Creative Commons Licence

Standardformat

 liegen in EpiDoc: TEI XML for Epigraphic Documents maschinenlesbar, system-unabhängig, programm-unabhängig – strukturierter Zugang

Interoperabilität

 referenzieren Normdaten, kontrollierte Vokabularien, Thesauri

Schnittstellen

 werden über eine maschinenlesbare Schnittstelle bereitgestellt

Nachnutzung – Kulturaktion

/TEI/teiHeader/fileDesc/titleStmt/title
/TEI/facsimile/graphic[1]
//*[@type='edition']
//*[@type='translation']

Woher stammt die Idee zu POETIC RELIEF?

Im Rahmen des ersten deutschen Kultur-Hackathons Coding da Vinci , wo das Steinheim-Institut als teilnehmende Kulturinstitution und Partner fungierte, wurde der epidat-Datensatz vorgestellt und daraus die Website entwickelt, um die Grabinschriften neu darzustellen.

http://www.poeticrelief.org/faq

Nachnutzung – Forschungsdaten

DHd2016 Leipzig workshop mit Forschungsdaten des Steinheim-Institut für Deutsch-Jüdische Geschichte und der Akademie der Wissenschaften und Literatur | Mainz

Kollatz-Kuczera-Schrade 2016

<particDesc>
 <listPerson>
  <person xml:id="aha-13-1" sex="1">
   <persName>Elieser ben Josef Hakohen</persName>
   <death when="1879-12-08"/>
  </person>
  <person xml:id="aha-13-2" sex="1">
   <persName>Jehuda ben Josef Hakohen</persName>
   <death when="1879-12-09"/>
  </person>
  <listRelation>
   <relation name="parent" active="#aha-21-1 #aha-48-1" passive="#aha-13-1"/>
   <relation name="sibling" mutual="#aha-50-1 #aha-13-1"/>
   <relation name="sibling" mutual="#aha-13-1 #aha-13-2"/>
  </listRelation>
 </listPerson>
</particDesc>

hha-3361-teip5

Nachnutzung – Genealogie

Torsten Schrade

Inspiration for this example drawn from a discussion about visualizing XML based relationships on the TEI mailinglist. Credits and thanks to Thomas Kollatz for the idea. The RDF extraction is modelled on FOAF to represent persons, BIO to represent dates of death and REL to build family relations between persons. Visualization is done using the Sgvizler library and it's Dracula Graph implementation.

about XTripels

Nachnutzung – RDF-Lifting

d1e255 A1 crm:E55_Type: "Mann" "Mann" A1->"Mann" crm:P3_has_note A3 crm:E21_Person: A4 crm:E55_Type: A3->A4 crm:P2_has_type A5 crm:E82_Actor_Appellation: A3->A5 crm:P131_is_identified_by A4->"Mann" crm:P3_has_note "Jehuda" "Jehuda" A5->"Jehuda" crm:P3_has_note http://www.steinheim-institut.de/cgi-bin/epidat?id=aha-13 crm:E19_Physical_Object: http://www.steinheim-institut.de/cgi-bin/epidat?id=aha-13 http://www.steinheim-institut.de/cgi-bin/epidat?id=aha-13->A3 crm:P131i_identifies "Breite, hochrechteckige Sandsteinstele mit geradem\nAbschluss. Das ver [...]" "Breite, hochrechteckige Sandsteinstele mit geradem Abschluss. Das ver [...]" http://www.steinheim-institut.de/cgi-bin/epidat?id=aha-13->"Breite, hochrechteckige Sandsteinstele mit geradem\nAbschluss. Das ver [...]" crm:P3_has_note A0 crm:E21_Person: http://www.steinheim-institut.de/cgi-bin/epidat?id=aha-13->A0 crm:P131i_identifies A0->A1 crm:P2_has_type A2 crm:E82_Actor_Appellation: A0->A2 crm:P131_is_identified_by "Elieser ben Josef Hakohen" "Elieser ben Josef Hakohen" A2->"Elieser ben Josef Hakohen" crm:P3_has_note
demo: http://xtriples.spatialhumanities.de | code: https://github.com/spatialhumanities/xtriples
Präsentation: Torsten Schrade (Digitale Akademie Mainz): CIDOC-CRM Modellierung epigraphischer Fachdaten mit dem XTriples Webservice - Werkstattbericht aus dem DARIAH UseCase 6.1 (Steinheim-Institut & ADWLM)

Jüdischer Friedhof Mainz im 3D Model

Workshop: IBR/RiR

Relationen im Raum

Mustererkennung

einzoomen auszoomen
Einzelobjekt Ensemble
Object Kontext
Mustererkennung Einheiten: Sektionen | Felder | Reihen

RiR (BMBF-Projekt 2012-2015) Template: Erstellen einer SVG-Planskizze in Inkscape

Form und Gestalt

Wandel funeraler Traditionen vollzieht sich nur sehr langsam. Veränderung manifestiert sich nicht nur in der textlichen Überlieferung. Kultureller Wandel spiegelt sich auch in der Verwendung (neuer) Formen wieder. Text und Form entwickeln sich nicht synchron.
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin/origDate/date/@notBefore

Genderdistribution

DIO 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 EPI 0 50 100 150 200 250 300 350 400 450 500 550 0 1 2 9

bar chart Legende

1 male
2 female
0 unknown
9 not defined
Configuration

Visualisierung http://app.rawgraphs.io

Sharing Data

IIP Inscriptions of Israel | Palestine epidat Research Platform for Jewish Epigraphy DIO Deutsche Inschriften Online
online
time 500 BCE - 640 CE midth 11th - 20th century 500-1650 CE
space Israel Palestine Germany Netherlands Czechia Lithuania Germany Austria South Tyrol
Genre Different Funeral Inscriptions Different
Format EpiDoc: TEI XML for Epigraphic Documents
Example QUAMR0001 ffb-80 34-561

target="_blank"PEACE Portal and DARIAH-DE

Nachwuchsförderung

Epigraphik – digital und traditionell

The focus of such a class is not so much an intensive EpiDoc training, but rather demonstrating that structured markup is nothing more than structured thinking about data. The structure of an XML document reflects the structure of an epigraphic edition. Following the strict hierarchy of XML forces one to better organise one’s thoughts, approach towards, and work on an epigraphic document. We have found that it is highly beneficial to be able to process and produce information in a well structured and clearer way, even if the students do not show interest in further DH training.

Bodard and Stoyanova 2016

That the principles of digital editing in EpiDoc share this bedrock foundation of technology with the anticipated Semantic Web gives reason to believe that the future of digital epigraphy will not be left in the past.

Bodel 2015:293

F I N I S

סוף דבר הכל נשמע

Software und Literature

Literature & Software

Digital Epigraphy

EpiDoc and Digital Epigraphy

Recent Presentations

Recent Presentations

Software