TEI in Libraries level 2

1. Level 2: Minimal Encoding

1.1. Reference

Note that this is a ‘syntactically conformant’ customization, in that documents that are valid against this scheme will also be valid against the TEI_all schema. However, it is unkown whether or not it is truly ‘TEI conformant’, as the TEI Guidelines do not make clear whether or not encoding of individual paragraphs is mandatory.

1.2. Purpose

To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

1.3. Rationale

The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Use cases for Level 2 require a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are not intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

Level 2 is most suitable for projects in which

a large volume of material is to be made available online quickly
a digital image of each page is desired
the material is of interest to a large community of users who wish to read texts that allow keyword searching
rudimentary search and display capabilities based on the large structures of the text are desired
each text is checked to ensure that textual divisions and headers are properly identified
extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

1.4. Workflow

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the textual divisions is created, likely based on the page images. The textual division metadata might contain the page number on which the division begins and a transcription of that division's heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

1.5. Element Recommendations for Level 2

Use all elements specified in Level 1 plus the following:

<front>, <back>	Optional. Contains one or more <div> or <div1>.
<body>	Contains one or more <div> or <div1>.
<div1> or <div>	Unlike in Level 1, in Level 2 one <div> or <div1> is used per section of the text identified with division-level metadata. If no type attribute is specified, a type value of section should be presumed.
<head>	Recommended if headings are present. As in the TEI Guidelines, this element must appear before the <ab> for that division.

1.6. Level 2 Examples

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

1.6.1. Level 2 Basic Structure

<TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader xml:lang="en">  </teiHeader> <text xml:lang="en"> <front>  <div type="titlePage"> <pb facs="[URI of title page image]"/> <ab>[ entire title page here ]</ab> </div> <div type="TOC"> <pb n="ii" facs="[URI of table of contents]"/> <head>[ heading of table of contents ]</head> <ab>[ entire table of contents here ]</ab> </div> <div type="preface"> <head>[ heading of preface ]</head> <ab>[ entire preface, with interspersed <pb/> elements pointing to page images as needed, here ]</ab> </div> </front> <body> <div type="section"> <pb n="1" facs="[URI of page 1 image]"/> <head>[ heading of section 1 ]</head> <ab>[ entire contents of section 1 here, with interspersed <gi>pb</gi> elements pointing to page images; in this example there are 26 more pages to section 1 ]</ab> </div> <div type="section"> <pb n="27" facs="[URI of page 27 image]"/> <div type="subsection"> <head>[ heading of section 2 subsection 1 ]</head> <ab>[ all the paragraphs of subsection one go here with page breaks inserted ]</ab> </div> </div> </body> <back>  </back> </text> </TEI>

1.6.2. Level 2 Alger Hiss document

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

1.7. Specification

1.7.1. Schema lib2: Added components

1.7.1.1. <p>

<p>
Module	derived-module-lib2
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-lib2
Used by	Element: namespace/@name
Content model	<content> <valList type="closed"> <valItem ident="http://www.tei-c.org/ns/1.0"/> </valList> </content>
Declaration	lib2_lib.teins = "http://www.tei-c.org/ns/1.0"

1.7.2. Schema lib2: changed components

1.7.2.1. <TEI>

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

Module

textstructure — Level 2: Minimal Encoding

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

<TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <fileDesc> <titleStmt> <title>A Short Level 2 Document</title> </titleStmt> <publicationStmt> <p>Only published as an example.</p> </publicationStmt> <sourceDesc> <p>Since this is an example, it doesn't really have a source</p> </sourceDesc> </fileDesc> </teiHeader> <text> <body> <div> <ab>This is about the shortest TEI document imaginable.</ab> </div> </body> </text> </TEI>

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"/>
 <elementRef key="text"/>
</content>

Schema Declaration

element TEI
{
   lib2_att.global.attributes,
   attribute version { text }?,
   lib2_teiHeader,
   model.resourceLike?,
   lib2_text
}

1.7.2.2. <ab>

