Difference between revisions of "EpiDoc"
m (→Agenda: "desire" -> "concrete plan") |
(→Links: link to GLs) |
||
Line 30: | Line 30: | ||
== Links == | == Links == | ||
+ | |||
+ | *[http://www.stoa.org/epidoc/gl/5/ EpiDoc Guidelines] at Stoa | ||
*[http://epidoc.sourceforge.net/ SourceForge project page] | *[http://epidoc.sourceforge.net/ SourceForge project page] | ||
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources] | *[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources] |
Revision as of 15:38, 8 September 2008
EpiDoc represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of epigraphic documents.
Contents
History
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).
EpiDoc Activities and focus
Text Transcription
The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the Leiden Conventions, especially (although not exclusively) as articulated by Krummrey-Panciera.
In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.
Epigraphic and papyrological metadata crosswalking
The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the EAGLE and HGV databases.
Tools
The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:
- EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [1])
- Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [2])
- CHETC (python tool for converting conventional Leiden to EpiDoc XML [3])
- Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [4])
Agenda
Concerete plan to move into conformant TEI P5 in Fall 2008 (some modifications to P5 already proposed).