LEAP Project

The Livingstone Online TEI P5 Encoding Guidelines

Table of contents

1. About the Livingstone Online TEI P5 Encoding Guidelines

These guidelines (TEI P5 ODD Customization) summarize Livingstone Online project practices for encoding in TEI P5 the manuscripts of David Livingstone (1813-1873), the Victorian explorer, abolitionist, and missionary. The guidelines also offer a fairly comprehensive overview of Livingstone's practices and idiosyncrasies as a writer.

The guidelines are a product of the Livingstone Online Enrichment and Access Project (LEAP), a three-year initiative (2013-2016) funded by the National Endowment for the Humanities (USA). James Cummings with assistance from Adrian S. Wisnicki, Heather F. Ball, and Justin Livingstone created the guidelines, with the initial prose based on Livingstone Online's TEI P5 Tagging Guidelines written by Adrian S. Wisnicki and Heather F. Ball.

Significant contributions to the development of the guidelines have also come from the LEAP critical encoding team: Angela Aliff, Mary Borgo, Erin Cheatham, Samantha Fitch, Ashanka Kumari, Chris Lawrence, Anne Martin, Jared McDonald, Alexander Munson, Kate Simpson, and Megan Ward (critical encoding director).

The guidelines are released under a Creative Commons Attribution-NonCommercial 3.0 Unported license, and we encourage broad, non-commercial use of the guidelines per the open educational remit of Livingstone Online.

2. Overview

2.1. Documentation Markup

In the prose of this documentation XML Elements, Attributes and Values appear as follows:

(Note: the colors/formats are provided only to assist you in distinguishing between tags, attributes, and values. You do not need to change font colors in your transcriptions as you are transcribing. In general these colours mimic those found in the oxygen XML editor.)

2.2. Marking Up Text - Basic Rules

  1. When text is marked up, a tag is placed at the beginning of the text as well as at the end, per the following format: Original text:
    the man turned out to be Livingstone
    Marked up:
    the man turned out to be <persName>Livingstone</persName>

    Note: that the first tag denotes the beginning of the marked up text, while the second tag begins with "/" and denotes the end of the marked up text.

  2. If the opening tag includes an attribute, the attribute is NOT repeated in the closing tag: Original text:
    we were greeted by the Nyamwezi
    Marked up:
    we were greeted by the <term type="tribe">Nyamwezi</term>
  3. If there are two or more tags nested over one bit of text, the closing tags are placed in reverse order:

    Original text:
    we saw the Lualaba
    Marked up:
    we saw the <placeName><geogName>Lualaba</geogName></placeName>
  4. An attribute is always accompanied by a value, for instance:
    <term type="tribe">Nyamwezi</term>
  5. If an opening tag ends with a "/", then it is an "empty element" combining the opening and closing tag and need not be used again at the end of whatever is being marked up. Original text:
    we saw the Lualaba
    Marked up:
    <lb/>we saw the Lualaba
  6. Any problems related to the transcription should be addressed directly in the transcription at the points where they occur using the "comment out" feature. Original text:
    He called me over.
    Marked up:
    He called me over. <!-- The text is very illegible here and I've done the best I could. However, this might also be transcribed as "He willed in on me." What should I do? DH -->
    In other words the commented out bit begins with <!-- followed by a space and ends with -->. Always add your initials inside but at the end of the comment.

2.3. File Naming

When transcribing, please use the LEAP designated file name for the given item. This can be found on Livingstone Online along with the rest of the bibliographical data for the given item. So, for instance, Livingstone's letter to Rev. D.G. Watt (18 August 1850) would be:

liv_000699.xml

If you are transcribing the given item with other individuals in sequence (and so the transcription is not yet final) please add your initials directly after the LEAP designated name:

liv_000699_aw_hb_ks_hb.xml

In the above example, the four sets of intials indicate that the transcription has been worked on in four stages. The first three stages were done by three different individuals (aw, hb, ks) and the last stage was done by the second individual (hb).

The xml:id value on the <TEI> element of any LEAP file should be the initial parts of the LEAP designated file name without the '.xml' suffix.
<?xml-model href="leap.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> <?xml-model href="leap.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?> <TEI xml:id="liv_000699" xmlns="http://www.tei-c.org/ns/1.0">   <!-- Change the xml:id above to be the LEAP file name without suffix -->  </TEI>                 

Please Note: All TEI P5 XML files are in the TEI Namespace which means their root element has a psuedo-attribute xmlns with a value of "http://www.tei-c.org/ns/1.0". This is the TEI Namespace and is inherited by any elements underneath keeps TEI elements safe from confusion with similarly-named elements from other schemes.

Definitions of the elements used above are:

4. Divisions of the Text

We use the <div> to contain the main body of text of any given Livingstone object, so in most cases a transcription will only have one <div> elment that opens and closes the text. However, there are some cases where a second <div> element should be used. See 5. Front and Back Matter, 11.4. Textual Colors, and 11.9. Textual Directions.

Definitions of the elements used above are:

5. Front and Back Matter

Use <front> and <back> elements (siblings of the <body> element) to contain to any material that, respectively, precedes (e.g., a table of contents) or succeeds (e.g. an appendix) the main text being encoded.
<front> <!-- Table of contents goes here --></front>   <body>    <div>        <p> <!-- Main text being encoded goes here --></p>    </div>   </body>   <back> <!-- Appendix goes here --></back>

Definitions of the elements used above are:

6. The Beginning of a New Page

After the initial <text><body><div> tags (already in the diary template document), make sure there is a <pb/> element at the beginning of each new page/image that you transcribe. Note that the manner in which this is based on the LEAP designated file name
<pb facs="liv_000699_0001.jpgn="0001"/> <!-- a page worth of text --> <pb facs="liv_000699_0002.jpgn="0002"/>

Note that this combined or empty element ends with a "/" and has no separate closing tag. The facs attribute points to the image facsimile for this page, the n attribute records the project page number separately.

Definitions of the elements used above are:

7. The Beginning of a Manuscript Line

Whenever you come to the beginning of a manuscript line, use
<lb/>
No corresponding tag is needed at the end of the line. Original text:
As we traveled 
I came
across two men.
Marked up:
<lb/>As we traveled <lb/>I came <lb/>across two men.
If line breaks occur in the middle of an addition, do not place <lb/> before the first line of the addition, but do use it to mark the beginning of each subsequent line of the addition:
<add place="marginleft">First line of addition <lb/>second line, <lb/>and third line.</add>

Definitions of the elements used above are:

8. The Beginning of a New Paragraph

When you start a new paragraph, use the following tag: <p>

The rend attribute is used to indicate information about the rendering of the paragraph as a whole in the original source. For example, if the paragraph as a whole was centered on the page, you might give it a value of "center" or if aligned right a value of "right". The use of rend to say whether something is centered or right (left is considered the default so there is no need to record that) is a bit of a judgment call regarding the placement of the paragraph on the page.
<p rend="right">This paragraph is aligned to the right on the page.</p>

For more information about the rend attribute see 11.3. Textual Formatting.

The default assumption is that a paragraph is indented, so there is no need to mark that. For marking the exceptionally indented first lines of paragraphs see 11.6. More Than One Space between Words.

However, if a paragraph is not indented, please mark it as follows:
<p rend="no-indent">This paragraph is not indented</p>

Note: It is especially important to use <p rend="no-indent"> when marking new, dated diary entries that Livingstone begins on a new line but does not indent.

Also, remember at the end of the paragraph to use the closing paragraph tag </p>.

Finally, note that we capitalize the first word of a new paragraph by default. If it is not capitalized, use the <choice>, <sic>, and <corr> tags to correct this.
<p><choice><sic>arrived</sic><corr>Arrived</corr></choice> at the lake.</p>

Definitions of the elements used above are:

9. Dates

For marking up dates use the <date> element with the when attribute. The value of the when attribute should always be given in this YYYY-MM-DD format (four-digit year, two-digit month, two-digit day). This is an important international standard for representing dates and stops people and computers getting confused as to whether '05/02/71' means the second of May or the fifth of February:
<date when="1871-02-05">5th February 1871</date>
If only the month and year (and not the day) are given, code as follows:
We visited in <date when="1871-02">February 1871</date>
However, if the day (and month) are given, but not the year, yet you know the year provide it. For instance, if Livingstone begins a diary entry with "5th" but you know from previous entries that this actually means 5th February 1871, then code it as follows:
We visited last year on the <date when="1871-02-05">5th</date>
If you don't know the year, bring it to the attention of the project and code it as follows:
We visited on <date when="--02-05">5th February</date>
Finally, use the from and to attributes to provide a start and end date of a range. Use these as needed:
<date from="1871-02-05to="1871-02-07">5th to 7th February 1871</date>
For B.C. dates code as follows:
<date when="-600-03-28">28 March 600 B.C.</date>
or
<date when="-600">600 B.C.</date>

For coding dates that Livingstone adds to the margin of the Unyanyembe Journal, see 11.15. Authorial Notes within the Text.

Definitions of the elements used above are:

10. Letters

10.1. The Opening and Closing of Letters

Note that the opening and closing of letters often have items which aren't strictly paragraphs. The TEI has special elements just for these. The entire beginning of a letter should be contained within an <opener> tag. Within this <opener> tag, any address or date will also be contained within a single <dateline>. Finally, any personalized greeting, should go inside of a <salute> tag:
<lb/><opener><dateline rend="right"><placeName>Hadley Green</placeName> <lb/><date when="1857-08-22">22 August <lb/>1857</date></dateline> <lb/> <lb/><salute>My Dear Sir,</salute></opener>                     
Likewise, the end of a letter should be contained within a <closer> tag, with any personalized address contained within a <salute> tag and any signature within a <signed> tag.:
<lb/><closer><salute>Sincerely,</salute> <lb/><signed><persName>David Livingstone</persName></signed></closer>                     

For both the <opener> and <closer>, linebreaks (see 7. The Beginning of a Manuscript Line) should be marked in the regular fashion, as in the examples above.

The <date> and <persName> elements are discussed in more detail below.

Definitions of the elements used above are:

10.2. Postal Address of Letter Recipient

The portion of each letter that contains that postal address of the letter recipient should be placed inside both the <closer> and <address> elements. If the placement of the address within the letter does not allow for the address to be added to the <closer>, then place the address in a separate set of <div> and <ab> elements. The beginning of each line of the address should be marked with <addrLine> and the end of each line of address should be marked with </addrLine>. Note too that when you use the <addrLine> tag, you should not use the <lb/> tag (see 7. The Beginning of a Manuscript Line). In other words, use <addrLine> or <lb/>, but not both.
<address> <addrLine><persName>Bevan Braithwaite</persName></addrLine> <addrLine><placeName>3 New Court</placeName></addrLine> <addrLine><placeName>Lincoln's Inn</placeName></addrLine> </address>

Definitions of the elements used above are:

10.3. Postscripts

Use the <postscript> element to contain the entirety of any postscript added to a letter. Each separate postscript should be contained by its own element. The n may be used to number successive postscripts.
<lb/><postscript n="1"><label>P.S.</label> Give my regards  <lb/>to your children.</postscript> <lb/><postscript n="2"><label>P.P.S.</label> And greet your parents</postscript>

Note: In order for your use of the <postscript> to validate, it may be necessary to place empty <opener/> and <closer/> tags before it, if you haven't already otherwise used such tags.

Definitions of the elements used above are:

11. Marking Authorial Composition Practices

11.1. Any Type of Heading

Use the <head> element for any type of heading, such as the title of a chapter or section or the heading of a list
<head>Chapter I</head>

Definitions of the elements used above are:

11.2. Running Header (including Authorial Page Numbers)

Use the <fw> element to contain any type of running head (usually, but not always, found in the header or footnote of a given page) that appears on a page or series of pages. The rend may be used as needed to mark the location of this element.
<fw rend="center">1</fw>

For any page numbers instituted by Livingstone himself, use the <fw> element plus n in the following manner:

<fw n="heading_XIV">XIV</fw>

In other words, whenever <fw> is used to encode one of Livingstone's page numbers, n value should begin with "heading_" followed by the number Livingstone uses, in the form that he uses it (i.e., Roman or Arabic numeral).

Definitions of the elements used above are:

11.3. Textual Formatting

If the original text is formatted in some manner such as underlining, superscript, etc., use the <hi> element with the rend attribute.

Original text:
I saw the man
Marked up:
I saw <hi rend="underline">the man</hi>

If there is more than one type of formatting, for instance both underline and superscript, use the rend attribute only once but provide two values separated by a space.

Original text:
He was the Number 1 man
Marked up:
He was the N<hi rend="sup underline">umber</hi> 1 man
Please Note: The rend attribute is part of the att.global class and so can be used on other elements if they are present. For example instead of marking up:
<hi rend="underline"><placeName><geogName type="river">Lualaba</geogName></placeName></hi>                     
one can do:
<placeName rend="underline"><geogName type="river">Lualaba</geogName></placeName>                     
but if unsure then the former is acceptable.

Definitions of the elements used above are:

11.4. Textual Colors

Livingstone occasionally changes the color of his text. In the majority of cases, such changes fall into one of two categories: a change in color for a few words; a change in color for a longer section of a text. Changes of the former sort (a few words) are usally due to an after-the-fact addition, so the color change should be marked with rend and the appropriate color directly on the <add> element:
We followed <add place="aboverend="blue">the</add> path
If Livingstone changes color for a longer section of text (this often happens in his field diaries), use the <seg> element (or, for very long sections, <div> element) plus rend and the appropriate color to mark the different sections of the text:
<div> <lb/><p><seg rend="black">First section in black would go here and <lb/>could span part of a line, a line, or several lines</seg>.</p> </div> <div rend="blue"> <lb/><p>Second longer section in blue would go here.</p> </div>             
Please note: Sometimes words appear to be the same color but are darker than their surrounding text. This may or may not be an intentional attempt by Livingstone to emphasize a portion of the text. To be on the safe side, code such darkening as appropriate. If it seems to be intentional, code it as follows with hi plus the appropriate color:
<p rend="black"><hi rend="black"><persName>Mtarika</persName></hi> came at last.</p>
If it seems to be unintentional, code it with seg plus the appropriate color:
<lb/><p rend="black">They do not appear to have asked for the <lb/><seg rend="black">names of places</seg> so much as for those of people</p>                 

Definitions of the elements used above are:

11.5. A Word Broken Up Over Two Lines

Use the <w> element to mark words that Livingstone breaks up over two lines. You also add the break attribute with the value of "no" to the <lb/> that falls between the two halves of the word. For LEAP materials the assumed value for the break attribute is yes, so you do not need to provide this unless it is an exceptional circumstance. Use maybe only in those cases when you are not sure whether a single word apparently broken up over two lines may indeed be two words.

Livingstone's use of hyphens is erratic. Sometimes he hyphenates a word at the end of the first line, sometimes at the beginning of the second, sometimes in both places, sometimes in neither.

We code each of these instances in the same way, but we also always supply a hyphen at the end of the line if Livingstone himself has failed to provide it.

Example #1 (no hyphen at all)
<lb/>I look on the drove they brought <w>un<supplied>-</supplied>  <lb break="no"/>chained</w> with a sort of pleasure after
Example #2 (hyphen only in first line)
<lb/>by one of <persName>Dugumbe</persName>'s people after <w>finish- <lb break="no"/>ing</w> a piece of work = said he was tired
Example #3 (hyphen only in second line)
<lb/>sorely needed to be employed <w>him<supplied>-</supplied>  <lb break="no"/>-self</w> in something else than penny
Example #4 (hyphen in both lines)
<lb/>by which the irresponsible <w>con- <lb break="no"/>-clave</w> brought the Indian command

Definitions of the elements used above are:

11.6. More Than One Space between Words

If you are encoding text where the author has placed more than one space between words, do not insert additional space in your transcription. Rather insert only one space plus the following markup:
a <space extent="4unit="chars"/>word

In other words, in the example above the space being marked is actually five characters long. One of these spaces is marked in the normal fashion, the other four are marked with the <space> tag. Please follow this format when marking usual spacing between words.

The value for the extent attribute will of course be a bit of a judgment call, but a good rule of thumb is to mark only those spaces that extend for more than two characters and/or have some obvious, non-trivial significance in the text. For instance, Livingstone on occasion inserts an unusally large space just before a new sentence and indeed uses this space to indicate that the substance of the sentence that follows the space differs significantly from that of the sentence that precedes the space.

The value "chars" stands for "characters"; you can also use "words". There is a dim attribute on <space> with allowed values of horiztonal or vertical. The default assumption in LEAP is that extra space is horizontal so this does not need to be marked.

Definitions of the elements used above are:

11.7. One or More Spaces between Lines

If you are encoding text where the author has left extra spaces between lines, you can mark up the spaces in one of two ways:

If there is only one space between lines, only an extra <lb/> tag is needed:
<lb/><p>...and he arranges any <lb/>differences that may <lb/>arise -</p> <lb/> <lb/><p>Called at <persName>Mataka</persName>'s house ...</p>                         
If there is more than one space between lines, a <space/> tag is used, along with the dim, extent, and unit attributes and their appropriate values.
<lb/><p>...and he arranges any <lb/>differences that may <lb/>arise -</p> <lb/><space dim="verticalextent="3unit="lines"/> <lb/><p>Called at <persName>Mataka</persName>'s house ...</p>                         

Definitions of the elements used above are:

11.8. Dividing Lines Across the Page

Livingstone often uses lines that he draws across the page to separate sections of the text. Sometimes he uses a single line that runs across the entire page from left to right; sometimes a double-line; sometimes a single line that only runs across half or a quarter of the page. For all such lines, use the <milestone/> element in the following manner:

<lb/><milestone unit="sectionrend="line"/>

As in the example, <milestone/> should always inlcude a unit attribute with the value of "section" and a rend attribute. Possible values for the rend attribute include: "line", "double-line", "triple-line", "three-quarter-line", "half-line", "quarter-line", "dotted-line", and "dotted-double-line".

Definitions of the elements used above are:

11.9. Textual Directions

There are four possible situations we've encountered, so here's how to handle them:

  1. The page text is upside-down. If it is upside-down for only a phrase or a few lines, use <seg rend="upside-down"> or some other relevant element to contain the text. If it runs upside-down for a larger amount of text, create a new <div> and mark the orientation there: <div rend="upside-down">.
  2. The page text is horizontal, then it clearly continues to vertical text in the margin. Use <cb/> plus rend with a value of vertical in either one of the two following ways (line numbering continues in the normal way):
    1. If the vertical text in the margin is really a new paragraph then mark it as such by ending the current paragraph with </p> at the end of the horizontal text, then start the vertical text with <cb rend="vertical"/><p> and when you finish the vertical text close it with </p> as normal.
    2. If the vertical text in the margin continues the horizontal text without a paragraph break, do not end the paragraph but indicate the place where the text changes to vertical with a <cb rend="vertical"/> element. When the paragraph ends mark it with a closing </p>.
  3. The page text is horizontal, but ends at the bottom of the page. You believe that the vertical text continues from the horizontal text, but it seems to be a new "section" (how you define section is a bit subjective). Then close the horizontal text as normal with </p></div>. Begin the vertical text as a new division with <div rend="vertical"><p> then when it is finished close the vertical text with </p></div> and begin the next section with a new <div> tag. In other words, you're breaking this up into two sections (with one or more paragraphs inside) that you believe are continuous. Line numbering is continuous.
  4. The page text is horizontal and may or may not end at the bottom of the page. The vertical text has no clear relationship to the horizontal text. End the page text with </p> (whether or not it continues to the next page), then begin the vertical text with <cb rend="vertical"><ab> and close the vertical text with </ab>. Then on the next page, whether or not it's a new paragraph, begin with <p>, etc. Restart the line numbering in this new <ab>section.

Definitions of the elements used above are:

11.10. Text with No Clear Relationship to the Surrounding Text

Occasionally Livingstone includes blocks of text on a given manuscript page that have no clear relationship to the main text on that page. Such blocks should be encoded with the <ab> element.

<lb/><p> <!-- First line of main text --> <lb/> <!-- Second line of main text --> <lb/> <!-- Last line of main text, etc. --></p> <lb/><ab> <!-- First line of text with no clear relation to main text --> <lb/> <!-- Second line of text with no clear relation to main text, etc. --></ab>

Note that, as in the example above, you can use <p> or <ab> to enclose sections of text, but not both.

Definitions of the elements used above are:

11.11. Addition to or Deletions from the Original Manuscript

