TEIWiki - User contributions [en]

Best Practices for TEI in Libraries

2009-05-06T19:27:37Z

Drsweeg: /* Appendix A: History of This Document */

----
* [http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

= TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices =

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the recommendations are as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

These recommendations are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to Level 4 in these recommendations to be trivial.

==General Recommendations==

=== Standards and local practice ===

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Filenames ===

A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters.

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, which should demark the top of a page (i.e. the text of page seven should immediately follow <tt><pb n="7"/></tt>), and should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>facs</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== rend ====

The <tt>rend</tt> attribute may be used when it is desirable to record information about how the content object was displayed in the source document.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use this attribute; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, this element should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

Difficulty using <tt>rend</tt> attributes occurs when it is desirable to record more than one rendition feature. With this in mind, projects should use the following adaptation of “rendition ladders,” a concept developed at the [http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for sets of multiple renditional features to be included in one <tt>rend</tt> value. Rendition ladders consist of categories of renditional features with values of each of those features enclosed in parentheses.

<tt>rend</tt> should only be used to override a default value. For instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>. Combining renditional features would result in an element with attributes such as <tt><l rend="slant(italics)align(right)"></tt>.
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}

==== xml:lang ====

Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4, it should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt>language</tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt>language</tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt>TEI</tt> element, containing:<ul>
<li>a <tt>teiHeader</tt> element</li>
<li>a <tt>text</tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt>teiHeader</tt> element serves as a description of the document presented in the <tt>text</tt> element. The <tt>text</tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI in the late 1980s, many people have described the TEI header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td>Record the names of other persons or organizations not covered by <tt><author></tt> and <tt><editor></tt>, one per <tt><respStmt></tt>. Each <tt><respStmt></tt> must have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>level</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. If the element has a <tt>type</tt> attribute with a value of <tt>MARC245c</tt>, its content is statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>MARC245c</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
Statement of responsibility, according to the national cataloging code. Include one <tt><respStmt></tt> for each responsible party.

Each <tt><respStmt></tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to produce content for this element, so it’s recommended to use <tt><title type="MARC245c"></tt> instead of this element.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
In this location, <tt><idno></tt> refers to identification numbers for the source document. Use <tt>type="isbn-13"</tt> and <tt>type="isbn-10"</tt> if applicable.

This element may also be used to indicate the source’s location in an individual institution’s collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <tt><idno type="LC_call_number"></tt>.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>Record encoding level for the content as an arabic numeral in the <tt>n</tt> attribute. Include one or more <tt>p</tt> elements as children with information on editorial decisions made during encoding and notes about omissions of material found in the original work. There should be a statement about the format of the data in the header. (Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?) There should also be a statement about any automated processes used to generate the markup or content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change, in ISO 8601 form (YYYY-MM-DD), should be recorded using the <tt>when</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="MARC245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images (“dirty OCR”) or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata (which page number corresponds to which image in the page sequence) collected during the imaging or preparation process. Generally speaking, this means markup is inserted at selected points into the raw OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’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.

For the most part, Level 2 texts are <i>not</i> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Front Matter=====

<p>'''<tt><div type="contents"></tt>''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt>ptr</tt> element used to reference the starting page number. The <tt>ptr</tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., an <tt>xml:id</tt> attribute) placed in the corresponding division of text.</p>

=====Body=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="bold"></tt>). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="#JHL">their manner</del> <add rend="sup" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====
Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The <tt>ref</tt> attribute should be used when pointing to web-accessible files and the <tt>key</tt> used for pointing to databases or files not generally web accessible.

For example, a web-accessible external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. The <tt>ref</tt> value in the source file references the <tt>xml:id</tt> value in the external file.
(In the examples below, the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non–web-accessible file, the <tt>key</tt> attribute points to the unique key in the database table or, as with the <tt>ref</tt> attribute, the <tt>key</tt> attribute can point to the <tt>xml:id</tt> value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in source file:
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in source file:
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* For example, the <tt>key</tt> attribute points to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:
<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

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

=====Level 4 Drama=====

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

For example,

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

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

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

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

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

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent(1)" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent(1)" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent(1)" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent(1)" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

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

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or other elements beyond a basic structural level. It is difficult to make recommendations for encoding at this level since the scholarly analysis required is usually quite specific to the project.

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging=====

<pre><lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg></pre>
Source: the Swinburne Project

=====Prosodic Analysis=====

<pre><div type="translation" xml:id="Harkins">
<head>Little House in Kolomna</head>
<epigraph xml:lang="la">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" xml:id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" xml:id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" xml:id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" xml:id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" xml:id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" xml:id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" xml:id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" xml:id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" xml:id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" xml:id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" xml:id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" xml:id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" xml:id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" xml:id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" xml:id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" xml:id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" xml:id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" xml:id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

</div></pre>
Source: William Harkins’s translation of Pushkin's “Little House in Kolomna”

=====Analytical Structures and Translation Markup=====
<pre><div type="poem">
<head>
<title rend="case(allcaps)">An Evidence</title>
</head>
<lg type="stanza">
<l rend="indent(1)">Ricardo,</l>
<l rend="indent(1)">when power is</l>
<l rend="indent(3)">rooted</l>
<l rend="indent(1)">in the land</l>
<l rend="indent(3)">
<foreign xml:lang="es">la tierra</foreign>
<note type="translation" resp="#trans" place="foot" xml:lang="en">the earth, soil</note>
</l>
<l rend="indent(1)">it is evident</l>
<l rend="indent(3)">and true.</l>
<l rend="indent(1)">Land, in some languages</l>
<l rend="indent(4)">is earth--</l>
<l rend="indent(1)">And this earth</l>
<l rend="indent(3)">(the planet...</l>
<l rend="indent(2)">all of it</l>
<l rend="indent(1)">is nurturing your powers</l>
</lg>
<signed>
<name type="personal">Lorenzo Thomas</name>
</signed>
<dateline rend="case(allcaps)">
<placeName>Amsterdam</placeName>, <placeName>The Netherlands</placeName>
<lb/><date when="1978-09-11">11 Sep 1978</date>
</dateline>
</div></pre>
Source: a poem from the Notebooks of Ricardo Sanchez

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-05-06T18:03:50Z

Drsweeg: /* Element Recommendations for the TEI Header */

----
* [http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

= TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices =

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the recommendations are as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

These recommendations are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to Level 4 in these recommendations to be trivial.

==General Recommendations==

=== Standards and local practice ===

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Filenames ===

A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters.

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, which should demark the top of a page (i.e. the text of page seven should immediately follow <tt><pb n="7"/></tt>), and should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>facs</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== rend ====

The <tt>rend</tt> attribute may be used when it is desirable to record information about how the content object was displayed in the source document.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use this attribute; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, this element should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

Difficulty using <tt>rend</tt> attributes occurs when it is desirable to record more than one rendition feature. With this in mind, projects should use the following adaptation of “rendition ladders,” a concept developed at the [http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for sets of multiple renditional features to be included in one <tt>rend</tt> value. Rendition ladders consist of categories of renditional features with values of each of those features enclosed in parentheses.

<tt>rend</tt> should only be used to override a default value. For instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>. Combining renditional features would result in an element with attributes such as <tt><l rend="slant(italics)align(right)"></tt>.
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}

==== xml:lang ====

Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4, it should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt>language</tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt>language</tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt>TEI</tt> element, containing:<ul>
<li>a <tt>teiHeader</tt> element</li>
<li>a <tt>text</tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt>teiHeader</tt> element serves as a description of the document presented in the <tt>text</tt> element. The <tt>text</tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI in the late 1980s, many people have described the TEI header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td>Record the names of other persons or organizations not covered by <tt><author></tt> and <tt><editor></tt>, one per <tt><respStmt></tt>. Each <tt><respStmt></tt> must have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>level</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. If the element has a <tt>type</tt> attribute with a value of <tt>MARC245c</tt>, its content is statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>MARC245c</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
Statement of responsibility, according to the national cataloging code. Include one <tt><respStmt></tt> for each responsible party.

Each <tt><respStmt></tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to produce content for this element, so it’s recommended to use <tt><title type="MARC245c"></tt> instead of this element.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
In this location, <tt><idno></tt> refers to identification numbers for the source document. Use <tt>type="isbn-13"</tt> and <tt>type="isbn-10"</tt> if applicable.

This element may also be used to indicate the source’s location in an individual institution’s collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <tt><idno type="LC_call_number"></tt>.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>Record encoding level for the content as an arabic numeral in the <tt>n</tt> attribute. Include one or more <tt>p</tt> elements as children with information on editorial decisions made during encoding and notes about omissions of material found in the original work. There should be a statement about the format of the data in the header. (Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?) There should also be a statement about any automated processes used to generate the markup or content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change, in ISO 8601 form (YYYY-MM-DD), should be recorded using the <tt>when</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="MARC245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images (“dirty OCR”) or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata (which page number corresponds to which image in the page sequence) collected during the imaging or preparation process. Generally speaking, this means markup is inserted at selected points into the raw OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’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.

For the most part, Level 2 texts are <i>not</i> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Front Matter=====

<p>'''<tt><div type="contents"></tt>''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt>ptr</tt> element used to reference the starting page number. The <tt>ptr</tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., an <tt>xml:id</tt> attribute) placed in the corresponding division of text.</p>

=====Body=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="bold"></tt>). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="#JHL">their manner</del> <add rend="sup" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====
Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The <tt>ref</tt> attribute should be used when pointing to web-accessible files and the <tt>key</tt> used for pointing to databases or files not generally web accessible.

