The Text Encoding Initiative (TEI) is a text-centric community of practice in the academic field of digital humanities, operating continuously since the 1980s. The community currently runs a mailing list, meetings and conference series, and maintains the TEI technical standard, a journal, a wiki, a GitHub repository and toolchains for processing files and customizing the TEI framework.
TEI guidelines The TEI Guidelines collectively define an encoding standard currently serialized as an XML format. Many of its recommendations were previously expressed using and recommending use of SGML and it may allow formats other than XML in the future. The TEI Guidelines form the basis of and are the defining output of this community of practice. The format is more of a framework and differs from other well-known open formats for text (such as HTML and OpenDocument) in that it is primarily semantic rather than presentational and users can customize the TEI for their own needs. The semantics and interpretation of every tag and attribute are specified. There are over 580 individual elements representing different textual components and concepts: word, sentence, character, glyph, person, etc. In many cases general purpose elements such as damage but are then semantically extended through a series of attributes such as 'agent', 'degree', or 'extent', to provide more context for the damage. The methods of recording the user's interpretation of the textual phenomena are often grounded in one or more academic disciplines and detailed sections of the TEI Guidelines explain them with numerous examples.
Technical details The standard is split into two parts, a discursive textual description with extended examples and discussion and set of tag-by-tag definitions. Schemata in most of the modern formats (DTD, RELAX NG and XML Schema (W3C)) are generated automatically from the tag-by-tag definitions. A number of tools support the production of the guidelines and the application of the guidelines to specific projects. A number of elements can be used to document the presence of glyphs not present in Unicode such as glyph., char., or charDecl. This enables encoders to document non-Unicode characters present in their texts, but the TEI Guidelines encourage users to first check whether this is necessary. The TEI Guidelines also include documentation on how to make use of the Unicode Private Use Areas. Most users of the format do not use the complete range of elements, but produce a customisation using a project-specific subset of the tags and attributes defined by the Guidelines. The TEI defines a sophisticated customization mechanism known as ODD for this purpose. In addition to documenting and describing each TEI tag, an ODD specification specifies its content model and other usage constraints, which may be expressed using schematron. TEI Lite is an example of such a customization. It defines an XML-based file format for exchanging texts. It is a manageable selection from the extensive set of elements available in the full TEI Guidelines. As an XML-based format, TEI cannot directly deal with overlapping markup and non-hierarchical structures. A variety of options to represent this sort of data is suggested by the guidelines.
Examples The text of the TEI guidelines is rich in examples. There is also a samples page on the TEI wiki, which gives examples of real-world projects that expose their underlying TEI.
Prose tags TEI allows texts to be marked up syntactically at any level of granularity, or mixture of granularities. For example, this paragraph (p) has been marked up into sentences (s) and clauses (cl).
Verse TEI has tags for marking up verse. This example (taken from the French translation of the TEI Guidelines) shows a sonnet.
Choice tag The choice tag is used to represent sections of text that might be encoded or tagged in more than one possible way. In the following example, based on one in the standard, choice is used twice, once to indicate an original and a corrected number, and once to indicate an original and regularised spelling.
It should be noted though that XML and TEI XML in specific is not necessarily formed of embedded markup as in the above examples. It also relies on attributes which take URI-based pointers, which when used with nested hierarchies effectively creates a powerful human-readable graph notation. Moreover, TEI XML allows and enables the creation of stand off markup, often linked by xml:id attribute, with elements such as <standOff>.
ODD One Document Does it all ("ODD") is a literate programming language for XML schemas. In literate-programming style, ODD documents combine human-readable documentation and machine-readable models using the Documentation Elements module of the Text Encoding Initiative. Tools generate localised and internationalised HTML, EPUB, or PDF human-readable output and DTDs, W3C XML Schema, Relax NG Compact Syntax, or Relax NG XML Syntax machine-readable output. The Roma web application is built around the ODD format and can use it to generate schemas in DTD, W3C XML Schema, Relax NG Compact Syntax, or Relax NG XML Syntax formats, as used by many XML validation tools and services. ODD is the format used internally by the Text Encoding Initiative for the TEI technical standard. Although ODD files generally describe the difference between a customized XML format and the full TEI model, ODD also can be used to describe XML formats that are entirely separate from the TEI. One example of this is the W3C's Internationalization Tag Set which uses the ODD format to generate schemas and document its vocabulary.
TEI customizations TEI customizations are specializations of the TEI XML specification for use in particular fields or by specific communities.
EpiDoc (Epigraphic Documents) Charters Encoding Initiative Medieval Nordic Text Archive (Menota) Customization in the TEI is done through the ODD mechanism mentioned above. In truth since its P5 version, all so-called 'TEI Conformant' uses of the TEI Guidelines are based on a TEI customization documented in a TEI ODD file. Even when users choose one of the off-the-shelf pre-generated schemas to validate against, these have been created from freely available customization files.
Projects The format is used by many projects worldwide. GitHub contains more than 2 million TEI XML files. Practically all projects are associated with one or more universities. Some well-known projects that encode texts using TEI include:
… excerpt ends here. Continue reading the full article.


