TEI in Libraries level 4

1. Level 4: Basic Content Analysis

1.1. Reference

Note that this is intended to be a ‘TEI conformant’ customization, per P5 section 23.3.

1.2. Purpose

To create text that can stand alone as electronic text, identifies hierarchy and typography, specifies function of textual and structural elements, and describes the nature of the content and not merely its appearance. This level is not meant to encode or identify all structural, semantic, or bibliographic features of the text.

1.3. Rationale

Greater description of function and content allows for:

flexibility of display and delivery
sophisticated searching within specified textual and structural elements
combining the broadest range of uses and audiences

Level 4 texts contain elements and attributes that describe content, not just appearance, of the text. Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers, and the encoding of content allows these texts to work effectively with screen readers and other applications that rely on the structure of a text, not just its appearance.

Finally, functionally accurate encoding in Level 4 texts allows them to be searched or displayed in sophisticated ways. For example, a searcher could limit his or her search in a dramatic text to stage directions or in a verse text to only first lines. In a political tract published by subscription, a search could be confined to names that appear in lists, thus limiting a search to names of people who subscribed to a particular volume. This ability to limit searches becomes more significant as textbases become larger, and thus is of great importance to the library community as it attempts to build into the initial design and implementation of textbases the features needed to enhance interoperability.

Level 4 is most suitable for projects with the following characteristics

sophisticated search and retrieval capabilities are desired
the texts will be used for textual analysis
extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added by the scholarly community at a later date
the users of the texts may have limited storage or display capabilities

1.4. Workflow

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup should be added, as discussed in Appendix A of TEI Tite.

1.5. Element Recommendations for Level 4

Use all elements specified in Levels 1, 2, and 3 except <ab>, plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.

<titlePage> and appropriate child elements	Recommended.
<group>	Recommended to encode a collection of independent texts that are regarded as a single group for processing or other purposes.
<div> or <div1>, <div2>, <div3>, etc.	Recommended for encoding a hierarchy of textual divisions. Use as many levels of hierarchy as needed to represent the source document.
<floatingText>	Recommended when a floating text is identified.
<list> and <item>	Recommended to indicate ordered and unordered list structures.
<table>, <row>, and <cell>	Recommended to indicate table structures.
<hi>	Recommended to indicate change in rendition when a more specific element is not being used; rend attribute is optional.
<opener>, <dateline>, <salute> <closer>, <signed>, <postscript>	Recommended to indicate specific parts of letters.
<castList>, <castItem>, <sp>, <speaker>, and <stage>	Recommended to encode different structures in performance texts (i.e. drama).
<sp> and <speaker>	Recommended to encode oral history interviews.
<epigraph>	Recommended for encoding epigraphs found as front matter
<quote rend="___">	Recommended for encoding blockquotes that appear outside the flow of a paragraph. In the rend attribute, give a CSS declaration-block (such as padding-left: 0.5in;)
<argument>	Recommended to encode a list of topics sometimes found at the start of a chapter or other textual division.
<trailer>	Recommended to encode a closing title or footer at the end of a division.
<quote>, <said>, <mentioned>, or <soCalled>	Optional.
<emph>, <distinct>, <foreign>, <gloss>, or <term>	Optional.
<title type="_">	Optional within the <text> (not the <teiHeader>), especially when text is typographically distinct. Optionally use the type attribute with a value as given in the full TEI guidelines except for main titles. (The main value should be used, when appropriate, for <title>s within a TEI header, but is not needed for <title>s elsewhere in a document.)
<ptr> and <ref>	In addition to using to point to notes (as in Level 3), optionally use for identifying cross-references within the text.
<sic>, <corr>, or <choice>	Optionally use to encode errors or typos.
<add>, <del>, <gap>, and <unclear>	Optionally use to encode material that is added, marked for deletion, or is illegible, invisible, or inaudible.
<persName>, <placeName>, <geogName>, <orgName>, and <name type="___">	Optionally use to encode personal, place, organizational, and other names used in a text. The <persName> element is also used to indicate a personal name inside a <person> element (see below).
<bibl>	May contain bibliographic elements like <author>, <biblScope>, <citedRange>, <distributor>, <edition> <editor>, <idno>, <pubPlace>, <publisher>, <relatedItem>, <respStmt>, <series>, and <title> in addition to text.
<listName>, <listPlace>, and <listOrg>	Optionally use in support of personal, place, and organizational names normalization and to capture additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.
<listPerson>	Optionally used in support of transcriptions of oral interviews.
<person>	Optionally used in support of transcriptions of oral interviews. The use of the role attribute is strongly recommended, particularly to differentiate interviewer(s) from interviewee(s).
<birth>	Optionally used inside a <person> to indicate the date or place of birth of the person being documented.
<bibl>	Contains a single bibliographic entry. Use of the <author> or <editor> element is recommended. Other valid elements that the TEI allows to appear in <bibl> may also be used to encode a bibliographic citation, such as <title>, <publisher> and, <biblScope>. It is recommended that the <date> always appear with a when attribute in order to provide a canonical form of the date.

1.6. General Level 4 Recommendations and Examples

There are many optinoal but not recommended elements at Level 4. While content for many of these elements can be identified within running prose based on changes in typography or use of quotation marks in the source document, they are not always so easily idenitified, or they may occur so often that identification of each instance is impractical. Use only those optional elements that are appropriate for your users' needs and your encoding budget.

The use of <group> is recommended when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section 4.3.1 Grouped Texts states, ‘The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.’
Use <argument> to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:
<div type="chapter" n="1"> <pb xml:id="albert14" n="14"/> <head>CHAPTER I.</head> <head>CHARLOTTE BROOKS.</head> <argument> <p>Causes of immorality among colored people - Charlotte Brooks - She is sold South - Sunday work.</p> </argument> <p> ... </p> </div>

Octavia V. Rogers Albert The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens. New York: Hunt & Eaton, 1890.
The <trailer> element is recommended to encode a heading- or title-like content at the end of a textual division:
<body> <head>[book title]</head> <div type="chapter" n="1"> <head>[chapter title]</head> <p>[text]</p> <trailer>Here ends the Chapter 1.</trailer> </div> <div type="chapter" n="2"> <head>[chapter title]</head> <p>[text]</p> <trailer>Here ends the Chapter 2.</trailer> </div> <trailer>FINIS.</trailer> </body>
Typographically distinct text may be encoded using the following elements:
- to represent speech, thought, quotation, etc.:
- to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
  - distinct
  - emph
  - foreign (e.g. <foreign xml:lang="fr">)
  - gloss
  - term
  - title
Any ambiguous typographically distinct text should be encoded as hi (e.g. <hi rend="font-weight: bold">). This element may also be used if the more specific elements above are not used.
Any of the following three methods may be used to encode errors or typos in original texts:
- the sic element used alone is optional to indicate errors without correcting them
- the corr element used alone is optional to provide corrections without indicating the initial error
- the choice element allows both the apparent error and its editorial correction to be recorded, as in the following examples:
  <p>He has no Scruple about Fish; but won't touch a bit of Pork, it being <choice> <sic>expresly</sic> <corr>expressly</corr> </choice> forbidden by their Law.</p>
  
  Thomas Bluett Some Memoirs of the Life of Job, the Son of Solomon, the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734. London: Printed for R. Ford, 1734.
  or
  <p>4. The art of writing she obtained by her own industry and curiosity, and in so short a time that in the year 1765, when she was not more than twelve years of <choice> <sic>age,she</sic> <corr>age, she</corr> </choice> was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various subjects. She also wrote to several persons in high stations.</p>
  
  Abigail Mott, 1766-1851 Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry. New-York: M. Day, 1826.
The elements <add>, <del>, <unclear>, <gap> may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<unclear>) or impossible (<gap>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):
<p>But it is well authenticated by the observation of every one, that <del rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e. the above</add> of writing influences the style of compos. of those who practise it considerably, when they grow up to years of manhood; for their productions, <del hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative, convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the most disgusting manner, without divisions or heads &amp; in short without a subject (so to speak).</p>

Class Composition of J. Horace Lacy [January 1851] 1. Lacy, James Horace 1834-1852

<p>But I still hope for &amp; trust in God and I believe he will animate our brave defenders with a superhuman power and we will yet drive from our soil the hated invaders whose tread <gap reason="ink blot"/> profanation, but this is an hour to try men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a flesh wound only, you must not be uneasy.</p>

Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

1.6.1. Level 4 Front and Back Matter

Encode each section of front and back matter as their own textual division. Beyond what is described in the P5 Guidelines, note the following:

Titles pages (recto and verso): The use of the <titlePage> element with appropriate child elements describing the major features of most title pages is recommended. The child elements are listed in Section 4.6 "Title Pages". <titlePage> must include the verso if present, divided by <pb n="verso"/>.
Tables of contents, errata, subscription lists, lists of other titles by the same author, and other such lists': should use a <list> with <item>s. For an index, use <ref target="____"> to mark up page numbers given in the index, with the value of target referring to the xml:id attribute of the <pb> of the referenced page.

1.6.2. Level 4 Name Tagging

Chapter 13.1.1, Linking Names and Their Referents

Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements. For names of entities other than persons, places, and organizations, use <name> with a type attribute containing an appropriate value, such as event for the name of an event.