For example, a web-accessible external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. The <tt>ref</tt> value in the source file references the <tt>xml:id</tt> value in the external file.
(In the examples below, the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non–web-accessible file, the <tt>key</tt> attribute points to the unique key in the database table or, as with the <tt>ref</tt> attribute, the <tt>key</tt> attribute can point to the <tt>xml:id</tt> value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in source file:
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in source file:
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* For example, the <tt>key</tt> attribute points to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:
<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

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

=====Level 4 Drama=====

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

For example,

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

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

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

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

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

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent(1)" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent(1)" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent(1)" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent(1)" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

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

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or other elements beyond a basic structural level. It is difficult to make recommendations for encoding at this level since the scholarly analysis required is usually quite specific to the project.

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging=====

<pre><lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg></pre>
Source: the Swinburne Project

=====Prosodic Analysis=====

<pre><div type="translation" xml:id="Harkins">
<head>Little House in Kolomna</head>
<epigraph xml:lang="la">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" xml:id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" xml:id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" xml:id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" xml:id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" xml:id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" xml:id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" xml:id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" xml:id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" xml:id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" xml:id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" xml:id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" xml:id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" xml:id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" xml:id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" xml:id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" xml:id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" xml:id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" xml:id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

</div></pre>
Source: William Harkins’s translation of Pushkin's “Little House in Kolomna”

=====Analytical Structures and Translation Markup=====
<pre><div type="poem">
<head>
<title rend="case(allcaps)">An Evidence</title>
</head>
<lg type="stanza">
<l rend="indent(1)">Ricardo,</l>
<l rend="indent(1)">when power is</l>
<l rend="indent(3)">rooted</l>
<l rend="indent(1)">in the land</l>
<l rend="indent(3)">
<foreign xml:lang="es">la tierra</foreign>
<note type="translation" resp="#trans" place="foot" xml:lang="en">the earth, soil</note>
</l>
<l rend="indent(1)">it is evident</l>
<l rend="indent(3)">and true.</l>
<l rend="indent(1)">Land, in some languages</l>
<l rend="indent(4)">is earth--</l>
<l rend="indent(1)">And this earth</l>
<l rend="indent(3)">(the planet...</l>
<l rend="indent(2)">all of it</l>
<l rend="indent(1)">is nurturing your powers</l>
</lg>
<signed>
<name type="personal">Lorenzo Thomas</name>
</signed>
<dateline rend="case(allcaps)">
<placeName>Amsterdam</placeName>, <placeName>The Netherlands</placeName>
<lb/><date when="1978-09-11">11 Sep 1978</date>
</dateline>
</div></pre>
Source: a poem from the Notebooks of Ricardo Sanchez

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-05-06T18:03:12Z

Drsweeg: /* General Level 4 Recommendations and Examples */

----
* [http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

= TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices =

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the recommendations are as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

These recommendations are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to Level 4 in these recommendations to be trivial.

==General Recommendations==

=== Standards and local practice ===

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Filenames ===

A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters.

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, which should demark the top of a page (i.e. the text of page seven should immediately follow <tt><pb n="7"/></tt>), and should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>facs</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== rend ====

The <tt>rend</tt> attribute may be used when it is desirable to record information about how the content object was displayed in the source document.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use this attribute; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, this element should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

Difficulty using <tt>rend</tt> attributes occurs when it is desirable to record more than one rendition feature. With this in mind, projects should use the following adaptation of “rendition ladders,” a concept developed at the [http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for sets of multiple renditional features to be included in one <tt>rend</tt> value. Rendition ladders consist of categories of renditional features with values of each of those features enclosed in parentheses.

<tt>rend</tt> should only be used to override a default value. For instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>. Combining renditional features would result in an element with attributes such as <tt><l rend="slant(italics)align(right)"></tt>.
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}

==== xml:lang ====

Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4, it should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt>language</tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt>language</tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt>TEI</tt> element, containing:<ul>
<li>a <tt>teiHeader</tt> element</li>
<li>a <tt>text</tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt>teiHeader</tt> element serves as a description of the document presented in the <tt>text</tt> element. The <tt>text</tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI in the late 1980s, many people have described the TEI header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td>Record the names of other persons or organizations not covered by <tt><author></tt> and <tt><editor></tt>, one per <tt><respStmt></tt>. Each <tt><respStmt></tt> must have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>level</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. If the element has a <tt>type</tt> attribute with a value of <tt>MARC245c</tt>, its content is statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>MARC245c</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
Statement of responsibility, according to the national cataloging code. Include one <tt><respStmt></tt> for each responsible party.

Each <tt><respStmt></tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to produce content for this element, so it’s recommended to use <tt><title type="MARC245c"></tt> instead of this element.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
In this location, <tt><idno></tt> refers to identification numbers for the source document. Use <tt>type="isbn-13"</tt> and <tt>type="isbn-10"</tt> if applicable.

This element may also be used to indicate the source’s location in an individual institution’s collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <tt><idno type="LC_call_number"></tt>.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>Record encoding level for the content as an arabic numeral in the <tt>n</tt> attribute. Include one or more <tt>p</tt> elements as children with information on editorial decisions made during encoding and notes about omissions of material found in the original work. There should be a statement about the format of the data in the header. (Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?) There should also be a statement about any automated processes used to generate the markup or content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change, in ISO 8601 form (YYYY-MM-DD), should be recorded using the <tt>when</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="MARC245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images (“dirty OCR”) or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata (which page number corresponds to which image in the page sequence) collected during the imaging or preparation process. Generally speaking, this means markup is inserted at selected points into the raw OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’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.

For the most part, Level 2 texts are <i>not</i> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Front Matter=====

<p>'''<tt><div type="contents"></tt>''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt>ptr</tt> element used to reference the starting page number. The <tt>ptr</tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., an <tt>xml:id</tt> attribute) placed in the corresponding division of text.</p>

=====Body=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="bold"></tt>). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="#JHL">their manner</del> <add rend="sup" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====
Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The <tt>ref</tt> attribute should be used when pointing to web-accessible files and the <tt>key</tt> used for pointing to databases or files not generally web accessible.

For example, a web-accessible external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. The <tt>ref</tt> value in the source file references the <tt>xml:id</tt> value in the external file.
(In the examples below, the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non–web-accessible file, the <tt>key</tt> attribute points to the unique key in the database table or, as with the <tt>ref</tt> attribute, the <tt>key</tt> attribute can point to the <tt>xml:id</tt> value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in source file:
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in source file:
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* For example, the <tt>key</tt> attribute points to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:
<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

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

=====Level 4 Drama=====

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

For example,

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

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

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

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

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

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent(1)" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent(1)" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent(1)" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent(1)" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

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

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or other elements beyond a basic structural level. It is difficult to make recommendations for encoding at this level since the scholarly analysis required is usually quite specific to the project.

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging=====

<pre><lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg></pre>
Source: the Swinburne Project

=====Prosodic Analysis=====

<pre><div type="translation" xml:id="Harkins">
<head>Little House in Kolomna</head>
<epigraph xml:lang="la">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" xml:id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" xml:id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" xml:id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" xml:id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" xml:id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" xml:id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" xml:id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" xml:id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" xml:id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" xml:id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" xml:id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" xml:id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" xml:id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" xml:id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" xml:id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" xml:id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" xml:id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" xml:id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

</div></pre>
Source: William Harkins’s translation of Pushkin's “Little House in Kolomna”

=====Analytical Structures and Translation Markup=====
<pre><div type="poem">
<head>
<title rend="case(allcaps)">An Evidence</title>
</head>
<lg type="stanza">
<l rend="indent(1)">Ricardo,</l>
<l rend="indent(1)">when power is</l>
<l rend="indent(3)">rooted</l>
<l rend="indent(1)">in the land</l>
<l rend="indent(3)">
<foreign xml:lang="es">la tierra</foreign>
<note type="translation" resp="#trans" place="foot" xml:lang="en">the earth, soil</note>
</l>
<l rend="indent(1)">it is evident</l>
<l rend="indent(3)">and true.</l>
<l rend="indent(1)">Land, in some languages</l>
<l rend="indent(4)">is earth--</l>
<l rend="indent(1)">And this earth</l>
<l rend="indent(3)">(the planet...</l>
<l rend="indent(2)">all of it</l>
<l rend="indent(1)">is nurturing your powers</l>
</lg>
<signed>
<name type="personal">Lorenzo Thomas</name>
</signed>
<dateline rend="case(allcaps)">
<placeName>Amsterdam</placeName>, <placeName>The Netherlands</placeName>
<lb/><date when="1978-09-11">11 Sep 1978</date>
</dateline>
</div></pre>
Source: a poem from the Notebooks of Ricardo Sanchez

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-05-06T18:02:15Z

Drsweeg: /* General Level 4 Recommendations and Examples */

----
* [http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

= TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices =

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the recommendations are as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

These recommendations are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to Level 4 in these recommendations to be trivial.

==General Recommendations==

=== Standards and local practice ===

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Filenames ===

A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters.

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, which should demark the top of a page (i.e. the text of page seven should immediately follow <tt><pb n="7"/></tt>), and should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>facs</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== rend ====

The <tt>rend</tt> attribute may be used when it is desirable to record information about how the content object was displayed in the source document.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use this attribute; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, this element should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

Difficulty using <tt>rend</tt> attributes occurs when it is desirable to record more than one rendition feature. With this in mind, projects should use the following adaptation of “rendition ladders,” a concept developed at the [http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for sets of multiple renditional features to be included in one <tt>rend</tt> value. Rendition ladders consist of categories of renditional features with values of each of those features enclosed in parentheses.

<tt>rend</tt> should only be used to override a default value. For instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>. Combining renditional features would result in an element with attributes such as <tt><l rend="slant(italics)align(right)"></tt>.
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}

==== xml:lang ====

Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4, it should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt>language</tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt>language</tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt>TEI</tt> element, containing:<ul>
<li>a <tt>teiHeader</tt> element</li>
<li>a <tt>text</tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt>teiHeader</tt> element serves as a description of the document presented in the <tt>text</tt> element. The <tt>text</tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI in the late 1980s, many people have described the TEI header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td>Record the names of other persons or organizations not covered by <tt><author></tt> and <tt><editor></tt>, one per <tt><respStmt></tt>. Each <tt><respStmt></tt> must have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>level</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. If the element has a <tt>type</tt> attribute with a value of <tt>MARC245c</tt>, its content is statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>MARC245c</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
Statement of responsibility, according to the national cataloging code. Include one <tt><respStmt></tt> for each responsible party.

Each <tt><respStmt></tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to produce content for this element, so it’s recommended to use <tt><title type="MARC245c"></tt> instead of this element.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
In this location, <tt><idno></tt> refers to identification numbers for the source document. Use <tt>type="isbn-13"</tt> and <tt>type="isbn-10"</tt> if applicable.

This element may also be used to indicate the source’s location in an individual institution’s collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <tt><idno type="LC_call_number"></tt>.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>Record encoding level for the content as an arabic numeral in the <tt>n</tt> attribute. Include one or more <tt>p</tt> elements as children with information on editorial decisions made during encoding and notes about omissions of material found in the original work. There should be a statement about the format of the data in the header. (Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?) There should also be a statement about any automated processes used to generate the markup or content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change, in ISO 8601 form (YYYY-MM-DD), should be recorded using the <tt>when</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="MARC245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images (“dirty OCR”) or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata (which page number corresponds to which image in the page sequence) collected during the imaging or preparation process. Generally speaking, this means markup is inserted at selected points into the raw OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’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.

For the most part, Level 2 texts are <i>not</i> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Front Matter=====

<p>'''<tt><div type="contents"></tt>''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt>ptr</tt> element used to reference the starting page number. The <tt>ptr</tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., an <tt>xml:id</tt> attribute) placed in the corresponding division of text.</p>

=====Body=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="bold"></tt>). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="#JHL">their manner</del> <add rend="sup" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====
Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The <tt>ref</tt> attribute should be used when pointing to web-accessible files and the <tt>key</tt> used for pointing to databases or files not generally web accessible.

For example, a web-accessible external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. The <tt>ref</tt> value in the source file references the <tt>xml:id</tt> value in the external file.
(In the examples below, the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non–web-accessible file, the <tt>key</tt> attribute points to the unique key in the database table or, as with the <tt>ref</tt> attribute, the <tt>key</tt> attribute can point to the <tt>xml:id</tt> value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in source file:
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in source file:
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* For example, the <tt>key</tt> attribute points to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:
<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

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

=====Level 4 Drama=====

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

For example,

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

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

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

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

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

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent(1)" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent(1)" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent(1)" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent(1)" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

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

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or other elements beyond a basic structural level. It is difficult to make recommendations for encoding at this level since the scholarly analysis required is usually quite specific to the project.

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging=====

<pre><lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg></pre>
Source: the Swinburne Project

=====Prosodic Analysis=====

<pre><div type="translation" xml:id="Harkins">
<head>Little House in Kolomna</head>
<epigraph xml:lang="la">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" xml:id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" xml:id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" xml:id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" xml:id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" xml:id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" xml:id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" xml:id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" xml:id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" xml:id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" xml:id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" xml:id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" xml:id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" xml:id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" xml:id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" xml:id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" xml:id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" xml:id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" xml:id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

</div></pre>
Source: William Harkins’s translation of Pushkin's “Little House in Kolomna”

=====Analytical Structures and Translation Markup=====
<pre><div type="poem">
<head>
<title rend="case(allcaps)">An Evidence</title>
</head>
<lg type="stanza">
<l rend="indent(1)">Ricardo,</l>
<l rend="indent(1)">when power is</l>
<l rend="indent(3)">rooted</l>
<l rend="indent(1)">in the land</l>
<l rend="indent(3)">
<foreign xml:lang="es">la tierra</foreign>
<note type="translation" resp="#trans" place="foot" xml:lang="en">the earth, soil</note>
</l>
<l rend="indent(1)">it is evident</l>
<l rend="indent(3)">and true.</l>
<l rend="indent(1)">Land, in some languages</l>
<l rend="indent(4)">is earth--</l>
<l rend="indent(1)">And this earth</l>
<l rend="indent(3)">(the planet...</l>
<l rend="indent(2)">all of it</l>
<l rend="indent(1)">is nurturing your powers</l>
</lg>
<signed>
<name type="personal">Lorenzo Thomas</name>
</signed>
<dateline rend="case(allcaps)">
<placeName>Amsterdam</placeName>, <placeName>The Netherlands</placeName>
<lb/><date when="1978-09-11">11 Sep 1978</date>
</dateline>
</div></pre>
Source: a poem from the Notebooks of Ricardo Sanchez

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-05-06T18:01:13Z

Drsweeg: /* Sample TEI Header */

----
* [http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

= TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices =

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the recommendations are as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

These recommendations are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to Level 4 in these recommendations to be trivial.

==General Recommendations==

=== Standards and local practice ===

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Filenames ===

A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters.

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, which should demark the top of a page (i.e. the text of page seven should immediately follow <tt><pb n="7"/></tt>), and should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>facs</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== rend ====

The <tt>rend</tt> attribute may be used when it is desirable to record information about how the content object was displayed in the source document.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use this attribute; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, this element should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

Difficulty using <tt>rend</tt> attributes occurs when it is desirable to record more than one rendition feature. With this in mind, projects should use the following adaptation of “rendition ladders,” a concept developed at the [http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for sets of multiple renditional features to be included in one <tt>rend</tt> value. Rendition ladders consist of categories of renditional features with values of each of those features enclosed in parentheses.

<tt>rend</tt> should only be used to override a default value. For instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>. Combining renditional features would result in an element with attributes such as <tt><l rend="slant(italics)align(right)"></tt>.
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}

==== xml:lang ====

Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4, it should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt>language</tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt>language</tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt>TEI</tt> element, containing:<ul>
<li>a <tt>teiHeader</tt> element</li>
<li>a <tt>text</tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt>teiHeader</tt> element serves as a description of the document presented in the <tt>text</tt> element. The <tt>text</tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI in the late 1980s, many people have described the TEI header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td>Record the names of other persons or organizations not covered by <tt><author></tt> and <tt><editor></tt>, one per <tt><respStmt></tt>. Each <tt><respStmt></tt> must have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>level</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. If the element has a <tt>type</tt> attribute with a value of <tt>MARC245c</tt>, its content is statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>MARC245c</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
Statement of responsibility, according to the national cataloging code. Include one <tt><respStmt></tt> for each responsible party.

Each <tt><respStmt></tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt><persName></tt> or <tt><orgName></tt> as children of <tt><name></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to produce content for this element, so it’s recommended to use <tt><title type="MARC245c"></tt> instead of this element.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
In this location, <tt><idno></tt> refers to identification numbers for the source document. Use <tt>type="isbn-13"</tt> and <tt>type="isbn-10"</tt> if applicable.

This element may also be used to indicate the source’s location in an individual institution’s collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <tt><idno type="LC_call_number"></tt>.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>Record encoding level for the content as an arabic numeral in the <tt>n</tt> attribute. Include one or more <tt>p</tt> elements as children with information on editorial decisions made during encoding and notes about omissions of material found in the original work. There should be a statement about the format of the data in the header. (Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?) There should also be a statement about any automated processes used to generate the markup or content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change, in ISO 8601 form (YYYY-MM-DD), should be recorded using the <tt>when</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="MARC245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images (“dirty OCR”) or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata (which page number corresponds to which image in the page sequence) collected during the imaging or preparation process. Generally speaking, this means markup is inserted at selected points into the raw OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’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.

For the most part, Level 2 texts are <i>not</i> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Front Matter=====

<p>'''<tt><div type="contents"></tt>''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt>ptr</tt> element used to reference the starting page number. The <tt>ptr</tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., an <tt>xml:id</tt> attribute) placed in the corresponding division of text.</p>

=====Body=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader>

</teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>

</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="bold"></tt>). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="#JHL">their manner</del> <add rend="sup" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====
Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The <tt>ref</tt> attribute should be used when pointing to web-accessible files and the <tt>key</tt> used for pointing to databases or files not generally web accessible.

For example, a web-accessible external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. The <tt>ref</tt> value in the source file references the <tt>xml:id</tt> value in the external file.
(In the examples below, the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non–web-accessible file, the <tt>key</tt> attribute points to the unique key in the database table or, as with the <tt>ref</tt> attribute, the <tt>key</tt> attribute can point to the <tt>xml:id</tt> value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in source file:
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in source file:
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* For example, the <tt>key</tt> attribute points to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:
<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

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

=====Level 4 Drama=====

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

For example,

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

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

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

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

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

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent(1)" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent(1)" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent(1)" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent(1)" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

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

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or other elements beyond a basic structural level. It is difficult to make recommendations for encoding at this level since the scholarly analysis required is usually quite specific to the project.

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging=====

<pre><lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg></pre>
Source: the Swinburne Project

=====Prosodic Analysis=====

<pre><div type="translation" xml:id="Harkins">
<head>Little House in Kolomna</head>
<epigraph xml:lang="la">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" xml:id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" xml:id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" xml:id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" xml:id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" xml:id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" xml:id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" xml:id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" xml:id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" xml:id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" xml:id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" xml:id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" xml:id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" xml:id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" xml:id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" xml:id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" xml:id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" xml:id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" xml:id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

</div></pre>
Source: William Harkins’s translation of Pushkin's “Little House in Kolomna”

=====Analytical Structures and Translation Markup=====
<pre><div type="poem">
<head>
<title rend="case(allcaps)">An Evidence</title>
</head>
<lg type="stanza">
<l rend="indent(1)">Ricardo,</l>
<l rend="indent(1)">when power is</l>
<l rend="indent(3)">rooted</l>
<l rend="indent(1)">in the land</l>
<l rend="indent(3)">
<foreign xml:lang="es">la tierra</foreign>
<note type="translation" resp="#trans" place="foot" xml:lang="en">the earth, soil</note>
</l>
<l rend="indent(1)">it is evident</l>
<l rend="indent(3)">and true.</l>
<l rend="indent(1)">Land, in some languages</l>
<l rend="indent(4)">is earth--</l>
<l rend="indent(1)">And this earth</l>
<l rend="indent(3)">(the planet...</l>
<l rend="indent(2)">all of it</l>
<l rend="indent(1)">is nurturing your powers</l>
</lg>
<signed>
<name type="personal">Lorenzo Thomas</name>
</signed>
<dateline rend="case(allcaps)">
<placeName>Amsterdam</placeName>, <placeName>The Netherlands</placeName>
<lb/><date when="1978-09-11">11 Sep 1978</date>
</dateline>
</div></pre>
Source: a poem from the Notebooks of Ricardo Sanchez

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T18:09:00Z

Drsweeg: /* Level 4 Drama */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially for older materials. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader type="text">[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</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 <pb> 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> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, page numbers and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>


<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <head> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T18:07:37Z

Drsweeg: /* Level 4 Figures */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially for older materials. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, page numbers and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>


<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <head> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T18:05:38Z

Drsweeg: /* Level 4 Verse */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, page numbers and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>


<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="indent" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="indent" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="indent" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

User:Drsweeg

2009-04-14T18:01:39Z

Drsweeg: New page: Drsweeg = Matthew Gibson Virginia Foundation for the Humanities University of Virginia

Drsweeg = Matthew Gibson
Virginia Foundation for the Humanities
University of Virginia

BPG Feedback on Complete Draft

2009-04-14T18:01:08Z

Drsweeg: /* Level 4 Drama */

[http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices Back to GBP]

The main sections of the BPG are outlined below to facilitate orderly feedback :-). '''Please provide feedback by Saturday, April 11th''' so Kevin and I have enough time to compile any of the more significant issues for discussion during our upcoming meeting on April 14th.

Add each new comment as a bullet point and be sure to attribute comments so we know how to follow-up if there's some debate. For example:

* feedback blah blah, [[User:Mdalmau|Mdalmau]]

==Introduction==
* Task Force w/c though historically correct may lose context in this new revision. Consider something more generic like "Working Group" or past tense: "the Task Force attempted to make these ..." [[User:Mdalmau|Mdalmau]]

==General Recommendations==
* Conisder moving facsimile page image info here as the final bullet point. [[User:Mdalmau|Mdalmau]]

==Structure of a TEI Document==

* Do we need to reference <tt><facsimile></tt>? [[User:Mdalmau|Mdalmau]]

==The TEI Header==

* I changed 'the Open Access Initiative (OAI)" to "the Open Archives Initiative (OAI)". Unless there is another initiative that I do not know about.[[User:Natasha|Natasha]]

* encodingDesc: Even though Melanie and I wrote most of the header, I don't remember any more why some information about sourceDesc is in encodingDesc/p and other info is in encodingDesc/editorialDecl/p . Seems like this info should be in one place or the other. Suggestions? Note that the P5 schema allows both p and non-p children of encodingDesc, but the prose implies that this isn't allowed. I've reported to SourceForge ( https://sourceforge.net/tracker/?func=detail&atid=644062&aid=2761884&group_id=106328 ), but maybe we should do it one way or the other. All the more reason to fix this.

* How to allow for automatic generation of sourceDesc from a MARC record yet not commit tag abuse on author and respStmt elements.

==Linking between encoded text and images of source documents==
* Consider moving this text up under the General Rec. section. [[User:Mdalmau|Mdalmau]]
* Do we need to say this: "The examples below use the former method." And do we want all examples to use @facs? I think we should mix it up since we are recommending both options. [[User:Mdalmau|Mdalmau]]
** Kevin suggested that we need more info for how to use xml:id with METS. I am not quite sure how to do this at-a-glance and any attempt at detail will lead us into a significant discussion about METS. Here are some things we can say, but may not all of them (and hopefully Chris P. can provide some guidance):
*** Use xml:id to locate content but not explicit representation of content (xml:id points to MET document, not images)
*** fileSec used to explicitly list all the images (master, jpg, pdf)
*** structMap orders the pages by page break and references each image defined in fileSec [[User:Mdalmau|Mdalmau]]

==LEVEL 1: Fully Automated Conversion and Encoding==

* Should an automated workflow be described? ([[User:Kshawkin|Kshawkin]])

==LEVEL 2: Minimal Encoding==

* Should an automated workflow be described? How does everyone feel about the one Kevin described by email on 2009-04-08? ([[User:Kshawkin|Kshawkin]])

Second paragraph of rationale: why "earlier than 1900"? Restate to explain what it is about certain older source documents that makes it difficult to use automated methods on them.

I think the last paragraph of "Rationale" in essence repeats what has been stated in the first para.
Suggestions - combine them and edit to avoid repetition. [[User:Natasha|Natasha]]

Consider revision? "Level 2 texts do not require any special knowledge or manual intervention below the section level." [[User:Natasha|Natasha]]

In "Linking between encoded text and images of source documents", we say that "The examples below use the former method", i.e. "Use the @facs attribute on each <pb> element to point to the corresponding page image using a URI." Indeed that's what we use in the Level 1 example:
<pb n="114" facs="00000002.tif"/>

However, here is the level 2 example:
<pb xml:id="p21198-zz0002mpqr" n="1"/>
[[User:Natasha|Natasha]]

maybe to keep one - Alger Hiss document - example?[[User:Natasha|Natasha]]

==LEVEL 3: Simple Analysis==

=== General Level 3 Recommendations ===
* need to check for consistency: sometimes it's <tt>pb</tt>, sometimes it's <tt><pb></tt> [[User:Natasha|Natasha]]

* sorry, but what does "Forme Works" mean? [[User:Natasha|Natasha]]

* Need to explain more about how to encode end-of-division notes. They need an n= attribute, but they also need a <tt>ptr</tt> in the text.
** Do we handle with: <ref target="#note01">1</ref> that points to end of division [1] <note xml:id="note01">blah</note>?
** Do we need to support bi-directional linking: <ref target="#note01" xml:id="ref01">1</ref> and <note xml:id="note01"><ref target="#ref01">[1]</ref>blah</note>? [[User:Mdalmau|Mdalmau]]
* Use of the "n" attribute for <l> should be optional. Remove from example? Or add optional "n" usage to the table? [[User:Mdalmau|Mdalmau]] (reported by Rich)

* Check: "Add the "target" attribute (@target) to reference the <pb> identifier to generate links from the index into the text proper." And in general the consistency with how we list attributes, i.e. "target" attribute or target= attribute; or @target, etc. [[User:Natasha|Natasha]]

** I revised this to make it somewhat clearer, but I think it should be rewritten and an example (even a fake one) included. It would be good to give guidance on what to do with things like page ranges in an index and errors in the index. ([[User:Kshawkin|Kshawkin]])

=== Level 3 Examples ===
==== Basic Structure: Verse ====
I am afraid that our examples for level 3 and level 4 verse are not that different. Level 3 verse has n= attribute for <l> element, while level 4 verse does not. Thoughts? [[User:Natasha|Natasha]]

==LEVEL 4: Basic Content Analysis==
* <strike>For name tagging, recommend the use of @ref when the target is web accessible and @key when not.</strike> [[User:Mdalmau|Mdalmau]]
* <strike>Matt has provided an @key example; some possible debate about where the explanation appears in the Header</strike> [[User:Mdalmau|Mdalmau]]
* Moved Name Tagging recommendations from bullet point under General Recommendations to its own section. The explanation and examples are too dense for a bullet point. We may need to find a better place for this. [[User:Mdalmau|Mdalmau]]

=== Level 4 Letters ===

* This text conflates personal letters (epistles) with situations where one text is embedded within another. These topics should be dealt with separately since there are encoding projects that encode personal correspondence only (where letters are not embedded within other texts), and there are cases of non-epistles included within frame texts. ([[User:Kshawkin|Kshawkin]])
** I see your point, Kevin. I will try to find a more clear-cut example, but, honestly, I would stay with the one we have :-) [[User:Natasha|Natasha]]

=== Level 4 Drama ===

* It says, "Stage directions are encoded as <stage> and enclose block level content describing scenery, etc." This is unclear: should block-level content describing the scenery etc. be "enclosed" in <stage> tags?

** I just changed this to read: "Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc." However, this may miss the point that Kevin indicated above, that basically elements such as <p> are allowed inside of <stage> ([[User:Drsweeg|Drsweeg]])

=== Level 4 Verse ===

* <l rend="">: Matt added a note in the GBP, which I've moved here: "note: I really don't think we want to keep something like this in here; what do others recommend as far as methods for encoding typographically explicit verse breaks, etc.?"

** Also, what sorts of values should be used on rend=? ([[User:Kshawkin|Kshawkin]])

==LEVEL 5: Scholarly Encoding Projects==

* Need examples. Syd was going to make scholarly the level 4 examples. Any updates? [[User:Mdalmau|Mdalmau]]
Syd, what do you think about my comments re your WWP example? It can be considered level 5. [[User:Natasha|Natasha]]

* I've added two verse examples, neither of which inspires much confidence. I wouldn't be hurt if someone were to replace these with other better (e.g. WWP) examples. [[User:Gworthey|Gworthey]]

==General Guidelines for Attribute Usage==

* It says, "For instance, if all text is encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>" . We need to say where this would be defined, and by whom. But we should also discuss the question of normalization in rendering. If a project wants to encode all monograph titles as italics regardless of how they were displayed in the source document, then there's no need to use rend=. But if the project wants to transcribe the source document faithfully, including all inconsistencies, then rend= should always be used. ([[User:Kshawkin|Kshawkin]])

==Acknowledgements==

==Appendix A: History of this Document==

* Why aren't we using the new rendition feature in P5? [[User:Mdalmau|Mdalmau]]

[[Category:SIG:Libraries]]

BPG Feedback on Complete Draft

2009-04-14T17:56:50Z

Drsweeg: /* Level 4 Drama */

[http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices Back to GBP]

The main sections of the BPG are outlined below to facilitate orderly feedback :-). '''Please provide feedback by Saturday, April 11th''' so Kevin and I have enough time to compile any of the more significant issues for discussion during our upcoming meeting on April 14th.

Add each new comment as a bullet point and be sure to attribute comments so we know how to follow-up if there's some debate. For example:

* feedback blah blah, [[User:Mdalmau|Mdalmau]]

==Introduction==
* Task Force w/c though historically correct may lose context in this new revision. Consider something more generic like "Working Group" or past tense: "the Task Force attempted to make these ..." [[User:Mdalmau|Mdalmau]]

==General Recommendations==
* Conisder moving facsimile page image info here as the final bullet point. [[User:Mdalmau|Mdalmau]]

==Structure of a TEI Document==

* Do we need to reference <tt><facsimile></tt>? [[User:Mdalmau|Mdalmau]]

==The TEI Header==

* I changed 'the Open Access Initiative (OAI)" to "the Open Archives Initiative (OAI)". Unless there is another initiative that I do not know about.[[User:Natasha|Natasha]]

* encodingDesc: Even though Melanie and I wrote most of the header, I don't remember any more why some information about sourceDesc is in encodingDesc/p and other info is in encodingDesc/editorialDecl/p . Seems like this info should be in one place or the other. Suggestions? Note that the P5 schema allows both p and non-p children of encodingDesc, but the prose implies that this isn't allowed. I've reported to SourceForge ( https://sourceforge.net/tracker/?func=detail&atid=644062&aid=2761884&group_id=106328 ), but maybe we should do it one way or the other. All the more reason to fix this.

* How to allow for automatic generation of sourceDesc from a MARC record yet not commit tag abuse on author and respStmt elements.

==Linking between encoded text and images of source documents==
* Consider moving this text up under the General Rec. section. [[User:Mdalmau|Mdalmau]]
* Do we need to say this: "The examples below use the former method." And do we want all examples to use @facs? I think we should mix it up since we are recommending both options. [[User:Mdalmau|Mdalmau]]
** Kevin suggested that we need more info for how to use xml:id with METS. I am not quite sure how to do this at-a-glance and any attempt at detail will lead us into a significant discussion about METS. Here are some things we can say, but may not all of them (and hopefully Chris P. can provide some guidance):
*** Use xml:id to locate content but not explicit representation of content (xml:id points to MET document, not images)
*** fileSec used to explicitly list all the images (master, jpg, pdf)
*** structMap orders the pages by page break and references each image defined in fileSec [[User:Mdalmau|Mdalmau]]

==LEVEL 1: Fully Automated Conversion and Encoding==

* Should an automated workflow be described? ([[User:Kshawkin|Kshawkin]])

==LEVEL 2: Minimal Encoding==

* Should an automated workflow be described? How does everyone feel about the one Kevin described by email on 2009-04-08? ([[User:Kshawkin|Kshawkin]])

Second paragraph of rationale: why "earlier than 1900"? Restate to explain what it is about certain older source documents that makes it difficult to use automated methods on them.

I think the last paragraph of "Rationale" in essence repeats what has been stated in the first para.
Suggestions - combine them and edit to avoid repetition. [[User:Natasha|Natasha]]

Consider revision? "Level 2 texts do not require any special knowledge or manual intervention below the section level." [[User:Natasha|Natasha]]

In "Linking between encoded text and images of source documents", we say that "The examples below use the former method", i.e. "Use the @facs attribute on each <pb> element to point to the corresponding page image using a URI." Indeed that's what we use in the Level 1 example:
<pb n="114" facs="00000002.tif"/>

However, here is the level 2 example:
<pb xml:id="p21198-zz0002mpqr" n="1"/>
[[User:Natasha|Natasha]]

maybe to keep one - Alger Hiss document - example?[[User:Natasha|Natasha]]

==LEVEL 3: Simple Analysis==

=== General Level 3 Recommendations ===
* need to check for consistency: sometimes it's <tt>pb</tt>, sometimes it's <tt><pb></tt> [[User:Natasha|Natasha]]

* sorry, but what does "Forme Works" mean? [[User:Natasha|Natasha]]

* Need to explain more about how to encode end-of-division notes. They need an n= attribute, but they also need a <tt>ptr</tt> in the text.
** Do we handle with: <ref target="#note01">1</ref> that points to end of division [1] <note xml:id="note01">blah</note>?
** Do we need to support bi-directional linking: <ref target="#note01" xml:id="ref01">1</ref> and <note xml:id="note01"><ref target="#ref01">[1]</ref>blah</note>? [[User:Mdalmau|Mdalmau]]
* Use of the "n" attribute for <l> should be optional. Remove from example? Or add optional "n" usage to the table? [[User:Mdalmau|Mdalmau]] (reported by Rich)

* Check: "Add the "target" attribute (@target) to reference the <pb> identifier to generate links from the index into the text proper." And in general the consistency with how we list attributes, i.e. "target" attribute or target= attribute; or @target, etc. [[User:Natasha|Natasha]]

** I revised this to make it somewhat clearer, but I think it should be rewritten and an example (even a fake one) included. It would be good to give guidance on what to do with things like page ranges in an index and errors in the index. ([[User:Kshawkin|Kshawkin]])

=== Level 3 Examples ===
==== Basic Structure: Verse ====
I am afraid that our examples for level 3 and level 4 verse are not that different. Level 3 verse has n= attribute for <l> element, while level 4 verse does not. Thoughts? [[User:Natasha|Natasha]]

==LEVEL 4: Basic Content Analysis==
* <strike>For name tagging, recommend the use of @ref when the target is web accessible and @key when not.</strike> [[User:Mdalmau|Mdalmau]]
* <strike>Matt has provided an @key example; some possible debate about where the explanation appears in the Header</strike> [[User:Mdalmau|Mdalmau]]
* Moved Name Tagging recommendations from bullet point under General Recommendations to its own section. The explanation and examples are too dense for a bullet point. We may need to find a better place for this. [[User:Mdalmau|Mdalmau]]

=== Level 4 Letters ===

* This text conflates personal letters (epistles) with situations where one text is embedded within another. These topics should be dealt with separately since there are encoding projects that encode personal correspondence only (where letters are not embedded within other texts), and there are cases of non-epistles included within frame texts. ([[User:Kshawkin|Kshawkin]])
** I see your point, Kevin. I will try to find a more clear-cut example, but, honestly, I would stay with the one we have :-) [[User:Natasha|Natasha]]

=== Level 4 Drama ===

* It says, "Stage directions are encoded as <stage> and enclose block level content describing scenery, etc." This is unclear: should block-level content describing the scenery etc. be "enclosed" in <stage> tags?

** I just changed this to read: "Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc." However, this may miss the point that Kevin indicated above, that basically elements such as <p> are allowed inside of <stage>

=== Level 4 Verse ===

* <l rend="">: Matt added a note in the GBP, which I've moved here: "note: I really don't think we want to keep something like this in here; what do others recommend as far as methods for encoding typographically explicit verse breaks, etc.?"

** Also, what sorts of values should be used on rend=? ([[User:Kshawkin|Kshawkin]])

==LEVEL 5: Scholarly Encoding Projects==

* Need examples. Syd was going to make scholarly the level 4 examples. Any updates? [[User:Mdalmau|Mdalmau]]
Syd, what do you think about my comments re your WWP example? It can be considered level 5. [[User:Natasha|Natasha]]

* I've added two verse examples, neither of which inspires much confidence. I wouldn't be hurt if someone were to replace these with other better (e.g. WWP) examples. [[User:Gworthey|Gworthey]]

==General Guidelines for Attribute Usage==

* It says, "For instance, if all text is encoded as <tt><hi></tt> is defined as being rendered in italics, there is no reason to encode text as <tt><hi rend="slant(italics)"></tt>" . We need to say where this would be defined, and by whom. But we should also discuss the question of normalization in rendering. If a project wants to encode all monograph titles as italics regardless of how they were displayed in the source document, then there's no need to use rend=. But if the project wants to transcribe the source document faithfully, including all inconsistencies, then rend= should always be used. ([[User:Kshawkin|Kshawkin]])

==Acknowledgements==

==Appendix A: History of this Document==

* Why aren't we using the new rendition feature in P5? [[User:Mdalmau|Mdalmau]]

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T17:54:25Z

Drsweeg: /* Reference */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, page numbers and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>


<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza">
<l>"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent">As he landed his crew with care;</l>
<l>Supporting each man on the top of the tide</l>
<l rend="indent">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza">
<l>"Just the place for a Snark! I have said it twice:</l>
<l rend="indent">That alone should encourage the crew.</l>
<l>Just the place for a Snark! I have said it thrice:</l>
<l rend="indent">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T17:30:51Z

Drsweeg: /* Level 4 Name Tagging */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, and other such forme work information should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l n="1">O the days gone by! O the days gone by!</l>
<l n="2">The apples in the orchard, and the pathway through the rye;</l>
<l n="3">The chirrup of the robin, and the whistle of the quail</l>
<l n="4">As he piped across the meadows sweet as any nightingale;</l>
<l n="5">When the bloom was on the clover, and the blue was in the sky,</l>
<l n="6">And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>


<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza">
<l>"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent">As he landed his crew with care;</l>
<l>Supporting each man on the top of the tide</l>
<l rend="indent">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza">
<l>"Just the place for a Snark! I have said it twice:</l>
<l rend="indent">That alone should encourage the crew.</l>
<l>Just the place for a Snark! I have said it thrice:</l>
<l rend="indent">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T17:25:16Z

Drsweeg: /* Level 4 Drama */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, and other such forme work information should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l n="1">O the days gone by! O the days gone by!</l>
<l n="2">The apples in the orchard, and the pathway through the rye;</l>
<l n="3">The chirrup of the robin, and the whistle of the quail</l>
<l n="4">As he piped across the meadows sweet as any nightingale;</l>
<l n="5">When the bloom was on the clover, and the blue was in the sky,</l>
<l n="6">And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>

<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza">
<l>"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent">As he landed his crew with care;</l>
<l>Supporting each man on the top of the tide</l>
<l rend="indent">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza">
<l>"Just the place for a Snark! I have said it twice:</l>
<l rend="indent">That alone should encourage the crew.</l>
<l>Just the place for a Snark! I have said it thrice:</l>
<l rend="indent">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth, soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T17:03:12Z

Drsweeg: /* Level 4 Figures */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, and other such forme work information should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l n="1">O the days gone by! O the days gone by!</l>
<l n="2">The apples in the orchard, and the pathway through the rye;</l>
<l n="3">The chirrup of the robin, and the whistle of the quail</l>
<l n="4">As he piped across the meadows sweet as any nightingale;</l>
<l n="5">When the bloom was on the clover, and the blue was in the sky,</l>
<l n="6">And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>

<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose block level content describing scenery, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza">
<l>"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent">As he landed his crew with care;</l>
<l>Supporting each man on the top of the tide</l>
<l rend="indent">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza">
<l>"Just the place for a Snark! I have said it twice:</l>
<l rend="indent">That alone should encourage the crew.</l>
<l>Just the place for a Snark! I have said it thrice:</l>
<l rend="indent">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth,
soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-04-14T17:02:46Z

Drsweeg: /* Level 4 Figures */

[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]

----
* [[BPG Feedback on Complete Draft]] (required, polishing before release for public comment)
* [[Copyediting Feedback]] (optional, helpful pointers to our copy editor)
----

==Introduction==

These recommendations are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, the Task Force has attempted to make these recommendations as inclusive as possible by developing a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing.

Recommendations for Levels 1-4 are intended for projects wishing to create encoded electronic text with structural markup, but minimal semantic or content markup. Also, the encoding levels are cumulative: encoding requirements at each level incorporate the requirements of lower levels. Levels 1-4 allow the conversion and encoding of texts to be performed without the assistance of deep content knowledge and can be enriched with more markup at any time. Level 5, in contrast, requires scholarly analysis.

==General Recommendations==

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

<ul>
<li>When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on
the first leaf of the original work. It may be impractical or undesirable to transcribe and encode
certain features of the text, such as publisher's advertisements or indexes, but if at all possible,
they should be included as links to page images. Any omissions of material found in the original work
should be noted in the <editorialDecl> in the TEI header.</li>

<li>A filename scheme that is internally consistent should be established for the project. If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. </li>

<li>An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of divs starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.</li>

<li>Whether numbered or unnumbered divisions are used, the <tt>@type</tt> attribute of the division element is not recommended at level 1, is optional at level 2, is recommended at level 3, and required at levels 4 and 5.</li>

<li>Page breaks should be encoded using the <tt><pb></tt> element,
which should demark the top of a page (i.e. the text of page
seven should immediately follow <tt><pb n="7"/></tt>), and should
always be contained within a div for ease of retrieval with indexing software. For example, a page break that
occurs between chapters 2 and 3 should be encoded near the top
of the <tt><div></tt> that holds chapter 3 (rather than near the bottom
of the <tt><div></tt> that holds chapter 2).
</li>
</ul>

==Structure of a TEI Document==

A valid TEI XML document must contain the following elements:
<ul><li>a root <tt><TEI></tt> element, containing:<ul>
<li>a <tt><teiHeader></tt> element</li>
<li>a <tt><text></tt> element </li></ul></li></ul>

Within those two elements, there are additional requirements, which are discussed in these guidelines and in the complete TEI P5 Guidelines. The <tt><teiHeader></tt> element serves as a description of the document presented in the <tt><text></tt> element. The <tt><text></tt> element contains the transcription of the source document.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI Header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI Header is to declare the bibliographic information related to the electronic document and if appropriate, the bibliographic data for original analog source document from which the electronic edition was created. The TEI Header often includes a description of the encoding decisions or practices used to create the electronic document. Since the advent of the TEI twenty years ago, many people have described the TEI Header as a title page for the electronic edition, and many librarians have compared it to traditional library catalog records (MARC).

As with any descriptive metadata, the metadata in the TEI Header can serve multiple audiences. In the local context, a TEI Header provides metadata about the TEI document, its source, and its provenance. The TEI Header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI Headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI Headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library's collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI Header and the MARC record.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI Header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards;” two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI Header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI Header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons, among them: the original document is a manuscript item or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence of a source document, the header creator<ol style="list-style: lower-alpha;">
<li> May assign a title and author, if appropriate.</li>
<li> Enclose the information in brackets, using the standard English language convention for editorial interjections.</li></ol></li></ol>

===Element Recommendations for the <teiHeader>===

<table border="1">
<tr>
<th colspan="6">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="6"><teiHeader></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><fileDesc></td>
<td>The fileDesc contains metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><titleStmt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><title></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><author></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entity primarily responsible for the content of the TEI document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>(unknown)</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><editor></td>
<td>If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that have made a significant intellectual contribution to the work. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><respStmt></td>
<td>Record the names of other persons or organizations not covered by <author> and <editor>, one per <tt>respStmt</tt>. Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><editionStmt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><publicationStmt></td>
<td>Use the child elements below rather than <p> for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><publisher></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><distributor></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <publisher>, in which case no <distributor> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><authority></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><idno></td>
<td>Any unique identification number for the TEI document determined by the publisher.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><availability><p></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><date when="____"/></td>
<td>Refers to the date of the first publication of the TEI document. Use <tt>when</tt> attribute to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><seriesStmt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt><title level="s"></tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="3"><title level="s" type="_"></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. Value of level attribute is drawn from TEI Guidelines.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><notesStmt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><sourceDesc></td>
<td>In order to effectively represent the source(s) when many documents are represented by the TEI header in the absence of structures identifying parent-child and component relationships, multiple source descriptions should be employed with relationships described in free text. Relationships also could be useful in other portions of the TEI header. Cataloger may need to do research to establish the original source.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><biblStruct></td>
<td>Metadata for the source document may be automatically generated from a MARC record. Use <biblStruct> with child elements listed, in the order below, for ease of display according to ISBD.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><monogr></td>
<td>Use this element to group together the elements describing the whole source document, even if the whole source document is not a "monograph", per the TEI definition of this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><author></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the source document, even if this creator is not the main entry in the catalog record. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="_"></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code.

The <tt>level</tt> attribute is used as in the TEI Guidelines.

Use of the <tt>type</tt> attribute is required: it may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>MARC245a</tt>
* <tt>MARC245b</tt>
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><title level="_" type="MARC245b"></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><respStmt></td>
<td>
Statement of responsibility, according to the national cataloging code.

If metadata is generated automatically from a MARC record, include a single empty <resp></resp> and put the entire statement of responsibility in <name>. If creating metadata manually, include one <tt>respStmt</tt> for each responsible party.

Each <tt>respStmt</tt> may have only one <tt>resp</tt> child element and one <tt>name</tt> element, though they may occur in either order. Use <tt>persName</tt> or <tt>orgName</tt> as children of <tt>name</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><edition></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><pubPlace></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><publisher></td>
<td>First publisher etc. from the original source (if present). It is recommended but not required to remove ISBN punctuation when deriving from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><date when="____"></date></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use <tt>when</tt> attribute to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><extent></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><series></td>
<td>Following the <monogr> element grouping together all the above metadata about the encoded item, information about the series to which the item belongs goes here, following the content model in the TEI Guidelines. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="1"><note></td>
<td>Notes about the source document, according to national cataloging codes.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="1"><idno></td>
<td>
In this location, <idno> refers to identification numbers for the source document. Use type="isbn-13" and type="isbn-10" if applicable.

This element may also be used to indicate the source's location in an individual institution's collection. If a formal standard location system is being used, indicate the nature of the system, e.g., <idno type="LC_call_number">.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5">encodingDesc</td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>├</td>
<td colspan="4"><p></td>
<td>In the first child of <tt>encodingDesc</tt>, include a <tt>p</tt> element containing a prose statement about the format of the data in the header. Does the data in the <tt>sourceDesc</tt> follow AACR rules? How about in the <tt>fileDesc</tt>? Is ISBD punctuation included?</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><projectDesc><p></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><editorialDecl n="_"><p></td>
<td>Record encoding level for the content as an arabic numeral in the n attribute. As content of this element, record editorial decisions made during encoding and notes about omissions of material found in the original work.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tagsDecl><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></td>
<td>
<tagUsage> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><classDecl><taxonomy xml:id="____"><bibl></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art & Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="5"><profileDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><textClass></td>
<td>The elements below are contained within this element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><classCode scheme="___"></td>
<td>True classification numbers as opposed to call numbers can be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in classDecl. Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="3"><keywords scheme="____"></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt>classDecl</tt>. Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="2"><term></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="5"><revisionDesc></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="4"><change when="''YYYY-MM-DD''" who="''URI''"></td>
<td>
Create a <tt><change></tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt><change></tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change in ISO 8601 form (YYYY-MM-DD) should be recorded on the <tt>when=</tt> attribute.

The person who is responsible for making the change is indicated by the <tt>who=</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt><respStmt></tt> or <tt><person></tt> element. E.g., <tt>who="#Kevin_Hawkins"</tt>.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader>
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="MARC245a">Lincoln and Seward.</title>
<title level="m" type="MARC245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<respStmt>
<resp/>
<name>By Gideon Welles</name>
</respStmt>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon & company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data follows
AACR2 when applicable.</p>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Only un-numbered divisions are used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Linking between encoded text and images of source documents==

There are two recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>@facs</tt> attribute on each <tt><pb></tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>@xml:id</tt> attribute on each <tt><pb></tt> element and a METS document to provide correspondence between <tt><pb></tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

The examples below use the former method.

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).

Texts at Level 1 can be created and encoded by fully automated means, using uncorrected OCR of page images ("dirty OCR") or exporting from existing electronic text files. Encoding is performed automatically based on artifacts of the OCR or other document creation process (page breaks, for example) and metadata collected during the imaging or preparation process. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>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</li>
</ul>

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">There should be only one child of <body>: a single <div> (or <div1>)</td>
</tr>

<tr>
<td colspan="1"><ab></td>
<td colspan="1">There should be only one child of the <div> (or <div1>): a single <ab> wrapping all of the OCR text. If the text is ever “upgraded” to a Level 3 or higher, the <ab> element will be replaced by structural elements like <p> and <table>.</td>
</tr>
<tr>

<td colspan="1"><pb></td>
<td colspan="1">Required in Level 1. Page images can be linked to the text by specifying a jpeg or other image file as the value of the facs= attribute. Page numbers can be supplied with the n= attribute to record the number that is on the page. The Task Force sees the use of METS here as having a tremendous advantage. METS/TEI page turning documentation will be included in the near future.</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>
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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====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.)

====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. Level 2 requires 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.

Though texts at Level 2 can be created and encoded by automated means, based on the typographic elements in the electronic file (for example, bold centered text at the top of the page surrounded by whitespace indicates a new chapter heading, and thus a new division), automated methods are not likely to be reliable across a large body of work, especially if the materials are from earlier than 1900. Level 2 encoding requires some human intervention to identify each textual division and heading. Level 2 texts do not require any special knowledge or manual intervention below the section level.

For the most part, Level 2 texts are <u>not</u> 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 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

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>
<td colspan="1">Optional</td>
</tr>
<tr>
<td colspan="1"><div1> or <div></td>
<td colspan="1">If no type= attribute is specified, a type= value of "section" should be presumed. </td>
</tr>
<tr>
<td colspan="1"><head></td>
<td colspan="1">Required if headings are present</td>
</tr>
<tr>
<td colspan="1"><ab></td>
<td colspan="1"> At least one container element is required.</td>
</tr>
</table>

====Level 2 Example: Basic Structure====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>[See above for an example of a TEI Header]</teiHeader>
<text>
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb xml:id="p21198-zz0002mpqr" n="1"/>
<head>A DISSERTATION UPON Religious Worship.</head>
<ab>[a whole section is contained within this anonymous block
tag; interspersed with <pb> elements pointing to page
images]<pb xml:id="p21198-zz0002mpwb" n="2"/></ab>
</div>
<div type="section">
<pb xml:id="p21198-zz0002mq0c" n="27"/>
<ab>
</ab>
<div type="subsection">
<head>CHAP. I. The Origin of the Customs and Ceremonies of the Jews. their federal Divisions;
and the various Particulars wherein they differ.</head>
<ab>[all the paragraphs of chapter one go here with page
breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

==== Level 2 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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 government documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail openings, 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 determination 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 regarding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents. 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' personal 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 requesting 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>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Level 3 texts can be created by conversion from an electronic source such as
HTML or word-processed documents or a print source with the automatic generation of full text by
optical character recognition software. Level 3 texts can also be created from scratch (e.g., transcription, born digital, etc.).
Encoding at this level offers the advantage of the TEI header, interoperability with other TEI collections, and extensibility to higher levels of encoding.
Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or
sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of
encoding these features, as well as figures, notes, and all changes of typography, allows a range of
options for display, delivery, and searching. For example, one has the option of identifying and,
therefore, specifying the display charactersitics of different typographic styles, and regularizing the
display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images and, therefore, can be uploaded, downloaded
and delivered quickly, and require less storage space than digital collections with page images.
However, the simple level of structural anaylsis and absence of specialized content analysis reflected
in Level 3 encoding may make it desirable for some, depending on project priorities, to include page
images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag,
or review texts</li>

<li>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</li>
</ul>

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2, plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><front>, <back></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><div></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><floatingText></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><p></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><lg> and <l></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><table>, <row>, and <cell></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><figure></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><hi></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><note></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as "margin".</td>

</tr>
<tr>
<td colspan="1"><lb></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

'''Forme Works'''

Running heads, catch words, and other such forme work information should not be included in Level 3, with the exception of page numbers, which are recorded using <tt>pb</tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

<p>'''Front Matter'''</p>

<p>'''<div type="contents">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT lists] to mark up the table of contents with the <tt><ptr></tt> element used to reference the starting page number. The <tt><ptr></tt> element can reference the <tt><pb></tt> identifier or an identifier (e.g., @xml:id) placed in the corresponding division of text.</p>

<p>'''Body'''</p>

<p>'''<note>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom
of a page, a note may become included in another paragraph or section of the encoded text, and thus
separated from its reference. There are options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note is inserted at the point of reference. An "n" attribute records the value of the
note reference if there is one.</li>
<li>End-of-Division. Notes moved to the end of the corresponding division of the text (e.g., end of chapter).</li>
</ul>

<p>'''Back Matter'''</p>

<p>'''<div type="index">''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt><ref></tt> element used to mark up page numbers given in the index entry. Add the "target" attribute (@target) to reference the n= attribute of the <tt><pb></tt> of the referenced page.</p>

====Level 3 Examples====

=====Basic Structure: Prose ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [stuff] </teiHeader>
<text>
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Basic Structure: Verse ([http://brie.dlib.indiana.edu/~mdalmau/bpg/VAA2383_prose_verse_p5_lev3.xml See full example])=====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader> [info] </teiHeader>
<text>
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l n="1">O the days gone by! O the days gone by!</l>
<l n="2">The apples in the orchard, and the pathway through the rye;</l>
<l n="3">The chirrup of the robin, and the whistle of the quail</l>
<l n="4">As he piped across the meadows sweet as any nightingale;</l>
<l n="5">When the bloom was on the clover, and the blue was in the sky,</l>
<l n="6">And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog <hi rend="right">3</hi>
<ptr target="#VAA2383_011"/></item>
<item>II. Romance <hi rend="right">12</hi>
<ptr target="#VAA2383_020"/></item>
<item>III. The Costume <hi rend="right">21</hi>
<ptr target="#VAA2383_029"/></item>
<item>IV. Desperation <hi rend="right">30</hi>
<ptr target="#VAA2383_038"/></item>
<item>V. The Pageant of the Table Round <hi rend="right">38</hi>
<ptr target="#VAA2383_046"/></item>
</div>
</pre>

=====Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="b">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"P<hi rend="sc">ENROD</hi> S<hi rend="sc">CHOFIELD</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
[Source and processing information goes here]
</teiHeader>
<text>
<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>
<p>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 government
documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail
openings, 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 determination
regarding these issues.</p>

<p>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

<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.</p>

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

<note place="bottom" anchored="true" n="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 regarding
an application for employment with the United Nations
was also intercepted, in a manner not revealed by the documents.
CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<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' personal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note requesting
information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

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.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

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

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

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

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

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

====Element Recommendations for Level 4====

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

<table border="1" width="80%">
<tr>
<td colspan="1"><titlePage> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><group></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><list> and <item></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><table>, <row>, and <cell></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><hi></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; rend attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><emph>, <foreign>, <gloss>, <term>, or <title></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><epigraph>, <quote>, <said>, <mentioned>, or <soCalled></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><sic>, <corr>, or <choice></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><opener>, <dateline>, <salute> <closer>, <signed>, <postscript></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><argument></td>
<td colspan="1">Recommended to encode a "list of topics sometimes found at the start of a chapter or other division".</td>
</tr>

<tr>
<td colspan="1"><trailer></td>
<td colspan="1">Recommended to encode a heading- or title-like content at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><add>, <del>, <gap>, and <unclear></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><figure>, <head>, <figDesc>, and <graphic></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><castList>, <castItem>, <sp>, <speaker>, and <stage></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><sp> and <speaker></td>
<td colspan="1">Required to encode oral histories interviews.</td>
</tr>

<tr>
<td colspan="1"><persName>, <placeName>, <geogName>, and <orgName> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><listName>, <listPlace>, and <listOrg> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, "The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way."

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html <epigraph>]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html <quote>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html <said>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html <mentioned>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html <soCalled>],
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html <emph>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html <foreign>] (e.g. <tt><foreign xml:lang="fr"></tt>),
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html <gloss>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html <term>],
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html <title>]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html <hi>] (e.g. <hi rend="bold">). This element may also be used if more specific elements are not used, as above.