<ab> (anonymous block) contains the entire content of a division of the document; or, when used within the <teiHeader>, 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]
Module	linking — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Member of	model.pLike
Contained by	core: item note q quote header: application availability change correction editionStmt editorialDecl langUsage normalization projectDesc publicationStmt punctuation quotation samplingDecl seriesStmt textstructure: div div1
May contain	core: pb character data
Note	At level 2, entire sections of the document (be they parts, chapters, etc.) are each encoded as a single <ab> — each division (whether <div>, <div1>, <div2>, etc.) should have one and only one <ab> child. Further, <ab> may be used in a variety of places within the <teiHeader>.
Example	<publicationStmt> <availability> <ab>Copyleft 2009 Syd Bauman</ab> </availability> </publicationStmt>
Example	<body> <div> <head>Genesis</head> <ab> In the beginning God created the heaven and the earth. And the earth was without form, and void; and darkness was upon the face of the deep. And the spirit of God moved upon the face of the waters. And God said, Let there be light: and there was light. </ab> </div> </body>
Schematron	<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum \|parent::tei:item \|parent::tei:note \|parent::tei:q \|parent::tei:quote \|parent::tei:remarks \|parent::tei:said \|parent::tei:sp \|parent::tei:stage \|parent::tei:cell \|parent::tei:figure)"> Abstract model violation: ab may not contain paragraphs or other ab elements. </s:report>
Schematron	<s:report test="ancestor::tei:l or ancestor::tei:lg"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab. </s:report>
Content model	<content> <alternate minOccurs="1" maxOccurs="unbounded"> <textNode/> <classRef key="model.global"/> </alternate> </content>
Schema Declaration	element ab { lib2_att.global.attributes, lib2_att.typed.attributes, ( text \| lib2_model.global )+ }

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 2: Minimal Encoding

Members

TEI ab abbr addrLine address analytic appInfo application att author availability back bibl biblScope biblStruct body change choice cit citedRange classCode classDecl correction date distributor div div1 edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign front gi gloss graphic head hyphenation idno imprint item keywords label langUsage language list media monogr name namespace normalization note notesStmt orgName p pb persName postBox postCode profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote ref relatedItem resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc street surface tag tagUsage tagsDecl term text textClass textLang title titleStmt val

Attributes

Attributes att.global.rendition (@style) 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.global.rendition

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

Module

tei — Level 2: Minimal Encoding

Members

att.global[TEI ab abbr addrLine address analytic appInfo application att author availability back bibl biblScope biblStruct body change choice cit citedRange classCode classDecl correction date distributor div div1 edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign front gi gloss graphic head hyphenation idno imprint item keywords label langUsage language list media monogr name namespace normalization note notesStmt orgName p pb persName postBox postCode profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote ref relatedItem resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc street surface tag tagUsage tagsDecl term text textClass textLang title titleStmt val]

Attributes

style

contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text

Status	Optional
Datatype	teidata.text
<head style="text-align: center; font-variant: small-caps"> <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/> <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note	Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output. The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

1.7.2.5. 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 2: Minimal Encoding

Members

ab application bibl biblStruct change cit date gloss head label media name note orgName pb persName ptr quote ref relatedItem schemaRef surface term text

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.6. <author>

