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.
XML is more interested in the meaning of data than in its presentation
Generalizing … we define markup, or (synonymously) encoding, as any means of making explicit an interpretation of a text.
<text>
<quote>To be or not to be</quote>
is one of the best known <name>Shakespeare</name> quotations
</text>
<tag>
</tag>
<tag>content</tag>
<tag/>
<tag attribute="value">
A well-formed XML [...] obeys the following simple rules:
- there is a single element enclosing the whole document: this is known as the root element;
- each element is completely contained by the root element, or by an element that is so contained;
- elements do not partially overlap one another;
- a tag explicitly marks the start and end of each element.
The Text Encoding Initiative (TEI) is a consortium which collectively develops and maintains a standard for the representation of texts in digital form. Its chief deliverable is a set of Guidelines which specify encoding methods for machine-readable texts, chiefly in the humanities, social sciences and linguistics. Since 1994, the TEI Guidelines have been widely used by libraries, museums, publishers, and individual scholars to present texts for online research, teaching, and preservation. In addition to the Guidelines themselves, the Consortium provides a variety of resources and training events for learning TEI, information on projects using the TEI, a bibliography of TEI-related publications, and software developed for or adapted to the TEI.
The TEI Guidelines for Electronic Text Encoding and Interchange define and document a markup language for representing the structural, renditional, and conceptual features of texts. They focus (though not exclusively) on the encoding of documents in the humanities and social sciences, and in particular on the representation of primary source materials for research and analysis. These guidelines are expressed as a modular, extensible XML schema, accompanied by detailed documentation, and are published under an open-source license.
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 and was developed initially for the publication of digital editions of ancient inscriptions [...]It addresses not only the transcription and editorial treatment of texts themselves, but also the history and materiality of the objects on which the texts appear.
https://sourceforge.net/p/epidoc/wiki/Home/
http://www.stoa.org/epidoc/gl/latest/
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:space="preserve" xml:lang="en">
<teiHeader>
<!-- Metadata -->
</teiHeader>
<facsimile>
<!-- Information on image files -->
</facsimile>
<text>
<!-- Textdata: edition, commentary, translation, etc. -->
</text>
</TEI>
EpiDoc offers a template file ex-epidoctemplate.xml
see EpiDoc Guidelines: Structure Of
An EpiDoc Edition
EpiDoc Guidelines: Structure Of An EpiDoc Edition
source epidat ffb-98
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.
Why store data about an object, when you have the object itself? Because without data about the objects contained in a space, any sufficiently complex space is indistinguishable from chaos.
Pomerantz 2017
<fileDesc>
<titleStmt>
<title>title of document</title>
</titleStmt>
<publicationStmt>
<authority></authority>
<idno type="filename"></idno>
</publicationStmt>
<sourceDesc>
<msDesc>
<msIdentifier>
<repository>museum/archive</repository>
<idno>inventory number</idno>
</msIdentifier>
<physDesc>
<objectDesc>
<supportDesc>
<support>description of object/monument
(likely to include <material/>
and <objectType/> information, <dimensions/>, etc.)
</support>
</supportDesc>
<layoutDesc>
<layout>description of text field/campus</layout>
</layoutDesc>
</objectDesc>
<handDesc>
<handNote>description of letters,
possibly including <height>letter-heights</height>
</handNote>
</handDesc>
</physDesc>
<history>
<origin>
<origPlace>Place of origin</origPlace>
<origDate>Date of origin</origDate>
</origin>
<provenance type="found"> Findspot and circumstances/context</provenance>
<provenance type="observed">Modern location(s)
(if different from repository, above)</provenance>
</history>
</msDesc>
</sourceDesc>
</fileDesc>
What characterises this class of objects is that they form a whole with their physical support. Indeed, the meaning of an epigraph cannot be fully understood without the analysis of the object or monument or other archaeological object on which it appears, just as one cannot fully understand the nature of that particular archaeological object without thoroughly investigating the sense of the inscription or iconographic representation it hosts"
Felicetti et al., 2016
http://vocab.getty.edu/tgn/7005293
to improve access to information about art, architecture, and material culture[AAT] refer to as
http://vocab.getty.edu/aat/300266769
a multilingual classification system for cultural content
By using controlled vocabularies project-specific findings are addressed by unique identifiers [digital shelf mark]
1607 | 1612 | 1774 | 1782 | 1795 | 1805 |
ffb-444 | ffb-2057 | ffb-55 | ffb-1584 | ffb-52 | ffb-1678 |
Schlomo Schuh Grotwol | Breinlen bat Schlomo | Joswel ben Schlomo Schuh | Schönle bat David Rapp | Breinche bat Süskind Leidersdorf | Gitle bat Izek ben Jaakow Hanau SeGaL |
… and displaying 200 years of shoe-design engraved in headstones
Symbols, ornaments, decoration found on Jewish headstones as well as biblical quotations in the epitaphs or the materials of the headstones or the type of script used are not strictly limited to Jewish cultural life.
- Refering to authority files and use of controlled vocabularies help to disseminate the results of our research
IIP – Inscriptions of Israel | Palestine | epidat – Database of Jewish Epigraphy | DIO – Deutsche Inschriften Online | |
---|---|---|---|
online | |||
quantity | 3.634 | 34.221 | ca. 18.000 |
time | 500 BCE - 640 CE | midth 11th - 20th century | 500-1650 CE |
space | Israel | Palestine | Germany | The Netherlands | Czechia | Lithunia | Germany | Austria | South Tyrol |
Genre | Different | Funeral Inscriptions | Different |
Format | EpiDoc: TEI XML for Epigraphic Documents | ||
Example | QUAMR0001 | ffb-80 |
XML-paths works both for
<!-- path to edition -->
/TEI//body//div [@type='edition']
<!-- path to persons -->
/TEI/teiHeader/profileDesc/particDesc/listPerson/person
<!-- metadata -->
/TEI/teiHeader
<!-- data -->
/TEI/text
These projects are the source of most examples used in the Guidelines.
xml:lang="he-Hebr"
Attributebase.css
-File div[lang="he-Hebr"], div[lang="he-Hebr"] span.ab {
direction: rtl;
unicode-bidi: bidi-override;
text-align:right;
We publish novice-friendly, peer-reviewed tutorials that help humanists learn a wide range of digital tools, techniques, and workflows to facilitate research and teaching. We are committed to fostering a diverse and inclusive community of editors, writers, and readers.