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 <category>s, 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.
| <ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [16.3. Blocks, Segments, and Anchors] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | header: availability change correspAction correspDesc editorialDecl encodingDesc handNote licence normalization projectDesc publicationStmt sourceDesc linking: ab msdescription: accMat acquisition binding bindingDesc collation decoNote filiation foliation handDesc history layout layoutDesc msContents msDesc msItem msItemStruct objectDesc physDesc provenance support supportDesc textcrit: rdg transcr: metamark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Note | The ab element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. Unlike paragraphs, ab may nest and may use the type and subtype attributes. |
| Example | <div n="Genesis" type="book"> <div n="1" type="chapter"> <ab>In the beginning God created the heaven and the earth.</ab> <ab>And the earth was without form, and void; and darkness was upon the face of the deep. And the spirit of God moved upon the face of the waters.</ab> <ab>And God said, Let there be light: and there was light.</ab> <!-- ...--> </div> </div> |
| Schematron | <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 divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText. </sch:report> |
| Content model | <content> |
| Schema Declaration | element ab { tei_att.global.attributes, tei_att.typed.attributes, tei_att.declaring.attributes, tei_att.fragmentable.attributes, tei_att.written.attributes, tei_macro.abContent } |
| <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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme | ||||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||
| 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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, attribute type { teidata.enumerated }?, tei_macro.phraseSeq } | ||||||||||||
| <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <accMat>A copy of a tax form from 1947 is included in the envelope with the letter. It is not catalogued separately.</accMat> |
| Content model | <content> |
| Schema Declaration | element accMat { tei_att.global.attributes, tei_att.typed.attributes, tei_macro.specialPara } |
| <acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History] | |||||||||||
| Module | msdescription | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: history | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Example | <acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element acquisition { tei_att.global.attributes, tei_att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, tei_macro.specialPara } | ||||||||||
| <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 head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.placement.attributes, tei_att.typed.attributes, tei_att.dimensions.attributes, tei_macro.paraContent } |
| <addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <persName> <forename>Frederick</forename> <addName type="epithet">the Great</addName> <roleName>Emperor of Prussia</roleName> </persName> |
| Content model | <content> |
| Schema Declaration | element addName { tei_att.global.attributes, tei_att.personal.attributes, tei_att.typed.attributes, tei_macro.phraseSeq } |
| <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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| 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 { tei_att.global.attributes, ( tei_model.global*, ( tei_model.addrPart, tei_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 | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_macro.phraseSeq } |
| <addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also add). [11.3.1.4. Additions and Deletions] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| May contain | Empty element |
| Note | Both the beginning and the end of the added material must be marked; the beginning by the addSpan element itself, the end by the spanTo attribute. |
| Example | <handNote scribe="HelgiÓlafsson" xml:id="HEOL"/> <!-- ... --> <body> <div> <!-- text here --> </div> <addSpan hand="#HEOL" n="added_gathering" spanTo="#P025"/> <div> <!-- text of first added poem here --> </div> <div> <!-- text of second added poem here --> </div> <div> <!-- text of third added poem here --> </div> <div> <!-- text of fourth added poem here --> </div> <anchor xml:id="P025"/> <div> <!-- more text here --> </div> </body> |
| Schematron | <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> |
| Schematron | <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> |
| Content model | <content> |
| Schema Declaration | element addSpan { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.placement.attributes, tei_att.typed.attributes, tei_att.spanning.attributes, tei_att.dimensions.attributes, empty } |
| <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | |
| Example | do you <abbr>Mr<am>.</am> </abbr> Jones? |
| Example | <choice> <abbr>Aug<am>g</am> </abbr> <expan>Aug<ex>ustorum duo</ex> </expan> </choice> |
| Example | <abbr>eu<am> <g ref="#b-er"/> </am>y</abbr> <abbr> <am> <g ref="#b-per"/> </am>sone </abbr> ... |
| Content model | <content> |
| Schema Declaration | element am { tei_att.global.attributes, tei_att.typed.attributes, tei_att.editLike.attributes, ( text | tei_model.gLike | tei_model.pPart.transcriptional )* } |
| <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 16.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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| 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 { tei_att.global.attributes, tei_att.typed.attributes, empty } |
| <app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [12.1.1. The Apparatus Entry] | |||||||||||||||||||||||||||||||||
| Module | textcrit | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||
| Example | <app> <lem wit="#El #Hg">Experience</lem> <rdg type="substantive" wit="#La">Experiment</rdg> <rdg type="substantive" wit="#Ra2">Eryment</rdg> </app> | ||||||||||||||||||||||||||||||||
| Example | <app type="substantive"> <rdgGrp type="subvariants"> <lem wit="#El #Hg">Experience</lem> <rdg wit="#Ha4">Experiens</rdg> </rdgGrp> <rdgGrp type="subvariants"> <lem wit="#Cp #Ld1">Experiment</lem> <rdg wit="#La">Ex<g ref="#per"/>iment</rdg> </rdgGrp> <rdgGrp type="subvariants"> <lem resp="#ed2013">Eriment</lem> <rdg wit="#Ra2">Eryment</rdg> </rdgGrp> </app> | ||||||||||||||||||||||||||||||||
| Example | <app loc="1"> <rdg resp="#SEG">TIMΩΔA</rdg> </app> | ||||||||||||||||||||||||||||||||
| Example | <app loc="1-6"> <note>Too badly worn to yield a text</note> </app> | ||||||||||||||||||||||||||||||||
| Example | <choice xml:id="choice3"> <reg>σύμπαντα</reg> <orig>ΣΙΝΠΑΤΑΝ</orig> </choice> <!-- ... --> <app from="#choice3"> <note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note> </app> | ||||||||||||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||||||||||||
| Schema Declaration | element app { tei_att.global.attributes, tei_att.typed.attribute.subtype, attribute type { teidata.enumerated }?, attribute from { teidata.pointer }?, attribute to { teidata.pointer }?, attribute loc { list { teidata.word+ } }?, ( lem?, ( tei_model.rdgLike | tei_model.noteLike | tei_witDetail | tei_wit | tei_rdgGrp )* ) } | ||||||||||||||||||||||||||||||||
| <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 | |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.naming.attributes, tei_att.datable.attributes, tei_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 | core: monogr header: publicationStmt |
| May contain | |
| Example | <authority>John Smith</authority> |
| Content model | <content> |
| Schema Declaration | element authority { tei_att.global.attributes, tei_att.canonical.attributes, tei_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 | 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 { tei_att.global.attributes, tei_att.declarable.attributes, attribute status { "free" | "unknown" | "restricted" }?, ( tei_model.availabilityPart | tei_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 | |
| 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 { tei_att.global.attributes, tei_att.declaring.attributes, ( ( tei_model.frontPart | tei_model.pLike.front | tei_model.pLike | tei_model.listLike | tei_model.global )*, ( ( tei_model.div1Like, ( tei_model.frontPart | tei_model.div1Like | tei_model.global )* ) | ( tei_model.divLike, ( tei_model.frontPart | tei_model.divLike | tei_model.global )* ) )?, ( tei_model.divBottomPart, ( tei_model.divBottomPart | tei_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 15.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address author bibl biblScope choice corr date del editor emph expan foreign gap gb hi index lb measure milestone note num orig pb ptr pubPlace publisher q ref reg relatedItem rs sic soCalled term title unclear header: availability distributor extent idno msdescription: decoNote msIdentifier transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo character data |
| 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 subtype="book_chapter" type="article" 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 { tei_att.global.attributes, tei_att.declarable.attributes, tei_att.typed.attributes, tei_att.sortable.attributes, tei_att.docStatus.attributes, ( text | tei_model.gLike | tei_model.highlighted | tei_model.pPart.data | tei_model.pPart.edit | tei_model.segLike | tei_model.ptrLike | tei_model.biblPart | tei_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 | |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 from="12" to="34" unit="page"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope> |
| Content model | <content> |
| Schema Declaration | element biblScope { tei_att.global.attributes, tei_att.citing.attributes, tei_macro.phraseSeq } |
| <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: monogr note ptr ref relatedItem |
| Example | <biblStruct> <monogr> <author>Blain, Virginia</author> <author>Clements, Patricia</author> <author>Grundy, Isobel</author> <title>The Feminist Companion to Literature in English: women writers from the middle ages to the present</title> <edition>first edition</edition> <imprint> <publisher>Yale University Press</publisher> <pubPlace>New Haven and London</pubPlace> <date>1990</date> </imprint> </monogr> </biblStruct> |
| Example | <biblStruct type="newspaper"> <analytic> <author> <forename>David</forename> <surname>Barstow</surname> </author> <author> <forename>Susanne</forename> <surname>Craig</surname> </author> <author> <forename>Russ</forename> <surname>Buettner</surname> </author> <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title> <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title> </analytic> <monogr> <title level="j">The New York Times</title> <imprint> <pubPlace>New York</pubPlace> <publisher>A. G. Sulzberger</publisher> <date when="2018-10-03">Wednesday, October 3, 2018</date> </imprint> <biblScope unit="volume">CLXVIII</biblScope> <biblScope unit="issue">58,104</biblScope> <biblScope unit="page">1</biblScope> </monogr> </biblStruct> |
| Content model | <content> |
| Schema Declaration | element biblStruct { tei_att.global.attributes, tei_att.declarable.attributes, tei_att.typed.attributes, tei_att.sortable.attributes, tei_att.docStatus.attributes, ( analytic*, ( tei_monogr, series* )+, ( tei_model.noteLike | tei_model.ptrLike | tei_relatedItem | citedRange )* ) } |
| <binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions] | |||||||||||||||||||
| Module | msdescription | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Contained by | msdescription: bindingDesc | ||||||||||||||||||
| May contain | |||||||||||||||||||
| Example | <binding contemporary="true"> <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp closing to the back cover.</p> </binding> | ||||||||||||||||||
| Example | <bindingDesc> <binding contemporary="false"> <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front pastedown.</p> </binding> <binding contemporary="false"> <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p> </binding> </bindingDesc> | ||||||||||||||||||
| Content model | <content> | ||||||||||||||||||
| Schema Declaration | element binding { tei_att.global.attributes, tei_att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, attribute contemporary { teidata.xTruthValue }?, ( tei_model.pLike | condition | tei_decoNote )+ } | ||||||||||||||||||
| <bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct binding elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Example | <bindingDesc> <p>Sewing not visible; tightly rebound over 19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with gilt tooling à la fanfare, Paris c. 1580-90, the centre of each cover inlaid with a 17th-cent. oval medallion of red morocco tooled in gilt (perhaps replacing the identifying mark of a previous owner); the spine similarly tooled, without raised bands or title-piece; coloured endbands; the edges of the leaves and boards gilt.Boxed.</p> </bindingDesc> |
| Content model | <content> |
| Schema Declaration | element bindingDesc { tei_att.global.attributes, ( ( tei_model.pLike | tei_decoNote | condition )+ | tei_binding+ ) } |
| <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 { tei_att.global.attributes, tei_att.declaring.attributes, ( tei_model.global*, ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )?, ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?, ( ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+ | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+ | ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+, ( ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+ | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+ )? ) ), ( tei_model.divBottom, tei_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 | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno textstructure: docAuthor transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, ( text | tei_model.gLike | tei_model.phrase | tei_docAuthor | tei_model.global )* } |
| <c> (character) represents a character. [17.1. Linguistic Segment Categories] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | Character data only |
| Note | Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc. |
| Example | <phr> <c>M</c> <c>O</c> <c>A</c> <c>I</c> <w>doth</w> <w>sway</w> <w>my</w> <w>life</w> </phr> |
| Content model | <content> |
| Schema Declaration | element c { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.notated.attributes, tei_macro.xtext } |
| <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 11.7. Identifying Changes and Revisions] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: listChange revisionDesc | ||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||
| 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 status="public" when="2008-02-02" who="#BZ">Finished chapter 23</change> <change status="draft" when="2008-01-02" who="#BZ">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 notBefore="1880-12-09" xml:id="DRAFT2">First revision, mostly using green ink</change> <change notBefore="1881-02-13" xml:id="DRAFT3">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 { tei_att.ascribed.attributes, tei_att.datable.attributes, tei_att.docStatus.attributes, tei_att.global.attributes, tei_att.typed.attributes, attribute target { list { teidata.pointer+ } }?, tei_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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| 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 12.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 { tei_att.global.attributes, ( tei_model.choicePart | tei_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 9.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| 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 { tei_att.global.attributes, tei_att.typed.attributes, ( tei_model.biblLike | tei_model.egLike | tei_model.entryPart | tei_model.global | tei_model.graphicLike | tei_model.ptrLike | tei_model.attributable | tei_pc | tei_q )+ } |
| <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 | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.written.attributes, ( text | tei_model.gLike | tei_signed | tei_dateline | tei_salute | tei_model.phrase | tei_model.global )* } |
| <collation> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [10.7.1. Object Description] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <collation>The written leaves preceded by an original flyleaf, conjoint with the pastedown.</collation> |
| Example | <collation> <p> <formula>1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula> <catchwords>Catchwords are written horizontally in center or towards the right lower margin in various manners: in red ink for quires 1-6 (which are also signed in red ink with letters of the alphabet and arabic numerals); quires 7-9 in ink of text within yellow decorated frames; quire 10 in red decorated frame; quire 12 in ink of text; quire 13 with red decorative slashes; quire 14 added in cursive hand.</catchwords> </p> </collation> |
| Content model | <content> |
| Schema Declaration |
element collation { tei_att.global.attributes, tei_macro.specialPara } |
| <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 head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.typed.attributes, tei_macro.paraContent } |
| <correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description] | |||||||||||
| Module | header | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | header: correspDesc | ||||||||||
| May contain | |||||||||||
| Example | <correspAction type="sent"> <persName>Adelbert von Chamisso</persName> <settlement>Vertus</settlement> <date when="1807-01-29"/> </correspAction> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element correspAction { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.sortable.attributes, attribute type { "sent" | "received" | "transmitted" | "redirected" | "forwarded" | teidata.enumerated }?, ( tei_model.correspActionPart+ | tei_model.pLike+ ) } | ||||||||||
| <correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Example | <correspDesc> <correspAction type="sent"> <persName>Carl Maria von Weber</persName> <settlement>Dresden</settlement> <date when="1817-06-23">23 June 1817</date> </correspAction> <correspAction type="received"> <persName>Caroline Brandt</persName> <settlement>Prag</settlement> </correspAction> <correspContext> <ref target="http://www.weber-gesamtausgabe.de/A041209" type="prev">Previous letter of <persName>Carl Maria von Weber</persName> to <persName>Caroline Brandt</persName>: <date from="1817-06-19" to="1817-06-20">June 19/20, 1817</date> </ref> <ref target="http://www.weber-gesamtausgabe.de/A041217" type="next">Next letter of <persName>Carl Maria von Weber</persName> to <persName>Caroline Brandt</persName>: <date when="1817-06-27">June 27, 1817</date> </ref> </correspContext> </correspDesc> |
| Content model | <content> |
| Schema Declaration | element correspDesc { tei_att.declarable.attributes, tei_att.canonical.attributes, tei_att.global.attributes, tei_att.typed.attributes, ( tei_model.correspDescPart+ | tei_model.pLike+ ) } |
| <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 { tei_att.global.attributes, tei_att.datable.attributes, ( text | tei_model.limitedPhrase | tei_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 15.2.3. The Setting Description 13.4. Dates] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi imprint item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.canonical.attributes, tei_att.datable.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, tei_att.typed.attributes, ( text | tei_model.gLike | tei_model.phrase | tei_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 | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, ( text | tei_model.gLike | tei_model.phrase | tei_model.global | docDate )* } |
| <decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | core: bibl msdescription: binding bindingDesc msItemStruct |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <decoDesc> <decoNote type="initial"> <p>The start of each book of the Bible with a 10-line historiated illuminated initial; prefaces decorated with 6-line blue initials with red penwork flourishing; chapters marked by 3-line plain red initials; verses with 1-line initials, alternately blue or red.</p> </decoNote> </decoDesc> |
| Content model | <content> |
| Schema Declaration | element decoNote { tei_att.global.attributes, tei_att.typed.attributes, tei_macro.specialPara } |
| <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 head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 21. 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 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.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 quantity="5" reason="illegible" unit="character"/> </del> |
| Content model | <content> |
| Schema Declaration | element del { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.typed.attributes, tei_att.dimensions.attributes, tei_macro.paraContent } |
| <delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. Additions and Deletions] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| May contain | Empty element |
| Note | Both the beginning and ending of the deleted sequence must be marked: the beginning by the delSpan element, the ending by the target of the spanTo attribute. The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the delSpan tag should not be used. Rather, the gap tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the unclear element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the delSpan tag with the gap, <damage>, unclear and supplied elements, 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination. The delSpan tag should not be used for deletions made by editors or encoders. In these cases, either the corr tag or the gap tag should be used. |
| Example | <p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p> |
| Schematron | <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> |
| Schematron | <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> |
| Content model | <content> |
| Schema Declaration | element delSpan { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.typed.attributes, tei_att.spanning.attributes, tei_att.dimensions.attributes, empty } |
| <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. [22.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 ident="teidata.point" module="tei"> <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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, attribute type { "deprecationInfo" | teidata.enumerated }?, tei_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 | header: publicationStmt |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <distributor>Oxford Text Archive</distributor> <distributor>Redwood and Burn Ltd</distributor> |
| Content model | <content> |
| Schema Declaration | element distributor { tei_att.global.attributes, tei_att.canonical.attributes, tei_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: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> |
| Schematron | <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> |
| Content model | <content> |
| Schema Declaration | element div { tei_att.global.attributes, tei_att.divLike.attributes, tei_att.typed.attributes, tei_att.declaring.attributes, tei_att.written.attributes, ( ( tei_model.divTop | tei_model.global )*, ( ( ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )+ | ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+, ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )* ) ), ( tei_model.divBottom, tei_model.global* )* )? ) } |
| <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 | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.canonical.attributes, tei_macro.phraseSeq } |
| <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 | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr pubPlace publisher q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, ( text | tei_model.gLike | tei_model.phrase | tei_pubPlace | docDate | tei_publisher | tei_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 { tei_att.global.attributes, tei_att.canonical.attributes, ( tei_model.global*, ( tei_titlePart, tei_model.global* )+ ) } |
| <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 | |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.naming.attributes, tei_att.datable.attributes, tei_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 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| 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 { tei_att.global.attributes, tei_att.declarable.attributes, tei_model.pLike+ } |
| <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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_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 | |
| 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 { tei_att.global.attributes, ( tei_model.encodingDescPart | tei_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 { tei_att.global.attributes, ( tei_model.common | tei_model.global )* } |
| <ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | Character data only |
| Example | The address is Southmoor <choice> <expan>R<ex>oa</ex>d</expan> <abbr>Rd</abbr> </choice> |
| Content model | <content> |
| Schema Declaration | element ex { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, tei_macro.xtext } |
| <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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.editLike.attributes, tei_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 10.7.1. Object Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 quantity="4.2" unit="MiB">About four megabytes</measure> <measure quantity="245" unit="pages">245 pages of source material</measure> </extent> |
| Content model | <content> |
| Schema Declaration |
element extent { tei_att.global.attributes, tei_macro.phraseSeq } |
| <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | textstructure: TEI |
| May contain | |
| Example | <facsimile> <graphic url="page1.png"/> <surface> <graphic url="page2-highRes.png"/> <graphic url="page2-lowRes.png"/> </surface> <graphic url="page3.png"/> <graphic url="page4.png"/> </facsimile> |
| Example | <facsimile> <surface lrx="200" lry="300" ulx="0" uly="0"> <graphic url="Bovelles-49r.png"/> </surface> </facsimile> |
| Schematron | <sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone"> <sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus transcribed text should not be present within it. </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element facsimile { tei_att.global.attributes, tei_att.declaring.attributes, ( tei_front?, ( tei_model.graphicLike | tei_surface | surfaceGrp )+, tei_back? ) } |
| <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 { tei_att.global.attributes, ( ( tei_titleStmt, editionStmt?, tei_extent?, tei_publicationStmt, seriesStmt*, tei_notesStmt? ), tei_sourceDesc+ ) } |
| <filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msItemStruct |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <msContents> <msItem> <title>Beljakovski sbornik</title> <filiation type="protograph">Bulgarian</filiation> <filiation type="antigraph">Middle Bulgarian</filiation> <filiation type="apograph"> <ref target="#DN17">Dujchev N 17</ref> </filiation> </msItem> </msContents> <!-- ... --> <msDesc xml:id="DN17"> <msIdentifier> <settlement>Faraway</settlement> </msIdentifier> <!-- ... --> </msDesc> In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier |
| Example | <msItem> <title>Guan-ben</title> <filiation> <p>The "Guan-ben" was widely current among mathematicians in the Qing dynasty, and "Zhao Qimei version" was also read. It is therefore difficult to know the correct filiation path to follow. The study of this era is much indebted to Li Di. We explain the outline of his conclusion here. Kong Guangsen (1752-1786)(17) was from the same town as Dai Zhen, so he obtained "Guan-ben" from him and studied it(18). Li Huang (d. 1811) (19) took part in editing Si Ku Quan Shu, so he must have had "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version, and studied "Da Yan Zong Shu Shu" (The General Dayan Computation). He wrote Jiu Yi Suan Shu (Mathematics Searching for One, 1803) based on this version of Shu Xue Jiu Zhang (20).</p> <p>One of the most important persons in restoring our knowledge concerning the filiation of these books was Li Rui (1768(21) -1817)(see his biography). ... only two volumes remain of this manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is, question 2 of "Huan Tian San Ji" (square of three loops), which later has been lost.</p> </filiation> </msItem> <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm--> |
| Content model | <content> |
| Schema Declaration | element filiation { tei_att.global.attributes, tei_att.typed.attributes, tei_macro.specialPara } |
| <foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [10.7.1.4. Foliation] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <foliation>Contemporary foliation in red roman numerals in the centre of the outer margin.</foliation> |
| Content model | <content> |
| Schema Declaration |
element foliation { tei_att.global.attributes, tei_macro.specialPara } |
| <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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_macro.phraseSeq } |
| <forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <persName> <roleName>Ex-President</roleName> <forename>George</forename> <surname>Bush</surname> </persName> |
| Content model | <content> |
| Schema Declaration | element forename { tei_att.global.attributes, tei_att.personal.attributes, tei_att.typed.attributes, tei_macro.phraseSeq } |
| <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 | |
| 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 { tei_att.global.attributes, tei_att.declaring.attributes, ( ( tei_model.frontPart | tei_model.pLike | tei_model.pLike.front | tei_model.global )*, ( ( ( tei_model.div1Like, ( tei_model.div1Like | tei_model.frontPart | tei_model.global )* ) | ( tei_model.divLike, ( tei_model.divLike | tei_model.frontPart | tei_model.global )* ) ), ( tei_model.divBottom, ( tei_model.divBottom | tei_model.global )* )? )? ) } |
| <fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter] | |||||||||||
| Module | transcr | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Note | Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The fw element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance. | ||||||||||
| Example | <fw place="bottom" type="sig">C3</fw> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element fw { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.placement.attributes, tei_att.written.attributes, attribute type { teidata.enumerated }?, tei_macro.phraseSeq } | ||||||||||
| <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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||||||
| 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 11.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" reason="illegible" unit="chars"/> | ||||||||||||||||
| Example | <gap quantity="1" reason="sampling" unit="essay"/> | ||||||||||||||||
| Example | <del> <gap atLeast="4" atMost="8" reason="illegible" unit="chars"/> </del> | ||||||||||||||||
| Example | <gap extent="several lines" reason="lost"/> | ||||||||||||||||
| Content model | <content> | ||||||||||||||||
| Schema Declaration | element gap { tei_att.global.attributes, tei_att.timed.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, attribute reason { list { ( "cancelled" | "deleted" | "editorial" | "illegible" | "inaudible" | "irrelevant" | "sampling" | teidata.enumerated )+ } }?, attribute agent { teidata.enumerated }?, ( tei_model.descLike | tei_model.certLike )* } | ||||||||||||||||
| <gb> (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex. [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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| May contain | Empty element |
| Note | By convention, gb elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation. The type attribute may be used to further characterize the gathering in any respect. |
| Example | <gb n="iii"/> <pb n="2r"/> <!-- material from page 2 recto of gathering iii here --> <pb n="2v"/> <!-- material from page 2 verso of gathering iii here --> |
| Content model | <content> |
| Schema Declaration | element gb { tei_att.global.attributes, tei_att.typed.attributes, tei_att.spanning.attributes, tei_att.breaking.attributes, tei_att.edition.attributes, empty } |
| <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 11.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material msItem provenance support verse: rhyme |
| 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 subtype="thumbnail" type="normal" url="spi/thumb/001r.jpg"/> <graphic subtype="low-res" type="normal" url="spi/normal/lowRes/001r.jpg"/> <graphic subtype="high-res" type="normal" url="spi/normal/highRes/001r.jpg"/> <graphic subtype="low-res" type="high-contrast" url="spi/contrast/lowRes/001r.jpg"/> <graphic subtype="high-res" type="high-contrast" url="spi/contrast/highRes/001r.jpg"/> </surface> <surface xml:id="spi001v"> <graphic subtype="thumbnail" type="normal" url="spi/thumb/001v.jpg"/> <graphic subtype="low-res" type="normal" url="spi/normal/lowRes/001v.jpg"/> <graphic subtype="high-res" type="normal" url="spi/normal/highRes/001v.jpg"/> <graphic subtype="low-res" type="high-contrast" url="spi/contrast/lowRes/001v.jpg"/> <graphic subtype="high-res" type="high-contrast" url="spi/contrast/highRes/001v.jpg"/> <zone xml:id="spi001v_detail01"> <graphic subtype="thumbnail" type="normal" url="spi/thumb/001v-detail01.jpg"/> <graphic subtype="low-res" type="normal" url="spi/normal/lowRes/001v-detail01.jpg"/> <graphic subtype="high-res" type="normal" url="spi/normal/highRes/001v-detail01.jpg"/> <graphic subtype="low-res" type="high-contrast" url="spi/contrast/lowRes/001v-detail01.jpg"/> <graphic subtype="high-res" type="high-contrast" url="spi/contrast/highRes/001v-detail01.jpg"/> </zone> </surface> </surfaceGrp> </facsimile> |
| Content model | <content> |
| Schema Declaration | element graphic { tei_att.global.attributes, tei_att.media.attributes, tei_att.resourced.attributes, tei_att.declaring.attributes, tei_att.typed.attributes, tei_model.descLike* } |
| <handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations] | |||||||
| Module | msdescription | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | msdescription: physDesc | ||||||
| May contain | |||||||
| Example | <handDesc> <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote> </handDesc> | ||||||
| Example | <handDesc hands="2"> <p>The manuscript is written in two contemporary hands, otherwise unknown, but clearly those of practised scribes. Hand I writes ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand on f. 24, but the evidence for this is insubstantial.</p> </handDesc> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element handDesc { tei_att.global.attributes, attribute hands { teidata.count }?, ( tei_model.pLike+ | ( summary?, tei_handNote+ ) ) } | ||||||
| <handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <handNote scope="sole"> <p>Written in insular phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed minuscule.</p> </handNote> |
| Content model | <content> |
| Schema Declaration | element handNote { tei_att.global.attributes, tei_att.handFeatures.attributes, tei_macro.specialPara } |
| <handNotes> contains one or more handNote elements documenting the different hands identified within the source texts. [11.3.2.1. Document Hands] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | header: handNote |
| Example | <handNotes> <handNote medium="brown-ink" script="copperplate" xml:id="H1">Carefully written with regular descenders</handNote> <handNote medium="pencil" script="print" xml:id="H2">Unschooled scrawl</handNote> </handNotes> |
| Content model | <content> |
| Schema Declaration |
element handNotes { tei_att.global.attributes, tei_handNote+ } |
| <handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands] | |||||||||
| Module | transcr | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||||
| May contain | Empty element | ||||||||
| Note | The handShift element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes. | ||||||||
| Example | <l>When wolde the cat dwelle in his ynne</l> <handShift medium="greenish-ink"/> <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element handShift { tei_att.global.attributes, tei_att.handFeatures.attributes, attribute new { teidata.pointer }?, empty } | ||||||||
| <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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.typed.attributes, tei_att.placement.attributes, tei_att.written.attributes, ( text | tei_lg | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.lLike | tei_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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout locus material provenance repository support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.written.attributes, tei_macro.paraContent } |
| <history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msDesc |
| May contain | |
| Example | <history> <origin> <p>Written in Durham during the mid twelfth century.</p> </origin> <provenance> <p>Recorded in two medieval catalogues of the books belonging to Durham Priory, made in 1391 and 1405.</p> </provenance> <provenance> <p>Given to W. Olleyf by William Ebchester, Prior (1446-56) and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne) according to inscriptions on ff. 4v and 5.</p> </provenance> <acquisition> <p>Presented to Trinity College in 1738 by Thomas Gale and his son Roger.</p> </acquisition> </history> |
| Content model | <content> |
| Schema Declaration | element history { tei_att.global.attributes, ( tei_model.pLike+ | ( summary?, origin?, tei_provenance*, tei_acquisition? ) ) } |
| <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. [13.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 | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure monogr note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: authority change correspAction creation distributor extent handNote idno licence publicationStmt msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msIdentifier provenance repository support verse: rhyme | ||||||||||
| 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 { tei_att.global.attributes, tei_att.sortable.attributes, tei_att.datable.attributes, tei_att.typed.attribute.subtype, attribute type { "ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC" | teidata.enumerated }?, ( text | tei_model.gLike | tei_idno )* } | ||||||||||
| <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Contained by | core: monogr |
| May contain | |
| Example | <imprint> <pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
| Content model | <content> |
| Schema Declaration | element imprint { tei_att.global.attributes, ( ( classCode | catRef )*, ( ( tei_model.imprintPart | tei_model.dateLike ), respStmt*, tei_model.global* )+ ) } |
| <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 head hi imprint index item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||
| 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 { tei_att.global.attributes, tei_att.spanning.attributes, attribute indexName { teidata.name }?, ( tei_term, tei_index? )* } | ||||||||
| <institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msIdentifier |
| May contain | |
| Example | <msIdentifier> <settlement>Oxford</settlement> <institution>University of Oxford</institution> <repository>Bodleian Library</repository> <idno>MS. Bodley 406</idno> </msIdentifier> |
| Content model | <content> |
| Schema Declaration | element institution { tei_att.global.attributes, tei_att.naming.attributes, tei_macro.phraseSeq.limited } |
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
| Module | core |
| Attributes |
|
| Contained by | — |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.sortable.attributes, tei_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 | core: term | ||||||
| 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 { tei_att.global.attributes, attribute scheme { teidata.pointer }?, ( tei_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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements. </sch:report> |
| Content model | <content> |
| Schema Declaration | element l { tei_att.global.attributes, tei_att.metrical.attributes, tei_att.enjamb.attributes, tei_att.fragmentable.attributes, ( text | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.global )* } |
| <layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations] | |||||||||||||||||||||||||||||||||
| Module | msdescription | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Contained by | msdescription: layoutDesc | ||||||||||||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||||||||||||||||||
| Example | <layout columns="1" ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout> | ||||||||||||||||||||||||||||||||
| Example | <layout columns="2" ruledLines="42"> <p>2 columns of 42 lines ruled in ink, with central rule between the columns.</p> </layout> | ||||||||||||||||||||||||||||||||
| Example | <layout columns="1 2" writtenLines="40 50"> <p>Some pages have 2 columns, with central rule between the columns; each column with between 40 and 50 lines of writing.</p> </layout> | ||||||||||||||||||||||||||||||||
| Example | <layout columns="3" streams="3"/> <!-- Further down in document body --> <div type="page"> <ab> <pb/> 一二三<cb type="top-stream"/> 一二三<cb type="mid-stream"/> 一二三<cb type="bottom-stream"/> <!-- cb here for demo purposes --> </ab> </div> | ||||||||||||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||||||||||||
| Schema Declaration | element layout { tei_att.global.attributes, attribute columns { list { teidata.count, teidata.count? } }?, attribute streams { list { teidata.count, teidata.count? } }?, attribute ruledLines { list { teidata.count, teidata.count? } }?, attribute writtenLines { list { teidata.count, teidata.count? } }?, tei_macro.specialPara } | ||||||||||||||||||||||||||||||||
| <layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: objectDesc |
| May contain | |
| Example | <layoutDesc> <p>Most pages have between 25 and 32 long lines ruled in lead.</p> </layoutDesc> |
| Example | <layoutDesc> <layout columns="2" ruledLines="42"> <p> <locus from="f12r" to="f15v"/> 2 columns of 42 lines pricked and ruled in ink, with central rule between the columns.</p> </layout> <layout columns="3"> <p> <locus from="f16"/>Prickings for three columns are visible.</p> </layout> </layoutDesc> |
| Content model | <content> |
| Schema Declaration | element layoutDesc { tei_att.global.attributes, ( tei_model.pLike+ | ( summary?, tei_layout+ ) ) } |
| <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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| 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 { tei_att.global.attributes, tei_att.typed.attributes, tei_att.edition.attributes, tei_att.spanning.attributes, tei_att.breaking.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: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> |
| Schematron | <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups. </sch:report> |
| Content model | <content> |
| Schema Declaration | element lg { tei_att.global.attributes, tei_att.divLike.attributes, tei_att.typed.attributes, tei_att.declaring.attributes, ( ( tei_model.divTop | tei_model.global )*, ( tei_model.lLike | tei_model.stageLike | tei_model.labelLike | tei_model.pPart.transcriptional | tei_lg ), ( tei_model.lLike | tei_model.stageLike | tei_model.labelLike | tei_model.pPart.transcriptional | tei_model.global | tei_lg )*, ( tei_model.divBottom, tei_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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 notBefore="2013-01-01" target="http://creativecommons.org/licenses/by/3.0/"> <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 { tei_att.global.attributes, tei_att.pointing.attributes, tei_att.datable.attributes, tei_macro.specialPara } |
| <listApp> (list of apparatus entries) contains a list of apparatus entries. [12.2. Linking the Apparatus to the Text] | |
| Module | textcrit |
| Attributes |
|
| Member of | |
| Contained by | dictionaries: xr header: change handNote licence sourceDesc msdescription: accMat acquisition collation decoNote filiation foliation layout provenance support verse: rhyme |
| May contain | |
| Note | listApp elements would normally be located in the back part of a document, but they may appear elsewhere. |
| Example | In the following example from the exegetical Yasna, the base text is encoded in the body of the document, and two separate listApp elements are used in the back, containing variant readings written in different scripts. <body> <div> <lg rend="italic" type="stanza" xml:id="Y-36.01" xml:lang="pal-Avst"> <l xml:id="Y-36.01_L-1"> <w xml:id="Y-36.01_L1_W-01">ahiiā</w> <w xml:id="Y-36.01_L1_W-02">ϑβā</w> <w xml:id="Y-36.01_L1_W-03">āϑrō</w> <w xml:id="Y-36.01_L1_W-04">vərəzə̄nā</w> <w xml:id="Y-36.01_L1_W-05">paouruiiē</w> <w xml:id="Y-36.01_L1_W-06">pairijasāmaiδē</w> <w xml:id="Y-36.01_L1_W-07">mazdā</w> <w xml:id="Y-36.01_L1_W-08">ahurā</w> </l> <!-- ... --> </lg> </div> </body> <!-- ... --> <back> <div> <listApp xml:id="CA_Y-36" xml:lang="pal-Avst"> <head>Variants from witnesses in Avestan script</head> <app from="#Y-36.01_L1_W-01"> <rdg wit="#Pt4 #F2 #J2 #M1">ahiiā</rdg> </app> <app from="#Y-36.01_L1_W-02"> <rdg wit="#Pt4 #F2 #J2 #M1">ϑβā</rdg> </app> <app from="#Y-36.01_L1_W-03"> <rdg wit="#Pt4 #J2 #M1">āϑrō</rdg> <rdg wit="#F2">āϑrōi</rdg> </app> <!-- ... --> </listApp> <listApp xml:id="CA_PY-36" xml:lang="pal-Phlv"> <head>Variants from witnesses written in Pahlavi script</head> <app from="#PY-36.01_L1_W-01"> <rdg wit="#Pt4 #F2 #J2 #M1">ʾytwnˈ</rdg> </app> <app from="#PY-36.01_L1_W-02"> <rdg wit="#Pt4 #F2 #J2 #M1">ʾwˈ</rdg> </app> <app from="#PY-36.01_L1_W-03"> <rdg wit="#Pt4 #F2 #J2 #M1">ḤNʾ</rdg> </app> <!-- ... --> </listApp> </div> </back> |
| Content model | <content> |
| Schema Declaration | element listApp { tei_att.global.attributes, tei_att.sortable.attributes, tei_att.declarable.attributes, tei_att.typed.attributes, ( tei_model.headLike*, tei_desc*, ( tei_app | tei_listApp )+ ) } |
| <listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 11.7. Identifying Changes and Revisions] | |||||||||
| Module | header | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | header: creation listChange revisionDesc linking: standOff | ||||||||
| May contain | core: desc header: change listChange | ||||||||
| Note | When this element appears within the creation element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the revisionDesc element, it documents only changes made during the evolution of the encoded representation of that text. | ||||||||
| Example | <revisionDesc> <listChange> <change when="1991-11-11" who="#LB"> deleted chapter 10 </change> <change when="1991-11-02" who="#MSM"> completed first draft </change> </listChange> </revisionDesc> | ||||||||
| Example | <profileDesc> <creation> <listChange ordered="true"> <change xml:id="CHG-1">First stage, written in ink by a writer</change> <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change> <change xml:id="CHG-3">Fixation of the revised passages and further revisions by Goethe using ink</change> <change xml:id="CHG-4">Addition of another stanza in a different hand, probably at a later stage</change> </listChange> </creation> </profileDesc> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element listChange { tei_att.global.attributes, tei_att.sortable.attributes, tei_att.typed.attributes, attribute ordered { teidata.truthValue }?, ( tei_desc*, ( tei_listChange | tei_change )+ ) } | ||||||||
| <listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [11.3.4.5. Transpositions] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| May contain | |
| Example | <listTranspose> <transpose> <ptr target="#ib02"/> <ptr target="#ib01"/> </transpose> </listTranspose> This example might be used for a source document which indicates in some way that the elements identified by |
| Content model | <content> |
| Schema Declaration | element listTranspose { tei_att.global.attributes, ( tei_desc*, tei_transpose+ ) } |
| <locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript] | |||||||||||||||||||
| Module | msdescription | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | core: abbr add addrLine author biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout locus material msItem msItemStruct provenance repository support verse: rhyme | ||||||||||||||||||
| May contain | |||||||||||||||||||
| Note | The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example. To associate a locus element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the surface, zone, graphic, or <binaryObject> elements. 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 | ||||||||||||||||||
| Example | <!-- within ms description --><msItem n="1"> <locus from="1r" target="#F1r #F1v #F2r" to="2r">ff. 1r-2r</locus> <author>Ben Jonson</author> <title>Ode to himself</title> <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric> <incipit>Com leaue the loathed stage</incipit> <explicit>And see his chariot triumph ore his wayne.</explicit> <bibl> <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... --> | ||||||||||||||||||
| Example | The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example: <msItem> <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus> <title>Birds Praise of Love</title> <bibl> <title>IMEV</title> <biblScope>1506</biblScope> </bibl> </msItem> | ||||||||||||||||||
| Content model | <content> | ||||||||||||||||||
| Schema Declaration | element locus { tei_att.global.attributes, tei_att.pointing.attributes, tei_att.typed.attributes, attribute scheme { teidata.pointer }?, attribute from { teidata.word }?, attribute to { teidata.word }?, ( text | tei_model.gLike | tei_hi | tei_locus )* } | ||||||||||||||||||
| <material> (material) contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type] | |||||||||||||||||
| Module | msdescription | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | core: abbr add addrLine author biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme | ||||||||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||
| Note | The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally. | ||||||||||||||||
| Example | <physDesc> <p> <material>Parchment</material> leaves with a <material>sharkskin</material> binding.</p> </physDesc> | ||||||||||||||||
| Content model | <content> | ||||||||||||||||
| Schema Declaration | element material { tei_att.global.attributes, tei_att.canonical.attributes, tei_att.typed.attributes, attribute function { teidata.enumerated }?, attribute target { list { teidata.pointer+ } }?, tei_macro.phraseSeq } | ||||||||||||||||
| <measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme | ||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||
| Example | This example references a definition of a measurement unit declared in the TEI header: <measure type="weight"> <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="area" unitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc> <unitDecl> <unitDef type="area" xml:id="merk"> <label>merk</label> <placeName ref="#Scotland"/> <desc>A merk was an area of land determined variably by its agricultural productivity.</desc> </unitDef> </unitDecl> </encodingDesc> | ||||||||
| Example | <measure commodity="rum" quantity="40" unit="hogshead">2 score hh rum</measure> <measure commodity="roses" quantity="12" unit="count">1 doz. roses</measure> <measure commodity="tulips" quantity="1" unit="count">a yellow tulip</measure> | ||||||||
| Example | <head>Long papers.</head> <p>Speakers will be given 30 minutes each: 20 minutes for presentation, 10 minutes for discussion. Proposals should not exceed <measure commodity="words" max="500" unit="count">500 words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element measure { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.measurement.attributes, tei_att.ranging.attributes, attribute type { teidata.enumerated }?, tei_macro.phraseSeq } | ||||||||
| <metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks] | |||||||||||||
| Module | transcr | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||
| Example | <surface> <metamark function="used" rend="line" target="#X2"/> <zone xml:id="zone-X2"> <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line> <line>The tears of foolish passion yet undried</line> <line>upon my cheeks.</line> <!-- ... --> <line>I pass through <add>the</add> travels and <del>fortunes</del> of <retrace>thirty</retrace> </line> <line>years and become old,</line> <line>Each in its due order comes and goes,</line> <line>And thus a message for me comes.</line> <line>The</line> </zone> <metamark function="used" target="#zone-X2">Entered - Yes</metamark> </surface> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element metamark { tei_att.spanning.attributes, tei_att.placement.attributes, tei_att.global.attributes, attribute function { teidata.word }?, attribute target { list { teidata.pointer+ } }?, tei_macro.specialPara } | ||||||||||||
| <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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| 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 ed="La" n="23" unit="Dreissiger"/> ... <milestone ed="AV" n="24" unit="verse"/> ... |
| Content model | <content> |
| Schema Declaration | element milestone { tei_att.global.attributes, tei_att.milestoneUnit.attributes, tei_att.typed.attributes, tei_att.edition.attributes, tei_att.spanning.attributes, tei_att.breaking.attributes, empty } |
| <mod> represents any kind of modification identified within a single document. [11.3.4.1. Generic Modification] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <mod type="subst"> <add>pleasing</add> <del>agreable</del> </mod> |
| Content model | <content> |
| Schema Declaration | element mod { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.typed.attributes, tei_att.spanning.attributes, tei_att.dimensions.attributes, tei_macro.paraContent } |
| <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core |
| Attributes |
|
| Contained by | core: biblStruct |
| May contain | |
| Note | May contain specialized bibliographic elements, in a prescribed order. The monogr element may only occur only within a biblStruct, where its use is mandatory for the description of a monographic-level bibliographic item. |
| Example | <biblStruct> <analytic> <author>Chesnutt, David</author> <title>Historical Editions in the States</title> </analytic> <monogr> <title level="j">Computers and the Humanities</title> <imprint> <date when="1991-12">(December, 1991):</date> </imprint> <biblScope>25.6</biblScope> <biblScope from="377" to="380" unit="page">377–380</biblScope> </monogr> </biblStruct> |
| Example | <biblStruct type="book"> <monogr> <author> <persName> <forename>Leo Joachim</forename> <surname>Frachtenberg</surname> </persName> </author> <title level="m" type="main">Lower Umpqua Texts</title> <imprint> <pubPlace>New York</pubPlace> <publisher>Columbia University Press</publisher> <date>1914</date> </imprint> </monogr> <series> <title level="s" type="main">Columbia University Contributions to Anthropology</title> <biblScope unit="volume">4</biblScope> </series> </biblStruct> |
| Content model | <content> |
| Schema Declaration | element monogr { tei_att.global.attributes, ( ( ( ( tei_author | tei_editor | meeting | respStmt ), ( tei_author | tei_editor | meeting | respStmt )*, tei_title+, ( tei_model.ptrLike | tei_idno | textLang | tei_editor | respStmt )* ) | ( ( tei_title | tei_model.ptrLike | tei_idno )+, ( textLang | tei_author | tei_editor | meeting | respStmt )* ) | ( tei_authority, tei_idno ) )?, tei_availability*, tei_model.noteLike*, ( edition, ( tei_idno | tei_model.ptrLike | tei_editor | sponsor | funder | respStmt )* )*, tei_imprint, ( tei_imprint | tei_extent | tei_biblScope )* ) } |
| <msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msDesc |
| May contain | |
| Note | Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, msItem, or msItemStruct. This constraint is not currently enforced by the schema. |
| Example | <msContents class="#sermons"> <p>A collection of Lollard sermons</p> </msContents> |
| Example | <msContents> <msItem n="1"> <locus>fols. 5r-7v</locus> <title>An ABC</title> <bibl> <title>IMEV</title> <biblScope>239</biblScope> </bibl> </msItem> <msItem n="2"> <locus>fols. 7v-8v</locus> <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title> <bibl> <title>IMEV</title> <biblScope>3747</biblScope> </bibl> </msItem> <msItem n="3"> <locus>fol. 8v</locus> <title>Truth</title> <bibl> <title>IMEV</title> <biblScope>809</biblScope> </bibl> </msItem> <msItem n="4"> <locus>fols. 8v-10v</locus> <title>Birds Praise of Love</title> <bibl> <title>IMEV</title> <biblScope>1506</biblScope> </bibl> </msItem> <msItem n="5"> <locus>fols. 10v-11v</locus> <title xml:lang="la">De amico ad amicam</title> <title xml:lang="la">Responcio</title> <bibl> <title>IMEV</title> <biblScope>16 & 19</biblScope> </bibl> </msItem> <msItem n="6"> <locus>fols. 14r-126v</locus> <title>Troilus and Criseyde</title> <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note> </msItem> </msContents> |
| Content model | <content> |
| Schema Declaration | element msContents { tei_att.global.attributes, tei_att.msExcerpt.attributes, tei_att.msClass.attributes, ( tei_model.pLike+ | ( summary?, textLang?, tei_titlePage?, ( tei_msItem | tei_msItemStruct )* ) ) } |
| <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Although the msDesc has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable. |
| Example | <msDesc> <msIdentifier> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <idno type="Bod">MS Poet. Rawl. D. 169.</idno> </msIdentifier> <msContents> <msItem> <author>Geoffrey Chaucer</author> <title>The Canterbury Tales</title> </msItem> </msContents> <physDesc> <objectDesc> <p>A parchment codex of 136 folios, measuring approx 28 by 19 inches, and containing 24 quires.</p> <p>The pages are margined and ruled throughout.</p> <p>Four hands have been identified in the manuscript: the first 44 folios being written in two cursive anglicana scripts, while the remainder is for the most part in a mixed secretary hand.</p> </objectDesc> </physDesc> </msDesc> |
| Schematron | <sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element msDesc { tei_att.global.attributes, tei_att.sortable.attributes, tei_att.typed.attributes, tei_att.declaring.attributes, tei_att.docStatus.attributes, ( tei_msIdentifier, tei_model.headLike*, ( tei_model.pLike+ | ( tei_msContents | tei_physDesc | tei_history | additional | msPart | msFrag )* ) ) } |
| <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <msIdentifier> <settlement>San Marino</settlement> <repository>Huntington Library</repository> <idno>MS.El.26.C.9</idno> </msIdentifier> |
| Schematron | <sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report> |
| Content model | <content> |
| Schema Declaration | element msIdentifier { tei_att.global.attributes, ( ( tei_placeName?, tei_settlement?, tei_institution?, tei_repository?, collection*, tei_idno* ), ( msName | objectName | altIdentifier )* ) } |
| <msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msContents |
| May contain | |
| Example | <msItem class="#saga"> <locus>ff. 1r-24v</locus> <title>Agrip af Noregs konunga sögum</title> <incipit>regi oc h<ex>ann</ex> setiho <gap extent="7" reason="illegible"/>sc heim se<ex>m</ex> þio</incipit> <explicit>h<ex>on</ex> hev<ex>er</ex> <ex>oc</ex>þa buit hesta .ij. aNan viþ fé enh<ex>on</ex>o<ex>m</ex> aNan til reiþ<ex>ar</ex> </explicit> <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem> |
| Content model | <content> |
| Schema Declaration | element msItem { tei_att.global.attributes, tei_att.msExcerpt.attributes, tei_att.msClass.attributes, ( ( tei_locus | locusGrp )*, ( tei_model.pLike+ | ( tei_model.titlepagePart | model.msItemPart | tei_model.global )+ ) ) } |
| <msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msContents msItemStruct |
| May contain | |
| Example | <msItemStruct class="#biblComm" defective="false" n="2"> <locus from="24v" to="97v">24v-97v</locus> <author>Apringius de Beja</author> <title type="uniform" xml:lang="la">Tractatus in Apocalypsin</title> <rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i Pacensis eccl<ex>esi</ex>e</rubric> <finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S. DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric> <bibl> <ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl> <textLang mainLang="la">Latin</textLang> </msItemStruct> |
| Content model | <content> |
| Schema Declaration | element msItemStruct { tei_att.global.attributes, tei_att.msExcerpt.attributes, tei_att.msClass.attributes, ( ( tei_locus | locusGrp )?, ( tei_model.pLike+ | ( tei_author*, respStmt*, tei_title*, rubric?, incipit?, tei_msItemStruct*, explicit?, finalRubric?, colophon*, tei_decoNote*, listBibl*, ( tei_bibl | tei_biblStruct )*, tei_filiation?, tei_model.noteLike*, textLang? ) ) ) } |
| <nameLink> (name link) contains a connecting phrase or link used within a name but not regarded as part of it, such as van der or of. [13.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <persName> <forename>Frederick</forename> <nameLink>van der</nameLink> <surname>Tronck</surname> </persName> |
| Example | <persName> <forename>Alfred</forename> <nameLink>de</nameLink> <surname>Musset</surname> </persName> |
| Content model | <content> |
| Schema Declaration | element nameLink { tei_att.global.attributes, tei_att.typed.attributes, tei_macro.phraseSeq } |
| <normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |||||||||
| Module | header | ||||||||
| Attributes |
| ||||||||
| Contained by | — | ||||||||
| May contain | |||||||||
| Example | <editorialDecl> <normalization method="markup"> <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern 20th century typographical practice, the <gi>choice</gi> element has been used to enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values respectively. ... </p> </normalization> <normalization method="silent"> <p>Spacing between words and following punctuation has been regularized to zero spaces; spacing between words has been regularized to one space.</p> </normalization> <normalization source="http://www.dict.sztaki.hu/webster"> <p>Spelling converted throughout to Modern American usage, based on Websters 9th Collegiate dictionary.</p> </normalization> </editorialDecl> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element normalization { tei_att.global.attributes, tei_att.declarable.attributes, attribute method { "silent" | "markup" }?, tei_model.pLike+ } | ||||||||
| <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 9.3.5.4. Notes within Entries] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope biblStruct cit corr date del editor emph expan foreign head hi imprint item l lg measure monogr note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem msItemStruct provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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" resp="#MDMH" type="gloss"> <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 anchored="true" n="126"> 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 { tei_att.global.attributes, tei_att.placement.attributes, tei_att.pointing.attributes, tei_att.typed.attributes, tei_att.written.attributes, tei_att.anchoring.attributes, tei_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 { tei_att.global.attributes, ( tei_model.noteLike | tei_relatedItem )+ } |
| <num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme | ||||||||||||||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||||||||
| Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. 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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.ranging.attributes, attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" | teidata.enumerated }?, attribute value { teidata.numeric }?, tei_macro.phraseSeq } | ||||||||||||||||||||||
| <objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description] | |||||||||
| Module | msdescription | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | msdescription: physDesc | ||||||||
| May contain | |||||||||
| Example | <objectDesc form="codex"> <supportDesc material="mixed"> <p>Early modern <material>parchment</material> and <material>paper</material>.</p> </supportDesc> <layoutDesc> <layout ruledLines="25 32"/> </layoutDesc> </objectDesc> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element objectDesc { tei_att.global.attributes, attribute form { teidata.enumerated }?, ( tei_model.pLike+ | ( tei_supportDesc?, tei_layoutDesc? ) ) } | ||||||||
| <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 | core: abbr add address choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.written.attributes, ( text | tei_model.gLike | tei_model.phrase | argument | tei_byline | tei_dateline | tei_epigraph | tei_salute | tei_signed | tei_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 12. Critical Apparatus] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_macro.paraContent } |
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | header: availability change correspAction correspDesc editorialDecl encodingDesc handNote licence normalization projectDesc publicationStmt sourceDesc msdescription: accMat acquisition binding bindingDesc collation decoNote filiation foliation handDesc history layout layoutDesc msContents msDesc msItem msItemStruct objectDesc physDesc provenance support supportDesc textcrit: rdg transcr: metamark |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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: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> |
| Schematron | <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> |
| Content model | <content> |
| Schema Declaration | element p { tei_att.global.attributes, tei_att.declaring.attributes, tei_att.fragmentable.attributes, tei_att.written.attributes, tei_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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme |
| 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 ed="ed2" n="145"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb ed="ed1" n="283"/> <!-- 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 facs="page1.png" n="1"/> <!-- page1.png contains an image of the page; the text it contains is encoded here --> <p> <!-- ... --> </p> <pb facs="page2.png" n="2"/> <!-- similarly, for page 2 --> <p> <!-- ... --> </p> </body> |
| Content model | <content> |
| Schema Declaration | element pb { tei_att.global.attributes, tei_att.typed.attributes, tei_att.edition.attributes, tei_att.spanning.attributes, tei_att.breaking.attributes, empty } |
| <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||||||||||||||||
| 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 msd="1.Pl.*.Nom" pos="PPER">Wir</w> <w msd="1.Pl.Pres.Ind" pos="VVFIN">fahren</w> <w msd="--" pos="APPR">in</w> <w msd="Def.Masc.Akk.Sg." pos="ART">den</w> <w msd="Masc.Akk.Sg." pos="NN">Urlaub</w> <pc join="left" msd="--" pos="$.">.</pc> </s> | ||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||
| Schema Declaration | element pc { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.linguistic.attributes, attribute force { "strong" | "weak" | "inter" }?, attribute unit { teidata.enumerated }?, attribute pre { teidata.truthValue }?, ( text | tei_model.gLike | tei_c | tei_model.pPart.edit )* } | ||||||||||||||||||||
| <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names] | |||||||||||
| Module | namesdates | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme | ||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Example | <persName> <forename>Edward</forename> <forename>George</forename> <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of <placeName>Knebworth</placeName> </roleName> </persName> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element persName { tei_att.global.attributes, tei_att.datable.attributes, tei_att.editLike.attributes, tei_att.personal.attributes, tei_att.typed.attributes, attribute calendar { list { teidata.pointer+ } }?, tei_macro.phraseSeq } | ||||||||||
| <physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msDesc |
| May contain | |
| Example | <physDesc> <objectDesc form="codex"> <supportDesc material="perg"> <support>Parchment.</support> <extent>i + 55 leaves <dimensions scope="all" type="leaf" unit="inch"> <height>7¼</height> <width>5⅜</width> </dimensions> </extent> </supportDesc> <layoutDesc> <layout columns="2">In double columns.</layout> </layoutDesc> </objectDesc> <handDesc> <p>Written in more than one hand.</p> </handDesc> <decoDesc> <p>With a few coloured capitals.</p> </decoDesc> </physDesc> |
| Content model | <content> |
| Schema Declaration | element physDesc { tei_att.global.attributes, ( tei_model.pLike*, tei_objectDesc?, tei_handDesc?, tei_bindingDesc?, tei_accMat? ) } |
| <placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names] | |||||||||||
| Module | namesdates | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msIdentifier provenance repository support verse: rhyme | ||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Example | <placeName> <settlement>Rochester</settlement> <region>New York</region> </placeName> | ||||||||||
| Example | <placeName> <geogName>Arrochar Alps</geogName> <region>Argylshire</region> </placeName> | ||||||||||
| Example | <placeName> <measure>10 miles</measure> <offset>Northeast of</offset> <settlement>Attica</settlement> </placeName> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element placeName { tei_att.datable.attributes, tei_att.editLike.attributes, tei_att.global.attributes, tei_att.personal.attributes, tei_att.typed.attributes, attribute calendar { list { teidata.pointer+ } }?, tei_macro.phraseSeq } | ||||||||||
| <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 | header: correspDesc creation textClass transcr: handNotes listTranspose |
| 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 degree="high" type="entertain"/> <purpose degree="medium" type="inform"/> </textDesc> <settingDesc> <setting> <name>Paris, France</name> <time>Late 19th century</time> </setting> </settingDesc> </profileDesc> |
| Content model | <content> |
| Schema Declaration |
element profileDesc { tei_att.global.attributes, tei_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 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Example | <projectDesc> <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc> |
| Content model | <content> |
| Schema Declaration | element projectDesc { tei_att.global.attributes, tei_att.declarable.attributes, tei_model.pLike+ } |
| <provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History] | |||||||||||
| Module | msdescription | ||||||||||
| Attributes |
| ||||||||||
| Contained by | msdescription: history | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Example | <provenance>Listed as the property of Lawrence Sterne in 1788.</provenance> <provenance>Sold at Sothebys in 1899.</provenance> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element provenance { tei_att.global.attributes, tei_att.datable.attributes, tei_att.typed.attributes, attribute calendar { list { teidata.pointer+ } }?, tei_macro.specialPara } | ||||||||||
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope biblStruct cit corr date del desc editor emph expan foreign head hi item l measure monogr note num orig p pubPlace publisher q quote ref reg relatedItem rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | Empty element |
| Example | <ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/> |
| Schematron | <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> |
| Content model | <content> |
| Schema Declaration | element ptr { tei_att.cReferencing.attributes, tei_att.declaring.attributes, tei_att.global.attributes, tei_att.pointing.attributes, tei_att.typed.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 { tei_att.global.attributes, ( ( tei_model.publicationStmtPart.agency, tei_model.publicationStmtPart.detail* )+ | tei_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 | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.canonical.attributes, tei_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 | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <publicationStmt> <publisher>Oxford University Press</publisher> <pubPlace>Oxford</pubPlace> <date>1989</date> </publicationStmt> |
| Content model | <content> |
| Schema Declaration | element pubPlace { tei_att.global.attributes, tei_att.naming.attributes, tei_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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support textstructure: body byline closer dateline div docAuthor docImprint epigraph opener salute signed titlePart verse: rhyme | ||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||
| 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 { tei_att.global.attributes, tei_att.ascribed.directed.attributes, attribute type { "spoken" | "thought" | "written" | "soCalled" | "foreign" | "distinct" | "term" | "emph" | "mentioned" | teidata.enumerated }?, tei_macro.specialPara } | ||||||||
| <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope cit corr del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Note | If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the cit element. |
| Example | Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref> |
| Content model | <content> |
| Schema Declaration | element quote { tei_att.global.attributes, tei_att.typed.attributes, tei_att.msExcerpt.attributes, tei_att.notated.attributes, tei_macro.specialPara } |
| <rdg> (reading) contains a single reading within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
| Module | textcrit |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <rdg wit="#Ra2">Eryment</rdg> |
| Content model | <content> |
| Schema Declaration | element rdg { tei_att.global.attributes, tei_att.textCritical.attributes, tei_att.witnessed.attributes, ( text | tei_model.divLike | tei_model.divPart | tei_titlePage | argument | tei_byline | tei_docAuthor | docDate | docEdition | tei_docImprint | tei_docTitle | tei_epigraph | imprimatur | tei_titlePart | epilogue | performance | prologue | set | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.global | tei_model.rdgPart )* } |
| <rdgGrp> (reading group) within a textual variation, groups two or more readings perceived to have a genetic relationship or other affinity. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
| Module | textcrit |
| Attributes |
|
| Contained by | |
| May contain | |
| Note | May contain readings and nested reading groups. Usually, only one <lem> element should appear within a single apparatus entry, whether it appears outside a rdgGrp element or within it. |
| Example | <app> <lem wit="#El #Ra2">though</lem> <rdgGrp type="orthographic"> <rdg wit="#Hg">thogh</rdg> <rdg wit="#La">thouhe</rdg> </rdgGrp> </app> |
| Schematron | <sch:assert test="count(tei:lem) < 2">Only one <lem> element may appear within a <rdgGrp></sch:assert> |
| Content model | <content> |
| Schema Declaration | element rdgGrp { tei_att.global.attributes, tei_att.textCritical.attributes, ( lem?, ( tei_model.rdgLike | tei_model.noteLike | tei_witDetail | tei_wit | tei_rdgGrp )* ) } |
| <redo> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications] | |||||||
| Module | transcr | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||
| May contain | Empty element | ||||||
| Example | <line> <redo cause="fix" hand="#g_t" target="#redo-1"/> <mod hand="#g_bl" rend="strikethrough" spanTo="#anchor-1" xml:id="redo-1"/>Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken </line> <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/> </line> This encoding represents the following sequence of events:
| ||||||
| Content model | <content> | ||||||
| Schema Declaration | element redo { tei_att.global.attributes, tei_att.spanning.attributes, tei_att.transcriptional.attributes, tei_att.dimensions.attributes, attribute target { list { teidata.pointer+ } }?, empty } | ||||||
| <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope biblStruct cit corr date del desc editor emph expan foreign head hi item l measure monogr note num orig p pubPlace publisher q quote ref reg relatedItem rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> |
| Content model | <content> |
| Schema Declaration | element ref { tei_att.cReferencing.attributes, tei_att.declaring.attributes, tei_att.global.attributes, tei_att.pointing.attributes, tei_att.typed.attributes, tei_macro.paraContent } |
| <reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.typed.attributes, tei_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 | core: bibl biblStruct header: notesStmt | ||||||
| May contain | core: bibl biblStruct ptr ref msdescription: msDesc | ||||||
| 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: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> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element relatedItem { tei_att.global.attributes, tei_att.typed.attributes, attribute target { teidata.pointer }?, ( tei_model.biblLike | tei_model.ptrLike )? } | ||||||
| <repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msIdentifier |
| May contain | |
| Example | <msIdentifier> <settlement>Oxford</settlement> <institution>University of Oxford</institution> <repository>Bodleian Library</repository> <idno>MS. Bodley 406</idno> </msIdentifier> |
| Content model | <content> |
| Schema Declaration | element repository { tei_att.global.attributes, tei_att.naming.attributes, tei_macro.phraseSeq.limited } |
| <restore> (restore) indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction. [11.3.1.6. Cancellation of Deletions and Other Markings] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Note | On this element, the type attribute categorizes the way that the cancelled intervention has been indicated in some way, for example by means of a marginal note, over-inking, additional markup, etc. |
| Example | For I hate this <restore hand="#dhl" type="marginalStetNote"> <del>my</del> </restore> body |
| Content model | <content> |
| Schema Declaration | element restore { tei_att.global.attributes, tei_att.transcriptional.attributes, tei_att.typed.attributes, tei_att.dimensions.attributes, tei_macro.paraContent } |
| <retrace> contains a sequence of writing which has been retraced, for example by over-inking, to clarify or fix it. [11.3.4.3. Fixation and Clarification] | |
| Module | transcr |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Note | Multiple retraces are indicated by nesting one retrace within another. In principle, a retrace differs from a substitution in that second and subsequent rewrites do not materially alter the content of an element. Where minor changes have been made during the retracing action however these may be marked up using del, add, etc. with an appropriate value for the change attribute. |
| Content model | <content> |
| Schema Declaration | element retrace { tei_att.global.attributes, tei_att.spanning.attributes, tei_att.transcriptional.attributes, tei_att.dimensions.attributes, tei_macro.paraContent } |
| <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 | header: change listChange |
| 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 { tei_att.global.attributes, tei_att.docStatus.attributes, ( list+ | tei_listChange+ | tei_change+ ) } |
| <rhyme> marks the rhyming part of a metrical line. [6.5. Rhyme] | |||||||||
| Module | verse | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author biblScope corr date del editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||
| Example | <lg rhyme="abababcc"> <l>'Tis pity learned virgins ever <rhyme label="a">wed</rhyme> </l> <l>With persons of no sort of edu<rhyme label="b">cation</rhyme>,</l> <l>Or gentlemen, who, though well born and <rhyme label="a">bred</rhyme>,</l> <l>Grow tired of scientific conver<rhyme label="b">sation</rhyme>:</l> <l>I don't choose to say much on this <rhyme label="a">head</rhyme>,</l> <l>I'm a plain man, and in a single <rhyme label="b">station</rhyme>,</l> <l>But — Oh! ye lords of ladies inte<rhyme label="c">llectual</rhyme>,</l> <l>Inform us truly, have they not hen-<rhyme label="c">peck'd you all</rhyme>?</l> </lg> | ||||||||
| Example | <lg> <l>Tyger! Tyger! burning <rhyme label="a">bright</rhyme> </l> <l>In the forests of the <rhyme label="a">night</rhyme>,</l> <l>What immortal hand or <rhyme label="b">eye</rhyme> </l> <l>Could frame thy fearful <rhyme label="b" type="eye-rhyme">symmetry</rhyme>?</l> </lg> | ||||||||
| Example | <lg> <l>"Hark! Lakshman! Hark, again that <rhyme label="a">cry</rhyme>!</l> <l>It is, — it is my husband's <rhyme label="b">voice</rhyme>!</l> <l>hasten, to his succour <rhyme label="a">fly</rhyme>,</l> <l>No more hast thou, dear friend, a <rhyme label="b">choice</rhyme>.</l> <l>He calls on thee, perhaps his <rhyme label="c">foes</rhyme> </l> <l>Environ him on all sides <rhyme label="d">round</rhyme>,</l> <l>That wail, — it means death's final <rhyme label="c">throes</rhyme>!</l> <l>Why standest thou, as magic-<rhyme label="d">bound</rhyme>?</l> </lg> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element rhyme { tei_att.global.attributes, tei_att.typed.attributes, attribute label { teidata.word }?, tei_macro.paraContent } | ||||||||
| <rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.naming.attributes, tei_att.typed.attributes, tei_macro.phraseSeq } |
| <s> (s-unit) contains a sentence-like division of a text. [17.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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:report test="tei:s">You may not nest one s element within another: use seg instead</sch:report> |
| Content model | <content> |
| Schema Declaration | element s { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.notated.attributes, tei_macro.phraseSeq } |
| <said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope cit corr del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||||||||
| Example | <!-- in the header --><editorialDecl> <quotation marks="all"/> </editorialDecl> <!-- ... --> <p> <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill his wine, and blunt his sword, and say his name begins with X, and in the end the Duke will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O rider of the sun!'</said>"</said> </p> | ||||||||||||||||||||||
| Example | <p> <said aloud="true" rend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear. <said aloud="true" rend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see. Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove yourself, now that's interesting. … So where shall I put you?</said> </p> <p>Harry gripped the edges of the stool and thought, <said aloud="false" rend="italic">Not Slytherin, not Slytherin</said>.</p> | ||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||
| Schema Declaration | element said { tei_att.global.attributes, tei_att.ascribed.directed.attributes, attribute aloud { teidata.xTruthValue }?, attribute direct { teidata.xTruthValue }?, tei_macro.specialPara } | ||||||||||||||||||||||
| <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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <salute>To all courteous mindes, that will voutchsafe the readinge.</salute> |
| Content model | <content> |
| Schema Declaration | element salute { tei_att.global.attributes, tei_att.written.attributes, tei_macro.paraContent } |
| <secl> (secluded text) Secluded. Marks text present in the source which the editor believes to be genuine but out of its original place (which is unknown). [11.3.1.7. Text Omitted from or Supplied in the Transcription] | |||||||
| Module | transcr | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||
| Example | <rdg source="#Pescani"> <secl> <l n="15" xml:id="l15">Alphesiboea suos ulta est pro coniuge fratres,</l> <l n="16" xml:id="l16">sanguinis et cari vincula rupit amor.</l> </secl> </rdg> <note>secl. Pescani</note> | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element secl { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, attribute reason { list { teidata.word+ } }?, tei_macro.paraContent } | ||||||
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.written.attributes, tei_att.notated.attributes, tei_macro.paraContent } |
| <settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names] | |||||||||||
| Module | namesdates | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msIdentifier provenance repository support verse: rhyme | ||||||||||
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Example | <placeName> <settlement type="town">Glasgow</settlement> <region>Scotland</region> </placeName> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element settlement { tei_att.global.attributes, tei_att.naming.attributes, tei_att.typed.attributes, tei_att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, tei_macro.phraseSeq } | ||||||||||
| <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 head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_att.written.attributes, tei_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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 { tei_att.global.attributes, tei_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 { tei_att.global.attributes, tei_att.declarable.attributes, ( tei_model.pLike+ | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+ ) } |
| <space> (space) indicates the location of a significant space in the text. [11.4.1. Space] | |||||||||||||||||||
| Module | transcr | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||||||||
| May contain | core: desc | ||||||||||||||||||
| Note | This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like. | ||||||||||||||||||
| Example | By god if wommen had writen storyes As <space quantity="7" unit="minims"/> han within her oratoryes | ||||||||||||||||||
| Example | στρατηλάτ<space quantity="1" unit="chars"/>ου | ||||||||||||||||||
| Content model | <content> | ||||||||||||||||||
| Schema Declaration | element space { tei_att.global.attribute.xmlid, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.xmlspace, tei_att.global.rendition.attribute.rend, tei_att.global.linking.attribute.corresp, tei_att.global.linking.attribute.next, tei_att.global.linking.attribute.prev, tei_att.global.analytic.attribute.ana, tei_att.global.facs.attribute.facs, tei_att.global.change.attribute.change, tei_att.global.responsibility.attribute.cert, tei_att.global.source.attribute.source, tei_att.typed.attributes, tei_att.dimensions.attributes, attribute resp { list { teidata.pointer+ } }?, attribute dim { "horizontal" | "vertical" }?, ( tei_model.descLike | tei_model.certLike )* } | ||||||||||||||||||
| <span> associates an interpretative annotation directly with a span of text. [17.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 head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||
| May contain | |||||||||||||
| Example | <p xml:id="para2">(The "aftermath" starts here)</p> <p xml:id="para3">(The "aftermath" continues here)</p> <p xml:id="para4">(The "aftermath" ends in this paragraph)</p> <!-- ... --> <span from="#para2" to="#para4" type="structure">aftermath</span> | ||||||||||||
| Schematron | <sch:report test="@from and @target">Only one of the attributes @target and @from may be supplied on <sch:name/> </sch:report> | ||||||||||||
| Schematron | <sch:report test="@to and @target">Only one of the attributes @target and @to may be supplied on <sch:name/> </sch:report> | ||||||||||||
| Schematron | <sch:report test="@to and not(@from)">If @to is supplied on <sch:name/>, @from must be supplied as well</sch:report> | ||||||||||||
| Schematron | <sch:report test="contains(normalize-space(@to),' ') or contains(normalize-space(@from),' ')">The attributes @to and @from on <sch:name/> may each contain only a single value</sch:report> | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element span { tei_att.global.attributes, tei_att.interpLike.attributes, tei_att.pointing.attributes, attribute from { teidata.pointer }?, attribute to { teidata.pointer }?, tei_macro.phraseSeq.limited } | ||||||||||||
| <standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | textstructure: TEI |
| May contain | analysis: span core: bibl biblStruct index note header: listChange linking: seg msdescription: msDesc textcrit: listApp transcr: listTranspose zone |
| Example | This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF). <TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <!-- ... --> </teiHeader> <text> <body> <!-- ... --> <p> <w xml:id="w51">I</w> <w xml:id="w52">wanna</w> <w xml:id="w53">put</w> <w xml:id="w54">up</w> <w xml:id="w55">new</w> <w xml:id="w56">wallpaper</w> <pc>.</pc> </p> <!-- ... --> </body> </text> <standOff type="morphosyntax"> <spanGrp type="wordForm"> <span ana="#fs01" target="#w51"/> <span ana="#fs02" target="#w52"/> <span ana="#fs03" target="#w52"/> <span ana="#fs04" target="#w53 #w54"/> <span ana="#fs05" target="#w55"/> <span ana="#fs06" target="#w56"/> </spanGrp> <fs xml:id="fs01"> <f name="lemma"> <string>I</string> </f> <f name="pos"> <symbol value="PP"/> </f> </fs> <fs xml:id="fs02"> <f name="lemma"> <string>want</string> </f> <f name="pos"> <symbol value="VBP"/> </f> </fs> <fs xml:id="fs03"> <f name="lemma"> <string>to</string> </f> <f name="pos"> <symbol value="TO"/> </f> </fs> <fs xml:id="fs04"> <f name="lemma"> <string>put up</string> </f> <f name="pos"> <symbol value="VB"/> </f> </fs> <fs xml:id="fs05"> <f name="lemma"> <string>new</string> </f> <f name="pos"> <symbol value="JJ"/> </f> </fs> <fs xml:id="fs06"> <f name="lemma"> <string>wallpaper</string> </f> <f name="pos"> <symbol value="NN"/> </f> </fs> </standOff> </TEI> |
| Example | This example shows an encoding of contextual information which is referred to from the main text. <TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <!-- ... --> </teiHeader> <standOff> <listPlace> <place xml:id="LATL"> <placeName>Atlanta</placeName> <location> <region key="US-GA">Georgia</region> <country key="USA">United States of America</country> <geo>33.755 -84.39</geo> </location> <population quantity="489359" source="https://www.biggestuscities.com/city/atlanta-georgia" type="interpolatedCensus" when="1963"/> </place> <place xml:id="LBHM"> <placeName>Birmingham</placeName> <location> <region key="US-AL">Alabama</region> <country key="USA">United States of America</country> <geo>33.653333 -86.808889</geo> </location> <population quantity="332891" source="https://www.biggestuscities.com/city/birmingham-alabama" type="interpolatedCensus" when="1963"/> </place> </listPlace> </standOff> <text> <body> <!-- ... --> <p>Moreover, I am <choice> <sic>congnizant</sic> <corr>cognizant</corr> </choice> of the interrelatedness of all communities and <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We <lb/>are caught in an inescapable network of mutuality, tied in a single garment <lb/>of destiny. Whatever affects one directly affects all indirectly. Never <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled> <lb/>idea. Anyone who lives inside the United States can never be considered <lb/>an outsider anywhere in this country.</p> <!-- ... --> </body> </text> </TEI> |
| Schematron | <sch:assert test="@type or not(ancestor::tei:standOff)">This <sch:name/> element must have a @type attribute, since it is nested inside a <sch:name/> </sch:assert> |
| Content model | <content> |
| Schema Declaration | element standOff { tei_att.global.attributes, tei_att.typed.attributes, tei_att.declaring.attributes, tei_model.standOffPart+ } |
| <supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |||||||
| Module | transcr | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||
| Note | The <damage>, gap, del, unclear and supplied elements may be closely allied in use. See section 11.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. | ||||||
| Example | I am dr Sr yr <supplied reason="illegible" source="#amanuensis_copy">very humble Servt</supplied> Sydney Smith | ||||||
| Example | <supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar | ||||||
| Content model | <content> | ||||||
| Schema Declaration | element supplied { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, attribute reason { list { teidata.word+ } }?, tei_macro.paraContent } | ||||||
| <support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: supportDesc |
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig p pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <objectDesc form="roll"> <supportDesc> <support> Parchment roll with <material>silk</material> ribbons. </support> </supportDesc> </objectDesc> |
| Content model | <content> |
| Schema Declaration |
element support { tei_att.global.attributes, tei_macro.specialPara } |
| <supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description] | |||||||||
| Module | msdescription | ||||||||
| Attributes |
| ||||||||
| Contained by | msdescription: objectDesc | ||||||||
| May contain | |||||||||
| Example | <supportDesc> <support> Parchment roll with <material>silk</material> ribbons. </support> </supportDesc> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element supportDesc { tei_att.global.attributes, attribute material { "paper" | "parch" | "mixed" | teidata.enumerated }?, ( tei_model.pLike+ | ( tei_support?, tei_extent?, tei_foliation*, tei_collation?, condition? ) ) } | ||||||||
| <surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||||||||
| Module | transcr | ||||||||||||||
| Attributes |
| ||||||||||||||
| Contained by | |||||||||||||||
| May contain | |||||||||||||||
| Note | The surface element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc. The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high. The surface element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every zone element contained by this element are to be understood with reference to the same grid. Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the <surfaceGrp> element. | ||||||||||||||
| Example | <facsimile> <surface lrx="200" lry="300" ulx="0" uly="0"> <graphic url="Bovelles-49r.png"/> </surface> </facsimile> | ||||||||||||||
| Content model | <content> | ||||||||||||||
| Schema Declaration | element surface { tei_att.global.attributes, tei_att.coordinated.attributes, tei_att.declaring.attributes, tei_att.typed.attributes, attribute attachment { teidata.enumerated }?, attribute flipping { teidata.truthValue }?, ( ( tei_model.global | tei_model.labelLike | tei_model.graphicLike )*, ( ( tei_zone | line | path | tei_surface | surfaceGrp ), tei_model.global* )* ) } | ||||||||||||||
| <surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Example | <surname type="combine">St John Stevas</surname> |
| Content model | <content> |
| Schema Declaration | element surname { tei_att.global.attributes, tei_att.personal.attributes, tei_att.typed.attributes, tei_macro.phraseSeq } |
| <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 15.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: TEI |
| 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 { tei_att.global.attributes, tei_att.typed.attributes, ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) ) } |
| <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 15.1. Varieties of Composite Text] | |
| Module | header |
| Attributes |
|
| Contained by | textstructure: TEI |
| 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 { tei_att.global.attributes, ( tei_fileDesc, tei_model.teiHeaderPart*, tei_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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi index item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material provenance repository support verse: rhyme |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| 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 rend="sc" xml:id="TDPV1">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 { tei_att.global.attributes, tei_att.declaring.attributes, tei_att.pointing.attributes, tei_att.typed.attributes, tei_att.canonical.attributes, tei_att.sortable.attributes, tei_att.cReferencing.attributes, tei_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 15.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: TEI |
| 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 { tei_att.global.attributes, tei_att.declaring.attributes, tei_att.typed.attributes, tei_att.written.attributes, ( tei_model.global*, ( tei_front, tei_model.global* )?, ( tei_body | group ), tei_model.global*, ( tei_back, tei_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 | header: keywords |
| 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 { tei_att.global.attributes, tei_att.declarable.attributes, ( classCode | catRef | tei_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 | core: abbr add addrLine author bibl biblScope corr date del desc editor emph expan foreign head hi item l measure monogr note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItemStruct provenance repository support verse: rhyme | ||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||||||||
| 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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.canonical.attributes, tei_att.datable.attributes, attribute type { teidata.enumerated }?, attribute level { "a" | "m" | "j" | "s" | "u" }?, tei_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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, attribute type { teidata.enumerated }?, ( tei_model.global*, tei_model.titlepagePart, ( tei_model.titlepagePart | tei_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 | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| 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 { tei_att.global.attributes, tei_att.typed.attribute.subtype, attribute type { "main" | "sub" | "alt" | "short" | "desc" | teidata.enumerated }?, tei_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 { tei_att.global.attributes, ( tei_title+, tei_model.respLike* ) } |
| <transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [11.3.4.5. Transpositions] | |
| Module | transcr |
| Attributes |
|
| Contained by | transcr: listTranspose |
| May contain | core: ptr |
| Note | Transposition is usually indicated in a document by a metamark such as a wavy line or numbering. The order in which ptr elements appear within a transpose element should correspond with the desired order, as indicated by the metamark. |
| Example | <transpose> <ptr target="#ib02"/> <ptr target="#ib01"/> </transpose> The transposition recorded here indicates that the content of the element with identifier |
| Content model | <content> |
| Schema Declaration |
element transpose { tei_att.global.attributes, ( tei_ptr, tei_ptr, tei_ptr* ) } |
| <unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. 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 head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index l lb lg measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||||||||
| 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 21. Certainty, Precision, and Responsibility. The <damage>, gap, del, unclear and supplied elements may be closely allied in use. See section 11.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 11.3.2.1. Document Hands. | ||||||||||||||||||||
| Example | <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u> | ||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||
| Schema Declaration | element unclear { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.dimensions.attributes, attribute reason { list { ( "illegible" | "inaudible" | "faded" | "background_noise" | "eccentric_ductus" | teidata.enumerated )+ } }?, attribute agent { teidata.enumerated }?, tei_macro.paraContent } | ||||||||||||||||||||
| <undo> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications] | |||||||
| Module | transcr | ||||||
| Attributes |
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor emph expan foreign head hi item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme | ||||||
| May contain | Empty element | ||||||
| Example | <line>This is <del change="#s2" rend="overstrike"> <seg xml:id="undo-a">just some</seg> sample <seg xml:id="undo-b">text</seg>, we need</del> <add change="#s2">not</add> a real example.</line> <undo change="#s3" rend="dotted" target="#undo-a #undo-b"/> This encoding represents the following sequence of events:
| ||||||
| Content model | <content> | ||||||
| Schema Declaration | element undo { tei_att.global.attributes, tei_att.spanning.attributes, tei_att.transcriptional.attributes, tei_att.dimensions.attributes, attribute target { list { teidata.pointer+ } }?, empty } | ||||||
| <variantEncoding> (variant encoding) declares the method used to encode text-critical variants. [12.1.1. The Apparatus Entry] | |||||||||||||||||||||||
| Module | textcrit | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | header: encodingDesc | ||||||||||||||||||||||
| May contain | Empty element | ||||||||||||||||||||||
| Example | <variantEncoding location="external" method="location-referenced"/> | ||||||||||||||||||||||
| Content model | <content> | ||||||||||||||||||||||
| Schema Declaration | element variantEncoding { tei_att.global.attributes, attribute method { "location-referenced" | "double-end-point" | "parallel-segmentation" }, attribute location { "internal" | "external" }, empty } | ||||||||||||||||||||||
| <w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.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 head hi item l measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr header: change distributor extent handNote licence msdescription: accMat acquisition collation decoNote filiation foliation layout material provenance support verse: rhyme |
| 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 { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.linguistic.attributes, tei_att.notated.attributes, ( text | tei_model.gLike | tei_seg | tei_w | m | tei_c | tei_pc | tei_model.global | tei_model.lPart | tei_model.hiLike | tei_model.pPart.edit )* } |
| <wit> (wit) contains a list of one or more sigla of witnesses attesting a given reading, in a textual variation. [12.1.4. Witness Information] | |
| Module | textcrit |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr add address choice cit corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data |
| Note | This element represents the same information as that provided by the wit attribute of the reading; it may be used to record the exact form of the sigla given in the source edition, when that is of interest. |
| Example | <rdg wit="#El #Hg">Experience</rdg> <wit>Ellesmere, Hengwryt</wit> |
| Content model | <content> |
| Schema Declaration | element wit { tei_att.global.attributes, tei_att.rdgPart.attributes, tei_macro.phraseSeq } |
| <witDetail> (witness detail) gives further information about a particular witness, or witnesses, to a particular reading. [12.1. The Apparatus Entry, Readings, and Witnesses] | |||||||||||||||
| Module | textcrit | ||||||||||||||
| Attributes |
| ||||||||||||||
| Member of | |||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor emph expan foreign head hi imprint item l lg measure note num orig p pubPlace publisher q quote ref reg rs said sic soCalled term title unclear dictionaries: xr msdescription: accMat acquisition collation decoNote filiation foliation institution layout material msItem provenance repository support textstructure: back body byline closer dateline div docAuthor docImprint docTitle epigraph front opener salute signed text titlePage titlePart verse: rhyme | ||||||||||||||
| May contain | core: abbr add address bibl choice corr date del emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q ref reg rs sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||||||
| Note | The witDetail element was formerly permitted anywhere that note could appear, but since it should only be used in association with <lem> and rdg, it is recommended that it be placed immediately following the reading that it modifies, in the same app. A witDetail without a target attribute should be assumed to refer to the closest preceding <lem> or rdg. | ||||||||||||||
| Example | <app type="substantive"> <lem wit="#El #HG" xml:id="W026x">Experience</lem> <rdg wit="#Ha4">Experiens</rdg> <witDetail resp="#PR" target="#W026x" type="presentation" wit="#El">Ornamental capital.</witDetail> </app> | ||||||||||||||
| Content model | <content> | ||||||||||||||
| Schema Declaration | element witDetail { tei_att.global.attributes, tei_att.placement.attributes, tei_att.pointing.attributes, tei_att.typed.attribute.subtype, attribute type { teidata.enumerated }?, attribute wit { list { teidata.pointer+ } }, ( text | tei_model.gLike | tei_model.phrase | tei_model.global | tei_bibl )* } | ||||||||||||||
| <witness> (witness) contains either a description of a single witness referred to within the critical apparatus, or a list of witnesses which is to be referred to by a single sigil. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
| Module | textcrit |
| Attributes |
|
| Contained by | — |
| May contain | |
| Note | The content of the witness element may give bibliographic information about the witness or witness group, or it may be empty. |
| Example | <listWit> <witness xml:id="EL">Ellesmere, Huntingdon Library 26.C.9</witness> <witness xml:id="HG">Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D</witness> <witness xml:id="RA2">Bodleian Library Rawlinson Poetic 149 (see further <ptr target="http://www.examples.com/MSdescs#MSRP149"/>)</witness> </listWit> |
| Content model | <content> |
| Schema Declaration | element witness { tei_att.global.attributes, tei_att.sortable.attributes, ( text | tei_model.limitedPhrase | tei_model.inter | tei_note | object )* } |
| <xr> (cross-reference phrase) contains a phrase, sentence, or icon referring the reader to some other location in this or another text. [9.3.5.3. Cross-References to Other Entries] | |||||||||||
| Module | dictionaries | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: cit | ||||||||||
| May contain | core: abbr add address bibl biblStruct choice cit corr date del desc emph expan foreign gap gb graphic hi index lb measure milestone note num orig pb ptr q quote ref reg rs said sic soCalled term title unclear header: idno transcr: addSpan am delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space supplied undo verse: rhyme character data | ||||||||||
| Note | May contain character data and phrase-level elements; usually contains a ref or a ptr element. This element encloses both the actual indication of the location referred to, which may be tagged using the ref or ptr elements, and any accompanying material which gives more information about why the reader is being referred there. | ||||||||||
| Example | <entry> <form> <orth>lavage</orth> </form> <etym>[Fr. < <mentioned>laver</mentioned>; L. <mentioned>lavare</mentioned>, to wash; <xr>see <ref>lather</ref> </xr>]. </etym> </entry> | ||||||||||
| Example | <entry> <form> <orth>lawful</orth> </form> <xr type="syn">SYN. see <ref>legal</ref> </xr> </entry> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element xr { tei_att.global.attributes, tei_att.typed.attribute.subtype, tei_att.lexicographic.attributes, attribute type { teidata.enumerated }?, ( text | tei_model.gLike | tei_model.phrase | tei_model.inter | usg | lbl | tei_model.global )* } | ||||||||||
| <zone> defines any two-dimensional area within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||
| Module | transcr | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface. A graphic element contained by a zone represents the whole of the zone. A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface. A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element. | ||||||||
| Example | <surface lrx="0" lry="0" ulx="14.54" uly="16.14"> <graphic url="stone.jpg"/> <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/> </surface> This example defines a non-rectangular zone: see the illustration in section [ID PH-surfzone in TEI Guidelines]. | ||||||||
| Example | <facsimile> <surface lrx="400" lry="280" ulx="50" uly="20"> <zone lrx="500" lry="321" ulx="0" uly="0"> <graphic url="graphic.png"/> </zone> </surface> </facsimile> This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains. | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element zone { tei_att.global.attributes, tei_att.coordinated.attributes, tei_att.typed.attributes, tei_att.written.attributes, attribute rotate { teidata.count }?, ( text | tei_model.gLike | tei_model.graphicLike | tei_model.global | tei_surface | tei_model.linePart )* } | ||||||||
| 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 [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] idno rs] addrLine |
| model.annotationLike groups elements used to represent annotations. [16.10. The standOff Container] | |
| Module | tei |
| Used by | |
| Members | note |
| 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 quote] said |
| 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 biblStruct msDesc |
| 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] availability bibl decoNote extent msIdentifier 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 am corr ex expan orig reg seg sic supplied unclear |
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.divPart [model.lLike [l] model.pLike [ab p] lg] model.entryLike model.inter [model.attributable [model.quoteLike [cit quote] said] model.biblLike [bibl biblStruct msDesc] model.egLike model.labelLike [desc] model.listLike [listApp] model.oddDecl model.stageLike] 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.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence. | |
| Module | tei |
| Used by | |
| Members | model.addressLike [address] model.dateLike [date] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] idno rs] note |
| model.correspDescPart groups together metadata elements for describing correspondence | |
| Module | tei |
| Used by | |
| Members | correspAction note |
| model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates] | |
| Module | tei |
| Used by | |
| Members | date |
| model.descLike groups elements which contain a description of their function. | |
| Module | tei |
| Used by | |
| Members | desc |
| 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 signed] model.divWrapper [byline dateline docAuthor 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 signed |
| 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 [ab p] lg |
| 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 [byline dateline docAuthor 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 | byline dateline docAuthor epigraph salute |
| 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 | emph foreign soCalled term title |
| model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | editorialDecl projectDesc variantEncoding |
| model.entryPart groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure] | |
| Module | tei |
| Used by | |
| Members | xr |
| 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 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 [addSpan app delSpan gap space witDetail] model.global.meta [index listTranspose span] model.milestoneLike [anchor fw gb lb milestone pb] model.noteLike [note] metamark |
| model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | addSpan app delSpan gap space witDetail |
| 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 listTranspose span |
| 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 | 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 [emph foreign 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 quote] said] model.biblLike [bibl biblStruct msDesc] model.egLike model.labelLike [desc] model.listLike [listApp] model.oddDecl model.stageLike |
| model.labelLike groups elements used to gloss or explain other parts of a document. | |
| Module | tei |
| Used by | |
| Members | desc |
| 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 [emph foreign soCalled term title] model.hiLike [hi q] model.pPart.data [model.addressLike [address] model.dateLike [date] model.measureLike [measure num] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] idno rs] ] model.pPart.editorial [abbr am choice ex expan] model.pPart.msdesc [locus material] model.phrase.xml model.ptrLike [ptr ref] |
| model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element. | |
| Module | tei |
| Used by | |
| Members | model.hiLike [hi q] add c choice del handShift mod pc redo restore retrace seg unclear undo w zone |
| model.listLike groups list-like elements. [3.8. Lists] | |
| Module | tei |
| Used by | |
| Members | listApp |
| model.lLike groups elements representing metrical components such as verse lines. | |
| Module | tei |
| Used by | |
| Members | l |
| model.lPart groups phrase-level elements which may appear within verse only. [6.2. Components of the Verse Line] | |
| Module | tei |
| Used by | |
| Members | rhyme |
| 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 | measure 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 fw gb 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 [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] 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 | persName |
| 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.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names] | |
| Module | namesdates |
| Used by | |
| Members | addName forename nameLink surname |
| 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 [graphic] model.highlighted [model.emphLike [emph foreign soCalled term title] model.hiLike [hi q] ] model.lPart [rhyme] model.pPart.data [model.addressLike [address] model.dateLike [date] model.measureLike [measure num] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] idno rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan] model.pPart.transcriptional [add corr del handShift mod orig redo reg restore retrace secl sic supplied unclear undo] ] model.pPart.msdesc [locus material] model.phrase.xml model.ptrLike [ptr ref] model.ptrLike.form model.segLike [c pc s seg w] model.specDescLike |
| Note | This class of elements can occur within paragraphs, list items, lines of verse, etc. |
| model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source. | |
| Module | msdescription |
| Used by | |
| Members | accMat bindingDesc handDesc objectDesc |
| model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names] | |
| Module | tei |
| Used by | |
| Members | placeName settlement |
| model.placeStateLike groups elements which describe changing states of a place. | |
| Module | tei |
| Used by | |
| Members | model.placeNamePart [placeName settlement] |
| 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 | byline dateline docAuthor 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] model.measureLike [measure num] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart [addName forename nameLink surname] model.placeStateLike [model.placeNamePart [placeName settlement] ] 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 am choice ex expan] model.pPart.transcriptional [add corr del handShift mod orig redo reg restore retrace secl sic supplied unclear undo] |
| 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 am choice ex expan |
| model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description] | |
| Module | tei |
| Used by | |
| Members | locus material |
| 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 handShift mod orig redo reg restore retrace secl sic supplied unclear undo |
| model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | correspDesc creation handNotes listTranspose 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 quote |
| model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
| Module | textcrit |
| Used by | |
| Members | rdg |
| Note | This class allows for variants of the rdg element to be easily created via TEI customizations. |
| model.rdgPart groups elements which mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses] | |
| Module | textcrit |
| Used by | |
| Members | wit |
| Note | These elements may appear anywhere within the elements <lem> and rdg, and also within any of their constituent elements. |
| 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 | facsimile standOff 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 |
| model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |
| Module | tei |
| Used by | |
| Members | c 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.standOffPart groups elements which may be used as children of standOff. | |
| Module | tei |
| Used by | |
| Members | model.annotationLike [note] model.biblLike [bibl biblStruct msDesc] model.entryLike model.global.meta [index listTranspose span] model.listLike [listApp] listChange seg zone |
| 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 | byline docAuthor docImprint docTitle epigraph graphic 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 said] 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 said | ||||||||||
| 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 | gb 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. [13.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | att.naming [att.personal [addName forename persName placeName surname] author editor institution pubPlace repository rs settlement] authority correspDesc date distributor docAuthor docTitle material publisher term 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.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system. | |||||||||||||||||||||||||||||||||||||
| Module | transcr | ||||||||||||||||||||||||||||||||||||
| Members | surface zone | ||||||||||||||||||||||||||||||||||||
| 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 | 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 13.4. Dates] | |||||||
| Module | tei | ||||||
| Members | acquisition author binding change creation date editor idno licence persName placeName provenance settlement 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.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.datable [acquisition author binding change creation date editor idno licence persName placeName provenance settlement title] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||
| Members | att.datable [acquisition author binding change creation date editor idno licence persName placeName provenance settlement title] | ||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||
| 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 ISO 8601:2004, using the Gregorian calendar. If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is, <date dur-iso="P8D" when-iso="2007-06-01"/> indicates the same time period as <date when-iso="2007-06-01/P8D"/> In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading. | ||||||||||||||||||||||||||||||||||
| 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 13.4. Dates] | |||||||||||||
| Module | tei | ||||||||||||
| Members | att.datable [acquisition author binding change creation date editor idno licence persName placeName provenance settlement title] | ||||||||||||
| Attributes |
| ||||||||||||
| Schematron | <sch:rule context="tei:*[@when]"> <sch:report role="nonfatal" test="@notBefore|@notAfter|@from|@to">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 role="nonfatal" test="@notBefore">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule> | ||||||||||||
| Schematron | <sch:rule context="tei:*[@to]"> <sch:report role="nonfatal" test="@notAfter">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. [9.5.2. Lexical View 18.3. Other Atomic Feature Values] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | att.lexicographic [xr] att.segLike [c pc s seg w] | ||||||||||||||||||
| 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 datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" name="POS"> <symbol value="NN" valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/> </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 fVal="#commonNoun" name="POS"/> <!-- ... --> </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 datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" value="NN" xml:id="commonNoun"/> <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae" value="NP" xml:id="properNoun"/> <!-- ... --> </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 datcat="https://universaldependencies.org/u/dep/index.html" xml:id="UD-SYN"> <desc> <term>UD syntactic relations</term> </desc> <category valueDatcat="https://universaldependencies.org/u/dep/acl.html" xml:id="acl"> <catDesc> <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc> </category> <category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html" xml:id="acl_relcl"> <catDesc> <term>acl:relcl</term>: relative clause modifier</catDesc> </category> <category valueDatcat="https://universaldependencies.org/u/dep/advcl.html" xml:id="advcl"> <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 datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545" value="NN"/> <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae" value="NP"/> <!-- ... --> </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 valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025" xml:id="domain.medical_and_health_sciences.medicine"> <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. [15.3. Associating Contextual Information with a Text] | |||||||||
| Module | tei | ||||||||
| Members | availability bibl biblStruct correspDesc editorialDecl listApp normalization projectDesc sourceDesc textClass | ||||||||
| Attributes |
| ||||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.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. [15.3. Associating Contextual Information with a Text] | |||||||
| Module | tei | ||||||
| Members | ab back body div facsimile front graphic lg msDesc p ptr ref standOff surface term text | ||||||
| Attributes |
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. | ||||||
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | add addSpan date del delSpan ex gap mod redo restore retrace secl space supplied unclear undo | ||||||||||||||||||||||||||||||||||||||
| 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 biblStruct change msDesc revisionDesc | ||||||||
| Attributes |
| ||||||||
| Example | <revisionDesc status="published"> <change status="published" when="2010-10-21"/> <change status="cleared" when="2010-10-02"/> <change status="embargoed" when="2010-08-02"/> <change status="frozen" when="2010-05-01" who="#MSM"/> <change status="draft" when="2010-03-01" who="#LB"/> </revisionDesc> | ||||||||
| att.edition provides attributes identifying the source edition from which some encoded feature derives. | |||||||||||||
| Module | tei | ||||||||||||
| Members | gb 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 edRef="#stapledon1968" n="411"/>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 edRef="#stapledon1937" n="291"/>sciousness;</p> | ||||||||||||
| att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | att.transcriptional [add addSpan del delSpan mod redo restore retrace undo] am corr date ex expan gap persName placeName reg secl supplied 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.enjamb (enjambement) provides attributes that may be used to indicate enjambement of the parent element. [6.2. Components of the Verse Line] | |||||||||||
| Module | verse | ||||||||||
| Members | l | ||||||||||
| Attributes |
| ||||||||||
| 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 [c pc s seg w] ab 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 ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone | ||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||
| att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated. | |||||||
| Module | transcr | ||||||
| Members | att.global [TEI ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||
| Attributes |
| ||||||
| att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles] | |||||||
| Module | transcr | ||||||
| Members | att.global [TEI ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||
| Attributes |
| ||||||
| att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||
| Members | att.global [TEI ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||||||||||||||||||||||
| 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 ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||||||
| 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 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.global [TEI ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||||||||||
| Attributes |
| ||||||||||||||
| Example | Blessed are the <choice> <sic>cheesemakers</sic> <corr cert="high" resp="#editor">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 ab abbr accMat acquisition add addName addSpan addrLine address am anchor app author authority availability back bibl biblScope biblStruct binding bindingDesc body byline c change choice cit closer collation corr correspAction correspDesc creation date dateline decoNote del delSpan desc distributor div docAuthor docImprint docTitle editor editorialDecl emph encodingDesc epigraph ex expan extent facsimile fileDesc filiation foliation foreign forename front fw gap gb graphic handDesc handNote handNotes handShift head hi history idno imprint index institution item keywords l layout layoutDesc lb lg licence listApp listChange listTranspose locus material measure metamark milestone mod monogr msContents msDesc msIdentifier msItem msItemStruct nameLink normalization note notesStmt num objectDesc opener orig p pb pc persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher q quote rdg rdgGrp redo ref reg relatedItem repository restore retrace revisionDesc rhyme rs s said salute secl seg settlement sic signed soCalled sourceDesc space span standOff supplied support supportDesc surface surname teiHeader term text textClass title titlePage titlePart titleStmt transpose unclear undo variantEncoding w wit witDetail witness xr zone] | ||||||||||
| 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.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands] | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | handNote handShift | ||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
| Note | Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied. | ||||||||||||||||||||||||||||||||||||||
| att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses] | |||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||
| Members | span | ||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||
| att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [9.2. The Structure of Dictionary Entries] | |||||||||||||||||||||||||||||||||||||||||
| Module | dictionaries | ||||||||||||||||||||||||||||||||||||||||
| Members | xr | ||||||||||||||||||||||||||||||||||||||||
| 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.lexicographic [xr] 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. [17.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 17.4.2. Lightweight Linguistic Annotation for discussion. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| att.measurement provides attributes to represent a regularized or normalized measurement. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | measure | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@unitRef]"> <sch:report role="info" test="@unit">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule> | ||||||||||||||||||||||||||||||
| Note | This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system. <l>So weren't you gonna buy <measure commodity="ice cream" quantity="0.5" unit="gal">half a gallon</measure>, baby</l> <l>So won't you go and buy <measure commodity="ice cream" quantity="1.893" unit="L">half a gallon</measure>, baby?</l> The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters. | ||||||||||||||||||||||||||||||
| att.media provides attributes for specifying display and related properties of external media. | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | graphic | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| att.metrical defines a set of attributes that certain elements may use to represent metrical information. [6.4. Rhyme and Metrical Analysis] | |||||||||||||||||||||||||
| Module | verse | ||||||||||||||||||||||||
| Members | att.divLike [div lg] att.segLike [c pc s seg w] l | ||||||||||||||||||||||||
| 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.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements] | |||||||
| Module | msdescription | ||||||
| Members | msContents msItem msItemStruct | ||||||
| Attributes |
| ||||||
| att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content] | |||||||
| Module | msdescription | ||||||
| Members | msContents msItem msItemStruct quote | ||||||
| Attributes |
| ||||||
| Note | In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole. | ||||||
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.personal [addName forename persName placeName surname] author editor institution pubPlace repository rs settlement | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.notated provides attributes to indicate any specialised notation used for element content. | |||||||
| Module | tei | ||||||
| Members | c quote 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. [13.2.1. Personal Names] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | addName forename persName placeName surname | ||||||||||||||
| 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 11.3.1.4. Additions and Deletions] | |||||||||||||
| Module | tei | ||||||||||||
| Members | add addSpan fw head metamark note witDetail | ||||||||||||
| 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 | licence locus note ptr ref span term witDetail | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | att.dimensions [add addSpan date del delSpan ex gap mod redo restore retrace secl space supplied unclear undo] measure num | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Example | The MS. was lost in transmission by mail from <del rend="overstrike"> <gap atLeast="1" atMost="2" extent="one or two letters" reason="illegible" 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" commodity="currency" unit="USD">more than $120m</measure> in aid to Ukrainians. | ||||||||||||||||||||||||||||||
| att.rdgPart provides attributes to mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses] | |||||||
| Module | textcrit | ||||||
| Members | wit | ||||||
| Attributes |
| ||||||
| Note | These elements may appear anywhere within the elements <lem> and rdg, and also within any of their constituent elements. | ||||||
| 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. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |||||||||
| Module | tei | ||||||||
| Members | c 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. [9.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei | ||||||||||
| Members | bibl biblStruct correspAction idno item listApp listChange msDesc term witness | ||||||||||
| Attributes |
| ||||||||||
| att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes] | |||||||||
| Module | tei | ||||||||
| Members | addSpan delSpan gb index lb metamark milestone mod pb redo retrace undo | ||||||||
| 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.textCritical defines a set of attributes common to all elements representing variant readings in text critical work. [12.1. The Apparatus Entry, Readings, and Witnesses] | |||||||||||||||||||||||||||||||
| Module | textcrit | ||||||||||||||||||||||||||||||
| Members | rdg rdgGrp | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Note | This element class defines attributes inherited by rdg, <lem>, and rdgGrp. | ||||||||||||||||||||||||||||||
| 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. [11.3.1.4. Additions and Deletions] | |||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||
| Members | add addSpan del delSpan mod redo restore retrace undo | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.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 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | TEI ab abbr accMat add addName addSpan am anchor app bibl biblStruct c change cit corr correspAction correspDesc date decoNote del delSpan desc div filiation forename fw gb graphic head idno lb lg listApp listChange locus material measure milestone mod msDesc nameLink note num pb pc persName placeName provenance ptr quote ref reg relatedItem restore rhyme rs s seg settlement space standOff surface surname term text title titlePage titlePart w witDetail xr zone | ||||||||||||||||||
| 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 23.3.1.3. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
| att.witnessed provides attributes used to identify the witnesses supporting a particular reading in a critical apparatus. [12.1. The Apparatus Entry, Readings, and Witnesses] | |||||||||
| Module | textcrit | ||||||||
| Members | rdg | ||||||||
| Attributes |
| ||||||||
| 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.textCritical [rdg rdgGrp] att.transcriptional [add addSpan del delSpan mod redo restore retrace undo] ab closer div fw head hi note opener p salute seg signed text zone | ||||||
| Attributes |
| ||||||
| teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | tei_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 | tei_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 |
tei_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 | tei_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 | Element:
|
| Content model | <content> |
| Declaration | tei_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 | |
| Content model | <content> |
| Declaration | tei_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 | Element:
|
| Content model | <content> |
| Declaration | tei_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.numeric defines the range of attribute values used for numeric values. | |
| Module | tei |
| Used by | Element:
|
| Content model | <content> |
| Declaration |
tei_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 | tei_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" url="http://www.tei-c.org/logos/TEI-600.jpg" width="600px"/> </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 | tei_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.point defines the data type used to express a point in cartesian space. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
tei_teidata.point =
token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" } |
| Example | <facsimile> <surface lrx="400" lry="280" ulx="0" uly="0"> <zone points="220,100 300,210 170,250 123,234"> <graphic url="handwriting.png"/> </zone> </surface> </facsimile> |
| Note | A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not. |
| 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 |
tei_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 | tei_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 | tei_teidata.probCert = teidata.probability | teidata.certainty |
| teidata.replacement defines attribute values which contain a replacement template. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | tei_teidata.replacement = text |
| teidata.temporal.iso 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 international standard Data elements and interchange formats – Information interchange – Representation of dates and times. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
tei_teidata.temporal.iso =
xsd:date
| xsd:gYear
| xsd:gMonth
| xsd:gDay
| xsd:gYearMonth
| xsd:gMonthDay
| xsd:time
| xsd:dateTime
| token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" } |
| 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. For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format. |
| 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 | tei_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.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 | tei_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 | tei_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.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration |
tei_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 |
tei_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.xpath defines attribute values which contain an XPath expression. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | tei_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 | tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" ) |
| Note | In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
| macro.abContent (anonymous block content) defines the content of anonymous block elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | tei_macro.abContent = ( text | tei_model.paraPart | tei_ab )* |
| 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 | tei_macro.limitedContent = ( text | tei_model.limitedPhrase | tei_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 | tei_macro.paraContent = ( text | tei_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 |
tei_macro.phraseSeq =
(
text
| tei_model.gLike
| tei_model.attributable
| tei_model.phrase
| tei_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 | tei_macro.phraseSeq.limited = ( text | tei_model.limitedPhrase | tei_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 |
tei_macro.specialPara =
(
text
| tei_model.gLike
| tei_model.phrase
| tei_model.inter
| tei_model.divPart
| tei_model.global
)* |
| macro.xtext (extended text) defines a sequence of character data and gaiji elements. | |
| Module | tei |
| Used by | |
| Content model | <content> |
| Declaration | tei_macro.xtext = ( text | tei_model.gLike )* |
http://www.tei-c.org/ns/1.0