For all of these elements, use the ref attribute (see discussion above) to provide a reference to a <person>, <place>, <org>, <event>, or other element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. An external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, <listOrg>, or <listEvent> which is uniquely identified with an xml:id attribute. The value of the ref attribute in the main TEI document (the transcription of the source document) references the value of the xml:id attribute in the external file. (In the examples below, the external file is named context.xml for ‘contextual information’ and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases by tag URI, it is strongly recommended to provide an explanation in a <p> element in the <editorialDecl> section of the TEI header. When referencing a controlled vocabulary by relative URI, be sure to specify the controlled vocabulary in the <classDecl> section of the TEI header.

Place-name tagging example in main TEI document (the transcription of the source document):
<p>The first Jews arrived in <placeName ref="http://vocab.getty.edu/page/tgn/7012924">Indianapolis</placeName> in the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the <placeName ref="http://vocab.getty.edu/page/tgn/7012149">United States</placeName> before they arrived in the city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in <placeName ref="http://vocab.getty.edu/page/tgn/7012924">Indianapolis</placeName>. </p>
Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="http://id.loc.gov/authorities/names/n82134365.html">Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with Professor of Law <persName ref="http://id.loc.gov/authorities/names/n00113347">W. Howard Mann</persName> as the two inspect some of the nearly 3,000 volumes of <orgName ref="http://id.loc.gov/authorities/names/n79006848">U.S. Supreme Court</orgName> records recently transferred to I.U. from the <orgName ref="http://id.loc.gov/authorities/names/n79109178">Indiana Supreme Court Library</orgName>. The collection, dating back to 1925, is one of the oldest and most complete sets in existence.</p>

1.6.3. Level 4 Embedded Texts

If the embedded text is more than a short quotation, use <floatingText> even if the instance is still only an excerpt of the embedded text.

Personal letters are a common example of an embedded text. While a collection of letters would use a textual division for each letter, if a letter is quoted as part of a larger text, use <floatingText><body><div1 type="letter"> (or <floatingText><body><div type="letter"> if using unnumbered textual divisions) with <opener>, <dateline>, <salute>, <signed>, <closer>, <postscript> included as appropriate. For example:

<p>She opened and read as follows:</p> <floatingText> <body> <div1 type="letter"> <opener> <dateline>AUGUSTA, March 4th, 18—</dateline> <salute> <hi rend="font-style: italic">Mrs. A. Mitten:</hi> </salute> </opener> <p>"Having recently understood that you have procured a private teacher, we have ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it until forbid,</hi> under the impression that you have probably forgotten to have it stopped. If, however, we have been misinformed, we will promptly resume the publication of it. You will find our account below; which as we are much in want of funds, you will oblige us by settling as soon as convenient. Hoping your teacher is all that you could desire in one,</p> <closer> <salute>"We remain, your ob't. serv'ts,</salute> <signed>"H—&amp; B—”</signed> </closer> </div1> </body> </floatingText>

Augustus Baldwin Longstreet, 1790-1870 Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck. Macon, Ga.: Burke, Boykin, 1864.

1.6.4. Level 4 Drama

Within the front matter (<front>) of a performance text, cast lists must be encoded as <castList>s, with each item in that list encoded as a <castItem>. If desired, each <castItem> may be uniquely identified with an xml:id attribute.

For example,

<front> <castList> <head>Dramatis Personae</head> <castItem xml:id="kllear">LEAR king of Britain</castItem> <castItem xml:id="klfrance">KING OF FRANCE</castItem> <castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem> <castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem> <castItem xml:id="klalbany">DUKE OF ALBANY</castItem> <castItem xml:id="klkent">EARL OF KENT</castItem> <castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem> <castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem> <castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>  </castList> </front>

Shakespeare’s King Lear

Within the body of performative texts:

speeches are encoded as <sp> and speakers identified by the <speaker> element, which is a child of <sp>.
Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
If normalizing the speaker(s) of a speech is desired, the who attribute of <sp> may be used to refer to the <castItem> of the speaker. When who is used, <speaker> is optional.
<div type="act" n="1"> <head>Act 1</head> <div type="scene" n="1"> <head>Scene 1</head> <stage>King Lear's palace.</stage> <stage>Enter KENT, GLOUCESTER, and EDMUND</stage> <sp n="1" who="#klkent"> <speaker>KENT</speaker> <p>I thought the king had more affected the Duke of<lb/> Albany than Cornwall.</p> </sp> <sp n="2" who="#klgloucester"> <speaker>GLOUCESTER</speaker> <p>It did always seem so to us: but now, in the<lb/> division of the kingdom, it appears not which of<lb/> the dukes he values most; for equalities are so<lb/> weighed, that curiosity in neither can make choice<lb/> of either's moiety.</p> </sp> <sp n="3" who="#klkent"> <speaker>KENT</speaker> <p>Is not this your son, my lord?</p> </sp>  </div> </div>

1.6.5. Level 4 Oral History

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> as a list of <author> elements (typically each with a single <persName>) within <fileDesc> / <titleStmt>.

In either method, use an xml:id on the <persName> element to uniquely identify the individual participant:

The list of an interview’s participants can be also listed within the body of the interview (see example below).
Questions and answers from interviewees and interviewers are encoded as <sp>, with each speaker identified either
- within <speaker> elements, which are the first child of <sp>, or
- with a who attribute on <sp>, the value of which points to the the <item> for the given speaker in the list of interview participants (by its xml:id), or
- both.

<list type="simple"> <head>Interview Participants</head> <item> <persName xml:id="spk1" ref="tag:docsouth.unc.edu,2016:wf" type="interviewee">WILLIAM C. FRIDAY</persName>, interviewee </item> <item> <persName xml:id="spk2" ref="tag:docsouth.unc.edu,2016:wl" type="interviewer">WILLIAM LINK</persName>, interviewer </item> </list>  <sp who="#spk2"> <speaker n="2">WILLIAM LINK:</speaker> <p>Last time we were talking about Frank Porter Graham. And I have a couple of questions about Graham, and I wonder if you could clear them up for me. You have mentioned that you had worked with him as a student at North Carolina State, had you met him before?</p> </sp> <sp who="#spk1"> <speaker n="1">WILLIAM C. FRIDAY:</speaker> <p>No. That budget hearing was the first that I knew of him, of course, but the first time that I ever encountered him. I was president of class at N.C. State, and that through me into this kind of public adventure. And so I went merrily on downtown and sat there in the budget hearing, along with the president of the student body, and some others.</p> </sp>

One possible way to synchronize audio and transcript has been introduced in Oral Histories of the American South, using <milestone> with a timestamp attribute:

1.6.6. Level 4 Verse

Use <lg> and <l> as in Level 3. In addition, use the rend attribute to indicate lines that are indented.

For example,

<div type="fit" n="1"> <head>Fit the First: THE LANDING</head> <lg type="stanza" n="1"> <l n="1.1">"Just the place for a Snark!" the Bellman cried,</l> <l n="1.2" rend="margin-left: 0.5in">As he landed his crew with care;</l> <l n="1.3">Supporting each man on the top of the tide</l> <l n="1.4" rend="margin-left: 0.5in">By a finger entwined in his hair.</l> </lg> <lg type="stanza" n="2"> <l n="2.1">"Just the place for a Snark! I have said it twice:</l> <l n="2.2" rend="margin-left: 0.5in">That alone should encourage the crew.</l> <l n="2.3">Just the place for a Snark! I have said it thrice:</l> <l n="2.4" rend="margin-left: 0.5in">What I tell you three times is true."</l> </lg>  </div>

Lewis Carroll’s The Hunting of the Snark

1.6.7. Level 4 Typographic Separators

To mark typographic elements that indicate a structural break or boundary use <ab type="typography">. The content of this element is the character(s) or device used to mark the division in the source document. The style attribute may be used to indicate how the separator is rendered. As a content-bearing element, <ab> is recommended over the empty elements <milestone> or <space>, as it can contain further markup and glyph information. For example:

Like <pb> elements, these should always be placed within the lowest-level text division unless otherwise documented in the <editorialDecl>.

1.6.8. Level 4 Alger Hiss document

<TEI xml:id="project_document_identifier" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader xml:lang="en">  </teiHeader> <text xml:lang="en"> <body> <div1> <pb n="113" facs="./pageImages/AH4_0113.jpg"/> <head>POINT VIII.</head> <head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S <lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY, <lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head> <p>The nature and extent of surveillance of Hiss, his <lb/>family and associates was not known at the time of trial by <lb/>the defense. Even now, with the release of some of the govern- <lb break="no"/>ment documents concerning FBI investigative techniques regarding <lb/>Hiss, the full extent of surveillance -- wiretapping, mail open- <lb break="no"/>ings, mail covers, physical surveillance, and other intrusive <lb/>techniques -- is still not 'clear. Nevertheless, it is apparent <lb/>that information gathered through the exploitation of unlawful <lb/>wiretaps and other illegal surveillance was used at trial and <lb/>consequently the conviction must be reversed. Alternatively, <lb/>further discovery and a hearing is essential to a fair deter- <lb break="no"/>mination regarding these issues.</p> <p>FBI surveillance of Hiss began in earnest in 1941 with <lb/>the institution of a mail cover on his incoming correspondence <lb/>at his home in connection with an FBI investigation of possible <lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed <pb n="114" facs="./pageImages/AH_0114.jpg"/> on the Hiss mail in 1945, and at the same time the FBI obtained <lb/>toll call records from the Hiss residence Telephone for the <lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945, <lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p> <p>In late November, 1945, FBI surveillance of the Hiss <lb/>residence in Washington, D.C., escalated. For the third time, <lb/>a mail cover was instituted beginning on November 28, 1945, <lb/>which was continued at least until 1946. CN Ex. 101 at p. 70; <lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun <lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour <lb/>surveillance was discontinued on December 14, 1945, physical <lb/>surveillance was conducted frequently at various times until <lb/>September, 1947.<ptr target="#N68">68</ptr> <note place="bottom" anchored="true" xml:id="N68"> <label>68</label>Also before 1947, a letter from Priscilla Hiss addressed <lb/>to her son, Timothy Hobson, was intercepted and its contents <lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947, <lb/>a letter from a Michael Greenberg addressed to petitioner re- <lb break="no"/>garding an application for employment with the United Nations <lb/>was also intercepted, in a manner not revealed by the docu- <lb break="no"/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p> <p>The most intrusive invasion of petitioner's rights <pb n="115" facs="./pageImages/AH_0115.jpg"/> <lb/>occurred from December 13, 1945 until the Hisses moved from <lb/>Washington, D.C. to New York City on September 13, 1947. A <soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss <lb/>telephone at their residence on P Street-in Washington, D.C. <lb/>The logs of this surveillance constitute twenty-nine volumes <lb/>of FBI serials and are roughly 2,500 pages in length, in which <lb/>an enormous amount of information concerning the Hisses' per- <lb break="no"/>sonal lives, relationships with friends and associates, and <lb/>habits is recorded.</p> <p>The wiretap was installed following FBI Director Hoover's <lb/>application to the Attorney General for authorization, <ptr target="#N69">69</ptr> <note place="bottom" anchored="true" xml:id="N69"> <label>69</label>Hoover's initial request was answered by a note reques- <lb break="no"/>ting information on Hiss. CN Ex. 104<sic/>. Additional information <lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic/>.</note> <lb/>although no written authorization appears in the documents released to <lb/>Hiss. The purpose of the application was to gather information <lb/>regarding Hiss' alleged contacts with Soviet espionage agents and <lb/>communists in government service, general allegations which had <lb/>been made by Elizabeth Bentley and Chambers.</p> <p>As one would expect, the interception of every telephone</p> </div1> </body> </text> </TEI>

1.7. Specification

1.7.1. Schema lib4: Added components

1.7.1.1. <p>

<p>
Module	derived-module-lib4
Contained by	header: hyphenation
May contain	Empty element
Content model	<content> <valList type="closed"> <valItem ident="All hyphens in source document encoded as U+2010."/> <valItem ident="All hyphens in source document encoded as U+002D."/> <valItem ident="Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element."/> <valItem ident="Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element."/> <valItem ident="Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element."/> <valItem ident="Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element."/> </valList> </content> Legal values are: All hyphens in source document encoded as U+2010. All hyphens in source document encoded as U+002D. Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element. Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element. Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element. Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.
Schema Declaration	element p { "All hyphens in source document encoded as U+2010." \| "All hyphens in source document encoded as U+002D." \| "Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element." \| "Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element." \| "Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element." \| "Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element." } Legal values are: All hyphens in source document encoded as U+2010. All hyphens in source document encoded as U+002D. Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element. Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element. Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element. Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.

1.7.1.2. lib.teins

lib.teins
Module	derived-module-lib4
Used by	Element: namespace/@name
Content model	<content> <valList type="closed"> <valItem ident="http://www.tei-c.org/ns/1.0"/> </valList> </content>
Declaration	lib4_lib.teins = "http://www.tei-c.org/ns/1.0"

1.7.2. Schema lib4: changed components

1.7.2.1. <TEI>

<TEI> (TEI document) contains a single TEI-in-Libraries level 4 document, comprising a TEI header and a text, the latter represented as either a transcription (in <text>) or a transcription and page images (in <facsimile>), either in isolation or as part of a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]

Module

textstructure — Level 4: Basic Content Analysis

Attributes

version

specifies the major version number of the TEI Guidelines against which this document is valid.

Status	Optional
Datatype	teidata.version
Note	The major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the <schemaSpec> element. The current version is P5.

Contained by

—

May contain

header: teiHeader

textstructure: text

Note

This element is required. The TEI namespace should be specified on this element, e.g. <TEI xmlns="http://www.tei-c.org/ns/1.0">.

Example

Note that for technical reasons the namespace is not shown in this example, but it should always be supplied on the root <TEI> element, e.g.: <TEI xmlns="http://www.tei-c.org/ns/1.0">.

<TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader xml:lang="en"> <fileDesc> <titleStmt> <title>A Short Level 4 Document</title> </titleStmt> <publicationStmt> <p>Only published as an example.</p> </publicationStmt> <sourceDesc> <biblStruct> <monogr> <title>The Princess Bride</title> <title type="sub">S. Morgenstern’s Classic Tale of True Love and High Adventure</title> <imprint> <publisher>Harcourt Brace Jovanovich</publisher> <date when="1973"/> </imprint> </monogr> <idno type="isbn-10">0-345-41826-3</idno> </biblStruct> </sourceDesc> </fileDesc> <encodingDesc> <schemaRef key="BPTL-L4-v3.1.0a"/> <tagsDecl> <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="div">Unnumbered divs used.</tagUsage> </namespace> </tagsDecl> </encodingDesc> </teiHeader> <text> <body> <div type="chapter" n="1" xml:id="Ch1"> <head>The Bride</head> <p>The year that <persName>Buttercup</persName> was born, the most beautiful woman <lb/>in the world …</p>  </div> <div type="chapter" n="2" xml:id="Ch2"> <head>The Groom</head> <note resp="author"> <p>This is my first major excision. <ref target="#Ch1">Chapter One, The Bride</ref>, is almost <lb/>in its entirety about the bride. …</p> </note>  </div>  </body> </text> </TEI>

Schematron

<s:rule context="tei:TEI | tei:teiHeader | tei:teiHeader//*"> <s:report test="@rend or @rendition or @xml:space">The @rend, @rendition, and @xml:space attributes are not permitted on the root TEI element or within the teiHeader element</s:report> </s:rule>

Schematron

<s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> <s:ns prefix="xs" uri="http://www.w3.org/2001/XMLSchema"/>

Schematron

<s:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/>

Content model

<content>
 <elementRef key="teiHeader"/>
 <classRef key="model.resourceLike"
  minOccurs="0" maxOccurs="unbounded"/>
 <elementRef key="text"/>
</content>

Schema Declaration

element TEI
{
   lib4_att.global.attributes,
   lib4_att.typed.attributes,
   attribute version { text }?,
   lib4_teiHeader,
   model.resourceLike*,
   lib4_text
}

1.7.2.2. att.breaking

att.breaking provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. Milestone Elements]

Module

tei — Level 4: Basic Content Analysis

Members

cb lb pb

Attributes

break

indicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.

Status	Recommended
Datatype	teidata.enumerated
Legal values are:	yes the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace no the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace maybe the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum. <ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

1.7.2.3. att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]

Module

tei — Level 4: Basic Content Analysis

Members

TEI ab add addrLine address analytic appInfo application argument att author availability back bibl biblScope biblStruct birth body castItem castList cb cell change choice citedRange classCode classDecl closer corr correction date dateline del desc distinct distributor div div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email emph encodingDesc epigraph extent facsimile figDesc figure fileDesc floatingText foreign front gap geogName gi gloss graphic group head hi hyphenation idno imprint item keywords l label langUsage language lb lg list listBibl listPerson media mentioned monogr name namespace normalization note notesStmt opener orgName p pb persName person placeName postBox postCode postscript profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation quote ref relatedItem resp respStmt revisionDesc row said salute samplingDecl schemaRef series seriesStmt sic signed soCalled sourceDesc sp speaker stage street surface table tag tagUsage tagsDecl term text textClass textLang title titlePage titlePart titleStmt trailer unclear val zone

Attributes

Attributes att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)

xml:id

(identifier) provides a unique identifier for the element bearing the attribute.

Status	Optional
Datatype	ID
Note	The xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. Reference Systems.

(number) gives a number (or other label) for an element, which is not necessarily unique within the document.

Status	Optional
Datatype	teidata.text
Note	The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang

(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.

Status	Optional
Datatype	teidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note	The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages. The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php. The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:space

signals an intention about how white space should be managed by applications.

Status	Optional
Datatype	teidata.enumerated
Legal values are:	default signals that the application's default white-space processing modes are acceptable preserve indicates the intent that applications preserve all white space
Note	The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

1.7.2.4. att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.5.1. Referring Strings 3.6. Simple Links and Cross-References 3.5.5. Abbreviations and Their Expansions 3.12.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.2. RELAX NG Content Models 8.3. Elements Unique to Spoken Texts 23.3.1.4. Modification of Attribute and Attribute Value Lists]

Module

tei — Level 4: Basic Content Analysis

Members

TEI ab add application bibl biblStruct cb change corr date del desc figure floatingText geogName gloss group head label lb lg listBibl listPerson media name note orgName pb persName placeName ptr quote ref relatedItem schemaRef surface table term text trailer zone

Attributes

type

characterizes the element in some sense, using any convenient classification scheme or typology.

Status	Optional
Datatype	teidata.enumerated
<div type="verse"> <head>Night in Tarras</head> <lg type="stanza"> <l>At evening tramping on the hot white road</l> <l>…</l> </lg> <lg type="stanza"> <l>A wind sprang up from nowhere as the sky</l> <l>…</l> </lg> </div>
Note	The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

Schematron

<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>

Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.4. Modification of Attribute and Attribute Value Lists .

1.7.2.5. <author>

<author> in a bibliographic reference, contains the name (typically encoded as <persName> or <orgName>) of the author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.respLike
Contained by	core: analytic bibl monogr header: editionStmt titleStmt
May contain	core: add address cb choice corr date del distinct email emph foreign gap gloss graphic hi lb media mentioned name note pb ptr ref sic soCalled term title unclear figures: figure header: idno namesdates: geogName orgName persName placeName tagdocs: att gi tag val character data
Note	Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attribute 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.
Example	<author> <orgName>British Broadcasting Corporation</orgName> </author>
Example	<author> <persName ref="persons.xml#mdalmau.cny">Michelle Dalmau</persName> </author>
Example	<author>anonymous</author>
Example	<author>unknown</author>
Content model	<content> <macroRef key="macro.phraseSeq"/> </content>
Schema Declaration	element author { lib4_att.global.attributes, lib4_macro.phraseSeq }

1.7.2.6. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Module	textstructure — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: floatingText text transcr: facsimile
May contain	textstructure: div div1
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> <div1 type="appendix"> <head>The Golden Dream or, the Ingenuous Confession</head> <p>To shew the Depravity of human Nature </p> </div1> <div1 type="epistle"> <head>A letter from the Printer, which he desires may be inserted</head> <p>Sir. I have done with your Copy, so you may return it to the Vatican, if you please</p> </div1> <div1 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> <p> The Christmas Box, Price 1d. The History of Giles Gingerbread, 1d. A Curious Collection of Travels, selected from the Writers of all Nations, 10 Vol, Pr. bound 1l. </p> </div1> <div1 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> <p> Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d Dr. Hooper's Female Pills, 1s. </p> </div1> </back>
Content model	<content> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.divLike" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.div1Like" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content>
Schema Declaration	element back { lib4_att.global.attributes, ( lib4_model.divLike+ \| lib4_model.div1Like+ ) }

1.7.2.7. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Module	textstructure — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: floatingText text
May contain	textstructure: div div1
Note	At level 4, the content of <body> may contain only <div> or <div1> elements.
Example	<body> <head>LA FOREST NVPTIALE,</head> <p>Où e∫t repre∫entee vne varieté bigarree, non mois e∫merveillable que plai∫an‐ te, de diuers mariages, ∫elon qu’ils ∫ont ob∫erueZ & pratiqueZ par plu∫ieurs peuples & nations e∫tranges. Auec la maniere de policier, regir, gouuer‐ ner & admini∫trer leur famille.</p> <div type="chapter"> <head>Les Romains. CHAPITRE I.</head> <p>Encores que ie ne veuille me formali‐ ∫er contre le droict Romain, neãtmoins puis que le forma‐ litez, qui e∫toient an‐ ciennement gardees au nopces Romaines, ∫ont maintenant mi∫es hors d’v∫ages & pratique, ie ne ∫e‐ A <pb/> ray point de difficulté d’emprunter des anciens autheurs ce qui appar‐ <!-- ... --> </p> </div> </body>
Content model	<content> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.divLike" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.div1Like" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content>
Schema Declaration	element body { lib4_att.global.attributes, ( lib4_model.divLike+ \| lib4_model.div1Like+ ) }

1.7.2.8. <change>

<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]

Module

header — Level 4: Basic Content Analysis

Attributes

Attributes att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.datable (@calendar, @period) att.datable.w3c (when, @notBefore, @notAfter, @from, @to) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)

who

indicates the person, or group of people, to whom the element content is ascribed.

Derived from	att.ascribed
Status	Required
Datatype	1–∞ occurrences of teidata.pointer separated by whitespace

when

supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.

Derived from	att.datable.w3c
Status	Required
Datatype	teidata.temporal.w3c

target

points to one or more elements that belong to this change.

Status	Optional
Datatype	1–∞ occurrences of teidata.pointer separated by whitespace

Contained by

header: revisionDesc

May contain

core: add address bibl biblStruct cb choice corr date del desc distinct email emph foreign gap gloss graphic hi l label lb lg list listBibl media mentioned name note p pb ptr quote ref said sic soCalled sp stage term title unclear

drama: castList

figures: figure table

header: idno

linking: ab

namesdates: geogName listPerson orgName persName placeName

tagdocs: att gi tag val

textstructure: floatingText

character data

Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example

<titleStmt> <title> ... </title> <editor xml:id="LDB">Lou Burnard</editor> <respStmt xml:id="BZ"> <resp>copy editing</resp> <name>Brett Zamir</name> </respStmt> </titleStmt>  <revisionDesc status="published"> <change who="#BZ" when="2008-02-02" status="public">Finished chapter 23</change> <change who="#BZ" when="2008-01-02" status="draft">Finished chapter 2</change> <change n="P2.2" when="1991-12-21" who="#LDB">Added examples to section 3</change> <change when="1991-11-11" who="#MSM">Deleted chapter 10</change> </revisionDesc>

Example

<profileDesc> <creation> <listChange> <change xml:id="DRAFT1">First draft in pencil</change> <change xml:id="DRAFT2" notBefore="1880-12-09">First revision, mostly using green ink</change> <change xml:id="DRAFT3" notBefore="1881-02-13">Final corrections as supplied to printer.</change> </listChange> </creation> </profileDesc>

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element change
{
   lib4_att.datable.attribute.calendar,
   lib4_att.datable.attribute.period,
   lib4_att.datable.w3c.attribute.notBefore,
   lib4_att.datable.w3c.attribute.notAfter,
   lib4_att.datable.w3c.attribute.from,
   lib4_att.datable.w3c.attribute.to,
   lib4_att.datable.custom.attribute.when-custom,
   lib4_att.datable.custom.attribute.notBefore-custom,
   lib4_att.datable.custom.attribute.notAfter-custom,
   lib4_att.datable.custom.attribute.from-custom,
   lib4_att.datable.custom.attribute.to-custom,
   lib4_att.datable.custom.attribute.datingPoint,
   lib4_att.datable.custom.attribute.datingMethod,
   lib4_att.docStatus.attributes,
   lib4_att.global.attributes,
   lib4_att.typed.attributes,
   attribute who { list { + } },
   attribute when { text },
   attribute target { list { + } }?,
   lib4_macro.specialPara
}

1.7.2.9. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Module	textstructure — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.written (@hand)
Member of	model.divLike
Contained by	textstructure: back body div front
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div floatingText opener signed
Note	At level 4, <div> may only contain <head>, <p>, <pb>, <note>, and more <div> elements.
Example	<body> <div type="part"> <head>Fallacies of Authority</head> <p>The subject of which is Authority in various shapes, and the object, to repress all exercise of the reasoning faculty.</p> <div n="1" type="chapter"> <head>The Nature of Authority</head> <p>With reference to any proposed measures having for their object the greatest happiness of the greatest number [...]</p> <div n="1.1" type="section"> <head>Analysis of Authority</head> <p>What on any given occasion is the legitimate weight or influence to be attached to authority [...] </p> </div> <div n="1.2" type="section"> <head>Appeal to Authority, in What Cases Fallacious.</head> <p>Reference to authority is open to the charge of fallacy when [...] </p> </div> </div> </div> </body>
Schematron	<s:report test="not(@type)">Use of the <att>type</att> attribute of <gi>div</gi> is recommended</s:report>
Schematron	<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div. </s:report>
Schematron	<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div. </s:report>
Content model	<content> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <alternate minOccurs="0" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.divLike"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divLike"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> </sequence> </content>
Schema Declaration	element div { lib4_att.global.attributes, lib4_att.written.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( lib4_model.divLike, lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( lib4_model.divLike, lib4_model.global* )* ) )? ) }