<author> in a bibliographic reference, contains the name (typically encoded as <name>, <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 monogr header: editionStmt titleStmt
May contain	core: abbr address choice date email emph expan foreign gloss graphic media name pb ptr ref term title header: idno namesdates: orgName persName 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 an <orgName> inside 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> <name>Gibson, Matthew</name> </author>
Example	<author>anonymous</author>
Example	<author>unknown</author>
Content model	<content> <macroRef key="macro.phraseSeq"/> </content>
Schema Declaration	element author { lib2_att.global.attributes, lib2_att.canonical.attributes, lib2_macro.phraseSeq }

1.7.2.7. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: text
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> <ab>To shew the Depravity of human Nature </ab> </div1> <div1 type="epistle"> <head>A letter from the Printer, which he desires may be inserted</head> <ab>Sir. I have done with your Copy, so you may return it to the Vatican, if you please</ab> </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> <ab> 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. </ab> </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> <ab> Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d Dr. Hooper's Female Pills, 1s. </ab> </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 { lib2_att.global.attributes, ( lib2_model.divLike+ \| lib2_model.div1Like+ ) }

1.7.2.8. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: text
May contain	textstructure: div div1
Note	At level 2, the content of <body> may contain only <head>, <ab>, <pb>, <note>, and either <div> or <div1> elements.
Example	<body> <head>LA FOREST NVPTIALE,</head> <ab>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.</ab> <div type="chapter"> <head>Les Romains. CHAPITRE I.</head> <ab>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‐ <!-- ... --> </ab> </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 { lib2_att.global.attributes, ( lib2_model.divLike+ \| lib2_model.div1Like+ ) }

1.7.2.9. <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 2: Minimal Encoding

Attributes

Attributes att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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: abbr address bibl biblStruct choice cit date email emph expan foreign gloss graphic label list media name p pb ptr q quote ref term title

header: idno

linking: ab

namesdates: orgName persName

tagdocs: att gi tag val

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
{
   lib2_att.datable.attribute.calendar,
   lib2_att.datable.attribute.period,
   lib2_att.datable.w3c.attribute.notBefore,
   lib2_att.datable.w3c.attribute.notAfter,
   lib2_att.datable.w3c.attribute.from,
   lib2_att.datable.w3c.attribute.to,
   lib2_att.datable.custom.attribute.when-custom,
   lib2_att.datable.custom.attribute.notBefore-custom,
   lib2_att.datable.custom.attribute.notAfter-custom,
   lib2_att.datable.custom.attribute.from-custom,
   lib2_att.datable.custom.attribute.to-custom,
   lib2_att.datable.custom.attribute.datingPoint,
   lib2_att.datable.custom.attribute.datingMethod,
   lib2_att.docStatus.attributes,
   lib2_att.global.attributes,
   lib2_att.typed.attributes,
   attribute who { list { + } },
   attribute when { text },
   attribute target { list { + } }?,
   lib2_macro.specialPara
}

1.7.2.10. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 front
May contain	core: head pb linking: ab
Note	At level 2, <div> may contain only an optional <head> followed by a required <ab>; also <pb> and <note> elements may be interspersed anywhere as needed.
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="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> <classRef key="model.global" minOccurs="0"/> <classRef key="model.divTop" minOccurs="0"/> <classRef key="model.global" minOccurs="0"/> <elementRef key="ab"/> <classRef key="model.global" minOccurs="0"/> </content>
Schema Declaration	element div { lib2_att.global.attributes, lib2_att.written.attributes, lib2_model.global?, lib2_model.divTop?, lib2_model.global?, lib2_ab, lib2_model.global? }

1.7.2.11. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of	model.div1Like model.divLike
Contained by	textstructure: back body front
May contain	core: head pb linking: ab
Note	At level 2, <div1> may contain only an optional <head> followed by a required <ab>.
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> <classRef key="model.global" minOccurs="0"/> <classRef key="model.divTop" minOccurs="0"/> <classRef key="model.global" minOccurs="0"/> <elementRef key="ab"/> <classRef key="model.global" minOccurs="0"/> </content>
Schema Declaration	element div1 { lib2_att.global.attributes, lib2_model.global?, lib2_model.divTop?, lib2_model.global?, lib2_ab, lib2_model.global? }

1.7.2.12. <editor>

<editor> contains the name (typically encoded as <name>, <persName>, or <orgName>) of an individual, institution, or organization acting as editor. [3.11.2.2. Titles, Authors, and Editors]
Module	core — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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: abbr address choice date email emph expan foreign gloss graphic media name pb ptr ref term title header: idno namesdates: orgName persName 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 { lib2_att.global.attributes, lib2_macro.phraseSeq }

1.7.2.13. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 { lib2_att.global.attributes, ( lib2_correction?, lib2_hyphenation?, lib2_normalization?, lib2_punctuation?, lib2_quotation?, ( lib2_model.pLike?, ( lib2_model.pLike, ( lib2_model.pLike, ( lib2_model.pLike, ( lib2_model.pLike, ( lib2_model.pLike, lib2_model.pLike? )? )? )? )? )? ) ) }

1.7.2.14. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 { lib2_att.global.attributes, ( lib2_projectDesc?, lib2_schemaRef*, lib2_editorialDecl, lib2_tagsDecl, lib2_classDecl?, lib2_appInfo? ) }

1.7.2.15. <facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
Module	transcr — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	—
May contain	transcr: surface
Example	<facsimile> <graphic url="page1.png"/> <surface> <graphic url="page2-highRes.png"/> <graphic url="page2-lowRes.png"/> </surface> <graphic url="page3.png"/> <graphic url="page4.png"/> </facsimile>
Example	<facsimile> <surface ulx="0" uly="0" lrx="200" lry="300"> <graphic url="Bovelles-49r.png"/> </surface> </facsimile>
Content model	<content> <elementRef key="surface" minOccurs="1" maxOccurs="unbounded"/> </content>
Schema Declaration	element facsimile { lib2_att.global.attributes, lib2_surface+ }

1.7.2.16. <front>

<front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Module	textstructure — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by	textstructure: text
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"> <ab>To our three selves</ab> </div> <div type="preface"> <head>Author's Note</head> <ab>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. ...</ab> </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 { lib2_att.global.attributes, ( lib2_model.divLike+ \| lib2_model.div1Like+ ) }

1.7.2.17. <graphic>

<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]
Module	core — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url)
Member of	model.graphicLike
Contained by	core: abbr addrLine author biblScope citedRange date editor email emph expan foreign gloss head item label name note p pubPlace publisher q quote ref street term textLang title header: change distributor edition extent namesdates: orgName persName transcr: surface
May contain	Empty element
Note	The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded.
Example	<figure> <graphic url="fig1.png"/> <head>Figure One: The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> </figure>
Example	<facsimile> <surfaceGrp n="leaf1"> <surface> <graphic url="page1.png"/> </surface> <surface> <graphic url="page2-highRes.png"/> <graphic url="page2-lowRes.png"/> </surface> </surfaceGrp> </facsimile>
Content model	<content/>
Schema Declaration	element graphic { lib2_att.global.attributes, lib2_att.media.attributes, lib2_att.resourced.attributes, empty }