If a portion of the text has been added by the author or someone else other than you (see above), use <add> to mark up that text. The place attribute has values of: "inline", "above", "below", "marginleft", "marginright", "margintop", "marginbottom". Original text:
he saw us [in this case it's clear in the ms. that "saw" was added later]
Marked up:
he <add place="inline">saw</add> us
If a portion of the text has been deleted by the author or someone else, use <del> to mark up that text. Optinally, use the type attribute to indicate the type of deletion with values of "strikethrough" (deleted with a single line) or "cancelled" (deleted with multiple lines). Original text:
he saw us
Marked up:
<del type="strikethrough">he saw us</del>
If the deletion makes the character(s) or word(s) being deleted impossible to read, use the <gap> element to indicate this:
<del><gap extent="1unit="words"/></del>

Note: For coding additions and deletions that span more than a few lines of text, please consult the project team.

If it isn't a standalone addition or deletion but you believe a combined deletion and addition has been done (usually by the author) as a single intervention, then you may nest the <del> and <add> elements in a <subst> (substitution) element.
Then we went <subst><del>towards</del><add place="inline">to</add> the river</subst>
When Livingstone uses a caret (^) to indicate the place of an addition, use a separate <add> tag for the caret and place a space between the tagged caret and the additional text that Livingstone has added:
<add place="below">^</add> <add place="above">a word</add>
In both the cases of added or deleted text, if you believe that the work has been done by someone other than Livingstone but cannot identify who that person is, use the hand attribute with a value of "#U".
he <add place="inlinehand="#U">saw</add> us
If the other hand is writing in a different color to that used in the body of Livingstone's text, capture this using the rend attribute with the appropriate color as a value (see 11.4. Textual Colors):
<add place="inlinerend="grayhand="#U2">addition by an editor</add>
Deletions work in the same way:
<del type="cancelledrend="redhand="#U3">deletion by an editor</del>
The #U is a pointer to a <handNote> element (in a <handDesc> in a <physDesc> in the <msDesc> in the <sourceDesc> in the header).
<!-- in the <sourceDesc> in the header --> <physDesc>     <handDesc>         <handNote xml:id="U"><label>Unknown Hand</label> This hand is unknown             but thought not David Livingstone's.</handNote>     </handDesc> </physDesc> <!-- later in the text --> <lb/>he <add place="inlinehand="#U">saw</add> us

If you can identify individual hands, but not to whom they belong, these values could be #hand01 or #hand02 or similar.

Finally, to denote any kind of arrow or other mark (other than a caret) that Livingstone uses to indicate where a bit of add or deleted text should go, use an empty <metamark/> element.
Then we went towards <metamark/><add place="inline">home</add>. <!-- Livingstone writes "home" in the margin, then uses a long arrow to indicate it should be placed here. AW -->

Note: The Missionary Travels team is also working with more specialized metamarks. For guidance on using these, see 24.4. Metamarks. This additional coding is not required in other parts of the project, so should only be done in consultation with the project team.

Definitions of the elements used above are:

11.12. Additions or Deletions that Span More Than One Paragraph

For additions or deletions that span more than one paragraph (<p>) or section of text (<ab>), use the <addSpan/> or <delSpan/> elements combined with the <anchor/> element.

The <addSpan/>, <delSpan/>, and <anchor/> elements can appear anywhere in a <div>, including outside or inside a <p> or <ab>. As a result, they can be used to mark precisely where a longer addition or deletion begins and ends without regard to other coding.

Use these tags as follows. First, place a <addSpan/> or <delSpan/> element where the given addition or deletion begins and include an spanTo attribute with the value preceded by "#" [number sign]:
<addSpan spanTo="#longadd-1"/>
or
<delSpan spanTo="#del-1"/>
Then, wherever the addition or deletion ends, place an <anchor/> with an xml:id attribute. The value of the xml:id will correspond to the spanTo value, but will not include the "#" [number sign]:
<anchor xml:id="longadd-1"/>
or
<anchor xml:id="del-1"/>

Note: In the above examples the values "longadd-1" and "del-1" are arbitrary. The value, however, must be the same for the <addSpan/> and its corresponding <anchor/> tag, or for <delSpan/> and its corresponding <anchor/> tag. The given value should not otherwise be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive these values for each instance of <addSpan/> or <delSpan/> in order to avoid repetition.

Also note: You may place the hand and rend attributes on the <addSpan/> or <delSpan/> to indicate, respectively, the individual who made the addition or deletion, or other characteristics of the addition or deletion:
<lb/><delSpan spanTo="#del-2rend="grayhand="#U2"/>lengthy passage written by Livingstone <lb/>but deleted by unknown hand #2 in pencil<anchor xml:id="del-2"/>

Also note: If the given addition or deletion spans less than one paragraph, then use the <add> or <del> tags (see 11.11. Addition to or Deletions from the Original Manuscript).

Definitions of the elements used above are:

11.13. Standalone Additions to the Main Text

On a number of occasions, Livingstone or someone else places an addition elsewhere other than in the immediate area where it should be added (for instance on another page). The place for insertion is often indicated by an arrow that runs from the addition to its intended position. Code such additions as follows.

First, code the addition in the place where it actually appears on the page.

If the addition is on an otherwise blank page, this will involve indicating that there are empty lines that precede the addition. For this, use the <space/> tag (see 11.7. One or More Spaces between Lines):
<space dim="verticalextent="10unit="lines"/>
Then transcribe the addition as normal, being sure to wrap it in the <add> tag. You should also use the attribute corresp on the <add> tag which will link the addition to the place in the text where it is to be inserted:
<add place="inlinecorresp="#add-1">a portion of text on a page of its own that DL wants to insert elsewhere</add>

(Notice that the value for corresp is preceded by a "#" [number sign].)

Finally, on the page where the addition should be inserted, indicate the specific place for the insertion by using the <anchor/> tag with an attribute xml:id. Be sure to leave a space before and after this tag:
<anchor xml:id="add-1"/>

(Notice that the value of the attribute xml:id is the same as on the corresp above, but now is not preceded by a "#" [number sign].)

Note: In the above example the value of "add-1" is arbitrary. The value must be the same for the relevant attributes on the <add> and <anchor/> tags, but should also not be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive this value for each such addition in order to avoid repetition.

Also note: The above method can be used to insert longer additions that span several paragraphs by replacing <add> with <addSpan/>. (For guidance on <addSpan> see 11.12. Additions or Deletions that Span More Than One Paragraph).

However, to use <addSpan/> to encode a standalone addition, two <anchor/> tags will be required – one in conjunction with <addSpan/> to record the extent of the addition (i.e., its beginning and end), the other to mark the place the addition is intended to be inserted. The <addSpan/> should thus have both the spanTo and corresp attributes.

For example:
<lb/><addSpan spanTo="#longadd-1corresp="#add-17"/><p>a long addition <lb/>going over multiple paragraphs</p> <lb/><p>to be inserted on another page.</p><anchor xml:id="longadd-1"/>                                  <pb facs="liv_000099_0376.jpgn="0376"/> <lb/><p>Text from Livingstone that does not  <lb/>continue from the previous page <anchor xml:id="add-17"/> <lb/>more text</p>

In the example above, the first <anchor/> tag thus indicates where the addition ends; the second <anchor/> tag indicates where Livingstone wants the addition inserted.

Note: In the above example, the value "longadd-1" on spanTo is arbitrary. The value must be the same for the corresponding <addSpan/> and <anchor/> tags but should also not be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive this value for each instance of <addSpan/> in order to avoid repetition.

Definitions of the elements used above are:

11.14. Text Written Over Other Text

Livingstone often deletes a character or word by writing another character or word over it. For such instances use the following coding formula:
He <subst><del>gave</del><add place="over-text">handed</add></subst> it to me.
If such a substitution occurs in the middle of a word, you may use <w> to avoid confusion by indicating the beginning and end of the full word:
He <w>g<subst><del>i</del><add place="over-text">a</add></subst>ve</w> it to me.
If someone else (for instance, the editor in Missionary Travels) intervenes by writing directly over one of Livingstone’s words or characters with a different word or symbol, code as follows.
<subst><del hand="#U2">no</del><add place="over-textrend="grayhand="#U2">any</add></subst>

In the example above, unknown hand #2 writes the word "any" over Livingstone’s word "no." The mark up shows that Livingstone’s initial word has been replaced (and hence deleted) by overwriting.

Sometimes Livingstone writes over a word suggested by another individual with a different character or word in order to delete or change the suggested character or word. We thus have an addition by someone else that is replaced by Livingstone's overwriting. This is encoded similarly to the previous examples, while also showing that the initial word was added by another hand:
<add place="marginleftrend="grayhand="#U2"><subst><del hand="#DL">editor's  word</del><add place="over-texthand="#DL">Livingstone’s correction</add></subst></add>
If Livingstone writes over a word or a symbol suggested by someone else in order to confirm it (i.e., Livingstone writes the same word or symbol), code Livingstone’s addition using the <retrace> element:
<retrace hand="#DL"><add place="belowrend="redhand="#U3">^</add>  <add place="aboverend="redhand="#U3">him from</add></retrace>

The <retrace> element specifies that it is Livingstone’s hand doing the retracing.

Finally, sometimes Livingstone deletes a word that has already been deleted by someone else. In other words, he confirms the deletion. To encode this form of overwriting, code the word as a double deletion by enclosing it within two <del> elements:
<del type="cancelledhand="#DL"><del type="cancelledhand="#U2">You</del></del>

In the example above, the word "You" has been deleted by someone else and then also deleted by Livingstone.

Definitions of the elements used above are:

11.15. Authorial Notes within the Text

Use the <note> element anytime Livingstone himself inserts a note, gloss, or footnote outside the body of the main text that explains an item within the main text.
the whole tribe x  <add place="marginleft"><note>if it were necessary for me  to seek a character I would confidently refer to the  <term type="tribe">Bakwains</term> for it</note></add>
The <note> element combined place and the "marginleft" value should also be used to mark the dates that Livingstone periodically adds to the left margin of the Unyanyembe Journal. These should be marked as they occur, even if that happens in the middle of a sentence:
<lb/>I was content <lb/><note place="marginleft"><date when="1871-05-08">8th</date></note> to take the canoe on any terms -

If the date added to the left margin spans more than one line, use <lb/> as appropriate (see 7. The Beginning of a Manuscript Line):

<lb/><note place="marginleft"><date when="1866-04-13">13<hi rend="sup underline">th</hi>  April <lb/>1866</date></note> alone but other nations feel

Definitions of the elements used above are:

12. Recording Editorial Interventions

12.1. Authorial Punctuation and Capitalization

Livingstone limits his punctuation primarily to n-dashes (-), which often shade into m-dashes or even longer dashes, and equal signs (=). He distinctly prefers n-dashes, but he uses these interchangeably with equal signs in places of such punctuation as commas, colons, semicolons, and periods as well as to mark simple pauses in the text. When transcribing an n-dash or equal sign, please adhere to the following guidelines.

When Livingstone uses an n-dash for any reason other than hyphenation of a word, place a space before and after the n-dash when trascribing it, even if it looks like Livingstone himself hasn't:

a very old town - country

Likewise, when transcribing an equal sign that Livingstone has used as punctuation, place a space before and after, even if it looks like Livingstone himself hasn't:

tea = coffee

When Livingstone uses an n-dash to introduce or follow a quotation, he places the n-dash directly below the opening or closing quotation marks rather than next to them. However, when transcribing this, you should nonetheless put a space between the dash and the quotation mark:

He said - "I will" - in answer to me.

If unsure, whether Livingstone is using a period or dash, select dash by default.

If Livingstone's n-dash looks like an m-dask or even longer, use two or more n-dashes without any space between them:

poor -- mostly

Livingstone also has a tendency to run the first person pronoun ("I") onto the following word, as in the following: "Iwent". All instances of this should be silently separated when transcribed:

I went

Livingstone is by no means consistent in his use of capitalization and, moreover, it is often even not clear whether a word is capitalized or not. When transcribing, use the following rules of thumb. When a word is capitalized (or not) and the context suggests this is correct, transcribe as is. When a word is capitalized (or not) and the context suggests this is incorrect, transcribe as is but if (in your opinion) it is very important that the capitalization be corrected, use <choice> plus <sic> and <corr> to provide a corrected verison of the word:

The man spoke to me - <choice><sic>then</sic><corr>Then</corr></choice> he left.

For use of the <choice>, <sic>, and <corr> elements, see 12.2. Authorial Grammatical, Typographical, and Other Mistakes.

Finally, if it is not clear whether a word is capitalized and it would therefore be OK to transcribe it either way, allow context to guide your decision as to whether to capialize it or not.

12.2. Authorial Grammatical, Typographical, and Other Mistakes

When you encounter some sort of textual mistake made by the author, mark it with a combination of the <choice> element and both the <sic> (apparent error) and <corr> (correction) elements. Original text:
I recieved your letter
Marked up:
<choice><sic>recieved</sic><corr>received</corr></choice> your letter
If there is an uncertainty as to the correction that you provide use the cert attribute with values of "low", "medium", "high" to denote the degree of confidence in the addition you have made:
<choice><sic>recieved</sic><corr cert="high">received</corr></choice>
If a duplicate word appears in the text, use the <choice>, <sic>, and <corr> elements to remove it:
till the <choice><sic>the</sic><corr/></choice> astringent poison
Note: Livingstone tends to leave off apostrophes for contractions and possessives. To mark such instances in the text, do not use <supplied> plus an apostrophe, but rather code with <choice> plus <sic> and <corr>:
<choice><sic>dont</sic><corr>don't</corr></choice>

Important Note: Be sure to remember that there is a difference between errors and variants. If Livingstone makes an obvious error, then use <choice>, <sic>, and <corr>, as described above. However, if Livingstone uses a variant that would not have been incorrect in his own day (e.g., Mosambique) and/or that exists in a more common, alternative form now (Mozambique), use <choice>, <orig>, and <reg> to normalize this (see 12.7. Normalized Text).

Definitions of the elements used above are:

12.3. Text that is Not Clear

Use <unclear> to mark up any text that is not clear; furthermore, use the cert attribute with values of "low", "medium", or "high" to denote the degree of confidence in the transcription you have made:
he said he would <unclear cert="low">say</unclear> me tomorrow

Definitions of the elements used above are:

12.4. Variant Readings

Use the <app> element plus at least two or more instances of the <rdg> element to mark valid alternate readings of a single word or textual passage. If needed, cert may be used with values of "low", "medium", "high" to denote the degree of confidence in a given reading.
<app><rdg cert="high">will</rdg><rdg>well</rdg></app>

Definitions of the elements used above are:

12.5. Missing Portions of the Manuscript Page or Text that is Illegible

We use <gap> to tag text that is wholly illegible due to deletion or some other factor, or missing all together from the manuscript page due to physical damage. The <gap> element never contains text:
<lb/><gap extent="6unit="charsagent="blot"/> sugar -- candles

In the <gap> element, the values we use for the agent attribute include: "blot", "fading", "hole", "illegible", "overwriting", and "stain".

The value of the extent attribute is always an approximation.

Note: For coding manuscript damage that spans more than a few lines of text, please consult the project team.

Definitions of the elements used above are:

12.6. Portion of the Text that You Have Supplied

If a portion of the original text is missing for whatever reason and you supply it, use <supplied> to mark up this addition; furthermore, use the cert with values of "low", "medium", "high" to denote the degree of confidence in the addition you have made:

Original text:
He saw man
Marked up:
he saw <supplied cert="high">the</supplied> man

Important Note: You should be very conservative in your use of the <supplied> tag and only supply text of which you are 100% certain. Otherwise, use <gap/>. In other words, avoid guessing at Livingstone's meaning unnecessarily.

Note: The <supplied> tag is never nested in the <gap> tag.
he saw <gap agent="damageextent="3unit="letters"/><supplied cert="high">the</supplied> man

Definitions of the elements used above are:

12.7. Normalized Text

Use the <choice> element plus <orig> and <reg> to mark any instances where Livingstone's text, although not incorrect necessarily, is nonetheless normalized or otherwise corrected by you.
<choice><orig>shew</orig><reg>show</reg></choice>
Note: this also includes the normalization of proper nouns:
The <term type="tribe"><choice><orig>Suaheli</orig><reg>Swahili</reg></choice></term>
The <placeName><geogName type="river"><choice><orig>Chambeze</orig><reg>Chambezi</reg></choice></geogName></placeName>

Definitions of the elements used above are:

13. Project-Specific Formatting Practices

13.1. The Ampersand and Other Special Characters

When you transcribe an ampersand, use &amp; instead of an actual ampersand: Original text:
I saw John & Jim
Marked up:
I saw John &amp;amp; Jim
If you come across any other unusual characters that are not found within the "Insert from Character Map" option from the "Edit" dropdown menu in oXygen, add a comment to draw the attention of the project to this.
<!-- Adrian, there is a weird character you need to insert here. DH -->

13.2. Quotation from Another Source

When dealing with a quotation from another source, usually a printed source (which may or may not be explicitly identified in Livingstone's text), use the <quote> element.
As it is stated in the Bible, "<quote>Neither do men light a candle, and put it under a bushel...</quote>."
Note: As in the example above, the <quote> element goes inside of the quotation marks that surround the given quotation. In other words, do not mark the quotation marks as part of the quotation.

Definitions of the elements used above are:

13.3. Abbreviations

When you encounter an abbreviation made by the author, mark it with the <choice> element and both the <abbr> (abbreviation) and <expan> (expansion) elements. Original text:
my no. 1 friend
Marked up:
my <choice><abbr>no.</abbr><expan>number</expan></choice> 1 friend
If there is an uncertainty as to the expansion that you provide, use the cert attribute with values of "low", "medium", "high" to denote the degree of confidence in the expansion you have provided.
my <choice><abbr>no.</abbr><expan cert="high">number</expan></choice>

Please note: any prefix pertaining to a personal name, i.e. Dr, Mr, Miss, Rev, need not be expanded.

Definitions of the elements used above are:

13.4. Fractions

We use <choice> and the <orig> and <reg> elements to encode fractions:
<choice><orig>½</orig><reg>1/2</reg></choice>

Definitions of the elements used above are:

14. Names of People

When marking up a person's name, use the <persName> element.
I saw <persName>David Livingstone</persName>
However, note the following example:
I saw <persName>Dr David Livingstone</persName>'s tent

Please note: any prefix pertaining to a personal name, i.e. Dr, Mr, Miss, Rev, should be included within the <persName> element but and does not need to be expanded. Likewise any possessive marker ('s) can be outside the <persName>.

Definitions of the elements used above are:

15. Place Names and Geographical Elements

When you mark up a geographical element, use the <placeName> element and one of the following: <bloc> (for multi-national entities like 'Africa'), <country> (for countries), <region> (for large administrative units), or <settlement> (for cities, towns, villages). On <settlement> use the type attribute to record values such as "city", "town", or "village".
<placeName><settlement type="village">Nyangwe</settlement></placeName>
Use <geogName> to denote a specific named geographical entity not covered by the above, using the type attribute with values such as "lake", "river", etc.
<placeName><geogName type="river">Nile</geogName></placeName>

Note: Livingstone uses distinct abbreviations to denote "river" and "rivulet." He abbreviates "river" as either "R." or "R", while he abbreviates "rivulet" as "Rt" or "Rt". In the latter case, the superscript "t" may resemble a superscript "r" but should nonetheless be treated as a "t". Code these abbreviations as follows:

the <placeName><geogName type="river">Lualaba <choice><abbr>R.</abbr> <expan>River</expan></choice></geogName></placeName>
the <placeName><geogName type="rivulet">Lipande <choice><abbr>R<hi rend="sup">t</hi></abbr> <expan>Rivulet</expan></choice></geogName></placeName>

You should also use <geogName> when encoding the full reference to a geographical entity that includes any kind of formal name (which itself would also be separately encoded:

<placeName><geogName type="source">sources of the <placeName><geogName type="river">Nile</geogName></placeName></geogName></placeName>

If Livingstone refers to a specific, named geographical entity (and you know what that entity is), but uses only a generic term such as "the Lake" or "the River," you should identify this entity in a comment that directly follows the relevant term, but not otherwise mark the term used:

I saw the Lake. <!-- geog: Tanganyika -->

Note: Livingstone uses "Metamba" to reference the Central African rainforest, although the term is really a local word for "forest." To account for this usage, please code as follows:

<foreign xml:lang="und"><placeName><region><geogName type="forest">Metamba</geogName></region></placeName></foreign>

Note: "Cape" and "Interior" should be coded with the <region> element (even though technically incorrect). Code "Zanzibar" as follows:

<placeName><geogName type="island">Zanzibar</geogName></placeName>

Directional words (North, South, East, and West) should not be tagged when referring to directions. Rather tag directional words only when Livingstone uses them to designate a region:

<placeName><region>South of <placeName><geogName type="lake">Lake Nyassa</geogName></placeName></region></placeName>

Definitions of the elements used above are:

15.1. Geographical Measurements

Use the <measure> element to mark any geographical quantities (including geographical coordinates) that Livingstone cites in the text. This includes distances measured in days or hours as well (most often used in reference to the party's marches).
The village was <measure>a few days' march</measure> from here
If Livingstone provides an obvious group of geographical quantities, an additional <measure> element should be used to encapsulate the group.
The river was <measure><measure>30 feet deep</measure>  and <measure>1000 yards across</measure></measure>

Note: If Livingstone introduces a larger set of geographical coordinates, these should normally not be transcribed, but rather be noted with the <figure> and <figDes> elements. See 22. Figures, Drawings, and Calculations.

Definitions of the elements used above are:

16. References to Weather

Use <seg type="weather"> to mark passages in the text where Livingstone refers to the weather.

We have <seg type="weather">rain in large quantity almost every night</seg>

Such weather references may be loosely made, and it may be difficult to determine where exactly they begin and end. In all cases use the <seg> elment and best judgment to mark such references. Opt for one use of <seg> to mark a longer passage with a series of specific descriptions rather than multiple uses of the <seg> element.

Note: When Livingstone provides the outside temperature, this should be be coded with only <seg type="weather">, and not the <measure> element.

6 AM <seg type="weather">98°</seg>

Definitions of the elements used above are:

17. Terms to Mark

17.1. Animals (Including Fish), Insects, Plants, and Foodstuffs

When dealing with animals, including fish, use the <term> element with the type attribute with a value of "animal". The value of "animal" in the singular should be used in all cases, even when the text refers to multiple animals of one kind. Livingstone's uses of general terms such as "animal" or "beast" need not be tagged.
<term type="animal">elephants</term>
When dealing with insects, use the <term> element with the type attribute with a value of "insect". The value of "insect" in the singular should be used in all cases, even when the text refers to multiple insects of one kind. Livingstone's uses of general terms such as "insects" or "bugs" need not be tagged.
<term type="insect">tetse</term>
When dealing with specifically named plants, use the <term> element with the type attribute with a value of "plant". The value of "plant" in the singular should be used in all cases, even when the text refers to multiple plants of one kind. Livingstone's uses of general terms such as "trees," "bushes," or "grass" need not be tagged.
<term type="plant">Euphorbias</term>
When dealing with foodstuffs, use the <term> element with the type attribute with a value of "foodstuff". The value of "foodstuff" in the singular should be used in all cases. Livingstone's uses of general terms such as "food" need not be tagged.
<term type="foodstuff">bread</term>
If Livingstone refers to a foodstuff that is also a plant, use the <term> element with the type attribute with the value of "plant_foodstuff" (in that order):
<term type="plant_foodstuff">maize</term>
This format should be used regardless of the state in which the given item appears in the text.
<term type="plant_foodstuff">coffee</term>
If Livingstone refers to an animal that, in context, is also a foodstuff, code as follows using two <term> elements:
<term type="animal"><term tag="foodstuff">goat</term></term>
Beverages, both alcoholic and non-alcoholic, should be coded as foodstuff and follow previously stated formats.
<term type="foodstuff">brandy</term>

Note: Terms relating to meals (such as breakfast, lunch, supper) should not be coded as "foodstuff."

Definitions of the elements used above are:

17.2. Nationalities

When dealing with nationalities used adjectivally, use the <term> element with the type attribute with a value of "nationality".
the <term type="nationality">English</term> settlements

Definitions of the elements used above are:

17.3. People of a Given Nationality

When dealing with people of a given nationality (e.g., Englishmen, Americans), use the <term> element with the type attribute with a value of "people".
<term type="people">Englishmen</term>
If the reference is to just one person of a nationality (e.g., a Englishman, American), use the <term> element with the type attribute with a value of "person".
<term type="person">Englishman</term>

Definitions of the elements used above are:

17.4. African Tribes

When marking up an African tribal name, use the <term> element with the type attribute with a value of "tribe".
I saw the <term type="tribe">Nyamwezi</term>

Definitions of the elements used above are:

17.5. Religious Faith

Use the <term> element with a type attribute with a value of "faith" to mark instances in the text where religious faith or an organized religion is cited.
<term type="faith">Christianity</term> and <term type="faith">Islam</term>
<term type="faith">Christian</term> values

However, for practitioners of particular faiths, see 18. Organizations and Other Groups.

Definitions of the elements used above are:

17.6. Occupation

Use the <term> element with a type attribute with a value of "occupation" anytime an occupation of any sort is mentioned in the text.
Livingstone was a <term type="occupation">missionary</term><term type="occupation">geographer</term>, and <term type="occupation">abolitionist</term> 

Note: In Missionary Travels, the following terms and any variations thereof should be marked up as "occupation": chief, chieftain, and rain doctor.

Definitions of the elements used above are:

17.7. Medical Terms

When marking up a medical reference or term, use <term> plus the type attribute and appropriate value, such as "ailment" or medicament".
I had <term type="ailment">malaria</term> for a month.

Definitions of the elements used above are:

18. Organizations and Other Groups

Use the <orgName> element to mark instances in the text where there is mention of an organization or other type of group (or any reference to an individual as being part of a group) that is not covered by 17.2. Nationalities, 17.3. People of a Given Nationality, or 17.4. African Tribes. Note that all the following entities should be marked with the <orgName> element: Aborigine, Aborigines, African, Africans, Arab, Arabs, Banian, Banians, Boer, Boers, Bushman, Bushmen, Caffre (or the variant spellings, Kaffre and Kaffir), Caffres (or the variant spellings, Kaffres and Kaffirs), Christian (an individual; for use of Christian as an adjective, see 17.5. Religious Faith), Christians, European, Europeans, Griqua, Moslem (an individual; for use of Moslem as an adjective, see 17.5. Religious Faith), and Moslems. For references to organized religions (e.g., Christianity, Islam), see 17.5. Religious Faith.

the <orgName>the London Missionary Society</orgName>
<orgName>African</orgName> villages
I spoke with the <orgName>Arab</orgName>

"Johanna men" and "Nassick boys" (and all variants of these two groups) to be coded as follows:

<orgName><placeName><geogName type="island">Johanna</geogName></placeName> men</orgName>
<orgName><placeName><settlement type="city">Nassick</settlement></placeName> boys</orgName>

Note: All references to "slaves" and "slavery" should also be marked with <orgName> as should references to "caste," "freemen," "free men," "natives," "cannibals," and "flesh eaters":

He had two <orgName>slaves</orgName> and spoke of <orgName>slavery</orgName>
It is believed by the <orgName>natives</orgName>.

Please note: Havildar and Sepoy (singular and plural) should be marked with both <orgName>, and <term> with the type attribute and a value of "occupation":

<orgName><term type="occupation">Havildar</term></orgName>
<orgName><term type="occupation">Sepoys</term></orgName>

Groups relating to a specific person should also be marked with <orgName>:

<lb/><orgName><persName>Emboro</persName>'s men</orgName>
<lb/>from depositions of survivors of <orgName><persName>Baron</persName>'s party</orgName>                 

Definitions of the elements used above are:

18.1. Additional Notes on Coding Organizations

In some cases, one or more entities encoded with the <orgName> or <term type="occupation"> tags may themselves, in combination, constitute a larger organization or group. In such cases, nestle the individual entities within one additonal <orgName> as follows:

An <orgName><orgName>Arab</orgName> <term type="occupation">trader</term></orgName>.
<orgName><term type="nationality">Portuguese</term> <term type="occupation">sailor</term></orgName>.

In the above examples, "Arab" and "trader" (first example) and "Portuguese" and "sailor" (second example) are coded per normal practice, but are also collectively encapsulated, in each case, in an additional <orgName> tag.

Note: All variants of "slave trader" should be coded in the following unique manner:

<orgName><term type="occupation"><orgName>slave</orgName> trader</term></orgName>

In other words code "slave" with <orgName> per usual practice. Then code the whole phrase "slave trader" as a <term type="occupation">. Finally, wrap the fully coded phrase "slave trader" in an additional <orgName> tag.

Definitions of the elements used above are:

19. Bibliographical Elements

Use <bibl> to encode any elements of a book, including the title, that Livingstone references:

<bibl>Genesis</bibl>
Also use <bibl> to encode any mention of letters or manuscripts, including Livingstone's own:
<lb/><bibl>Letters from <placeName><settlement type="city">Mecca</settlement></placeName></bibl> told of its coming
or
<lb/>he assures me that my <bibl>packet of letters</bibl> was not destroyed

Definitions of the elements used above are:

20. Words in a Foreign Language

When dealing with foreign words, there are three steps to complete:

  1. Find the abbreviation for the foreign language at the following webpage: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
  2. In the header, add in a <langUsage> for the foreign language under the one for English as follows. Put English first, then all other languages in alphabetical order:
    <langUsage>  <language ident="en">English</language>  <language ident="la">Latin</language> </langUsage>
  3. Within the text, when the language comes up, you code the word/phrase as follows:
    <foreign xml:lang="la">et id genus omne</foreign>
    Please note: The <foreign> tag should go outside of any other tags used relating to the word or phrase:
    <foreign xml:lang="nym">  <term type="occupation">Pagazi</term> </foreign>

Please note: If you are unsure of the language/dialect, but know that it is not English, simply mark it as "Undetermined" using the code "und". Also, we do not tag references to languages (Spanish, French, etc.) in any way.

Definitions of the elements used above are:

21. Using Lists and Tables

Use the <list> element to contain any lists that appear in the text. The title of any such list should be marked with the <head> element, while <item> should be used for each item within the list:
<list><head>Villages:</head> <item>Bambarre,</item> <item>Nyangwe,</item> <item>Ujiji</item></list>
Lists may also be broken up with line breaks (<lb/>)as needed:
<list><head>Villages</head>  <lb/><item>Bambarre</item> <lb/><item>Nyangwe</item> <lb/><item>Ujiji</item></list>
Livingstone's texts sometimes also contain tables or have information laid out in a such a way that the table format seems appropriate. Code tables and similar text (as seems appropriate -- such use may be subjective) with the <table> tag plus the <head> (for any title that the table may have), <row>, and <cell> tags.
<table><head>Villages</head>  <lb/><row><cell>Bambarre</cell> <cell>West of Lake Tanganyika</cell></row> <lb/><row><cell>Nyangwe</cell> <cell>West of Lake Tanganyika</cell></row> <lb/><row><cell>Ujiji</cell> <cell>East of Lake Tanganyika</cell></row></table>
Note: Headings, lists, items, tables, rows, and cells may all be assigned various attributes and values as relevant, as in the following example where color is marked, rows are numbered, and cells are coded for placement on the page:
<table rend="blue"><head rend="black">Villages</head>  <lb/><row n="1"><cell rend="left">Bambarre</cell> <cell rend="right">West of Lake Tanganyika</cell></row> <lb/><row n="2"><cell rend="left">Nyangwe</cell> <cell rend="right">West of Lake Tanganyika</cell></row> <lb/><row n="3"><cell rend="left">Ujiji</cell> <cell rend="right">East of Lake Tanganyika</cell></row></table>
Note on all the above: Normally, in the examples above, the various settlements, regions, and geographical entities would be coded as per the instructions set out elsewhere in this manual. However, such coding has here been omitted for the sake of simplicity and clarity in the examples given. Additionally, in the last example, the numbering of rows is done only for illustrative purposes. Such numbering is optional and should normally not be undertaken.

Definitions of the elements used above are:

22. Figures, Drawings, and Calculations

If you come across any figures, drawings, or calculations, please mark them with an empty <figure/> element. However, you can also describe them using the <figDesc> element, which must then be contained by the <figure> element.
The <term type="animal">lion</term> looked like this: <figure/>
The <term type="animal">lion</term> looked like this: <figure>  <figDesc>Drawing of a lion with it's mouth open towards the viewer.</figDesc> </figure>
The description of the figure should be short and to the point, as in the example above. In the description, you should not as a rule describe the extent of the figure (i.e, "for three lines," etc.), but rather should focus only on its content. Also, assume that phrases like "Livingstone has here..." are a given and do not need to be used explicitly.
If Livingstone has himself given the figure a title, use the <head> element to record this:
The <term type="animal">lion</term> looked like this: <figure>  <head>Lion</head>  <figDesc>Drawing of a lion with it's mouth open towards the viewer.</figDesc> </figure>
If your description of the figure cites any text that Livingstone himself has provided and that text in turn can be coded, then it should be coded directly in the citation:
The <term type="animal">lion</term> looked like this: <figure>  <head>Lion</head>  <figDesc>Drawing of a lion with it's mouth open    towards the viewer, with a note from Livingstone that he saw this lion "in the <placeName>    <geogName type="desert">Kalahari</geogName>   </placeName>."</figDesc> </figure>

Definitions of the elements used above are:

23. Anything Unusual in the Text

If you come across anything unusal in the text that cannot be otherwise encoded, please do not mark it other than leaving a comment to alert the project team.
<!-- Adrian: There's a drawing or something strange here. DH -->

24. Missionary Travels Specific Practices

24.1. Page Numbers

In the manuscript of Missionary Travels, page numbers generally appear in the running header in the top margin and so should appear in the <fw> element. The <add> elements plus the place attribute is used to show that they appear in the "margintop". Since the numbers have been added later by an editor or group of editors hand is also required. To indicate the colour and their position within the margintop, use rend. For example:
<lb/><fw><add place="margintophand="#U1rend="gray right">5</add></fw>
If there are two sets of numbers, as often happens, encode them as follows:
<lb/><fw><add place="margintophand="#U1rend="gray right">26</add>  <add place="margintophand="#U1rend="gray right">29</add></fw>

The above example indicates that "26" and "29" appear sequentially, left to right and separated by a space, in the right-hand corner of the top margin of the given page.

Note: While the various sets of numbers may be added by different hands there is little to be gained by differentiating them. Indeed, it’s quite likely that they’re actually the same hand – sometimes it’s difficult to distinguish between them. So on the assumption that it’s one hand adding the numbers, but perhaps at different times, we consider them to be two separate additions.

Also note: While "gray right" is often the right value to use on rend, "gray left" and "gray center" will also be required on occasion.

Also note: Occasionally one set of page numbers appears below the other. In such cases, use a second place value to indicate this, as follows:
<fw><add place="margintophand="#U1rend="gray right">58</add>  <add place="margintop belowhand="#U1rend="gray right">80</add></fw>

Definitions of the elements used above are:

24.2. Page Layout

In Missionary Travels, the majority of text is rendered to the right of the page in order to leave room for marginal comments on the left. Accordingly, the value "right" is used on rend in the <body> element at the beginning of the transcription i.e. <body rend="right">.

Encode any departure from this norm. To do so, use <seg> with the rend attribute. For example, when Livingstone writes across the full width of the page, departing from his usual practice of writing on the right hand side, mark it up as follows:
<lb/><seg rend="left">portion of text written across the full width of the page</seg> <lb/>return to normal text

Please also include a comment in such places, noting that Livingstone has departed from his norm by writing a portion of text across the full width of the page.

Definitions of the elements used above are:

24.3. Textual Formatting in Another Hand

In Missionary Travels the various editors occasionally format portions of Livingstone's text. For instance, unknown hand#2 might underline one of Livingstone's words in pencil. Record such occurrences using the resp (responsibility) attribute on the <hi> tag. Use the rend attribute per usual practice, as necessary, to record other characteristics of the formatting.

For example:
<hi rend="gray underlineresp="#U2">some words of Livingstone's underlined in gray by unknown hand #2</hi>

Note: The <hi> element doesn’t accept hand, so we indicate authorial responsibility using resp, as in the example above.

Also note: If both Livingstone and an editor format the same portion of text, use two separate <hi> tags to distinguish between the hands:
<hi rend="gray underlineresp="#U2"><hi rend="underlineresp="#DL">rain making</hi></hi>

Definitions of the elements used above are:

24.4. Metamarks

  1. Long Arrows

    Carets that appear on their own are encoded as follows:
    <add place="below">^</add>

    But when there appears to be a caret with a long line following it, we should just treat this as an arrow and therefore encode it with the <metamark/> tag. In other words, in such a case we shouldn’t mark up the caret and arrow separately.

    For such arrows: Use the <add> element since most of them are clearly added later in order to point to an additional piece of text.

    Also include function on the <metamark/> to indicate the purpose of the metamark. Arrows will be marked up with the function "insertion".

    For the most part, these arrows go all the way from a point in the body of the text to a portion of additional text in the margin. We'll consider the arrow, along with the additional text, to be added in the "marginleft" (or "margintop", "marginbottom", etc. as appropriate). The <metamark/> is thus included as part of the same addition as the portion of text in the margin. Accordingly, long arrows will generally be encoded as follows:
    <add place="marginleft"><metamark function="insertion"/>rest of Livingstone's text in the margin</add>

    Note: Long arrows leading to a portion of text are generally the only metamarks (aside from carets) that should be nested in an <add> tag. See further details below.

    Definitions of the elements used above are:

    • add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.
    • metamark contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document.
      functiondescribes the function (for example status, insertion, deletion, transposition) of the mark.
  2. Other Metamarks

    Where possible, record the purpose of a particular metamark by using the function attribute with any of the following values: "insertion", "deletion", "reorder", "newParagraph", "let-stand", or "query":

    • "insertion": Use this for arrows intended to indicate an addition included in the margin or elsewhere.
    • "deletion": Use this for the proof correction mark for delete (used by unknown hand #2), and editorial pencil marks/boxes that are intended to indicate a deletion.
    • "reorder": This should be used when a line or mark is included to indicate that a portion of text should be moved to another place. (Also see Note on "reorder" below.)
    • "newParagraph": Use this for signs that are intended to indicate that a new paragraph should be taken. For the most part we’ll use this when Livingstone or an editor uses "/" and "//".
    • "let-stand": Use this when Livingstone or the editor underlines a word with a dotted line. This is the proof correction mark for "let stand," indicating that a word marked for deletion should instead be retained.
    • "query": Use this for any mark used to query a word or portion of text. For example, a circle or square drawn around a word in order to draw attention to it.

    For metamarks not covered by the above, only record the presence of the <metamark/> along with a note that the metamark should be reviewed.

    Sometimes, a closed metamark will be sufficient:
    <metamark function="insertion"/>

    However, if a metamark encloses text (for example, a square or circle is drawn around a word, or a long line in the margin brackets a portion of text), encode the extent of the metamark by using the spanTo attribute and the <anchor/> tag, as per the following instructions.

    At the beginning of a portion of text surrounded by a metamark, encode as normal, marking the function, but now including the spanTo attribute as well.
    <metamark function="queryspanTo="#meta-1"/>

    (Notice that the value for spanTo is preceded by a "#" [number sign].)

    Next, indicate the place that the metamark ends by using the <anchor/> tag with an attribute of xml:id. The <anchor/> tag simply marks a spot, and in this case indicates the endpoint of the metamark:
    <anchor xml:id="meta-1"/>

    (Notice that the value of the attribute xml:id is the same as on the spanTo above, but now is not preceded by a "#" [number sign].)

    For example:
    <metamark function="queryspanTo="#meta-1"/>Livingstone's text, enclosed in a circle<anchor xml:id="meta-1"/>
    Please also add a comment describing the metamark:
    <!-- Livingstone has drawn a circle around the word "and." JL -->

    In the above example, the value of "meta-1" is arbitrary. The value must be the same for spanTo on the <metamark/> tag and xml:id on the <anchor/> tag, but should also not be repeated for any other tags. Drawing from the list on the Missionary Travels google doc "Transcription Workflows," use the next available value and highlight it in yellow to show that it has been used.

    Note: If a metamark is in an unusual place (for example "marginleft", "margintop", "marginbottom"), you may also include the place attribute on <metamark/>. This is only necessary if the metamark is outside (or above or below) the body of the text and needs to be signalled specially.

    Also note: Often a metamark is written by an editorial/unknown hand, but surrounds text written by Livingstone. Record such instances using the rend and resp (responsibility) attributes on <metamark/>:
    <metamark function="queryrend="grayresp="#U2"  spanTo="#meta-2"/> Livingstone's text<anchor xml:id="meta-2"/>

    As in the example above, the <metamark/> element doesn’t accept hand, so we indicate the authorial responsibility using resp.

    Please note that it is generally only necessary to use a separate <add> tag on a metamark when encoding a long arrow leading to a portion of text. In other words, if the metamark is part of a longer addition that includes text added by either DL or an editor, it should be nested in an <add> tag. Otherwise, by default we assume that metamarks are added later and therefore this does not need to be coded separately.

    Definitions of the elements used above are:

    • metamark contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document.
      functiondescribes the function (for example status, insertion, deletion, transposition) of the mark.
      spanTo [att.spanning]indicates the end of a span initiated by the element bearing this attribute.
      rend [att.global.rendition](rendition) indicates how the element in question was rendered or presented in the source text.
      resp [att.global.responsibility](responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
    • anchor/ (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
      xml:id [att.global](identifier) provides a unique identifier for the element bearing the attribute.
    • add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.
  3. Note on "reorder"

    When a textual mark or arrow is used to signal that a portion of text should be moved to another place in the document (often up or down several lines), do not move the word itself while transcribing. Instead, transcribe what you see on the page, while capturing the intended reordering as follows:

    First, mark the portion of text intended for relocation using the <seg> element with the corresp attribute. For example:
    <seg corresp="#reorder-1">some words to be moved three lines below</seg>

    (Notice that the value for corresp is preceded by a "#" [number sign].)

    Next, at the place where the word(s) are intended to be moved to, indicate this by using the anchor tag, which simply marks a spot. Leave a space before and after this tag:
    <lb/>the text to be repositioned belongs right <anchor xml:id="reorder-1"/> in the middle of this sentence.

    (Notice that the value of the attribute xml:id is the same as on the corresp above, but now is not preceded by a "#" [number sign].)

    Finally, since reordering in Livingstone’s manuscripts is indicated using a metamark of some kind, the word or words marked up using <seg> should also be wrapped in the <metamark/> and <anchor/> tags. Use these tags as explained above, remembering to include the function, rend, and resp attributes on <metamark/> as appropriate. For example:
    <lb/><metamark function="reorderrend="grayresp="#U2"  spanTo="#meta-3"/> <seg corresp="#reorder-2">some words, circled by an editor,</seg><anchor xml:id="meta-3"/> <lb/>to be placed in the middle <anchor xml:id="reorder-2"/> of the line below.

    Note: In the above examples the values "reorder-1" and "reorder-2" are arbitrary. The value must be the same for corresp on the <seg> tag and the xml:id on the <anchor/> tag, but should also not be repeated for any other tags. Drawing from the list on the Missionary Travels google doc "Transcription Workflows," take the next available value and highlight it in yellow to show that it has been used.

    Also note: If it is the case that two words are intended to be switched (a transposition, technically), code this as a single reordering where possible (i.e. if the two words are side-by-side). However, if it is not possible to capture Livingstone's or the editor's intention using a single reordering, code the two words as separate reorderings, each contained in their own <metamark/> and <anchor/> tags.

    In the example below, Livingstone intends to transpose the words "lions" and "baboons":
    <lb/><metamark function="reorderspanTo="#meta-4"/><seg corresp="#reorder-3">lions</seg> <anchor xml:id="meta-4"/> <anchor xml:id="reorder-4"/> and <metamark function="reorderspanTo="#meta-5"/> <seg corresp="#reorder-4">baboons</seg><anchor xml:id="meta-5"/> <anchor xml:id="reorder-3"/> 

    Definitions of the elements used above are:

    • seg (arbitrary segment) represents any segmentation of text below the ‘chunk’ level.
      corresp [att.global.linking](corresponds) points to elements that correspond to the current element in some way.
    • anchor/ (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
      xml:id [att.global](identifier) provides a unique identifier for the element bearing the attribute.
    • metamark contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document.
      functiondescribes the function (for example status, insertion, deletion, transposition) of the mark.
      rend [att.global.rendition](rendition) indicates how the element in question was rendered or presented in the source text.
      resp [att.global.responsibility](responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
      spanTo [att.spanning]indicates the end of a span initiated by the element bearing this attribute.

24.5. Substantial Sections in Another Hand

Short portions of text in another hand are encoded using variations on the following formula:
<add place="inlinerend="grayhand="#U2">addition by an editor</add>
If, however, the hand changes for a longer portion of text (for instance, for many paragraphs or even several pages), use the <div> element plus the resp attribute to mark the new hand composing the section. For example:
<div resp="#CL"> <lb/><p>long portion of text in Charles Livingstone's hand.</p> </div>

This is particularly important for volume three of Missionary Travels, where a considerable portion of text is written by Charles Livingstone and by another unidentified hand.

Note: <p> must be contained within <div>, so the previous paragraph must be closed before a new <div> can be opened. Whether or not the long portion of text begins a new paragraph, it will thus be necessary to make one to indicate the change of hand.

Definitions of the elements used above are:

24.6. Handnotes

It is important to note that multiple hands contribute to the manuscript of Missionary Travels. (For guidance on coding these, see 11.11. Addition to or Deletions from the Original Manuscript and 24.5. Substantial Sections in Another Hand.)

In Missionary Travels the hands currently in use are:

Remember that both known and unknown hands require a <handNote> in the header:
<handNote xml:id="U1"><label>Unknown Hand 1</label>  This hand belongs to a later librarian or archivist, whose  additions are normally limited to adding page numbers.</handNote> <handNote xml:id="U2"><label>Unknown Hand 2</label>  This hand is unknown but is thought to be an editor or group  of editors in the employment of the publisher, John Murray,  making corrections and additions in pencil.</handNote> <handNote xml:id="U3"><label>Unknown Hand 3</label>  This hand is unknown but is thought to be an editor or group  of editors in the employment of the publisher, John Murray,  making corrections and additions in red ink.</handNote> <handNote xml:id="U4"><label>Unknown Hand 4</label>  This unknown hand is possibly Dr Keith of Hamilton.</handNote> <handNote xml:id="CL"><label>Charles Livingstone</label>  This hand belongs to Charles Livingstone.</handNote>                         

Please notify the project team if you discover another hand.

Note: In the example above, empty lines have been put between the <handNote> elements to facilitate reading, but such emtpy lines are not necessary in your actual transcription

Definitions of the elements used above are:

Appendix A Summary of Elements in LEAP Schema

Analysis Module

Core Module

Figures Module

Header Module

Linking Module

Manuscript Description Module

Names and Dates Module

Text Critical Apparatus Module

Text Structure Module

Transcription Module

Appendix B Formal declaration and Reference Pages

Appendix B.1 Elements

Appendix B.1.1 <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of <TEI> elements may be combined together to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
versionspecifies the major version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatype
data.version
NoteThe major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the <schemaSpec> element. The current version is P5.
Contained by
May contain
header: teiHeader
textstructure: text
transcr: facsimile
Declaration
element TEI
{
   att.global.attributes,
   attribute version { data.version }?,
   ( teiHeader, ( ( model.resourceLike+, text? ) | text ) )
}
Schematron
<s:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <s:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<s:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/>
Example
<TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a name space.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
NoteThis element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

Appendix B.1.2 <ab>

<ab> (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. Blocks, Segments, and Anchors]
Modulelinking — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element ab { att.global.attributes, att.typed.attributes, macro.paraContent }
Schematron
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure)"> Abstract model violation: ab may not contain paragraphs or other ab elements. </s:report>
Schematron
<s:report test="ancestor::tei:l or ancestor::tei:lg"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab. </s:report>
Example
<div type="bookn="Genesis">  <div type="chaptern="1">   <ab>In the beginning God created the heaven and the earth.</ab>   <ab>And the earth was without form, and void; and      darkness was upon the face of the deep. And the      spirit of God moved upon the face of the waters.</ab>   <ab>And God said, Let there be light: and there was light.</ab> <!-- ...-->  </div> </div>
NoteThe <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined.

Appendix B.1.3 <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source)
typeallows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatype
data.enumerated
Sample values include:
suspension
the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
the abbreviation includes writing above the line.
acronym
the abbreviation comprises the initial letters of the words of a phrase.
title
the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
the abbreviation is for the name of an organization.
geographic
the abbreviation is for a geographic name.
NoteThe type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see [[undefined PETTY]]
Member of
Contained by
May contain
Declaration
element abbr
{
   att.global.attributes,
   att.source.attributes,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
NoteThe <abbr> tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate.

Appendix B.1.4 <accMat>

<accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript being described, such as non-contemporaneous documents or fragments bound in with the manuscript at some earlier historical period. [10.7.3.3. Accompanying Material]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
msdescription: physDesc
May contain
Declaration
element accMat
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}
Example
<accMat>A copy of a tax form from 1947 is included in the envelope with the letter. It is not catalogued separately.</accMat>

Appendix B.1.5 <acquisition>

<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Contained by
msdescription: history
May contain
Declaration
element acquisition
{
   att.global.attributes,
   att.datable.attributes,
   macro.specialPara
}
Example
<acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition>

Appendix B.1.6 <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.placement (@place) att.typed (@type)
Member of
Contained by
May contain
Declaration
element add
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.placement.attributes,
   att.typed.attributes,
   macro.paraContent
}
Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
NoteIn a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

Appendix B.1.7 <addName>

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element addName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<persName>  <forename>Frederick</forename>  <addName type="epithet">the Great</addName>  <roleName>Emperor of Prussia</roleName> </persName>

Appendix B.1.8 <addSpan/>

<addSpan/> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [11.3.1.4. Additions and Deletions]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.placement (@place) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element addSpan
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.placement.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}
Schematron
<sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
Schematron
<sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
Example
<handNote xml:id="HEOLscribe="HelgiÓlafsson"/> <!-- ... --> <body>  <div> <!-- text here -->  </div>  <addSpan n="added gatheringhand="#HEOLspanTo="#P025"/>  <div> <!-- text of first added poem here -->  </div>  <div> <!-- text of second added poem here -->  </div>  <div> <!-- text of third added poem here -->  </div>  <div> <!-- text of fourth added poem here -->  </div>  <anchor xml:id="P025"/>  <div> <!-- more text here -->  </div> </body>
NoteBoth the beginning and the end of the added material must be marked; the beginning by the <addSpan/> element itself, the end by the spanTo attribute.

Appendix B.1.9 <additional>

<additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. Additional Information]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msPart
May contain
msdescription: adminInfo surrogates
Declaration
element additional
{
   att.global.attributes,
   ( adminInfo?, surrogates?, listBibl? )
}
Example
<additional>  <adminInfo>   <recordHist>    <p> <!-- record history here -->    </p>   </recordHist>   <custodialHist>    <p> <!-- custodial history here -->    </p>   </custodialHist>  </adminInfo>  <surrogates>   <p> <!-- information about surrogates here -->   </p>  </surrogates>  <listBibl>   <bibl> <!-- ... -->   </bibl> <!-- full bibliography here -->  </listBibl> </additional>

Appendix B.1.10 <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: address
May contain
Declaration
element addrLine { att.global.attributes, macro.phraseSeq }
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
NoteAddresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.

Appendix B.1.11 <address>

<address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element address
{
   att.global.attributes,
   ( model.global*, ( ( model.addrPart ), model.global* )+ )
}
Example
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name n="I">Italy</name> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
NoteThis element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.

Appendix B.1.12 <adminInfo>

<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript, and also about the record description itself. [10.9.1. Administrative Information]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: additional
May contain
core: note
header: availability
msdescription: custodialHist recordHist
Declaration
element adminInfo
{
   att.global.attributes,
   ( recordHist?, availability?, custodialHist?, model.noteLike? )
}
Example
<adminInfo>  <recordHist>   <source>Record created <date>1 Aug 2004</date>   </source>  </recordHist>  <availability>   <p>Until 2015 permission to photocopy some materials from this      collection has been limited at the request of the donor. Please ask repository staff for details      if you are interested in obtaining photocopies from Series 1:      Correspondence.</p>  </availability>  <custodialHist>   <p>Collection donated to the Manuscript Library by the Estate of      Edgar Holden in 1993. Donor number: 1993-034.</p>  </custodialHist> </adminInfo>

Appendix B.1.13 <affiliation>

<affiliation> contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
May contain
Declaration
element affiliation
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for    the Humanities</name> </affiliation> <affiliation notAfter="1960-01-01notBefore="1957-02-28">Paid up member of the <orgName>Australian Journalists Association</orgName> </affiliation>
NoteIf included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.

Appendix B.1.14 <age>

<age> specifies the age of a person. [13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
valuesupplies a numeric code representing the age or age group
StatusOptional
Datatype
data.count
NoteThis attribute may be used to complement a more detailed discussion of a person's age in the content of the element
Member of
Contained by
namesdates: person
May contain
Declaration
element age
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   attribute value { data.count }?,
   macro.phraseSeq.limited
}
Example
<age value="2notAfter="1986">under 20 in the early eighties</age>
NoteAs with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text.

Appendix B.1.15 <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
msdescription: msIdentifier msPart
May contain
Declaration
element altIdentifier
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.placeNamePart_sequenceOptional,
      institution?,
      repository?,
      collection?,
      idno,
      note?
   )
}
Example
<altIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </altIdentifier>
NoteAn identifying number of some kind must be supplied if known; if it is not known, this should be stated.

Appendix B.1.16 <anchor/>

<anchor/> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.4. Correspondence and Alignment]
Modulelinking — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May containEmpty element
Declaration
element anchor { att.global.attributes, att.typed.attributes, empty }
Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s> <s>Help me find it.<ptr target="#A234"/> </s>
NoteOn this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

Appendix B.1.17 <app>

<app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [12.1.1. The Apparatus Entry]
Moduletextcrit — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
typeclassifies the variation contained in this element according to some convenient typology.
StatusOptional
Datatype
data.enumerated
fromidentifies the beginning of the lemma in the base text.
StatusOptional
Datatype
data.pointer
NoteThis attribute should be used when either the double-end point method of apparatus markup, or the location-referenced method with a URL rather than canonical reference, are used.
toidentifies the endpoint of the lemma in the base text.
StatusOptional
Datatype
data.pointer
NoteThis attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not embedded in-line in the base-text.
loc(location) indicates the location of the variation, when the location-referenced method of apparatus markup is used.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
NoteThis attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage to which the variation applies.
Member of
Contained by
May contain
Declaration
element app
{
   att.global.attributes,
   attribute type { data.enumerated }?,
   attribute from { data.pointer }?,
   attribute to { data.pointer }?,
   attribute loc { list { data.word+ } }?,
   (
      (
         model.global.meta
       | model.global.spoken
       | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
       | notatedMusic
      )*,
      (
         lem,
         (
            model.global.meta
          | model.global.spoken
          | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
          | notatedMusic
         )*,
         (
            wit,
            (
               model.global.meta
             | model.global.spoken
             | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
             | notatedMusic
            )*
         )?
      )?,
      (
         (
            model.rdgLike,
            (
               model.global.meta
             | model.global.spoken
             | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
             | notatedMusic
            )*,
            (
               wit,
               (
                  model.global.meta
                | model.global.spoken
                | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
                | notatedMusic
               )*
            )?
         )
       | (
            rdgGrp,
            (
               model.global.meta
             | model.global.spoken
             | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
             | notatedMusic
            )*,
            (
               wit,
               (
                  model.global.meta
                | model.global.spoken
                | model.milestoneLikemodel.noteLikeaddSpandamageSpandelSpangapspacefiguremetamark
                | notatedMusic
               )*
            )?
         )
      )*
   )
}
Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg wit="#Latype="substantive">Experiment</rdg>  <rdg wit="#Ra2type="substantive">Eryment</rdg> </app>
Example
<app type="substantive">  <rdgGrp type="subvariants">   <lem wit="#El #Hg">Experience</lem>   <rdg wit="#Ha4">Experiens</rdg>  </rdgGrp>  <rdgGrp type="subvariants">   <lem wit="#Cp #Ld1">Experiment</lem>   <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>  </rdgGrp>  <rdgGrp type="subvariants">   <lem resp="#ed2013">Eriment</lem>   <rdg wit="#Ra2">Eryment</rdg>  </rdgGrp> </app>
Example
<app loc="1">  <rdg resp="#SEG">TIMΩΔA</rdg> </app>
Example
<app loc="1-6">  <note>Too badly worn to yield a text</note> </app>
Example
<choice xml:id="choice3">  <reg>σύμπαντα</reg>  <orig>ΣΙΝΠΑΤΑΝ</orig> </choice> <!-- ... --> <app from="#choice3">  <note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note> </app>

Appendix B.1.18 <author>

<author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
core: bibl monogr
msdescription: msItem
May contain
Declaration
element author
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
NoteParticularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.
Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Appendix B.1.19 <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: monogr
May contain
Declaration
element authority { att.global.attributes, macro.phraseSeq.limited }
Example
<authority>John Smith</authority>

Appendix B.1.20 <availability>

<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
statussupplies a code identifying the current availability of the text.
StatusOptional
Datatype
data.enumerated
Legal values are:
free
the text is freely available.
unknown
the status of the text is unknown.[Default]
restricted
the text is not freely available.
Member of
Contained by
core: bibl monogr
msdescription: adminInfo
May contain
core: p
header: licence
linking: ab
Declaration
element availability
{
   att.global.attributes,
   att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( model.availabilityPart | model.pLike )+
}
Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
NoteA consistent format should be adopted

Appendix B.1.21 <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
textstructure: text
transcr: facsimile
May contain
Declaration
element back
{
   att.global.attributes,
   (
      (
         model.frontPartmodel.pLike.frontmodel.pLikemodel.listLikemodel.global
      )*,
      (
         (
            (
               ( model.div1Like ),
               ( model.frontPart | model.div1Like | model.global )*
            )
          | (
               ( model.divLike ),
               ( model.frontPart | model.divLike | model.global )*
            )
         )?
      ),
      ( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? )
   )
}
Example
<back>  <div1 type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>To shew the Depravity of human Nature </p>  </div1>  <div1 type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please </p>  </div1>  <div1 type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item>    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div1>  <div1 type="advert">   <head>    <hi rend="center">By the KING's Royal Patent,</hi> Are sold by J. NEWBERY, at the      Bible and Sun in St. Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c.        2s. 6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item>   </list>  </div1> </back>
NoteBecause cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

Appendix B.1.22 <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Declaration
element bibl
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      text
    | model.gLike
    | model.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapterxml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
NoteContains phrase-level elements, together with any combination of elements from the biblPart class

Appendix B.1.23 <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.citing (@unit, @from, @to)
Member of
Contained by
May contain
Declaration
element biblScope
{
   att.global.attributes,
   att.citing.attributes,
   macro.phraseSeq
}
Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
NoteWhen a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.

Appendix B.1.24 <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
header: idno
Declaration
element biblStruct
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      analytic*,
      ( monogr, series* )+,
      ( model.noteLike | idno | model.ptrLike | relatedItem | citedRange )*
   )
}
SchematronThe use of an <idno> element as a direct child of <biblStruct> is deprecated. Rather, <idno> should appear as a child of a <monogr>, <analytic>, or <series>.
<sch:report test="child::tei:idno"  role="nonfatal">WARNING: use of deprecated method — the use of the idno element as a direct child of the biblStruct element will be removed from the TEI on 2016-09-18</sch:report>
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>