1.7.2.10. <div1>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div1Like
Contained by	textstructure: back body front
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div2 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div2Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div2Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div1 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div2Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div2Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.11. <div2>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div2Like
Contained by	textstructure: div1
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div3 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div3Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div3Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div2 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div3Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div3Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.12. <div3>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div3Like
Contained by	textstructure: div2
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div4 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div4Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div4Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div3 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div4Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div4Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.13. <div4>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div4Like
Contained by	textstructure: div3
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div5 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div5Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div5Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div4 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div5Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div5Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.14. <div5>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div5Like
Contained by	textstructure: div4
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div6 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div6Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div6Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div5 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div6Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div6Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.15. <div6>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div6Like
Contained by	textstructure: div5
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: div7 floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div7Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.div7Like"/> <classRef key="model.divGenLike"/> </alternate> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </alternate> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div6 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( ( ( lib4_model.div7Like \| lib4_model.divGenLike ), lib4_model.global )+ \| ( ( lib4_model.common, lib4_model.global* )+, ( ( lib4_model.div7Like \| lib4_model.divGenLike ), lib4_model.global* )* ) ), lib4_model.global** )? ) }

1.7.2.16. <div7>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div7Like
Contained by	textstructure: div6
May contain	core: bibl biblStruct cb desc gap head l label lb lg list listBibl note p pb quote said sp stage drama: castList figures: figure table linking: ab namesdates: listPerson textstructure: floatingText opener signed
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> <sequence minOccurs="1" maxOccurs="1"> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.divTop"/> <classRef key="model.global"/> </alternate> <sequence minOccurs="0" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.common"/> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> <sequence minOccurs="0" maxOccurs="unbounded"> <classRef key="model.global" minOccurs="0" maxOccurs="unbounded"/> </sequence> </sequence> </sequence> </content>
Schema Declaration	element div7 { lib4_att.global.attributes, ( ( lib4_model.divTop \| lib4_model.global ), ( ( lib4_model.common, lib4_model.global )+, lib4_model.global** )? ) }

1.7.2.17. <editor>

<editor> contains the name (typically encoded as <persName> or <orgName>) of an individual, institution, or organization acting as editor. [3.11.2.2. Titles, Authors, and Editors]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.respLike
Contained by	core: analytic bibl monogr series header: editionStmt seriesStmt titleStmt
May contain	core: add address cb choice corr date del distinct email emph foreign gap gloss graphic hi lb media mentioned name note pb ptr ref sic soCalled term title unclear figures: figure header: idno namesdates: geogName orgName persName placeName tagdocs: att gi tag val character data
Note	A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.
Example	<editor> <persName ref="names.xml#khawkins.tvt">Kevin Hawkins</persName> </editor>
Content model	<content> <macroRef key="macro.phraseSeq"/> </content>
Schema Declaration	element editor { lib4_att.global.attributes, lib4_macro.phraseSeq }

1.7.2.18. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module	header — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	header: encodingDesc
May contain	core: p header: correction hyphenation normalization punctuation quotation linking: ab
Example	<editorialDecl> <p>Metadata in the TEI header comes from an AACR2-conformant record, translated to TEI via the <name type="software">Thutmose I</name> program.</p> <p>Content originally generated by <name type="software">c-n-rite</name> OCR software, then the needed TEI encoding put in place with <name type="software">cnr2tei.xslt</name>.</p> <correction method="markup" status="low"/> <normalization method="silent"> <p>Spacing between words and the following punctuation mark has been removed. Spacing between words has generally been regularized to one space.</p> </normalization> <normalization method="markup"> <p>Distances expressed in imperial units in the source have been normalized to the metric system using the attributes of the <gi>measure</gi> element.</p> </normalization> <hyphenation eol="all"> <p>All hyphens in source document encoded as U+2010.</p> </hyphenation> </editorialDecl>
Content model	<content> <sequence minOccurs="1" maxOccurs="1"> <elementRef key="correction" minOccurs="0" maxOccurs="1"/> <elementRef key="hyphenation" minOccurs="0" maxOccurs="1"/> <elementRef key="normalization" minOccurs="0" maxOccurs="1"/> <elementRef key="punctuation" minOccurs="0" maxOccurs="1"/> <elementRef key="quotation" minOccurs="0" maxOccurs="1"/> <classRef key="model.pLike" minOccurs="0" maxOccurs="6"/> </sequence> </content>
Schema Declaration	element editorialDecl { lib4_att.global.attributes, ( lib4_correction?, lib4_hyphenation?, lib4_normalization?, lib4_punctuation?, lib4_quotation?, ( lib4_model.pLike?, ( lib4_model.pLike, ( lib4_model.pLike, ( lib4_model.pLike, ( lib4_model.pLike, ( lib4_model.pLike, lib4_model.pLike? )? )? )? )? )? ) ) }

1.7.2.19. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Module	header — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	header: teiHeader
May contain	header: appInfo classDecl editorialDecl projectDesc schemaRef tagsDecl
Example	<encodingDesc> <p>Basic encoding, capturing lexical information only. All hyphenation, punctuation, and variant spellings normalized. No formatting or layout information preserved.</p> </encodingDesc>
Content model	<content> <sequence minOccurs="1" maxOccurs="1"> <elementRef key="projectDesc" minOccurs="0" maxOccurs="1"/> <elementRef key="schemaRef" minOccurs="0" maxOccurs="unbounded"/> <elementRef key="editorialDecl" minOccurs="1" maxOccurs="1"/> <elementRef key="tagsDecl" minOccurs="1" maxOccurs="1"/> <elementRef key="classDecl" minOccurs="0" maxOccurs="1"/> <elementRef key="appInfo" minOccurs="0" maxOccurs="1"/> </sequence> </content>
Schema Declaration	element encodingDesc { lib4_att.global.attributes, ( lib4_projectDesc?, lib4_schemaRef*, lib4_editorialDecl, lib4_tagsDecl, lib4_classDecl?, lib4_appInfo? ) }

1.7.2.20. <floatingText>

<floatingText> 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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Member of	model.qLike
Contained by	core: add corr del desc emph head hi item l note p quote ref said sic sp stage title unclear drama: castList figures: cell figDesc figure header: change rendition linking: ab textstructure: argument div div1 div2 div3 div4 div5 div6 div7 docEdition epigraph postscript salute signed titlePart trailer
May contain	textstructure: back body front group
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> <sequence minOccurs="1" maxOccurs="1"> <elementRef key="front" minOccurs="0"/> <alternate minOccurs="1" maxOccurs="1"> <elementRef key="body"/> <elementRef key="group"/> </alternate> <elementRef key="back" minOccurs="0"/> </sequence> </content>
Schema Declaration	element floatingText { lib4_att.global.attributes, lib4_att.typed.attributes, ( lib4_front?, ( lib4_body \| lib4_group ), lib4_back? ) }

1.7.2.21. <front>

<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 — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: floatingText text transcr: facsimile
May contain	textstructure: div div1
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> <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>
Content model	<content> <alternate minOccurs="1" maxOccurs="1"> <classRef key="model.divLike" minOccurs="1" maxOccurs="unbounded"/> <classRef key="model.div1Like" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content>
Schema Declaration	element front { lib4_att.global.attributes, ( lib4_model.divLike+ \| lib4_model.div1Like+ ) }

1.7.2.22. <head>

<head> (heading) contains the heading of a division (for example the title of a section), line group, list, figure, table, argument, or group. [4.2.1. Headings and Trailers]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.written (@hand)
Member of	model.headLike
Contained by	core: lg list listBibl drama: castList figures: figure table namesdates: listPerson textstructure: argument div div1 div2 div3 div4 div5 div6 div7 group postscript
May contain	core: add address bibl biblStruct cb choice corr date del desc distinct email emph foreign gap gloss graphic hi l label lb lg list listBibl media mentioned name note pb ptr quote ref said sic soCalled stage term title unclear drama: castList figures: figure table header: idno namesdates: geogName listPerson orgName persName placeName tagdocs: att gi tag val textstructure: floatingText character data
Note	The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a textual division (i.e., <div>, <divN>, or <lg>) 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	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> <alternate minOccurs="0" maxOccurs="unbounded"> <textNode/> <elementRef key="lg"/> <classRef key="model.gLike"/> <classRef key="model.phrase"/> <classRef key="model.inter"/> <classRef key="model.lLike"/> <classRef key="model.global"/> </alternate> </content>
Schema Declaration	element head { lib4_att.global.attributes, lib4_att.typed.attributes, lib4_att.written.attributes, ( text \| lib4_lg \| lib4_model.gLike \| lib4_model.phrase \| lib4_model.inter \| lib4_model.lLike \| lib4_model.global )* }

1.7.2.23. <hyphenation>

<hyphenation> summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]

Module

header — Level 4: Basic Content Analysis

Attributes

eol

(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.

Status	Optional
Datatype	teidata.enumerated
Legal values are:	all all end-of-line hyphenation has been retained, even though the lineation of the original may not have been. some end-of-line hyphenation has been retained in some cases.[Default] hard all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained. none all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.

Contained by

header: editorialDecl

May contain

core: p

derived-module-lib4: p

Example

<hyphenation eol="some"> <p>End-of-line hyphenation silently removed where appropriate</p> </hyphenation>

Content model

<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="hyphenation-para"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="p" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="p" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>

Schema Declaration

element hyphenation
{
   lib4_att.global.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   ( ( lib4_hyphenation-para, lib4_p* ) | ( lib4_p+ ) )
}

1.7.2.24. <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]

Module header — Level 4: Basic Content Analysis

Attributes

Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))

type

categorizes the identifier, for example as an ISBN, Social Security number, etc.

Derived from	att.typed
Status	Optional
Datatype	teidata.enumerated
Suggested values include:	ISBN International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency. ISSN International Standard Serial Number: an eight-digit number to uniquely identify a serial publication. DOI Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document. URI Uniform Resource Identifier: a string of characters to uniquely identify a resource which usually contains indication of the means of accessing that resource, the name of its host, and its filepath. VIAF A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity. ESTC English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801. OCLC union catalog number in WorldCat representing a resource held by one or more of the member libraries in the global cooperative Online Computer Library Center. LC_call_number (U.S. Library of Congress call number) LCCN (Library of Congress control number)

Member of

model.nameLike model.personPart model.publicationStmtPart.detail

Contained by

drama: castItem

figures: cell figDesc

header: change classCode distributor edition extent idno language publicationStmt rendition seriesStmt

linking: ab

namesdates: birth geogName orgName persName person placeName

textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

header: idno

character data

Note

<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Example

<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat"> <g ref="#sym"/>345 </idno>

In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>

Schema Declaration

element idno
{
   lib4_att.global.attributes,
   lib4_att.sortable.attributes,
   lib4_att.datable.attributes,
   attribute type
   {
      "ISBN"
    | "ISSN"
    | "DOI"
    | "URI"
    | "VIAF"
    | "ESTC"
    | "OCLC"
    | "LC_call_number"
    | "LCCN"
   }?,
   ( text | lib4_model.gLike | lib4_idno )*
}

1.7.2.25. <namespace>

<namespace> supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]

Module

header — Level 4: Basic Content Analysis

Attributes

name

specifies the full formal name of the namespace concerned.

Status	Required
Datatype	lib.teins

Contained by

header: tagsDecl

May contain

header: tagUsage

