Abstract
Maya hieroglyphic script (300 BCE–1500 CE) is a semi-deciphered logographic and syllabic autochthonous writing system from the Americas and is one of the most significant writing traditions of the ancient world. Because of its incomplete state of decipherment, complexity and variation in graphematics, and partially lost lexicon, transliterations cannot be used within the encoding. The project Text Database and Dictionary of Classic Mayan approaches this challenge with an encoding strategy relying on stand-off markup, which is enriched with additional information sources. Using different formats (RDF, XML) and standards (CIDOC CRM, TEI P5), the inscriptions are encoded in a multilevel corpus: (1) a tei_all-compliant schema defining values and rules for the encoding of the text’s topological and structural features, (2) a “Sign Catalogue” for the classification of Maya hieroglyphs, and (3) the tool ALMAH (Annotator for the Linguistic analysis of MAya Hieroglyphs) for linguistic analyses. In this paper, we focus on the TEI schema and highlight our strategy for encoding hieroglyphs without using linguistic transliterations and transcriptions.
Highlights
Maya hieroglyphic script (300 BCE–1500 CE) is a semi-deciphered logographic and syllabic autochthonous writing system from the Americas and is one of the most signi cant writing traditions of the ancient world
Because of its incomplete state of decipherment, complexity and variation in graphematics, and partially lost lexicon, transliterations cannot be used within the encoding
The project Text Database and Dictionary of Classic Mayan approaches this challenge with an encoding strategy relying on stand-o markup, which is enriched with additional information sources
Summary
10 A Maya text consists of three units: elds, blocks, and glyphs ( gure 4). In order to identify glyphs that form a group within a block, a fourth element, (arbitrary segment), is used. This is needed to represent the positioning of the glyphs (see section 5). Information speci c to Maya texts is encoded in the values of attributes such as @type (see above) or @rend (see below). While these attribute values are controlled by projectspeci c taxonomies, this approach has the disadvantage that this information is not made machine-readable and interchangeable. The advantage, on the other hand, is that the markup as a whole validates to tei_all and may be processed and interpreted by generic tools
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