Appendix B.1.25 <birth>

<birth> contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
namesdates: person
May contain
Declaration
element birth
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>

Appendix B.1.26 <bloc>

<bloc> contains the name of a geo-political unit consisting of two or more nation states or countries. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
May contain
Declaration
element bloc
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}
Example
<bloc type="union">the European Union</bloc> <bloc type="continent">Africa</bloc>

Appendix B.1.27 <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
textstructure: text
May contain
Declaration
element body
{
   att.global.attributes,
   (
      model.global*,
      ( ( model.divTop ), ( model.global | model.divTop )* )?,
      ( ( model.divGenLike ), ( model.global | model.divGenLike )* )?,
      (
         ( ( model.divLike ), ( model.global | model.divGenLike )* )+
       | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
       | (
            ( ( model.common ), model.global* )+,
            (
               ( ( model.divLike ), ( model.global | model.divGenLike )* )+
             | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
            )?
         )
      ),
      ( ( model.divBottom ), model.global* )*
   )
}

Appendix B.1.28 <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc. [2.3.7. The Classification Declaration]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: category
May contain
Declaration
element catDesc
{
   att.global.attributes,
   ( text | model.limitedPhrase | model.catDescPart )*
}
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc> </catDesc>

Appendix B.1.29 <category>

<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
core: desc gloss
Declaration
element category
{
   att.global.attributes,
   ( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* )
}
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>