1.7.2.18. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Module	core — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Member of	model.headLike
Contained by	core: list textstructure: div div1
May contain	core: abbr address bibl biblStruct choice cit date email emph expan foreign gloss graphic label list media name pb ptr q quote ref term title header: idno namesdates: orgName persName tagdocs: att gi tag val 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 <div> or <div1> is the title of that chapter or section.
Example	The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example: <div1 n="I" type="book"> <head>In the name of Christ here begins the first book of the ecclesiastical history of Georgius Florentinus, known as Gregory, Bishop of Tours.</head> <div2 type="section"> <head>In the name of Christ here begins Book I of the history.</head> <p>Proposing as I do ...</p> <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve years passed.</p> <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six years from the beginning of the world down to the death of Saint Martin.</trailer> </div2> </div1>
Example	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/> <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 { lib2_att.global.attributes, lib2_att.typed.attributes, ( text \| lib2_model.gLike \| lib2_model.phrase \| lib2_model.inter \| lib2_model.lLike \| lib2_model.global )* }

1.7.2.19. <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 2: Minimal Encoding

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-lib2: 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
{
   lib2_att.global.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   ( ( lib2_hyphenation-para, lib2_p* ) | ( lib2_p+ ) )
}

1.7.2.20. <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 2: Minimal Encoding

Attributes

Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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.publicationStmtPart.detail

Contained by

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

namesdates: orgName persName

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
{
   lib2_att.global.attributes,
   lib2_att.sortable.attributes,
   lib2_att.datable.attributes,
   attribute type
   {
      "ISBN"
    | "ISSN"
    | "DOI"
    | "URI"
    | "VIAF"
    | "ESTC"
    | "OCLC"
    | "LC_call_number"
    | "LCCN"
   }?,
   ( text | lib2_model.gLike | lib2_idno )*
}