Example

<namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="hi" occurs="28" withId="2"> Used only to mark English words italicized in the copy text </tagUsage> </namespace>

Content model

<content>
 <elementRef key="tagUsage"/>
</content>

Schema Declaration

element namespace
{
   lib4_att.global.attributes,
   attribute name { text },
   lib4_tagUsage
}

1.7.2.26. <note>

<note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]

Module

core — Level 4: Basic Content Analysis

Attributes

Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type) att.written (@hand) att.pointing (target, @targetLang, @evaluate)

anchored

indicates whether the copy text shows the exact place of reference for the note.

Status	Optional
Datatype	teidata.truthValue
Default	true
Note	In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

Member of

model.noteLike

Contained by

drama: castItem castList

figures: cell figure table

header: change classCode distributor edition extent language notesStmt

linking: ab

namesdates: birth geogName orgName persName person placeName

transcr: surface zone

May contain

drama: castList

figures: figure table

header: idno

linking: ab

namesdates: geogName listPerson orgName persName placeName

tagdocs: att gi tag val

textstructure: floatingText

character data

Example

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottom" 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.

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:

<respStmt xml:id="MDMH"> <resp>translation from German to English</resp> <name>Hottinger, Marie Donald Mackie</name> </respStmt>

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>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element note
{
   lib4_att.global.attributes,
   lib4_att.placement.attributes,
   lib4_att.pointing.attribute.targetLang,
   lib4_att.pointing.attribute.evaluate,
   lib4_att.typed.attributes,
   lib4_att.written.attributes,
   attribute anchored { text }?,
   lib4_macro.specialPara
}

1.7.2.27. <orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Module	namesdates — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) att.typed (@type)
Member of	model.nameLike.agent
Contained by	core: add addrLine address author bibl biblScope citedRange corr date del desc distinct editor email emph foreign gloss head hi item l label mentioned name note p pubPlace publisher quote ref resp respStmt said sic soCalled speaker stage street term textLang title unclear drama: castItem figures: cell figDesc header: change classCode distributor edition extent language rendition linking: ab namesdates: birth geogName orgName persName placeName textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer
May contain	core: add address cb choice corr date del distinct email emph foreign gap gloss graphic hi lb media mentioned name note pb ptr ref sic soCalled term title unclear figures: figure header: idno namesdates: geogName orgName persName placeName tagdocs: att gi tag val character data
Example	About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary"> <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model	<content> <macroRef key="macro.phraseSeq"/> </content>
Schema Declaration	element orgName { lib4_att.global.attributes, lib4_att.personal.attributes, lib4_att.typed.attributes, lib4_macro.phraseSeq }

1.7.2.28. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Module	namesdates — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) att.typed (@type)
Member of	model.nameLike.agent
Contained by	core: add addrLine address author bibl biblScope citedRange corr date del desc distinct editor email emph foreign gloss head hi item l label mentioned name note p pubPlace publisher quote ref resp respStmt said sic soCalled speaker stage street term textLang title unclear drama: castItem figures: cell figDesc header: change classCode distributor edition extent language rendition linking: ab namesdates: birth geogName orgName persName placeName textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer
May contain	core: add address cb choice corr date del distinct email emph foreign gap gloss graphic hi lb media mentioned name note pb ptr ref sic soCalled term title unclear figures: figure header: idno namesdates: geogName orgName persName placeName tagdocs: att gi tag val character data
Example	<persName> <forename>Edward</forename> <forename>George</forename> <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of <placeName>Knebworth</placeName> </roleName> </persName>
Content model	<content> <macroRef key="macro.phraseSeq"/> </content>
Schema Declaration	element persName { lib4_att.global.attributes, lib4_att.personal.attributes, lib4_att.typed.attributes, lib4_macro.phraseSeq }

1.7.2.29. <person>

<person> provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]

Module

namesdates — Level 4: Basic Content Analysis

Attributes

role

specifies a primary role or classification for the person.

Status	Optional
Datatype	1–∞ occurrences of teidata.enumerated separated by whitespace
Note	Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sex

specifies the sex of the person.

Status	Optional
Datatype	1–∞ occurrences of teidata.sex separated by whitespace
Note	Values for this attribute may be locally defined by a project, or may refer to an external standard, such as vCard's sex property http://microformats.org/wiki/gender-formats (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes http://standards.iso.org/ittf/PubliclyAvailableStandards/c036266_ISO_IEC_5218_2004(E_F).zip (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People http://transhealth.ucsf.edu/trans?page=lib-data-collection.

age

specifies an age group for the person.

Status	Optional
Datatype	teidata.enumerated
Note	Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of

model.personLike

Contained by

namesdates: listPerson

May contain

core: bibl biblStruct cb gap lb listBibl note p pb

figures: figure

header: idno

linking: ab

namesdates: birth

Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example

<person sex="F" age="adult"> <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic status B2.</p> </person>

Example

<person sex="intersex" role="god" age="immortal"> <persName>Hermaphroditos</persName> <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>

Example

<person xml:id="Ovi01" sex="1" role="poet"> <persName xml:lang="en">Ovid</persName> <persName xml:lang="la">Publius Ovidius Naso</persName> <birth when="-0044-03-20"> 20 March 43 BC <placeName> <settlement type="city">Sulmona</settlement> <country key="IT">Italy</country> </placeName> </birth> <death notBefore="0017" notAfter="0018">17 or 18 AD <placeName> <settlement type="city">Tomis (Constanta)</settlement> <country key="RO">Romania</country> </placeName> </death> </person>

Content model

<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>

Schema Declaration

element person
{
   lib4_att.global.attributes,
   lib4_att.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute age { text }?,
   ( lib4_model.pLike+ | ( lib4_model.personPart | lib4_model.global )* )
}

1.7.2.30. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.6. Simple Links and Cross-References 16.1. Links]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.internetMedia (@mimeType) att.typed (@type)
Member of	model.ptrLike
Contained by	core: add addrLine analytic author bibl biblScope biblStruct citedRange corr date del desc distinct editor email emph foreign gloss head hi item l label mentioned monogr name note p pubPlace publisher quote ref relatedItem resp said series sic soCalled speaker stage street term textLang title unclear drama: castItem figures: cell figDesc header: application change classCode distributor edition extent language rendition linking: ab namesdates: birth geogName orgName persName placeName textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer
May contain	Empty element
Example	<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron	<s:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <s:name/>.</s:report>
Content model	<content/>
Schema Declaration	element ptr { lib4_att.global.attributes, lib4_att.pointing.attributes, lib4_att.internetMedia.attributes, lib4_att.typed.attributes, empty }

1.7.2.31. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Module	header — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	header: fileDesc
May contain	core: address date p pubPlace publisher header: availability distributor idno linking: ab
Note	For normally published items, the specialized children elements (e.g. <publisher>) should be used. Paragraphs are permitted as an alternative for unusual cases like unpublished works.
Example	<publicationStmt> <publisher>C. Muquardt </publisher> <pubPlace>Bruxelles & Leipzig</pubPlace> <date when="1846"/> </publicationStmt>
Example	<publicationStmt> <publisher>Chadwyck Healey</publisher> <pubPlace>Cambridge</pubPlace> <availability> <p>Available under licence only</p> </availability> <date when="1992">1992</date> </publicationStmt>
Schematron	<s:report test="child::tei:p">Use of specialized child elements of the publication statement (rather than paragraphs) is recommended whenever possible</s:report>
Schematron	<s:rule context="tei:publicationStmt/tei:date"> <s:assert test="@when">Dates inside the publication statement should have @when (and should not have content)</s:assert> <s:report test="string-length( normalize-space(.) ) > 0">Dates inside the publication statement should not have content (and should have @when)</s:report> </s:rule>
Content model	<content> <alternate minOccurs="1" maxOccurs="1"> <sequence minOccurs="1" maxOccurs="unbounded"> <classRef key="model.publicationStmtPart.agency"/> <classRef key="model.publicationStmtPart.detail" minOccurs="0" maxOccurs="unbounded"/> </sequence> <classRef key="model.pLike" minOccurs="1" maxOccurs="unbounded"/> </alternate> </content>
Schema Declaration	element publicationStmt { lib4_att.global.attributes, ( ( lib4_model.publicationStmtPart.agency, lib4_model.publicationStmtPart.detail* )+ \| lib4_model.pLike+ ) }

1.7.2.32. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.internetMedia (@mimeType) att.typed (@type)
Member of	model.ptrLike
Contained by	core: add addrLine analytic author bibl biblScope biblStruct citedRange corr date del desc distinct editor email emph foreign gloss head hi item l label mentioned monogr name note p pubPlace publisher quote ref relatedItem resp said series sic soCalled speaker stage street term textLang title unclear drama: castItem figures: cell figDesc header: application change classCode distributor edition extent language rendition linking: ab namesdates: birth geogName orgName persName placeName textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer
May contain	core: add address bibl biblStruct cb choice corr date del desc distinct email emph foreign gap gloss graphic hi l label lb lg list listBibl media mentioned name note pb ptr quote ref said sic soCalled stage term title unclear drama: castList figures: figure table header: idno namesdates: geogName listPerson orgName persName placeName tagdocs: att gi tag val textstructure: floatingText character data
Note	The target and cRef attributes are mutually exclusive.
Example	See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example	See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron	<s:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <s:name/> </s:report>
Content model	<content> <macroRef key="macro.paraContent"/> </content>
Schema Declaration	element ref { lib4_att.global.attributes, lib4_att.pointing.attributes, lib4_att.internetMedia.attributes, lib4_att.typed.attributes, lib4_macro.paraContent }

1.7.2.33. <rendition>

<rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]

Module

header — Level 4: Basic Content Analysis

Attributes

Attributesatt.global (xml:id, @n, @xml:lang, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source) att.styleDef (scheme, @schemeVersion)

xml:id

(identifier) provides a unique identifier for the element bearing the attribute.

Derived from	att.global
Status	Required
Datatype	ID

scheme

identifies the language used to describe the rendition.

Derived from	att.styleDef
Status	Required
Datatype	teidata.enumerated
Legal values are:	css Cascading Stylesheet Language

scope

where CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.

Status	Optional
Datatype	teidata.enumerated
Sample values include:	first-line styling applies to the first line of the target element first-letter styling applies to the first letter of the target element before styling should be applied immediately before the content of the target element after styling should be applied immediately after the content of the target element

selector

contains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.

Status	Optional
Datatype	teidata.text
<rendition scheme="css" selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css" selector="[rend=italic]"> font-style: italic; </rendition>
Note	Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.
Note	While rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

Contained by

header: tagsDecl

May contain

core: address bibl biblStruct choice date desc distinct email emph foreign gloss hi label list listBibl mentioned name ptr quote ref said soCalled stage term title

drama: castList

figures: table

header: idno

namesdates: geogName listPerson orgName persName placeName

tagdocs: att gi tag val

textstructure: floatingText

character data

Example

<tagsDecl> <rendition xml:id="r-center" scheme="css">text-align: center;</rendition> <rendition xml:id="r-small" scheme="css">font-size: small;</rendition> <rendition xml:id="r-large" scheme="css">font-size: large;</rendition> <rendition xml:id="initcaps" scope="first-letter" scheme="css">font-size: xx-large</rendition> </tagsDecl>

Content model

<content>
 <macroRef key="macro.limitedContent"/>
</content>

Schema Declaration