Appendix B.1.30 <cb/>

<cb/> (column break) marks the beginning of a new column of a text on a multi-column page. [3.10.3. Milestone Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Declaration
element cb
{
   att.global.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}
ExampleMarkup of an early English dictionary printed in two columns:
<pb/> <cb n="1"/> <entryFree>  <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>: <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner    sinks into the Ground, to find out and disappoint the Enemies Mines,    or to prepare one</sense>. </entryFree> <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or <sense>lie groveling</sense>.</entryFree> <!-- remainder of column --> <cb n="2"/> <entryFree>  <form>Wey</form>, <sense>the greatest Measure for dry Things,    containing five Chaldron</sense>. </entryFree> <entryFree>  <form>Whale</form>, <sense>the greatest of    Sea-Fishes</sense>. </entryFree>
NoteOn this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb/> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb/> element is placed at the head of the column to which it refers.

Appendix B.1.31 <cell>

<cell> contains one cell of a table. [14.1.1. TEI Tables]
Modulefigures — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (@role, @rows, @cols)
Contained by
figures: row
May contain
Declaration
element cell
{
   att.global.attributes,
   att.tableDecoration.attributes,
   macro.specialPara
}
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>

Appendix B.1.32 <change>

<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Changes]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
targetpoints to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Contained by
msdescription: recordHist
May contain
Declaration
element change
{
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute target { list { data.pointer+ } }?,
   macro.specialPara
}
Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
NoteThe who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Appendix B.1.33 <choice>

<choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element choice { att.global.attributes, ( model.choicePart | choice )* }
ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
NoteBecause the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.Note also that <choice> elements may self-nest.
Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

Appendix B.1.34 <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Declaration
element classDecl { att.global.attributes, taxonomy+ }
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>

Appendix B.1.35 <closer>

<closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
figures: figure table
textstructure: back body div front postscript
May contain
Declaration
element closer
{
   att.global.attributes,
   (
      text
    | model.gLike
    | signeddatelinesalutemodel.phrasemodel.global
   )*
}
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- .... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>

Appendix B.1.36 <collection>

<collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type)
Contained by
May containCharacter data only
Declaration
element collection
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.xtext
}
Example
<msIdentifier>  <country>USA</country>  <region>California</region>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <collection>Ellesmere</collection>  <idno>El 26 C 9</idno>  <msName>The Ellesmere Chaucer</msName> </msIdentifier>

Appendix B.1.37 <condition>

<condition> contains a description of the physical condition of the manuscript. [10.7.1.5. Condition]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: sealDesc supportDesc
May contain
Declaration
element condition { att.global.attributes, macro.specialPara }
Example
<condition>  <p>There are lacunae in three places in this    manuscript. After 14v two    leaves has been cut out and narrow strips leaves remains in the spine. After    68v one gathering is missing and after 101v at least one gathering of 8 leaves    has been lost. </p>  <p>Several leaves are damaged with tears or holes or have a    irregular shape. Some of the damages do not allow the lines to be of full    length and they are apparently older than the script. There are tears on fol.    2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,    37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,    74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98    the corner has been torn off. Several leaves are in a bad condition due to    moist and wear, and have become dark, bleached or    wrinkled. </p>  <p>The script has been    touched up in the 17th century with black ink. The touching up on the following    fols. was done by  <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,    6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An    AM-note says according to the lawman  <name>Sigurður Björnsson</name> that the rest of the    touching up was done by himself and another lawman  <name>Sigurður Jónsson</name>.  <name>Sigurður Björnsson</name> did the touching up    on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.  <name>Sigurður Jónsson</name> did the rest of the    touching up in the section 36r-59r containing  <title>Bretasögur</title>  </p> </condition>

Appendix B.1.38 <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element corr
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?

Appendix B.1.39 <country>

<country> contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
May contain
Declaration
element country
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}
Example
<country key="DK">Denmark</country>
NoteThe recommended source for codes to represent coded country names is ISO 3166.

Appendix B.1.40 <custEvent>

<custEvent> (custodial event) describes a single event during the custodial history of a manuscript. [10.9.1.2. Availability and Custodial History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.typed (@type)
Contained by
msdescription: custodialHist
May contain
Declaration
element custEvent
{
   att.global.attributes,
   att.datable.attributes,
   att.typed.attributes,
   macro.specialPara
}
Example
<custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date> </custEvent>

Appendix B.1.41 <custodialHist>

<custodialHist> (custodial history) contains a description of a manuscript's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: adminInfo
May contain
core: p
linking: ab
msdescription: custEvent
Declaration
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }
Example
<custodialHist>  <custEvent type="conservationnotBefore="1961-03"   notAfter="1963-02">Conserved between March 1961 and February 1963 at    Birgitte Dalls Konserveringsværksted.</custEvent>  <custEvent type="photographynotBefore="1988-05-01"   notAfter="1988-05-30">Photographed in    May 1988 by AMI/FA.</custEvent>  <custEvent type="transfer-dispatchnotBefore="1989-11-13"   notAfter="1989-11-13">Dispatched to Iceland    13 November 1989.</custEvent> </custodialHist>

Appendix B.1.42 <damage>

<damage> contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) )
Member of
Contained by
May contain
Declaration
element damage
{
   att.global.attributes,
   att.typed.attributes,
   att.damaged.attributes,
   macro.paraContent
}
Example
<l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l> <l>Moves <damage agent="watergroup="1">   <supplied>on: nor all your</supplied>  </damage> Piety nor Wit</l>
NoteSince damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Appendix B.1.43 <damageSpan/>

<damageSpan/> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element damageSpan
{
   att.global.attributes,
   att.damaged.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}
Schematron
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Example
<p>Paragraph partially damaged. This is the undamaged portion <damageSpan spanTo="#a34"/>and this the damaged portion of the paragraph.</p> <p>This paragraph is entirely damaged.</p> <p>Paragraph partially damaged; in the middle of this paragraph the damage ends and the anchor point marks the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p>
NoteBoth the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan/> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor/> element may be used for this purpose.The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan/> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 11.3.3.1. Damage, Illegibility, and Supplied Text and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

Appendix B.1.44 <date>

<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element date
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>

Appendix B.1.45 <dateline>

<dateline> contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
figures: figure table
textstructure: body closer div front opener
May contain
Declaration
element dateline
{
   att.global.attributes,
   ( text | model.gLike | model.phrase | model.global | docDate )*
}
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>

Appendix B.1.46 <death>

<death> contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
namesdates: person
May contain
Declaration
element death
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>

Appendix B.1.47 <decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements. [10.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
msdescription: decoNote summary
Declaration
element decoDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, decoNote+ ) )
}
Example
<decoDesc>  <p>The start of each book of the Bible with a 10-line historiated    illuminated initial; prefaces decorated with 6-line blue initials with red    penwork flourishing; chapters marked by 3-line plain red initials; verses    with 1-line initials, alternately blue or red.</p> </decoDesc>

Appendix B.1.48 <decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
msdescription: decoDesc msItem seal sealDesc
May contain
Declaration
element decoNote
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}
Example
<decoDesc>  <decoNote type="initial">   <p>The start of each book of the Bible with      a 10-line historiated illuminated initial;      prefaces decorated with 6-line blue initials      with red penwork flourishing; chapters marked by      3-line plain red initials; verses with 1-line initials,      alternately blue or red.</p>  </decoNote> </decoDesc>

Appendix B.1.49 <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element del
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   macro.paraContent
}
Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegiblequantity="5unit="character"/> </del>
NoteThis element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan/> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.
Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21. Certainty, Precision, and Responsibility).
There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

Appendix B.1.50 <delSpan/>

<delSpan/> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. Additions and Deletions]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element delSpan
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}
Schematron
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Example
<p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p>
NoteBoth the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan/> element, the ending by the target of the spanTo attribute.The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <delSpan/> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the <delSpan/> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.
The <delSpan/> tag should not be used for deletions made by editors or encoders. In these cases, either the <corr> tag or the <gap> tag should be used.

Appendix B.1.51 <depth>

<depth> contains a measurement measured across the spine of a book or codex, or (for other text-bearing objects) perpendicular to the measurement given by the ‘width’ element. [10.3.4. Dimensions]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element depth { att.global.attributes, att.dimensions.attributes, macro.xtext }
Example
<depth unit="inquantity="4"/>
NoteIf used to specify the width of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘width’ axis.

Appendix B.1.52 <desc>

<desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.1. Description of Components]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element desc
{
   att.global.attributes,
   att.typed.attributes,
   macro.limitedContent
}
Example
<desc>contains a brief description of the purpose and application for an element, attribute, attribute value, class, or entity.</desc>
NoteTEI convention requires that this be expressed as a finite clause, begining with an active verb.

Appendix B.1.53 <dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element dim
{
   att.global.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.xtext
}
Example
<dim type="circumferenceextent="4.67 in"/>
NoteThe specific elements <width>, <height>, and <depth> should be used in preference to this generic element wherever appropriate.

Appendix B.1.54 <dimensions>

<dimensions> contains a dimensional specification. [10.3.4. Dimensions]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
typeindicates which aspect of the object is being measured.
StatusOptional
Datatype
data.enumerated
Sample values include:
leaves
dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)
ruled
dimensions relate to the area of a leaf which has been ruled in preparation for writing.
pricked
dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable).
written
dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.
miniatures
dimensions relate to the miniatures within the manuscript
binding
dimensions relate to the binding in which the codex or manuscript is contained
box
dimensions relate to the box or other container in which the manuscript is stored.
Member of
Contained by
May contain
msdescription: depth dim height width
Declaration
element dimensions
{
   att.global.attributes,
   att.dimensions.attributes,
   attribute type { data.enumerated }?,
   ( ( dim | model.dimLike )* )
}
Schematron
<s:report test="count(tei:width)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only </s:report>
Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
ExampleThis element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="reliefunit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
ExampleWhen simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height unit="cmscope="mostquantity="90"/>  <width unit="cmscope="mostquantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
NoteContains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

Appendix B.1.55 <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
textcrit: rdg
textstructure: back body div front
May contain
Declaration
element div
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( ( model.divLike | model.divGenLike ), model.global* )+ )
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.divLike | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Schematron
<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div. </s:report>
Schematron
<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div. </s:report>
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number....</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority ... </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when... </p>    </div>   </div>  </div> </body>

Appendix B.1.56 <edition>

<edition> describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
Declaration
element edition { att.global.attributes, macro.phraseSeq }
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>

Appendix B.1.57 <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: fileDesc
May contain
Declaration
element editionStmt
{
   att.global.attributes,
   ( model.pLike+ | ( edition, model.respLike* ) )
}
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>

Appendix B.1.58 <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. Titles, Authors, and Editors]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
core: bibl monogr
msdescription: msItem
May contain
Declaration
element editor
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<editor>Eric Johnson</editor> <editor role="illustrator">John Tenniel</editor>
NoteA consistent format should be adopted.Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

Appendix B.1.59 <education>

<education> contains a description of the educational experience of a person. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
namesdates: person
May contain
Declaration
element education
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01to="1990-06-30">Attended <name>Cherwell School</name> </education>
Example
<education notBefore="1685-07notAfter="1690-06">Anthony Hammond smuggled her into the University of Cambridge, where she was disguised as his male cousin, Jack. She remained there for some months learning grammar, logic, rhetoric, and ethics</education>

Appendix B.1.60 <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: teiHeader
May contain
Declaration
element encodingDesc
{
   att.global.attributes,
   ( ( model.encodingDescPart | model.pLike )+ )
}
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>

Appendix B.1.61 <event>

<event> contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type) att.naming (@role) (att.canonical (@ref)) att.sortable (@sortKey)
whereindicates the location of an event by pointing to a <place> element
StatusOptional
Datatype
data.pointer
Member of
Contained by
May contain
linking: ab link linkGrp
msdescription: msDesc
namesdates: event
Declaration
element event
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   att.naming.attributes,
   att.sortable.attributes,
   attribute where { data.pointer }?,
   (
      model.headLike*,
      ( ( model.pLike+ ) | ( model.labelLike+ ) ),
      ( model.noteLike | model.biblLike | linkGrp | link )*,
      event*
   )
}
Example
<person>  <event type="matwhen="1972-10-12">   <label>matriculation</label>  </event>  <event type="gradwhen="1975-06-23">   <label>graduation</label>  </event> </person>

Appendix B.1.62 <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
May contain
Declaration
element expan
{
   att.global.attributes,
   att.editLike.attributes,
   macro.phraseSeq
}
Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<expan xml:lang="la">  <abbr>Imp</abbr>  <ex>erator</ex> </expan>
NoteThe content of this element should usually be a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

Appendix B.1.63 <facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
textstructure: TEI
May contain
core: graphic
textstructure: back front
Declaration
element facsimile
{
   att.global.attributes,
   ( front?, ( model.graphicLike | surface | surfaceGrp )+, back? )
}
Example
<facsimile>  <graphic url="page1.png"/>  <surface>   <graphic url="page2-highRes.png"/>   <graphic url="page2-lowRes.png"/>  </surface>  <graphic url="page3.png"/>  <graphic url="page4.png"/> </facsimile>
Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>

Appendix B.1.64 <faith>

<faith> specifies the faith, religion, or belief set of a person. [13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.canonical (@ref)
Member of
Contained by
namesdates: person
May contain
Declaration
element faith
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>

Appendix B.1.65 <figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
Modulefigures — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
figures: figure
May contain
Declaration
element figDesc { att.global.attributes, macro.limitedContent }
Example
<figure>  <graphic url="emblem1.png"/>  <head>Emblemi d'Amore</head>  <figDesc>A pair of naked winged cupids, each holding a    flaming torch, in a rural setting.</figDesc> </figure>
NoteThis element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Appendix B.1.66 <figure>

<figure> groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
Modulefigures — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place) att.typed (@type)
Member of
Contained by
May contain
Declaration
element figure
{
   att.global.attributes,
   att.placement.attributes,
   att.typed.attributes,
   (
      model.headLikemodel.commonfigDescmodel.graphicLikemodel.globalmodel.divBottom
   )*
}
Example
<figure>  <head>The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc>  <graphic url="http://www.example.org/fig1.pngscale="0.5"/> </figure>

Appendix B.1.67 <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: teiHeader
May contain
Declaration
element fileDesc
{
   att.global.attributes,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt?,
         notesStmt?
      ),
      sourceDesc+
   )
}
Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
NoteThe major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

Appendix B.1.68 <foliation>

<foliation> describes the numbering system or systems used to count the leaves or pages in a codex. [10.7.1.4. Foliation]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: supportDesc
May contain
Declaration
element foliation { att.global.attributes, macro.specialPara }
Example
<foliation>Contemporary foliation in red roman numerals in the centre of the outer margin.</foliation>

Appendix B.1.69 <foreign>

<foreign> identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element foreign { att.global.attributes, macro.phraseSeq }
Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
NoteThe global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.
The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Appendix B.1.70 <forename>

<forename> contains a forename, given or baptismal name. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element forename
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>

Appendix B.1.71 <front>

<front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
textstructure: text
transcr: facsimile
May contain
Declaration
element front
{
   att.global.attributes,
   (
      ( ( model.frontPart | model.pLike | model.pLike.front | model.global )* ),
      (
         (
            (
               model.div1Like,
               ( model.div1Like | model.frontPart | model.global )*
            )
          | (
               model.divLike,
               ( model.divLike | model.frontPart | model.global )*
            )
         ),
         ( ( ( model.divBottom ), ( model.divBottom | model.global )* )? )
      )?
   )
}
Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis      vidi in ampulla pendere, et cum illi pueri dicerent:   <q xml:lang="gr">Σίβυλλα τί θέλεις</q>; respondebat      illa: <q xml:lang="gr">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently.      ...</p>  </div> </front>
NoteBecause cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Appendix B.1.72 <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
Member of
Contained by
core: bibl monogr
msdescription: msItem
May contain
Declaration
element funder
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq.limited
}
Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
NoteFunders provide financial support for a project; they are distinct from sponsors, who provide intellectual support and authority.

Appendix B.1.73 <fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place)
typeclassifies the material encoded according to some useful typology.
StatusRecommended
Datatype
data.enumerated
Sample values include:
header
a running title at the top of the page
footer
a running title at the bottom of the page
pageNum
(page number) a page number or foliation symbol
lineNum
(line number) a line number, either of prose or poetry
sig
(signature) a signature or gathering symbol
catch
(catchword) a catch-word
Member of
Contained by
May contain
Declaration
element fw
{
   att.global.attributes,
   att.placement.attributes,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Example
<fw type="sigplace="bottom">C3</fw>
NoteWhere running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

Appendix B.1.74 <gap>

<gap> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
reasongives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
handin the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, indicates the hand which made the deletion.
StatusOptional
Datatype
data.pointer
agentin the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatype
data.enumerated
Suggested values include:
blot
There is a blotting
fading
There is fading
hole
There is a hole
illegible
There is illegible text
overwriting
There is overwriting
stain
There is a stain
Member of
Contained by
May contain
core: desc
Declaration
element gap
{
   att.global.attributes,
   att.editLike.attributes,
   attribute reason { list { data.word+ } }?,
   attribute hand { data.pointer }?,
   attribute agent
   {
      "blot"
    | "fading"
    | "hole"
    | "illegible"
    | "overwriting"
    | "stain"
    | xsd:Name
   }?,
   ( model.descLike | model.certLike )*
}
Example
<gap quantity="4unit="charsreason="illegible"/>
Example
<gap quantity="1unit="essayreason="sampling"/>
Example
<del>  <gap atLeast="4atMost="8unit="charsreason="illegible"/> </del>
Example
<gap extent="unknownunit="linesreason="lost"/>
NoteThe <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

Appendix B.1.75 <gb/>

<gb/> (gathering begins) marks the point in a transcribed codex at which a new gathering or quire begins. [3.10.3. Milestone Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Declaration
element gb
{
   att.global.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}
Example
<gb n="iii"/> <pb n="2r"/> <!-- material from page 2 recto of gathering iii here --> <pb n="2v"/> <!-- material from page 2 verso of gathering iii here -->
NoteBy convention, <gb/> elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.The type attribute may be used to further characterize the gathering in any respect.

Appendix B.1.76 <geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May containCharacter data only
Declaration
element geo { att.global.attributes, text }
Example
<geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl> <!-- .... --> <location>  <desc>A tombstone plus six lines of    Anglo-Saxon text, built into the west tower (on the south side    of the archway, at 8 ft. above the ground) of the    Church of St. Mary-le-Wigford in Lincoln.</desc>  <geo decls="#WGS">53.226658 -0.541254</geo>  <geo decls="#OS">SK 97481 70947</geo> </location>
Example
<geo>41.687142 -74.870109</geo>
NoteUses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Appendix B.1.77 <geogFeat>

<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element geogFeat
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName>

Appendix B.1.78 <geogName>

<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element geogName
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<geogName>  <geogFeat>Mount</geogFeat>  <name>Sinai</name> </geogName>

Appendix B.1.79 <gloss>

<gloss> identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. Terms, Glosses, Equivalents, and Descriptions 22.4.1. Description of Components]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.pointing (@target)
Member of
Contained by
May contain
Declaration
element gloss
{
   att.global.attributes,
   att.typed.attributes,
   att.pointing.attributes,
   macro.phraseSeq
}
Example
We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
NoteThe target and cRef attributes are mutually exclusive.

Appendix B.1.80 <graphic>

<graphic> indicates the location of an inline graphic, illustration, or figure. [3.9. Graphics and Other Non-textual Components]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.media (@width, @height, @scale) att.resourced (@url)
Member of
Contained by
May contain
core: desc
Declaration
element graphic
{
   att.global.attributes,
   att.media.attributes,
   att.resourced.attributes,
   model.descLike*
}
Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
NoteThe mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Appendix B.1.81 <handDesc>

<handDesc> (description of hands) contains a description of all the different kinds of writing used in a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
handsspecifies the number of distinct hands identified within the manuscript
StatusOptional
Datatype
data.count
Member of
Contained by
msdescription: physDesc
May contain
core: p
header: handNote
linking: ab
msdescription: summary
Declaration
element handDesc
{
   att.global.attributes,
   attribute hands { data.count }?,
   ( model.pLike+ | ( summary?, handNote+ ) )
}
Example
<handDesc>  <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote> </handDesc>
Example
<handDesc hands="2">  <p>The manuscript is written in two contemporary hands, otherwise    unknown, but clearly those of practised scribes. Hand I writes    ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably    Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand    on f. 24, but the evidence for this is insubstantial.</p> </handDesc>

Appendix B.1.82 <handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
Contained by
msdescription: handDesc
transcr: handNotes
May contain
Declaration
element handNote
{
   att.global.attributes,
   att.handFeatures.attributes,
   macro.specialPara
}
Example
<handNote scope="sole">  <p>Written in insular    phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed    minuscule.</p> </handNote>

Appendix B.1.83 <handNotes>

<handNotes> contains one or more <handNote> elements documenting the different hands identified within the source texts. [11.3.2.1. Document Hands]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: profileDesc
May contain
header: handNote
Declaration
element handNotes { att.global.attributes, handNote+ }
Example
<handNotes>  <handNote xml:id="H1script="copperplatemedium="brown-ink">Carefully written with regular descenders</handNote>  <handNote xml:id="H2script="printmedium="pencil">Unschooled scrawl</handNote> </handNotes>

Appendix B.1.84 <handShift/>

<handShift/> marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) att.source (@source)
newindicates a <handNote> element describing the hand concerned.
StatusRecommended
Datatype
data.pointer
NoteThis attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.
Member of
Contained by
May containEmpty element
Declaration
element handShift
{
   att.global.attributes,
   att.handFeatures.attributes,
   att.source.attributes,
   attribute new { data.pointer }?,
   empty
}
Example
<l>When wolde the cat dwelle in his ynne</l> <handShift medium="greenish-ink"/> <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
NoteThe <handShift/> element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

Appendix B.1.85 <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element head
{
   att.global.attributes,
   att.typed.attributes,
   (
      text
    | lg
    | model.gLike
    | model.phrasemodel.inter
    | model.lLike
    | model.global
   )*
}
ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
ExampleThe <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
NoteThe <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