1.7.2.21. model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Module	tei — Level 2: Minimal Encoding
Used by	head macro.limitedContent macro.paraContent macro.specialPara
Members	model.biblLike[bibl biblStruct] model.egLike model.labelLike[label] model.listLike[list] model.oddDecl model.qLike[model.quoteLike[cit quote] q] model.stageLike

1.7.2.22. model.noteLike

model.noteLike groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing]
Module	tei — Level 2: Minimal Encoding
Used by	biblStruct monogr notesStmt
Members	note

1.7.2.23. <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 2: Minimal Encoding

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
{
   lib2_att.global.attributes,
   attribute name { text },
   lib2_tagUsage
}

1.7.2.24. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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.noteLike
Contained by	core: biblStruct monogr header: notesStmt
May contain	core: abbr address bibl biblStruct choice cit date email emph expan foreign gloss graphic label list media name p pb ptr q quote ref term title header: idno linking: ab namesdates: orgName persName tagdocs: att gi tag val 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 { lib2_att.global.attributes, lib2_att.typed.attributes, lib2_att.written.attributes, lib2_macro.specialPara }

1.7.2.25. <orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Module	namesdates — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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: abbr addrLine address author bibl biblScope citedRange date editor email emph expan foreign gloss head item label name note p pubPlace publisher q quote ref resp respStmt street term textLang title header: change classCode distributor edition extent language rendition namesdates: orgName persName
May contain	core: abbr address choice date email emph expan foreign gloss graphic media name pb ptr ref term title header: idno namesdates: orgName persName 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 { lib2_att.global.attributes, lib2_att.personal.attributes, lib2_att.typed.attributes, lib2_macro.phraseSeq }

1.7.2.26. <pb>

<pb> (page break) marks the start of a new page in a paginated document. [3.10.3. Milestone Elements]
Module	core — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break) att.edition (ed, @edRef)
Member of	model.milestoneLike
Contained by	core: abbr addrLine address author bibl biblScope cit citedRange date editor email emph expan foreign gloss head imprint item label list name note p pubPlace publisher q quote ref resp series street term textLang title header: change classCode distributor edition extent language linking: ab namesdates: orgName persName textstructure: div div1 text
May contain	Empty element
Note	A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself. The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.
Example	Page numbers may vary in different editions of a text. <p> ... <pb n="145" ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
Example	A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body> <pb n="1" facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here --> <p> <!-- ... --> </p> <pb n="2" facs="page2.png"/> <!-- similarly, for page 2 --> <p> <!-- ... --> </p> </body>
Content model	<content/>
Schema Declaration	element pb { lib2_att.global.attributes, lib2_att.typed.attributes, lib2_att.edition.attribute.edRef, lib2_att.spanning.attributes, lib2_att.breaking.attributes, empty }

1.7.2.27. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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: abbr addrLine address author bibl biblScope citedRange date editor email emph expan foreign gloss head item label name note p pubPlace publisher q quote ref resp respStmt street term textLang title header: change classCode distributor edition extent language rendition namesdates: orgName persName
May contain	core: abbr address choice date email emph expan foreign gloss graphic media name pb ptr ref term title header: idno namesdates: orgName persName 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 { lib2_att.global.attributes, lib2_att.personal.attributes, lib2_att.typed.attributes, lib2_macro.phraseSeq }

1.7.2.28. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.6. Simple Links and Cross-References 16.1. Links]
Module	core — Level 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.typed (@type)
Member of	model.ptrLike
Contained by	core: abbr addrLine analytic author bibl biblScope biblStruct cit citedRange date editor email emph expan foreign gloss head item label monogr name note p pubPlace publisher q quote ref relatedItem resp series street term textLang title header: application change classCode distributor edition extent language rendition namesdates: orgName persName
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 { lib2_att.global.attributes, lib2_att.internetMedia.attributes, lib2_att.typed.attributes, empty }

1.7.2.29. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 { lib2_att.global.attributes, ( ( lib2_model.publicationStmtPart.agency, lib2_model.publicationStmtPart.detail* )+ \| lib2_model.pLike+ ) }