* Any of the following three methods may be used to encode errors or typos in original texts.
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html <sic>] element used alone is recommend to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html <corr>] element used alone is recommended to provide corrections without indicating the initial error
** both together inside a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html <choice>] element is a combination of the two approaches: both the apparent error and its editorial correction are recorded:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
FROM: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
FROM: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <argument>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <argument> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
FROM: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <trailer>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.)
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <add>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <del>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <unclear>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <gap>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews.)

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="overstrike" hand="JHL">their manner</del> <add rend="sup" hand="JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="JHL" rend="overstrike">instead</del> far from being terse, argumentative,
convincing, are without head or tail & are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads & in short without a subject (so to
speak).</p>
</pre>
FROM: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for & trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
FROM: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"]

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <titlePage>] should include the verso if present, divided by <pb n="verso"/>.

* Frontispieces should be encoded as a <figure>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <p>.

* Tables of contents, errata, subscription lists, "other titles by the same author" should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded.

*For publisher's advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <samplingDecl>]

=====Level 4 Name Tagging=====
Names should be encoded using <persName>, <placeName>, <geogName>, and <orgName> elements with the "ref" or "key" attribute providing a reference to a <person>, <place>, or <org> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. The "ref" attribute should be used when pointing to web accessible files and the "key" used for pointing to databases or files not generally web accessible.