Appendix B.1.86 <height>

<height> contains a measurement measured along the axis at right angles to the bottom of the written surface, i.e. parallel to the spine for a codex or book. [10.3.4. Dimensions]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element height
{
   att.global.attributes,
   att.dimensions.attributes,
   macro.xtext
}
Example
<height unit="inquantity="7"/>
NoteIf used to specify the height of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis perpendicular to the surface of the earth.

Appendix B.1.87 <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element hi { att.global.attributes, macro.paraContent }
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...

Appendix B.1.88 <history>

<history> groups elements describing the full history of a manuscript or manuscript part. [10.8. History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msPart
May contain
core: p
linking: ab
Declaration
element history
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, origin?, provenance*, acquisition? ) )
}
Example
<history>  <origin>   <p>Written in Durham during the mid twelfth      century.</p>  </origin>  <provenance>   <p>Recorded in two medieval      catalogues of the books belonging to Durham Priory, made in 1391 and      1405.</p>  </provenance>  <provenance>   <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)      and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)      according to inscriptions on ff. 4v and 5.</p>  </provenance>  <acquisition>   <p>Presented to Trinity College in 1738 by      Thomas Gale and his son Roger.</p>  </acquisition> </history>

Appendix B.1.89 <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
StatusOptional
Datatype
data.enumerated
Member of
Contained by
May contain
header: idno
Declaration
element idno
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type { data.enumerated }?,
   ( text | model.gLike | idno )*
}
Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Note<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Appendix B.1.90 <imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
core: monogr
May contain
Declaration
element imprint
{
   att.global.attributes,
   (
      ( classCode | catRef )*,
      (
         ( ( model.imprintPart ) | ( model.dateLike ) ),
         respStmt*,
         model.global*
      )+
   )
}
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>

Appendix B.1.91 <institution>

<institution> contains the name of an organization such as a university or library, with which a manuscript is identified, generally its holding institution. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref))
Contained by
May containCharacter data only
Declaration
element institution
{
   att.global.attributes,
   att.naming.attributes,
   macro.xtext
}
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>

Appendix B.1.92 <item>

<item> contains one component of a list. [3.7. Lists 2.6. The Revision Description]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
Contained by
core: list
May contain
Declaration
element item
{
   att.global.attributes,
   att.sortable.attributes,
   macro.specialPara
}
Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
NoteMay contain simple prose or a sequence of chunks.Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.

Appendix B.1.93 <keywords>

<keywords> contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined identifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatype
data.pointer
Contained by
header: textClass
May contain
core: list term
Declaration
element keywords
{
   att.global.attributes,
   attribute scheme { data.pointer }?,
   ( term+ | list )
}
Example
<keywords scheme="http://classificationweb.net">  <term>Babbage, Charles</term>  <term>Mathematicians - Great Britain - Biography</term> </keywords>
Example
<keywords>  <term>Fermented beverages</term>  <term>Central Andes</term>  <term>Schinus molle</term>  <term>Molle beer</term>  <term>Indigenous peoples</term>  <term>Ethnography</term>  <term>Archaeology</term> </keywords>
NoteEach individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within a <item> inside a <list> is permitted for backwards compatibility, but is deprecated.If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.

Appendix B.1.94 <label>

<label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.placement (@place)
Member of
Contained by
May contain
Declaration
element label
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   macro.phraseSeq
}
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.

Appendix B.1.95 <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
Member of
Contained by
header: profileDesc
May contain
header: language
Declaration
element langUsage
{
   att.global.attributes,
   att.declarable.attributes,
   language+
}
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>

Appendix B.1.96 <language>

<language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
StatusRequired
Datatype
data.language
usagespecifies the approximate percentage (by volume) of the text which uses this language.
StatusOptional
Datatype
xsd:nonNegativeInteger { maxInclusive = "100" }
Contained by
header: langUsage
May contain
Declaration
element language
{
   att.global.attributes,
   attribute ident { data.language },
   attribute usage { xsd:nonNegativeInteger { maxInclusive = "100" } }?,
   macro.phraseSeq.limited
}
Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
NoteParticularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Appendix B.1.97 <layout>

<layout> describes how text is laid out on the page, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
columnsspecifies the number of columns per page
StatusOptional
Datatype1–2 occurrences of 
data.count
separated by whitespace
NoteIf a single number is given, all pages have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied.
ruledLinesspecifies the number of ruled lines per column
StatusOptional
Datatype1–2 occurrences of 
data.count
separated by whitespace
NoteIf a single number is given, all columns have this number of ruled lines. If two numbers are given, the number of ruled lines per column varies between the values supplied.
writtenLinesspecifies the number of written lines per column
StatusOptional
Datatype1–2 occurrences of 
data.count
separated by whitespace
NoteIf a single number is given, all columns have this number of written lines. If two numbers are given, the number of written lines per column varies between the values supplied.
Contained by
msdescription: layoutDesc
May contain
Declaration
element layout
{
   att.global.attributes,
   attribute columns { list { data.count, data.count? } }?,
   attribute ruledLines { list { data.count, data.count? } }?,
   attribute writtenLines { list { data.count, data.count? } }?,
   macro.specialPara
}
Example
<layout columns="1ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
Example
<layout columns="2ruledLines="42">  <p>2 columns of 42 lines ruled in ink, with central rule    between the columns.</p> </layout>
Example
<layout columns="1 2writtenLines="40 50">  <p>Some pages have 2 columns, with central rule    between the columns; each column with between 40 and 50 lines of writing.</p> </layout>

Appendix B.1.98 <layoutDesc>

<layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: objectDesc
May contain
core: p
linking: ab
msdescription: layout summary
Declaration
element layoutDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, layout+ ) )
}
Example
<layoutDesc>  <p>Most pages have between 25 and 32 long lines ruled in lead.</p> </layoutDesc>
Example
<layoutDesc>  <layout columns="2ruledLines="42">   <p>    <locus from="f12rto="f15v"/>      2 columns of 42 lines pricked and ruled in ink, with      central rule between the columns.</p>  </layout>  <layout columns="3">   <p xml:lang="zh-TW">    <locus from="f16"/>小孔的三欄可見.</p>  </layout> </layoutDesc>

Appendix B.1.99 <lb/>

<lb/> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone Elements 7.2.5. Speech Contents]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Declaration
element lb
{
   att.global.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}
ExampleThis example shows typographical line breaks within metrical lines, where they occur at different places in different editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
ExampleThis example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
NoteBy convention, <lb/> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb/> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.

Appendix B.1.100 <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@target) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
header: availability
May contain
Declaration
element licence
{
   att.global.attributes,
   att.pointing.attributes,
   att.datable.attributes,
   macro.specialPara
}
Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
NoteA <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

Appendix B.1.102 <linkGrp>

<linkGrp> (link group) defines a collection of associations or hypertextual links. [16.1. Links]
Modulelinking — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
linking: link
Declaration
element linkGrp { att.global.attributes, ( link | ptr )+ }
Example
<linkGrp type="translation">  <link target="#CCS1 #SW1"/>  <link target="#CCS2 #SW2"/>  <link target="#CCS #SW"/> </linkGrp> <div type="volumexml:id="CCSxml:lang="fr">  <p>   <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>   <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>  </p> <!-- ... --> </div> <div type="volumexml:id="SWxml:lang="en">  <p>   <s xml:id="SW1">For a long time I used to go to bed early.</s>   <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>  </p> <!-- ... --> </div>
NoteMay contain one or more <link/> elements only, optionally with interspersed pointer elements.A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

Appendix B.1.103 <list>

<list> contains any sequence of items organized as a list. [3.7. Lists]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
typedescribes the nature of the items in the list.
Derived fromatt.typed
StatusOptional
Datatype
data.enumerated
Suggested values include:
gloss
each list item glosses some term or concept, which is given by a label element preceding the list item.
index
each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
each list item is a step in a sequence of instructions, as in a recipe.
litany
each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
NotePrevious versions of these Guidelines recommended the use of type on <list> to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.
NoteThe formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.
Member of
Contained by
May contain
Declaration
element list
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type
   {
      "gloss" | "index" | "instructions" | "litany" | "syllogism" | xsd:Name
   }?,
   (
      ( ( model.divTop ) | ( model.global ) )*,
      (
         ( item, model.global* )+
       | (
            headLabel?,
            headItem?,
            ( label, model.global*, item, model.global* )+
         )
      ),
      ( ( model.divBottom ), model.global* )*
   )
}
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert></sch:rule>
Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
ExampleThe following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
NoteMay contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Appendix B.1.104 <listChange>

<listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 11.7. Changes]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
orderedindicates whether the ordering of its child <change> elements is to be considered significant or not
StatusOptional
Datatype
data.truthValue
Defaulttrue
Contained by
May contain
Declaration
element listChange
{
   att.global.attributes,
   att.sortable.attributes,
   attribute ordered { data.truthValue }?,
   ( listChange | change )+
}
Example
<revisionDesc>  <listChange>   <change when="1991-11-11who="#LB"> deleted chapter 10 </change>   <change when="1991-11-02who="#MSM"> completed first draft </change>  </listChange> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange ordered="true">    <change xml:id="CHG-1">First stage, written in ink by a writer</change>    <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>    <change xml:id="CHG-3">Fixation of the revised passages and further revisions by        Goethe using ink</change>    <change xml:id="CHG-4">Addition of another stanza in a different hand,        probably at a later stage</change>   </listChange>  </creation> </profileDesc>
NoteWhen this element appears within the <creation> element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text.

Appendix B.1.105 <listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [13.3.1. Basic Principles]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.declarable (@default) att.sortable (@sortKey)
Member of
Contained by
May contain
core: head
namesdates: event listEvent
Declaration
element listEvent
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   ( model.headLike*, ( event | listEvent )+, ( relation | listRelation )* )
}
Example
<listEvent>  <head>Battles of the American Civil War: Kentucky</head>  <event xml:id="event01when="1861-09-19">   <label>Barbourville</label>   <desc>The Battle of Barbourville was one of the early engagements of      the American Civil War. It occurred September 19, 1861, in Knox      County, Kentucky during the campaign known as the Kentucky Confederate      Offensive. The battle is considered the first Confederate victory in      the commonwealth, and threw a scare into Federal commanders, who      rushed troops to central Kentucky in an effort to repel the invasion,      which was finally thwarted at the <ref target="#event02">Battle of        Camp Wildcat</ref> in October.</desc>  </event>  <event xml:id="event02when="1861-10-21">   <label>Camp Wild Cat</label>   <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp      Wild Cat) was one of the early engagements of the American Civil      War. It occurred October 21, 1861, in northern Laurel County, Kentucky      during the campaign known as the Kentucky Confederate Offensive. The      battle is considered one of the very first Union victories, and marked      the first engagement of troops in the commonwealth of Kentucky.</desc>  </event>  <event xml:id="event03from="1864-06-11to="1864-06-12">   <label>Cynthiana</label>   <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement      during the American Civil War that was fought on June 11 and 12, 1864,      in Harrison County, Kentucky, near the town of Cynthiana. A part of      Confederate Brigadier General John Hunt Morgan's 1864 Raid into      Kentucky, the battle resulted in a victory by Union forces over the      raiders and saved the town from capture.</desc>  </event> </listEvent>

Appendix B.1.106 <listOrg>

<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [13.2.2. Organizational Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.declarable (@default) att.sortable (@sortKey)
Member of
Contained by
May contain
core: head
namesdates: listOrg org
Declaration
element listOrg
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   ( model.headLike*, ( org | listOrg )+, ( relation | listRelation )* )
}
Example
<listOrg>  <head>Libyans</head>  <org>   <orgName>Adyrmachidae</orgName>   <desc>These people have, in most points, the same customs as the Egyptians, but      use the costume of the Libyans. Their women wear on each leg a ring made of      bronze [...]</desc>  </org>  <org>   <orgName>Nasamonians</orgName>   <desc>In summer they leave their flocks and herds upon the sea-shore, and go up      the country to a place called Augila, where they gather the dates from the      palms [...]</desc>  </org>  <org>   <orgName>Garamantians</orgName>   <desc>[...] avoid all society or intercourse with their fellow-men, have no      weapon of war, and do not know how to defend themselves. [...]</desc> <!-- ... -->  </org> </listOrg>
NoteThe type attribute may be used to distinguish lists of organizations of a particular type if convenient.

Appendix B.1.107 <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.declarable (@default) att.sortable (@sortKey)
Member of
Contained by
May contain
core: head
namesdates: listPerson org person
Declaration
element listPerson
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      ( model.personLike | listPerson )+,
      ( relation | listRelation )*
   )
}
Example
<listPerson type="respondents">  <personGrp xml:id="PXXX"/>  <person xml:id="P1234sex="2age="mid"/>  <person xml:id="P4332sex="1age="mid"/>  <listRelation>   <relation type="personalname="spousemutual="#P1234 #P4332"/>  </listRelation> </listPerson>
NoteThe type attribute may be used to distinguish lists of people of a particular type if convenient.

Appendix B.1.108 <listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.declarable (@default) att.sortable (@sortKey)
Member of
Contained by
May contain
core: head
namesdates: listPlace place
Declaration
element listPlace
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      ( model.placeLike | listPlace )+,
      ( relation | listRelation )*
   )
}
Example
<listPlace type="offshoreIslands">  <place>   <placeName>La roche qui pleure</placeName>  </place>  <place>   <placeName>Ile aux cerfs</placeName>  </place> </listPlace>

Appendix B.1.109 <listPrefixDef>

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in data.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element listPrefixDef
{
   att.global.attributes,
   ( ( prefixDef | listPrefixDef )+ )
}
ExampleIn this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psnmatchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="biblmatchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>

Appendix B.1.110 <listTranspose>

<listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [11.3.4.5. Transpositions]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
transcr: transpose
Declaration
element listTranspose { att.global.attributes, transpose+ }
Example
<listTranspose>  <transpose>   <ptr target="#ib02"/>   <ptr target="#ib01"/>  </transpose> </listTranspose>
This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source.

Appendix B.1.111 <location>

<location> defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [13.3.4. Places]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
May contain
Declaration
element location
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   (
      precision
    | model.labelLikemodel.placeNamePartmodel.offsetLikemodel.measureLikemodel.addressLikemodel.noteLikemodel.biblLike
   )*
}
Example
<place>  <placeName>Abbey Dore</placeName>  <location>   <geo>51.969604 -2.893146</geo>  </location> </place>
Example
<place type="building">  <placeName>Brasserie Georges</placeName>  <location>   <country key="FR"/>   <settlement type="city">Lyon</settlement>   <district type="arrondissement">Perrache</district>   <placeName type="street">Rue de la Charité</placeName>  </location> </place>
Example
<place type="imaginary">  <placeName>Atlantis</placeName>  <location>   <offset>beyond</offset>   <placeName>The Pillars of <persName>Hercules</persName>   </placeName>  </location> </place>

Appendix B.1.112 <locus>

<locus> defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@target)
schemeidentifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
StatusOptional
Datatype
data.pointer
fromspecifies the starting point of the location in a normalized form, typically a page number.
StatusOptional
Datatype
data.word
tospecifies the end-point of the location in a normalized form, typically as a page number.
StatusOptional
Datatype
data.word
Member of
Contained by
May containCharacter data only
Declaration
element locus
{
   att.global.attributes,
   att.pointing.attributes,
   attribute scheme { data.pointer }?,
   attribute from { data.word }?,
   attribute to { data.word }?,
   macro.xtext
}
Example
<!-- within ms description --><msItem n="1">  <locus target="#F1r #F1v #F2rfrom="1rto="2r">ff. 1r-2r</locus>  <author>Ben Jonson</author>  <title>Ode to himself</title>  <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>  <incipit>Com leaue the loathed stage</incipit>  <explicit>And see his chariot triumph ore his wayne.</explicit>  <bibl>   <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... -->
ExampleThe facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:
<msItem>  <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>  <title>Birds Praise of Love</title>  <bibl>   <title>IMEV</title>   <biblScope>1506</biblScope>  </bibl> </msItem>
NoteThe target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the first example above. To associate a <locus> element with a page image or other comparable representation, the global facs attribute should be used instead, as shown in the second example. Use of the target attribute to indicate an image is strongly deprecated. The facs attribute may be used to indicate one or more image files, as above, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone> element, <graphic>, or <binaryObject> elements.
NoteWhen the location being defined consists of a single page, use the from and to attributes with an identical value. When no clear endpoint is given the from attribute should be used without to. For example, if the manuscript description being transcribed has ‘p. 3ff’ as the locus.

Appendix B.1.113 <locusGrp>

<locusGrp> groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation. [10.3.5. References to Locations within a Manuscript]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
schemeidentifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
StatusOptional
Datatype
data.pointer
Member of
Contained by
May contain
msdescription: locus
Declaration
element locusGrp
{
   att.global.attributes,
   attribute scheme { data.pointer }?,
   locus+
}
Example
<msItem>  <locusGrp>   <locus from="13to="26">Bl. 13--26</locus>   <locus from="37to="58">37--58</locus>   <locus from="82to="96">82--96</locus>  </locusGrp>  <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note> </msItem>

Appendix B.1.114 <material>

<material> contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
Member of
Contained by
May contain
Declaration
element material
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}
Example
<physDesc>  <p>   <material>Parchment</material> leaves with a  <material>sharkskin</material> binding.</p> </physDesc>
NoteThe ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally.

Appendix B.1.115 <measure>

<measure> contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.5.3. Numbers and Measures]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.measurement (@unit, @quantity, @commodity)
typespecifies the type of measurement in any convenient typology.
StatusOptional
Datatype
data.enumerated
Member of
Contained by
May contain
Declaration
element measure
{
   att.global.attributes,
   att.measurement.attributes,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Example
<measure type="weight">  <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="area">2 merks of old extent</measure>
Example
<measure quantity="40unit="hogsheadcommodity="rum">2 score hh rum</measure> <measure quantity="12unit="countcommodity="roses">1 doz. roses</measure> <measure quantity="1unit="countcommodity="tulips">a yellow tulip</measure>

Appendix B.1.116 <measureGrp>

<measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [10.3.4. Dimensions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.measurement (@unit, @quantity, @commodity) att.typed (@type)
Member of
Contained by
May contain
msdescription: depth dim height width
namesdates: geo
Declaration
element measureGrp
{
   att.global.attributes,
   att.measurement.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.measureLike )*
}
Example
<measureGrp type="leavesunit="mm">  <height scope="range">157-160</height>  <width quantity="105"/> </measureGrp> <measureGrp type="ruledAreaunit="mm">  <height scope="mostquantity="90"/>  <width scope="mostquantity="48"/> </measureGrp> <measureGrp type="boxunit="in">  <height quantity="12"/>  <width quantity="10"/>  <depth quantity="6"/> </measureGrp>

Appendix B.1.117 <metamark>

<metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.spanning (@spanTo) att.placement (@place) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
functiondescribes the function (for example status, insertion, deletion, transposition) of the mark.
StatusOptional
Datatype
data.word
targetidentifies one or more elements to which the function indicated by the metamark applies.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
May contain
Declaration
element metamark
{
   att.spanning.attributes,
   att.placement.attributes,
   att.global.attributes,
   attribute function { data.word }?,
   attribute target { list { data.pointer+ } }?,
   macro.specialPara
}

Appendix B.1.118 <milestone/>

<milestone/> marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.10.3. Milestone Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.milestoneUnit (@unit) att.typed (@type) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Declaration
element milestone
{
   att.global.attributes,
   att.milestoneUnit.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}
Example
<milestone n="23ed="Launit="Dreissiger"/> ... <milestone n="24ed="AVunit="verse"/> ...
NoteFor this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.The order in which milestone elements are given at a given point is not normally significant.

Appendix B.1.119 <mod>

<mod> represents any kind of modification identified within a single document. [11.3.4.1. Generic Modification]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May contain
Declaration
element mod
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   macro.paraContent
}
Example
<mod type="subst">  <add>pleasing</add>  <del>agreable</del> </mod>

Appendix B.1.120 <monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.11.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
Declaration
element monogr
{
   att.global.attributes,
   (
      (
         (
            ( author | editor | meeting | respStmt ),
            ( author | editor | meeting | respStmt )*,
            title+,
            ( model.ptrLike | idno | textLang | editor | respStmt )*
         )
       | (
            ( title | model.ptrLike | idno )+,
            ( textLang | author | editor | meeting | respStmt )*
         )
       | ( authority, idno )
      )?,
      availability*,
      model.noteLike*,
      (
         edition,
         ( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
      )*,
      imprint,
      ( imprint | extent | biblScope )*
   )
}
Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope unit="pagefrom="377to="380">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title type="mainlevel="m">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title type="mainlevel="s">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
NoteMay contain specialized bibliographic elements, in a prescribed order.The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item.

Appendix B.1.121 <msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.msExcerpt (@defective)
classidentifies the text types or classifications applicable to this object by pointing to other elements or resources defining the classification concerned.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Contained by
msdescription: msDesc msPart
May contain
core: p
linking: ab
msdescription: msItem summary
Declaration
element msContents
{
   att.global.attributes,
   att.msExcerpt.attributes,
   attribute class { list { data.pointer+ } }?,
   (
      model.pLike+
    | ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* )
   )
}
Example
<msContents class="#sermons">  <p>A collection of Lollard sermons</p> </msContents>
Example
<msContents>  <msItem n="1">   <locus>fols. 5r-7v</locus>   <title>An ABC</title>   <bibl>    <title>IMEV</title>    <biblScope>239</biblScope>   </bibl>  </msItem>  <msItem n="2">   <locus>fols. 7v-8v</locus>   <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>   <bibl>    <title>IMEV</title>    <biblScope>3747</biblScope>   </bibl>  </msItem>  <msItem n="3">   <locus>fol. 8v</locus>   <title>Truth</title>   <bibl>    <title>IMEV</title>    <biblScope>809</biblScope>   </bibl>  </msItem>  <msItem n="4">   <locus>fols. 8v-10v</locus>   <title>Birds Praise of Love</title>   <bibl>    <title>IMEV</title>    <biblScope>1506</biblScope>   </bibl>  </msItem>  <msItem n="5">   <locus>fols. 10v-11v</locus>   <title xml:lang="la">De amico ad amicam</title>   <title xml:lang="la">Responcio</title>   <bibl>    <title>IMEV</title>    <biblScope>16 &amp; 19</biblScope>   </bibl>  </msItem>  <msItem n="6">   <locus>fols. 14r-126v</locus>   <title>Troilus and Criseyde</title>   <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>  </msItem> </msContents>
NoteUnless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema.

Appendix B.1.122 <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object. [10.1. Overview]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.typed (@type)
Member of
Contained by
May contain
Declaration
element msDesc
{
   att.global.attributes,
   att.sortable.attributes,
   att.typed.attributes,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents?, physDesc?, history?, additional?, msPart* )
      )
   )
}
Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>

Appendix B.1.123 <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript being described. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: bibl
msdescription: msDesc msPart
May contain
Declaration
element msIdentifier
{
   att.global.attributes,
   (
      (
         model.placeNamePart_sequenceOptional,
         institution?,
         repository?,
         collection*,
         idno?
      ),
      ( msName | altIdentifier )*
   )
}
Schematron
<s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location of some type, or a manuscript name</s:report>
Example
<msIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </msIdentifier>

Appendix B.1.124 <msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part. [10.6.1. The msItem and msItemStruct Elements]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.msExcerpt (@defective)
classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
msdescription: msContents msItem
May contain
Declaration
element msItem
{
   att.global.attributes,
   att.msExcerpt.attributes,
   attribute class { list { data.pointer+ } }?,
   (
      ( locus | locusGrp )*,
      (
         model.pLike+
       | ( model.titlepagePart | model.msItemPart | model.global )+
      )
   )
}
Example
<msItem class="#saga">  <locus>ff. 1r-24v</locus>  <title>Agrip af Noregs konunga sögum</title>  <incipit>regi oc h<ex>ann</ex> setiho  <gap reason="illegibleextent="7"/>sc    heim se<ex>m</ex> þio</incipit>  <explicit>h<ex>on</ex> hev<ex>er</ex>   <ex>oc</ex>þa buit hesta .ij. aNan viþ    fé enh<ex>on</ex>o<ex>m</ex> aNan til    reiþ<ex>ar</ex>  </explicit>  <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem>

Appendix B.1.125 <msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
msdescription: msIdentifier
May containCharacter data only
Declaration
element msName { att.global.attributes, att.typed.attributes, macro.xtext }
Example
<msName>The Vercelli Book</msName>

Appendix B.1.126 <msPart>

<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, now forming part of a composite manuscript. [10.10. Manuscript Parts]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msPart
May contain
Declaration
element msPart
{
   att.global.attributes,
   (
      ( altIdentifier | msIdentifier ),
      model.headLike*,
      (
         model.pLike+
       | ( msContents?, physDesc?, history?, additional?, msPart* )
      )
   )
}
SchematronThe <msIdentifier> element is now allowed as a child of <msPart>, and it (with its <altIdentifier> children if needed) should be used instead of an <altIdentifier> directly within <msPart>.
<sch:report test="child::tei:altIdentifier"  role="nonfatal">WARNING: use of deprecated method — the use of the altIdentifier element as a direct child of the msPart element will be removed from the TEI on 2016-09-09</sch:report>
Example
<msPart>  <msIdentifier>   <idno>A</idno>   <altIdentifier type="catalog">    <collection>Becker</collection>    <idno>48, Nr. 145</idno>   </altIdentifier>   <altIdentifier type="catalog">    <collection>Wiener Liste</collection>    <idno>4°5</idno>   </altIdentifier>  </msIdentifier>  <head>   <title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>   <origPlace key="tgn_7008085">Weissenburg (?)</origPlace>   <origDate notBefore="0801notAfter="0815">IX. Jh., Anfang</origDate>  </head> </msPart>
Example
<msDesc>  <msIdentifier>   <settlement>Amiens</settlement>   <repository>Bibliothèque Municipale</repository>   <idno>MS 3</idno>   <msName>Maurdramnus Bible</msName>  </msIdentifier> <!-- other elements here -->  <msPart>   <altIdentifier>    <idno>MS 6</idno>   </altIdentifier> <!-- other information specific to this part here -->  </msPart> <!-- more parts here --> </msDesc>
NoteAs this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple <altIdentifier> rather than using the more structured <msIdentifier> element. This usage is however deprecated.