1.7.2.30. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.typed (@type)
Member of	model.ptrLike
Contained by	core: abbr addrLine analytic author bibl biblScope biblStruct cit citedRange date editor email emph expan foreign gloss head item label monogr name note p pubPlace publisher q quote ref relatedItem resp series street term textLang title header: application change classCode distributor edition extent language rendition namesdates: orgName persName
May contain	core: abbr address bibl biblStruct choice cit date email emph expan foreign gloss graphic label list media name pb ptr q quote ref term title header: idno namesdates: orgName persName tagdocs: att gi tag val 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 { lib2_att.global.attributes, lib2_att.internetMedia.attributes, lib2_att.typed.attributes, lib2_macro.paraContent }

1.7.2.31. <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 2: Minimal Encoding

Attributes

Attributesatt.global (xml:id, @n, @xml:lang, @xml:space) att.global.rendition (@style) 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: abbr address bibl biblStruct choice cit date email emph expan foreign gloss label list name ptr q quote ref term title

header: idno

namesdates: orgName persName

tagdocs: att gi tag val

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
{
   lib2_att.global.attribute.n,
   lib2_att.global.attribute.xmllang,
   lib2_att.global.attribute.xmlspace,
   lib2_att.global.rendition.attribute.style,
   lib2_att.global.facs.attribute.facs,
   lib2_att.global.change.attribute.change,
   lib2_att.global.responsibility.attribute.cert,
   lib2_att.global.responsibility.attribute.resp,
   lib2_att.global.source.attribute.source,
   lib2_att.styleDef.attribute.schemeVersion,
   attribute xml:id { text },
   attribute scheme { "css" },
   attribute scope { text }?,
   attribute selector { text }?,
   lib2_macro.limitedContent
}

1.7.2.32. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 { lib2_att.global.attributes, lib2_att.canonical.attributes, ( lib2_resp, lib2_model.nameLike.agent+ ) }

1.7.2.33. <schemaRef>

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

Module

header — Level 2: Minimal Encoding

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

Empty element

Example

Content model

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

Schema Declaration

element schemaRef
{
   lib2_att.global.attributes,
   lib2_att.typed.attributes,
   lib2_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"
   }?,
   lib2_model.descLike?
}

1.7.2.34. <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 2: Minimal Encoding
Attributes	Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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 { lib2_att.global.attributes, lib2_biblStruct }

1.7.2.35. <surface>

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

Module

transcr — Level 2: Minimal Encoding

Attributes

attachment

describes the method by which this surface is or was connected to the main surface

Status	Optional
Datatype	teidata.enumerated
Sample values include:	glued glued in place pinned pinned or stapled in place sewn sewn in place

flipping

indicates whether the surface is attached and folded in such a way as to provide two writing surfaces

Status	Optional
Datatype	teidata.truthValue

Contained by

transcr: facsimile

May contain

core: graphic

Note

The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Example

Content model

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

Schema Declaration

element surface
{
   lib2_att.global.attributes,
   lib2_att.typed.attributes,
   attribute attachment { text }?,
   attribute flipping { text }?,
   lib2_graphic
}

1.7.2.36. <tagUsage>

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

Module