element rendition
{
   lib4_att.global.attribute.n,
   lib4_att.global.attribute.xmllang,
   lib4_att.global.attribute.xmlspace,
   lib4_att.global.rendition.attribute.rend,
   lib4_att.global.rendition.attribute.style,
   lib4_att.global.rendition.attribute.rendition,
   lib4_att.global.linking.attribute.corresp,
   lib4_att.global.linking.attribute.synch,
   lib4_att.global.linking.attribute.sameAs,
   lib4_att.global.linking.attribute.copyOf,
   lib4_att.global.linking.attribute.next,
   lib4_att.global.linking.attribute.prev,
   lib4_att.global.linking.attribute.exclude,
   lib4_att.global.linking.attribute.select,
   lib4_att.global.facs.attribute.facs,
   lib4_att.global.change.attribute.change,
   lib4_att.global.responsibility.attribute.cert,
   lib4_att.global.responsibility.attribute.resp,
   lib4_att.global.source.attribute.source,
   lib4_att.styleDef.attribute.schemeVersion,
   attribute xml:id { text },
   attribute scheme { "css" },
   attribute scope { text }?,
   attribute selector { text }?,
   lib4_macro.limitedContent
}

1.7.2.34. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module	core — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of	model.respLike
Contained by	core: analytic bibl imprint monogr series header: editionStmt seriesStmt titleStmt
May contain	core: name resp namesdates: orgName persName
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> <sequence minOccurs="1" maxOccurs="1"> <elementRef minOccurs="1" maxOccurs="1" key="resp"/> <classRef minOccurs="1" maxOccurs="unbounded" key="model.nameLike.agent"/> </sequence> </content>
Schema Declaration	element respStmt { lib4_att.global.attributes, lib4_att.canonical.attributes, ( lib4_resp, lib4_model.nameLike.agent+ ) }

1.7.2.35. <schemaRef>

<schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.9. The Schema Specification]

Module

header — Level 4: Basic Content Analysis

Attributes

key

the identifier used for the customization or schema

Status	Optional
Datatype	teidata.enumerated
Suggested values include:	BPTL-L1-v3.4.1a (Best Practices for TEI in Libraries level 1, version 3.4.1a) BPTL-L2-v3.4.1a (Best Practices for TEI in Libraries level 2, version 3.4.1a) BPTL-L3-v3.4.1a (Best Practices for TEI in Libraries level 3, version 3.4.1a) BPTL-L4-v3.4.1a (Best Practices for TEI in Libraries level 4, version 3.4.1a) BPTL-L5-v3.4.1a (Best Practices for TEI in Libraries level 5, version 3.4.1a)

Contained by

header: encodingDesc

May contain

core: desc

Example

Content model

<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>

Schema Declaration

element schemaRef
{
   lib4_att.global.attributes,
   lib4_att.typed.attributes,
   lib4_att.resourced.attributes,
   attribute key
   {
      "BPTL-L1-v3.4.1a"
    | "BPTL-L2-v3.4.1a"
    | "BPTL-L3-v3.4.1a"
    | "BPTL-L4-v3.4.1a"
    | "BPTL-L5-v3.4.1a"
   }?,
   lib4_model.descLike?
}

1.7.2.36. <sourceDesc>

<sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Module	header — Level 4: Basic Content Analysis
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	header: fileDesc
May contain	core: biblStruct
Example	<sourceDesc> <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> </sourceDesc>
Example	<sourceDesc> <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model	<content> <elementRef key="biblStruct"/> </content>
Schema Declaration	element sourceDesc { lib4_att.global.attributes, lib4_biblStruct }

1.7.2.37. <tagUsage>

<tagUsage> documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]

Module

header — Level 4: Basic Content Analysis

Attributes

(element name) the name (generic identifier) of the element indicated by the tag.

Status	Required
Datatype	teidata.enumerated
Schematron	<s:rule context="tei:text"> <s:report test=".//tei:div and .//tei:div1">A single TEI in Libraries document should not mix numbered and unnumbered divisions. </s:report> </s:rule> <s:rule context="tei:TEI"> <s:assert test="/tei:TEI/tei:teiHeader/tei:encodingDesc/tei:tagsDecl/tei:namespace/tei:tagUsage/@gi">The use of divisions (i.e., whether numbered or unnumbered divisions are used) should be documented in a <tagUsage> element by "Unnumbered divs used." or "Numbered divs used." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element. </s:assert> </s:rule> <s:rule context="tei:tagUsage"> <s:assert test="( @gi eq 'div' and normalize-space(.) eq 'Unnumbered divs used.' and not( /tei:TEI/tei:text//tei:div1 ) ) or ( @gi eq 'div1' and normalize-space(.) eq 'Numbered divs used.' and not( /tei:TEI/tei:text//tei:div ) )">A document that uses un-numbered divisions should specify so by using <tagUsage gi="div">Unnumbered divs used.</tagUsage>; a document that uses numbered divisions should specify so by using <tagUsage gi="div1">Numbered divs used.</tagUsage>.</s:assert> </s:rule>
Legal values are:	div (divisions are un-numbered) The document uses <div>, not <div1>, <div2>, etc. The content of this <tagUsage> should be ‘Unnumbered divs used.’. div1 (divisions are numbered) The document uses <div1> (and perhaps <div2>, etc.), not <div> elements. The content of this <tagUsage> should be ‘Numbered divs used.’.

occurs

specifies the number of occurrences of this element within the text.

Status	Recommended
Datatype	teidata.count

withId

(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.

Status	Recommended
Datatype	teidata.count

render

specifies the identifier of a <rendition> element which defines how this element was rendered in the source text.

Deprecated	will be removed on 2017-01-01
Status	Optional
Datatype	1–∞ occurrences of teidata.pointer separated by whitespace
Note	The recommended way of specifying a default rendition for a set of elements is to use the selector attribute on the <rendition> element.

Contained by

header: namespace

May contain

Empty element

Example

<tagsDecl partial="true"> <rendition xml:id="it" scheme="css" selector="foreign hi"> font-style: italic; </rendition>  <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="hi" occurs="28" withId="2"> Used to mark English words italicized in the copy text.</tagUsage> <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage>  </namespace> </tagsDecl>

Example

<tagsDecl>  <rendition xml:id="dit">Render using a slant or italic variant on the current font</rendition>  <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="hi" occurs="28" withId="2" render="#dit"> Used to mark English words italicized in the copy text.</tagUsage> <tagUsage gi="foreign" render="#dit">Used to mark non-English words in the copy text.</tagUsage>  </namespace> </tagsDecl>

Content model

<content>
 <valList type="closed">
  <valItem ident="Unnumbered divs used."/>
  <valItem ident="Numbered divs used."/>
 </valList>
</content>

Legal values are:

Unnumbered divs used.
Numbered divs used.

Schema Declaration

element tagUsage
{
   lib4_att.global.attributes,
   attribute gi { "div" | "div1" }
   >>
   tei:constraintSpec
   [
      scheme = "isoschematron"
      ident = "numbered-vs-unnumbered"
      " "
      " A single TEI in Libraries document should not mix numbered and unnumbered divisions."
      " "
      " "
      """ The use of divisions (i.e., whether numbered or unnumbered divisions are used) should be documented in a <tagUsage> element by "Unnumbered divs used." or "Numbered divs used." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element."""
      " "
      " "
      """ A document that uses un-numbered divisions should specify so by using <tagUsage gi="div">Unnumbered divs used.</tagUsage>; a document that uses numbered divisions should specify so by using <tagUsage gi="div1">Numbered divs used.</tagUsage>."""
   ],
   attribute occurs { text }?,
   attribute withId { text }?,
   attribute render { list { + } }?,
   ( "Unnumbered divs used." | "Numbered divs used." )
}

Legal values are:

Unnumbered divs used.
Numbered divs used.

1.7.2.38. <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]

Module

header — Level 4: Basic Content Analysis

Attributes

partial

indicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.

Status	Recommended
Datatype	teidata.truthValue
Note	TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Contained by

header: encodingDesc

May contain

header: namespace rendition

Example

<tagsDecl partial="true"> <rendition xml:id="rend-it" scheme="css" selector="emph hi name title">font-style: italic;</rendition> <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="hi" occurs="467"/> <tagUsage gi="title" occurs="45"/> </namespace> <namespace name="http://docbook.org/ns/docbook"> <tagUsage gi="para" occurs="10"/> </namespace> </tagsDecl>

If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace"/>
 </sequence>
</content>

Schema Declaration

element tagsDecl
{
   lib4_att.global.attributes,
   attribute partial { text }?,
   ( lib4_rendition*, lib4_namespace )
}

1.7.2.39. <taxonomy>

<taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]

Module

header — Level 4: Basic Content Analysis

Attributes

xml:id

(identifier) provides a unique identifier for the element bearing the attribute.

Derived from	att.global
Status	Required
Datatype	ID

Contained by

header: classDecl taxonomy

May contain

core: bibl biblStruct desc gloss listBibl

header: taxonomy

Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Example

<taxonomy xml:id="tax.b"> <bibl>Brown Corpus</bibl> <category xml:id="tax.b.a"> <catDesc>Press Reportage</catDesc> <category xml:id="tax.b.a1"> <catDesc>Daily</catDesc> </category> <category xml:id="tax.b.a2"> <catDesc>Sunday</catDesc> </category> <category xml:id="tax.b.a3"> <catDesc>National</catDesc> </category> <category xml:id="tax.b.a4"> <catDesc>Provincial</catDesc> </category> <category xml:id="tax.b.a5"> <catDesc>Political</catDesc> </category> <category xml:id="tax.b.a6"> <catDesc>Sports</catDesc> </category> </category> <category xml:id="tax.b.d"> <catDesc>Religion</catDesc> <category xml:id="tax.b.d1"> <catDesc>Books</catDesc> </category> <category xml:id="tax.b.d2"> <catDesc>Periodicals and tracts</catDesc> </category> </category> </taxonomy>

Example

<taxonomy> <category xml:id="literature"> <catDesc>Literature</catDesc> <category xml:id="poetry"> <catDesc>Poetry</catDesc> <category xml:id="sonnet"> <catDesc>Sonnet</catDesc> <category xml:id="shakesSonnet"> <catDesc>Shakespearean Sonnet</catDesc> </category> <category xml:id="petraSonnet"> <catDesc>Petrarchan Sonnet</catDesc> </category> </category> <category xml:id="haiku"> <catDesc>Haiku</catDesc> </category> </category> <category xml:id="drama"> <catDesc>Drama</catDesc> </category> </category> <category xml:id="meter"> <catDesc>Metrical Categories</catDesc> <category xml:id="feet"> <catDesc>Metrical Feet</catDesc> <category xml:id="iambic"> <catDesc>Iambic</catDesc> </category> <category xml:id="trochaic"> <catDesc>trochaic</catDesc> </category> </category> <category xml:id="feetNumber"> <catDesc>Number of feet</catDesc> <category xml:id="pentameter"> <catDesc>>Pentameter</catDesc> </category> <category xml:id="tetrameter"> <catDesc>>Tetrameter</catDesc> </category> </category> </category> </taxonomy>  <lg ana="#shakesSonnet #iambic #pentameter"> <l>Shall I compare thee to a summer's day</l>  </lg>

Content model

<content>
 <alternate minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.glossLike"/>
     <classRef key="model.descLike"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>

Schema Declaration

element taxonomy
{
   lib4_att.global.attribute.n,
   lib4_att.global.attribute.xmllang,
   lib4_att.global.attribute.xmlspace,
   lib4_att.global.rendition.attribute.rend,
   lib4_att.global.rendition.attribute.style,
   lib4_att.global.rendition.attribute.rendition,
   lib4_att.global.linking.attribute.corresp,
   lib4_att.global.linking.attribute.synch,
   lib4_att.global.linking.attribute.sameAs,
   lib4_att.global.linking.attribute.copyOf,
   lib4_att.global.linking.attribute.next,
   lib4_att.global.linking.attribute.prev,
   lib4_att.global.linking.attribute.exclude,
   lib4_att.global.linking.attribute.select,
   lib4_att.global.facs.attribute.facs,
   lib4_att.global.change.attribute.change,
   lib4_att.global.responsibility.attribute.cert,
   lib4_att.global.responsibility.attribute.resp,
   lib4_att.global.source.attribute.source,
   attribute xml:id { text },
   (
      (
         ( category | lib4_taxonomy )+
       | (
            ( lib4_model.glossLike | lib4_model.descLike )+,
            ( category | lib4_taxonomy )*
         )
      )
    | ( lib4_model.biblLike, ( category | lib4_taxonomy )* )
   )
}

