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/Vault/P4/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.
At the outset of its work, the overall goals of the TEI were defined by the closing statement of a planning conference held at Vassar College, N.Y., in November, 1987; these ‘Poughkeepsie Principles’ were further elaborated in a series of design documents. The Guidelines, say these design documents, should:
The world of scholarship is large and diverse. For the Guidelines to have wide acceptability, it was important to ensure that:
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.
Our goals in defining this subset may be summarized as follows:
The reader may judge our success in meeting these goals for him or herself.
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.
CHAPTER 38
READER, I married him. A quiet wedding we had: he and I, the par-
son and clerk, were alone present. When we got back from church, I
went into the kitchen of the manor-house, where Mary was cooking
the dinner, and John cleaning the knives, and I said --
'Mary, I have been married to Mr Rochester this morning.' The
housekeeper and her husband were of that decent, phlegmatic
order of people, to whom one may at any time safely communicate a
remarkable piece of news without incurring the danger of having
one's ears pierced by some shrill ejaculation and subsequently stunned
by a torrent of wordy wonderment. Mary did look up, and she did
stare at me; the ladle with which she was basting a pair of chickens
roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the
polishing process; but Mary, bending again over the roast, said only --
'Have you, miss? Well, for sure!'
A short time after she pursued, 'I seed you go out with the master,
but I didn't know you were gone to church to be wed'; and she
basted away. John, when I turned to him, was grinning from ear to
ear.
'I telled Mary how it would be,' he said: 'I knew what Mr Ed-
ward' (John was an old servant, and had known his master when he
was the cadet of the house, therefore he often gave him his Christian
name) -- 'I knew what Mr Edward would do; and I was certain he
would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!' and he politely pulled his forelock.
'Thank you, John. Mr Rochester told me to give you and Mary
this.'
I put into his hand a five-pound note. Without waiting to hear
more, I left the kitchen. In passing the door of that sanctum some time
after, I caught the words --
'She'll happen do better for him nor ony o' t' grand ladies.' And
again, 'If she ben't one o' th' handsomest, she's noan faa\l, and varry
good-natured; and i' his een she's fair beautiful, onybody may see
that.'
I wrote to Moor House and to Cambridge immediately, to say what
I had done: fully explaining also why I had thus acted. Diana and
474
JANE EYRE 475
Mary approved the step unreservedly. Diana announced that she
would just give me time to get over the honeymoon, and then she
would come and see me.
'She had better not wait till then, Jane,' said Mr Rochester, when I
read her letter to him; 'if she does, she will be too late, for our honey-
moon will shine our life long: its beams will only fade over your
grave or mine.'
How St John received the news I don't know: he never answered
the letter in which I communicated it: yet six months after he wrote
to me, without, however, mentioning Mr Rochester's name or allud-
ing to my marriage. His letter was then calm, and though very serious,
kind. He has maintained a regular, though not very frequent correspond-
ence ever since: he hopes I am happy, and trusts I am not of those who
live without God in the world, and only mind earthly things.
⚓This transcription suffers from a number of shortcomings:
This particular encoding represents a set of choices or priorities. As a trivial example, note that in the second example, end-of-line hyphenation has been silently removed. Conceivably Brontë (or her printer) intended the word ‘honeymoon’ to appear as ‘honey-moon’ on its second appearance, though this seems unlikely: our decision to focus on Brontë's text, rather than on the printing of it in this particular edition, makes it impossible to be certain. This is an instance of the fundamental selectivity of any encoding. An encoding makes explicit only those textual features of importance to the encoder. It is not difficult to think of ways in which the encoding of even this short passage might readily be extended. For example:
TEI-recommended ways of carrying out most of these are described in the remainder of this document. The TEI scheme as a whole also provides for an enormous range of other possibilities, of which we cite only a few:
For recommendations on these and many other possibilities, the full Guidelines should be consulted.
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.
For example, here are the elements discussed so far:
As indicated above, a simple TEI document at the textual level consists of the following elements:
Elements specific to front and back matter are described below in section 18 Front and Back Matter. In this section we discuss the elements making up the body of a text.
The body of a prose text may be just a series of paragraphs, or these paragraphs may be grouped together into chapters, sections, subsections, etc. Each paragraph is tagged using the p tag. The div element is used to represent any such grouping of paragraphs.
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.
Every div may have a title or heading at its start, and (less commonly) a trailer such as ‘End of Chapter 1’ at its end. The following elements may be used to transcribe them:
Some other elements which may be necessary at the beginning or ending of text divisions are discussed below in section 18.1.2 Prefatory Matter.
<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: As in the Bronte example above, the paragraphs making up a textual division are tagged with the p tag. In poetic or dramatic texts different tags are needed, to represent verse lines and stanzas in the first case, or individual speeches and stage directions in the second. :
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: Page and line breaks etc. may be marked with the following elements.
These elements mark a single point in the text, not a span of text. The global n attribute should be used to supply the number of the page or line beginning at the tag.
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.
It is not always possible or desirable to interpret the reasons for such changes of rendering in a text. In such cases, the element hi may be used to mark a sequence of highlighted text without making any claim as to its status.
Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available.
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.
Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation. When possible, we recommend that the underlying feature be tagged, rather than the simple fact that quotation marks appear in the text, using the following elements:
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.
The codes used to identify languages, supplied on the xml:lang attribute, must be constructed in a particular way, and must conform to common Internet standards2, as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here:
| zh | Chinese | grc | Ancient Greek |
| en | English | el | Greek |
| enm | Middle English | ja | Japanese |
| fr | French | la | Latin |
| de | German | sa | Sanskrit |
All notes, whether printed as footnotes, endnotes, marginalia, or elsewhere, should be marked using the same element:
Where possible, the body of a note should be inserted in the text at the point at which its identifier or mark first appears. This may not be possible for example with marginalia, which may not be anchored to an exact location. For simplicity, it may be adequate to position marginal notes before the relevant paragraph or other element. Notes may also be placed in a separate division of the text (as end-notes are, in printed books) and linked to the relevant portion of the text using their target attribute.
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.
A cross reference from one point within a single document to another can be encoded using either of the following elements:
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.
Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an anchor element at the appropriate spot. If the target is some sequence of words not otherwise tagged, the seg element may be introduced to mark them. These two elements are described as follows:
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)Note: 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 following special purpose linking attributes are defined for every element in the TEI Lite scheme:
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.
The following elements may be used to mark correction, that is editorial changes introduced where the editor believes the original to be erroneous:
The following elements may be used to mark normalization, that is editorial changes introduced for the sake of consistency or modernization of a text:
As an example, consider this extract from the quarto printing of Shakespeare's Henry V.
... for his nose was as sharp as a pen and a table of green feelds⚓
In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena:
#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 full TEI scheme provides more precise ways of capturing different aspects of a transcription, distinguishing for example between text added or supplied by the encoder and text indicated as supplied or deleted in the source. TEI Lite does not provide different tags for these purposes.
Like names, dates, and numbers, abbreviations may be transcribed as they stand or expanded; they may be left unmarked, or encoded using the following elements:
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.
A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings:
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.
Tags for the more detailed encoding of times and dates include the following:
| period | supplies pointers to one or more definitions of named periods of time (typically categorys, dates or <event>s) within which the datable item is understood to have occurred. |
| when [att.datable.w3c] | supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. |
Numbers can be written with either letters or digits (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:
The element list is used to mark any kind of list. A list is a sequence of text items, which may be numbered, bulleted, or arranged as a glossary list. Each item may be preceded by an item label (in a glossary list, this label is the term being defined):
<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.
It is often useful to distinguish bibliographic citations where they occur within texts being transcribed for research, if only so that they will be properly formatted when the text is printed out. The element bibl is provided for this purpose. Where the components of a bibliographic reference are to be distinguished, the following elements may be used as appropriate. It is generally useful to mark at least those parts (such as the titles of articles, books, and journals) which will need special formatting. The other elements are provided for cases where particular interest attaches to such details.
For lists of bibliographic citations, the listBibl element should be used; it may contain a series of bibl elements.
Tables represent a challenge for any text processing system, but simple tables, at least, appear in so many texts that even in the simplified TEI tag set presented here, markup for tables is necessary. The following elements are provided for this purpose:
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.
The encoder may simply record the presence of a graphic within the text, possibly with a brief description of its content, and may also provide a link to a digitized version of the graphic, using the following elements:
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.
Interpretation typically ranges across the whole of a text, with no particular respect to other structural units. A useful preliminary to intensive interpretation is therefore to segment the text into discrete and identifiable units, each of which can then bear a label for use as a sort of ‘canonical reference’. To facilitate such uses, these units may not cross each other, nor nest within each other. They may conveniently be represented using the following element:
Tokenization, that is, the identification of lexical or non-lexical tokens within a text, is a very common requirement for all kinds of textual analysis, and not an entirely trivial one. The decision as to whether, for example, ‘can't’ in English or ‘du’ in French should be treated as one word or two is not simple. Consequently it is often useful to make explicit the preferred tokenization in a marked up text. The following elements are available for this purpose:
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.
Neither restriction applies to the interp element, which provides powerful features for the encoding of quite complex interpretive information in a relatively straightforward manner.
These elements allow the encoder to specify both the class of an interpretation, and the particular instance of that class which the interpretation involves. Thus, whereas with seg one can say simply that something is an apostrophe, with interp one can say that it is an instance (apostrophe) of a larger class (rhetorical figures).
Moreover, interp is a ‘stand off’ element: it does not surround the segments of text which it describes, but instead is linked to the passage in question 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, independently of the document hierarchy, as well as facilitating 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.
The following elements may be used to mark particular features of technical documents:
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.
A particular problem arises when XML encoding is the subject of discussion within a technical document, itself encoded in XML. In such a document, it is clearly essential to distinguish clearly the markup occurring within examples from that marking up the document itself, and end-tags are highly likely to occur. One simple solution is to use the predefined entity reference < 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:
<p>A list should be encoded as
follows: <eg><![ CDATA [ <list> <item>First item in the
list</item> <item>Second item</item> </list> ]]> </eg> The
<gi>list</gi> element consists of a series of <gi>item</gi>
elements.⚓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.
Most modern document production systems have the ability to generate automatically whole sections such as a table of contents or an index. The TEI Lite scheme provides an element to mark the location at which such a generated section should be placed.
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.
The TEI schema provides a special purpose index tag which may be used to mark both the parts of the document which should be indexed, and how the indexing should be done.
The address element is used to mark a postal address of any kind. It contains one or more addrLine elements, one for each line of the address.
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.
The start of a title page should be marked with the element titlePage. All text contained on the page should be transcribed and tagged with the appropriate element from the following list:
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.
Major blocks of text within the front matter should be marked using div elements; the following suggested values for the type attribute may be used to distinguish various common types of prefatory matter:
Where other kinds of prefatory matter are encountered, the encoder is at liberty to invent other values for the type attribute.
Like any text division, those in front matter may contain low level structural or non-structural elements as described elsewhere. They will generally begin with a heading or title of some kind which should be tagged using the head element. Epistles will contain the following additional elements:
Epistles which appear elsewhere in a text will, of course, contain these same elements.
Because of variations in publishing practice, back matter can contain virtually any of the elements listed above for front matter, and the same elements should be used where this is so. Additionally, back matter may contain the following types of matter within the back element. Like the structural divisions of the body, these should be marked as div elements, and distinguished by the following suggested values of the type attribute:
Every TEI text has a header which provides information analogous to that provided by the title page of printed text. The header is introduced by the element teiHeader and has four major parts:
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.
Some of the header elements contain running prose which consists of one or more ps. Others are grouped:
The fileDesc element is mandatory. It contains a full bibliographic description of the file with the following elements:
The following elements can be used in the titleStmt:
[title of source]: a machine readable transcription [title of source]: electronic edition A machine readable version of: [title of source]⚓The respStmt element contains the following subcomponents:
The editionStmt groups information relating to one edition of the digital resource (where edition is used as elsewhere in bibliography), and may include the following elements:
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 publicationStmt is mandatory. It may contain a simple prose description or groups of the elements described below:
At least one of these three elements must be present, unless the entire publication statement is in prose. The following elements may occur within them:
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 sourceDesc is a mandatory element which records details of the source or sources from which the computer file is derived. It may contain simple prose or a bibliographic citation, using one or more of the following elements:
The encodingDesc element specifies the methods and editorial principles which governed the transcription of the text. Its use is highly recommended. It may be prose description or may contain elements from the following list:
The editorialDecl contains a prose description of the practices used when encoding the text. Typically this description should cover such topics as the following, each of which may conveniently be given as a separate paragraph.
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.
The classDecl element groups together definitions or sources for any descriptive classification schemes used by other parts of the header. At least one such scheme must be provided, encoded using the following elements:
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 profileDesc element enables information characterizing various descriptive aspects of a text to be recorded within a single framework. It has three optional components:
The creation element is useful for documenting where a work was created, even though it may not have been published or recorded there.
The textClass element classifies a text. This may be done with reference to a classification system locally defined by means of the classDecl element, or by reference to some externally defined established scheme such as the Universal Decimal Classification. Texts may also be classified using lists of keywords, which may themselves be drawn from locally or externally defined control lists. The following elements are used to supply such classifications:
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.
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||||
| May contain | |||||||||||||
| Note | If abbreviations are expanded silently, this practice should be documented in the editorialDecl, either with a <normalization> element or a p. | ||||||||||||
| Example | <choice> <expan>North Atlantic Treaty Organization</expan> <abbr cert="low">NorATO</abbr> <abbr cert="high">NATO</abbr> <abbr cert="high" xml:lang="fr">OTAN</abbr> </choice> | ||||||||||||
| Example | <choice> <abbr>SPQR</abbr> <expan>senatus populusque romanorum</expan> </choice> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element abbr { att.global.attributes, att.typed.attribute.subtype, att.cmc.attributes, attribute type { teidata.enumerated }?, macro.phraseSeq } | ||||||||||||
| <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | In a diplomatic edition attempting to represent an original source, the add element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the corr or <supplied> element are recommended. In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of add may be appropriate, dependent on the editorial philosophy of the project. |
| Example | The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title. |
| Content model | <content> |
| Schema Declaration | element add { att.global.attributes, att.transcriptional.attributes, att.placement.attributes, att.typed.attributes, att.dimensions.attributes, att.cmc.attributes, macro.paraContent } |
| <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal publicationStmt sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc. |
| Example | Using just the elements defined by the core module, an address could be represented as follows: <address> <street>via Marsala 24</street> <postCode>40126</postCode> <name>Bologna</name> <name>Italy</name> </address> |
| Example | When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name: <address> <street>via Marsala 24</street> <postCode>40126</postCode> <settlement>Bologna</settlement> <country>Italy</country> </address> |
| Example | <address> <addrLine>Computing Center, MC 135</addrLine> <addrLine>P.O. Box 6998</addrLine> <addrLine>Chicago, IL 60680</addrLine> <addrLine>USA</addrLine> </address> |
| Example | <address> <country key="FR"/> <settlement type="city">Lyon</settlement> <postCode>69002</postCode> <district type="arrondissement">IIème</district> <district type="quartier">Perrache</district> <street> <num>30</num>, Cours de Verdun</street> </address> |
| Content model | <content> |
| Schema Declaration | element address { att.global.attributes, att.cmc.attributes, ( model.global*, ( ( model.addrPart, model.global* )+ ) ) } |
| <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: address |
| May contain | |
| Note | Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text. |
| Example | <address> <addrLine>Computing Center, MC 135</addrLine> <addrLine>P.O. Box 6998</addrLine> <addrLine>Chicago, IL</addrLine> <addrLine>60680 USA</addrLine> </address> |
| Example | <addrLine> <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine> |
| Content model | <content> |
| Schema Declaration |
element addrLine { att.global.attributes, macro.phraseSeq } |
| <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 17.5. Correspondence and Alignment] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list listBibl mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | Empty element |
| Note | On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence. |
| Example | <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s> <s>Help me find it.<ptr target="#A234"/> </s> |
| Content model | <content> |
| Schema Declaration | element anchor { att.global.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <argument> (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <argument> <p>Monte Video — Maldonado — Excursion to R Polanco — Lazo and Bolas — Partridges — Absence of Trees — Deer — Capybara, or River Hog — Tucutuco — Molothrus, cuckoo-like habits — Tyrant Flycatcher — Mocking-bird — Carrion Hawks — Tubes formed by Lightning — House struck</p> </argument> |
| Content model | <content> |
| Schema Declaration | element argument { att.global.attributes, att.cmc.attributes, ( ( model.global | model.headLike )*, ( ( model.common, model.global* )+ ) ) } |
| <att> (attribute) contains the name of an attribute appearing within running text. [23. Documentation Elements] | |||||||||
| Module | tagdocs | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||
| May contain | XSD Name | ||||||||
| Note | As an alternative to using the scheme attribute a namespace prefix may be used. Where both scheme and a prefix are used, the prefix takes precedence. | ||||||||
| Example | <p>The TEI defines several <soCalled>global</soCalled> attributes; their names include <att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>, and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element att { att.global.attributes, attribute scheme { teidata.enumerated }?, teidata.name } | ||||||||
| <author> (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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Note | Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource. In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast. Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given. |
| Example | <author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author> <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author> <orgName key="BBC">British Broadcasting Corporation</orgName>: Radio 3 Network </author> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element author { att.global.attributes, att.naming.attributes, att.datable.attributes, macro.phraseSeq } |
| <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. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | |
| Example | <authority>John Smith</authority> |
| Content model | <content> |
| Schema Declaration | element authority { att.global.attributes, att.canonical.attributes, macro.phraseSeq.limited } |
| <availability> (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. Publication, Distribution, Licensing, etc.] | |||||||||
| Module | header | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: bibl header: publicationStmt | ||||||||
| May contain | |||||||||
| Note | A consistent format should be adopted | ||||||||
| Example | <availability status="restricted"> <p>Available for academic research purposes only.</p> </availability> <availability status="free"> <p>In the public domain</p> </availability> <availability status="restricted"> <p>Available under licence from the publishers.</p> </availability> | ||||||||
| Example | <availability> <licence target="http://opensource.org/licenses/MIT"> <p>The MIT License applies to this document.</p> <p>Copyright (C) 2011 by The University of Victoria</p> <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p> <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p> <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> </licence> </availability> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element availability { att.global.attributes, att.declarable.attributes, attribute status { "free" | "unknown" | "restricted" }?, ( model.availabilityPart | model.pLike )+ } | ||||||||
| <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Note | Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical. |
| Example | <back> <div type="appendix"> <head>The Golden Dream or, the Ingenuous Confession</head> <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she had like to have been, too fond of Money <!-- .... --> </p> </div> <!-- ... --> <div type="epistle"> <head>A letter from the Printer, which he desires may be inserted</head> <salute>Sir.</salute> <p>I have done with your Copy, so you may return it to the Vatican, if you please; <!-- ... --> </p> </div> <div type="advert"> <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr Newbery's at the Bible and Sun in St Paul's Church-yard.</head> <list> <item n="1">The Christmas Box, Price 1d.</item> <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... --> <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations, 10 Vol, Pr. bound 1l.</item> </list> </div> <div type="advert"> <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St. Paul's Church-Yard.</head> <list> <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d</item> <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... --> </list> </div> </back> |
| Content model | <content> |
| Schema Declaration | element back { att.global.attributes, att.declaring.attributes, ( ( model.frontPart | model.pLike.front | model.pLike | model.listLike | model.global )*, ( ( model.div1Like, ( model.frontPart | model.div1Like | model.global )* ) | ( model.divLike, ( model.frontPart | model.divLike | model.global )* ) )?, ( ( model.divBottomPart, ( model.divBottomPart | model.global )* )? ) ) } |
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl> |
| Example | <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> |
| Example | <bibl type="article" subtype="book_chapter" xml:id="carlin_2003"> <author> <name> <surname>Carlin</surname> (<forename>Claire</forename>)</name> </author>, <title level="a">The Staging of Impotence : France’s last congrès</title> dans <bibl type="monogr"> <title level="m">Theatrum mundi : studies in honor of Ronald W. Tobin</title>, éd. <editor> <name> <forename>Claire</forename> <surname>Carlin</surname> </name> </editor> et <editor> <name> <forename>Kathleen</forename> <surname>Wine</surname> </name> </editor>, <pubPlace>Charlottesville, Va.</pubPlace>, <publisher>Rookwood Press</publisher>, <date when="2003">2003</date>. </bibl> </bibl> |
| Content model | <content> |
| Schema Declaration | element bibl { att.global.attributes, att.declarable.attributes, att.typed.attributes, att.sortable.attributes, att.docStatus.attributes, att.cmc.attributes, ( text | model.gLike | model.highlighted | model.pPart.data | model.pPart.edit | model.segLike | model.ptrLike | model.biblPart | model.global )* } |
| <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: seriesStmt |
| May contain | |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint. |
| Example | <biblScope>pp 12–34</biblScope> <biblScope unit="page" from="12" to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope> |
| Content model | <content> |
| Schema Declaration | element biblScope { att.global.attributes, att.citing.attributes, macro.phraseSeq } |
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Example | <body> <l>Nu scylun hergan hefaenricaes uard</l> <l>metudæs maecti end his modgidanc</l> <l>uerc uuldurfadur sue he uundra gihuaes</l> <l>eci dryctin or astelidæ</l> <l>he aerist scop aelda barnum</l> <l>heben til hrofe haleg scepen.</l> <l>tha middungeard moncynnæs uard</l> <l>eci dryctin æfter tiadæ</l> <l>firum foldu frea allmectig</l> <trailer>primo cantauit Cædmon istud carmen.</trailer> </body> |
| Content model | <content> |
| Schema Declaration | element body { att.global.attributes, att.declaring.attributes, ( model.global*, ( ( model.divTop, ( model.global | model.divTop )* )? ), ( ( model.divGenLike, ( model.global | model.divGenLike )* )? ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) )? ) ), ( ( model.divBottom, model.global* )* ) ) } |
| <byline> (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. Openers and Closers 4.5. Front Matter] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the docAuthor element. |
| Example | <byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline> |
| Example | <byline>Written from her own MEMORANDUMS</byline> |
| Example | <byline>By George Jones, Political Editor, in Washington</byline> |
| Example | <byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline> |
| Content model | <content> |
| Schema Declaration | element byline { att.global.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | docAuthor | model.global )* } |
| <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | header: category |
| May contain | |
| Example | <catDesc>Prose reportage</catDesc> |
| Example | <catDesc> <textDesc n="novel"> <channel mode="w">print; part issues</channel> <constitution type="single"/> <derivation type="original"/> <domain type="art"/> <factuality type="fiction"/> <interaction type="none"/> <preparedness type="prepared"/> <purpose type="entertain" degree="high"/> <purpose type="inform" degree="medium"/> </textDesc> </catDesc> |
| Content model | <content> |
| Schema Declaration | element catDesc { att.global.attributes, att.canonical.attributes, ( text | model.limitedPhrase | model.catDescPart )* } |
| <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | |
| Example | <category xml:id="b1"> <catDesc>Prose reportage</catDesc> </category> |
| Example | <category xml:id="b2"> <catDesc>Prose </catDesc> <category xml:id="b11"> <catDesc>journalism</catDesc> </category> <category xml:id="b12"> <catDesc>fiction</catDesc> </category> </category> |
| Example | <category xml:id="LIT"> <catDesc xml:lang="pl">literatura piękna</catDesc> <catDesc xml:lang="en">fiction</catDesc> <category xml:id="LPROSE"> <catDesc xml:lang="pl">proza</catDesc> <catDesc xml:lang="en">prose</catDesc> </category> <category xml:id="LPOETRY"> <catDesc xml:lang="pl">poezja</catDesc> <catDesc xml:lang="en">poetry</catDesc> </category> <category xml:id="LDRAMA"> <catDesc xml:lang="pl">dramat</catDesc> <catDesc xml:lang="en">drama</catDesc> </category> </category> |
| Content model | <content> |
| Schema Declaration | element category { att.global.attributes, att.datcat.attributes, ( ( catDesc+ | ( model.descLike | equiv | gloss )* ), category* ) } |
| <catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: textClass | ||||||
| May contain | Empty element | ||||||
| Note | The scheme attribute needs to be supplied only if more than one taxonomy has been declared. | ||||||
| Example | <catRef scheme="#myTopics" target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics"> <category xml:id="news"> <catDesc>Newspapers</catDesc> </category> <category xml:id="prov"> <catDesc>Provincial</catDesc> </category> <category xml:id="sales2"> <catDesc>Low to average annual sales</catDesc> </category> </taxonomy> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element catRef { att.global.attributes, att.pointing.attributes, attribute scheme { teidata.pointer }?, empty } | ||||||
| <cell> (cell) contains one cell of a table. [15.1.1. TEI Tables] | |
| Module | figures |
| Attributes |
|
| Contained by | figures: row |
| May contain | |
| Example | <row> <cell role="label">General conduct</cell> <cell role="data">Not satisfactory, on account of his great unpunctuality and inattention to duties</cell> </row> |
| Content model | <content> |
| Schema Declaration | element cell { att.global.attributes, att.tableDecoration.attributes, macro.specialPara } |
| <change> (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.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: revisionDesc | ||||||
| May contain | |||||||
| Note | The who attribute may be used to point to any other element, but will typically specify a respStmt or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it. It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented. | ||||||
| Example | <titleStmt> <title> ... </title> <editor xml:id="LDB">Lou Burnard</editor> <respStmt xml:id="BZ"> <resp>copy editing</resp> <name>Brett Zamir</name> </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published"> <change who="#BZ" when="2008-02-02" status="public">Finished chapter 23</change> <change who="#BZ" when="2008-01-02" status="draft">Finished chapter 2</change> <change n="P2.2" when="1991-12-21" who="#LDB">Added examples to section 3</change> <change when="1991-11-11" who="#MSM">Deleted chapter 10</change> </revisionDesc> | ||||||
| Example | <profileDesc> <creation> <listChange> <change xml:id="DRAFT1">First draft in pencil</change> <change xml:id="DRAFT2" notBefore="1880-12-09">First revision, mostly using green ink</change> <change xml:id="DRAFT3" notBefore="1881-02-13">Final corrections as supplied to printer.</change> </listChange> </creation> </profileDesc> | ||||||
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element change { att.ascribed.attributes, att.datable.attributes, att.docStatus.attributes, att.global.attributes, att.typed.attributes, attribute target { list { teidata.pointer+ } }?, macro.specialPara } | ||||||
| <choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | Because the children of a choice element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel. Note also that choice elements may self-nest. Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred. |
| Example | An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows. <p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice> <sic>1724</sic> <corr>1728</corr> </choice> of our subjects, with free access to our royal person, and other marks of our <choice> <orig>favour</orig> <reg>favor</reg> </choice>.</p> |
| Content model | <content> |
| Schema Declaration | element choice { att.global.attributes, att.cmc.attributes, ( model.choicePart | choice ), ( model.choicePart | choice ), ( model.choicePart | choice )* } |
| <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. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope cit corr del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled sp speaker stage term title unclear header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: argument body div docAuthor docDate docEdition epigraph imprimatur postscript salute signed titlePart trailer |
| May contain | |
| Example | <cit> <q>and the breath of the whale is frequently attended with such an insupportable smell, as to bring on disorder of the brain.</q> <bibl>Ulloa's South America</bibl> </cit> |
| Content model | <content> |
| Schema Declaration | element cit { att.global.attributes, att.typed.attributes, att.cmc.attributes, ( model.biblLike | model.egLike | model.entryPart | model.global | model.graphicLike | model.ptrLike | model.attributable | pc | q )+ } |
| <classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: textClass | ||||||
| May contain | |||||||
| Example | <classCode scheme="http://www.udc.org">410</classCode> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element classCode { att.global.attributes, attribute scheme { teidata.pointer }, macro.phraseSeq.limited } | ||||||
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | header: taxonomy |
| Example | <classDecl> <taxonomy xml:id="LCSH"> <bibl>Library of Congress Subject Headings</bibl> </taxonomy> </classDecl> <!-- ... --> <textClass> <keywords scheme="#LCSH"> <term>Political science</term> <term>United States -- Politics and government — Revolution, 1775-1783</term> </keywords> </textClass> |
| Content model | <content> |
| Schema Declaration |
element classDecl { att.global.attributes, taxonomy+ } |
| <closer> (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. Openers and Closers 4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <div type="letter"> <p> perhaps you will favour me with a sight of it when convenient.</p> <closer> <salute>I remain, &c. &c.</salute> <signed>H. Colburn</signed> </closer> </div> |
| Example | <div type="chapter"> <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p> <closer> <dateline> <name type="place">Trieste-Zürich-Paris,</name> <date>1914–1921</date> </dateline> </closer> </div> |
| Content model | <content> |
| Schema Declaration | element closer { att.global.attributes, att.written.attributes, att.cmc.attributes, ( text | model.gLike | signed | dateline | salute | model.phrase | model.global )* } |
| <code> contains literal code from some formal language such as a programming language. [23.1.1. Phrase Level Terms] | |||||||
| Module | tagdocs | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||
| May contain | Character data only | ||||||
| Example | <code lang="JAVA"> Size fCheckbox1Size = new Size(); fCheckbox1Size.Height = 500; fCheckbox1Size.Width = 500; xCheckbox1.setSize(fCheckbox1Size); </code> | ||||||
| Content model | <content> | ||||||
| Schema Declaration |
element code { att.global.attributes, attribute lang { teidata.word }?, text } | ||||||
| <corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | If all that is desired is to call attention to the fact that the copy text has been corrected, corr may be used alone: I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories? |
| Example | It is also possible, using the choice and sic elements, to provide an uncorrected reading: I don't know, Juan. It's so far in the past now — how <choice> <sic>we can</sic> <corr>can we</corr> </choice> prove or disprove anyone's theories? |
| Content model | <content> |
| Schema Declaration | element corr { att.global.attributes, att.editLike.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Note | The creation element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest. It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the publicationStmt element, which records date and place of publication. |
| Example | <creation> <date>Before 1987</date> </creation> |
| Example | <creation> <date when="1988-07-10">10 July 1988</date> </creation> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element creation { att.global.attributes, att.datable.attributes, ( text | model.limitedPhrase | listChange )* } |
| <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal publicationStmt sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | <date when="1980-02">early February 1980</date> |
| Example | Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date> |
| Example | <date when="1990-09">September 1990</date> |
| Content model | <content> |
| Schema Declaration | element date { att.global.attributes, att.canonical.attributes, att.datable.attributes, att.editLike.attributes, att.dimensions.attributes, att.typed.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.global )* } |
| <dateline> (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. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <dateline>Walden, this 29. of August 1592</dateline> |
| Example | <div type="chapter"> <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p> <closer> <dateline> <name type="place">Trieste-Zürich-Paris,</name> <date>1914–1921</date> </dateline> </closer> </div> |
| Content model | <content> |
| Schema Declaration | element dateline { att.global.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.global | docDate )* } |
| <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, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions. The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the gap tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the gap element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the unclear element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way. Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility). There is a clear distinction in the TEI between del and <surplus> on the one hand and gap or unclear on the other. del indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. gap or unclear, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription. |
| Example | <l> <del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del> weht der Wind </l> |
| Example | <del rend="overstrike"> <gap reason="illegible" quantity="5" unit="character"/> </del> |
| Content model | <content> |
| Schema Declaration | element del { att.global.attributes, att.transcriptional.attributes, att.typed.attributes, att.dimensions.attributes, att.cmc.attributes, macro.paraContent } |
| <desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. | ||||||||||||
| Example | Example of a desc element inside a documentation element. <dataSpec module="tei" ident="teidata.point"> <desc versionDate="2010-10-17" xml:lang="en">defines the data type used to express a point in cartesian space.</desc> <content> <dataRef name="token" restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/> </content> <!-- ... --> </dataSpec> | ||||||||||||
| Example | Example of a desc element in a non-documentation element. <place xml:id="KERG2"> <placeName>Kerguelen Islands</placeName> <!-- ... --> <terrain> <desc>antarctic tundra</desc> </terrain> <!-- ... --> </place> | ||||||||||||
| Schematron | A desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element. <sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element desc { att.global.attributes, att.translatable.attributes, att.typed.attribute.subtype, att.cmc.attributes, attribute type { "deprecationInfo" | teidata.enumerated }?, macro.limitedContent } | ||||||||||||
| <distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: publicationStmt |
| May contain | |
| Example | <distributor>Oxford Text Archive</distributor> <distributor>Redwood and Burn Ltd</distributor> |
| Content model | <content> |
| Schema Declaration | element distributor { att.global.attributes, att.canonical.attributes, macro.phraseSeq } |
| <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <body> <div type="part"> <head>Fallacies of Authority</head> <p>The subject of which is Authority in various shapes, and the object, to repress all exercise of the reasoning faculty.</p> <div n="1" type="chapter"> <head>The Nature of Authority</head> <p>With reference to any proposed measures having for their object the greatest happiness of the greatest number [...]</p> <div n="1.1" type="section"> <head>Analysis of Authority</head> <p>What on any given occasion is the legitimate weight or influence to be attached to authority [...] </p> </div> <div n="1.2" type="section"> <head>Appeal to Authority, in What Cases Fallacious.</head> <p>Reference to authority is open to the charge of fallacy when [...] </p> </div> </div> </div> </body> |
| Schematron | <sch:rule context="tei:div"> <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule> |
| Schematron | <sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element div { att.global.attributes, att.divLike.attributes, att.typed.attributes, att.declaring.attributes, att.written.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.divLike | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.divLike | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | core: head | ||||||||||||
| Note | This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software. | ||||||||||||
| Example | One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on index elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS: <back> <div1 type="backmat"> <head>Bibliography</head> <!-- ... --> </div1> <div1 type="backmat"> <head>Indices</head> <divGen n="Index Nominum" type="NAMES"/> <divGen n="Index Rerum" type="THINGS"/> </div1> </back> | ||||||||||||
| Example | Another use for divGen is to specify the location of an automatically produced table of contents: <front> <!--<titlePage>...</titlePage>--> <divGen type="toc"/> <div> <head>Preface</head> <p> ... </p> </div> </front> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element divGen { att.global.attributes, att.typed.attribute.subtype, attribute type { teidata.enumerated }?, model.headLike* } | ||||||||||||
| <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. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The document author's name often occurs within a byline, but the docAuthor element may be used whether the byline element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with byline without docAuthor.) |
| Example | <titlePage> <docTitle> <titlePart>Travels into Several Remote Nations of the World, in Four Parts.</titlePart> </docTitle> <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon, and then a Captain of several Ships</byline> </titlePage> |
| Content model | <content> |
| Schema Declaration | element docAuthor { att.global.attributes, att.canonical.attributes, att.cmc.attributes, macro.phraseSeq } |
| <docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the general date element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it. |
| Example | <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate> </docImprint> |
| Content model | <content> |
| Schema Declaration | element docDate { att.global.attributes, att.cmc.attributes, att.datable.attributes, macro.phraseSeq } |
| <docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the edition element of bibliographic citation. As usual, the shorter name has been given to the more frequent element. |
| Example | <docEdition>The Third edition Corrected</docEdition> |
| Content model | <content> |
| Schema Declaration |
element docEdition { att.global.attributes, macro.paraContent } |
| <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. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often. |
| Example | <docImprint>Oxford, Clarendon Press, 1987</docImprint> Imprints may be somewhat more complex: <docImprint> <pubPlace>London</pubPlace> Printed for <name>E. Nutt</name>, at <pubPlace>Royal Exchange</pubPlace>; <name>J. Roberts</name> in <pubPlace>wick-Lane</pubPlace>; <name>A. Dodd</name> without <pubPlace>Temple-Bar</pubPlace>; and <name>J. Graves</name> in <pubPlace>St. James's-street.</pubPlace> <date>1722.</date> </docImprint> |
| Content model | <content> |
| Schema Declaration | element docImprint { att.global.attributes, ( text | model.gLike | model.phrase | pubPlace | docDate | publisher | model.global )* } |
| <docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <docTitle> <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart> <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart> </docTitle> |
| Content model | <content> |
| Schema Declaration | element docTitle { att.global.attributes, att.canonical.attributes, ( model.global*, ( ( titlePart, model.global* )+ ) ) } |
| <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt |
| May contain | |
| Example | <edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition> |
| Content model | <content> |
| Schema Declaration |
element edition { att.global.attributes, macro.phraseSeq } |
| <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <editionStmt> <edition n="S2">Students' edition</edition> <respStmt> <resp>Adapted by </resp> <name>Elizabeth Kirk</name> </respStmt> </editionStmt> |
| Example | <editionStmt> <p>First edition, <date>Michaelmas Term, 1991.</date> </p> </editionStmt> |
| Content model | <content> |
| Schema Declaration | element editionStmt { att.global.attributes, ( model.pLike+ | ( edition, model.respLike* ) ) } |
| <editor> contains a 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.12.2.2. Titles, Authors, and Editors] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt seriesStmt titleStmt |
| May contain | |
| Note | A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. |
| Example | <editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element editor { att.global.attributes, att.naming.attributes, att.datable.attributes, macro.phraseSeq } |
| <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Example | <editorialDecl> <p>All words converted to Modern American spelling using Websters 9th Collegiate dictionary</p> <p>All opening quotation marks converted to “ all closing quotation marks converted to &cdq;.</p> </editorialDecl> |
| Content model | <content> |
| Schema Declaration | element editorialDecl { att.global.attributes, att.declarable.attributes, model.pLike+ } |
| <eg> (example) contains any kind of illustrative example. [23.5. Element Specifications 23.5.3. Attribute List Specification] | |
| Module | tagdocs |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | If the example contains material in XML markup, either it must be enclosed within a CDATA marked section, or character entity references must be used to represent the markup delimiters. If the example contains well-formed XML, it should be marked using the more specific <egXML> element. |
| Example | <p>The <gi>term</gi> element is declared using the following syntax: <eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg> </p> |
| Content model | <content> |
| Schema Declaration |
element eg { att.global.attributes, macro.phraseSeq } |
| <emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | You took the car and did <emph>what</emph>?!! |
| Example | <q>What it all comes to is this,</q> he said. <q> <emph>What does Christopher Robin do in the morning nowadays?</emph> </q> |
| Content model | <content> |
| Schema Declaration |
element emph { att.global.attributes, att.cmc.attributes, macro.paraContent } |
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | core: p |
| Example | <encodingDesc> <p>Basic encoding, capturing lexical information only. All hyphenation, punctuation, and variant spellings normalized. No formatting or layout information preserved.</p> </encodingDesc> |
| Content model | <content> |
| Schema Declaration | element encodingDesc { att.global.attributes, ( model.encodingDescPart | model.pLike )+ } |
| <epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <epigraph xml:lang="la"> <cit> <bibl>Lucret.</bibl> <quote> <l part="F">petere inde coronam,</l> <l>Vnde prius nulli velarint tempora Musae.</l> </quote> </cit> </epigraph> |
| Content model | <content> |
| Schema Declaration | element epigraph { att.global.attributes, att.cmc.attributes, ( model.common | model.global )* } |
| <expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion. If abbreviations are expanded silently, this practice should be documented in the editorialDecl, either with a <normalization> element or a p. |
| Example | The address is Southmoor <choice> <expan>Road</expan> <abbr>Rd</abbr> </choice> |
| Example | <choice xml:lang="la"> <abbr>Imp</abbr> <expan>Imp<ex>erator</ex> </expan> </choice> |
| Content model | <content> |
| Schema Declaration | element expan { att.global.attributes, att.editLike.attributes, att.cmc.attributes, macro.phraseSeq } |
| <extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent> |
| Example | The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned. <extent> <measure unit="MiB" quantity="4.2">About four megabytes</measure> <measure unit="pages" quantity="245">245 pages of source material</measure> </extent> |
| Content model | <content> |
| Schema Declaration |
element extent { att.global.attributes, macro.phraseSeq } |
| <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. [15.4. Specific Elements for Graphic Images] | |
| Module | figures |
| Attributes |
|
| Contained by | figures: figure |
| May contain | |
| Note | This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes. |
| Example | <figure> <graphic url="emblem1.png"/> <head>Emblemi d'Amore</head> <figDesc>A pair of naked winged cupids, each holding a flaming torch, in a rural setting.</figDesc> </figure> |
| Content model | <content> |
| Schema Declaration |
element figDesc { att.global.attributes, macro.limitedContent } |
| <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images] | |
| Module | figures |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | |
| Example | <figure> <head>The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> <graphic url="http://www.example.org/fig1.png" scale="0.5"/> </figure> |
| Content model | <content> |
| Schema Declaration | element figure { att.global.attributes, att.placement.attributes, att.typed.attributes, att.written.attributes, att.cmc.attributes, ( model.headLike | model.common | figDesc | model.graphicLike | model.global | model.divBottom )* } |
| <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | |
| Note | The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
| Example | <fileDesc> <titleStmt> <title>The shortest possible TEI document</title> </titleStmt> <publicationStmt> <p>Distributed as part of TEI P5</p> </publicationStmt> <sourceDesc> <p>No print source exists: this is an original digital text</p> </sourceDesc> </fileDesc> |
| Content model | <content> |
| Schema Declaration | element fileDesc { att.global.attributes, ( ( titleStmt, editionStmt?, extent?, publicationStmt, seriesStmt*, notesStmt? ), sourceDesc+ ) } |
| <foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification. This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
| Example | This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>? |
| Content model | <content> |
| Schema Declaration |
element foreign { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <formula> (formula) contains a mathematical or other formula. [15.2. Formulæ and Mathematical Expressions] | |
| Module | figures |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope cit corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | <formula notation="tex">$E=mc^2$</formula> |
| Example | <formula notation="none">E=mc<hi rend="sup">2</hi> </formula> |
| Example | <formula notation="mathml"> <m:math> <m:mi>E</m:mi> <m:mo>=</m:mo> <m:mi>m</m:mi> <m:msup> <m:mrow> <m:mi>c</m:mi> </m:mrow> <m:mrow> <m:mn>2</m:mn> </m:mrow> </m:msup> </m:math> </formula> |
| Content model | <content> |
| Schema Declaration | element formula { att.global.attributes, att.notated.attributes, att.cmc.attributes, ( text | model.graphicLike | model.hiLike )* } |
| <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Note | Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the front and back elements are identical. |
| Example | <front> <epigraph> <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q> </quote> </epigraph> <div type="dedication"> <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q> </p> </div> </front> |
| Example | <front> <div type="dedication"> <p>To our three selves</p> </div> <div type="preface"> <head>Author's Note</head> <p>All the characters in this book are purely imaginary, and if the author has used names that may suggest a reference to living persons she has done so inadvertently. ...</p> </div> </front> |
| Example | <front> <div type="abstract"> <div> <head> BACKGROUND:</head> <p>Food insecurity can put children at greater risk of obesity because of altered food choices and nonuniform consumption patterns.</p> </div> <div> <head> OBJECTIVE:</head> <p>We examined the association between obesity and both child-level food insecurity and personal food insecurity in US children.</p> </div> <div> <head> DESIGN:</head> <p>Data from 9,701 participants in the National Health and Nutrition Examination Survey, 2001-2010, aged 2 to 11 years were analyzed. Child-level food insecurity was assessed with the US Department of Agriculture's Food Security Survey Module based on eight child-specific questions. Personal food insecurity was assessed with five additional questions. Obesity was defined, using physical measurements, as body mass index (calculated as kg/m2) greater than or equal to the age- and sex-specific 95th percentile of the Centers for Disease Control and Prevention growth charts. Logistic regressions adjusted for sex, race/ethnic group, poverty level, and survey year were conducted to describe associations between obesity and food insecurity.</p> </div> <div> <head> RESULTS:</head> <p>Obesity was significantly associated with personal food insecurity for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to 2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95% CI 0.51 to 1.51). Child-level food insecurity was not associated with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p> </div> <div> <head> CONCLUSIONS:</head> <p>Personal food insecurity is associated with an increased risk of obesity only in children aged 6 to 11 years. Personal food-insecurity measures may give different results than aggregate food-insecurity measures in children.</p> </div> </div> </front> |
| Content model | <content> |
| Schema Declaration | element front { att.global.attributes, att.declaring.attributes, ( ( model.frontPart | model.pLike | model.pLike.front | model.global )*, ( ( ( ( model.div1Like, ( model.div1Like | model.frontPart | model.global )* ) | ( model.divLike, ( model.divLike | model.frontPart | model.global )* ) ), ( ( model.divBottom, ( model.divBottom | model.global )* )? ) )? ) ) } |
| <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Note | Funders provide financial support for a project; they are distinct from sponsors (see element sponsor), who provide intellectual support and authority. |
| Example | <funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element funder { att.global.attributes, att.canonical.attributes, att.datable.attributes, macro.phraseSeq.limited } |
| <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.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||
| Module | core | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg | ||||||||||||||||
| May contain | core: desc | ||||||||||||||||
| Note | The gap, unclear, and del core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The gap tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as del in the case of deliberate deletion. | ||||||||||||||||
| Example | <gap quantity="4" unit="chars" reason="illegible"/> | ||||||||||||||||
| Example | <gap quantity="1" unit="essay" reason="sampling"/> | ||||||||||||||||
| Example | <del> <gap atLeast="4" atMost="8" unit="chars" reason="illegible"/> </del> | ||||||||||||||||
| Example | <gap extent="several lines" reason="lost"/> | ||||||||||||||||
| Content model | <content> | ||||||||||||||||
| Schema Declaration | element gap { att.global.attributes, att.timed.attributes, att.editLike.attributes, att.dimensions.attributes, att.cmc.attributes, attribute reason { list { ( "cancelled" | "deleted" | "editorial" | "illegible" | "inaudible" | "irrelevant" | "sampling" | teidata.enumerated )+ } }?, attribute agent { teidata.enumerated }?, ( model.descLike | model.certLike )* } | ||||||||||||||||
| <gi> (element name) contains the name (generic identifier) of an element. [23. Documentation Elements 23.5. Element Specifications] | |||||||||
| Module | tagdocs | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||
| May contain | XSD Name | ||||||||
| Example | <p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p> This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the gi in question is not a TEI element name: in practice only one method should be adopted. | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element gi { att.global.attributes, attribute scheme { teidata.enumerated }?, teidata.name } | ||||||||
| <gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 23.4.1. Description of Components] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc category change classCode creation distributor edition extent funder language licence principal sponsor taxonomy linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | We may define <term xml:id="tdpv" rend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> |
| Content model | <content> |
| Schema Declaration | element gloss { att.global.attributes, att.declaring.attributes, att.translatable.attributes, att.typed.attributes, att.pointing.attributes, att.cReferencing.attributes, att.cmc.attributes, macro.phraseSeq } |
| <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope cit corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePage titlePart trailer |
| May contain | core: desc |
| Note | The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. Within the body of a text, a graphic element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a graphic element provides an additional digital representation of some part of the source being encoded. |
| Example | <figure> <graphic url="fig1.png"/> <head>Figure One: The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> </figure> |
| Example | <facsimile> <surfaceGrp n="leaf1"> <surface> <graphic url="page1.png"/> </surface> <surface> <graphic url="page2-highRes.png"/> <graphic url="page2-lowRes.png"/> </surface> </surfaceGrp> </facsimile> |
| Example | <facsimile> <surfaceGrp n="leaf1" xml:id="spi001"> <surface xml:id="spi001r"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001r.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001r.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001r.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001r.jpg"/> </surface> <surface xml:id="spi001v"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001v.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001v.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001v.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001v.jpg"/> <zone xml:id="spi001v_detail01"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001v-detail01.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001v-detail01.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001v-detail01.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001v-detail01.jpg"/> </zone> </surface> </surfaceGrp> </facsimile> |
| Content model | <content> |
| Schema Declaration | element graphic { att.global.attributes, att.media.attributes, att.resourced.attributes, att.declaring.attributes, att.typed.attributes, att.cmc.attributes, model.descLike* } |
| <group> (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. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Contained by | |
| May contain | |
| Example | <text> <!-- Section on Alexander Pope starts --> <front> <!-- biographical notice by editor --> </front> <group> <text> <!-- first poem --> </text> <text> <!-- second poem --> </text> </group> </text> <!-- end of Pope section--> |
| Content model | <content> |
| Schema Declaration | element group { att.global.attributes, att.declaring.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( text | group ), ( text | group | model.global )* ), model.divBottom* ) } |
| <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. Headings and Trailers] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The head element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a head element based on its structural position. A head occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section. |
| Example | The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a trailer, as in this example: <div1 n="I" type="book"> <head>In the name of Christ here begins the first book of the ecclesiastical history of Georgius Florentinus, known as Gregory, Bishop of Tours.</head> <div2 type="section"> <head>In the name of Christ here begins Book I of the history.</head> <p>Proposing as I do ...</p> <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve years passed.</p> <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six years from the beginning of the world down to the death of Saint Martin.</trailer> </div2> </div1> |
| Example | When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute. <div type="subsection"> <head place="margin">Secunda conclusio</head> <p> <lb n="1251"/> <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied> </hi> <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium [...] </p> </div> |
| Example | The head element is also used to mark headings of other units, such as lists: With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted"> <head>Connectives</head> <item>above</item> <item>accordingly</item> <item>across from</item> <item>adjacent to</item> <item>again</item> <item> <!-- ... --> </item> </list> |
| Content model | <content> |
| Schema Declaration | element head { att.global.attributes, att.typed.attributes, att.placement.attributes, att.written.attributes, att.cmc.attributes, ( text | lg | model.gLike | model.phrase | model.inter | model.lLike | model.global )* } |
| <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. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | <hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ... |
| Content model | <content> |
| Schema Declaration | element hi { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <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. [23.1.1. Phrase Level Terms] | |
| Module | tagdocs |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | Character data only |
| Note | In running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements gi and att are provided. |
| Example | <ident type="ns">http://www.tei-c.org/ns/Examples</ident> |
| Content model | <content> |
| Schema Declaration |
element ident { att.global.attributes, att.typed.attributes, text } |
| <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. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||
| Module | header | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder idno language licence principal publicationStmt seriesStmt sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||
| May contain | header: idno character data | ||||||||||
| Note | idno should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on idno are ISBN, ISSN, DOI, and URI. | ||||||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat"> <g ref="#sym"/>345 </idno> In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as | ||||||||||
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element idno { att.global.attributes, att.sortable.attributes, att.datable.attributes, att.typed.attribute.subtype, att.cmc.attributes, attribute type { "ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC" | teidata.enumerated }?, ( text | model.gLike | idno )* } | ||||||||||
| <imprimatur> (imprimatur) contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: titlePage |
| May contain | |
| Example | <imprimatur>Licensed and entred acording to Order.</imprimatur> |
| Content model | <content> |
| Schema Declaration |
element imprimatur { att.global.attributes, macro.paraContent } |
| <index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi index item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg | ||||||||
| May contain | |||||||||
| Example | David's other principal backer, Josiah ha-Kohen <index indexName="NAMES"> <term>Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES"> <term>Sura</term> </index> was David's own first cousin. | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element index { att.global.attributes, att.spanning.attributes, att.cmc.attributes, attribute indexName { teidata.name }?, ( ( term, index? )* ) } | ||||||||
| <interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [18.3. Spans and Interpretations] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | core: desc character data |
| Note | Generally, each interp element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an interp with any textual element through its ana attribute. Alternatively (or, in addition) an interp may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the interp applies. |
| Example | <interp type="structuralunit" xml:id="ana_am">aftermath</interp> |
| Content model | <content> |
| Schema Declaration | element interp { att.global.attributes, att.interpLike.attributes, att.cmc.attributes, ( text | model.gLike | model.descLike | model.certLike )* } |
| <interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [18.3. Spans and Interpretations] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | |
| Note | Any number of interp elements. |
| Example | <interpGrp resp="#TMA" type="structuralunit"> <desc>basic structural organization</desc> <interp xml:id="I1">introduction</interp> <interp xml:id="I2">conflict</interp> <interp xml:id="I3">climax</interp> <interp xml:id="I4">revenge</interp> <interp xml:id="I5">reconciliation</interp> <interp xml:id="I6">aftermath</interp> </interpGrp> <bibl xml:id="TMA"> <!-- bibliographic citation for source of this interpretive framework --> </bibl> |
| Content model | <content> |
| Schema Declaration | element interpGrp { att.global.attributes, att.interpLike.attributes, att.cmc.attributes, ( model.descLike*, interp+ ) } |
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
| Module | core |
| Attributes |
|
| Contained by | core: list |
| May contain | |
| Note | May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n. |
| Example | <list rend="numbered"> <head>Here begin the chapter headings of Book IV</head> <item n="4.1">The death of Queen Clotild.</item> <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item> <item n="4.3">The wives and children of Lothar.</item> <item n="4.4">The Counts of the Bretons.</item> <item n="4.5">Saint Gall the Bishop.</item> <item n="4.6">The priest Cato.</item> <item> ...</item> </list> |
| Content model | <content> |
| Schema Declaration | element item { att.global.attributes, att.sortable.attributes, macro.specialPara } |
| <keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: textClass | ||||||
| May contain | |||||||
| Note | Each individual keyword (including compound subject headings) should be supplied as a term element directly within the keywords element. An alternative usage, in which each term appears within an item inside a list is permitted for backwards compatibility, but is deprecated. If no control list exists for the keywords used, then no value should be supplied for the scheme attribute. | ||||||
| Example | <keywords scheme="http://classificationweb.net"> <term>Babbage, Charles</term> <term>Mathematicians - Great Britain - Biography</term> </keywords> | ||||||
| Example | <keywords> <term>Fermented beverages</term> <term>Central Andes</term> <term>Schinus molle</term> <term>Molle beer</term> <term>Indigenous peoples</term> <term>Ethnography</term> <term>Archaeology</term> </keywords> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element keywords { att.global.attributes, attribute scheme { teidata.pointer }?, ( term+ | list ) } | ||||||
| <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l> |
| Schematron | <sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element l { att.global.attributes, att.fragmentable.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.inter | model.global )* } |
| <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin: <list type="gloss" xml:lang="enm"> <head xml:lang="en">Vocabulary</head> <headLabel xml:lang="en">Middle English</headLabel> <headItem xml:lang="en">New English</headItem> <label>nu</label> <item xml:lang="en">now</item> <label>lhude</label> <item xml:lang="en">loudly</item> <label>bloweth</label> <item xml:lang="en">blooms</item> <label>med</label> <item xml:lang="en">meadow</item> <label>wude</label> <item xml:lang="en">wood</item> <label>awe</label> <item xml:lang="en">ewe</item> <label>lhouth</label> <item xml:lang="en">lows</item> <label>sterteth</label> <item xml:lang="en">bounds, frisks (cf. <cit> <ref>Chaucer, K.T.644</ref> <quote>a courser, <term>sterting</term>as the fyr</quote> </cit> </item> <label>verteth</label> <item xml:lang="la">pedit</item> <label>murie</label> <item xml:lang="en">merrily</item> <label>swik</label> <item xml:lang="en">cease</item> <label>naver</label> <item xml:lang="en">never</item> </list> |
| Example | Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element: I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runon" type="ordered"> <label>(1)</label> <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item> <label>(2) </label> <item>Not a sheet has been seen by any human eyes, excepting those of the author and the printer: the faults and the merits are exclusively my own.</item> </list> |
| Example | Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon: <list type="gloss"> <label>March 1757.</label> <item>I wrote some critical observations upon Plautus.</item> <label>March 8th.</label> <item>I wrote a long dissertation upon some lines of Virgil.</item> <label>June.</label> <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus amori.</quote> </item> <label>August.</label> <item>I went to Crassy, and staid two days.</item> </list> Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice. |
| Example | Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it. <p>[...] <lb/>& n’entrer en mauuais & mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale entre les Romains.</label> <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p> In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label. |
| Content model | <content> |
| Schema Declaration | element label { att.global.attributes, att.typed.attributes, att.placement.attributes, att.written.attributes, att.cmc.attributes, macro.phraseSeq } |
| <language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage] | |||||||||||||
| Module | header | ||||||||||||
| Attributes |
| ||||||||||||
| Contained by | header: langUsage | ||||||||||||
| May contain | |||||||||||||
| Note | Particularly for sublanguages, an informal prose characterization should be supplied as content for the element. | ||||||||||||
| Example | <langUsage> <language ident="en-US" usage="75">modern American English</language> <language ident="az-Arab" usage="20">Azerbaijani in Arabic script</language> <language ident="x-lap" usage="05">Pig Latin</language> </langUsage> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element language { att.global.attributes, attribute ident { teidata.language }, attribute usage { xsd:nonNegativeInteger }?, macro.phraseSeq.limited } | ||||||||||||
| <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Example | <langUsage> <language ident="fr-CA" usage="60">Québecois</language> <language ident="en-CA" usage="20">Canadian business English</language> <language ident="en-GB" usage="20">British English</language> </langUsage> |
| Content model | <content> |
| Schema Declaration | element langUsage { att.global.attributes, att.declarable.attributes, ( model.pLike+ | language+ ) } |
| <lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list listBibl mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | Empty element |
| Note | By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked. The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives. |
| Example | This example shows typographical line breaks within metrical lines, where they occur at different places in different editions: <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> |
| Example | This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word. <titlePart> <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart> |
| Content model | <content> |
| Schema Declaration | element lb { att.global.attributes, att.typed.attributes, att.edition.attributes, att.spanning.attributes, att.breaking.attributes, att.cmc.attributes, empty } |
| <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | contains verse lines or nested line groups only, possibly prefixed by a heading. |
| Example | <lg type="free"> <l>Let me be my own fool</l> <l>of my own making, the sum of it</l> </lg> <lg type="free"> <l>is equivocal.</l> <l>One says of the drunken farmer:</l> </lg> <lg type="free"> <l>leave him lay off it. And this is</l> <l>the explanation.</l> </lg> |
| Schematron | <sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule> |
| Schematron | <sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element lg { att.global.attributes, att.divLike.attributes, att.typed.attributes, att.declaring.attributes, att.cmc.attributes, ( ( model.divTop | model.global )*, ( model.lLike | model.stageLike | model.labelLike | model.pPart.transcriptional | lg ), ( model.lLike | model.stageLike | model.labelLike | model.pPart.transcriptional | model.global | lg )*, ( ( model.divBottom, model.global* )* ) ) } |
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: availability |
| May contain | |
| Note | A licence element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. |
| Example | <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence> |
| Example | <availability> <licence target="http://creativecommons.org/licenses/by/3.0/" notBefore="2013-01-01"> <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence applies to this document.</p> <p>The licence was added on January 1, 2013.</p> </licence> </availability> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element licence { att.global.attributes, att.pointing.attributes, att.datable.attributes, macro.specialPara } |
| <list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||||
| Example | <list rend="numbered"> <item>a butcher</item> <item>a baker</item> <item>a candlestick maker, with <list rend="bulleted"> <item>rings on his fingers</item> <item>bells on his toes</item> </list> </item> </list> | ||||||||||||
| Example | <list type="syllogism" rend="bulleted"> <item>All Cretans are liars.</item> <item>Epimenides is a Cretan.</item> <item>ERGO Epimenides is a liar.</item> </list> | ||||||||||||
| Example | <list type="litany" rend="simple"> <item>God save us from drought.</item> <item>God save us from pestilence.</item> <item>God save us from wickedness in high places.</item> <item>Praise be to God.</item> </list> | ||||||||||||
| Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section"> <head>Athelstan's Ordinance</head> <list rend="numbered"> <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with the stolen goods, [if he is] over twelve years and [if the value of the goods is] over eightpence. <list rend="numbered"> <item n="1.1">And if anyone does spare one, he is to pay for the thief with his wergild — and the thief is to be no nearer a settlement on that account — or to clear himself by an oath of that amount.</item> <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is not to be spared [whether younger or older than twelve].</item> <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may then be redeemed with 120 shillings; and the kindred are to stand surety for him that he will desist for ever.</item> <item n="1.4">And if he steals after that, they are to pay for him with his wergild, or to bring him back there.</item> <item n="1.5">And if he steals after that, they are to pay for him with his wergild, whether to the king or to him to whom it rightly belongs; and everyone of those who supported him is to pay 120 shillings to the king as a fine.</item> </list> </item> <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom no justice can be obtained, that one should order their kindred to fetch back such a person to justice and to find him a lord in public meeting. <list rend="numbered"> <item n="2.1">And if they then will not, or cannot, produce him on that appointed day, he is then to be a fugitive afterwards, and he who encounters him is to strike him down as a thief.</item> <item n="2.2">And he who harbours him after that, is to pay for him with his wergild or to clear himself by an oath of that amount.</item> </list> </item> <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds his guilty man, so that the king is appealed to, is to repay the value of the goods and 120 shillings to the king; and he who appeals to the king before he demands justice as often as he ought, is to pay the same fine as the other would have done, if he had refused him justice. <list rend="numbered"> <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes known about him, is to forfeit the slave and be liable to his wergild on the first occasionp if he does it more often, he is to be liable to pay all that he owns.</item> <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been an accessory of thieves who have committed theft, is to liable to the same.</item> </list> </item> <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is afterwards convicted at the three-fold ordeal.</item> </list> </div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. | ||||||||||||
| Example | <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple"> <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have subscribed to the pious and catholic validity of this document with the sign of the Holy Cross.</item> <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with the sign of the Holy Cross.</item> <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the sign of the Holy Cross.</item> <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the sign of the Holy Cross.</item> <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of the Holy Cross.</item> <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item> <item>I, Æthelwine, bishop, have subscribed through delegates.</item> <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy Cross.</item> </list> </p> | ||||||||||||
| Schematron | <sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element list { att.global.attributes, att.sortable.attributes, att.typed.attribute.subtype, att.cmc.attributes, attribute type { "gloss" | "index" | "instructions" | "litany" | "syllogism" | teidata.enumerated }?, ( ( model.divTop | model.global | desc* )*, ( ( ( item, model.global* )+ ) | ( headLabel?, headItem?, ( ( label, model.global*, item, model.global* )+ ) ) ), ( ( model.divBottom, model.global* )* ) ) } | ||||||||||||
| <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listBibl> <head>Works consulted</head> <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990) </bibl> <biblStruct> <analytic> <title>The Interesting story of the Children in the Wood</title> </analytic> <monogr> <title>The Penny Histories</title> <author>Victor E Neuberg</author> <imprint> <publisher>OUP</publisher> <date>1968</date> </imprint> </monogr> </biblStruct> </listBibl> |
| Content model | <content> |
| Schema Declaration | element listBibl { att.global.attributes, att.sortable.attributes, att.declarable.attributes, att.typed.attributes, att.cmc.attributes, ( model.headLike*, desc*, ( model.milestoneLike | relation | listRelation )*, ( ( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+ ) ) } |
| <mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234" xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235" xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last. |
| Content model | <content> |
| Schema Declaration | element mentioned { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <milestone> (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.11.3. Milestone Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list listBibl mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | Empty element |
| Note | For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc. The order in which milestone elements are given at a given point is not normally significant. |
| Example | <milestone n="23" ed="La" unit="Dreissiger"/> ... <milestone n="24" ed="AV" unit="verse"/> ... |
| Content model | <content> |
| Schema Declaration | element milestone { att.global.attributes, att.milestoneUnit.attributes, att.typed.attributes, att.edition.attributes, att.spanning.attributes, att.breaking.attributes, att.cmc.attributes, empty } |
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp respStmt rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. |
| Example | <name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="person" ref="#HOC001">Occleve</name> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element name { att.global.attributes, att.personal.attributes, att.datable.attributes, att.editLike.attributes, att.typed.attributes, att.cmc.attributes, macro.phraseSeq } |
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list mentioned name note num orig p pubPlace publisher q ref reg resp respStmt rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence notesStmt principal sponsor linking: seg tagdocs: eg |
| May contain | |
| Example | In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottom" type="gloss" resp="#MDMH"> <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH"> <resp>translation from German to English</resp> <name>Hottinger, Marie Donald Mackie</name> </respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
| Example | The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126" anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
| Content model | <content> |
| Schema Declaration | element note { att.global.attributes, att.placement.attributes, att.pointing.attributes, att.typed.attributes, att.written.attributes, att.anchoring.attributes, att.cmc.attributes, macro.specialPara } |
| <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. The Notes Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | core: note relatedItem |
| Note | Information of different kinds should not be grouped together into the same note. |
| Example | <notesStmt> <note>Historical commentary provided by Mark Cohen</note> <note>OCR scanning done at University of Toronto</note> </notesStmt> |
| Content model | <content> |
| Schema Declaration |
element notesStmt { att.global.attributes, ( model.noteLike | relatedItem )+ } |
| <num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||||||||||||||
| May contain | |||||||||||||||||||||||
| Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The num element is intended for use in simple applications. | ||||||||||||||||||||||
| Example | <p>I reached <num type="cardinal" value="21">twenty-one</num> on my <num type="ordinal" value="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi> </num> cm per second.</p> | ||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||
| Schema Declaration | element num { att.global.attributes, att.typed.attribute.subtype, att.ranging.attributes, att.cmc.attributes, attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" | teidata.enumerated }?, attribute value { teidata.numeric }?, macro.phraseSeq } | ||||||||||||||||||||||
| <opener> (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. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <opener> <dateline>Walden, this 29. of August 1592</dateline> </opener> |
| Example | <opener> <dateline> <name type="place">Great Marlborough Street</name> <date>November 11, 1848</date> </dateline> <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p> |
| Content model | <content> |
| Schema Declaration | element opener { att.global.attributes, att.written.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | argument | byline | dateline | epigraph | salute | signed | model.global )* } |
| <orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | If all that is desired is to call attention to the original version in the copy text, orig may be used alone: <l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l> |
| Example | More usually, an orig will be combined with a regularized form within a choice element: <l>But this will be a <choice> <orig>meere</orig> <reg>mere</reg> </choice> confusion</l> <l>And hardly shall we all be <choice> <orig>vnderstoode</orig> <reg>understood</reg> </choice> </l> |
| Content model | <content> |
| Schema Declaration |
element orig { att.global.attributes, att.cmc.attributes, macro.paraContent } |
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you done?</q> </p> <p> <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p> <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p> <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p> |
| Schematron | <sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule> |
| Schematron | <sch:rule context="tei:p"> <sch:report test="( ancestor::tei:l or ancestor::tei:lg ) and not( ancestor::tei:floatingText | parent::tei:figure | parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element p { att.global.attributes, att.declaring.attributes, att.fragmentable.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label lg list listBibl mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg |
| May contain | Empty element |
| Note | A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself. The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives. |
| Example | Page numbers may vary in different editions of a text. <p> ... <pb n="145" ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p> |
| Example | A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body> <pb n="1" facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here --> <p> <!-- ... --> </p> <pb n="2" facs="page2.png"/> <!-- similarly, for page 2 --> <p> <!-- ... --> </p> </body> |
| Content model | <content> |
| Schema Declaration | element pb { att.global.attributes, att.typed.attributes, att.edition.attributes, att.spanning.attributes, att.breaking.attributes, att.cmc.attributes, empty } |
| <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [18.1.2. Below the Word Level 18.4.2. Lightweight Linguistic Annotation] | |||||||||||||||||||||
| Module | analysis | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope cit corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||||||||||||
| May contain | |||||||||||||||||||||
| Example | <phr> <w>do</w> <w>you</w> <w>understand</w> <pc type="interrogative">?</pc> </phr> | ||||||||||||||||||||
| Example | Example encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [ID AILALW in TEI Guidelines]. <s> <w pos="PPER" msd="1.Pl.*.Nom">Wir</w> <w pos="VVFIN" msd="1.Pl.Pres.Ind">fahren</w> <w pos="APPR" msd="--">in</w> <w pos="ART" msd="Def.Masc.Akk.Sg.">den</w> <w pos="NN" msd="Masc.Akk.Sg.">Urlaub</w> <pc pos="$." msd="--" join="left">.</pc> </s> | ||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||
| Schema Declaration | element pc { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.linguistic.attributes, att.cmc.attributes, attribute force { "strong" | "weak" | "inter" }?, attribute unit { teidata.enumerated }?, attribute pre { teidata.truthValue }?, ( text | model.gLike | c | model.pPart.edit )* } | ||||||||||||||||||||
| <postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <div type="letter"> <opener> <dateline> <placeName>Rimaone</placeName> <date when="2006-11-21">21 Nov 06</date> </dateline> <salute>Dear Susan,</salute> </opener> <p>Thank you very much for the assistance splitting those logs. I'm sorry about the misunderstanding as to the size of the task. I really was not asking for help, only to borrow the axe. Hope you had fun in any case.</p> <closer> <salute>Sincerely yours,</salute> <signed>Seymour</signed> </closer> <postscript> <label>P.S.</label> <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p> </postscript> </div> |
| Content model | <content> |
| Schema Declaration | element postscript { att.global.attributes, att.written.attributes, att.cmc.attributes, ( ( model.global | model.divTopPart )*, model.common, ( model.global | model.common )*, ( ( model.divBottomPart, model.global* )* ) ) } |
| <principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Example | <principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element principal { att.global.attributes, att.canonical.attributes, att.datable.attributes, macro.phraseSeq.limited } |
| <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. The Profile Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | |
| Note | Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts. |
| Example | <profileDesc> <langUsage> <language ident="fr">French</language> </langUsage> <textDesc n="novel"> <channel mode="w">print; part issues</channel> <constitution type="single"/> <derivation type="original"/> <domain type="art"/> <factuality type="fiction"/> <interaction type="none"/> <preparedness type="prepared"/> <purpose type="entertain" degree="high"/> <purpose type="inform" degree="medium"/> </textDesc> <settingDesc> <setting> <name>Paris, France</name> <time>Late 19th century</time> </setting> </settingDesc> </profileDesc> |
| Content model | <content> |
| Schema Declaration |
element profileDesc { att.global.attributes, model.profileDescPart* } |
| <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. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Example | <projectDesc> <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc> |
| Content model | <content> |
| Schema Declaration | element projectDesc { att.global.attributes, att.declarable.attributes, model.pLike+ } |
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope cit corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg relatedItem resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal publicationStmt sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | Empty element |
| Example | <ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/> |
| Schematron | <sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element ptr { att.cReferencing.attributes, att.declaring.attributes, att.global.attributes, att.pointing.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Note | Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
| Example | <publicationStmt> <publisher>C. Muquardt </publisher> <pubPlace>Bruxelles & Leipzig</pubPlace> <date when="1846"/> </publicationStmt> |
| Example | <publicationStmt> <publisher>Chadwyck Healey</publisher> <pubPlace>Cambridge</pubPlace> <availability> <p>Available under licence only</p> </availability> <date when="1992">1992</date> </publicationStmt> |
| Example | <publicationStmt> <publisher>Zea Books</publisher> <pubPlace>Lincoln, NE</pubPlace> <date>2017</date> <availability> <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p> </availability> <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt> |
| Content model | <content> |
| Schema Declaration | element publicationStmt { att.global.attributes, ( ( ( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+ ) | model.pLike+ ) } |
| <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
| Example | <imprint> <pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
| Content model | <content> |
| Schema Declaration | element publisher { att.global.attributes, att.canonical.attributes, macro.phraseSeq } |
| <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <publicationStmt> <publisher>Oxford University Press</publisher> <pubPlace>Oxford</pubPlace> <date>1989</date> </publicationStmt> |
| Content model | <content> |
| Schema Declaration | element pubPlace { att.global.attributes, att.naming.attributes, macro.phraseSeq } |
| <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. Quotation] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope cit corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled sp speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg | ||||||||
| May contain | |||||||||
| Note | May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks. | ||||||||
| Example | It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element q { att.global.attributes, att.ascribed.directed.attributes, att.cmc.attributes, attribute type { "spoken" | "thought" | "written" | "soCalled" | "foreign" | "distinct" | "term" | "emph" | "mentioned" | teidata.enumerated }?, macro.specialPara } | ||||||||
| <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope cit corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg relatedItem resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal publicationStmt sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref> |
| Example | See also <ref target="#locution">s.v. <term>locution</term> </ref>. |
| Schematron | <sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element ref { att.cReferencing.attributes, att.declaring.attributes, att.global.attributes, att.pointing.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Example | <refsDecl> <cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)" replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/> </refsDecl> This example is a formal representation for the referencing scheme described informally in the following example. |
| Example | <refsDecl> <p>References are made up by concatenating the value for the <att>n</att> attribute on the highest level <gi>div</gi> element, followed by a space, followed by the sequential number of the next level <gi>div</gi> followed by a colon followed by the sequential number of the next (and lowest) level <gi>div</gi>.</p> </refsDecl> |
| Content model | <content> |
| Schema Declaration | element refsDecl { att.global.attributes, att.declarable.attributes, ( model.pLike+ | citeStructure+ | cRefPattern+ | refState+ ) } |
| <reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | If all that is desired is to call attention to the fact that the copy text has been regularized, reg may be used alone: <q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q> |
| Example | It is also possible to identify the individual responsible for the regularization, and, using the choice and orig elements, to provide both the original and regularized readings: <q>Please <choice> <reg resp="#LB">knock</reg> <orig>cnk</orig> </choice> if an <choice> <reg>answer</reg> <orig>nsr</orig> </choice> is <choice> <reg>required</reg> <orig>reqd</orig> </choice> </q> |
| Content model | <content> |
| Schema Declaration | element reg { att.global.attributes, att.editLike.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <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.12.2.7. Related Items] | |||||||
| Module | core | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | |||||||
| May contain | |||||||
| Note | If the target attribute is used to reference the related bibliographic item, the element must be empty. | ||||||
| Example | <biblStruct> <monogr> <author>Shirley, James</author> <title type="main">The gentlemen of Venice</title> <imprint> <pubPlace>New York</pubPlace> <publisher>Readex Microprint</publisher> <date>1953</date> </imprint> <extent>1 microprint card, 23 x 15 cm.</extent> </monogr> <series> <title>Three centuries of drama: English, 1642–1700</title> </series> <relatedItem type="otherForm"> <biblStruct> <monogr> <author>Shirley, James</author> <title type="main">The gentlemen of Venice</title> <title type="sub">a tragi-comedie presented at the private house in Salisbury Court by Her Majesties servants</title> <imprint> <pubPlace>London</pubPlace> <publisher>H. Moseley</publisher> <date>1655</date> </imprint> <extent>78 p.</extent> </monogr> </biblStruct> </relatedItem> </biblStruct> | ||||||
| Schematron | <sch:rule context="tei:relatedItem"> <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the relatedItem element must be empty</sch:report> <sch:assert test="@target or child::*">A relatedItem element should have either a @target attribute or a child element to indicate the related bibliographic item</sch:assert> </sch:rule> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element relatedItem { att.global.attributes, att.typed.attributes, attribute target { teidata.pointer }?, ( model.biblLike | model.ptrLike )? } | ||||||
| <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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Contained by | core: respStmt |
| May contain | |
| Note | The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. |
| Example | <respStmt> <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp> <name>Edward Child</name> </respStmt> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element resp { att.global.attributes, att.canonical.attributes, att.datable.attributes, macro.phraseSeq.limited } |
| <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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt seriesStmt titleStmt |
| May contain | |
| Example | <respStmt> <resp>transcribed from original ms</resp> <persName>Claus Huitfeldt</persName> </respStmt> |
| Example | <respStmt> <resp>converted to XML encoding</resp> <name>Alan Morrison</name> </respStmt> |
| Content model | <content> |
| Schema Declaration | element respStmt { att.global.attributes, att.canonical.attributes, ( ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ), note* ) } |
| <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | |
| Note | If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any change to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list. |
| Example | <revisionDesc status="embargoed"> <change when="1991-11-11" who="#LB"> deleted chapter 10 </change> </revisionDesc> |
| Content model | <content> |
| Schema Declaration | element revisionDesc { att.global.attributes, att.docStatus.attributes, ( list+ | listChange+ | change+ ) } |
| <row> (row) contains one row of a table. [15.1.1. TEI Tables] | |
| Module | figures |
| Attributes |
|
| Contained by | figures: table |
| May contain | figures: cell |
| Example | <row role="data"> <cell role="label">Classics</cell> <cell>Idle listless and unimproving</cell> </row> |
| Content model | <content> |
| Schema Declaration |
element row { att.global.attributes, att.tableDecoration.attributes, cell+ } |
| <rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | <q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q> |
| Content model | <content> |
| Schema Declaration | element rs { att.global.attributes, att.naming.attributes, att.typed.attributes, att.cmc.attributes, macro.phraseSeq } |
| <s> (s-unit) contains a sentence-like division of a text. [18.1. Linguistic Segment Categories 8.4.1. Segmentation] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the seg should be used instead. The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology. |
| Example | <head> <s>A short affair</s> </head> <s>When are you leaving?</s> <s>Tomorrow.</s> |
| Schematron | <sch:rule context="tei:s"> <sch:report test="tei:s">You may not nest one s element within another: use seg instead</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element s { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.notated.attributes, att.cmc.attributes, macro.phraseSeq } |
| <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. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <salute>To all courteous mindes, that will voutchsafe the readinge.</salute> |
| Content model | <content> |
| Schema Declaration | element salute { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Note | This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest. |
| Example | <samplingDecl> <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each text identified as relevant by respondents.</p> </samplingDecl> |
| Content model | <content> |
| Schema Declaration | element samplingDecl { att.global.attributes, att.declarable.attributes, model.pLike+ } |
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element. |
| Example | <seg>When are you leaving?</seg> <seg>Tomorrow.</seg> |
| Example | <s> <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield. </s> |
| Example | <seg type="preamble"> <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg> <seg>Sinfiotli was the eldest of his sons ...</seg> <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg> |
| Content model | <content> |
| Schema Declaration | element seg { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.written.attributes, att.notated.attributes, att.cmc.attributes, macro.paraContent } |
| <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <seriesStmt> <title>Machine-Readable Texts for the Study of Indian Literature</title> <respStmt> <resp>ed. by</resp> <name>Jan Gonda</name> </respStmt> <biblScope unit="volume">1.2</biblScope> <idno type="ISSN">0 345 6789</idno> </seriesStmt> |
| Content model | <content> |
| Schema Declaration | element seriesStmt { att.global.attributes, att.declarable.attributes, ( model.pLike+ | ( title+, ( editor | respStmt )*, ( idno | biblScope )* ) ) } |
| <sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields. |
| Example | If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone: I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories? |
| Example | It is also possible, using the choice and corr elements, to provide a corrected reading: I don't know, Juan. It's so far in the past now — how <choice> <sic>we can</sic> <corr>can we</corr> </choice> prove or disprove anyone's theories? |
| Example | for his nose was as sharp as a pen, and <choice> <sic>a Table</sic> <corr>a' babbld</corr> </choice> of green fields. |
| Content model | <content> |
| Schema Declaration |
element sic { att.global.attributes, att.cmc.attributes, macro.paraContent } |
| <signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <signed>Thine to command <name>Humph. Moseley</name> </signed> |
| Example | <closer> <signed>Sign'd and Seal'd, <list> <item>John Bull,</item> <item>Nic. Frog.</item> </list> </signed> </closer> |
| Content model | <content> |
| Schema Declaration | element signed { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <soCalled> (so called) 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. Quotation] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call <soCalled>nuts</soCalled> to Scrooge. |
| Content model | <content> |
| Schema Declaration |
element soCalled { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <sourceDesc> (source description) describes the source(s) 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. The Source Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <sourceDesc> <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> </sourceDesc> |
| Example | <sourceDesc> <p>Born digital: no previous source exists.</p> </sourceDesc> |
| Content model | <content> |
| Schema Declaration | element sourceDesc { att.global.attributes, att.declarable.attributes, ( model.pLike+ | ( model.biblLike | model.sourceDescPart | model.listLike )+ ) } |
| <sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The who attribute on this element may be used either in addition to the speaker element or as an alternative. |
| Example | <sp> <speaker>The reverend Doctor Opimian</speaker> <p>I do not think I have named a single unpresentable fish.</p> </sp> <sp> <speaker>Mr Gryll</speaker> <p>Bream, Doctor: there is not much to be said for bream.</p> </sp> <sp> <speaker>The Reverend Doctor Opimian</speaker> <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p> <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I will forbear [...]</p> </sp> |
| Content model | <content> |
| Schema Declaration | element sp { att.global.attributes, att.ascribed.directed.attributes, ( model.global*, ( ( speaker, model.global* )? ), ( ( ( lg | model.lLike | model.pLike | model.listLike | model.stageLike | model.attributable ), ( model.global* | q ) )+ ) ) } |
| <speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama] | |
| Module | core |
| Attributes |
|
| Contained by | core: sp |
| May contain | |
| Note | This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an sp element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used. |
| Example | <sp who="#ni #rsa"> <speaker>Nancy and Robert</speaker> <stage type="delivery">(speaking simultaneously)</stage> <p>The future? ...</p> </sp> <list type="speakers"> <item xml:id="ni"/> <item xml:id="rsa"/> </list> |
| Content model | <content> |
| Schema Declaration |
element speaker { att.global.attributes, macro.phraseSeq } |
| <sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Note | Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element funder), who provide the funding but do not necessarily take intellectual responsibility. |
| Example | <sponsor>Association for Computers and the Humanities</sponsor> <sponsor>Association for Computational Linguistics</sponsor> <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor> |
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element sponsor { att.global.attributes, att.canonical.attributes, att.datable.attributes, macro.phraseSeq.limited } |
| <stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction. | ||||||||||
| Example | <stage type="setting">A curtain being drawn.</stage> <stage type="setting">Music</stage> <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage> <!-- Middleton : Yorkshire Tragedy --> <stage type="exit">Exit pursued by a bear.</stage> <stage type="business">He quickly takes the stone out.</stage> <stage type="delivery">To Lussurioso.</stage> <stage type="novelistic">Having had enough, and embarrassed for the family.</stage> <!-- Lorraine Hansbury : a raisin in in the sun --> <stage type="modifier">Disguised as Ansaldo.</stage> <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage> <!-- Middleton: The Widow --> <stage type="location">At a window.</stage> <stage rend="inline" type="delivery">Aside.</stage> | ||||||||||
| Example | <l>Behold. <stage n="*" place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the <hi>Prologue</hi> was spoken, which being ended, they descended in order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element stage { att.ascribed.directed.attributes, att.global.attributes, att.placement.attributes, att.written.attributes, att.cmc.attributes, attribute type { list { ( "setting" | "entrance" | "exit" | "business" | "novelistic" | "delivery" | "modifier" | "location" | "mixed" | teidata.enumerated )* } }?, macro.specialPara } | ||||||||||
| <table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables] | |||||||||||||||||
| Module | figures | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | |||||||||||||||||
| May contain | |||||||||||||||||
| Note | Contains an optional heading and a series of rows. Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate. | ||||||||||||||||
| Example | <table rows="4" cols="4"> <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head> <row role="label"> <cell role="data"/> <cell role="data">Dossing Cribs or Lodging Houses</cell> <cell role="data">Beds</cell> <cell role="data">Needys or Nightly Lodgers</cell> </row> <row role="data"> <cell role="label">Bury St Edmund's</cell> <cell role="data">5</cell> <cell role="data">8</cell> <cell role="data">128</cell> </row> <row role="data"> <cell role="label">Thetford</cell> <cell role="data">3</cell> <cell role="data">6</cell> <cell role="data">36</cell> </row> <row role="data"> <cell role="label">Attleboro'</cell> <cell role="data">3</cell> <cell role="data">5</cell> <cell role="data">20</cell> </row> <row role="data"> <cell role="label">Wymondham</cell> <cell role="data">1</cell> <cell role="data">11</cell> <cell role="data">22</cell> </row> </table> | ||||||||||||||||
| Content model | <content> | ||||||||||||||||
| Schema Declaration | element table { att.global.attributes, att.typed.attributes, att.cmc.attributes, attribute rows { teidata.count }?, attribute cols { teidata.count }?, ( ( model.headLike | model.global )*, ( ( ( row, model.global* )+ ) | ( ( model.graphicLike, model.global* )+ ) ), ( ( model.divBottom, model.global* )* ) ) } | ||||||||||||||||
| <taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | |
| Note | Nested taxonomies are common in many fields, so the taxonomy element can be nested. |
| Example | <taxonomy xml:id="tax.b"> <bibl>Brown Corpus</bibl> <category xml:id="tax.b.a"> <catDesc>Press Reportage</catDesc> <category xml:id="tax.b.a1"> <catDesc>Daily</catDesc> </category> <category xml:id="tax.b.a2"> <catDesc>Sunday</catDesc> </category> <category xml:id="tax.b.a3"> <catDesc>National</catDesc> </category> <category xml:id="tax.b.a4"> <catDesc>Provincial</catDesc> </category> <category xml:id="tax.b.a5"> <catDesc>Political</catDesc> </category> <category xml:id="tax.b.a6"> <catDesc>Sports</catDesc> </category> </category> <category xml:id="tax.b.d"> <catDesc>Religion</catDesc> <category xml:id="tax.b.d1"> <catDesc>Books</catDesc> </category> <category xml:id="tax.b.d2"> <catDesc>Periodicals and tracts</catDesc> </category> </category> </taxonomy> |
| Example | <taxonomy> <category xml:id="literature"> <catDesc>Literature</catDesc> <category xml:id="poetry"> <catDesc>Poetry</catDesc> <category xml:id="sonnet"> <catDesc>Sonnet</catDesc> <category xml:id="shakesSonnet"> <catDesc>Shakespearean Sonnet</catDesc> </category> <category xml:id="petraSonnet"> <catDesc>Petrarchan Sonnet</catDesc> </category> </category> <category xml:id="haiku"> <catDesc>Haiku</catDesc> </category> </category> <category xml:id="drama"> <catDesc>Drama</catDesc> </category> </category> <category xml:id="meter"> <catDesc>Metrical Categories</catDesc> <category xml:id="feet"> <catDesc>Metrical Feet</catDesc> <category xml:id="iambic"> <catDesc>Iambic</catDesc> </category> <category xml:id="trochaic"> <catDesc>trochaic</catDesc> </category> </category> <category xml:id="feetNumber"> <catDesc>Number of feet</catDesc> <category xml:id="pentameter"> <catDesc>>Pentameter</catDesc> </category> <category xml:id="tetrameter"> <catDesc>>Tetrameter</catDesc> </category> </category> </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter"> <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg> |
| Content model | <content> |
| Schema Declaration | element taxonomy { att.global.attributes, att.datcat.attributes, ( ( ( category | taxonomy )+ | ( ( model.descLike | equiv | gloss )+, ( category | taxonomy )* ) ) | ( model.biblLike, ( category | taxonomy )* ) ) } |
| <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or teiCorpus) element. [4. Default Text Structure 16.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. |
| Example | <TEI version="3.3.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 namespace.</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> |
| Example | <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <fileDesc> <titleStmt> <title>A TEI Document containing four page images </title> </titleStmt> <publicationStmt> <p>Unpublished demonstration file.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <facsimile> <graphic url="page1.png"/> <graphic url="page2.png"/> <graphic url="page3.png"/> <graphic url="page4.png"/> </facsimile> </TEI> |
| Schematron | <sch:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs" uri="http://www.w3.org/2001/XMLSchema"/> |
| Schematron | <sch:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/> <sch:ns prefix="rna" uri="http://relaxng.org/ns/compatibility/annotations/1.0"/> |
| Schematron | <sch:ns prefix="sch" uri="http://purl.oclc.org/dsdl/schematron"/> <sch:ns prefix="sch1x" uri="http://www.ascc.net/xml/schematron"/> |
| Content model | <content> |
| Schema Declaration | element TEI { att.global.attributes, att.typed.attributes, ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) ) } |
| <teiCorpus> (TEI corpus) 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. Default Text Structure 16.1. Varieties of Composite Text] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: teiCorpus | ||||||||
| May contain | |||||||||
| Note | Should contain one TEI header for the corpus, and a series of TEI elements, one for each text. | ||||||||
| Example | <teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <!-- header for corpus --> </teiHeader> <TEI> <teiHeader> <!-- header for first text --> </teiHeader> <text> <!-- content of first text --> </text> </TEI> <TEI> <teiHeader> <!-- header for second text --> </teiHeader> <text> <!-- content of second text --> </text> </TEI> <!-- more TEI elements here --> </teiCorpus> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element teiCorpus { att.global.attributes, att.typed.attributes, attribute version { teidata.version }?, ( teiHeader, model.resource*, model.describedResource+ ) } | ||||||||
| <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | header: encodingDesc fileDesc profileDesc revisionDesc |
| Note | One of the few elements unconditionally required in any TEI document. |
| Example | <teiHeader> <fileDesc> <titleStmt> <title>Shakespeare: the first folio (1623) in electronic form</title> <author>Shakespeare, William (1564–1616)</author> <respStmt> <resp>Originally prepared by</resp> <name>Trevor Howard-Hill</name> </respStmt> <respStmt> <resp>Revised and edited by</resp> <name>Christine Avern-Carr</name> </respStmt> </titleStmt> <publicationStmt> <distributor>Oxford Text Archive</distributor> <address> <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine> </address> <idno type="OTA">119</idno> <availability> <p>Freely available on a non-commercial basis.</p> </availability> <date when="1968">1968</date> </publicationStmt> <sourceDesc> <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile, 1968)</bibl> </sourceDesc> </fileDesc> <encodingDesc> <projectDesc> <p>Originally prepared for use in the production of a series of old-spelling concordances in 1968, this text was extensively checked and revised for use during the editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p> </projectDesc> <editorialDecl> <correction> <p>Turned letters are silently corrected.</p> </correction> <normalization> <p>Original spelling and typography is retained, except that long s and ligatured forms are not encoded.</p> </normalization> </editorialDecl> <refsDecl xml:id="ASLREF"> <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)" replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])"> <p>A reference is created by assembling the following, in the reverse order as that listed here: <list> <item>the <att>n</att> value of the preceding <gi>lb</gi> </item> <item>a period</item> <item>the <att>n</att> value of the ancestor <gi>div2</gi> </item> <item>a space</item> <item>the <att>n</att> value of the parent <gi>div1</gi> </item> </list> </p> </cRefPattern> </refsDecl> </encodingDesc> <revisionDesc> <list> <item> <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item> <item> <date when="1989-03-01">1 Mar 89</date> LB made new file</item> </list> </revisionDesc> </teiHeader> |
| Content model | <content> |
| Schema Declaration | element teiHeader { att.global.attributes, ( fileDesc, model.teiHeaderPart*, revisionDesc? ) } |
| <term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi index item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder keywords language licence principal sponsor linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Note | When this element appears within an index element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a gloss element by means of its ref attribute; alternatively a gloss element may point to a term element by means of its target attribute. In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The term element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the term element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release. |
| Example | A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers. |
| Example | We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> |
| Example | We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> |
| Example | We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below. |
| Content model | <content> |
| Schema Declaration | element term { att.global.attributes, att.declaring.attributes, att.pointing.attributes, att.typed.attributes, att.canonical.attributes, att.sortable.attributes, att.cReferencing.attributes, att.cmc.attributes, macro.phraseSeq } |
| <text> (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. Default Text Structure 16.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose. |
| Example | <text> <front> <docTitle> <titlePart>Autumn Haze</titlePart> </docTitle> </front> <body> <l>Is it a dragonfly or a maple leaf</l> <l>That settles softly down upon the water?</l> </body> </text> |
| Example | The body of a text may be replaced by a group of nested texts, as in the following schematic: <text> <front> <!-- front matter for the whole group --> </front> <group> <text> <!-- first text --> </text> <text> <!-- second text --> </text> </group> </text> |
| Content model | <content> |
| Schema Declaration | element text { att.global.attributes, att.declaring.attributes, att.typed.attributes, att.written.attributes, ( model.global*, ( ( front, model.global* )? ), ( body | group ), model.global*, ( ( back, model.global* )? ) ) } |
| <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. The Text Classification] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Example | <taxonomy> <category xml:id="acprose"> <catDesc>Academic prose</catDesc> </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass> <catRef target="#acprose"/> <classCode scheme="http://www.udcc.org">001.9</classCode> <keywords scheme="http://authorities.loc.gov"> <list> <item>End of the world</item> <item>History - philosophy</item> </list> </keywords> </textClass> |
| Content model | <content> |
| Schema Declaration | element textClass { att.global.attributes, att.declarable.attributes, ( classCode | catRef | keywords )* } |
| <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg resp rs sic soCalled speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder language licence principal seriesStmt sponsor titleStmt linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||||||||||||||
| May contain | |||||||||||||||||||||||
| Note | The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title. | ||||||||||||||||||||||
| Example | <title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title> | ||||||||||||||||||||||
| Example | <title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title> | ||||||||||||||||||||||
| Example | <title type="full"> <title type="main">Synthèse</title> <title type="sub">an international journal for epistemology, methodology and history of science</title> </title> | ||||||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule> | ||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||
| Schema Declaration | element title { att.global.attributes, att.typed.attribute.subtype, att.canonical.attributes, att.datable.attributes, att.cmc.attributes, attribute type { teidata.enumerated }?, attribute level { "a" | "m" | "j" | "s" | "u" }?, macro.paraContent } | ||||||||||||||||||||||
| <titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages] | |||||||||||
| Module | textstructure | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Example | <titlePage> <docTitle> <titlePart type="main">THOMAS OF Reading.</titlePart> <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart> </docTitle> <docEdition>Now the fourth time corrected and enlarged</docEdition> <byline>By T.D.</byline> <figure> <head>TP</head> <p>Thou shalt labor till thou returne to duste</p> <figDesc>Printers Ornament used by TP</figDesc> </figure> <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name> <date>1612.</date> </docImprint> </titlePage> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element titlePage { att.global.attributes, att.typed.attribute.subtype, attribute type { teidata.enumerated }?, ( model.global*, model.titlepagePart, ( model.titlepagePart | model.global )* ) } | ||||||||||
| <titlePart> (title part) contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages] | |||||||||||
| Module | textstructure | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Example | <docTitle> <titlePart type="main">THE FORTUNES AND MISFORTUNES Of the FAMOUS Moll Flanders, &c. </titlePart> <titlePart type="desc">Who was BORN in NEWGATE, And during a Life of continu'd Variety for Threescore Years, besides her Childhood, was Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof once to her own Brother) Twelve Year a <hi>Thief,</hi> Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>, at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a <hi>Penitent</hi>.</titlePart> </docTitle> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element titlePart { att.global.attributes, att.typed.attribute.subtype, attribute type { "main" | "sub" | "alt" | "short" | "desc" | teidata.enumerated }?, macro.paraContent } | ||||||||||
| <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <titleStmt> <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title> <respStmt> <resp>compiled by</resp> <name>P.J. Lucas</name> </respStmt> </titleStmt> |
| Content model | <content> |
| Schema Declaration |
element titleStmt { att.global.attributes, ( title+, model.respLike* ) } |
| <trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <trailer>Explicit pars tertia</trailer> |
| Example | <trailer> <l>In stead of FINIS this advice <hi>I</hi> send,</l> <l>Let Rogues and Thieves beware of <lb/> <hi>Hamans</hi> END.</l> </trailer> From EEBO A87070 |
| Content model | <content> |
| Schema Declaration | element trailer { att.global.attributes, att.typed.attributes, att.placement.attributes, att.written.attributes, att.cmc.attributes, ( text | lg | model.gLike | model.phrase | model.inter | model.lLike | model.global )* } |
| <unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||||||
| Module | core | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign gloss head hi item l label lg mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer | ||||||||||||||||||||
| May contain | |||||||||||||||||||||
| Note | The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility. The <damage>, gap, del, unclear and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands. | ||||||||||||||||||||
| Example | <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u> | ||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||
| Schema Declaration | element unclear { att.global.attributes, att.editLike.attributes, att.dimensions.attributes, att.cmc.attributes, attribute reason { list { ( "illegible" | "inaudible" | "faded" | "background_noise" | "eccentric_ductus" | teidata.enumerated )+ } }?, attribute agent { teidata.enumerated }?, macro.paraContent } | ||||||||||||||||||||
| <w> (word) represents a grammatical (not necessarily orthographic) word. [18.1. Linguistic Segment Categories 18.4.2. Lightweight Linguistic Annotation] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled speaker stage term time title unclear figures: cell header: change distributor edition extent licence linking: seg tagdocs: eg textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer |
| May contain | |
| Example | This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant. <l> <w lemma="it" pos="pn" xml:id="A19883-003-a-0100">IT</w> <w lemma="have" pos="vvz" xml:id="A19883-003-a-0110">hath</w> <w lemma="be" pos="vvn" xml:id="A19883-003-a-0120">been</w> <w lemma="say" pos="vvn" xml:id="A19883-003-a-0130">said</w> <w lemma="of" pos="acp-p" xml:id="A19883-003-a-0140">of</w> <w lemma="old" pos="j" xml:id="A19883-003-a-0150">old</w> <pc xml:id="A19883-003-a-0160">,</pc> <w lemma="that" pos="cs" xml:id="A19883-003-a-0170">that</w> <w lemma="play" pos="vvz" xml:id="A19883-003-a-0180"> <choice> <orig>Playes</orig> <reg>Plays</reg> </choice> </w> <w lemma="be" pos="vvb" xml:id="A19883-003-a-0190">are</w> <w lemma="feast" pos="n2" xml:id="A19883-003-a-0200">Feasts</w> <pc xml:id="A19883-003-a-0210">,</pc> </l> <l xml:id="A19883-e100220"> <w lemma="poet" pos="n2" xml:id="A19883-003-a-0220">Poets</w> <w lemma="the" pos="d" xml:id="A19883-003-a-0230">the</w> <w lemma="cook" pos="n2" xml:id="A19883-003-a-0240"> <choice> <orig>Cookes</orig> <reg>Cooks</reg> </choice> </w> <pc xml:id="A19883-003-a-0250">,</pc> <w lemma="and" pos="cc" xml:id="A19883-003-a-0260">and</w> <w lemma="the" pos="d" xml:id="A19883-003-a-0270">the</w> <w lemma="spectator" pos="n2" xml:id="A19883-003-a-0280">Spectators</w> <w lemma="guest" pos="n2" xml:id="A19883-003-a-0290">Guests</w> <pc xml:id="A19883-003-a-0300">,</pc> </l> <l xml:id="A19883-e100230"> <w lemma="the" pos="d" xml:id="A19883-003-a-0310">The</w> <w lemma="actor" pos="n2" xml:id="A19883-003-a-0320">Actors</w> <w lemma="waiter" pos="n2" xml:id="A19883-003-a-0330">Waiters</w> <pc xml:id="A19883-003-a-0340">:</pc> <!-- ... --> </l> |
| Content model | <content> |
| Schema Declaration | element w { att.global.attributes, att.segLike.attributes, att.typed.attributes, att.linguistic.attributes, att.notated.attributes, att.cmc.attributes, ( text | model.gLike | seg | w | m | c | pc | model.global | model.lPart | model.hiLike | model.pPart.edit )* } |
| model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure] | |
| Module | tei |
| Used by | |
| Members | address |
| model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses] | |
| Module | tei |
| Used by | |
| Members | model.nameLike [model.nameLike.agent [name] model.offsetLike model.placeStateLike [model.placeNamePart] idno rs] addrLine |
| model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts] | |
| Module | tei |
| Used by | |
| Members | model.quoteLike [cit] |
| model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | licence |
| model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | bibl listBibl |
| model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | model.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor funder principal respStmt sponsor] availability bibl edition extent relatedItem |
| model.choicePart groups elements (other than choice itself) which can be used within a choice alternation. [3.5. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | abbr corr expan orig reg seg sic unclear |
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.cmc model.divPart [model.lLike [l] model.pLike [p] lg sp] model.inter [model.attributable [model.quoteLike [cit] ] model.biblLike [bibl listBibl] model.egLike [eg] model.labelLike [desc label] model.listLike [list table] model.oddDecl model.stageLike [stage] ] q |
| Note | This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
| model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates] | |
| Module | tei |
| Used by | |
| Members | date time |
| model.descLike groups elements which contain a description of their function. | |
| Module | tei |
| Used by | |
| Members | desc |
| model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | TEI teiCorpus |
| model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | model.divBottomPart [closer postscript signed trailer] model.divWrapper [argument byline dateline docAuthor docDate epigraph salute] |
| model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | closer postscript signed trailer |
| model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source. | |
| Module | tei |
| Used by | |
| Members | divGen |
| model.divLike groups elements used to represent un-numbered generic structural divisions. | |
| Module | tei |
| Used by | |
| Members | div |
| model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.lLike [l] model.pLike [p] lg sp |
| Note | Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items. |
| model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | model.divTopPart [model.headLike [head] opener signed] model.divWrapper [argument byline dateline docAuthor docDate epigraph salute] |
| model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | model.headLike [head] opener signed |
| model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | argument byline dateline docAuthor docDate epigraph salute |
| model.egLike groups elements containing examples or illustrations. [23.1.1. Phrase Level Terms] | |
| Module | tei |
| Used by | |
| Members | eg |
| model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | code emph foreign gloss ident mentioned soCalled term title |
| model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | classDecl editorialDecl projectDesc refsDecl samplingDecl |
| model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ] | |
| Module | tei |
| Used by | |
| Members | model.frontPart.drama divGen listBibl titlePage |
| model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.global.edit [gap] model.global.meta [index interp interpGrp] model.milestoneLike [anchor lb milestone pb] model.noteLike [note] figure |
| model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | gap |
| model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | index interp interpGrp |
| Note | Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text. |
| model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components] | |
| Module | tei |
| Used by | |
| Members | formula graphic |
| model.headLike groups elements used to provide a title or heading at the start of a text division. | |
| Module | tei |
| Used by | |
| Members | head |
| model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | model.emphLike [code emph foreign gloss ident mentioned soCalled term title] model.hiLike [hi q] |
| model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | hi q |
| model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | biblScope distributor pubPlace publisher |
| model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.attributable [model.quoteLike [cit] ] model.biblLike [bibl listBibl] model.egLike [eg] model.labelLike [desc label] model.listLike [list table] model.oddDecl model.stageLike [stage] |
| model.labelLike groups elements used to gloss or explain other parts of a document. | |
| Module | tei |
| Used by | |
| Members | desc label |
| model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.emphLike [code emph foreign gloss ident mentioned soCalled term title] model.hiLike [hi q] model.pPart.data [model.addressLike [address] model.dateLike [date time] model.measureLike [num] model.nameLike [model.nameLike.agent [name] model.offsetLike model.placeStateLike [model.placeNamePart] idno rs] ] model.pPart.editorial [abbr choice expan] model.pPart.msdesc model.phrase.xml [att gi val] model.ptrLike [ptr ref] |
| model.listLike groups list-like elements. [3.8. Lists] | |
| Module | tei |
| Used by | |
| Members | list table |
| model.lLike groups elements representing metrical components such as verse lines. | |
| Module | tei |
| Used by | |
| Members | l |
| model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures] | |
| Module | tei |
| Used by | |
| Members | num |
| model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements] | |
| Module | tei |
| Used by | |
| Members | anchor lb milestone pb |
| model.nameLike groups elements which name or refer to a person, place, or organization. | |
| Module | tei |
| Used by | |
| Members | model.nameLike.agent [name] model.offsetLike model.placeStateLike [model.placeNamePart] idno rs |
| Note | A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
| model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | name |
| Note | This class is used in the content model of elements which reference names of people or organizations. |
| model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing] | |
| Module | tei |
| Used by | |
| Members | note |
| model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.graphicLike [formula graphic] model.highlighted [model.emphLike [code emph foreign gloss ident mentioned soCalled term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address] model.dateLike [date time] model.measureLike [num] model.nameLike [model.nameLike.agent [name] model.offsetLike model.placeStateLike [model.placeNamePart] idno rs] ] model.pPart.edit [model.pPart.editorial [abbr choice expan] model.pPart.transcriptional [add corr del orig reg sic unclear] ] model.pPart.msdesc model.phrase.xml [att gi val] model.ptrLike [ptr ref] model.segLike [pc s seg w] model.specDescLike |
| Note | This class of elements can occur within paragraphs, list items, lines of verse, etc. |
| model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [23. Documentation Elements] | |
| Module | tei |
| Used by | |
| Members | att gi val |
| model.placeStateLike groups elements which describe changing states of a place. | |
| Module | tei |
| Used by | |
| Members | model.placeNamePart |
| model.pLike groups paragraph-like elements. | |
| Module | tei |
| Used by | |
| Members | p |
| model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | argument byline dateline docAuthor docDate docEdition docImprint docTitle epigraph head titlePart |
| model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | model.addressLike [address] model.dateLike [date time] model.measureLike [num] model.nameLike [model.nameLike.agent [name] model.offsetLike model.placeStateLike [model.placeNamePart] idno rs] |
| model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | model.pPart.editorial [abbr choice expan] model.pPart.transcriptional [add corr del orig reg sic unclear] |
| model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | abbr choice expan |
| model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | add corr del orig reg sic unclear |
| model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | creation langUsage textClass |
| model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
| Module | tei |
| Used by | |
| Members | ptr ref |
| model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | authority distributor publisher |
| Note | The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element. See also model.publicationStmtPart.detail. |
| model.publicationStmtPart.detail groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | model.ptrLike [ptr ref] address availability date idno pubPlace |
| Note | A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
| model.quoteLike groups elements used to directly contain quotations. | |
| Module | tei |
| Used by | |
| Members | cit |
| model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | text |
| model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element. | |
| Module | tei |
| Used by | |
| Members | author editor funder principal respStmt sponsor |
| model.segLike groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories] | |
| Module | tei |
| Used by | |
| Members | pc s seg w |
| Note | The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the encodingDesc within the associated TEI header. |
| model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text] | |
| Module | tei |
| Used by | |
| Members | stage |
| Note | Stage directions are members of class inter: that is, they can appear between or within component-level elements. |
| model.teiHeaderPart groups high level elements which may appear more than once in a TEI header. | |
| Module | tei |
| Used by | |
| Members | encodingDesc profileDesc |
| model.titlepagePart groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | argument byline docAuthor docDate docEdition docImprint docTitle epigraph graphic imprimatur titlePart |
| att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations. | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | note | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234"> <note xml:lang="en"> Quatuor Tempora, so called dry fast days. </note> <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne. </note> </noteGrp> | ||||||||||||||||||
| att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | att.ascribed.directed [q sp stage] change | ||||||||||
| Attributes |
| ||||||||||
| att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | q sp stage | ||||||||||
| Attributes |
| ||||||||||
| att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone Elements] | |||||||||||
| Module | tei | ||||||||||
| Members | lb milestone pb | ||||||||||
| Attributes |
| ||||||||||
| att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | att.naming [att.personal [name] author editor pubPlace rs] authority catDesc date distributor docAuthor docTitle funder principal publisher resp respStmt sponsor term time title | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Example | In this contrived example, a canonical reference to the same organisation is provided in four different ways. <author n="1"> <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html" type="organisation">New Zealand Parliament, Legislative Council</name> </author> <author n="2"> <name ref="nzvn:427308" type="organisation">New Zealand Parliament, Legislative Council</name> </author> <author n="3"> <name ref="./named_entities.xml#o427308" type="organisation">New Zealand Parliament, Legislative Council</name> </author> <author n="4"> <name key="name-427308" type="organisation">New Zealand Parliament, Legislative Council</name> </author> The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the | ||||||||||||||||||||
| Note | The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange. These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange. | ||||||||||||||||||||
| att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | biblScope | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment. | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | abbr add address anchor argument bibl byline choice cit closer corr date dateline del desc docAuthor docDate emph epigraph expan figure foreign formula gap gloss graphic head hi idno index interp interpGrp l label lb lg list listBibl mentioned milestone name note num opener orig p pb pc postscript ptr q ref reg rs s salute seg sic signed soCalled stage table term time title trailer unclear w | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer. | |||||||||
| Module | tei | ||||||||
| Members | gloss ptr ref term | ||||||||
| Attributes |
| ||||||||
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates] | |||||||
| Module | tei | ||||||
| Members | author change creation date docDate editor funder idno licence name principal resp sponsor time title | ||||||
| Attributes |
| ||||||
| Note | This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. | ||||||
| att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates] | |||||||||||||
| Module | tei | ||||||||||||
| Members | att.datable [author change creation date docDate editor funder idno licence name principal resp sponsor time title] | ||||||||||||
| Attributes |
| ||||||||||||
| Schematron | <sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to" role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule> | ||||||||||||
| Schematron | <sch:rule context="tei:*[@from]"> <sch:report test="@notBefore" role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule> | ||||||||||||
| Schematron | <sch:rule context="tei:*[@to]"> <sch:report test="@notAfter" role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule> | ||||||||||||
| Example | <date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date> | ||||||||||||
| Note | The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar. The most commonly-encountered format for the date portion of a temporal attribute is Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used. | ||||||||||||
| att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [10.5.2. Lexical View 19.3. Other Atomic Feature Values] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | att.segLike [pc s seg w] category taxonomy | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | The example below presents the TEI encoding of the name-value pair The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology. <fs> <f name="POS" datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"> <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545" value="NN"/> </f> <!-- ... --> </fs> ‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun. While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry. If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [ID FS in TEI Guidelines]. <fs> <f name="POS" fVal="#commonNoun"/> <!-- ... --> </fs> The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of text or a child of encodingDesc; a taxonomy available resource-wide (e.g., in a shared header) is also an option. The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories. <fvLib n="POS values"> <symbol xml:id="commonNoun" value="NN" datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/> <symbol xml:id="properNoun" value="NP" datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </fvLib> Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value. | ||||||||||||||||||
| Example | In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above. <gramGrp> <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp> Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>: <tagsDecl partial="true"> <!-- ... --> <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="pos" targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage> <tagUsage gi="case" targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... --> </namespace> </tagsDecl> Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below: <listPrefixDef> <prefixDef ident="ccr" matchPattern="pos" replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/> <prefixDef ident="ccr" matchPattern="adj" replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...--> <form> <orth>isotope</orth> </form> <gramGrp> <pos datcat="ccr:pos" valueDatcat="ccr:adj">adj</pos> </gramGrp> <!--...--> </entry> This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised. Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>. | ||||||||||||||||||
| Example | The taxonomy element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local taxonomy element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the taxonomy creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the category elements stored in the header (as well as the taxonomy element itself), whereas these same category and taxonomy elements use att.datcat attributes to reference the original taxonomy or ontology. <encodingDesc> <!-- ... --> <classDecl> <!-- ... --> <taxonomy xml:id="UD-SYN" datcat="https://universaldependencies.org/u/dep/index.html"> <desc> <term>UD syntactic relations</term> </desc> <category xml:id="acl" valueDatcat="https://universaldependencies.org/u/dep/acl.html"> <catDesc> <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc> </category> <category xml:id="acl_relcl" valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"> <catDesc> <term>acl:relcl</term>: relative clause modifier</catDesc> </category> <category xml:id="advcl" valueDatcat="https://universaldependencies.org/u/dep/advcl.html"> <catDesc> <term>advcl</term>: Adverbial clause modifier</catDesc> </category> <!-- ... --> </taxonomy> </classDecl> </encodingDesc> The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here. Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on taxonomy on the one hand, and the valueDatcat used on category on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly. | ||||||||||||||||||
| Example | The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object. <fDecl name="POS" targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"> <fDescr>part of speech (morphosyntactic category)</fDescr> <vRange> <vAlt> <symbol value="NN" datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/> <symbol value="NP" datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </vAlt> </vRange> </fDecl> Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element. | ||||||||||||||||||
| Example | The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project. <!-- in the dictionary header --><encodingDesc> <classDecl> <taxonomy xml:id="domains"> <!--...--> <category xml:id="domain.medical_and_health_sciences"> <catDesc xml:lang="en">Medical and Health Sciences</catDesc> <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc> <category xml:id="domain.medical_and_health_sciences.medicine" valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"> <catDesc xml:lang="en"> <term>Medicine</term> <gloss> <!--...--> </gloss> </catDesc> <catDesc xml:lang="pt"> <term>Medicina</term> <gloss> <!--...--> </gloss> </catDesc> </category> </category> <!--...--> </taxonomy> </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain" valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg> In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH). | ||||||||||||||||||
| Note | The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container. A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute. In a TEI XML example of two equivalent serializations expressing the name-value pair The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech). The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects. Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example. Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices. | ||||||||||||||||||
| att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [16.3. Associating Contextual Information with a Text] | |||||||||
| Module | tei | ||||||||
| Members | availability bibl editorialDecl langUsage listBibl projectDesc refsDecl samplingDecl seriesStmt sourceDesc textClass | ||||||||
| Attributes |
| ||||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true. | ||||||||
| 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. [16.3. Associating Contextual Information with a Text] | |||||||
| Module | tei | ||||||
| Members | back body div front gloss graphic group lg p ptr ref term text | ||||||
| Attributes |
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. | ||||||
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | add date del gap time unclear | ||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
| att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | div lg | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
| Module | tei | ||||||||
| Members | bibl change revisionDesc | ||||||||
| Attributes |
| ||||||||
| Example | <revisionDesc status="published"> <change when="2010-10-21" status="published"/> <change when="2010-10-02" status="cleared"/> <change when="2010-08-02" status="embargoed"/> <change when="2010-05-01" status="frozen" who="#MSM"/> <change when="2010-03-01" status="draft" who="#LB"/> </revisionDesc> | ||||||||
| att.edition provides attributes identifying the source edition from which some encoded feature derives. | |||||||||||||
| Module | tei | ||||||||||||
| Members | lb milestone pb | ||||||||||||
| Attributes |
| ||||||||||||
| Example | <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> | ||||||||||||
| Example | <listBibl> <bibl xml:id="stapledon1937"> <author>Olaf Stapledon</author>, <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date> </bibl> <bibl xml:id="stapledon1968"> <author>Olaf Stapledon</author>, <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date> </bibl> </listBibl> <!-- ... --> <p>Looking into the future aeons from the supreme moment of the cosmos, I saw the populations still with all their strength maintaining the<pb n="411" edRef="#stapledon1968"/>essentials of their ancient culture, still living their personal lives in zest and endless novelty of action, … I saw myself still preserving, though with increasing difficulty, my lucid con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p> | ||||||||||||
| att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | att.transcriptional [add del] corr date expan gap name reg time unclear | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Note | The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc. Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or bibl element, or another external bibliographic citation, documenting the source concerned. | ||||||||||||||||
| att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy. | |||||||||||
| Module | tei | ||||||||||
| Members | att.divLike [div lg] att.segLike [pc s seg w] l p | ||||||||||
| Attributes |
| ||||||||||
| att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||
| Members | TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w | ||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||
| att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [12.1. Digital Facsimiles] | |||||||
| Module | transcr | ||||||
| Members | att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w] | ||||||
| Attributes |
| ||||||
| att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||
| Members | att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w] | ||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||
| att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators] | |||||||||||
| Module | tei | ||||||||||
| Members | att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w] | ||||||||||
| Attributes |
| ||||||||||
| att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w] | ||||||||||||||
| Attributes |
| ||||||||||||||
| Example | Blessed are the <choice> <sic>cheesemakers</sic> <corr resp="#editor" cert="high">peacemakers</corr> </choice>: for they shall be called the children of God. | ||||||||||||||
| Example | <!-- in the <text> ... --><lg> <!-- ... --> <l>Punkes, Panders, baſe extortionizing sla<choice> <sic>n</sic> <corr resp="#JENS1_transcriber">u</corr> </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber"> <resp when="2014">Transcriber</resp> <name>Janelle Jenstad</name> </respStmt> | ||||||||||||||
| att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing] | |||||||||||
| Module | tei | ||||||||||
| Members | att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w] | ||||||||||
| Attributes |
| ||||||||||
| Example | <p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested term.</quote> <!-- ... --> </p> | ||||||||||
| Example | <p> <!-- ... --> <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed"> <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl> | ||||||||||
| Example | <elementRef key="p" source="tei:2.0.1"/> Include in the schema an element named p available from the TEI P5 2.0.1 release. | ||||||||||
| Example | <schemaSpec ident="myODD" source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec> Create a schema using components taken from the file mycompiledODD.xml. | ||||||||||
| att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [18.2. Global Attributes for Simple Analyses] | |||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||
| Members | interp interpGrp | ||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||
| att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. | |||||||||||||||||||||||||||||||
| Module | analysis | ||||||||||||||||||||||||||||||
| Members | att.linguistic [pc w] | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Note | It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on choice, orig, and reg needs to be employed. | ||||||||||||||||||||||||||||||
| att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. [18.4.2. Lightweight Linguistic Annotation] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | analysis | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | pc w | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Note | These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 18.4.2. Lightweight Linguistic Annotation for discussion. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.media provides attributes for specifying display and related properties of external media. | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | graphic | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| att.milestoneUnit provides attributes to indicate the type of section which is changing at a specific milestone. [3.11.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration] | |||||||||||||
| Module | core | ||||||||||||
| Members | milestone | ||||||||||||
| Attributes |
| ||||||||||||
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.personal [name] author editor pubPlace rs | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.notated provides attributes to indicate any specialised notation used for element content. | |||||||
| Module | tei | ||||||
| Members | formula s seg w | ||||||
| Attributes |
| ||||||
| 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. [14.2.1. Personal Names] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | name | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 12.3.1.4. Additions and Deletions] | |||||||||||||
| Module | tei | ||||||||||||
| Members | add figure head label note stage trailer | ||||||||||||
| Attributes |
| ||||||||||||
| att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References] | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | catRef gloss licence note ptr ref term | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | att.dimensions [add date del gap time unclear] num | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Example | The MS. was lost in transmission by mail from <del rend="overstrike"> <gap reason="illegible" extent="one or two letters" atLeast="1" atMost="2" unit="chars"/> </del> Philadelphia to the Graphic office, New York. | ||||||||||||||||||||||||||||||
| Example | Americares has been supporting the health sector in Eastern Europe since 1986, and since 1992 has provided <measure atLeast="120000000" unit="USD" commodity="currency">more than $120m</measure> in aid to Ukrainians. | ||||||||||||||||||||||||||||||
| att.resourced provides attributes by which a resource (such as an externally held media file) may be located. | |||||||
| Module | tei | ||||||
| Members | graphic | ||||||
| Attributes |
| ||||||
| att.segLike provides attributes for elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories] | |||||||||
| Module | tei | ||||||||
| Members | pc s seg w | ||||||||
| Attributes |
| ||||||||
| 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. [10.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei | ||||||||||
| Members | bibl idno item list listBibl term | ||||||||||
| Attributes |
| ||||||||||
| att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [12.3.1.4. Additions and Deletions 1.3.1. Attribute Classes] | |||||||||
| Module | tei | ||||||||
| Members | index lb milestone pb | ||||||||
| Attributes |
| ||||||||
| Note | The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself. | ||||||||
| att.tableDecoration provides attributes used to decorate rows or cells of a table. [15. Tables, Formulæ, Graphics, and Notated Music] | |||||||||||||||||||||||||||||||
| Module | figures | ||||||||||||||||||||||||||||||
| Members | cell row | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | gap | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [12.3.1.4. Additions and Deletions] | |||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||
| Members | add del | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document. | |||||||||
| Module | tagdocs | ||||||||
| Members | desc gloss | ||||||||
| Attributes |
| ||||||||
| att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | TEI abbr add anchor bibl change cit corr date del desc div divGen figure gloss graphic group head ident idno label lb lg list listBibl milestone name note num pb pc ptr ref reg relatedItem rs s seg table teiCorpus term text time title titlePage titlePart trailer w | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule> | ||||||||||||||||||
| Note | When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
| att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes] | |||||||
| Module | tei | ||||||
| Members | att.transcriptional [add del] closer div figure head hi label note opener p postscript salute seg signed stage text trailer | ||||||
| Attributes |
| ||||||
| teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.certainty = "high" | "medium" | "low" | "unknown" |
| Note | Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. |
| teidata.count defines the range of attribute values used for a non-negative integer value used as a count. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.count = xsd:nonNegativeInteger |
| Note | Any positive integer value or zero is permitted |
| teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" } |
| Example | <time dur-iso="PT0,75H">three-quarters of an hour</time> |
| Example | <date dur-iso="P1,5D">a day and a half</date> |
| Example | <date dur-iso="P14D">a fortnight</date> |
| Example | <time dur-iso="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
| teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.duration.w3c = xsd:duration |
| Example | <time dur="PT45M">forty-five minutes</time> |
| Example | <date dur="P1DT12H">a day and a half</date> |
| Example | <date dur="P7D">a week</date> |
| Example | <time dur="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the For complete details, see the W3C specification. |
| teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.enumerated = teidata.word |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
| teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration | teidata.language = xsd:language | ( "" ) |
| Note | The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice. A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications. Second, an entire language tag can consist of only a private use subtag. These tags start with Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
| teidata.name defines the range of attribute values expressed as an XML Name. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.name = xsd:Name |
| Note | Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
| teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
teidata.namespace = xsd:anyURI { pattern = "\S+" } |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax |
| teidata.numeric defines the range of attribute values used for numeric values. | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration |
teidata.numeric =
xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal |
| Note | Any numeric value, represented as a decimal number, in floating point format, or as a ratio. To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3. A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2. |
| teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.outputMeasurement = token { pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)" } |
| Example | <figure> <head>The TEI Logo</head> <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in between and <mentioned>text encoding initiative</mentioned> underneath, all on a white background.</figDesc> <graphic height="600px" width="600px" url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure> |
| Note | These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft. |
| teidata.pattern defines attribute values which are expressed as a regular expression. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.pattern = token |
| Note | A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern Wikipedia H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema. |
| teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration |
teidata.pointer = xsd:anyURI { pattern = "\S+" } |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, |
| teidata.probability defines the range of attribute values expressing a probability. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.probability = xsd:double |
| Note | Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. |
| teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.probCert = teidata.probability | teidata.certainty |
| teidata.replacement defines attribute values which contain a replacement template. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.replacement = text |
| teidata.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 Second Edition specification. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
| teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
teidata.temporal.working =
xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
| xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" } |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z. |
| teidata.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. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.text = string |
| Note | Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
| teidata.truthValue defines the range of attribute values used to express a truth value. | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration | teidata.truthValue = xsd:boolean |
| Note | The possible values of this datatype are 1 or true, or 0 or false. This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue. |
| teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" ) |
| teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration |
teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" } |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
| teidata.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
teidata.versionNumber =
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" } |
| teidata.word defines the range of attribute values expressed as a single word or token. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
teidata.word = token { pattern = "[^\p{C}\p{Z}]+" } |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
| teidata.xmlName defines attribute values which contain an XML name. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.xmlName = xsd:NCName |
| Note | The rules defining an XML name form a part of the XML Specification. |
| teidata.xpath defines attribute values which contain an XPath expression. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.xpath = text |
| Note | Any XPath expression using the syntax defined in 6.2. . When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP. |
| teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" ) |
| Note | In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
| macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | macro.limitedContent = ( text | model.limitedPhrase | model.inter )* |
| macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | macro.paraContent = ( text | model.paraPart )* |
| macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | macro.phraseSeq = ( text | model.gLike | model.attributable | model.phrase | model.global )* |
| 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. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )* |
| 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. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
macro.specialPara =
(
text
| model.gLike
| model.phrase
| model.inter
| model.divPart
| model.global
)* |
http://www.tei-c.org/ns/1.0