header — Level 2: Minimal Encoding

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
{
   lib2_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.37. <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 2: Minimal Encoding

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
{
   lib2_att.global.attributes,
   attribute partial { text }?,
   ( lib2_rendition*, lib2_namespace )
}

1.7.2.38. <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 2: Minimal Encoding

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 gloss

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
{
   lib2_att.global.attribute.n,
   lib2_att.global.attribute.xmllang,
   lib2_att.global.attribute.xmlspace,
   lib2_att.global.rendition.attribute.style,
   lib2_att.global.facs.attribute.facs,
   lib2_att.global.change.attribute.change,
   lib2_att.global.responsibility.attribute.cert,
   lib2_att.global.responsibility.attribute.resp,
   lib2_att.global.source.attribute.source,
   attribute xml:id { text },
   (
      (
         ( category | lib2_taxonomy )+
       | (
            ( lib2_model.glossLike | lib2_model.descLike )+,
            ( category | lib2_taxonomy )*
         )
      )
    | ( lib2_model.biblLike, ( category | lib2_taxonomy )* )
   )
}

1.7.2.39. <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 2: Minimal Encoding

Attributes

Attributesatt.global (xml:lang, @xml:id, @n, @xml:space) att.global.rendition (@style) 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
{
   lib2_att.global.attribute.xmlid,
   lib2_att.global.attribute.n,
   lib2_att.global.attribute.xmlspace,
   lib2_att.global.rendition.attribute.style,
   lib2_att.global.facs.attribute.facs,
   lib2_att.global.change.attribute.change,
   lib2_att.global.responsibility.attribute.cert,
   lib2_att.global.responsibility.attribute.resp,
   lib2_att.global.source.attribute.source,
   attribute xml:lang { text },
   ( lib2_fileDesc, lib2_encodingDesc, lib2_profileDesc?, lib2_revisionDesc? )
}

1.7.2.40. <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 2: Minimal Encoding

Attributes

Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (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

header: change classCode distributor edition extent language rendition seriesStmt titleStmt

namesdates: orgName persName

May contain

core: abbr address bibl biblStruct choice cit date email emph expan foreign gloss graphic label list media name pb ptr q quote ref term title

header: idno

namesdates: orgName persName

tagdocs: att gi tag val

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
{
   lib2_att.global.attributes,
   lib2_att.canonical.attributes,
   lib2_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'."""
   ],
   lib2_macro.paraContent
}

1.7.3. Schema lib2: unchanged components

abbr: (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]

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]

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.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]

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.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.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.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.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]

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

cit: (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]

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]

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]

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

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]

expan: (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions]

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]

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]

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]

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]

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]

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

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]

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.choicePart: groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. Simple Editorial Changes]

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.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.entryPart: groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure]

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.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.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.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.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]

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:

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

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]

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]

q: (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]

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]

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]

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]

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.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.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]

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]

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

when-or-before-after:

(unknown project)

TEI in Libraries level 2

Best Practices for TEI in Libraries

Level 2: Minimal Encoding

Setting

Table of contents

1. Level 2: Minimal Encoding

1.1. Reference

1.2. Purpose

1.3. Rationale

1.4. Workflow

1.5. Element Recommendations for Level 2

1.6. Level 2 Examples

1.6.1. Level 2 Basic Structure

1.6.2. Level 2 Alger Hiss document

1.7. Specification

1.7.1. Schema lib2: Added components

1.7.1.1. <p>

1.7.1.2. lib.teins

1.7.2. Schema lib2: changed components

1.7.2.1. <TEI>

1.7.2.2. <ab>

1.7.2.3. att.global

1.7.2.4. att.global.rendition

1.7.2.5. att.typed

1.7.2.6. <author>

1.7.2.7. <back>

1.7.2.8. <body>

1.7.2.9. <change>

1.7.2.10. <div>

1.7.2.11. <div1>

1.7.2.12. <editor>

1.7.2.13. <editorialDecl>

1.7.2.14. <encodingDesc>

1.7.2.15. <facsimile>

1.7.2.16. <front>

1.7.2.17. <graphic>

1.7.2.18. <head>

1.7.2.19. <hyphenation>

1.7.2.20. <idno>

1.7.2.21. model.inter

1.7.2.22. model.noteLike

1.7.2.23. <namespace>

1.7.2.24. <note>

1.7.2.25. <orgName>

1.7.2.26. <pb>

1.7.2.27. <persName>

1.7.2.28. <ptr>

1.7.2.29. <publicationStmt>

1.7.2.30. <ref>

1.7.2.31. <rendition>

1.7.2.32. <respStmt>

1.7.2.33. <schemaRef>

1.7.2.34. <sourceDesc>

1.7.2.35. <surface>

1.7.2.36. <tagUsage>

1.7.2.37. <tagsDecl>

1.7.2.38. <taxonomy>

1.7.2.39. <teiHeader>

1.7.2.40. <title>

1.7.3. Schema lib2: unchanged components