For example, a web accessible external TEI file may contain an entry for each name, grouped accordingly under <listPerson>, <listPlace>, and <listOrg>, which is uniquely identified with an "xml:id" attribute. The "ref" value in the source file references the "xml:id" value in the external file.
(In the examples below the external file is named <tt>context.xml</tt> for “contextual information,” and is in the same directory as the source file, but it may be named anything and placed anywhere, including elsewhere on the web.) When pointing to a database or a non-web accessible file, the "key" attribute points to the unique key in the database table or, like with the "ref" attribute," the "key" attribute can point to the "xml:id" value in the external file (see example below).

When referencing external files or databases, it is strongly recommended to provide an explanation in the <editorialDecl> section of the TEI Header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the "xml:id" attribute (e.g., tgn_0000000 for the Getty's Thesaurus of Geographic Names). When referencing a controlled vocabulary be sure to specify this information in the <classDecl> section of the TEI Header.

<pre>

<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

<pre>

<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

<pre>

<figure n="VAA7662-004-001">
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</figure>
</pre>

<pre>


<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

<pre>

<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====
* <figure> groups elements representing or containing graphic information such as an illustration or figure; in this context <figure> typically contains the following elements:
** <caption> which is a literal transcription of a caption on a figurative image.
** <figDesc> which is a free text description of the image used, potentially, for searching the images themselves.
** <graphic> which points to the URI of the image itself using a "url" attribute and containing other presentation instructinos such as dimension at which the graphic should be displayed, etc.

Take this as an example of encoding the frontispiece of the ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.
<pre>

<front>
<div type="frontispiece">
<figure>
<caption>Sojourner Truth.</caption>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>

</pre>

=====Level 4 Letters=====

* Letters that occur within the text body provided memorable challenges in P4. However, the introduction of the <floatingText> element in TEI P5 gives a cleaner approach of encoding letters or any "independent text which interrupts the text containing it at any point but after which the surrounding text resumes” (see more in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFLT Section 4.3.2 Floating Texts]) It is recommended that quoted letters that occur as part of a text (and not collections of letters themselves) be encoded within <floatingText> <body> <div1 type="letter"> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <opener>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <dateline>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <salute>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <signed>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <closer>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <postscript>] included as appropriate.

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="italics">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="italics">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—& B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
FROM: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====
*Within the front matter (<front>) of a performance text, cast lists should be encoded as <castList>s, with each item in that list encoded as <castItem>s.
*Also, if desired (though not required), each <castItem> may be uniquely identified with the xml:id attribute construct.

From Shakespeare's ''King Lear'':

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>
*Within the body of performative texts, speeches are encoded as <sp>, with speakers identified by the <speaker> element which is a child of <sp>
*Stage directions are encoded as <stage> and enclose block level content describing scenery, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <p> for prose speech with <lb> to designate a new line in a particular edition of the text or <lg> and <l> to describe dramatic verse structures).
*If referencing the xml:id defined in the <castList> is desired, utilize the "who" attribute construct for the IDREF datatype.

