TEI Lite was the name adopted for what the TEI editors originally conceived of as a simple demonstration of how the TEI (Text Encoding Initiative) encoding scheme might be adopted to meet 90% of the needs of 90% of the TEI user community. In retrospect, it was predictable that many people should imagine TEI Lite to be all there is to TEI, or find TEI Lite to be far too heavy for their needs.
The original TEI Lite (1996) was based largely on observations of existing and previous practice in the encoding of texts, particularly as manifest in the collections of the Oxford Text Archive and other collections of the period. It is therefore unsurprising that it seems to have become, if not a de facto standard, at least a common point of departure for electronic text centres and encoding projects world wide. Maybe the fact that we actually produced this shortish, readable, manual for it also helped.
Early adopters of TEI Lite included a number of ‘Electronic Text Centers’ and digital library initiatives. It was also adopted as the basis for some early TEI-conformant authoring systems, and as the basis for introductory tutorials, many of them in languages other than English (see further the list of legacy versions at http://www.tei-c.org/Lite/).
In 2002, following the publication of TEI P4 , the XML version of the TEI Guidelines, which uses the generation of TEI Lite as an example of the TEI modification mechanism, the opportunity was taken to produce a lightly revised XML-conformant version. In 2006, a more substantially revised version based on TEI P5 was produced; this reflected the many changes between TEI P4 and TEI P5, but was not otherwise significantly different. In 2012, the TEI Technical Council, decided that a final revision should be undertaken to ensure that the documentation remained consistent with the latest (2.1) release of TEI P5. This version uses a recently added mechanism in the TEI customization architecture, which permits a customization to define only the TEI elements to be included in a schema, rather than the elements to be excluded from it. As such it is probably more resilient to change than earlier versions.
This document provides an introduction to the recommendations of the Text Encoding Initiative (TEI), by describing a specific subset of the full TEI encoding scheme. The scheme documented here can be used to encode a wide variety of commonly encountered textual features, in such a way as to maximize the usability of electronic transcriptions and to facilitate their interchange among scholars using different computer systems. It is fully compatible with the full TEI scheme, as defined by TEI document P5, Guidelines for Electronic Text Encoding and Interchange, as of February 2006, and available from the TEI Consortium website at http://www.tei-c.org.
The Text Encoding Initiative (TEI) Guidelines are addressed to anyone who wants to interchange information stored in an electronic form. They emphasize the interchange of textual information, but other forms of information such as images and sound are also addressed. The Guidelines are equally applicable in the creation of new resources and in the interchange of existing ones.
The Guidelines provide a means of making explicit certain features of a text in such a way as to aid the processing of that text by computer software running on different machines. This process of making explicit we call markup or encoding. Any textual representation on a computer uses some form of markup; the TEI came into being partly because of the enormous variety of mutually incomprehensible encoding schemes currently besetting scholarship, and partly because of the expanding range of scholarly uses now being identified for texts in electronic form.
The TEI Guidelines describe an encoding scheme which can be expressed using a number of different formal languages. The first editions of the Guidelines used the Standard Generalized Markup Language (SGML); since 2002, this has been replaced by the use of the Extensible Markup Language (XML). These markup languages have in common the definition of text in terms of elements and attributes, and rules governing their appearance within a text. The TEI's use of XML is ambitious in its complexity and generality, but it is fundamentally no different from that of any other XML markup scheme, and so any general-purpose XML-aware software is able to process TEI-conformant texts.
Since 2001, the TEI has been a community initiative supported by an international membership consortium. It was originally an international research project sponsored by the Association for Computers and the Humanities, the Association for Computational Linguistics, and the Association for Literary and Linguistic Computing, with substantial funding over its first five years from the U.S. National Endowment for the Humanities, Directorate General XIII of the Commission of the European Communities, the Andrew W. Mellon Foundation, the Social Science and Humanities Research Council of Canada and others. The Guidelines were first published in May 1994, after six years of development involving many hundreds of scholars from different academic disciplines worldwide. During the years that followed, the Guidelines became increasingly influential in the development of the digital library, in the language industries, and even in the development of the World Wide Web itself. The TEI Consortium was set up in January 2001, and a year later produced an edition of the Guidelines entirely revised for XML compatibility. In 2004, it set about a major revision of the Guidelines to take full advantage of new schema languages, the first release of which appeared in 2005. This revision of the TEI Lite document conforms to version 2.1 of this most recent edition of the Guidelines, TEI P5, released in June 2012.
The present document describes a manageable selection from the extensive set of elements and recommendations resulting from those design goals, which is called TEI Lite.
In selecting from the several hundred elements defined by the full TEI scheme, we have tried to identify a useful ‘starter set’, comprising the elements which almost every user should know about. Experience working with TEI Lite will be invaluable in understanding the full TEI scheme and in knowing how to integrate specialized parts of it into the general TEI framework.
Although we have tried to make this document self-contained, as suits a tutorial text, the reader should be aware that it does not cover every detail of the TEI encoding scheme. All of the elements described here are fully documented in the TEI Guidelines themselves, which should be consulted for authoritative reference information on these, and on the many others which are not described here. Some basic knowledge of XML is assumed.
We begin with a short example, intended to show what happens when a passage of prose is typed into a computer by someone with little sense of the purpose of mark-up, or the potential of electronic texts. In an ideal world, such output might be generated by a very accurate optical scanner. It attempts to be faithful to the appearance of the printed text, by retaining the original line breaks, by introducing blanks to represent the layout of the original headings and page breaks, and so forth. Where characters not available on the keyboard are needed (such as the accented letter a in faàl or the long dash), it attempts to mimic their appearance.
All TEI-conformant texts contain (a) a TEI header (marked up as a teiHeader element) and (b) the transcription of the text proper (marked up as a text element). These two elements are combined together to form a single TEI element, which must be declared within the TEI namespace1.
The TEI header provides information analogous to that provided by the title page of a printed text. It has up to four parts: a bibliographic description of the machine-readable text, a description of the way it has been encoded, a non-bibliographic description of the text (a text profile), and a revision history. The header is described in more detail in section 19 The Electronic Title Page.
A TEI text may be unitary (a single work) or composite (a collection of single works, such as an anthology). In either case, the text may have an optional front or back. In between is the body of the text, which, in the case of a composite text, may consist of groups, each containing more groups or texts.
In the remainder of this document, we discuss chiefly simple text structures. The discussion in each case consists of a short list of relevant TEI elements with a brief definition of each, followed by definitions for any attributes specific to that element, and a reference to any classes of which the element is a member. These references are linked to full specifications for each object, as given in the TEI Guidelines. In most cases, short examples are also given.
The type attribute on the div element may be used to supply a conventional name for this category of text division, or otherwise distinguish them. Typical values might be ‘book’, ‘chapter’, ‘section’, ‘part’, ‘poem’, ‘song’, etc. For a given project, it will usually be advisable to define and adhere to a specific list of such values.
A div element may itself contain further, nested, divs, thus mimicking the traditional structure of a book, which can be decomposed hierarchically into units such as parts, containing chapters, containing sections, and so on. TEI texts in general conform to this simple hierarchic model.
The xml:id attribute may be used to supply a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary, as further discussed in section 8 Cross References and Links. It is often useful to provide an xml:id attribute for every major structural unit in a text, and to derive its values in some systematic way, for example by appending a section number to a short code for the title of the work in question, as in the examples below. It is particularly useful to supply such identifiers if the resource concerned is to be made available over the web, since they make it much easier for other web-based applications to link directly to the corresponding parts of your text.
The n attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for a division, or any other element. If a conventional form of reference or abbreviation for the parts of a work already exists (such as the book/chapter/verse pattern of Biblical citations), the n attribute is the place to record it; unlike the identifier supplied by xml:id, it does not need to be unique.
The xml:lang attribute may be used to specify the language of the division. Languages are identified by an internationally defined code, as further discussed in section 6.3 Foreign Words or Expressions below.
The rend attribute may be used to supply information about the rendition (appearance) of a division, or any other element, as further discussed in section 6 Marking Highlighted Phrases below. As with the type attribute, a project will often find it useful to predefine the possible values for this attribute, but TEI Lite does not constrain it in anyway.
These four attributes, xml:id, n, xml:lang, and rend are so widely useful that they are allowed on any element in any TEI schema: they are global attributes. Other global attributes defined in the TEI Lite scheme are discussed in section 8.3 Special kinds of Linking.
<div type="chapter" n="1">), it may be omitted; where it contains
otherwise unrecoverable text it should always be included. For example, the start of Hardy's
Under the Greenwood Tree might be encoded as follows: Note that the l element marks verse lines, not typographic lines: the original lineation of the first few lines above has not therefore been made explicit by this encoding, and may be lost. The lb element described in section 5 Page and Line Numbers might additionally be used to mark typographic lines if so desired.
#OPI etc.) are links,
pointing to a list of the characters in the novel, each of which has an identifier: When working from a paginated original, it is often useful to record its pagination, if only to simplify later proof-reading. It is also useful for synchronizing an encoded text with a set of page images. Recording the line breaks may be useful for similar reasons.
A special attribute break may be used to indicate whether or not this empty element is considered as a word-breaking, irrespective of any adjacent whitespace. For example, in the following encoded sample:
The pb and lb elements are special cases of the general class of milestone elements which mark reference points within a text. The generic milestone element can mark any kind of reference point: for example, a column break, the start of a new kind of section not otherwise tagged, or in general any significant change in the text not marked by an XML element. The names used for types of unit and for editions referred to by the ed and unit attributes may be chosen freely, but should be documented in the header refsDecl element (see 19.2.3 Reference and Classification Declarations). The milestone element may be used to replace the others, or the others may be used as a set; they should not be mixed arbitrarily.
Highlighted words or phrases are those made visibly different from the rest of the text, typically by a change of type font, handwriting style, ink colour etc., which is intended to draw the reader's attention to some associated change.
The global rend attribute can be attached to any element, and used wherever
necessary to specify details of the highlighting used for it in the source. For example, a
heading rendered in bold might be tagged <head rend="bold">, and one in
italic <head rend="italic">.
The values to be used for the
rend attribute are not specified by the TEI Guidelines, since they will depend
entirely on the needs of the particular project. Some typical values might include
italic, bold etc. for font variations;
center, right etc. for alignment; large,
small etc. for size; smallcaps, allcaps etc. for type
variants and so on. Several such words may be used in combination as necessary, but no formal
syntax is proposed. The full TEI Guidelines provide more rigorous mechanisms, using other W3C
standards such as CSS, as an alternative to the use of rend.
Some features (notably quotations and glosses) may be found in a text either marked by highlighting, or with quotation marks. In either case, the elements q and gloss (as discussed in the following section) should be used. If the highlighting is to be recorded, use the global rend attribute.
Interpreting the role of the highlighting, the sentence might look like this:On the one hand the Nibelungenlied is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach.
To record how a quotation was printed (for example, in-line or set off as a display or block quotation), the rend attribute should be used. This may also be used to indicate the kind of quotation marks used.
The creator of the electronic text must decide whether quotation marks are replaced by the tags or whether the tags are added and the quotation marks kept. If the quotation marks are removed from the text, the rend attribute may be used to record the way in which they were rendered in the copy text.
The full TEI Guidelines provide additional elements to distinguish direct speech, quotation, and other typical uses of quotation mark although it is not always possible and may not be considered desirable to interpret the function of quotation marks in a text. For simplicity, only q (which may be used for any such case) has been included in TEI Lite.
As these examples show, the foreign element should not be used to tag foreign words if some other more specific element such as title, mentioned, or term applies. The global xml:lang attribute may be attached to any element to show that it uses some other language than that of the surrounding text.
| zh | Chinese | grc | Ancient Greek |
| en | English | el | Greek |
| enm | Middle English | ja | Japanese |
| fr | French | la | Latin |
| de | German | sa | Sanskrit |
The n attribute may be used to supply the number or identifier of a note if this is required. The resp attribute should be used consistently to distinguish between authorial and editorial notes, if the work has both kinds.
Explicit cross references or links from one point in a text to another in the same or another document may be encoded using the elements described in this section. Implicit links (such as the association between two parallel texts, or that between a text and its interpretation) may be encoded using the linking attributes discussed in section 8.3 Special kinds of Linking.
The difference between these two elements is that ptr is an empty element, simply marking a point from which a link is to be made, whereas ref may contain some text as well, typically identifying the target of the cross reference. The ptr element would be used for a cross reference which is to be indicated by some non-verbal means such as a symbol or icon, or in an electronic text by a button. It is also useful in document production systems, where the formatter can generate the correct verbal form of the cross reference.
ABCD and
EFGH in this example) are to be found somewhere else in the current document.
Assuming that no element already exists to carry these identifiers, the anchor and
seg elements may be used: The type attribute should be used (as above) to distinguish amongst different purposes for which these general purpose elements might be used in a text. Some other uses are discussed in section 8.3 Special kinds of Linking below.
So far, we have shown how the elements ptr and ref may be used for
cross-references or links whose targets occur within the same document as their source.
However, the same elements may also be used to refer to elements in any other XML document or
resource, such as a document on the web, or a database component. This is possible because the
value of the target attribute may be any valid universal resource
indicator (URI) [A full definition of this term, defined by the W3C (the
consortium which manages the development and maintenance of the World Wide Web), is beyond
the scope of this tutorial: however, the most frequently encountered version of a URI is the
familiar ‘URL’ used to indicate a web page, such as
http://www.tei-c.org/index.xml].
A URI may reference a web page or just a part of one, for example
http://www.tei-c.org/index.xml#SEC2. The sharp sign indicates that what follows
it is the identifier of an element to be located within the XML document identified by what
precedes it: this example will therefore locate an element which has an xml:id
attribute value of SEC2 within the document retrieved from
http://www.tei-c.org/index.xml. In the examples we have discussed so far, the
part to the left of the sharp sign has been omitted: this is understood to mean that the
referenced element is to be located within the current document.
Parts of an XML document can be specified by means of other more sophisticated mechanisms using a special language called Xpath, also defined by the W3C. This is particularly useful where the elements to be linked to do not bear identifiers and must therefore be located by some other means.
The process of encoding an electronic text has much in common with the process of editing a manuscript or other text for printed publication. In either case a conscientious editor may wish to record both the original state of the source and any editorial correction or other change made in it. The elements discussed in this and the next section provide some facilities for meeting these needs.
#LB on the resp attribute is used to point to a fuller definition
(typically in a respStmt element) for the agency responsible for correcting the
duplication of for.#DHL points to another location where more information about the hand
concerned is to be found3. The type attribute may be used to distinguish types of abbreviation by their function.
The TEI scheme defines elements for a large number of ‘data-like’ features which may appear almost anywhere within almost any kind of text. These features may be of particular interest in a range of disciplines; they all relate to objects external to the text itself, such as the names of persons and places, numbers and dates. They also pose particular problems for many natural language processing (NLP) applications because of the variety of ways in which they may be presented within a text. The elements described here, by making such features explicit, reduce the complexity of processing texts containing them.
The name element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the rs element, or nested within it if a referring string contains a mixture of common and proper nouns.
Simply tagging something as a name is rarely enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name prefixes such as van or de la, may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.
| calendar | indicates the system or calendar to which the date represented by the content of this element belongs. |
| period | supplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred. |
| when | supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. |
twenty-one,
xxi, and 21) and their presentation is language-dependent (e.g.
English 5th becomes Greek 5.; English
123,456.78 equals French 123.456,78). In
natural-language processing or machine-translation applications, it is often helpful to
distinguish them from other, more ‘lexical’ parts of the text. In other
applications, the ability to record a number's value in standard notation is important. The
num element provides this possibility: <list type="gloss">. Here, each item comprises a term and a
gloss, marked with label and item respectively. These
correspond to the elements term and gloss, which can occur anywhere in prose
text. Where the internal structure of a list item is more complex, it may be preferable to regard the list as a table, for which special-purpose tagging is defined below (13 Tables).
Lists of bibliographic items should be tagged using the listBibl element, described in the next section.
He was a member of Parliament for Warwickshire in 1445, and died March 14, 1470 (according to Kittredge, Harvard Studies 5. 88ff).
For lists of bibliographic citations, the listBibl element should be used; it may contain a series of bibl elements.
Not all the components of a document are necessarily textual. The most straightforward text will often contain diagrams or illustrations, to say nothing of documents in which image and text are inextricably intertwined, or electronic resources in which the two are complementary.
Any textual information accompanying the graphic, such as a heading and/or caption, may be included within the figure element itself, in a head and one or more p elements, as also may any text appearing within the graphic itself. It is strongly recommended that a prose description of the image be supplied, as the content of a figDesc element, for the use of applications which are not able to render the graphic, and to render the document accessible to vision-impaired readers. (Such text is not normally considered part of the document proper.)
It is often said that all markup is a form of interpretation or analysis. While it is certainly difficult, and may be impossible, to distinguish firmly between ‘objective’ and ‘subjective’ information in any universal way, it remains true that judgments concerning the latter are typically regarded as more likely to provide controversy than those concerning the former. Many scholars therefore prefer to record such interpretations only if it is possible to alert the reader that they are considered more open to dispute, than the rest of the markup. This section describes some of the elements provided by the TEI scheme to meet this need.
The w element is a specialisation of the seg element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section 8 Cross References and Links); it identifies some phrase-level portion of text to which the encoder may assign a user-specified type, as well as a unique identifier; it may thus be used to tag textual features for which there is no other provision in the published TEI Guidelines.
A seg element of one type (unlike the s element which it superficially resembles) can be nested within a seg element of the same or another type. This enables quite complex structures to be represented; some examples were given in section 8.3 Special kinds of Linking above. However, because it must respect the requirement that elements be properly nested and may not cut across each other, it cannot cope with the common requirement to associate an interpretation with arbitrary segments of a text which may completely ignore the document hierarchy. It also requires that the interpretation itself be represented by a single coded value in the type attribute.
Moreover, interp is an empty element, which must be linked to the passage to which it applies either by means of the ana attribute discussed in section 8.3 Special kinds of Linking above, or by means of its own inst attribute. This means that any kind of analysis can be represented, with no need to respect the document hierarchy, and also facilitates the grouping of analyses of a particular type together. A special purpose interpGrp element is provided for the latter purpose.
For example, suppose that you wish to mark such diverse aspects of a text as themes or subject matter, rhetorical figures, and the locations of individual scenes of the narrative. Different portions of our sample passage from Jane Eyre for example, might be associated with the rhetorical figures of apostrophe, hyperbole, and metaphor; with subject-matter references to churches, servants, cooking, postal service, and honeymoons; and with scenes located in the church, in the kitchen, and in an unspecified location (drawing room?).
Although the focus of this document is on the use of the TEI scheme for the encoding of existing ‘pre-electronic’ documents, the same scheme may also be used for the encoding of new documents. In the preparation of new documents (such as this one), XML has much to recommend it: the document's structure can be clearly represented, and the same electronic text can be re-used for many purposes — to provide both online hypertext or browsable versions and well-formatted typeset versions from a common source for example.
To facilitate this, the TEI Lite schema includes some elements for marking features of technical documents in general, and of XML-related documents in particular.
A formatting application, given a text like that above, can be instructed to format examples appropriately (e.g. to preserve line breaks, or to use a distinctive font). Similarly, the use of tags such as ident greatly facilitates the construction of a useful index.
< to represent each < character which marks the start
of an XML tag within the examples. A more general solution is to mark off the whole body of
each example as containing data which is not to be scanned for XML mark-up by the parser. This
is achieved by enclosing it within a special XML construct called a CDATA
marked section, as in the following example: The list element used within the example above will not be regarded as forming part of the document proper, because it is embedded within a marked section (beginning with the special markup declaration <![CDATA[ , and ending with ]]>).
Note also the use of the gi element to tag references to element names (or generic identifiers) within the body of the text.
This example also demonstrates the use of the type attribute to distinguish the different kinds of division to be generated: in the first case a table of contents (a toc) and in the second an index.
When an existing index or table of contents is to be encoded (rather than one being generated) for some reason, the list element discussed in section 11 Lists should be used.
While production of a table of contents from a properly tagged document is generally unproblematic for an automatic processor, the production of a good quality index will often require more careful tagging. It may not be enough simply to produce a list of all parts tagged in some particular way, although extracting (for example) all occurrences of elements such as term or name will often be a good departure point for an index.
With the advent of XML and its adoption of Unicode as the required character set for all documents, most problems previously associated with the representation of the divers languages and writing systems of the world are greatly reduced. For those working with standard forms of the European languages in particular, almost no special action is needed: any XML editor should enable you to input accented letters or other ‘non-ASCII’ characters directly, and they should be stored in the resulting file in a way which is transferable directly between different systems.
There are two important exceptions: the characters & and < may not be entered directly
in an XML document, since they have a special significance as initiating markup. They must
always be represented as entity references, like this: & or
<. Other characters may also be represented by means of entity reference
where necessary, for example to retain compatibility with a pre-Unicode processing system.
For many purposes, particularly in older texts, the preliminary material such as title pages, prefatory epistles, etc., may provide very useful additional linguistic or social information. P5 provides a set of recommendations for distinguishing the textual elements most commonly encountered in front matter, which are summarized here.
Typeface distinctions should be marked with the rend attribute when necessary, as described above. Very detailed description of the letter spacing and sizing used in ornamental titles is not as yet provided for by the Guidelines. Changes of language should be marked by appropriate use of the xml:lang attribute or the foreign element, as necessary. Names of people, places, or organizations, may be tagged using the name element wherever they appear if no other more specific element is available.
Where other kinds of prefatory matter are encountered, the encoder is at liberty to invent other values for the type attribute.
Epistles which appear elsewhere in a text will, of course, contain these same elements.
A corpus or collection of texts with many shared characteristics may have one header for
the corpus and individual headers for each component of the corpus. In this case the
type attribute indicates the type of header. <teiHeader
type="corpus"> introduces the header for corpus-level information.
Determining exactly what constitutes a new edition of an electronic text is left to the encoder.
The extent statement describes the approximate size of the digital resource.
The seriesStmt element groups information about the series, if any, to which a publication belongs. It may contain title, idno, or respStmt elements.
The notesStmt, if used, contains one or more note elements which contain a note or annotation. Some information found in the notes area in conventional bibliography has been assigned specific elements in the TEI scheme.
The refsDecl element is used to document the way in which any standard referencing scheme built into the encoding works. In its simplest form, it consists of prose description.
Linkage between a particular text and a category within such a taxonomy is made by means of the catRef element within the textClass element, as described in the next section below.
The creation element is useful for documenting where a work was created, even though it may not have been published or recorded there.
Press
reportage - Sunday and also as Religion might be documented as follows:
Multiple classifications may be supplied using any of the mechanisms described in this section.
The revisionDesc element provides a change log in which each change made to a text may be recorded. The log may be recorded as a sequence of change elements each of which contains a brief description of the change. The attributes when and who may be used to identify when the change was carried out and the agency responsible for it.
In a production environment it will usually be found preferable to use some kind of automated system to track and record changes. Many such version control systems, as they are known, can also be configured to update the TEI Header of a file automatically.
The TEI Lite schema is a pure subset of TEI P5. In the following list of elements and classes used, some information, notably the examples, derives from the canonical definition for the element in TEI P5 and may therefore refer to elements or attributes not provided by TEI Lite. Note however that only the elements listed here are available within the TEI Lite schema. These specifications also refer to many attributes which although available in TEI Lite are not discussed in this tutorial for lack of space.
| <TEI> (TEI document) contains a single TEI-conformant document, comprising a TEI header and a text, either in isolation or as part of a teiCorpus element. [4. 15.1. ] | |
| Module | textstructure — List of Elements Described |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @rend, @style) (att.global.linking (@next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) |
| Used by | |
| Contained by | core: teiCorpus |
| May contain | |
| Declaration | element TEI { att.global.attributes, ( teiHeader, ( ( model.resourceLike+, text? ) | text ) ) } |
| Schematron | <s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> |
| Schematron | <s:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/> |
| Example | <TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <fileDesc> <titleStmt> <title>The shortest TEI Document Imaginable</title> </titleStmt> <publicationStmt> <p>First published as part of TEI P2, this is the P5 version using a name space.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <text> <body> <p>This is about the shortest TEI document imaginable.</p> </body> </text> </TEI> |
| Note | This element is required. |
| att.datable.w3c provides attributes for normalization of elements that contain datable events using the W3C datatypes. | |||||||||||||||||
| Module | tei — List of Elements Described | ||||||||||||||||
| Members | att.datable [name date time licence creation change] | ||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||
| att.global provides attributes common to all elements in the TEI encoding scheme. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | tei — List of Elements Described | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | p foreign emph hi q cit mentioned soCalled desc gloss term sic corr choice reg orig gap add del unclear name rs address addrLine num date time abbr expan ptr ref list item label head note index graphic milestone pb lb author editor respStmt resp title publisher biblScope pubPlace bibl listBibl relatedItem l lg sp speaker stage teiCorpus divGen teiHeader fileDesc titleStmt sponsor funder principal editionStmt edition extent publicationStmt distributor authority idno availability licence seriesStmt notesStmt sourceDesc encodingDesc projectDesc samplingDecl editorialDecl refsDecl classDecl taxonomy category profileDesc creation langUsage language textClass keywords classCode catRef revisionDesc change TEI text body group div trailer byline dateline argument epigraph opener closer salute signed postscript titlePage docTitle titlePart docAuthor docEdition docImprint docDate front back table row cell formula figure figDesc anchor seg s w pc interp interpGrp att code eg gi ident val | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes | Attributes att.global.linking (@next, @prev) att.global.analytic (@ana) att.global.facs (@facs)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| abbr: (abbreviation) contains an abbreviation of any sort. [3.5.5. ] |
| add: (addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator, or corrector. [3.4.3. ] |
| addrLine: (address line) contains one line of a postal address. [3.5.2. 2.2.4. 3.11.2.3. ] |
| address: contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. 2.2.4. 3.11.2.3. ] |
| anchor: (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. 16.4. ] |
| argument: A formal list or prose description of the topics addressed by a subdivision of a text. [4.2. 4.6. ] |
| att: (attribute) contains the name of an attribute appearing within running text. [22. ] |
| att.ascribed: provides attributes for elements representing speech or action that can be ascribed to a specific individual. |
| att.breaking: provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. |
| att.cReferencing: provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer. |
| att.canonical: provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. |
| att.datable: provides attributes for normalization of elements that contain dates, times, or datable events. |
| att.datcat: introduces dcr:datacat and dcr:ValueDatacat attributes that may be used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. |
| att.declarable: provides attributes for those elements in the TEI Header which may be independently selected by means of the special purpose decls attribute. |
| att.declaring: provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. |
| att.dimensions: provides attributes for describing the size of physical objects. |
| att.divLike: provides attributes common to all elements which behave in the same way as divisions. |
| att.docStatus: provides attributes for use on metadata elements describing the status of a document. |
| att.editLike: provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. |
| att.global.analytic: provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. |
| att.global.facs: groups elements corresponding with all or part of an image, because they contain an alternative representation of it, typically but not necessarily a transcription of it. |
| att.interpLike: provides attributes for elements which represent a formal analysis or interpretation. |
| att.milestoneUnit: provides an attribute to indicate the type of section which is changing at a specific milestone. |
| att.naming: provides attributes common to elements which refer to named persons, places, organizations etc. |
| att.personal: (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. |
| att.placement: provides attributes for describing where on the source page or object a textual element appears. |
| att.pointing: defines a set of attributes used by all elements which point to other elements by means of one or more URI references. |
| att.ranging: provides attributes for describing numerical ranges. |
| att.responsibility: provides attributes indicating who is responsible for something asserted by the markup and the degree of certainty associated with it. |
| att.segLike: provides attributes for elements used for arbitrary segmentation. |
| att.sortable: provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. |
| att.sourced: provides attributes identifying the source edition from which some encoded feature derives. |
| att.spanning: provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. |
| att.tableDecoration: provides attributes used to decorate rows or cells of a table. |
| att.transcriptional: provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. |
| att.translatable: provides attributes used to indicate the status of a translatable portion of an ODD document. |
| att.typed: provides attributes which can be used to classify or subclassify elements in any way. |
| author: in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. 2.2.1. ] |
| authority: (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. ] |
| availability: supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. ] |
| back: (back matter) contains any appendixes, etc. following the main part of a text. [4.7. 4. ] |
| bibl: (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. 2.2.7. 15.3.2. ] |
| biblScope: (scope of citation) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.3. ] |
| body: (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. ] |
| byline: contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. 4.5. ] |
| catRef: (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. ] |
| category: contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. ] |
| cell: contains one cell of a table. [14.1.1. ] |
| change: documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.5. 2.4.1. ] |
| choice: groups a number of alternative encodings for the same point in a text. [3.4. ] |
| cit: (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. 4.3.1. 9.3.5.1. ] |
| classCode: (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. ] |
| classDecl: (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. 2.3. ] |
| closer: groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. 4.2. ] |
| code: contains literal code from some formal language such as a programming language. |
| corr: (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. ] |
| creation: contains information about the creation of a text. [2.4.1. 2.4. ] |
| data.certainty: defines the range of attribute values expressing a degree of certainty. |
| data.code: defines the range of attribute values expressing a coded value by means of a pointer to some other element which contains a definition for it. |
| data.count: defines the range of attribute values used for a non-negative integer value used as a count. |
| data.duration.w3c: defines the range of attribute values available for representation of a duration in time using W3C datatypes. |
| data.enumerated: defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. |
| data.language: defines the range of attribute values used to identify a particular combination of human language and writing system. |
| data.name: defines the range of attribute values expressed as an XML Name. |
| data.namespace: defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. |
| data.numeric: defines the range of attribute values used for numeric values. |
| data.outputMeasurement: defines a range of values for use in specifying the size of an object that is intended for display on the web. |
| data.pointer: defines the range of attribute values used to provide a single URI pointer to any other resource, either within the current document or elsewhere. |
| data.probability: defines the range of attribute values expressing a probability. |
| data.temporal.w3c: defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes specification. |
| data.text: defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace. |
| data.truthValue: defines the range of attribute values used to express a truth value. |
| data.version: defines the range of attribute values which may be used to specify a TEI version number. |
| data.word: defines the range of attribute values expressed as a single word or token. |
| data.xTruthValue: (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. |
| date: contains a date in any format. [3.5.4. 2.2.4. 2.5. 3.11.2.3. 15.2.3. 13.3.6. ] |
| dateline: contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. ] |
| del: (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector. [3.4.3. ] |
| desc: (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.4. 22.4.5. 22.4.6. 22.4.7. ] |
| distributor: supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. ] |
| div: (text division) contains a subdivision of the front, body, or back of a text. [4.1. ] |
| divGen: (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.8.2. ] |
| docAuthor: (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. ] |
| docDate: (document date) contains the date of a document, as given (usually) on a title page. [4.6. ] |
| docEdition: (document edition) contains an edition statement as presented on a title page of a document. [4.6. ] |
| docImprint: (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. ] |
| docTitle: (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. ] |
| edition: (edition) describes the particularities of one edition of a text. [2.2.2. ] |
| editionStmt: (edition statement) groups information relating to one edition of a text. [2.2.2. 2.2. ] |
| editor: secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. ] |
| editorialDecl: (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. 2.3. 15.3.2. ] |
| eg: (example) contains any kind of illustrative example. [22.4.4. 22.4.5. ] |
| emph: (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. 3.3.2. ] |
| encodingDesc: (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. 2.1.1. ] |
| epigraph: contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. 4.2. 4.6. ] |
| expan: (expansion) contains the expansion of an abbreviation. [3.5.5. ] |
| extent: describes the approximate size of a text as stored on some carrier medium, whether digital or non-digital, specified in any convenient units. [2.2.3. 2.2. 3.11.2.3. ] |
| figDesc: (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. ] |
| figure: groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. ] |
| fileDesc: (file description) contains a full bibliographic description of an electronic file. [2.2. 2.1.1. ] |
| foreign: (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. ] |
| formula: contains a mathematical or other formula. [14.2. ] |
| front: (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. 4. ] |
| funder: (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. ] |
| gap: (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. ] |
| gi: (element name) contains the name (generic identifier) of an element. [22. 22.4.4. ] |
| gloss: identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. ] |
| graphic: indicates the location of an inline graphic, illustration, or figure. [3.9. ] |
| group: contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. 4.3.1. 15.1. ] |
| head: (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. ] |
| hi: (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. 3.3.2. ] |
| ident: (identifier) contains an identifier or name for an object of some kind in a formal language. ident is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. ] |
| idno: (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. 2.2.5. 3.11.2.3. ] |
| index: (index entry) marks a location to be indexed for whatever purpose. [3.8.2. ] |
| interp: (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. ] |
| interpGrp: (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. ] |
| item: contains one component of a list. [3.7. 2.5. ] |
| keywords: contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. ] |
| l: (verse line) contains a single, possibly incomplete, line of verse. [3.12.1. 3.12. 7.2.5. ] |
| label: contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. ] |
| langUsage: (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. 2.4. 15.3.2. ] |
| language: characterizes a single language or sublanguage used within a text. [2.4.2. ] |
| lb: (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. 7.2.5. ] |
| lg: (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.12.1. 3.12. 7.2.5. ] |
| licence: contains information about a licence or other legal agreement applicable to the text. [2.2.4. ] |
| list: (list) contains any sequence of items organized as a list. [3.7. ] |
| listBibl: (citation list) contains a list of bibliographic citations of any kind. [3.11.1. 2.2.7. 15.3.2. ] |
| macro.limitedContent: (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. |
| macro.paraContent: (paragraph content) defines the content of paragraphs and similar elements. |
| macro.phraseSeq: (phrase sequence) defines a sequence of character data and phrase-level elements. |
| macro.phraseSeq.limited: (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. |
| macro.specialPara: ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. |
| mentioned: marks words or phrases mentioned, not used. [3.3.3. ] |
| milestone: marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.10.3. ] |
| model.addrPart: groups elements such as names or postal codes which may appear as part of a postal address. |
| model.addressLike: groups elements used to represent a postal or e-mail address. |
| model.availabilityPart: groups elements such as licences and paragraphs of text which may appear as part of an availability statment |
| model.biblLike: groups elements containing a bibliographic description. |
| model.biblPart: groups elements which represent components of a bibliographic description. |
| model.certLike: groups elements which are used to indicate uncertainty or precision of other elements. |
| model.choicePart: groups elements (other than choice itself) which can be used within a choice alternation. |
| model.common: groups common chunk- and inter-level elements. |
| model.dateLike: groups elements containing temporal expressions. |
| model.descLike: groups elements which contain a description of their function. |
| model.div1Like: groups top-level structural divisions. |
| model.divBottom: groups elements appearing at the end of a text division. |
| model.divBottomPart: groups elements which can occur only at the end of a text division. |
| model.divGenLike: groups elements used to represent a structural division which is generated rather than explicitly present in the source. |
| model.divLike: groups elements used to represent un-numbered generic structural divisions. |
| model.divPart: groups paragraph-level elements appearing directly within divisions. |
| model.divTop: groups elements appearing at the beginning of a text division. |
| model.divTopPart: groups elements which can occur only at the beginning of a text division. |
| model.divWrapper: groups elements which can appear at either top or bottom of a textual division. |
| model.editorialDeclPart: groups elements which may be used inside editorialDecl and appear multiple times. |
| model.egLike: groups elements containing examples or illustrations. |
| model.emphLike: groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. |
| model.encodingDescPart: groups elements which may be used inside encodingDesc and appear multiple times. |
| model.entryPart: groups elements appearing at any level within a dictionary entry. |
| model.entryPart.top: groups high level elements within a structured dictionary entry |
| model.frontPart: groups elements which appear at the level of divisions within front or back matter. |
| model.gLike: groups elements used to represent individual non-Unicode characters or glyphs. |
| model.global: groups elements which may appear at any point within a TEI text. |
| model.global.edit: groups globally available elements which perform a specifically editorial function. |
| model.global.meta: groups globally available elements which describe the status of other elements. |
| model.glossLike: groups elements which provide an alternative name, explanation, or description for any markup construct. |
| model.graphicLike: groups elements containing images, formulae, and similar objects. |
| model.headLike: groups elements used to provide a title or heading at the start of a text division. |
| model.hiLike: groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. |
| model.highlighted: groups phrase-level elements which are typographically distinct. |
| model.imprintPart: groups the bibliographic elements which occur inside imprints. |
| model.inter: groups elements which can appear either within or between paragraph-like elements. |
| model.lLike: groups elements representing metrical components such as verse lines. |
| model.lPart: groups phrase-level elements which may appear within verse only. |
| model.labelLike: groups elements used to gloss or explain other parts of a document. |
| model.limitedPhrase: groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. |
| model.linePart: groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element. |
| model.listLike: groups list-like elements. |
| model.measureLike: groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. |
| model.milestoneLike: groups milestone-style elements used to represent reference systems. |
| model.nameLike: groups elements which name or refer to a person, place, or organization. |
| model.nameLike.agent: groups elements which contain names of individuals or corporate bodies. |
| model.noteLike: groups globally-available note-like elements. |
| model.pLike: groups paragraph-like elements. |
| model.pLike.front: groups paragraph-like elements which can occur as direct constituents of front matter. |
| model.pPart.data: groups phrase-level elements containing names, dates, numbers, measures, and similar data. |
| model.pPart.edit: groups phrase-level elements for simple editorial correction and transcription. |
| model.pPart.editorial: groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. |
| model.pPart.transcriptional: groups phrase-level elements used for editorial transcription of pre-existing source materials. |
| model.phrase: groups elements which can occur at the level of individual words or phrases. |
| model.phrase.xml: groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values |
| model.profileDescPart: groups elements which may be used inside profileDesc and appear multiple times. |
| model.ptrLike: groups elements used for purposes of location and reference. |
| model.publicationStmtPart: groups elements which may appear within the publicationStmt element of the TEI Header. |
| model.qLike: groups elements related to highlighting which can appear either within or between chunk-level elements. |
| model.quoteLike: groups elements used to directly contain quotations. |
| model.resourceLike: groups non-textual elements which may appear together with a header and a text to constitute a TEI document. |
| model.respLike: groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element. |
| model.segLike: groups elements used for arbitrary segmentation. |
| model.sourceDescPart: groups elements which may be used inside sourceDesc and appear multiple times. |
| model.stageLike: groups elements containing stage directions or similar things defined by the module for performance texts. |
| model.teiHeaderPart: groups high level elements which may appear more than once in a TEI Header. |
| model.titlepagePart: groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. |
| name: (name, proper noun) contains a proper noun or noun phrase. [3.5.1. ] |
| note: contains a note or annotation. [3.8.1. 2.2.6. 3.11.2.6. 9.3.5.4. ] |
| notesStmt: (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. 2.2. ] |
| num: (number) contains a number, written in any form. [3.5.3. ] |
| opener: groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. ] |
| orig: (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.4.2. 12. ] |
| p: (paragraph) marks paragraphs in prose. [3.1. 7.2.5. ] |
| pb: (page break) marks the boundary between one page of a text and the next in a standard reference system. [3.10.3. ] |
| pc: (punctuation character) a character or string of characters regarded as constituting a single punctuation mark. [17.1. ] |
| postscript: contains a postscript, e.g. to a letter. [4.2. ] |
| principal: (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. ] |
| profileDesc: (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. 2.1.1. ] |
| projectDesc: (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. 2.3. 15.3.2. ] |
| ptr: (pointer) defines a pointer to another location. [3.6. 16.1. ] |
| pubPlace: (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.3. ] |
| publicationStmt: (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. 2.2. ] |
| publisher: provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.3. 2.2.4. ] |
| q: (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. ] |
| ref: (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. 16.1. ] |
| refsDecl: (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. 2.3. 2.3.6. ] |
| reg: (regularization) contains a reading which has been regularized or normalized in some sense. [3.4.2. 12. ] |
| relatedItem: contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.11.2.5. ] |
| resp: (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.11.2.2. 2.2.1. 2.2.2. 2.2.5. ] |
| respStmt: (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. 2.2.1. 2.2.2. 2.2.5. ] |
| revisionDesc: (revision description) summarizes the revision history for a file. [2.5. 2.1.1. ] |
| row: contains one row of a table. [14.1.1. ] |
| rs: (referencing string) contains a general purpose name or referring string. [13.2.1. 3.5.1. ] |
| s: (s-unit) contains a sentence-like division of a text. [17.1. 8.4.1. ] |
| salute: (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. ] |
| samplingDecl: (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. 2.3. 15.3.2. ] |
| seg: (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. 6.2. 7.2.5. ] |
| seriesStmt: (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. 2.2. ] |
| sic: (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. ] |
| signed: (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. ] |
| soCalled: contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. ] |
| sourceDesc: (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. ] |
| sp: (speech) An individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.12.2. 3.12. 7.2.2. ] |
| speaker: A specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.12.2. ] |
| sponsor: specifies the name of a sponsoring organization or institution. [2.2.1. ] |
| stage: (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.12.2. 3.12. 7.2.4. ] |
| table: contains text displayed in tabular form, in rows and columns. [14.1.1. ] |
| taxonomy: defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. ] |
| teiCorpus: contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text. [4. 15.1. ] |
| teiHeader: (TEI Header) supplies the descriptive and declarative information making up an electronic title page prefixed to every TEI-conformant text. [2.1.1. 15.1. ] |
| term: contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. ] |
| text: contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. 15.1. ] |
| textClass: (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. ] |
| time: contains a phrase defining a time of day in any format. [3.5.4. ] |
| title: contains a title for any kind of work. [3.11.2.2. 2.2.1. 2.2.5. ] |
| titlePage: (title page) contains the title page of a text, appearing within the front or back matter. [4.6. ] |
| titlePart: contains a subsection or division of the title of a work, as indicated on a title page. [4.6. ] |
| titleStmt: (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. 2.2. ] |
| trailer: contains a closing title or footer appearing at the end of a division of a text. [4.2.4. 4.2. ] |
| unclear: contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. 3.4.3. ] |
| val: (value) contains a single attribute value. [22. 22.4.5. ] |
| w: (word) represents a grammatical (not necessarily orthographic) word. [17.1. ] |
http://www.tei-c.org/ns/1.0