TEI Tite is a constrained customization of TEI designed for use when outsourcing production of TEI documents to vendors, who use some combination of OCR and keyboarding to produce encoded text. While the canonical version of Tite is maintained by the TEI Council, a derived version is used in the AccessTEI program.
TEI Tite is meant to express a transitional format for documents, not an archival one. A project outsourcing encoding of documents using Tite should convert Tite documents created by vendors into a more suitable format for long-term preservation, such as one of the encoding levels of Best Practices for TEI in Libraries or a project-specific TEI customization.
While Tite includes only a limited set of all of the elements in TEI, it should not be confused with TEI Lite, which also contains a subset of elements. What distinguishes Tite from other TEI customizations is that Tite is meant to prescribe exactly one way of encoding a particular feature of a document in as many cases as possible, ensuring that any two encoders would produce the same XML document for a source document.
This document specifies how a source document should be encoded using TEI Tite. Its organizing model is roughly the structure of a TEI document itself, and it proceeds from high-level features to low, starting with general requirements, text structure, directions on when to group texts, considerations about type of text (genre and format), continuing down to instructions on marking phrase-level features, reference systems, and so forth. In its original ODD (one document does-it-all) format, this document can generate everything necessary for working in TEI Tite: both documentation (this Tite-specific prose as well as the full technical documentation for each of its elements) and schemas in either W3C Schema, RELAX NG, or XML DTD. Software utilities, including the Roma web tool, can generate these.
Tite uses a subset of the TEI's elements, except for a few shortcut elements for the convenience of use by vendors (b, i, ul, sup, sub, smcap, colShift and ornament) which can be transformed to normal TEI elements. Tite is also not a TEI-conformant customization since it breaks the TEI Abstract Model by omitting <teiHeader> for encoder convenience. That is, Tite was created primarily by removing elements and attributes from the TEI, and not from extensive modification. As a TEI customization, Tite inherits TEI semantics, and ambiguity in this specification should be resolved with reference to the TEI Guidelines. What makes Tite distinct is that where the TEI in general is famously tolerant of multiple methods of encoding a given feature, Tite seeks uniformity of encoding through constraint, via its stripped-down tag set and via this specification.
Tite can be used to encode printed prose, poetry, drama, newspapers, and anything else which can be described with the basic TEI building-blocks of divisions, paragraphs, line groups, and speeches.
In this documentation, document refers generally to the item (book, pamphlet, newspaper, etc.) to be encoded and text to either linguistic (as opposed to graphic) material or a logically distinct literary unit.
All printed material should be captured: all text (that is, printed characters) should be transcribed and the presence of graphical items or other non-transcribable elements should be indicated with markup.
A distinction should be maintained in the electronic transcription between end-of-line or ‘soft’ hyphens (an artifact of page layout) and ‘hard’ hyphens (a linguistic feature). The former should be transcribed as the SOFT HYPHEN (U+00AD) character; the latter, as the HYPHEN-MINUS (U+002D) character generally available on Western keyboards. In the rare case of coincidence of the two types — where a word that is normally hyphenated is split across a line break at its hyphen — the hyphen should be considered hard, and transcribed as the HYPHEN-MINUS.
Characters should be encoded in UTF-8. For characters not easily input from the keyboard, use hexadecimal numeric entities (e.g. é, the small latin e with acute accent, is represented as é).
The standard for accuracy of transcription should be at least 99.99% (1 error in 10,000 characters). The sample size for verification will be 5% of the total text.
Almost surely, difficult encoding situations will arise whose resolution may not be covered by this documentation or the TEI Guidelines. In such cases, it is important to document the markup choices that are made. To this end each encoded file should be accompanied by a document with such notes. These notes should reference features of a document that seem remarkable to encoders and how these were handled by encoders.
The text's xml:id attribute should contain a unique identifier for the document being encoded.
Tite omits the <teiHeader> element as a convenience to transcribers. This departs from normal TEI practice, which requires <TEI> as the root element, containing <teiHeader> and text elements. In order to bring a document encoded in TEI Tite into adherence with the TEI Abstract Model, projects should add a teiHeader before engaging in post-transcription processing.
In cases where a document appears to contain a group of texts but the above condition is not met, encode each unit as a (numbered) <div> with an appropriate type attribute.
Tite uses numbered divisions: div1 through div7, which stand for levels of nesting within a text. div1s nest inside or are contained by the front, body, and back elements, div2s nest inside or are contained by div1s, etc. The document's table of contents is often a good place to find cues about where structural divisions start and end; other cues can be blank pages, recurring typographical or ornamental features, or a numbering system ("Chapter 5" etc.). Also, the presence of a heading will often indicate the beginning of a division.
The type attribute should be used to express the type of division being marked. Where present, use a name for division type given in the document itself. Though any constrained enumerated list of type values will have to be determined on a job-by-job basis, some examples of appropriate division types are:
When a heading is present, encode it with the head element. If there is more than one heading at the beginning of a given division, encode each heading with its own head element, using the type attribute to distinguish them. Appropriate values are:
A divisional title is a page that resembles a half-title page: it displays the title or heading of a major structural unit on an otherwise blank page. Divisional titles should be encoded not with a separate <div> element, but as a head within the appropriate <div>. For half-title pages and similar fly-title pages see the section on Front Matter.
Another potential false indication of a new structural division is an ornament used as an informal division: a printer's ornament of some sort, a string of asterisks or periods, or a horizontal line. Mark these with the special ornament element. If the ornament is a horizontal line or printer's device or otherwise not transcribable, make the element empty and include an appropriate type attribute (line or ornament); if the ornament is made up of characters, transcribe the characters into the ornament's content.
Front and back matter should be encoded with the front and back elements, respectively. div1 elements should contain the major sections and should be characterized by type attribute values. The exception, however, is the title page, which should be encoded with the titlePage element and its children. The titlePart element should have a type attribute with one of the following values:
<titlePart type="volume"> should be used to encode volume information wherever it is found on the title page, even if it is separated from the other title information. The elements that make up the titlePage content model are: graphic, byline, epigraph, docTitle, titlePart, docAuthor, docEdition, docImprint, docDate, figure, ornament.
Information on the verso of the title page should be included as well (after a pb).
Common items to encode in front and back matter -- and therefore common type attribute values for front and back divisions are:
Half-title and fly-title pages may be encountered in the front matter. A half-title page precedes the title page proper and sometimes includes volume or series information; a fly-title page comes at the very end of the front matter, just before the body. In the case of half-titles, encode these as <div1 type="half-title"> (with titlePart elements as appropriate); in the case of fly-titles, encode them likewise with <div1 type="fly-title">, making sure to make the fly-title division the last part of the front matter (and not the first part of the body, as may seem reasonable as well).
Tite is equipped to support basic encoding of several types of text: in terms of genre, it supports prose, verse, and drama, and in terms of format, it supports books, newspapers, pamphlets, and other similar printed material. Tite has special elements for letters, verse, drama, and newspapers.
opener and closer are elements designed to encode the beginning and ending sections of letters, prefaces, diary entries, or other personal types of writing. Both elements contain:
opener contains the additional elements epigraph, argument, and byline. epigraph will often be useful in the context of a letter. When encoding an epigraph, make sure to encode the content as you would any other feature, marking line groups, bibliographical elements, etc.
argument and byline, however, are not intended specifically for use with letters:
All verse should be encoded within at least one lg element, even when there are no distinct stanzas or when the verse is interspersed with prose. If it is known, use the type attribute to express the type of line group. Sometimes within a poem there is a question about what should be tagged as a lg or as a separate <div>. As a rough rule of thumb, if there is a title accompanying the division, use the <div> element; otherwise, use lg.
AS virtuous men pass mildly away, And whisper to their souls to go, Whilst some of their sad friends do say, "Now his breath goes," and some say, "No." ⚓should be encoded as
The standard TEI elements for drama should be used: sp, stage, speaker. If the who attribute is used on sp, also transcribe who is given as the speaker, in whatever form it is written, in the speaker element. Short pieces of stage direction that accompany the speaker designation may be included in the speaker element.
Scenes and acts should be encoded as appropriately nested <div> elements with type attributes of scene or act, respectively. Cast lists can likewise be encoded using <div> and type="castlist".
Prologues and epilogues can be treated as sps of their own, unless their structure would be better represented by nested <div> elements.
Tite includes the elements colShift and cb which are well suited for the multi-column layout of newspapers. Additional relevant elements are: ref, to encode a pointer to the continuation of a story in a different column or on a different page; and figure, to describe illustrations, advertisements, and cartoons.
If present, transcribe all quotation marks or other delimiters inside the q element.
Use the figure element to encode figures. If a figure has a heading or caption, encode it with the head element. If there is associated text, simply use a p to encode it.
Tables and lists are encoded as in the TEI Guidelines, but note the following.
If a cell in a table is a heading or a label, set the role attribute to label; if the cell contains data, there is no need to use role: data is the default. If a cell or row spans more than one column or row, use the rows or cols attributes set to the number of columns or rows that it spans.
If unsure about whether a structure is best encoded as a list or table, record it as a table only if it would not be properly understood without tabular layout.
Lists should be encoded as either sequences of <items> or label-item pairs. When items in the list contain a label, as in a gloss list, be sure to use the latter form.
Both the reference to the note in the running text and the note itself must be encoded. Use ptr or ref to encode the reference. If there is no reference in the text (often the case for marginal notes), supply a ptr element in a reasonable place in the text running beside the note. If there is a reference (number, symbol, etc.), use the ref element and include the reference text as the content. In both cases, a target attribute must be supplied which contains the xml:id value of the associated note.
When encoding the note itself with the note element, the xml:id and place attributes must be supplied. See the TEI documentation for acceptable values for place; the most common will be foot, end, margin-left (-right, -top, -bot).
Transcribe the note directly after it is referenced in the document. In the case of notes without explicit reference (pointed to with ptr), set the anchored attribute to false.
In rare cases where the logical identity of a block-level element is hard to discern, use the TEI element ab (anonymous block) instead of applying a p or <div> element. In these cases, be sure to document this decision in accompanying notes. Applying this element should be viewed as a last resort.
The gap element should be used when for some reason the document being transcribed contains illegible text (smudged, torn, missing, etc.) or something outside the scope of transcription for a given project: characters in an unsupported character set, for instance. gap indicates that something is omitted. When using gap, set the reason attribute to an appropriate value. (See <unclear> below.)
There are six elements in Tite that capture specific typographical features:
These mark the physical change, and are agnostic about a logical motivation for it. There are two exceptions to this approach, however: marking foreign words and titles. In the case of foreign words, use the foreign element; in the case of titles, use the title element only if certain that the word or phrase in question is a title. If a phrase is, say, italicized, but you are uncertain about its being a title, use the i element instead. Foreign words should be marked only if they are typographically distinguished from surrounding text.
In addition, the <handshift> element may be used within the body of a transcription to indicate where a change of hand is detected for whatever reason.
If there is a typographical feature not covered by the above elements, the TEI hi element is still available in Tite. Use it without a rend attribute.
For passages set off by quotation marks or another delimeter, use the q element, including the delimeter inside the tag.
If the alignment of an element seems remarkable, set the element's rend attribute to an appropriate value (normally center, right, left, etc.). However, when semantic already accounts for its cause, description of alignment is not necessary. Headings, for instance, do not need to be marked as being centered.
To indicate level of indentation (often in verse), use numerical ‘arguments’ to ‘indent’, as in indent(1), indent(-1), and so on.
The seg element is the phrase-level analogue to the ab element. If a phrase-level feature seems to be present but its identity is hard to fathom, use this element. This, again, is a last resort.
Alternately, when a passage of text is for some reason too hard to read, use the unclear element, setting the reason attribute to an appropriate value. When using unclear, surround the entire word with the tag if any part of it is unclear (not just the illegible letter, say).
For cases in which it is unknown which character a given glyph corresponds to, mark the glyph with the g element to indicate the uncertainty. By convention in Tite, g represents any unknown glyph; no ref attribute is necessary. Note that unknown glyphs are different from illegible text.
Encode page breaks (pb) at the start of each page, and encode breaks even for blank pages. If the page is numbered, include the page number as the value of the n attribute and, again, no matter where the page number is printed on the page, place the pb element at the ‘top.’
If marking column breaks, follow the same rules as for page breaks. Column breaks are imagined to appear at the top of the column, at the beginning of the column's text. The colShift element exists to record a change in columnar layout. If such a change occurs, mark the beginning of the new layout with colShift and supply the new number of columns as the value for the n attribute.
For many applications, it will not be important to capture line breaks in ordinary prose text, but in cases where they are purposeful (such as the layout of acrostics, or where a word is broken across a line), they should be captured using the lb element, placing it at the start of each line.
The Best Practices for TEI in Libraries ("BP") creates common definitions of ‘levels of encoding’ based on depth of markup applied. Because the levels of encoding provide a tremendously useful common set of terms, it's helpful to situate TEI Tite according to them.
Mapped to BP levels, TEI Tite would sit between Level 3 and Level 4: it requires use of all the elements from Level 3 plus additional ones, but requires fewer elements than Level 4. Relative to Level 3, ‘Simple Analysis,’ Tite
The most useful comparison for Tite is to Level 4 (‘Basic Content Analysis’), provides the most useful comparison. The folowing items represent instances where Tite is less ambitious than Level 4:
Bringing Tite-encoded documents up to BP Level 4 would simply require application of additional markup, not significant reworking of markup, and in that way Tite is compatible with the BP.
Do also keep in mind that Tite lacks both the <teiHeader> and root <TEI> element used in TEI-conformant documents.
| <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. [17.3. Blocks, Segments, and Anchors] | |
| Module | linking |
| Member of | |
| Contained by | |
| May contain | |
| 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 type="book" n="Genesis"> <div type="chapter" n="1"> <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:rule context="tei:ab"> <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> </sch:rule> |
| Content model | <content> |
| Schema Declaration |
element ab { macro.abContent } |
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a p. |
| Example | <choice> <expan>North Atlantic Treaty Organization</expan> <abbr cert="low">NorATO</abbr> <abbr cert="high">NATO</abbr> <abbr cert="high" xml:lang="fr">OTAN</abbr> </choice> |
| Example | <choice> <abbr>SPQR</abbr> <expan>senatus populusque romanorum</expan> </choice> |
| Content model | <content> |
| Schema Declaration |
element abbr { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | In a diplomatic edition attempting to represent an original source, the add element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended. In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of add may be appropriate, dependent on the editorial philosophy of the project. |
| Example | The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title. |
| Content model | <content> |
| Schema Declaration | element add { att.global.attributes, att.transcriptional.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc. |
| Example | Using just the elements defined by the core module, an address could be represented as follows: <address> <street>via Marsala 24</street> <postCode>40126</postCode> <name>Bologna</name> <name>Italy</name> </address> |
| Example | When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name: <address> <street>via Marsala 24</street> <postCode>40126</postCode> <settlement>Bologna</settlement> <country>Italy</country> </address> |
| Example | <address> <addrLine>Computing Center, MC 135</addrLine> <addrLine>P.O. Box 6998</addrLine> <addrLine>Chicago, IL 60680</addrLine> <addrLine>USA</addrLine> </address> |
| Example | <address> <country key="FR"/> <settlement type="city">Lyon</settlement> <postCode>69002</postCode> <district type="arrondissement">IIème</district> <district type="quartier">Perrache</district> <street> <num>30</num>, Cours de Verdun</street> </address> |
| Content model | <content> |
| Schema Declaration | element address { att.global.attributes, att.cmc.attributes, ( model.global*, ( ( model.addrPart, model.global* )+ ) ) } |
| <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: address |
| May contain | |
| Note | Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text. |
| Example | <address> <addrLine>Computing Center, MC 135</addrLine> <addrLine>P.O. Box 6998</addrLine> <addrLine>Chicago, IL</addrLine> <addrLine>60680 USA</addrLine> </address> |
| Example | <addrLine> <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine> |
| Content model | <content> |
| Schema Declaration |
element addrLine { att.global.attributes, macro.phraseSeq } |
| <argument> (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <argument> <p>Monte Video — Maldonado — Excursion to R Polanco — Lazo and Bolas — Partridges — Absence of Trees — Deer — Capybara, or River Hog — Tucutuco — Molothrus, cuckoo-like habits — Tyrant Flycatcher — Mocking-bird — Carrion Hawks — Tubes formed by Lightning — House struck</p> </argument> |
| Content model | <content> |
| Schema Declaration | element argument { att.global.attributes, att.cmc.attributes, ( ( model.global | model.headLike )*, ( ( model.common, model.global* )+ ) ) } |
| <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | core: bibl | ||||||||||
| May contain | |||||||||||
| Note | Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource. In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast. Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given. | ||||||||||
| Example | <author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author> <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author> <orgName key="BBC">British Broadcasting Corporation</orgName>: Radio 3 Network </author> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element author { att.global.attributes, att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, macro.phraseSeq } | ||||||||||
| <b> (bold) for capturing typographical feature: bold glyphs. | |
| Namespace | http://www.tei-c.org/ns/tite/1.0 |
| Module | derived-module-tei_tite |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Content model | <content> |
| Schema Declaration |
element b { att.global.attributes, macro.paraContent } |
| <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: floatingText text |
| May contain | |
| Note | Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical. |
| Example | <back> <div type="appendix"> <head>The Golden Dream or, the Ingenuous Confession</head> <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she had like to have been, too fond of Money <!-- .... --> </p> </div> <!-- ... --> <div type="epistle"> <head>A letter from the Printer, which he desires may be inserted</head> <salute>Sir.</salute> <p>I have done with your Copy, so you may return it to the Vatican, if you please; <!-- ... --> </p> </div> <div type="advert"> <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr Newbery's at the Bible and Sun in St Paul's Church-yard.</head> <list> <item n="1">The Christmas Box, Price 1d.</item> <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... --> <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations, 10 Vol, Pr. bound 1l.</item> </list> </div> <div type="advert"> <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St. Paul's Church-Yard.</head> <list> <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d</item> <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... --> </list> </div> </back> |
| Content model | <content> |
| Schema Declaration | element back { att.global.attributes, ( ( model.frontPart | model.pLike.front | model.pLike | model.listLike | model.global )*, ( ( model.div1Like, ( model.frontPart | model.div1Like | model.global )* ) | ( model.divLike, ( model.frontPart | model.divLike | model.global )* ) )?, ( ( model.divBottomPart, ( model.divBottomPart | model.global )* )? ) ) } |
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl> |
| Example | <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> |
| Example | <bibl type="article" subtype="book_chapter" xml:id="carlin_2003"> <author> <name> <surname>Carlin</surname> (<forename>Claire</forename>)</name> </author>, <title level="a">The Staging of Impotence : France’s last congrès</title> dans <bibl type="monogr"> <title level="m">Theatrum mundi : studies in honor of Ronald W. Tobin</title>, éd. <editor> <name> <forename>Claire</forename> <surname>Carlin</surname> </name> </editor> et <editor> <name> <forename>Kathleen</forename> <surname>Wine</surname> </name> </editor>, <pubPlace>Charlottesville, Va.</pubPlace>, <publisher>Rookwood Press</publisher>, <date when="2003">2003</date>. </bibl> </bibl> |
| Content model | <content> |
| Schema Declaration | element bibl { att.global.attributes, att.declarable.attributes, att.typed.attributes, att.sortable.attributes, att.docStatus.attributes, att.cmc.attributes, ( text | model.gLike | model.highlighted | model.pPart.data | model.pPart.edit | model.segLike | model.ptrLike | model.biblPart | model.global )* } |
| <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: floatingText text |
| May contain | |
| Example | <body> <l>Nu scylun hergan hefaenricaes uard</l> <l>metudæs maecti end his modgidanc</l> <l>uerc uuldurfadur sue he uundra gihuaes</l> <l>eci dryctin or astelidæ</l> <l>he aerist scop aelda barnum</l> <l>heben til hrofe haleg scepen.</l> <l>tha middungeard moncynnæs uard</l> <l>eci dryctin æfter tiadæ</l> <l>firum foldu frea allmectig</l> <trailer>primo cantauit Cædmon istud carmen.</trailer> </body> |
| Content model | <content> |
| Schema Declaration | element body { att.global.attributes, ( model.global*, ( ( model.divTop, ( model.global | model.divTop )* )? ), ( ( model.divGenLike, ( model.global | model.divGenLike )* )? ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.divLike, ( model.global | model.divGenLike )* )+ ) | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ ) )? ) ), ( ( model.divBottom, model.global* )* ) ) } |
| <byline> (byline) contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the docAuthor element. |
| Example | <byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline> |
| Example | <byline>Written from her own MEMORANDUMS</byline> |
| Example | <byline>By George Jones, Political Editor, in Washington</byline> |
| Example | <byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline> |
| Content model | <content> |
| Schema Declaration | element byline { att.global.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | docAuthor | model.global )* } |
| <cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Empty element |
| Note | On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this cb element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The cb element is placed at the head of the column to which it refers. |
| Example | Markup of an early English dictionary printed in two columns: <pb/> <cb n="1"/> <entryFree> <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>: <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner sinks into the Ground, to find out and disappoint the Enemies Mines, or to prepare one</sense>. </entryFree> <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or <sense>lie groveling</sense>.</entryFree> <!-- remainder of column --> <cb n="2"/> <entryFree> <form>Wey</form>, <sense>the greatest Measure for dry Things, containing five Chaldron</sense>. </entryFree> <entryFree> <form>Whale</form>, <sense>the greatest of Sea-Fishes</sense>. </entryFree> |
| Content model | <content> |
| Schema Declaration | element cb { att.global.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <cell> (cell) contains one cell of a table. [15.1.1. TEI Tables] | |
| Module | figures |
| Attributes |
|
| Contained by | figures: row |
| May contain | |
| Example | <row> <cell role="label">General conduct</cell> <cell role="data">Not satisfactory, on account of his great unpunctuality and inattention to duties</cell> </row> |
| Content model | <content> |
| Schema Declaration | element cell { att.global.attributes, att.tableDecoration.attributes, macro.specialPara } |
| <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples] | |
| Module | core |
| Member of | |
| Contained by | |
| May contain | |
| Example | <cit> <quote>and the breath of the whale is frequently attended with such an insupportable smell, as to bring on disorder of the brain.</quote> <bibl>Ulloa's South America</bibl> </cit> |
| Example | <entry> <form> <orth>horrifier</orth> </form> <cit type="translation" xml:lang="en"> <quote>to horrify</quote> </cit> <cit type="example"> <quote>elle était horrifiée par la dépense</quote> <cit type="translation" xml:lang="en"> <quote>she was horrified at the expense.</quote> </cit> </cit> </entry> |
| Example | <cit type="example"> <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote> <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav" mimeType="audio/wav"/> <cit type="translation"> <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote> </cit> <cit type="translation"> <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote> </cit> </cit> |
| Content model | <content> |
| Schema Declaration | element cit { ( model.biblLike | model.egLike | model.entryPart | model.global | model.graphicLike | model.ptrLike | model.attributable | pc | 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 | |
| Example | <div type="letter"> <p> perhaps you will favour me with a sight of it when convenient.</p> <closer> <salute>I remain, &c. &c.</salute> <signed>H. Colburn</signed> </closer> </div> |
| Example | <div type="chapter"> <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p> <closer> <dateline> <name type="place">Trieste-Zürich-Paris,</name> <date>1914–1921</date> </dateline> </closer> </div> |
| Content model | <content> |
| Schema Declaration | element closer { att.global.attributes, att.written.attributes, att.cmc.attributes, ( text | model.gLike | signed | dateline | salute | model.phrase | model.global )* } |
| <colShift> (column shift) with the cols attribute is used to mark where a document changes columnar layout. | |||||||||||||
| Namespace | http://www.tei-c.org/ns/tite/1.0 | ||||||||||||
| Module | derived-module-tei_tite | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | Empty element | ||||||||||||
| Content model | <content> | ||||||||||||
| Schema Declaration | element colShift { att.global.attributes, attribute [http://www.tei-c.org/ns/tite/1.0]ed { teidata.word }?, attribute [http://www.tei-c.org/ns/tite/1.0]cols { teidata.count }?, empty } | ||||||||||||
| <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <date when="1980-02">early February 1980</date> |
| Example | Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date> |
| Example | <date when="1990-09">September 1990</date> |
| Content model | <content> |
| Schema Declaration | element date { att.global.attributes, att.datable.attributes, att.typed.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.global )* } |
| <dateline> (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <dateline>Walden, this 29. of August 1592</dateline> |
| Example | <div type="chapter"> <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p> <closer> <dateline> <name type="place">Trieste-Zürich-Paris,</name> <date>1914–1921</date> </dateline> </closer> </div> |
| Content model | <content> |
| Schema Declaration | element dateline { att.global.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.global | docDate )* } |
| <del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions. The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the gap tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the gap element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the unclear element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way. Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility). There is a clear distinction in the TEI between del and <surplus> on the one hand and gap or unclear on the other. del indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. gap or unclear, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription. |
| Example | <l> <del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del> weht der Wind </l> |
| Example | <del rend="overstrike"> <gap reason="illegible" quantity="5" unit="character"/> </del> |
| Content model | <content> |
| Schema Declaration | element del { att.global.attributes, att.transcriptional.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. | ||||||||||
| Example | Example of a desc element inside a documentation element. <dataSpec module="tei" ident="teidata.point"> <desc versionDate="2010-10-17" xml:lang="en">defines the data type used to express a point in cartesian space.</desc> <content> <dataRef name="token" restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/> </content> <!-- ... --> </dataSpec> | ||||||||||
| Example | Example of a desc element in a non-documentation element. <place xml:id="KERG2"> <placeName>Kerguelen Islands</placeName> <!-- ... --> <terrain> <desc>antarctic tundra</desc> </terrain> <!-- ... --> </place> | ||||||||||
| Schematron | A desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element. <sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element desc { att.global.attributes, att.cmc.attributes, attribute type { teidata.enumerated }?, macro.limitedContent } | ||||||||||
| <div1> (level-1 text division) contains a first-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div1 xml:id="levi" n="I" type="part"> <head>Part I: Of Man </head> <div2 xml:id="levi1" n="1" type="chapter"> <head>Chap. I. Of Sense </head> <p>Concerning the Thoughts of man... </p> </div2> </div1> <div1 xml:id="levii" n="II" type="part"> <head>Part II: Of Common-Wealth</head> </div1> |
| Content model | <content> |
| Schema Declaration | element div1 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div2Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div2Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div2> (level-2 text division) contains a second-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div1 |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div1 n="2" type="part"> <head>The Second Partition: The Cure of Melancholy</head> <div2 n="2.1" type="section"> <div3 n="2.1.1" type="member"> <div4 n="2.1.1.1" type="subsection"> <head>Unlawful Cures rejected.</head> <p>Inveterate melancholy, howsoever it may seem to be a continuate, inexorable disease, hard to be cured, accompanying them to their graves most part (as <ref target="#a">Montanus</ref> observes), yet many times it may be helped... </p> </div4> </div3> </div2> <div2 n="2.2" type="section"> <div3 n="2.2.1" type="member"> <head>Sect. II. Memb. I</head> <p/> </div3> </div2> <div2 n="2.3" type="section"> <div3 n="2.3.1" type="member"> <head>Sect. III. Memb. I</head> <p/> </div3> </div2> </div1> |
| Content model | <content> |
| Schema Declaration | element div2 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div3Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div3Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div3> (level-3 text division) contains a third-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div2 |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div2 n="2.2" type="section"> <div3 n="2.2.1" type="member"> <head>Sect. II. Memb. I</head> <p/> </div3> <div3 n="2.2.2" type="member"> <head>Memb. II Retention and Evacuation rectified.</head> <p/> </div3> <div3 n="2.2.3" type="member"> <head>Memb. III Ayr rectified. With a digression of the Ayr.</head> <p/> </div3> </div2> |
| Content model | <content> |
| Schema Declaration | element div3 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div4Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div4Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div4> (level-4 text division) contains a fourth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div3 |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div3 n="2.2.1" type="member"> <head>Sect. II. Memb. I</head> <div4 n="2.2.1.1" type="subsection"> <head>Subsect I. — Dyet rectified in substance.</head> <p>Diet, <term xml:lang="grc">diaitotiku</term>, <term xml:lang="la">victus</term> or living </p> </div4> <div4 n="2.2.2.1" type="subsection"> <head>Subsect II. — Dyet rectified in quantity.</head> <p>Man alone, saith Cardan, eates and drinks without appetite, and useth all his pleasures without necessity </p> </div4> </div3> |
| Content model | <content> |
| Schema Declaration | element div4 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div5Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div5Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div5> (level-5 text division) contains a fifth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div4 |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div2 type="chapter"> <head>Recipes</head> <head>Chapter VI.</head> <div3> <head>Fruit and vegetable soups</head> <p>...</p> <div4> <head>Stocks for all kinds of soups</head> <div5 type="recipe"> <head>Rich strong stock</head> <!-- ... --> </div5> <div5 type="recipe"> <head>Medium Stock</head> <!-- ... --> </div5> </div4> <div4 type="recipe"> <head>Apple soup</head> <div5> <head>Ingredients</head> <list> <item>2 lbs. of good boiling apples,</item> <item>3/4 teaspoonful of white pepper,</item> <item>6 cloves,</item> <item>cayenne or ginger to taste,</item> <item>3 quarts of medium stock</item> </list> </div5> <div5> <head>Mode</head> <p>Peel and quarter the apples taking out their cores; put them into the stock, stew them gently till tender, Rub the whole through a strainer, add the seasoning. give it one boil up, and serve.</p> </div5> <div5> <head>Time</head> <p>1 hour.</p> </div5> <div5> <head>Average cost</head> <p>per quart, 1s.</p> </div5> <div5> <head>Seasonable</head> <p>from September to December.</p> </div5> <div5> <head>Sufficient</head> <p> for 10 persons</p> </div5> <div5> <head>The apple</head> <p>This useful fruit is mentioned in Holy Writ; and Homer describes it as valuable in his time... As a food, the apple cannot be considered to rank high, as more than the half of it consists of water, and the rest of its properties are not the most nourishing. It is however a useful adjunct to other kinds of food, and, when cooked, is esteemed as slightly laxative.</p> </div5> </div4> <div4 type="recipe"> <head>Artichoke (Jerusalem) soup</head> <p>...</p> </div4> <!-- other recipes here --> </div3> </div2> |
| Content model | <content> |
| Schema Declaration | element div5 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div6Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div6Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div6> (level-6 text division) contains a sixth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div5 |
| May contain | |
| Note | any sequence of low-level structural elements, possibly grouped into lower subdivisions. |
| Example | <div2 type="chapter"> <head>Recipes</head> <head>Chapter VI.</head> <div3> <head>Fruit and vegetable soups</head> <p>...</p> <div4> <head>Stocks for all kinds of soups</head> <div5 type="recipe"> <head>Rich strong stock</head> <div6> <head>Ingredients</head> <list> <item>4 lbs of shin of beef,</item> <item>4 lbs of knuckle of veal,</item> <!-- ... --> <item>4 quarts of water</item> </list> </div6> <div6> <head>Mode</head> <p>Line a delicately clean stewpan... Strain through a very fine hair sieve, or tammy, and it will be fit for use</p> </div6> <div6> <head>Time</head> <p>5 hours.</p> </div6> <div6> <head>Average cost</head> <p>1s 3d. per quart</p> </div6> </div5> <div5 type="recipe"> <head>Medium Stock</head> <!-- ... --> </div5> </div4> <!-- ... --> </div3> </div2> |
| Content model | <content> |
| Schema Declaration | element div6 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( ( model.div7Like | model.divGenLike ), model.global* )+ ) | ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( ( model.div7Like | model.divGenLike ), model.global* )* ) ) ), ( ( model.divBottom, model.global* )* ) )? ) ) } |
| <div7> (level-7 text division) contains the smallest possible subdivision of the front, body or back of a text, larger than a paragraph. [4.1.2. Numbered Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | textstructure: div6 |
| May contain | |
| Note | any sequence of low-level structural elements, e.g., paragraphs (p), lists (list), or examples (<eg> or <egXML>). |
| Example | <div2 type="chapter"> <head>Recipes</head> <head>Chapter VI.</head> <div3> <head>Fruit and vegetable soups</head> <p>...</p> <div4> <head>Stocks for all kinds of soups</head> <div5 type="recipe"> <head>Asparagus soup</head> <div6 type="altRecipe"> <head>I.</head> <div7> <head>Ingredients</head> <list> <item> ...</item> </list> </div7> <div7> <head>Mode</head> <p>Put the beef, cut into pieces and rolled in flour, into a stewpan...</p> </div7> <!-- ... --> </div6> <div6 type="altRecipe"> <head>II.</head> <div7> <head>Ingredients</head> <list> <item> ...</item> </list> </div7> <div7> <head>Mode</head> <p>Boil the peas, and rub them through a sieve; add the gravy...</p> </div7> </div6> </div5> </div4> </div3> </div2> |
| Content model | <content> |
| Schema Declaration | element div7 { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( schemaSpec | model.common ), model.global* )+ ), ( ( model.divBottom, 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 | |
| Note | The document author's name often occurs within a byline, but the docAuthor element may be used whether the byline element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with byline without docAuthor.) |
| Example | <titlePage> <docTitle> <titlePart>Travels into Several Remote Nations of the World, in Four Parts.</titlePart> </docTitle> <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon, and then a Captain of several Ships</byline> </titlePage> |
| Content model | <content> |
| Schema Declaration | element docAuthor { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the general date element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it. |
| Example | <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate> </docImprint> |
| Content model | <content> |
| Schema Declaration | element docDate { att.global.attributes, att.cmc.attributes, att.datable.attributes, att.calendarSystem.attributes, macro.phraseSeq } |
| <docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element. |
| Example | <docEdition>The Third edition Corrected</docEdition> |
| Content model | <content> |
| Schema Declaration |
element docEdition { att.global.attributes, macro.paraContent } |
| <docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often. |
| Example | <docImprint>Oxford, Clarendon Press, 1987</docImprint> Imprints may be somewhat more complex: <docImprint> <pubPlace>London</pubPlace> Printed for <name>E. Nutt</name>, at <pubPlace>Royal Exchange</pubPlace>; <name>J. Roberts</name> in <pubPlace>wick-Lane</pubPlace>; <name>A. Dodd</name> without <pubPlace>Temple-Bar</pubPlace>; and <name>J. Graves</name> in <pubPlace>St. James's-street.</pubPlace> <date>1722.</date> </docImprint> |
| Content model | <content> |
| Schema Declaration | element docImprint { att.global.attributes, ( text | model.gLike | model.phrase | pubPlace | docDate | publisher | model.global )* } |
| <docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <docTitle> <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart> <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart> </docTitle> |
| Content model | <content> |
| Schema Declaration | element docTitle { att.global.attributes, ( model.global*, ( ( titlePart, 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 | core: bibl | ||||||||||
| May contain | |||||||||||
| Note | A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. | ||||||||||
| Example | <editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element editor { att.global.attributes, att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, macro.phraseSeq } | ||||||||||
| <email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The format of a modern Internet email address is defined in RFC 2822 |
| Example | <email>membership@tei-c.org</email> |
| Content model | <content> |
| Schema Declaration |
element email { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <epigraph xml:lang="la"> <cit> <bibl>Lucret.</bibl> <quote> <l part="F">petere inde coronam,</l> <l>Vnde prius nulli velarint tempora Musae.</l> </quote> </cit> </epigraph> |
| Content model | <content> |
| Schema Declaration | element epigraph { att.global.attributes, att.cmc.attributes, ( model.common | model.global )* } |
| <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images] | |
| Module | figures |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <figure> <head>The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> <graphic url="http://www.example.org/fig1.png" scale="0.5"/> </figure> |
| Content model | <content> |
| Schema Declaration | element figure { att.global.attributes, att.typed.attributes, att.written.attributes, att.cmc.attributes, ( model.headLike | model.common | figDesc | model.graphicLike | model.global | model.divBottom )* } |
| <floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | A floating text has the same content as any other text and may thus be interrupted by another floating text, or contain a group of tesselated texts. |
| Example | <body> <div type="scene"> <sp> <p>Hush, the players begin...</p> </sp> <floatingText type="pwp"> <body> <div type="act"> <sp> <l>In Athens our tale takes place [...]</l> </sp> <!-- ... rest of nested act here --> </div> </body> </floatingText> <sp> <p>Now that the play is finished ...</p> </sp> </div> </body> |
| Content model | <content> |
| Schema Declaration | element floatingText { att.global.attributes, att.typed.attributes, att.cmc.attributes, ( model.global*, ( ( front, model.global* )? ), ( body | group ), model.global*, ( ( back, model.global* )? ) ) } |
| <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 | |
| May contain | |
| Note | The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification. This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
| Example | This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>? |
| Content model | <content> |
| Schema Declaration |
element foreign { att.global.attributes, att.cmc.attributes, macro.phraseSeq } |
| <formula> (formula) contains a mathematical or other formula. [15.2. Formulæ and Mathematical Expressions] | |
| Module | figures |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <formula notation="tex">$E=mc^2$</formula> |
| Example | <formula notation="none">E=mc<hi rend="sup">2</hi> </formula> |
| Example | <formula notation="mathml"> <m:math> <m:mi>E</m:mi> <m:mo>=</m:mo> <m:mi>m</m:mi> <m:msup> <m:mrow> <m:mi>c</m:mi> </m:mrow> <m:mrow> <m:mn>2</m:mn> </m:mrow> </m:msup> </m:math> </formula> |
| Content model | <content> |
| Schema Declaration | element formula { att.global.attributes, att.cmc.attributes, ( text | model.graphicLike | model.hiLike )* } |
| <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: floatingText text |
| May contain | |
| Note | Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the front and back elements are identical. |
| Example | <front> <epigraph> <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q> </quote> </epigraph> <div type="dedication"> <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q> </p> </div> </front> |
| Example | <front> <div type="dedication"> <p>To our three selves</p> </div> <div type="preface"> <head>Author's Note</head> <p>All the characters in this book are purely imaginary, and if the author has used names that may suggest a reference to living persons she has done so inadvertently. ...</p> </div> </front> |
| Example | <front> <div type="abstract"> <div> <head> BACKGROUND:</head> <p>Food insecurity can put children at greater risk of obesity because of altered food choices and nonuniform consumption patterns.</p> </div> <div> <head> OBJECTIVE:</head> <p>We examined the association between obesity and both child-level food insecurity and personal food insecurity in US children.</p> </div> <div> <head> DESIGN:</head> <p>Data from 9,701 participants in the National Health and Nutrition Examination Survey, 2001-2010, aged 2 to 11 years were analyzed. Child-level food insecurity was assessed with the US Department of Agriculture's Food Security Survey Module based on eight child-specific questions. Personal food insecurity was assessed with five additional questions. Obesity was defined, using physical measurements, as body mass index (calculated as kg/m2) greater than or equal to the age- and sex-specific 95th percentile of the Centers for Disease Control and Prevention growth charts. Logistic regressions adjusted for sex, race/ethnic group, poverty level, and survey year were conducted to describe associations between obesity and food insecurity.</p> </div> <div> <head> RESULTS:</head> <p>Obesity was significantly associated with personal food insecurity for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to 2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95% CI 0.51 to 1.51). Child-level food insecurity was not associated with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p> </div> <div> <head> CONCLUSIONS:</head> <p>Personal food insecurity is associated with an increased risk of obesity only in children aged 6 to 11 years. Personal food-insecurity measures may give different results than aggregate food-insecurity measures in children.</p> </div> </div> </front> |
| Content model | <content> |
| Schema Declaration | element front { att.global.attributes, ( ( model.frontPart | model.pLike | model.pLike.front | model.global )*, ( ( ( ( model.div1Like, ( model.div1Like | model.frontPart | model.global )* ) | ( model.divLike, ( model.divLike | model.frontPart | model.global )* ) ), ( ( model.divBottom, ( model.divBottom | model.global )* )? ) )? ) ) } |
| <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes] | |
| Module | gaiji |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Character data only |
| Note | The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph. |
| Example | <g ref="#ctlig">ct</g> This example points to a <glyph> element with the identifier ctlig like the following: <glyph xml:id="ctlig"> <!-- here we describe the particular ct-ligature intended --> </glyph> |
| Example | <g ref="#per-glyph">per</g> The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows: <glyph xml:id="per-glyph"> <!-- ... --> </glyph> |
| Content model | <content> |
| Schema Declaration |
element g { att.global.attributes, att.typed.attributes, text } |
| <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 | |||||||||
| May contain | core: desc | ||||||||
| Note | The gap, unclear, and del core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The gap tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as del in the case of deliberate deletion. | ||||||||
| Example | <gap quantity="4" unit="chars" reason="illegible"/> | ||||||||
| Example | <gap quantity="1" unit="essay" reason="sampling"/> | ||||||||
| Example | <del> <gap atLeast="4" atMost="8" unit="chars" reason="illegible"/> </del> | ||||||||
| Example | <gap extent="several lines" reason="lost"/> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element gap { att.global.attributes, att.timed.attributes, att.cmc.attributes, attribute reason { list { ( "cancelled" | "deleted" | "editorial" | "illegible" | "inaudible" | "irrelevant" | "sampling" | teidata.enumerated )+ } }?, ( model.descLike | model.certLike )* } | ||||||||
| <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: desc |
| Note | The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. Within the body of a text, a graphic element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a graphic element provides an additional digital representation of some part of the source being encoded. |
| Example | <figure> <graphic url="fig1.png"/> <head>Figure One: The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> </figure> |
| Example | <facsimile> <surfaceGrp n="leaf1"> <surface> <graphic url="page1.png"/> </surface> <surface> <graphic url="page2-highRes.png"/> <graphic url="page2-lowRes.png"/> </surface> </surfaceGrp> </facsimile> |
| Example | <facsimile> <surfaceGrp n="leaf1" xml:id="spi001"> <surface xml:id="spi001r"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001r.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001r.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001r.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001r.jpg"/> </surface> <surface xml:id="spi001v"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001v.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001v.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001v.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001v.jpg"/> <zone xml:id="spi001v_detail01"> <graphic type="normal" subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/> <graphic type="normal" subtype="low-res" url="spi/normal/lowRes/001v-detail01.jpg"/> <graphic type="normal" subtype="high-res" url="spi/normal/highRes/001v-detail01.jpg"/> <graphic type="high-contrast" subtype="low-res" url="spi/contrast/lowRes/001v-detail01.jpg"/> <graphic type="high-contrast" subtype="high-res" url="spi/contrast/highRes/001v-detail01.jpg"/> </zone> </surface> </surfaceGrp> </facsimile> |
| Content model | <content> |
| Schema Declaration | element graphic { att.global.attributes, att.resourced.attributes, att.typed.attributes, att.cmc.attributes, model.descLike* } |
| <group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: floatingText group text |
| May contain | |
| Example | <text> <!-- Section on Alexander Pope starts --> <front> <!-- biographical notice by editor --> </front> <group> <text> <!-- first poem --> </text> <text> <!-- second poem --> </text> </group> </text> <!-- end of Pope section--> |
| Content model | <content> |
| Schema Declaration | element group { att.global.attributes, att.typed.attributes, ( ( model.divTop | model.global )*, ( ( text | group ), ( text | group | model.global )* ), model.divBottom* ) } |
| <handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [12.3.2.1. Document Hands] | |||||||||
| Module | transcr | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| 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 { att.global.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 | |
| Note | The head element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a head element based on its structural position. A head occurring as the first element of a list is the title of that list; one occurring as the first element of a div1 is the title of that chapter or section. |
| Example | The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a trailer, as in this example: <div1 n="I" type="book"> <head>In the name of Christ here begins the first book of the ecclesiastical history of Georgius Florentinus, known as Gregory, Bishop of Tours.</head> <div2 type="section"> <head>In the name of Christ here begins Book I of the history.</head> <p>Proposing as I do ...</p> <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve years passed.</p> <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six years from the beginning of the world down to the death of Saint Martin.</trailer> </div2> </div1> |
| Example | When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute. <div type="subsection"> <head place="margin">Secunda conclusio</head> <p> <lb n="1251"/> <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied> </hi> <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium [...] </p> </div> |
| Example | The head element is also used to mark headings of other units, such as lists: With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted"> <head>Connectives</head> <item>above</item> <item>accordingly</item> <item>across from</item> <item>adjacent to</item> <item>again</item> <item> <!-- ... --> </item> </list> |
| Content model | <content> |
| Schema Declaration | element head { att.global.attributes, att.typed.attributes, att.written.attributes, att.cmc.attributes, ( text | lg | model.gLike | model.phrase | model.inter | model.lLike | model.global )* } |
| <hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ... |
| Content model | <content> |
| Schema Declaration | element hi { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <i> (italics) for capturing typographical feature: italicized glyphs. | |
| Namespace | http://www.tei-c.org/ns/tite/1.0 |
| Module | derived-module-tei_tite |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Content model | <content> |
| Schema Declaration |
element i { att.global.attributes, macro.paraContent } |
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
| Module | core |
| Attributes |
|
| Contained by | core: list |
| May contain | |
| Note | May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n. |
| Example | <list rend="numbered"> <head>Here begin the chapter headings of Book IV</head> <item n="4.1">The death of Queen Clotild.</item> <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item> <item n="4.3">The wives and children of Lothar.</item> <item n="4.4">The Counts of the Bretons.</item> <item n="4.5">Saint Gall the Bishop.</item> <item n="4.6">The priest Cato.</item> <item> ...</item> </list> |
| Content model | <content> |
| Schema Declaration | element item { att.global.attributes, att.sortable.attributes, macro.specialPara } |
| <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l> |
| Schematron | <sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element l { att.global.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | model.inter | model.global )* } |
| <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin: <list type="gloss" xml:lang="enm"> <head xml:lang="en">Vocabulary</head> <headLabel xml:lang="en">Middle English</headLabel> <headItem xml:lang="en">New English</headItem> <label>nu</label> <item xml:lang="en">now</item> <label>lhude</label> <item xml:lang="en">loudly</item> <label>bloweth</label> <item xml:lang="en">blooms</item> <label>med</label> <item xml:lang="en">meadow</item> <label>wude</label> <item xml:lang="en">wood</item> <label>awe</label> <item xml:lang="en">ewe</item> <label>lhouth</label> <item xml:lang="en">lows</item> <label>sterteth</label> <item xml:lang="en">bounds, frisks (cf. <cit> <ref>Chaucer, K.T.644</ref> <quote>a courser, <term>sterting</term>as the fyr</quote> </cit> </item> <label>verteth</label> <item xml:lang="la">pedit</item> <label>murie</label> <item xml:lang="en">merrily</item> <label>swik</label> <item xml:lang="en">cease</item> <label>naver</label> <item xml:lang="en">never</item> </list> |
| Example | Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element: I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runon" type="ordered"> <label>(1)</label> <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item> <label>(2) </label> <item>Not a sheet has been seen by any human eyes, excepting those of the author and the printer: the faults and the merits are exclusively my own.</item> </list> |
| Example | Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon: <list type="gloss"> <label>March 1757.</label> <item>I wrote some critical observations upon Plautus.</item> <label>March 8th.</label> <item>I wrote a long dissertation upon some lines of Virgil.</item> <label>June.</label> <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus amori.</quote> </item> <label>August.</label> <item>I went to Crassy, and staid two days.</item> </list> Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice. |
| Example | Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it. <p>[...] <lb/>& n’entrer en mauuais & mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale entre les Romains.</label> <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p> In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label. |
| Content model | <content> |
| Schema Declaration | element label { att.global.attributes, att.typed.attributes, att.written.attributes, att.cmc.attributes, macro.phraseSeq } |
| <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 | |
| May contain | Empty element |
| Note | By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked. The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives. |
| Example | This example shows typographical line breaks within metrical lines, where they occur at different places in different editions: <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> |
| Example | This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word. <titlePart> <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart> |
| Content model | <content> |
| Schema Declaration | element lb { att.global.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | contains verse lines or nested line groups only, possibly prefixed by a heading. |
| Example | <lg type="free"> <l>Let me be my own fool</l> <l>of my own making, the sum of it</l> </lg> <lg type="free"> <l>is equivocal.</l> <l>One says of the drunken farmer:</l> </lg> <lg type="free"> <l>leave him lay off it. And this is</l> <l>the explanation.</l> </lg> |
| Schematron | <sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule> |
| Schematron | <sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element lg { att.global.attributes, att.typed.attributes, att.cmc.attributes, ( ( model.divTop | model.global )*, ( model.lLike | model.stageLike | model.labelLike | model.pPart.transcriptional | lg ), ( model.lLike | model.stageLike | model.labelLike | model.pPart.transcriptional | model.global | lg )*, ( ( model.divBottom, model.global* )* ) ) } |
| <list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||
| Example | <list rend="numbered"> <item>a butcher</item> <item>a baker</item> <item>a candlestick maker, with <list rend="bulleted"> <item>rings on his fingers</item> <item>bells on his toes</item> </list> </item> </list> | ||||||||||
| Example | <list type="syllogism" rend="bulleted"> <item>All Cretans are liars.</item> <item>Epimenides is a Cretan.</item> <item>ERGO Epimenides is a liar.</item> </list> | ||||||||||
| Example | <list type="litany" rend="simple"> <item>God save us from drought.</item> <item>God save us from pestilence.</item> <item>God save us from wickedness in high places.</item> <item>Praise be to God.</item> </list> | ||||||||||
| Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section"> <head>Athelstan's Ordinance</head> <list rend="numbered"> <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with the stolen goods, [if he is] over twelve years and [if the value of the goods is] over eightpence. <list rend="numbered"> <item n="1.1">And if anyone does spare one, he is to pay for the thief with his wergild — and the thief is to be no nearer a settlement on that account — or to clear himself by an oath of that amount.</item> <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is not to be spared [whether younger or older than twelve].</item> <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may then be redeemed with 120 shillings; and the kindred are to stand surety for him that he will desist for ever.</item> <item n="1.4">And if he steals after that, they are to pay for him with his wergild, or to bring him back there.</item> <item n="1.5">And if he steals after that, they are to pay for him with his wergild, whether to the king or to him to whom it rightly belongs; and everyone of those who supported him is to pay 120 shillings to the king as a fine.</item> </list> </item> <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom no justice can be obtained, that one should order their kindred to fetch back such a person to justice and to find him a lord in public meeting. <list rend="numbered"> <item n="2.1">And if they then will not, or cannot, produce him on that appointed day, he is then to be a fugitive afterwards, and he who encounters him is to strike him down as a thief.</item> <item n="2.2">And he who harbours him after that, is to pay for him with his wergild or to clear himself by an oath of that amount.</item> </list> </item> <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds his guilty man, so that the king is appealed to, is to repay the value of the goods and 120 shillings to the king; and he who appeals to the king before he demands justice as often as he ought, is to pay the same fine as the other would have done, if he had refused him justice. <list rend="numbered"> <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes known about him, is to forfeit the slave and be liable to his wergild on the first occasionp if he does it more often, he is to be liable to pay all that he owns.</item> <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been an accessory of thieves who have committed theft, is to liable to the same.</item> </list> </item> <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is afterwards convicted at the three-fold ordeal.</item> </list> </div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. | ||||||||||
| Example | <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple"> <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have subscribed to the pious and catholic validity of this document with the sign of the Holy Cross.</item> <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with the sign of the Holy Cross.</item> <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the sign of the Holy Cross.</item> <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the sign of the Holy Cross.</item> <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of the Holy Cross.</item> <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item> <item>I, Æthelwine, bishop, have subscribed through delegates.</item> <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy Cross.</item> </list> </p> | ||||||||||
| Schematron | <sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element list { att.global.attributes, att.sortable.attributes, att.cmc.attributes, attribute type { teidata.enumerated }?, ( ( model.divTop | model.global | desc* )*, ( ( ( item, model.global* )+ ) | ( headLabel?, headItem?, ( ( label, model.global*, item, model.global* )+ ) ) ), ( ( model.divBottom, model.global* )* ) ) } | ||||||||||
| <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listBibl> <head>Works consulted</head> <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990) </bibl> <biblStruct> <analytic> <title>The Interesting story of the Children in the Wood</title> </analytic> <monogr> <title>The Penny Histories</title> <author>Victor E Neuberg</author> <imprint> <publisher>OUP</publisher> <date>1968</date> </imprint> </monogr> </biblStruct> </listBibl> |
| Content model | <content> |
| Schema Declaration | element listBibl { att.global.attributes, att.sortable.attributes, att.declarable.attributes, att.typed.attributes, att.cmc.attributes, ( model.headLike*, desc*, ( model.milestoneLike | relation | listRelation )*, ( ( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+ ) ) } |
| <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 | |
| May contain | Empty element |
| Note | For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc. The order in which milestone elements are given at a given point is not normally significant. |
| Example | <milestone n="23" ed="La" unit="Dreissiger"/> ... <milestone n="24" ed="AV" unit="verse"/> ... |
| Content model | <content> |
| Schema Declaration | element milestone { att.global.attributes, att.milestoneUnit.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. | ||||||||||
| Example | <name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="person" ref="#HOC001">Occleve</name> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element name { att.global.attributes, att.personal.attributes, att.datable.attributes, att.typed.attributes, att.cmc.attributes, attribute calendar { list { teidata.pointer+ } }?, macro.phraseSeq } | ||||||||||
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottom" type="gloss" resp="#MDMH"> <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH"> <resp>translation from German to English</resp> <name>Hottinger, Marie Donald Mackie</name> </respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
| Example | The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126" anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
| Content model | <content> |
| Schema Declaration | element note { att.global.attributes, att.pointing.attributes, att.typed.attributes, att.written.attributes, att.cmc.attributes, macro.specialPara } |
| <num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The num element is intended for use in simple applications. | ||||||||||
| Example | <p>I reached <num type="cardinal" value="21">twenty-one</num> on my <num type="ordinal" value="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi> </num> cm per second.</p> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element num { att.global.attributes, att.cmc.attributes, attribute type { teidata.enumerated }?, macro.phraseSeq } | ||||||||||
| <opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <opener> <dateline>Walden, this 29. of August 1592</dateline> </opener> |
| Example | <opener> <dateline> <name type="place">Great Marlborough Street</name> <date>November 11, 1848</date> </dateline> <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p> |
| Content model | <content> |
| Schema Declaration | element opener { att.global.attributes, att.written.attributes, att.cmc.attributes, ( text | model.gLike | model.phrase | argument | byline | dateline | epigraph | salute | signed | model.global )* } |
| <ornament> for capturing typographical feature: printer's ornament, horizontal line, strings of asterisks or periods, etc, indicating an informal division that does not call for a new <div> element. If a horizontal rule or printer's ornament, use appropriate rend attribute and leave the element empy; if the ornament can be represented with characters, include these in the element. | |
| Namespace | http://www.tei-c.org/ns/tite/1.0 |
| Module | derived-module-tei_tite |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Character data only |
| Content model | <content> |
| Schema Declaration |
element ornament { att.global.attributes, text } |
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you done?</q> </p> <p> <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p> <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p> <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p> |
| Schematron | <sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule> |
| Schematron | <sch:rule context="tei:p"> <sch:report test="( ancestor::tei:l or ancestor::tei:lg ) and not( ancestor::tei:floatingText | parent::tei:figure | parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element p { att.global.attributes, att.fragmentable.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Empty element |
| Note | A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself. The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives. |
| Example | Page numbers may vary in different editions of a text. <p> ... <pb n="145" ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p> |
| Example | A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body> <pb n="1" facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here --> <p> <!-- ... --> </p> <pb n="2" facs="page2.png"/> <!-- similarly, for page 2 --> <p> <!-- ... --> </p> </body> |
| Content model | <content> |
| Schema Declaration | element pb { att.global.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <div type="letter"> <opener> <dateline> <placeName>Rimaone</placeName> <date when="2006-11-21">21 Nov 06</date> </dateline> <salute>Dear Susan,</salute> </opener> <p>Thank you very much for the assistance splitting those logs. I'm sorry about the misunderstanding as to the size of the task. I really was not asking for help, only to borrow the axe. Hope you had fun in any case.</p> <closer> <salute>Sincerely yours,</salute> <signed>Seymour</signed> </closer> <postscript> <label>P.S.</label> <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p> </postscript> </div> |
| Content model | <content> |
| Schema Declaration | element postscript { att.global.attributes, att.written.attributes, att.cmc.attributes, ( ( model.global | model.divTopPart )*, model.common, ( model.global | model.common )*, ( ( model.divBottomPart, model.global* )* ) ) } |
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Empty element |
| Example | <ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/> |
| Schematron | <sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element ptr { att.global.attributes, att.pointing.attributes, att.typed.attributes, att.cmc.attributes, empty } |
| <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 | core: bibl textstructure: docImprint |
| May contain | |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
| Example | <imprint> <pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
| Content model | <content> |
| Schema Declaration |
element publisher { att.global.attributes, 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 | core: bibl textstructure: docImprint |
| May contain | |
| Example | <publicationStmt> <publisher>Oxford University Press</publisher> <pubPlace>Oxford</pubPlace> <date>1989</date> </publicationStmt> |
| Content model | <content> |
| Schema Declaration |
element pubPlace { att.global.attributes, 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 | |||||||||
| May contain | |||||||||
| Note | May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks. | ||||||||
| Example | It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q> | ||||||||
| Content model | <content> | ||||||||
| Schema Declaration | element q { att.global.attributes, att.ascribed.directed.attributes, att.cmc.attributes, attribute type { "spoken" | "thought" | "written" | "soCalled" | "foreign" | "distinct" | "term" | "emph" | "mentioned" | teidata.enumerated }?, macro.specialPara } | ||||||||
| <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref> |
| Example | See also <ref target="#locution">s.v. <term>locution</term> </ref>. |
| Schematron | <sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> </sch:rule> |
| Content model | <content> |
| Schema Declaration | element ref { att.global.attributes, att.pointing.attributes, att.typed.attributes, att.cmc.attributes, macro.paraContent } |
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Contained by | core: respStmt | ||||||||||
| May contain | |||||||||||
| Note | The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. | ||||||||||
| Example | <respStmt> <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp> <name>Edward Child</name> </respStmt> | ||||||||||
| Content model | <content> | ||||||||||
| Schema Declaration | element resp { att.global.attributes, att.datable.attributes, attribute calendar { list { teidata.pointer+ } }?, macro.phraseSeq.limited } | ||||||||||
| <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl |
| May contain | |
| Example | <respStmt> <resp>transcribed from original ms</resp> <persName>Claus Huitfeldt</persName> </respStmt> |
| Example | <respStmt> <resp>converted to XML encoding</resp> <name>Alan Morrison</name> </respStmt> |
| Content model | <content> |
| Schema Declaration | element respStmt { att.global.attributes, ( ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ), note* ) } |
| <row> (row) contains one row of a table. [15.1.1. TEI Tables] | |
| Module | figures |
| Attributes |
|
| Contained by | figures: table |
| May contain | figures: cell |
| Example | <row role="data"> <cell role="label">Classics</cell> <cell>Idle listless and unimproving</cell> </row> |
| Content model | <content> |
| Schema Declaration |
element row { att.global.attributes, att.tableDecoration.attributes, cell+ } |
| <salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <salute>To all courteous mindes, that will voutchsafe the readinge.</salute> |
| Content model | <content> |
| Schema Declaration | element salute { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element. |
| Example | <seg>When are you leaving?</seg> <seg>Tomorrow.</seg> |
| Example | <s> <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield. </s> |
| Example | <seg type="preamble"> <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg> <seg>Sinfiotli was the eldest of his sons ...</seg> <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg> |
| Content model | <content> |
| Schema Declaration | element seg { att.global.attributes, att.typed.attributes, att.written.attributes, att.notated.attributes, att.cmc.attributes, macro.paraContent } |
| <signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <signed>Thine to command <name>Humph. Moseley</name> </signed> |
| Example | <closer> <signed>Sign'd and Seal'd, <list> <item>John Bull,</item> <item>Nic. Frog.</item> </list> </signed> </closer> |
| Content model | <content> |
| Schema Declaration | element signed { att.global.attributes, att.written.attributes, att.cmc.attributes, macro.paraContent } |
| <smcap> (smallcaps) for capturing typographical feature: glyphs in small capitals. | |
| Namespace | http://www.tei-c.org/ns/tite/1.0 |
| Module | derived-module-tei_tite |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Content model | <content> |
| Schema Declaration |
element smcap { att.global.attributes, macro.paraContent } |
| <sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The who attribute on this element may be used either in addition to the speaker element or as an alternative. |
| Example | <sp> <speaker>The reverend Doctor Opimian</speaker> <p>I do not think I have named a single unpresentable fish.</p> </sp> <sp> <speaker>Mr Gryll</speaker> <p>Bream, Doctor: there is not much to be said for bream.</p> </sp> <sp> <speaker>The Reverend Doctor Opimian</speaker> <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p> <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I will forbear [...]</p> </sp> |
| Content model | <content> |
| Schema Declaration | element sp { att.global.attributes, att.ascribed.directed.attributes, ( model.global*, ( ( speaker, model.global* )? ), ( ( ( lg | model.lLike | model.pLike | model.listLike | model.stageLike | model.attributable ), ( model.global* | q ) )+ ) ) } |
| <speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama] | |
| Module | core |
| Attributes |
|
| Contained by | core: sp |
| May contain | |
| Note | This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an sp element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used. |
| Example | <sp who="#ni #rsa"> <speaker>Nancy and Robert</speaker> <stage type="delivery">(speaking simultaneously)</stage> <p>The future? ...</p> </sp> <list type="speakers"> <item xml:id="ni"/> <item xml:id="rsa"/> </list> |
| Content model | <content> |
| Schema Declaration |
element speaker { att.global.attributes, macro.phraseSeq } |
| <stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The who attribute may be used to indicate more precisely the person or persons participating in the action describ |