Again, from ''King Lear'':
<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp>
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp>
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp>
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

=====Level 4 Oral History=====

* Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <teiHeader> in several ways:
** In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <profileDesc>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <particDesc>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <list>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <name>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <item>]s.
** As a list of author <name>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <fileDesc>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <titleStmt>]

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

* The list of interview's participants can be also listed within the body of the interview (see an example below.)
* Questions and answers from interviewees and interviewers are encoded as <sp>, with speakers identified within <speaker> elements with a who= attribute the value of which corresponds to the xml:id= in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

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

* One of the possible approaches to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ "Oral Histories of the American South"], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <milestone>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====
* All verse, even poems without separate stanzas or verse paragraphs, should be contained within a line group element <lg> and
* Each line of verse should be contained within a line element <l>.
* It is common to see informal divisions within poems, noted by a string of asterisks or periods. These should be encoded as <milestone>s with attribute values of unit="typography" and n="()" indicating the character used and its occurrence, <milestone unit="typography" n="******"/>.
* Use the <l> element to encode each line of verse, with the rend= attribute used record indentation.

The following is from Lewis Carroll's ''The Hunting of the Snark''
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza">
<l>"Just the place for a Snark!" the Bellman cried,</l>
<l rend="indent">As he landed his crew with care;</l>
<l>Supporting each man on the top of the tide</l>
<l rend="indent">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza">
<l>"Just the place for a Snark! I have said it twice:</l>
<l rend="indent">That alone should encourage the crew.</l>
<l>Just the place for a Snark! I have said it thrice:</l>
<l rend="indent">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>

