1. EpiDoc History, goals, tools
Dr Gabriel Bodard, Simona Stoyanova
Institute of Classical Studies, University of London
Elli Mylonas
Brown University

2. EAGLE Commission

3. EAGLE
1999 Silvio Panciera, AIEGL Commission for Epigraphy and Information Technology:
È importante che siano utilizzati programmi che consentano l'esportazione dei documenti in “Document Type Definition (DTD) format”.

4. AWMC

5. AWMC
2000 Tom Elliott, Hugh Cayless, Amy Hawkins, Ancient World Mapping Center (UNC-CH)
EpiDoc Guidelines, version 1

6. History of EpiDoc: prior art
EpiDoc recommended use of TEI
SGML/XML for literary/linguistic corpora since 1988
Based on Leiden distinctions (1931)
EAGLE / Krummrey-Panciera 1980/Panciera 1991
EAGLE fields
EDR / EDH / PETRAE etc.
Expanded for neighbouring disciplines
Papyrology
Other ancient inscribed objects (seals, coins…)
Other scripts (Mycenaean, Cuneiform, Mayan…)

7. Text Encoding Initiative (TEI)
An XML language designed for the encoding of literary and historical texts, used and supported by a large community of humanities researchers
EpiDoc is a “customization” of TEI, therefore is able to participate and benefit from the larger community

8. ALA 2004

9. IAph 2007

14. Papyri.info

15. EAGLE Europeana Network

16. EAGLE Europeana Network
Migrate more epigraphic datasets
Bi-directional conversion
Community involvement
Wikimedia/Wikidata
Translations
Image identification
Community outreach/contribution
Vocabularies — linked open data

18. Assumptions Epigraphy and/or papyrology Leiden Conventions
Greek and/or Latin
Or other traditions
No tech background required

19. This week you will learn:
XML basics
Well-formedness
Validation
Use of XML editor
How we map TEI to epigraphic edition
How we map TEI to Leiden Conventions
Basic use of EFES publication platform
EpiDoc Guidelines & community resources

20. EpiDoc Tools Guidelines Example XSLT Converters
(CHETC, SoSOL, crosswalks, Transcoder)
EAGLE Storytelling app
Search and browse environments
Papyri.info / IDEs
Kiln / EFES
Editing environments
SoSOL / Perseids / Tiglio
EAGLE (WikiData / WikiMedia Commons)

22. EpiDoc Conformance Epigraphic Texts: Leiden Conformance
All sigla and epigraphic distinctions expressed in XML
at least in the epigraphic text 
Adherence to EpiDoc Guidelines
Epigraphic Metadata: EAGLE Conformance
All metadata required by relevant database (EDR, EDH, EDB, etc.) tagged according to EpiDoc recommendations

23. EpiDoc vs Epigraphy Teaching EpiDoc Teaching epigraphy
Assume epigraphic/classical knowledge
Assume Greek and Latin
Introduce technology
Introduce epigraphic practice
Give reference materials (Guidelines) and customized summary of reference (cheatsheet)
Give reference materials (handbooks) and customized summary of reference (Leiden conventions)
Give lots of exercises and practice

24. Teaching Materials Slideshows, examples, tutorials Pool of trainers
All multi-authored, CC-BY licensed
Pool of trainers
(UK, France, Germany, Italy, USA, Bulgaria, Norway, + + +)
Project-funded
Mini-workshops at conferences
London April workshop at ICS

25. Encoding made me an epigrapher!
Pay attention to
What you're saying
What you mean
What you know/guess/extrapolate
What you want to index/encode
Publish scientifically
Make data and methodology available
Images
Apparatus criticus
Links to comparanda and secondary sources

26. Encoding made me an epigrapher!
Take responsibility for
Readings
Measurements
Publication
Give credit for
Contributions
Encoding

27. Future plans EFES — EpiDoc Front-End Services Advanced training IDEs
Integrated editing environments
Shared bibliographies
Localised guidelines

28. Text encoding Document analysis: Metadata:
Identify the structure of your text (you might draw a tree diagram to help visualise and plan)
= structural markup
Think about what information you want to be able to represent or search for within the document
= semantic markup
Metadata:
Who is responsible for creating the document?
Where did the document come from and where is it now?
Is there any bibliographical information related to the document?
How has it been digitised (e.g. converted from another format, or ‘born digital’)?

29. Markup Renditional markup captures appearance:
<i>mens sana in corpore sano</i>
<i>The Roman Stonecutter</i>
This could <i>just</i> belong to…
Semantic markup captures meanings:
<foreign>mens sana in corpore sano</foreign>
<title>The Roman Stonecutter</title>
This could <emph>just</emph> belong to…

30. Structure of an XML document

31. XML syntax Nesting of elements
<b><i>some text</i></b>
Overlapping
<b><i>some text</b></i>

32. XML syntax Elements may have attributes:
<element attribute=“value”>content</element>
e. g.:
<city name="Montevideo">capital of Uruguay</city>
<coord type=“latitude”>-7.175</coord>
Comments are useful for documenting
<!-- comment here -->

33. Leiden conventions and EpiDoc
Leiden is also a markup language:
Mapping Leiden to EpiDoc:

34. Inscription in EpiDoc IOSPE, I.18
Tyras, Dedication to Egyptian Gods, II-I centiry BCE

35. Inscription in EpiDoc