1.7.2.40. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]

Module

header — Level 4: Basic Content Analysis

Attributes

Attributesatt.global (xml:lang, @xml:id, @n, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)

xml:lang

(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.

Derived from	att.global
Status	Required
Datatype	teidata.language

Contained by

textstructure: TEI

May contain

header: encodingDesc fileDesc profileDesc revisionDesc

Note

One of the few elements unconditionally required in any TEI document.

Example

<teiHeader> <fileDesc> <titleStmt> <title>Shakespeare: the first folio (1623) in electronic form</title> <author>Shakespeare, William (1564–1616)</author> <respStmt> <resp>Originally prepared by</resp> <name>Trevor Howard-Hill</name> </respStmt> <respStmt> <resp>Revised and edited by</resp> <name>Christine Avern-Carr</name> </respStmt> </titleStmt> <publicationStmt> <distributor>Oxford Text Archive</distributor> <address> <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine> </address> <idno type="OTA">119</idno> <availability> <p>Freely available on a non-commercial basis.</p> </availability> <date when="1968">1968</date> </publicationStmt> <sourceDesc> <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile, 1968)</bibl> </sourceDesc> </fileDesc> <encodingDesc> <projectDesc> <p>Originally prepared for use in the production of a series of old-spelling concordances in 1968, this text was extensively checked and revised for use during the editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p> </projectDesc> <editorialDecl> <correction> <p>Turned letters are silently corrected.</p> </correction> <normalization> <p>Original spelling and typography is retained, except that long s and ligatured forms are not encoded.</p> </normalization> </editorialDecl> <refsDecl xml:id="ASLREF"> <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)" replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])"> <p>A reference is created by assembling the following, in the reverse order as that listed here: <list> <item>the <att>n</att> value of the preceding <gi>lb</gi> </item> <item>a period</item> <item>the <att>n</att> value of the ancestor <gi>div2</gi> </item> <item>a space</item> <item>the <att>n</att> value of the parent <gi>div1</gi> </item> </list> </p> </cRefPattern> </refsDecl> </encodingDesc> <revisionDesc> <list> <item> <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item> <item> <date when="1989-03-01">1 Mar 89</date> LB made new file</item> </list> </revisionDesc> </teiHeader>

Schematron

<s:report test=".//tei:ab">Use <gi>p</gi> instead of <gi>ab</gi> in the TEI header. (There are <s:value-of select="count(.//tei:ab)"/> <gi>ab</gi> elements in this header.)</s:report>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="fileDesc" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="encodingDesc"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="profileDesc"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="revisionDesc"
   minOccurs="0" maxOccurs="1"/>
 </sequence>
</content>

Schema Declaration

element teiHeader
{
   lib4_att.global.attribute.xmlid,
   lib4_att.global.attribute.n,
   lib4_att.global.attribute.xmlspace,
   lib4_att.global.rendition.attribute.rend,
   lib4_att.global.rendition.attribute.style,
   lib4_att.global.rendition.attribute.rendition,
   lib4_att.global.linking.attribute.corresp,
   lib4_att.global.linking.attribute.synch,
   lib4_att.global.linking.attribute.sameAs,
   lib4_att.global.linking.attribute.copyOf,
   lib4_att.global.linking.attribute.next,
   lib4_att.global.linking.attribute.prev,
   lib4_att.global.linking.attribute.exclude,
   lib4_att.global.linking.attribute.select,
   lib4_att.global.facs.attribute.facs,
   lib4_att.global.change.attribute.change,
   lib4_att.global.responsibility.attribute.cert,
   lib4_att.global.responsibility.attribute.resp,
   lib4_att.global.source.attribute.source,
   attribute xml:lang { text },
   ( lib4_fileDesc, lib4_encodingDesc, lib4_profileDesc?, lib4_revisionDesc? )
}

1.7.2.41. <title>

<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]

Module

core — Level 4: Basic Content Analysis

Attributes

Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))

type

Status	Recommended
Datatype	teidata.enumerated
Schematron	<s:rule context="tei:titleStmt/tei:title"> <s:assert test="@type">Inside the title statment the @type of a <title> should be specified</s:assert> </s:rule> <s:rule context="tei:monogr/tei:title"> <s:assert test="@type">Inside a structured bibliographic citation of a mongraphic-level item, @type of a <title> should be specified</s:assert> </s:rule> <s:rule context="tei:analytic/tei:title"> <s:assert test="@type">Inside the analytic portion of a structured bibliographic citation, @type of a <title> should be specified</s:assert> </s:rule> <s:rule context="tei:relatedItem/tei:bibl/tei:title"> <s:assert test="@type">Inside a bibliographic citation of a related item, the @type of a <title> should be specified</s:assert> </s:rule>
Suggested values include:	main main title sub (subordinate) subtitle, title of part alt (alternate) alternate title, often in another language, by which the work is also known short abbreviated form of title desc (descriptive) translated a translation of a title marc245a used for the title proper and alternative title according to the national cataloging code marc245b used for the the remainder of the title information — parallel titles, titles subsequent to the first, and other title information — according to the national cataloging code) marc245c used for the statement of responsibility according to the national cataloging code uniform used for a uniform title according to the national cataloging code

level

indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.

Status	Optional
Schematron	<s:rule context="tei:fileDesc/tei:titleStmt/tei:title"> <s:report test="@level">The @level attribute should not be specified on a <title> within the <titleStmt>.</s:report> </s:rule> <s:rule context="tei:title[parent::tei:seriesStmt]"> <s:assert test="@level='s'">When a child of <seriesStmt>, the level of a title should be specified as 's'.</s:assert> </s:rule> <s:rule context="tei:title[ancestor::tei:series]"> <s:assert test="@level='s'">When inside the series-level portion of a structured bibliographic citation, the level of a title should be specified as 's'.</s:assert> </s:rule> <s:rule context="tei:title[parent::tei:analytic]"> <s:assert test="@level='a'">When a child of <analytic>, the level of a title should be specified as 'a'.</s:assert> </s:rule> <s:rule context="tei:title[parent::tei:monogr]"> <s:report test="@level='a'">When a child of <monogr>, the level of a title should not be specified as 'a'.</s:report> </s:rule>
Legal values are:	a (analytic) analytic title (article, poem, or other item published as part of a larger item) m (monographic) monographic title (book, collection, or other item published as a distinct item, including single volumes of multi-volume works) j (journal) journal title s (series) series title u (unpublished) title of unpublished material (including theses and dissertations unless published by a commercial press)
Note	The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level a, and one appearing within a <series> element of level s. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of

model.emphLike

Contained by

drama: castItem

figures: cell figDesc

header: change classCode distributor edition extent language rendition seriesStmt titleStmt

linking: ab

namesdates: birth geogName orgName persName placeName

textstructure: closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

drama: castList

figures: figure table

header: idno

namesdates: geogName listPerson orgName persName placeName

tagdocs: att gi tag val

textstructure: floatingText

character data

Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example

<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>

Example

<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>

Example

<title type="full"> <title type="main">Synthèse</title> <title type="sub">an international journal for epistemology, methodology and history of science</title> </title>

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element title
{
   lib4_att.global.attributes,
   lib4_att.canonical.attributes,
   lib4_att.datable.attributes,
   attribute type
   {
      "main"
    | "sub"
    | "alt"
    | "short"
    | "desc"
    | "translated"
    | "marc245a"
    | "marc245b"
    | "marc245c"
    | "uniform"
   }?
   >>
   tei:constraintSpec
   [
      scheme = "isoschematron"
      ident = "titleType"
      " "
      "Inside the title statment the @type of a <title> should be specified"
      " "
      " "
      "Inside a structured bibliographic citation of a mongraphic-level item, @type of a <title> should be specified"
      " "
      " "
      "Inside the analytic portion of a structured bibliographic citation, @type of a <title> should be specified"
      " "
      " "
      "Inside a bibliographic citation of a related item, the @type of a <title> should be specified"
   ],
   attribute level { "a" | "m" | "j" | "s" | "u" }?
   >>
   tei:constraintSpec
   [
      scheme = "isoschematron"
      ident = "titleLevel"
      " "
      "The @level attribute should not be specified on a <title> within the <titleStmt>."
      " "
      " "
      """When a child of <seriesStmt>, the level of a title should be specified as 's'."""
      " "
      " "
      """When inside the series-level portion of a structured bibliographic citation, the level of a title should be specified as 's'."""
      " "
      " "
      """When a child of <analytic>, the level of a title should be specified as 'a'."""
      " "
      " "
      """When a child of <monogr>, the level of a title should not be specified as 'a'."""
   ],
   lib4_macro.paraContent
}

1.7.3. Schema lib4: unchanged components

ab: (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. Blocks, Segments, and Anchors]

add: (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]

addrLine: (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]

address: contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]

analytic: (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.11.2.1. Analytic, Monographic, and Series Levels]

appInfo: (application information) records information about an application which has edited the TEI file. [2.3.10. The Application Information Element]

application: provides information about an application which has acted upon the document. [2.3.10. The Application Information Element]

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]

att: (attribute) contains the name of an attribute appearing within running text. [22. Documentation Elements]

att.ascribed: provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]

att.cReferencing: provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.

att.canonical: provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.

att.citing: provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]

att.datable: provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.6. Dates and Times]

att.datable.custom: provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.6. Dates and Times]

att.datable.w3c: provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.6. Dates and Times]

att.docStatus: provides attributes for use on metadata elements describing the status of a document.

att.edition: provides attributes identifying the source edition from which some encoded feature derives.

att.fragmentable: provides an attribute for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.

att.global.change: supplies the change attribute, allowing its member elements to specify one or more states or revision campaigns with which they are associated.

att.global.facs: provides an attribute used to express correspondence between an element containing transcribed text and all or part of an image representing that text. [11.1. Digital Facsimiles]

att.global.linking: provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]

att.global.rendition: provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]

att.global.responsibility: provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]

att.global.source: provides an attribute used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]

att.internetMedia: provides attributes for specifying the type of a computer resource using a standard taxonomy.

att.media: provides attributes for specifying display and related properties of external media.

att.personal: (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]

att.placement: provides attributes for describing where on the source page or object a textual element appears. [3.4.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]

att.pointing: provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.6. Simple Links and Cross-References]

att.resourced: provides attributes by which a resource (such as an externally held media file) may be located.

att.sortable: provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]

att.spanning: provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]

att.styleDef: provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.

att.tableDecoration: provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics and Notated Music]

att.timed: provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]

att.transcriptional: provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]

att.translatable: provides attributes used to indicate the status of a translatable portion of an ODD document.

att.written: provides an attribute to indicate the hand in which the textual content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]

availability: supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]

bibl: (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

biblScope: (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]

biblStruct: (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

birth: contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]

castItem: (cast list item) contains a single entry within a cast list, describing either a single role or a list of non-speaking roles. [7.1.4. Cast Lists]

castList: (cast list) contains a single cast list or dramatis personae. [7.1.4. Cast Lists 7.1. Front and Back Matter ]

cb: (column break) marks the beginning of a new column of a text on a multi-column page. [3.10.3. Milestone Elements]

cell: contains one cell of a table. [14.1.1. TEI Tables]

choice: groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]

citedRange: (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.5. Scopes and Ranges in Bibliographic Citations]

classCode: (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]