===LEVEL 5: Scholarly Encoding Projects===

<p>Level 5 texts are those that require subject knowledge, and encode semantic, linguistic, prosodic, or
other elements beyond a basic structural level.</p>

====Level 5 Examples====

=====Lemmatization and Thematic Keyword Tagging from the Swinburne Project=====

<pre>
<lg>
<l n="67"><w lemma="high">High</w>
<w lemma="thing">things</w>
<seg type="keyword" xml:id="ke39" corresp="#kw-song"><w lemma="the">the</w>
<w lemma="high">high</w>
<w lemma="song">song</w></seg>
<w lemma="teach">taught</w>
<w lemma="he">him</w>; <w lemma="how">how</w>
<w lemma="the">the</w>
<w lemma="breath">breath</w></l>
<l n="68"><w lemma="too">Too</w>
<w lemma="frail">frail</w>
<w lemma="for">for</w>
<w lemma="life">life</w>
<w lemma="may">may</w>
<w lemma="be">be</w>
<w lemma="more">more</w>
<w lemma="strong">strong</w>
<w lemma="than">than</w>
<w lemma="death">death</w>;</l>
<l n="69"><w lemma="and">And</w>
<w lemma="this">this</w>
<w lemma="poor">poor</w>
<w lemma="flash">flash</w>
<w lemma="of">of</w>
<w lemma="sense">sense</w>
<w lemma="in">in</w>
<w lemma="life">life</w>, <w lemma="that">that</w>
<w lemma="gleam">gleams</w></l>
</lg>
</pre>