Appendix B.1.127 <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element name
{
   att.global.attributes,
   att.personal.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
NoteProper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

Appendix B.1.128 <nationality>

<nationality> contains an informal description of a person's present or past nationality or citizenship. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
namesdates: person
May contain
Declaration
element nationality
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<nationality key="USnotBefore="1966"> Obtained US Citizenship in 1966</nationality>

Appendix B.1.129 <note>

<note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place) att.pointing (@target) att.source (@source) att.typed (@type)
anchoredindicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatype
data.truthValue
Defaulttrue
NoteIn modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.
targetEndpoints to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
NoteThis attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().
Member of
Contained by
May contain
Declaration
element note
{
   att.global.attributes,
   att.placement.attributes,
   att.pointing.attributes,
   att.source.attributes,
   att.typed.attributes,
   attribute anchored { data.truthValue }?,
   attribute targetEnd { list { data.pointer+ } }?,
   macro.specialPara
}
ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="glossresp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance.
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header:
<respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

Appendix B.1.130 <notesStmt>

<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: fileDesc
May contain
core: note
Declaration
element notesStmt { att.global.attributes, ( model.noteLike | relatedItem )+ }
Example
<notesStmt>  <note>Historical commentary provided by Mark Cohen</note>  <note>OCR scanning done at University of Toronto</note> </notesStmt>
NoteInformation of different kinds should not be grouped together into the same note.

Appendix B.1.131 <objectDesc>

<objectDesc> contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
forma short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
StatusOptional
Datatype
data.enumerated
NoteDefinitions for the terms used may typically be provided by a <valList> element in the project schema specification.
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
msdescription: layoutDesc supportDesc
Declaration
element objectDesc
{
   att.global.attributes,
   attribute form { data.enumerated }?,
   ( model.pLike+ | ( supportDesc?, layoutDesc? ) )
}
Example
<objectDesc form="codex">  <supportDesc material="mixed">   <p>Early modern   <material>parchment</material> and   <material>paper</material>.</p>  </supportDesc>  <layoutDesc>   <layout ruledLines="25 32"/>  </layoutDesc> </objectDesc>

Appendix B.1.132 <objectType>

<objectType> contains a word or phrase describing the type of object being referred to. [10.3.2. Material and Object Type]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
Member of
Contained by
May contain
Declaration
element objectType
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}
Example
<physDesc>  <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p> </physDesc>
Example
<physDesc>  <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.  </p> </physDesc>
NoteThe ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

Appendix B.1.133 <occupation>

<occupation> contains an informal description of a person's trade, profession or occupation. [15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.naming (@role) (att.canonical (@ref))
schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
StatusOptional
Datatype
data.pointer
codeidentifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatype
data.pointer
Member of
Contained by
namesdates: person
May contain
Declaration
element occupation
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   attribute scheme { data.pointer }?,
   attribute code { data.pointer }?,
   macro.phraseSeq
}
Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomycode="#acc">accountant</occupation>
NoteThe content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Appendix B.1.134 <offset>

<offset> marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or times involved in the expression. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element offset
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<placeName key="NRPA1">  <offset>50 metres below the summit of</offset>  <geogName>   <geogFeat>Mount</geogFeat>   <name>Sinai</name>  </geogName> </placeName>

Appendix B.1.135 <opener>

<opener> groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
textstructure: body div postscript
May contain
Declaration
element opener
{
   att.global.attributes,
   (
      text
    | model.gLike
    | model.phrase
    | argument
    | byline
    | dateline
    | epigraph
    | salutesignedmodel.global
   )*
}
Example
<opener>  <dateline>Walden, this 29. of August 1592</dateline> </opener>
Example
<opener>  <dateline>   <name type="place">Great Marlborough Street</name>   <date>November 11, 1848</date>  </dateline>  <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p>

Appendix B.1.136 <org>

<org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [13.2.2. Organizational Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.sortable (@sortKey)
rolespecifies a primary role or classification for the organization.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
NoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, family group, or political party, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
Member of
Contained by
namesdates: listOrg listPerson org
May contain
Declaration
element org
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   attribute role { list { data.word+ } }?,
   (
      model.headLike*,
      (
         ( model.pLike* )
       | (
            model.labelLikemodel.nameLikemodel.placeLikemodel.orgPartmodel.milestoneLike
         )*
      ),
      ( model.noteLike | model.biblLike | linkGrp | link )*,
      model.personLike*
   )
}
Example
<org xml:id="JAMs">  <orgName>Justified Ancients of Mummu</orgName>  <desc>An underground anarchist collective spearheaded by <persName>Hagbard      Celine</persName>, who fight the Illuminati from a golden submarine, the  <name>Leif Ericson</name>  </desc>  <bibl>   <author>Robert Shea</author>   <author>Robert Anton Wilson</author>   <title>The Illuminatus! Trilogy</title>  </bibl> </org>

Appendix B.1.137 <orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element orgName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName>....

Appendix B.1.138 <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.4.2. Regularization and Normalization 12. Critical Apparatus]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source)
Member of
Contained by
May contain
Declaration
element orig
{
   att.global.attributes,
   att.source.attributes,
   macro.paraContent
}
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>

Appendix B.1.139 <origDate>

<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part. [10.3.1. Origination]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element origDate
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}
Example
<origDate notBefore="-0300notAfter="-0200">3rd century BCE</origDate>

Appendix B.1.140 <origPlace>

<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript or manuscript part. [10.3.1. Origination]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element origPlace
{
   att.global.attributes,
   att.naming.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<origPlace>Birmingham</origPlace>
NoteThe type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

Appendix B.1.141 <origin>

<origin> contains any descriptive or other information concerning the origin of a manuscript or manuscript part. [10.8. History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Contained by
msdescription: history
May contain
Declaration
element origin
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   macro.specialPara
}
Example
<origin notBefore="1802notAfter="1845evidence="internal"  resp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>. </origin>

Appendix B.1.142 <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element p { att.global.attributes, macro.paraContent }
Schematron
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure)"> Abstract model violation: Paragraphs may not contain other paragraphs or ab elements. </s:report>
Schematron
<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab. </s:report>
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>

Appendix B.1.143 <pb/>

<pb/> (page break) marks the start of a new page in a paginated document. [3.10.3. Milestone Elements]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Declaration
element pb
{
   att.global.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}
ExamplePage numbers may vary in different editions of a text.
<p> ... <pb n="145ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
ExampleA page break may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>  <pb n="1facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb n="2facs="page2.png"/> <!-- similarly, for page 2 -->  <p> <!-- ... -->  </p> </body>
NoteA <pb/> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb/> element itself.The type attribute may be used to characterize the page break in any respect, for example as word-breaking or not.

Appendix B.1.144 <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element persName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>

Appendix B.1.145 <person>

<person> provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.sortable (@sortKey)
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of 
data.enumerated
separated by whitespace
NoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
sexspecifies the sex of the person.
StatusOptional
Datatype1–∞ occurrences of 
data.sex
separated by whitespace
NoteValues for this attribute may be locally defined by a project, or may refer to an external standard, such as vCard's sex property http://microformats.org/wiki/gender-formats (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes http://standards.iso.org/ittf/PubliclyAvailableStandards/c036266_ISO_IEC_5218_2004(E_F).zip (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People http://transhealth.ucsf.edu/trans?page=lib-data-collection.
agespecifies an age group for the person.
StatusOptional
Datatype
data.enumerated
NoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
Member of
Contained by
namesdates: listPerson org
May contain
Declaration
element person
{
   att.global.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   attribute role { list { data.enumerated+ } }?,
   attribute sex { list { data.sex+ } }?,
   attribute age { data.enumerated }?,
   ( model.pLike+ | ( model.personPart | model.global )* )
}
Example
<person sex="Fage="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersexrole="godage="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01sex="1role="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
NoteMay contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Appendix B.1.146 <physDesc>

<physDesc> (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msPart
May contain
Declaration
element physDesc
{
   att.global.attributes,
   ( model.pLike*, ( model.physDescPart_sequenceOptional ) )
}
Example
<physDesc>  <objectDesc form="codex">   <supportDesc material="perg">    <support>Parchment.</support>    <extent>i + 55 leaves    <dimensions scope="alltype="leafunit="inch">      <height></height>      <width>5⅜</width>     </dimensions>    </extent>   </supportDesc>   <layoutDesc>    <layout columns="2">In double columns.</layout>   </layoutDesc>  </objectDesc>  <handDesc>   <p>Written in more than one hand.</p>  </handDesc>  <decoDesc>   <p>With a few coloured capitals.</p>  </decoDesc> </physDesc>

Appendix B.1.147 <place>

<place> contains data about a geographic location [13.3.4. Places]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.sortable (@sortKey)
Member of
Contained by
namesdates: listPlace org place
May contain
Declaration
element place
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      (
         ( model.pLike* )
       | ( model.labelLike | model.placeStateLike | model.eventLike )*
      ),
      ( model.noteLike | model.biblLike | idno | linkGrp | link )*,
      ( model.placeLike | listPlace )*
   )
}
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>

Appendix B.1.148 <placeName>

<placeName> contains an absolute or relative place name. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element placeName
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>

Appendix B.1.149 <postscript>

<postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
figures: figure table
textstructure: back body div front postscript
May contain
Declaration
element postscript
{
   att.global.attributes,
   (
      ( model.global | model.divTopPart )*,
      ( model.common ),
      ( model.global | model.common )*,
      ( ( model.divBottomPart ), model.global* )*
   )
}
Example
<div type="letter">  <opener>   <dateline>    <placeName>Rimaone</placeName>    <date when="2006-11-21">21 Nov 06</date>   </dateline>   <salute>Dear Susan,</salute>  </opener>  <p>Thank you very much for the assistance splitting those    logs. I'm sorry about the misunderstanding as to the size of    the task. I really was not asking for help, only to borrow the    axe. Hope you had fun in any case.</p>  <closer>   <salute>Sincerely yours,</salute>   <signed>Seymour</signed>  </closer>  <postscript>   <label>P.S.</label>   <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p>  </postscript> </div>

Appendix B.1.150 <prefixDef>

<prefixDef> (prefixing scheme used in data.pointer values) defines a prefixing scheme used in data.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.patternReplacement (@matchPattern, @replacementPattern)
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatype
data.name
Contained by
May contain
core: p
linking: ab
Declaration
element prefixDef
{
   att.global.attributes,
   att.patternReplacement.attributes,
   attribute ident { data.name },
   model.pLike*
}
Example
<prefixDef ident="refmatchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
NoteThe abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Appendix B.1.151 <principal>

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
Member of
Contained by
core: bibl
msdescription: msItem
May contain
Declaration
element principal
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq.limited
}
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>

Appendix B.1.152 <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: teiHeader
May contain
Declaration
element profileDesc { att.global.attributes, ( model.profileDescPart* ) }
Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
NoteAlthough the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.In earlier versions of these Guidelines, it was required that the <creation> element appear first.

Appendix B.1.153 <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Declaration
element projectDesc
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>

Appendix B.1.154 <provenance>

<provenance> contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript or manuscript part, after its creation but before its acquisition. [10.8. History]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.typed (@type) att.source (@source)
Contained by
msdescription: history
May contain
Declaration
element provenance
{
   att.global.attributes,
   att.datable.attributes,
   att.typed.attributes,
   att.source.attributes,
   macro.specialPara
}
Example
<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance> <provenance>Sold at Sothebys in 1899.</provenance>

Appendix B.1.155 <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
May contain
Declaration
element pubPlace
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>

Appendix B.1.156 <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: fileDesc
May contain
Declaration
element publicationStmt
{
   att.global.attributes,
   (
      (
         ( model.publicationStmtPart.agency ),
         model.publicationStmtPart.detail*
      )+
    | model.pLike+
   )
}
Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
NoteWhere a publication statement contains several members of the model.publicationStmtPart classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Appendix B.1.157 <publisher>

<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element publisher { att.global.attributes, macro.phraseSeq }
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
NoteUse the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Appendix B.1.158 <q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.ascribed (@who) att.source (@source)
typemay be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatype
data.enumerated
Suggested values include:
spoken
representation of speech
thought
representation of thought, e.g. internal monologue
written
quotation from a written source
soCalled
authorial distance
foreign
distinct
linguistically distinct
term
technical term
emph
rhetorically emphasized
mentioned
refering to itself, not its normal referent
Member of
Contained by
May contain
Declaration
element q
{
   att.global.attributes,
   att.ascribed.attributes,
   att.source.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
    | xsd:Name
   }?,
   macro.specialPara
}
Example
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
NoteMay be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.

Appendix B.1.159 <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.msExcerpt (@defective) att.source (@source)
Member of
Contained by
May contain
Declaration
element quote
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   att.source.attributes,
   macro.specialPara
}
Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
NoteIf a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Appendix B.1.160 <rdg>

<rdg> (reading) contains a single reading within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.textCritical (@type, @cause, @varSeq, @hand) (att.source (@source)) att.witnessed (@wit)
Member of
Contained by
textcrit: app
May contain
Declaration
element rdg
{
   att.global.attributes,
   att.textCritical.attributes,
   att.witnessed.attributes,
   (
      text
    | model.divLikemodel.divPart
    | model.gLike
    | model.phrasemodel.intermodel.global
    | model.rdgPart
   )*
}
Example
<rdg wit="#Ra2">Eryment</rdg>

Appendix B.1.161 <recordHist>

<recordHist> (recorded history) provides information about the source and revision status of the parent manuscript description itself. [10.9.1. Administrative Information]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: adminInfo
May contain
core: p
header: change
linking: ab
Declaration
element recordHist
{
   att.global.attributes,
   ( model.pLike+ | ( source, change* ) )
}
Example
<recordHist>  <source>   <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research      by P.M.W.Robinson</p>  </source>  <change when="1999-06-23">   <name>LDB</name> (editor)    checked examples against DTD version 3.6  </change> </recordHist>

Appendix B.1.162 <redo/>

<redo/> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
targetpoints to one or more elements representing the interventions which are being reasserted.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
May containEmpty element
Declaration
element redo
{
   att.global.attributes,
   att.spanning.attributes,
   att.transcriptional.attributes,
   attribute target { list { data.pointer+ } }?,
   empty
}
Example
<line>  <redo hand="#g_ttarget="#redo-1cause="fix"/>  <mod xml:id="redo-1rend="strikethroughspanTo="#anchor-1"   hand="#g_bl"/>Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken </line> <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/> </line>
This encoding represents the following sequence of events:
  • "Ihr hagren, triſten, krummgezog nenener Nacken/ Wenn ihr nur piepſet iſt die Welt ſchon matt." is written
  • the redundant letters "nen" in "nenener" are deleted
  • the whole passage is deleted by hand g_bl using strikethrough
  • the deletion is reasserted by another hand (identified here as g_t)

Appendix B.1.163 <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@target) att.typed (@type)
Member of
Contained by
May contain
Declaration
element ref
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   macro.paraContent
}
Schematron
<s:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <s:name/></s:report>
Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
NoteThe target and cRef attributes are mutually exclusive.

Appendix B.1.164 <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.4.2. Regularization and Normalization 12. Critical Apparatus]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Declaration
element reg
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>

Appendix B.1.165 <region>

<region> contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
May contain
Declaration
element region
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}
Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>

Appendix B.1.166 <rendition>

<rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.styleDef (@scheme, @schemeVersion)
scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatype
data.enumerated
Sample values include:
first-line
styling applies to the first line of the target element
first-letter
styling applies to the first letter of the target element
before
styling should be applied immediately before the content of the target element
after
styling should be applied immediately after the content of the target element
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatype
data.text
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
NoteSince the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.
NoteWhile rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.
Contained by
header: tagsDecl
May contain
Declaration
element rendition
{
   att.global.attributes,
   att.styleDef.attributes,
   attribute scope { data.enumerated }?,
   attribute selector { data.text }?,
   macro.limitedContent
}
Example
<tagsDecl>  <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>  <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>  <rendition xml:id="r-largescheme="css">font-size: large;</rendition>  <rendition xml:id="initcapsscope="first-letterscheme="css">font-size: xx-large</rendition> </tagsDecl>
NoteThe present release of these Guidelines does not specify the content of this element in any further detail. It may be used to hold a description of the default rendition to be associated with the specified element, expressed in running prose, or in some more formal language such as CSS.

Appendix B.1.167 <repository>

<repository> contains the name of a repository within which manuscripts are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref))
Contained by
May containCharacter data only
Declaration
element repository
{
   att.global.attributes,
   att.naming.attributes,
   macro.xtext
}
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>

Appendix B.1.168 <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Contained by
core: respStmt
May contain
Declaration
element resp
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   macro.phraseSeq.limited
}
Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
NoteThe attributes key or ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form, by referring directly (using ref) or indirectly (using key) to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Appendix B.1.169 <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
Member of
Contained by
msdescription: msItem
May contain
core: name resp
namesdates: orgName persName
Declaration
element respStmt
{
   att.global.attributes,
   att.canonical.attributes,
   ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) )
}
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>

Appendix B.1.170 <restore>

<restore> indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction. [11.3.1.6. Cancellation of Deletions and Other Markings]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element restore
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   macro.paraContent
}
Example
For I hate this <restore hand="#dhltype="marginalStetNote">  <del>my</del> </restore> body
NoteOn this element, the type attribute categorizes the way that the cancelled intervention has been indicated in some way, for example by means of a marginal note, over-inking, additional markup, etc.

Appendix B.1.171 <retrace>

<retrace> contains a sequence of writing which has been retraced, for example by over-inking, to clarify or fix it. [11.3.4.3. Fixation and Clarification]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
Member of
Contained by
May contain
Declaration
element retrace
{
   att.global.attributes,
   att.spanning.attributes,
   att.transcriptional.attributes,
   macro.paraContent
}
NoteMultiple retraces are indicated by nesting one <retrace> within another. In principle, a retrace differs from a substitution in that second and subsequent rewrites do not materially alter the content of an element. Where minor changes have been made during the retracing action however these may be marked up using <del>, <add>, etc. with an appropriate value for the change attribute.

Appendix B.1.172 <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.docStatus (@status)
Contained by
header: teiHeader
May contain
core: list
Declaration
element revisionDesc
{
   att.global.attributes,
   att.docStatus.attributes,
   ( list | listChange | change+ )
}
Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
NoteIf present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.

Appendix B.1.173 <roleName>

<roleName> contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element roleName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<persName>  <forename>William</forename>  <surname>Poulteny</surname>  <roleName>Earl of Bath</roleName> </persName>
NoteA <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder.

Appendix B.1.174 <row>

<row> contains one row of a table. [14.1.1. TEI Tables]
Modulefigures — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (@role, @rows, @cols)
Contained by
figures: table
May contain
figures: cell
Declaration
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }
Example
<row role="data">  <cell role="label">Classics</cell>  <cell>Idle listless and unimproving</cell> </row>

Appendix B.1.175 <salute>

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
figures: figure table
textstructure: body closer div front opener
May contain
Declaration
element salute { att.global.attributes, macro.paraContent }
Example
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>

Appendix B.1.176 <scriptDesc>

<scriptDesc> contains a description of the scripts used in a manuscript or similar source. [10.7.2.1. Writing]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
msdescription: summary
Declaration
element scriptDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, scriptNote+ ) )
}
Example
<scriptDesc>  <p/> </scriptDesc>
Example
<scriptDesc>  <summary>Contains two distinct styles of scripts </summary>  <scriptNote xml:id="style-1">.</scriptNote>  <scriptNote xml:id="style-2">.</scriptNote> </scriptDesc>

Appendix B.1.177 <seal>

<seal> contains a description of one seal or similar attachment applied to a manuscript. [10.7.3.2. Seals]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
contemporaryspecifies whether or not the seal is contemporary with the item to which it is affixed
StatusOptional
Datatype
data.xTruthValue
Contained by
msdescription: sealDesc
May contain
core: p
linking: ab
msdescription: decoNote
Declaration
element seal
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute contemporary { data.xTruthValue }?,
   ( model.pLike | decoNote )+
}
Example
<seal n="2type="pendantsubtype="cauda_duplex">  <p>The seal of <name>Jens Olufsen</name> in black wax.    (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.    Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p> </seal>

Appendix B.1.178 <sealDesc>

<sealDesc> (seal description) describes the seals or other external items attached to a manuscript, either as a series of paragraphs or as a series of distinct <seal> elements, possibly with additional <decoNote>s. [10.7.3.2. Seals]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
Declaration
element sealDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, ( decoNote | seal | condition )+ ) )
}
Example
<sealDesc>  <seal type="pendantcontemporary="true">   <p>Green wax vertical oval seal attached at base.</p>  </seal> </sealDesc>
Example
<sealDesc>  <p>Parchment strip for seal in place; seal missing.</p> </sealDesc>

Appendix B.1.179 <seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
Modulelinking — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.source (@source)
Member of
Contained by
May contain
Declaration
element seg
{
   att.global.attributes,
   att.typed.attributes,
   att.source.attributes,
   macro.paraContent
}
Example
<seg>When are you leaving?</seg> <seg>Tomorrow.</seg>
Example
<s>  <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield. </s>
Example
<seg type="preamble">  <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>  <seg>Sinfiotli was the eldest of his sons ...</seg>  <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg>
NoteThe <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

Appendix B.1.180 <settlement>

<settlement> contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role) (att.canonical (@ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
May contain
Declaration
element settlement
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>

Appendix B.1.181 <sic>

<sic> (Latin for thus or so ) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. Apparent Errors]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source)
Member of
Contained by
May contain
Declaration
element sic { att.global.attributes, att.source.attributes, macro.paraContent }
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.

Appendix B.1.182 <signatures>

<signatures> contains discussion of the leaf or quire signatures found within a codex. [10.3.7. Catchwords, Signatures, Secundo Folio]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element signatures { att.global.attributes, macro.specialPara }
Example
<signatures>Quire and leaf signatures in letters, [b]-v, and roman numerals; those in quires 10 (1) and 17 (s) in red ink and different from others; every third quire also signed with red crayon in arabic numerals in the center lower margin of the first leaf recto: "2" for quire 4 (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for quire 10 (f. 65), "5," in a later hand, for quire 13 (f. 89), "6," in a later hand, for quire 16 (f. 113).</signatures>

Appendix B.1.183 <signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: list
figures: figure table
May contain
Declaration
element signed { att.global.attributes, macro.paraContent }
Example
<signed>Thine to command <name>Humph. Moseley</name> </signed>
Example
<closer>  <signed>Sign'd and Seal'd,  <list>    <item>John Bull,</item>    <item>Nic. Frog.</item>   </list>  </signed> </closer>

Appendix B.1.184 <sourceDesc>

<sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
Contained by
header: fileDesc
May contain
figures: table
linking: ab
msdescription: msDesc
Declaration
element sourceDesc
{
   att.global.attributes,
   att.declarable.attributes,
   (
      model.pLike+
    | ( model.biblLike | model.sourceDescPart | model.listLike )+
   )
}
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>

Appendix B.1.185 <space>

<space> indicates the location of a significant space in the text. [11.5.1. Space]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.typed (@type) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.source (@source) att.global (@xml:id, @n, @xml:lang) att.global.rendition (@rend, @style) att.global.linking (@corresp) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (resp, @cert)
resp(responsible party) (responsible party) indicates the individual responsible for identifying and measuring the space
Derived fromatt.global.responsibility
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
dim(dimension) indicates whether the space is horizontal or vertical.
StatusRecommended
Datatype
data.enumerated
Legal values are:
horizontal
the space is horizontal.
vertical
the space is vertical.
NoteFor irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.
Member of
Contained by
May contain
core: desc
Declaration
element space
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.linking.attribute.corresp,
   att.global.analytic.attribute.ana,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.typed.attributes,
   att.dimensions.attributes,
   att.source.attributes,
   attribute resp { list { data.pointer+ } }?,
   attribute dim { "horizontal" | "vertical" }?,
   ( model.descLike | model.certLike )*
}
Example
By god if wommen had writen storyes As <space quantity="7unit="minims"/> han within her oratoryes
Example
στρατηλάτ<space quantity="1unit="chars"/>ου
NoteThis element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

Appendix B.1.186 <stamp>

<stamp> contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
May contain
Declaration
element stamp
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}
Example
<rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/> SI NON LICET<lb/> NOBIS RO<lb/> manii imperii <stamp>Bodleian stamp</stamp>  <lb/> </rubric>

Appendix B.1.187 <state>

<state> contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type) att.naming (@role) (att.canonical (@ref))
Member of
Contained by
May contain
linking: ab
msdescription: msDesc
namesdates: state
Declaration
element state
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   att.naming.attributes,
   (
      precision*,
      (
         state+
       | (
            model.headLike*,
            model.pLike+,
            ( model.noteLike | model.biblLike )*
         )
       | ( ( model.labelLike | model.noteLike | model.biblLike )* )
      )
   )
}
Example
<state ref="#SCHOLtype="status">  <label>scholar</label> </state>
Example
<org>  <orgName notAfter="1960">The Silver Beetles</orgName>  <orgName notBefore="1960">The Beatles</orgName>  <state type="membershipfrom="1960-08to="1962-05">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Stuart Sutcliffe</persName>    <persName>Pete Best</persName>   </desc>  </state>  <state type="membershipnotBefore="1963">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Ringo Starr</persName>   </desc>  </state> </org>
NoteWhere there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Appendix B.1.188 <styleDefDecl>

<styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.styleDef (@scheme, @schemeVersion)
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Declaration
element styleDefDecl
{
   att.global.attributes,
   att.declarable.attributes,
   att.styleDef.attributes,
   model.pLike*
}
Example
<styleDefDecl scheme="cssschemeVersion="2.1"/> <!-- ... --> <tagsDecl>  <rendition xml:id="boldface">font-weight: bold;</rendition>  <rendition xml:id="italicstyle">font-style: italic;</rendition> </tagsDecl>

Appendix B.1.189 <subst>

<subst> (substitution) groups one or more deletions with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
Member of
Contained by
May contain
linking: anchor
transcr: fw
Declaration
element subst
{
   att.global.attributes,
   att.transcriptional.attributes,
   ( add | del | model.milestoneLike )+
}
Schematron
<s:assert test="child::tei:add and child::tei:del"> <s:name/> must have at least one child add and at least one child del</s:assert>
Example
... are all included. <del hand="#RG">It is</del> <subst>  <add>T</add>  <del>t</del> </subst>he expressed
Example
that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>  <del>very</del>  <lb/>  <add>principally</add> </subst> remembered in her Will.
Example
<ab>τ<subst>   <add place="above">ῶν</add>   <del>α</del>  </subst> συνκυρόντ<subst>   <add place="above">ων</add>   <del>α</del>  </subst> ἐργαστηρί<subst>   <add place="above">ων</add>   <del>α</del>  </subst> </ab>
Example
<subst>  <del>   <gap reason="illegiblequantity="5unit="character"/>  </del>  <add>apple</add> </subst>

Appendix B.1.190 <summary>

<summary> contains an overview of the available information concerning some aspect of an item (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
Declaration
element summary { att.global.attributes, macro.specialPara }
Example
<summary>This item consists of three books with a prologue and an epilogue. </summary>
Example
<typeDesc>  <summary>Uses a mixture of Roman and Black Letter types.</summary>  <typeNote>Antiqua typeface, showing influence of Jenson's Venetian    fonts.</typeNote>  <typeNote>The black letter face is a variant of Schwabacher.</typeNote> </typeDesc>

Appendix B.1.191 <supplied>

<supplied> signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
reasonone or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
Member of
Contained by
May contain
Declaration
element supplied
{
   att.global.attributes,
   att.editLike.attributes,
   attribute reason { list { data.word+ } }?,
   macro.paraContent
}
Example
I am dr Sr yr <supplied reason="illegiblesource="#amanuensis_copy">very humble Servt</supplied> Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
NoteThe <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Appendix B.1.192 <support>

<support> contains a description of the materials etc. which make up the physical support for the written part of a manuscript. [10.7.1. Object Description]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: supportDesc
May contain
Declaration
element support { att.global.attributes, macro.specialPara }
Example
<objectDesc form="roll">  <supportDesc>   <support> Parchment roll with <material>silk</material> ribbons.   </support>  </supportDesc> </objectDesc>

Appendix B.1.193 <supportDesc>

<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript. [10.7.1. Object Description]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
materiala short project-defined name for the material composing the majority of the support
StatusOptional
Datatype
data.enumerated
Suggested values include:
paper
parch
(parchment)
mixed
Contained by
msdescription: objectDesc
May contain
core: p
linking: ab
msdescription: condition foliation support
Declaration
element supportDesc
{
   att.global.attributes,
   attribute material { "paper" | "parch" | "mixed" | xsd:Name }?,
   ( model.pLike+ | ( support?, extent?, foliation*, collation?, condition? ) )
}
Example
<supportDesc>  <support> Parchment roll with <material>silk</material> ribbons.  </support> </supportDesc>

Appendix B.1.194 <surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type)
attachmentdescribes the method by which this surface is or was connected to the main surface
StatusOptional
Datatype
data.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
StatusOptional
Datatype
data.truthValue
Contained by
May contain
Declaration
element surface
{
   att.global.attributes,
   att.coordinated.attributes,
   att.typed.attributes,
   attribute attachment { data.enumerated }?,
   attribute flipping { data.truthValue }?,
   (
      ( model.global | model.labelLike | model.graphicLike )*,
      ( ( zone | line | surface | surfaceGrp ), model.global* )*
   )
}
Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
NoteThe <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.
The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.
Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Appendix B.1.195 <surfaceGrp>

<surfaceGrp> defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
May contain
Declaration
element surfaceGrp
{
   att.global.attributes,
   att.typed.attributes,
   ( model.global | surface | surfaceGrp )+
}
Example
<sourceDoc>  <surfaceGrp>   <surface ulx="0uly="0lrx="200lry="300">    <graphic url="Bovelles-49r.png"/>   </surface>   <surface ulx="0uly="0lrx="200lry="300">    <graphic url="Bovelles-49v.png"/>   </surface>  </surfaceGrp> </sourceDoc>
NoteWhere it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Appendix B.1.196 <surname>

<surname> contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full) (att.naming (@role) (att.canonical (@ref)) ) att.typed (@type)
Member of
Contained by
May contain
Declaration
element surname
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<surname type="combine">St John Stevas</surname>

Appendix B.1.197 <surplus>

<surplus> marks text present in the source which the editor believes to be superfluous or redundant. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
reasonone or more words indicating why this text is believed to be superfluous, e.g. repeated, interpolated etc.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
Member of
Contained by
May contain
Declaration
element surplus
{
   att.global.attributes,
   att.editLike.attributes,
   attribute reason { list { data.word+ } }?,
   macro.paraContent
}
Example
I am dr Sr yrs <surplus reason="repeated">yrs</surplus> Sydney Smith

Appendix B.1.198 <surrogates>

<surrogates> contains information about any representations of the manuscript being described which may exist in the holding institution or elsewhere. [10.9. Additional Information]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: additional
May contain
Declaration
element surrogates { att.global.attributes, macro.specialPara }
Example
<surrogates>  <bibl>   <title type="gmd">diapositive</title>   <idno>AM 74 a, fol.</idno>   <date>May 1984</date>  </bibl>  <bibl>   <title type="gmd">b/w prints</title>   <idno>AM 75 a, fol.</idno>   <date>1972</date>  </bibl> </surrogates>

Appendix B.1.199 <table>

<table> contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
Modulefigures — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
rowsindicates the number of rows in the table.
StatusOptional
Datatype
data.count
NoteIf no number is supplied, an application must calculate the number of rows.Rows should be presented from top to bottom.
cols(columns) indicates the number of columns in each row of the table.
StatusOptional
Datatype
data.count
NoteIf no number is supplied, an application must calculate the number of columns.Within each row, columns should be presented left to right.
Member of
Contained by
May contain
Declaration
element table
{
   att.global.attributes,
   attribute rows { data.count }?,
   attribute cols { data.count }?,
   (
      ( model.headLike | model.global )*,
      ( ( row, model.global* )+ | ( ( model.graphicLike ), model.global* )+ ),
      ( ( model.divBottom ), model.global* )*
   )
}
Example
<table rows="4cols="4">  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>  <row role="label">   <cell role="data"/>   <cell role="data">Dossing Cribs or Lodging Houses</cell>   <cell role="data">Beds</cell>   <cell role="data">Needys or Nightly Lodgers</cell>  </row>  <row role="data">   <cell role="label">Bury St Edmund's</cell>   <cell role="data">5</cell>   <cell role="data">8</cell>   <cell role="data">128</cell>  </row>  <row role="data">   <cell role="label">Thetford</cell>   <cell role="data">3</cell>   <cell role="data">6</cell>   <cell role="data">36</cell>  </row>  <row role="data">   <cell role="label">Attleboro'</cell>   <cell role="data">3</cell>   <cell role="data">5</cell>   <cell role="data">20</cell>  </row>  <row role="data">   <cell role="label">Wymondham</cell>   <cell role="data">1</cell>   <cell role="data">11</cell>   <cell role="data">22</cell>  </row> </table>
NoteContains an optional heading and a series of rows.Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Appendix B.1.200 <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatype
data.truthValue
NoteTEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.
Member of
Contained by
header: encodingDesc
May contain
header: rendition
Declaration
element tagsDecl
{
   att.global.attributes,
   attribute partial { data.truthValue }?,
   ( rendition*, namespace* )
}
Example
<tagsDecl>  <rendition xml:id="rend-it">to be rendered in italic font</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467render="#rend-it"/>   <tagUsage gi="titleoccurs="45render="#rend-it"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>

Appendix B.1.201 <taxonomy>

<taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: classDecl
May contain
header: category
msdescription: msDesc
Declaration
element taxonomy
{
   att.global.attributes,
   (
      ( model.glossLike | model.descLike )*
    | category+
    | ( ( model.biblLike ), category* )
   )
}
Example
<taxonomy xml:id="tax.b">  <bibl>Brown Corpus</bibl>  <category xml:id="tax.b.a">   <catDesc>Press Reportage</catDesc>   <category xml:id="tax.b.a1">    <catDesc>Daily</catDesc>   </category>   <category xml:id="tax.b.a2">    <catDesc>Sunday</catDesc>   </category>   <category xml:id="tax.b.a3">    <catDesc>National</catDesc>   </category>   <category xml:id="tax.b.a4">    <catDesc>Provincial</catDesc>   </category>   <category xml:id="tax.b.a5">    <catDesc>Political</catDesc>   </category>   <category xml:id="tax.b.a6">    <catDesc>Sports</catDesc>   </category>  </category>  <category xml:id="tax.b.d">   <catDesc>Religion</catDesc>   <category xml:id="tax.b.d1">    <catDesc>Books</catDesc>   </category>   <category xml:id="tax.b.d2">    <catDesc>Periodicals and tracts</catDesc>   </category>  </category> </taxonomy>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>

Appendix B.1.202 <teiHeader>

<teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
typespecifies the kind of document to which the header is attached, for example whether it is a corpus or individual text.
Deprecatedwill be removed on 2016-11-18
StatusOptional
Datatype
data.enumerated
Sample values include:
text
the header is attached to a single text.[Default]
corpus
the header is attached to a corpus.
Contained by
textstructure: TEI
May contain
Declaration
element teiHeader
{
   att.global.attributes,
   attribute type { data.enumerated }?,
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}
Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
NoteOne of the few elements unconditionally required in any TEI document.

Appendix B.1.203 <term>

<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@target) att.typed (@type) att.canonical (@ref) att.sortable (@sortKey)
Member of
Contained by
May contain
Declaration
element term
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   att.canonical.attributes,
   att.sortable.attributes,
   macro.phraseSeq
}
Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term xml:id="TDPVrend="sc">discoursal point of view</term> as <gloss target="#TDPV">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
NoteThis element is used to supply the form under which an index entry is to be made for the location of a parent <index> element.In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.
As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Appendix B.1.204 <text>

<text> contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
textstructure: TEI
May contain
Declaration
element text
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}
Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>  <front> <!-- front matter for the whole group -->  </front>  <group>   <text> <!-- first text -->   </text>   <text> <!-- second text -->   </text>  </group> </text>
NoteThis element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Appendix B.1.205 <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
Member of
Contained by
header: profileDesc
May contain
header: keywords
Declaration
element textClass
{
   att.global.attributes,
   att.declarable.attributes,
   ( classCode | catRef | keywords )*
}
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>

Appendix B.1.206 <title>

<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@ref)
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatype
data.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
NoteThis attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatype
data.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
NoteThe level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.
Member of
Contained by
May contain
Declaration
element title
{
   att.global.attributes,
   att.canonical.attributes,
   attribute type { data.enumerated }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   macro.paraContent
}
Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
NoteThe attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Appendix B.1.207 <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: fileDesc
May contain
Declaration
element titleStmt { att.global.attributes, ( title+, model.respLike* ) }
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>

Appendix B.1.208 <trailer>

<trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]
Moduletextstructure — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
core: list
figures: figure table
textstructure: back body div front postscript
May contain
Declaration
element trailer
{
   att.global.attributes,
   att.typed.attributes,
   (
      text
    | lg
    | model.gLike
    | model.phrasemodel.inter
    | model.lLike
    | model.global
   )*
}
Example
<trailer>Explicit pars tertia</trailer>
Example
<trailer>  <l>In stead of FINIS this advice <hi>I</hi> send,</l>  <l>Let Rogues and Thieves beware of <lb/>   <hi>Hamans</hi> END.</l> </trailer>
From EEBO A87070

Appendix B.1.209 <trait>

<trait> contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.naming (@role) (att.canonical (@ref)) att.typed (@type)
Member of
Contained by
May contain
linking: ab
msdescription: msDesc
namesdates: trait
Declaration
element trait
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   att.typed.attributes,
   (
      precision*,
      (
         trait+
       | (
            model.headLike*,
            model.pLike+,
            ( model.noteLike | model.biblLike )*
         )
       | ( ( model.labelLike | model.noteLike | model.biblLike )* )
      )
   )
}
Example
<trait type="physical">  <label>Eye colour</label>  <desc>Blue</desc> </trait>
NoteWhere there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Appendix B.1.210 <transpose>

<transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [11.3.4.5. Transpositions]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
transcr: listTranspose
May containEmpty element
Declaration
element transpose { att.global.attributes, ( ptr, ptr+ ) }
Example
<transpose>  <ptr target="#ib02"/>  <ptr target="#ib01"/> </transpose>
The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01.
NoteTransposition is usually indicated in a document by a metamark such as a wavy line or numbering. The order in which <ptr> elements appear within a <transpose> element should correspond with the desired order, as indicated by the metamark.

Appendix B.1.211 <unclear>

<unclear> contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
reasonindicates why the material is hard to transcribe.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
<div>  <head>Rx</head>  <p>500 mg <unclear reason="illegible">placebo</unclear>  </p> </div>
NoteOne or more words may be used to describe the reason; usually each word will refer to a single cause. Typical examples might thus include faded, illegible, eccentric_ductus background_noise, passing_truck,etc.
handWhere the difficulty in transcription arises from action (partial deletion, etc.) assignable to an identifiable hand, signifies the hand responsible for the action.
StatusOptional
Datatype
data.pointer
agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatype
data.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Declaration
element unclear
{
   att.global.attributes,
   att.editLike.attributes,
   attribute reason { list { data.word+ } }?,
   attribute hand { data.pointer }?,
   attribute agent { data.enumerated }?,
   macro.paraContent
}
Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
NoteThe same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.
The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands.

Appendix B.1.212 <undo/>

<undo/> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
targetpoints to one or more elements representing the interventions which are to be reverted or undone.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
May containEmpty element
Declaration
element undo
{
   att.global.attributes,
   att.spanning.attributes,
   att.transcriptional.attributes,
   attribute target { list { data.pointer+ } }?,
   empty
}
Example
<line>This is <del change="#s2rend="overstrike">   <seg xml:id="undo-a">just some</seg>    sample <seg xml:id="undo-b">text</seg>,    we need</del>  <add change="#s2">not</add> a real example.</line> <undo target="#undo-a #undo-brend="dottedchange="#s3"/>
This encoding represents the following sequence of events:
  • "This is just some sample text, we need a real example" is written
  • At stage s2, "just some sample text, we need" is deleted by overstriking, and "not" is added
  • At stage s3, parts of the deletion are cancelled by underdotting, thus reinstating the words "just some" and "text".

Appendix B.1.213 <w>

<w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories]
Moduleanalysis — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
lemmaprovides a lemma for the word, such as an uninflected dictionary entry form.
StatusOptional
Datatype
data.text
lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
StatusOptional
Datatype
data.pointer
Member of
Contained by
May contain
Declaration
element w
{
   att.global.attributes,
   att.typed.attributes,
   attribute lemma { data.text }?,
   attribute lemmaRef { data.pointer }?,
   (
      text
    | model.gLike
    | segw
    | m
    | c
    | pc
    | model.global
    | model.lPart
    | model.hiLikemodel.pPart.edit
   )*
}
Example
<w type="verblemma="hit"  lemmaRef="http://www.example.com/lexicon/hitvb.xml">hitt<m type="suffix">ing</m> </w>

Appendix B.1.214 <width>

<width> contains a measurement measured along the axis parallel to the bottom of the written surface, i.e. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
Modulemsdescription — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element width { att.global.attributes, att.dimensions.attributes, macro.xtext }
Example
<width unit="in">4</width>
NoteIf used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

Appendix B.1.215 <zone>

<zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr — Formal declaration and Reference Pages
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type)
rotateindicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent <surface> element as implied by the dimensions given in the <msDesc> element or by the coordinates of the <surface> itself. The orientation is expressed in arc degrees.
StatusOptional
Datatype
data.count
Default0
Member of
Contained by
transcr: surface zone
May contain
Declaration
element zone
{
   att.global.attributes,
   att.coordinated.attributes,
   att.typed.attributes,
   attribute rotate { data.count }?,
   ( text | model.graphicLike | model.global | surface | model.linePart )*
}
Example
<surface ulx="14.54uly="16.14lrx="0lry="0">  <graphic url="stone.jpg"/>  <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/> </surface>
This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]].
Example
<facsimile>  <surface ulx="50uly="20lrx="400lry="280">   <zone ulx="0uly="0lrx="500lry="321">    <graphic url="graphic.png "/>   </zone>  </surface> </facsimile>
This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.
NoteThe position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface. A graphic element contained by a zone represents the whole of the zone.
A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

Appendix B.2 Model classes

Appendix B.2.2 model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Moduletei — Formal declaration and Reference Pages
Used by
Membersaddress affiliation

Appendix B.2.3 model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Formal declaration and Reference Pages
Used by
Memberslicence

Appendix B.2.4 model.biblLike

Appendix B.2.5 model.biblPart

Appendix B.2.6 model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. Simple Editorial Changes]
Moduletei — Formal declaration and Reference Pages
Used by
Membersabbr corr expan orig reg seg sic unclear

Appendix B.2.7 model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.divPart[model.lLike model.pLike[ab p]] model.inter[model.biblLike[bibl biblStruct msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace table] model.oddDecl model.qLike[model.quoteLike[quote] q] model.stageLike]
NoteThis class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

Appendix B.2.8 model.dateLike

model.dateLike groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Formal declaration and Reference Pages
Used by
Membersdate

Appendix B.2.9 model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei — Formal declaration and Reference Pages
Used by
Membersdesc

Appendix B.2.10 model.dimLike

model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
Moduletei — Formal declaration and Reference Pages
Used by
Membersdepth height width

Appendix B.2.11 model.divBottom

Appendix B.2.12 model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages]
Moduletei — Formal declaration and Reference Pages
Used by
Memberscloser postscript signed trailer

Appendix B.2.13 model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei — Formal declaration and Reference Pages
Used by
Membersdiv

Appendix B.2.14 model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.lLike model.pLike[ab p]
NoteNote that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

Appendix B.2.15 model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.divTopPart[model.headLike[head] opener signed] model.divWrapper[dateline salute]

Appendix B.2.16 model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.headLike[head] opener signed

Appendix B.2.17 model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
Moduletei — Formal declaration and Reference Pages
Used by
Membersdateline salute

Appendix B.2.18 model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei — Formal declaration and Reference Pages
Used by
Membersforeign gloss term title

Appendix B.2.19 model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei — Formal declaration and Reference Pages
Used by
MembersclassDecl listPrefixDef projectDesc styleDefDecl tagsDecl

Appendix B.2.20 model.eventLike

model.eventLike groups elements which describe events.
Moduletei — Formal declaration and Reference Pages
Used by
Membersevent listEvent

Appendix B.2.21 model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.frontPart.drama

Appendix B.2.23 model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
MembersaddSpan app damageSpan delSpan gap space

Appendix B.2.24 model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Memberslink linkGrp listTranspose
NoteElements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

Appendix B.2.25 model.glossLike

model.glossLike groups elements which provide an alternative name, explanation, or description for any markup construct.
Moduletei — Formal declaration and Reference Pages
Used by
Membersgloss

Appendix B.2.26 model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.9. Graphics and Other Non-textual Components]
Moduletei — Formal declaration and Reference Pages
Used by
Membersgraphic

Appendix B.2.27 model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei — Formal declaration and Reference Pages
Used by
Membershead

Appendix B.2.28 model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei — Formal declaration and Reference Pages
Used by
Membershi

Appendix B.2.29 model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.emphLike[foreign gloss term title] model.hiLike[hi]

Appendix B.2.30 model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References]
Moduletei — Formal declaration and Reference Pages
Used by
MembersbiblScope pubPlace publisher

Appendix B.2.31 model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.biblLike[bibl biblStruct msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace table] model.oddDecl model.qLike[model.quoteLike[quote] q] model.stageLike

Appendix B.2.32 model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei — Formal declaration and Reference Pages
Used by
Membersdesc label

Appendix B.2.34 model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.hiLike[hi] model.pPart.transcriptional[add corr damage del handShift mod orig redo reg restore retrace sic supplied surplus unclear undo] model.segLike[seg w] choice zone

Appendix B.2.35 model.listLike

model.listLike groups list-like elements. [3.7. Lists]
Moduletei — Formal declaration and Reference Pages
Used by
Memberslist listEvent listOrg listPerson listPlace table

Appendix B.2.36 model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. Numbers and Measures]
Moduletei — Formal declaration and Reference Pages
Used by
Membersdepth dim geo height measure measureGrp width

Appendix B.2.37 model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.10.3. Milestone Elements]
Moduletei — Formal declaration and Reference Pages
Used by
Membersanchor cb fw gb lb milestone pb

Appendix B.2.38 model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.biblLike[bibl biblStruct msDesc] model.msQuoteLike[title] model.quoteLike[quote] model.respLike[author editor funder principal respStmt] decoNote idno msItem

Appendix B.2.39 model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Moduletei — Formal declaration and Reference Pages
Used by
Memberstitle

Appendix B.2.40 model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike[geogFeat offset] model.persNamePart[addName forename roleName surname] model.placeStateLike[model.placeNamePart[bloc country geogName placeName region settlement] location state trait] idno
NoteA superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

Appendix B.2.41 model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei — Formal declaration and Reference Pages
Used by
Membersname orgName persName
NoteThis class is used in the content model of elements which reference names of people or organizations.

Appendix B.2.42 model.noteLike

Appendix B.2.43 model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. Place Names]
Moduletei — Formal declaration and Reference Pages
Used by
MembersgeogFeat offset

Appendix B.2.44 model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.eventLike[event listEvent] listOrg listPerson listPlace

Appendix B.2.46 model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
Moduletei — Formal declaration and Reference Pages
Used by
Membershead

Appendix B.2.48 model.pPart.edit

Appendix B.2.49 model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. Simple Editorial Changes]
Moduletei — Formal declaration and Reference Pages
Used by
Membersabbr choice expan subst

Appendix B.2.50 model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
Moduletei — Formal declaration and Reference Pages
Used by
Membersdimensions locus locusGrp material objectType origDate origPlace signatures stamp

Appendix B.2.51 model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. Simple Editorial Changes]
Moduletei — Formal declaration and Reference Pages
Used by
Membersadd corr damage del handShift mod orig redo reg restore retrace sic supplied surplus unclear undo

Appendix B.2.52 model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Modulenamesdates — Formal declaration and Reference Pages
Used by
MembersaddName forename roleName surname

Appendix B.2.53 model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei — Formal declaration and Reference Pages
Used by
Membersaffiliation age education faith nationality occupation persName state trait
NoteThese characteristics of an individual are typically a consequence of their own action or that of others.

Appendix B.2.54 model.personLike

model.personLike groups elements which provide information about people and their relationships.
Moduletei — Formal declaration and Reference Pages
Used by
Membersorg person

Appendix B.2.55 model.personPart

Appendix B.2.57 model.physDescPart

model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
Moduletei — Formal declaration and Reference Pages
Used by
MembersaccMat decoDesc handDesc objectDesc scriptDesc sealDesc

Appendix B.2.58 model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Moduletei — Formal declaration and Reference Pages
Used by
Membersplace

Appendix B.2.59 model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Moduletei — Formal declaration and Reference Pages
Used by
Membersbloc country geogName placeName region settlement

Appendix B.2.60 model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.placeNamePart[bloc country geogName placeName region settlement] location state trait

Appendix B.2.61 model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei — Formal declaration and Reference Pages
Used by
MembershandNotes langUsage listTranspose textClass

Appendix B.2.62 model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]
Moduletei — Formal declaration and Reference Pages
Used by
Membersref

Appendix B.2.63 model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Formal declaration and Reference Pages
Used by
Membersauthority publisher
NoteThe ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.See also model.publicationStmtPart.detail.

Appendix B.2.64 model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Formal declaration and Reference Pages
Used by
Membersaddress availability date idno pubPlace
NoteA ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.See also model.publicationStmtPart.agency.

Appendix B.2.65 model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]
Moduletei — Formal declaration and Reference Pages
Used by
Membersmodel.quoteLike[quote] q

Appendix B.2.66 model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei — Formal declaration and Reference Pages
Used by
Membersquote

Appendix B.2.67 model.rdgLike

model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit — Formal declaration and Reference Pages
Used by
Membersrdg
NoteThis class allows for variants of the <rdg> element to be easily created via TEI customizations.

Appendix B.2.68 model.resourceLike

model.resourceLike groups non-textual elements which may appear together with a header and a text to constitute a TEI document. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Membersfacsimile

Appendix B.2.69 model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei — Formal declaration and Reference Pages
Used by
Membersauthor editor funder principal respStmt

Appendix B.2.70 model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Moduletei — Formal declaration and Reference Pages
Used by
Membersseg w
NoteThe principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

Appendix B.2.71 model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Moduletei — Formal declaration and Reference Pages
Used by
MembersencodingDesc profileDesc

Appendix B.2.72 model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
Moduletei — Formal declaration and Reference Pages
Used by
Membersgraphic

Appendix B.3 Attribute classes

Appendix B.3.1 att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei — Formal declaration and Reference Pages
Memberschange q
AttributesAttributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.
<castItem type="role">  <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role">  <role xml:id="Francisco">Francisco</role>  <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo">  <speaker>Bernardo</speaker>  <l n="1">Who's there?</l> </sp> <sp who="#Francisco">  <speaker>Francisco</speaker>  <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
NoteFor transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