classDecl: (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]

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]

corr: (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors]

correction: (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]

date: contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]

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]

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.4.3. Additions, Deletions, and Omissions]

desc: (description) contains a brief description of the object documented by its parent element, typically a documentation element or an entity. [22.4.1. Description of Components]

distinct: identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]

distributor: supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]

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]

docDate: (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]

docEdition: (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]

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]

docTitle: (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]

edition: describes the particularities of one edition of a text. [2.2.2. The Edition Statement]

editionStmt: (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]

email: (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.5.2. Addresses]

emph: (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

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]

extent: describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]

facsimile: contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]

figDesc: (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]

figure: groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]

fileDesc: (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]

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]

gap: indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions]

geogName: (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]

gi: (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.5. Element Specifications]

gloss: identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. Terms, Glosses, Equivalents, and Descriptions 22.4.1. Description of Components]

graphic: indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.9. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]

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 15.1. Varieties of Composite Text]

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]

imprint: groups information relating to the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]

item: contains one component of a list. [3.7. Lists 2.6. The Revision Description]

keywords: contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]

l: (verse line) contains a single, possibly incomplete, line of verse. [3.12.1. Core Tags for Verse 3.12. Passages of Verse or Drama 7.2.5. Speech Contents]

label: contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists]

langUsage: (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]

language: characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

lb: (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone Elements 7.2.5. Speech Contents]

lg: (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.12.1. Core Tags for Verse 3.12. Passages of Verse or Drama 7.2.5. Speech Contents]

list: contains any sequence of items organized as a list. [3.7. Lists]

listBibl: (citation list) contains a list of bibliographic citations of any kind. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

listPerson: (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements]

macro.limitedContent: (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]

macro.paraContent: (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]

macro.phraseSeq: (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]

macro.phraseSeq.limited: (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]

macro.specialPara: ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]

media: indicates the location of any form of external media such as an audio or video clip etc. [3.9. Graphics and Other Non-textual Components]

mentioned: marks words or phrases mentioned, not used. [3.3.3. Quotation]

model.addrPart: groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. Addresses]

model.addressLike: groups elements used to represent a postal or email address. [1. The TEI Infrastructure]

model.applicationLike: groups elements used to record application-specific information about a document in its header.

model.availabilityPart: groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]

model.biblLike: groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]

model.biblPart: groups elements which represent components of a bibliographic description. [3.11. Bibliographic Citations and References]

model.castItemPart: groups component elements of an entry in a cast list, such as dramatic role or actor's name.

model.certLike: groups elements which are used to indicate uncertainty or precision of other elements.

model.choicePart: groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. Simple Editorial Changes]

model.common: groups common chunk- and inter-level elements. [1.3. The TEI Class System]

model.dateLike: groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.6. Dates and Times]

model.descLike: groups elements which contain a description of their function.

model.div1Like: groups top-level structural divisions.

model.div2Like: groups second-level structural divisions.

model.div3Like: groups third-level structural divisions.

model.div4Like: groups fourth-level structural divisions.

model.div5Like: groups fifth-level structural divisions.

model.div6Like: groups sixth-level structural divisions.

model.div7Like: groups seventh-level structural divisions.

model.divGenLike: groups elements used to represent a structural division which is generated rather than explicitly present in the source.

model.divLike: groups elements used to represent un-numbered generic structural divisions.

model.divPart: groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]

model.divTop: groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]

model.divTopPart: groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]

model.egLike: groups elements containing examples or illustrations. [22.1.1. Phrase Level Terms]

model.emphLike: groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]

model.eventLike: groups elements which describe events.

model.gLike: groups elements used to represent individual non-Unicode characters or glyphs.

model.global: groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]

model.global.edit: groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]

model.global.meta: groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]

model.glossLike: groups elements which provide an alternative name, explanation, or description for any markup construct.

model.graphicLike: groups elements containing images, formulae, and similar objects. [3.9. Graphics and Other Non-textual Components]

model.headLike: groups elements used to provide a title or heading at the start of a text division.

model.hiLike: groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]

model.highlighted: groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]

model.imprintPart: groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References]

model.inter: groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]

model.lLike: groups elements representing metrical components such as verse lines.

model.lPart: groups phrase-level elements which may appear within verse only. [6.2. Components of the Verse Line]

model.labelLike: groups elements used to gloss or explain other parts of a document.

model.limitedPhrase: groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]

model.linePart: groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.

model.listLike: groups list-like elements. [3.7. Lists]

model.measureLike: groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. Numbers and Measures]

model.milestoneLike: groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.10.3. Milestone Elements]

model.nameLike: groups elements which name or refer to a person, place, or organization.

model.nameLike.agent: groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]

model.noteLike: groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing]

model.oddDecl: groups elements which generate declarations in some markup language in ODD documents.

model.offsetLike: groups elements which can appear only as part of a place name. [13.2.3. Place Names]

model.pLike: groups paragraph-like elements.

model.pPart.data: groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]

model.pPart.edit: groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]

model.pPart.editorial: groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. Simple Editorial Changes]

model.pPart.msdesc: groups phrase-level elements used in manuscript description. [10. Manuscript Description]

model.pPart.transcriptional: groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. Simple Editorial Changes]

model.persNamePart: groups elements which form part of a personal name. [13.2.1. Personal Names]

model.personLike: groups elements which provide information about people and their relationships.

model.personPart: groups elements which form part of the description of a person. [15.2.2. The Participant Description]

model.phrase: groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]

model.phrase.xml: groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements]

model.placeNamePart: groups elements which form part of a place name. [13.2.3. Place Names]

model.placeStateLike: groups elements which describe changing states of a place.

model.profileDescPart: groups elements which may be used inside <profileDesc> and appear multiple times.

model.ptrLike: groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]

model.publicationStmtPart.agency: groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]

model.publicationStmtPart.detail: groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]

model.qLike: groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]

model.quoteLike: groups elements used to directly contain quotations.

model.respLike: groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.

model.segLike: groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

model.specDescLike: groups elements for referring to specification elements. [22. Documentation Elements]

model.stageLike: groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]

model.titlepagePart: groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]

monogr: (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.11.2.1. Analytic, Monographic, and Series Levels]

name: (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings]

no-extent-in-fileDesc:

normalization: indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]

notesStmt: (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]

onlyAllowedAttrs:

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]

p: (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]

pb: (page break) marks the start of a new page in a paginated document. [3.10.3. Milestone Elements]

placeName: contains an absolute or relative place name. [13.2.3. Place Names]

postBox: (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.5.2. Addresses]

postCode: (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.5.2. Addresses]

postscript: contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]

profileDesc: (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]

projectDesc: (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]

pubPlace: (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]

publisher: provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]

punctuation: specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]

quotation: specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]

quote: (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]

relatedItem: contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.11.2.7. Related Items]

resp: (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

revisionDesc: (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]

row: contains one row of a table. [14.1.1. TEI Tables]

said: (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]

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]

samplingDecl: (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]

series: (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.11.2.1. Analytic, Monographic, and Series Levels]

seriesStmt: (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]

sic: (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. Apparent Errors]

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]

soCalled: contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]

sp: (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.12.2. Core Tags for Drama 3.12. Passages of Verse or Drama 7.2.2. Speeches and Speakers]

speaker: contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.12.2. Core Tags for Drama]

stage: (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.12.2. Core Tags for Drama 3.12. Passages of Verse or Drama 7.2.4. Stage Directions]

street: contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.5.2. Addresses]

surface: defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]

table: contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]

tag: contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [22. Documentation Elements]

teidata.certainty: defines the range of attribute values expressing a degree of certainty.

teidata.count: defines the range of attribute values used for a non-negative integer value used as a count.

teidata.duration.iso: defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats

teidata.duration.w3c: defines the range of attribute values available for representation of a duration in time using W3C datatypes.

teidata.enumerated: defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.

teidata.language: defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]

teidata.name: defines the range of attribute values expressed as an XML Name.

teidata.namespace: defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.

teidata.numeric: defines the range of attribute values used for numeric values.

teidata.outputMeasurement: defines a range of values for use in specifying the size of an object that is intended for display.

teidata.pattern: defines attribute values which are expressed as a regular expression.

teidata.pointer: defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.

teidata.probCert: defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.

teidata.probability: defines the range of attribute values expressing a probability.

teidata.replacement: defines attribute values which contain a replacement template.

teidata.sex: defines the range of attribute values used to identify human or animal sex.

teidata.temporal.w3c: defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.

teidata.text: defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.

teidata.truthValue: defines the range of attribute values used to express a truth value.

teidata.unboundedInt: defines an attribute value which can be either any non-negative integer or the string "unbounded".

teidata.version: defines the range of attribute values which may be used to specify a TEI or Unicode version number.

teidata.versionNumber: defines the range of attribute values used for version numbers.

teidata.word: defines the range of attribute values expressed as a single word or token.

teidata.xTruthValue: (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.

teidata.xmlName: defines attribute values which contain an XML name.

term: contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]

text: contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]

textClass: (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]

textLang: (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]

titlePage: (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages]

titlePart: contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages]

titleStmt: (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]

trailer: contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]

unclear: contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.4.3. Additions, Deletions, and Omissions]

val: (value) contains a single attribute value. [22. Documentation Elements 22.5.4. Attribute List Specification]

when-or-before-after:

zone: defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]

(unknown project)

TEI in Libraries level 4

Best Practices for TEI in Libraries

Level 4: Basic Content Analysis

Setting

Table of contents

1. Level 4: Basic Content Analysis

1.1. Reference

1.2. Purpose

1.3. Rationale

1.4. Workflow

1.5. Element Recommendations for Level 4

1.6. General Level 4 Recommendations and Examples

1.6.1. Level 4 Front and Back Matter

1.6.2. Level 4 Name Tagging

1.6.3. Level 4 Embedded Texts

1.6.4. Level 4 Drama

1.6.5. Level 4 Oral History

1.6.6. Level 4 Verse

1.6.7. Level 4 Typographic Separators

1.6.8. Level 4 Alger Hiss document

1.7. Specification

1.7.1. Schema lib4: Added components

1.7.1.1. <p>

1.7.1.2. lib.teins

1.7.2. Schema lib4: changed components

1.7.2.1. <TEI>

1.7.2.2. att.breaking

1.7.2.3. att.global

1.7.2.4. att.typed

1.7.2.5. <author>

1.7.2.6. <back>

1.7.2.7. <body>

1.7.2.8. <change>

1.7.2.9. <div>

1.7.2.10. <div1>

1.7.2.11. <div2>

1.7.2.12. <div3>

1.7.2.13. <div4>

1.7.2.14. <div5>

1.7.2.15. <div6>

1.7.2.16. <div7>

1.7.2.17. <editor>

1.7.2.18. <editorialDecl>

1.7.2.19. <encodingDesc>

1.7.2.20. <floatingText>

1.7.2.21. <front>

1.7.2.22. <head>

1.7.2.23. <hyphenation>

1.7.2.24. <idno>

1.7.2.25. <namespace>

1.7.2.26. <note>

1.7.2.27. <orgName>

1.7.2.28. <persName>

1.7.2.29. <person>

1.7.2.30. <ptr>

1.7.2.31. <publicationStmt>

1.7.2.32. <ref>

1.7.2.33. <rendition>

1.7.2.34. <respStmt>

1.7.2.35. <schemaRef>

1.7.2.36. <sourceDesc>

1.7.2.37. <tagUsage>

1.7.2.38. <tagsDecl>

1.7.2.39. <taxonomy>

1.7.2.40. <teiHeader>

1.7.2.41. <title>

1.7.3. Schema lib4: unchanged components