=====Prosodic Elements in William Harkins's translation of Pushkin's "Little House in Kolomna"=====

<pre>
<text>
<body lang="rus">
<div type="translation" id="Harkins">
<head>Little House in Kolomna</head>
<epigraph lang="lat">
<quote>Modo vir, modo femina.</quote>
<bibl>Ov.</bibl>
</epigraph>
<lg type="octave" id="st1" n="1">
<head>I.</head>
<l rhyme="a" met="m" id="l1.1" n="1">By now I'm all fed up with four-foot verse;</l>
<l rhyme="B" met="f" id="l1.2" n="2">Each scribbler writes it. It's a mere diversion</l>
<l rhyme="a" met="m" id="l1.3" n="3">For children — let them keep it. I could do worse</l>
<l rhyme="B" met="f" id="l1.4" n="4">Than in the octave's measure make excursion.</l>
<l rhyme="a" met="m" id="l1.5" n="5">It's true, in triple rhyme I'm little versed —</l>
<l rhyme="B" met="f" id="l1.6" n="6">But let me try it. To fame I've no aversion!</l>
<l rhyme="c" met="m" id="l1.7" n="7">For rhymes have ever echoed in my song!</l>
<l rhyme="c" met="m" id="l1.8" n="8">Two come themselves: the third they'll bring along.</l>
</lg>
<lg type="octave" id="st2" n="2">
<head>II.</head>
<l rhyme="A" met="f" id="l2.1" n="1">And so with types of rhyme I can't be choosy:</l>
<l rhyme="b" met="m" id="l2.2" n="2">To verbal rhyme I'll grant the widest play.</l>
<l rhyme="A" met="f" id="l2.3" n="3">You know, our poets past have oft refused it,</l>
<l rhyme="b" met="m" id="l2.4" n="4">As though ashamed of it. Why so, I say?</l>
<l rhyme="A" met="f" id="l2.5" n="5">True, S. of pious memory never used it,</l>
<l rhyme="b" met="m" id="l2.6" n="6">And I eschew it too, whene'er I may,</l>
<l rhyme="C" met="f" id="l2.7" n="7">Why should we so? Of rhymes we've scarce sufficient;</l>
<l rhyme="C" met="f" id="l2.8" n="8">Without the verbs our rhyme will be deficient.</l>
</lg>