Appendix B.3.2 att.breaking

att.breaking provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. Milestone Elements]
Moduletei — Formal declaration and Reference Pages
Memberscb gb lb milestone pb
AttributesAttributes
breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
StatusRecommended
Datatype
data.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.
<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

Appendix B.3.3 att.canonical

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Moduletei — Formal declaration and Reference Pages
Membersatt.naming[att.personal[addName forename name orgName persName placeName roleName surname] affiliation author birth bloc collection country death editor education event geogFeat geogName institution nationality occupation offset origPlace pubPlace region repository settlement state trait] faith funder material objectType principal resp respStmt term title
AttributesAttributes
ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
NoteThe value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

Appendix B.3.4 att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei — Formal declaration and Reference Pages
MembersbiblScope
AttributesAttributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume.
StatusOptional
Datatype
data.enumerated
Suggested values include:
volume
the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
fromspecifies the starting point of the range of units indicated by the unit attribute.
StatusOptional
Datatype
data.word
tospecifies the end-point of the range of units indicated by the unit attribute.
StatusOptional
Datatype
data.word

Appendix B.3.5 att.coordinated

att.coordinated elements which can be positioned within a two dimensional coordinate system.
Moduletranscr — Formal declaration and Reference Pages
Memberssurface zone
AttributesAttributes
startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
StatusOptional
Datatype
data.pointer
ulxgives the x coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatype
data.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatype
data.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatype
data.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatype
data.numeric
pointsidentifies a two dimensional area within the bounding box specified by the other attributes by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
StatusOptional
Datatype3–∞ occurrences of 
data.point
separated by whitespace

Appendix B.3.6 att.damaged

att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes]
Moduletei — Formal declaration and Reference Pages
Membersdamage damageSpan
AttributesAttributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
handin the case of damage (deliberate defacement, inking out, etc.) assignable to a distinct hand, signifies the hand responsible for the damage by pointing to one of the hand identifiers declared in the document header (see section [[undefined PHDH]]).
StatusOptional
Datatype
data.pointer
agentcategorizes the cause of the damage, if it can be identified.
StatusOptional
Datatype
data.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The <damage> element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as <supplied>.
StatusOptional
Datatype
data.probability | data.certainty
NoteThe <damage> element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the <unclear> tag (for partial illegibility) or the <gap> tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.
groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
StatusOptional
Datatype
data.count

Appendix B.3.7 att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Formal declaration and Reference Pages
Membersacquisition affiliation age birth bloc change country custEvent date death education event faith geogFeat geogName licence location name nationality occupation offset orgName origDate origPlace origin persName placeName provenance region resp seal settlement stamp state trait
AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)
calendarindicates the system or calendar to which the date represented by the content of this element belongs.
StatusOptional
Datatype
data.pointer
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length(.) gt 0">@calendar indicates the system or calendar to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert></sch:rule>
He was born on <date calendar="#Gregorian">Feb. 22, 1732</date> (<date calendar="#Julian"  when="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).
NoteNote that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.
periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
StatusOptional
Datatype
data.pointer
NoteThis ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

Appendix B.3.8 att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Formal declaration and Reference Pages
Membersatt.datable[acquisition affiliation age birth bloc change country custEvent date death education event faith geogFeat geogName licence location name nationality occupation offset orgName origDate origPlace origin persName placeName provenance region resp seal settlement stamp state trait]
AttributesAttributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatype
data.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#Julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatype
data.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatype
data.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatype
data.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatype
data.temporal.w3c
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
NoteThe value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.
Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

Appendix B.3.9 att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
Moduletei — Formal declaration and Reference Pages
Membersavailability bibl biblStruct langUsage listEvent listOrg listPerson listPlace projectDesc sourceDesc styleDefDecl textClass
AttributesAttributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatype
data.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
NoteThe rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

Appendix B.3.10 att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei — Formal declaration and Reference Pages
Membersatt.damaged[damage damageSpan] att.editLike[att.transcriptional[add addSpan del delSpan mod redo restore retrace subst undo] affiliation age birth corr date death education event expan faith gap geogFeat geogName location name nationality occupation offset org orgName origDate origPlace origin persName person place placeName reg state supplied surplus trait unclear] depth dim dimensions height space width
AttributesAttributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
unitnames the unit used for the measurement
StatusOptional
Datatype
data.enumerated
Legal values are:
mm
Millimetres
chars
Characters in the text
words
Words in the text
lines
Lines in the text
pages
Pages in the text
section
Section in the text
quantityspecifies the length in the units specified
StatusOptional
Datatype
data.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatype
data.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatype
data.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatype
data.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

Appendix B.3.11 att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei — Formal declaration and Reference Pages
Membersbibl biblStruct change revisionDesc
AttributesAttributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatype
data.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02status="embargoed"/>  <change when="2010-05-01status="frozenwho="#MSM"/>  <change when="2010-03-01status="draftwho="#LB"/> </revisionDesc>

Appendix B.3.12 att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind.
Moduletei — Formal declaration and Reference Pages
Membersatt.transcriptional[add addSpan del delSpan mod redo restore retrace subst undo] affiliation age birth corr date death education event expan faith gap geogFeat geogName location name nationality occupation offset org orgName origDate origPlace origin persName person place placeName reg state supplied surplus trait unclear
AttributesAttributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.source (@source)

Appendix B.3.13 att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
Moduletei — Formal declaration and Reference Pages
MembersTEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone
AttributesAttributes att.global.rendition (@rend, @style) att.global.linking (@corresp) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
Datatype
xsd:ID
NoteThe xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. Reference Systems.
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatype
data.text
NoteThe value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
StatusOptional
Datatype
data.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
NoteThe xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see http://www.w3.org/International/questions/qa-choosing-language-tags.
The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

Appendix B.3.14 att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.3. Spans and Interpretations]
Moduleanalysis — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
NoteWhen multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

Appendix B.3.15 att.global.change

att.global.change supplies the change attribute, allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
changepoints to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace

Appendix B.3.16 att.global.facs

att.global.facs groups elements corresponding with all or part of an image, because they contain an alternative representation of it, typically but not necessarily a transcription of it. [11.1. Digital Facsimiles]
Moduletranscr — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
facs(facsimile) points to all or part of an image which corresponds with the content of the element.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace

Appendix B.3.17 att.global.linking

att.global.linking defines a set of attributes for hypertextual linking.
Modulelinking — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
<group>  <text xml:id="t1-g1-t1"   xml:lang="mi">   <body xml:id="t1-g1-t1-body1">    <div type="chapter">     <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>     <p></p>    </div>   </body>  </text>  <text xml:id="t1-g1-t2"   xml:lang="en">   <body xml:id="t1-g1-t2-body1"    corresp="#t1-g1-t1-body1">    <div type="chapter">     <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>     <p></p>    </div>   </body>  </text> </group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
<!-- In a placeography --><place xml:id="LOND1"  corresp="#LOND2 #GENI1">  <placeName>London</placeName>  <desc>The city of London...</desc> </place> <!-- In a literary personography --> <person xml:id="LOND2"  corresp="#LOND1 #GENI1">  <persName type="lit">London</persName>  <note>   <p>Allegorical character representing the city of <ref target="LOND1.xml">London</ref>.   </p>  </note> </person> <person xml:id="GENI1"  corresp="#LOND1 #LOND2">  <persName type="lit">London’s Genius</persName>  <note>   <p>Personification of London’s genius. Appears as an      allegorical character in mayoral shows.   </p>  </note> </person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

Appendix B.3.18 att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme.
Moduletei — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
Legal values are:
above
rendered above the line
below
rendered below the line
caps
rendered as capitals
center
aligned in the center
dotted-double-line
rendering is of a dotted double line
dotted-line
rendering is of a dotted line
double-line
rendering is of a double line
double-underline
double-underlined
half-line
rendering is of a half line
indent
rendered as indented (e.g. first line in a paragraph)
italic
rendered italic
large
rendering is of large size
left
aligned to the left (default)
line
rendering is of a line
no-indent
rendered as not indented
other
other rendering
quarter-line
rendering is of a quarter line
right
aligned to the right
sub
rendered in subscript
sup
rendered in superscript
small
rendered as smaller
smallcaps
rendered as smallcaps
three-quarter-line
rendering is of a three-quarter line
triple-line
rendering is of a triple line
triple-underline
triple-underlined
underline
underlined
diagonal
rendered diagonally
upside-down
rendered upside-down
vertical
rendered vertically
black
rendered in black
blue
rendered in blue
brown
rendered in brown
gray
rendered in gray
green
rendered in green
orange
rendered in orange
purple
rendered in purple
red
rendered in red
yellow
rendered in yellow
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
NoteThese Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.
stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
StatusOptional
Datatype
data.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
NoteUnlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

Appendix B.3.19 att.global.responsibility

att.global.responsibility provides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Moduletei — Formal declaration and Reference Pages
Membersatt.global[TEI ab abbr accMat acquisition add addName addSpan additional addrLine address adminInfo affiliation age altIdentifier anchor app author authority availability back bibl biblScope biblStruct birth bloc body catDesc category cb cell change choice classDecl closer collection condition corr country custEvent custodialHist damage damageSpan date dateline death decoDesc decoNote del delSpan depth desc dim dimensions div edition editionStmt editor education encodingDesc event expan facsimile faith figDesc figure fileDesc foliation foreign forename front funder fw gap gb geo geogFeat geogName gloss graphic handDesc handNote handNotes handShift head height hi history idno imprint institution item keywords label langUsage language layout layoutDesc lb licence link linkGrp list listChange listEvent listOrg listPerson listPlace listPrefixDef listTranspose location locus locusGrp material measure measureGrp metamark milestone mod monogr msContents msDesc msIdentifier msItem msName msPart name nationality note notesStmt objectDesc objectType occupation offset opener org orgName orig origDate origPlace origin p pb persName person physDesc place placeName postscript prefixDef principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote rdg recordHist redo ref reg region rendition repository resp respStmt restore retrace revisionDesc roleName row salute scriptDesc seal sealDesc seg settlement sic signatures signed sourceDesc stamp state styleDefDecl subst summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagsDecl taxonomy teiHeader term text textClass title titleStmt trailer trait transpose unclear undo w width zone]
AttributesAttributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatype
data.certainty
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
NoteNote that a simple resp pointing to a person or organization is likely to be somewhat ambiguous with regard to the nature of the responsibility. For this reason, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).
Example
Blessed are the <choice>  <sic>placemakers</sic>  <corr resp="#editorcert="high">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<!-- in the <text> ... --><lg> <!-- ... -->  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

Appendix B.3.20 att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands]
Moduletei — Formal declaration and Reference Pages
MembershandNote handShift
AttributesAttributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatype
data.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of 
data.name
separated by whitespace
scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
StatusOptional
Datatype1–∞ occurrences of 
data.enumerated
separated by whitespace
scopespecifies how widely this hand is used in the manuscript.
StatusOptional
Datatype
data.enumerated
Legal values are:
sole
only this hand is used throughout the manuscript
major
this hand is used through most of the manuscript
minor
this hand is used occasionally in the manuscript
NoteUsually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

Appendix B.3.21 att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei — Formal declaration and Reference Pages
Membersmeasure measureGrp
AttributesAttributes
unitindicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatype
data.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
NoteIf the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.
quantityspecifies the number of the specified units that comprise the measurement
StatusOptional
Datatype
data.numeric
commodityindicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
NoteIn general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.
NoteThis attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure quantity="0.5unit="galcommodity="ice cream">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure quantity="1.893unit="Lcommodity="ice cream">half    a gallon</measure>, baby?</l>
NoteThe unit should normally be named using the standard abbreviation for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

Appendix B.3.22 att.media

att.media provides attributes for specifying display and related properties of external media.
Moduletei — Formal declaration and Reference Pages
Membersgraphic
AttributesAttributes
widthWhere the media are displayed, indicates the display width
StatusOptional
Datatype
data.outputMeasurement
heightWhere the media are displayed, indicates the display height
StatusOptional
Datatype
data.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
StatusOptional
Datatype
data.numeric

Appendix B.3.23 att.milestoneUnit

att.milestoneUnit provides an attribute to indicate the type of section which is changing at a specific milestone. [3.10.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Modulecore — Formal declaration and Reference Pages
Membersmilestone
AttributesAttributes
unitprovides a conventional name for the kind of section changing at this milestone.
StatusRequired
Datatype
data.enumerated
Suggested values include:
page
physical page breaks (synonymous with the <pb/> element).
column
column breaks.
line
line breaks (synonymous with the <lb/> element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
<milestone n="23"  ed="La"  unit="Dreissiger"/> ... <milestone n="24"  ed="AV"  unit="verse"/> ...
NoteIf the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next <milestone/> tag for the edition in question is encountered.In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

Appendix B.3.24 att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
Modulemsdescription — Formal declaration and Reference Pages
MembersmsContents msItem quote
AttributesAttributes
defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
StatusOptional
Datatype
data.xTruthValue
Defaultfalse
NoteIn the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

Appendix B.3.25 att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.
Moduletei — Formal declaration and Reference Pages
Membersatt.personal[addName forename name orgName persName placeName roleName surname] affiliation author birth bloc collection country death editor education event geogFeat geogName institution nationality occupation offset origPlace pubPlace region repository settlement state trait
AttributesAttributes att.canonical (@ref)
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of 
data.enumerated
separated by whitespace

Appendix B.3.26 att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader — Formal declaration and Reference Pages
MembersprefixDef
AttributesAttributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatype
data.pattern
NoteThe syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.
replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
StatusRequired
Datatype
data.replacement
NoteThe strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

Appendix B.3.27 att.personal

att.personal common attributes for those elements which form part of a name usually, but not necessarily, a personal name.
Moduletei — Formal declaration and Reference Pages
MembersaddName forename name orgName persName placeName roleName surname
AttributesAttributes att.naming (@role) (att.canonical (@ref))
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatype
data.enumerated
Legal values are:
yes
the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.

Appendix B.3.28 att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears.
Moduletei — Formal declaration and Reference Pages
Membersadd addSpan figure fw label metamark note
AttributesAttributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of 
data.enumerated
separated by whitespace
Legal values are:
above
above the line
below
below the line
bottom
at the foot of the page
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
marginleft
in the left margin
marginright
in right margin
margintop
in the top margin
marginbottom
in the bottom margin
over-text
over pre-existing text
top
at the top of the page
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

Appendix B.3.29 att.pointing

att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references.
Moduletei — Formal declaration and Reference Pages
Membersgloss licence link locus note ref term
AttributesAttributes
targetspecifies the destination of the reference by supplying one or more URI References
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
NoteOne or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

Appendix B.3.30 att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei — Formal declaration and Reference Pages
Membersatt.dimensions[att.damaged[damage damageSpan] att.editLike[att.transcriptional[add addSpan del delSpan mod redo restore retrace subst undo] affiliation age birth corr date death education event expan faith gap geogFeat geogName location name nationality occupation offset org orgName origDate origPlace origin persName person place placeName reg state supplied surplus trait unclear] depth dim dimensions height space width]
AttributesAttributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatype
data.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatype
data.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatype
data.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatype
data.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatype
data.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegibleextent="one or two lettersatLeast="1"   atMost="2unit="chars"/> </del> Philadelphia to the Graphic office, New York.

Appendix B.3.31 att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Moduletei — Formal declaration and Reference Pages
Membersgraphic
AttributesAttributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
StatusRequired
Datatype
data.pointer

Appendix B.3.32 att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
Moduletei — Formal declaration and Reference Pages
Membersbibl biblStruct event idno item list listChange listEvent listOrg listPerson listPlace msDesc org person place term
AttributesAttributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatype
data.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
NoteThe sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependentDictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

Appendix B.3.33 att.source

att.source provides attributes for pointing to the source of a bibliographic reference. [3.3.3. Quotation 8.3.4. Writing]
Moduletei — Formal declaration and Reference Pages
Membersatt.editLike[att.transcriptional[add addSpan del delSpan mod redo restore retrace subst undo] affiliation age birth corr date death education event expan faith gap geogFeat geogName location name nationality occupation offset org orgName origDate origPlace origin persName person place placeName reg state supplied surplus trait unclear] att.textCritical[rdg] abbr handShift note orig provenance q quote seg sic space
AttributesAttributes
sourceprovides a pointer to the bibliographical source from which a quotation or citation is drawn.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a    problematic and should be a contested term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories    are in flux, and the more we learn, the less we    seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>

Appendix B.3.34 att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [1.3.1. Attribute Classes]
Moduletei — Formal declaration and Reference Pages
MembersaddSpan cb damageSpan delSpan gb lb metamark milestone mod pb redo retrace undo
AttributesAttributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatype
data.pointer
SchematronThe @spanTo attribute must point to an element following the current element
<sch:rule context="tei:*[@spanTo]"> <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/></sch:assert></sch:rule>
NoteThe span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

Appendix B.3.35 att.styleDef

att.styleDef groups elements which specify the name of a formal definition language used to provide formatting or rendition information.
Moduletei — Formal declaration and Reference Pages
Membersrendition styleDefDecl
AttributesAttributes
schemeidentifies the language used to describe the rendition.
StatusOptional
Datatype
data.enumerated
Legal values are:
css
Cascading Stylesheet Language
xslfo
Extensible Stylesheet Language Formatting Objects
free
Informal free text description
other
A user-defined rendition description language
NoteIf no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.
schemeVersionsupplies a version number for the style language provided in scheme.
StatusOptional
Datatype
data.versionNumber
Schematron
<sch:rule context="tei:*[@schemeVersion]"> <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified. </sch:assert></sch:rule>
NoteIf schemeVersion is used, then scheme should also appear, with a value other than free.

Appendix B.3.36 att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics and Notated Music]
Moduletei — Formal declaration and Reference Pages
Memberscell row
AttributesAttributes
roleindicates the kind of information held in this cell or in each cell of this row.
StatusOptional
Datatype
data.enumerated
Suggested values include:
label
labelling or descriptive information only.
data
data values.[Default]
NoteWhen this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent <row> element.
rowsindicates the number of rows occupied by this cell or row.
StatusOptional
Datatype
data.count
Default1
NoteA value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.
cols(columns) indicates the number of columns occupied by this cell or row.
StatusOptional
Datatype
data.count
Default1
NoteA value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

Appendix B.3.37 att.textCritical

att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work. [12.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit — Formal declaration and Reference Pages
Membersrdg
AttributesAttributes att.source (@source)
typeclassifies the reading according to some useful typology.
StatusOptional
Datatype
data.enumerated
Sample values include:
substantive
the reading offers a substantive variant.
orthographic
the reading differs only orthographically, not in substance, from other readings.
causeclassifies the cause for the variant reading, according to any appropriate typology of possible origins.
StatusOptional
Datatype
data.enumerated
Sample values include:
homeoteleuton
homeoarchy
paleographicConfusion
haplography
dittography
falseEmendation
varSeq(variant sequence) provides a number indicating the position of this reading in a sequence, when there is reason to presume a sequence to the variants.
StatusOptional
Datatype
data.count
NoteDifferent variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More complex variant sequences, with (for example) multiple branchings from single readings, may be expressed through the <join> element.
handindicates the hand responsible for a particular reading in the witness.
StatusOptional
Datatype
data.pointer
NoteThis attribute is only available within an apparatus gathering variant readings in the transcription of an individual witness. It may not occur in an apparatus gathering readings from different witnesses.
NoteThis element class defines attributes inherited by <rdg>, <lem>, and <rdgGrp>.

Appendix B.3.38 att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]
Moduletei — Formal declaration and Reference Pages
Membersadd addSpan del delSpan mod redo restore retrace subst undo
AttributesAttributes att.editLike (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
handindicates the hand of the agent which made the intervention.
StatusOptional
Datatype
data.pointer
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
StatusOptional
Datatype
data.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty.[Default]
NoteStatus information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.
causedocuments the presumed cause for the intervention.
StatusOptional
Datatype
data.enumerated
Legal values are:
fix
repeated for the purpose of fixation
unclear
repeated to clarify a previously illegible or badly written text or mark
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
StatusOptional
Datatype
data.count

Appendix B.3.39 att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way.
Moduletei — Formal declaration and Reference Pages
Membersab accMat add addName addSpan altIdentifier anchor bibl biblStruct bloc cb change collection corr country custEvent damage damageSpan date decoNote del delSpan desc dim div event figure forename gb geogFeat geogName gloss head label lb link listEvent listOrg listPerson listPlace location measureGrp milestone mod msDesc msName name note offset org orgName origDate origPlace pb persName place placeName provenance quote ref reg region restore roleName seal seg settlement space stamp state surface surfaceGrp surname term text trailer trait w zone
AttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatype
data.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
NoteThe type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.
Schematron
<sch:rule context="*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert></sch:rule>

Appendix B.3.40 att.witnessed

att.witnessed supplies the attribute used to identify the witnesses supporting a particular reading in a critical apparatus. [12.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit — Formal declaration and Reference Pages
Membersrdg
AttributesAttributes
wit(witness or witnesses) contains a space-delimited list of one or more pointers indicating the witnesses which attest to a given reading.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
NoteIf the apparatus contains readings only for a single witness, this attribute may be consistently omitted.This attribute may occur both within an apparatus gathering variant readings in the transcription of an individual witness and within an apparatus gathering readings from different witnesses.
Additional descriptions or alternative versions of the sigla referenced may be supplied as the content of a child <wit> element.

Appendix B.4 Macros

Appendix B.4.1 data.certainty

data.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.certainty = "high" | "medium" | "low" | "unknown"
NoteCertainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. For more precise indication, data.probability may be used instead or in addition.

Appendix B.4.2 data.count

data.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.count = xsd:nonNegativeInteger
NoteOnly positive integer values (including zero) are permitted

Appendix B.4.3 data.duration.iso

data.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
NoteA duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

Appendix B.4.4 data.duration.w3c

data.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
NoteA duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.For complete details, see the W3C specification.

Appendix B.4.5 data.enumerated

data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.enumerated = data.word
NoteAttributes using this datatype must contain a single word matching the pattern defined for this datatype: for example it cannot include whitespace but may begin with digits. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

Appendix B.4.6 data.language

data.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.language = xsd:language | ""
NoteThe values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.
Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.
Examples include
sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

Appendix B.4.7 data.name

data.name defines the range of attribute values expressed as an XML Name.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.name = xsd:Name
NoteAttributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

Appendix B.4.8 data.numeric

data.numeric defines the range of attribute values used for numeric values.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
NoteAny numeric value, represented as a decimal number, in floating point format, or as a ratio.To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.
A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

Appendix B.4.9 data.outputMeasurement

data.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
   }
Example
<figure>  <head>The TEI Logo</head>  <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in    between and <mentioned>text encoding initiative</mentioned> underneath, all on a white    background.</figDesc>  <graphic height="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
NoteThese values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

Appendix B.4.10 data.pattern

data.pattern (regular expression pattern) defines attribute values which are expressed as a regular expression.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

Appendix B.4.11 data.point

data.point defines the data type used to express a point in cartesian space.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.point = token { pattern = "(\-?[0-9]+\.?[0-9]*,\-?[0-9]+\.?[0-9]*)" }
Example
<facsimile>  <surface ulx="0uly="0lrx="400lry="280">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png "/>   </zone>  </surface> </facsimile>
NoteA point is defined by two numeric values, which may be expressed in any notation permitted.

Appendix B.4.12 data.pointer

data.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.pointer = xsd:anyURI
NoteThe range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

Appendix B.4.13 data.probability

data.probability defines the range of attribute values expressing a probability.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.probability = xsd:double { minInclusive = "0" maxInclusive = "1" }
NoteProbability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

Appendix B.4.14 data.replacement

data.replacement defines attribute values which contain a replacement template.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.replacement = text

Appendix B.4.15 data.sex

data.sex defines the range of attribute values used to identify human or animal sex.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.sex = data.word
NoteValues for attributes using this datatype may be locally defined by a project, or may refer to an external standard, such as vCard's sex property http://microformats.org/wiki/gender-formats (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes http://standards.iso.org/ittf/PubliclyAvailableStandards/c036266_ISO_IEC_5218_2004(E_F).zip (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People http://transhealth.ucsf.edu/trans?page=lib-data-collection.

Appendix B.4.16 data.temporal.w3c

data.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
NoteIf it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

Appendix B.4.17 data.text

data.text defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.text = string
NoteAttributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

Appendix B.4.18 data.truthValue

data.truthValue defines the range of attribute values used to express a truth value.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.truthValue = xsd:boolean
NoteThe possible values of this datatype are 1 or true, or 0 or false.This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: data.xTruthValue.

Appendix B.4.19 data.version

data.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
NoteThe value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

Appendix B.4.20 data.versionNumber

data.versionNumber defines the range of attribute values used for version numbers.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
data.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

Appendix B.4.21 data.word

data.word defines the range of attribute values expressed as a single word or token.
Moduletei — Formal declaration and Reference Pages
Used by
data.enumerated data.sexElement:
Declaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
NoteAttributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Appendix B.4.22 data.xTruthValue

data.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei — Formal declaration and Reference Pages
Used by
Element:
Declaration
data.xTruthValue = xsd:boolean | "unknown" | "inapplicable"
NoteIn cases where where uncertainty is inappropriate, use the datatype data.TruthValue.

Appendix B.4.23 macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

Appendix B.4.24 macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
macro.paraContent =
   (
      text
    | model.gLike
    | model.phrasemodel.intermodel.global
    | lg
    | model.lLike
   )*

Appendix B.4.26 macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

Appendix B.4.27 macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
macro.specialPara =
   (
      text
    | model.gLike
    | model.phrasemodel.intermodel.divPartmodel.global
   )*

Appendix B.4.28 macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei — Formal declaration and Reference Pages
Used by
Declaration
macro.xtext = ( text | model.gLike )*
Date: 2016-03-11 -- Version: 2.0.1