[ETC.]
</pre>

=====Prosodic, Analytical Structure, and Translations marked up in a poem from the Notebooks of Ricardo Sanchez=====
<pre>
<div1 type="poem">
<head><title>AN EVIDENCE </title></head>

<lg type="stanza">
<l rend="indent1"> Ricardo,</l>
<l rend="indent1"> when power is</l>
<l rend="indent3"> rooted</l>
<l rend="indent1"> in the land</l>
<l rend="indent3"> la tierra <note type="translation" resp="trans" place="foot"> the earth,
soil </note></l>
<l rend="indent1"> it is evident</l>
<l rend="indent3"> and true.</l>
<l rend="indent1"> Land, in some languages</l>
<l rend="indent4"> is earth--</l>
<l rend="indent1"> And this earth</l>
<l rend="indent3"> (the planet...</l>
<l rend="indent2"> all of it</l>
<l rend="indent1"> is nurturing your powers </l>
</lg>

<signed><name type="personal"> Lorenzo Thomas </name></signed>

<trailer><name type="place"> AMSTERDAM, THE NETHERLANDS </name>
<date> 11 SEP 1978 </date>

<address>
<addrline>
<name type="personal"> Lorenzo Thomas </name>
</addrline>
<addrline> P.O. Box 14645 </addrline>
<addrline> Houston, TX 77021 USA </addrline>
</address>
</trailer>

</div1>

</pre>

==General Guidelines for Attribute Usage==

<p>Some general advice on the use of particular attributes
follows.</p>
<ul>
<li><b>type=</b>: Constructing a list of acceptable attribute values
for the type attribute for each element, on which everyone could agree, is impossible. Instead,
it is recommended that projects describe the type= attribute
values used in their texts in the project ODD file and that this list be made available to people
using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For
a list of standard names and definitions of bibliographic
features of printed books, see <i>ABC for Book Collectors</i> by John
Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf). For those elements where type is not
required, such as <head> and <title>, use the
attribute values for subtitles and additional titles, but not
main titles.<br /> Example: <tt><div1 type="volume"></tt></li>

<li><b>n=</b>: This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers. For example, <tt><pb n="456"/></tt></li>

<li><b>xml:id=</b>: If you are in a situation that requires you to
uniquely identify an element that will be used to reference
another specific location in one or more texts, use an <tt>@xml:id</tt>
attribute. The value of this attribute must be unique within a
document, and must be composed of alphanumeric characters,
dots, hyphens, and underscores, and must start with a
letter.<br /> Example: <tt><note xml:id="n5" n="5"></tt></li>

<li><b>target=</b>: A URI. May be used to point internally within the same document by preceding the value of the target element's <tt>@xml:id</tt> with a number sign (U+0023). E.g., in the case of footnotes where
the <tt><anchor xml:id="n5" n="5"></tt> is at a specific place in the
text and is referred to by the <tt><note target="#n5" n="5"></tt>
which contains the actual content of the footnote itself
elsewhere.</li>
<li><b>rend=</b>: Difficulty using <tt>rend=</tt> attributes occurs when it is desirable to
record more than one rendition feature. With this in mind, it is recommended that projects
employ the following adaptation of “rendition ladders”, a concept developed at the
[http://www.wwp.brown.edu/ Brown University Women Writers Project]. This system allows for
sets of multiple renditional features to be included in one <tt>rend=</tt> value. Rendition
ladders consist of categories of renditional features with values of each of those features
enclosed in parentheses.<br/> rend= should only be used to override a default value. For
instance, if all text encoded as <tt><hi></tt> is defined as being rendered in italics,
there is no reason to encode text as <tt><hi rend="slant(italics)"></tt> Combining
renditional features would result in an element with attributes such as <tt><l
rend="slant(italics)align(right)"></tt>
{| border="1"
|-
! keyword
! some possible values
|-
| <tt>slant</tt>
| <tt>italics</tt> or <tt>upright</tt>
|-
| <tt>weight</tt>
| <tt>bold</tt> or <tt>normal</tt>
|-
| <tt>case</tt>
| <tt>allcaps</tt> or <tt>lower</tt> or <tt>smallcaps</tt> or <tt>upper</tt> or <tt>mixed</tt>
|-
| <tt>align</tt>
| <tt>left</tt> or <tt>right</tt> or <tt>center</tt> or <tt>centre</tt> or <tt>inside</tt> or <tt>outside</tt> or <tt>none</tt>
|-
| <tt>indent</tt>
| a number
|}
</li>
<li><b>xml:lang=</b>: Used to indicate the natural language of the content of an element. Generally not used at levels 1 or 2. At levels 3 or 4 should contain the appropriate language subtag; further subtags (script, region, variant, extension, private use) are rarely appropriate. If only the language subtag is present (the most common case), a corresponding <tt><language></tt> element should '''not''' be present in the TEI header. If a private use subtag is present, a corresponding <tt><language></tt> element must be present in the TEI header. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the TEI documentation].</li>
</ul>

==Acknowledgements==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota and the Spring 2009 Forum in Raleigh, North Carolina in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of this Document==
<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Christina Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA mid-winter (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Christina Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natalia Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, Virginia Foundation for the Humanities (chair)</li>
<li>Chris Powell, The University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina at Chapel Hill</li>
<li>Perry Willett, The University of Michigan</li>
</ul>

[[Category:SIG:Libraries]]