(unknown project)

TEI with OUCS setup

Table of contents

1. Introduction

Today documents are usually prepared electronically using a word processor such as Word or OpenOffice. Such programs allow their users to make good-looking documents easily and quickly. However, there are problems associated with the multitude of different formats and programs used to produce documents. For instance:

OUCS has adopted an open, vendor independent format approach to maintain our documentation in an accessible and interchangeable format. Our system uses XML or eXtensible Markup Language to store documents. XML allows the user to develop their own rules to code up their documents. However, there are already many different versions of XML rules available so we do not need to develop anything new for OUCS. Our system uses a modified version of the Text Encoding Initiative (TEI) XML for writing documentation.

1.1. TEI and OUCS

The Text Encoding Initiative (TEI) Guidelines are an international and interdisciplinary standard that enables libraries, museums, publishers, and individual scholars to represent a variety of literary and linguistic texts for online research, teaching, and preservation.

The TEI standard is maintained by a consortium of leading institutions and projects worldwide; Oxford is one of these institutions. Two of the major players in the TEI are members of OUCS: Lou Burnard and Sebastian Rahtz. Lou joined the Text Encoding Initiative project as its European Editor back in 1989 (a post he still holds), while Sebastian is one of the consortium's directors and actively develops the TEI itself.

1.2. OUCS Web Site Accessibility

Since 2002 it has been law to provide documents (including web pages) in accessible formats to users of alternative technologies such as screen readers. The relevant legislation is the Special Educational Needs and Disability Act (SENDA) 2001 which is part 4 of the Disability Discrimination Act (DDA). This act brought Education establishments into line with commercial providers in the way that they provide information and services to the disabled community.

The W3C organisation have created various standards for web accessibility. These are:

Priority level details

All OUCS pages should reach level 1 standard. The University has decided that its web sites should ideally conform to the level 2 standard and meet as many level 3 points as possible.

The following document includes details on how to make your XML documents accessible to as wide an audience as possible. Please make sure that you follow these accessibility guidelines - it's the LAW!

2. How does the OUCS system work?

The OUCS XML documentation system has six components:

  1. An XML schema, derived from the Text Encoding Initiative, located at http://www.oucs.ox.ac.uk/schemas/tei-oucs.rng
  2. A set of XSLT stylesheets, which can transform document instances to HTML pages; see http://www.tei-c.org.uk/Stylesheets/
  3. A set of XSLT stylesheets, which can transform document instances into PDF for printing; see http://www.tei-c.org.uk/Stylesheets/
  4. CSS stylesheets for displaying the XML files directly (http://www.oucs.ox.ac.uk/schemas/tei-oucs.css, which can also be used with some editors), and for enhancing the HTML versions (http://www.oucs.ox.ac.uk/stylesheet/oucs/tei-oucs.css)
  5. The XML text document
  6. The change management system where all the material is stored

Taking each of these parts in turn:

2.1. XML Schema

The rules of the TEI XML format are stored in a schema (we use the RELAXNG schema language) file. This file defines the structure of how XML is to be written and is the key to transforming the text from one format to another. In order to write a valid TEI XML document the schema has to be followed. Luckily there are many XML editors that look after the schema for you and show any errors when the document is tested against the schema.

2.2. XSLT Stylesheets

An XSLT Stylesheet or Extensible Stylesheet Language Transformation Stylesheet is basically a set of rules to process a XML document. It turns an XML rendition of a file into the final version of a file. OUCS uses two versions of XSLT files, one turns an XML file into a web page (HTML format), the other turns XML into PDF format for printing.

2.3. CSS Stylesheets

CSS or Cascading Style Sheets are files containing information on how a document is to be presented e.g. bold, red headings or grey backgrounds. There are two versions used by OUCS: one displays the XML file directly and is fairly simple; the other displays the final web page and is fairly complex.

2.4. Change Management System

This is the method by which documents are stored. OUCS uses an open source system called Subversion to store XML documents. It is not restricted in the type of documents it can accept, allowing us to store just about anything we might need.

3. OUCS documents - The Basics

3.1. A Few Definitions

Elements and Tags
XML documents have lots of elements, one example is the title element. This begins with a start-tag <title> and is closed by the end-tag </title>. Any text between the start and end tags is therefore defined as the title of the document. Most XML tags work in this way: a start tag, some text, followed by an end tag. There are some elements that are self closing (i.e. they have no end tag); where appropriate these will be highlighted later in this document.
Content and Data
Any text between tags is the content of the element. This can be of two forms: the actual information or data; and other elements. Where the two occur together this is termed mixed content.
Attributes

All elements can have additional properties beside the element name and content. These properties are the attributes of an element and they consist of name-value pairs. For example a <div> element can have the attribute id="xxx", where xxx represents a name or number. In the example below, the id is 'email':

<div id="email">  <head>Configuring your email client</head>  <p> text....</p> </div>
XML structure and nesting tags

XML is very strict on its element structure, especially compared to HTML. In XML, tags usually have to be started and ended. They must be nested properly and used in the correct place within the document hierarchy. This generally means that you cannot open a new tag e.g. <p> without closing the previous <p> tag. (N.B. there are exceptions to this rule e.g. self-closing tags).

3.2. Dissecting the OUCS XML Template

Viewing the OUCS template code in an editor shows the document structure. The complete page structure is shown below:

<TEI.2>  <teiHeader>   <fileDesc>    <titleStmt>     <title>Markup for OUCS documents</title>     <author>Sebastian Rahtz</author>    </titleStmt>    <editionStmt>     <edition>      <date>May 2009</date>     </edition>    </editionStmt>    <publicationStmt>     <authority>webmaster@it.ox.ac.uk</authority>    </publicationStmt>    <sourceDesc>     <p>This is the master version of an original document.</p>    </sourceDesc>   </fileDesc>   <revisionDesc>    <change>     <date>$LastChangedDate: 2009-09-10 14:39:46 +0100 (Thu, 10 Sep 2009) $</date>     <respStmt>      <name>$LastChangedBy: barry $</name>     </respStmt>     <item>$LastChangedRevision: 98035 $</item>    </change>   </revisionDesc>  </teiHeader>  <text>   <body> <!-- Your text goes in here.... -->   </body>  </text> </TEI.2>

First comes the declaration that the file is a TEI document <TEI.2>. This is effectively the start tag for the document, all other elements must be correctly arranged or nested inside the <TEI.2> tags for the document to be valid TEI XML.

The first element inside <TEI.2> is the <teiHeader> element. Everything within this element is part of the document's Metadata (Metadata is data about the document, e.g. its title, author, creation date etc.). OUCS documents have a number of fields in the <teiHeader>; some have to be manually completed, such as the title of the document, while others are automatically added on document submission e.g. Last changed by information. Usually, when writing your own documents, you should complete the following metadata elements:

It will also be necessary to complete an extra sections in the header recording who is responsible

The end of the metadata is marked by the closing </teiHeader> tag.

After the metadata comes the body of the document. This can be split into three sections:

<front>
contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found before the start of a text proper.
<body>
contains the whole body of a single unitary text, excluding any front or back matter.
<back>
contains any appendices, etc., following the main part of a text.

The majority of OUCS documents only use the body section for the text. This is shown in the next example:

<teiHeader>... </teiHeader> <text>  <body>   <p>Your text goes in here....</p>  </body> </text>

When there are front and/or back additions to a document, the sections are coded in the following manner:

<text>  <front>   <titlePage>    <docTitle>     <titlePart type="main">Markup for OUCS documents</titlePart>    </docTitle>    <docAuthor>Ian Senior</docAuthor>    <docDate>May 2005</docDate>   </titlePage>  </front>  <body>   <p>Your text goes in here....</p>  </body>  <back>   <div id="appendix">    <head>Appendix</head>    <p>More text in here...</p>   </div>  </back> </text>

4. Coding your document

OUCS XML has many elements available for use, although in any one document only a subset of these will ever be applied. In this section we discuss the elements making up the body of a text.

4.1. Sections

A text may be just a series of paragraphs, or these paragraphs may be grouped together into chapters, sections, subsections, etc. In the former case, each paragraph is embedded inside a the <p> element. In the latter case, the <body> may be divided into a series of <div> elements, which may be further subdivided. An example of div structure is shown below:

<div>  <head>This is my heading</head>  <p> This is a paragraph</p>  <div>   <head>This is my inner section heading</head>   <p> This is a paragraph in the inner section</p>  </div> <!--This div closes the inner section--> </div> <!--This div formally closes entire section-->

Sectioning a document has important effects on the OUCS web site. Each div used is processed when the document is converted into html. Major divisions are treated as separate web pages and help to form the basis of the internal page navigation system. Each division is also sequentially numbered: 1, 2, 3 ... Where a div section is within another div, it is treated as a subsection and numbered accordingly e.g. 2.1, 2.2, 2.3....

Sectioning documents also influences the HTML output to browsers. The title of a document is always given the <h1> tag, major divisions are thus given the <h2> tag and minor section divisions are given <h3>, <h4>, <h5> etc. depending on how deep they are nested within the document.

The following elements can be used to divide up a text:

<p>
marks paragraphs in prose.
<div>
contains a subdivision of the front, body, or back of a text.

When structural divisions smaller than a <div> are necessary, inner <div> elements may be used, without limit to the depth of nesting (see example above).

A div element can have the following three attributes:

type
This indicates the conventional name for this category of text division. Its value might be something like ‘Preface’.
id
This specifies a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary.
n
The n attribute specifies a mnemonic short name or number for the division, which can be used to identify it in preference to the id. If a conventional form of reference or abbreviation for the parts of a work already exists (such as the book/chapter/verse pattern of Biblical citations), the n attribute is the place to record it.

The attributes id and n, indeed, are so widely useful that they are allowed on any element in any TEI schema: they are global attributes.

The value of every id attribute must be unique within a document. They may be used to derive the names of HTML pages, so giving sensible mnemonic names is a good idea.

4.2. Headings and Closings

Every <div> may have a title or heading, and (less commonly) a closing such as ‘End of Chapter 1’. The following elements may be used to mark them up:

<head>
contains any heading, for example, the title of a section, or the heading of a list or glossary.
<trailer>
contains a closing title or footer appearing at the end of a division of a text.

Here is an example of their use:

<div>  <head>This is my heading</head>  <p>This is the body of the text</p>  <trailer>   <p>This is the trailer to my text</p>  </trailer> </div>

N.B. At present it is not possible to use the <head> tag without using the <div> tag first.

4.3. Marking Highlighted Phrases

4.3.1. Changes of Typeface, etc.

Highlighted words or phrases are those made visibly different from the rest of the text, typically by a change of type font, handwriting style, or ink colour, intended to draw the reader's attention to them.

<hi>
marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.
Code view:
<hi>example</hi>
Rendered view:
example

Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available. All but the first two are OUCS extensions to the standard TEI markup.

<emph>
marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect
Code view:
<emph>example</emph>
Rendered view:
example
<term>
contains a single-word, multi-word or symbolic designation which is regarded as a technical term
Code view:
<term>example</term>
Rendered view:
example
<gi>
An SGML, XML or HTML element name
Code view:
<gi>h1</gi>
Rendered view:
<h1>
<Button>
A button which a user can see
Code view:
<Button>Logout</Button>
Rendered view:
Logout
<Code>
Some sort of computer language code
Code view:
<Code>\textbf{a}$^34$</Code>
Rendered view:
\textbf{a}$^34$
<Command>
The name of a command
Code view:
<Command>tcsh</Command>
Rendered view:
tcsh
<Field>
A labelled input field
Code view:
<Field>Subject</Field>
Rendered view:
Subject
<Filespec>
A file or directory specification of any kind
Code view:
<Filespec>C:\Windows\My Documents</Filespec>
Rendered view:
C:\Windows\My Documents
<Icon>
an icon in a GUI
Code view:
<Icon>Notepad</Icon>
Rendered view:
Notepad
<Input>
Text for a user to type
Code view:
<Input>quota</Input>
Rendered view:
quota
<Key>
A key to press
Code view:
<Key>R</Key>
Rendered view:
R
<Keyword>
A keyword in some technical code the user is being asked to write
Code view:
<Keyword>font-family</Keyword>
Rendered view:
font-family
<Label>
The label for a button, radio box, etc.
Code view:
<Label>select to activate account</Label>
Rendered view:
select to activate account
<Link>
The text of a link which is being described
Code view:
<Link>IT Information</Link>
Rendered view:
IT Information
<Menu>
A menu item
Code view:
<Menu>Save as</Menu>
Rendered view:
Save as
<Output>
What comes back when you give a command
Code view:
<Output>job completed</Output>
Rendered view:
job completed
<Program>
A simple program listing
Code view:
<Program>i:=0;
j:=-1;</Program>
Rendered view:
i:=0; j:=-1;
<Prompt>
A prompt from the computer
Code view:
<Prompt>password:</Prompt>
Rendered view:
password:
<Screen>
A prettified display of text screenshot
Code view:
<Screen>Thanks!
Your work is complete.</Screen>
Rendered view:
Thanks!<lb/> Your work is complete.
<Software>
The name of a program
Code view:
<Software>Microsoft Word</Software>
Rendered view:
Microsoft Word
<Value>
A possible value for some option
Code view:
<Value>Times-Roman 10pt</Value>
Rendered view:
Times-Roman 10pt

The <lb/> element marks the start of a new (typographic) line.

4.4. Cross References and Links

Explicit cross references or links from one point to another in a text in the same XML document may be encoded using the elements described in section 4.4.1. Simple Cross References. References or links to elements of some other XML document, or to parts of non-XML documents, may be encoded using the TEI extended pointers described in section 4.4.2. Extended Pointers.

By default our system will add a title attribute to any link on a page when it is transformed into HTML. Additional text can be included using the n attribute

4.4.1. Simple Cross References

A cross reference from one point to another within a single document can be encoded using either of the following elements:

<ref>
a reference to another location in the current document usually modified by additional text.
<ptr/>
a pointer to another location in the current document.

These elements share the following attribute:

target
specifies the destination of the pointer.

The difference between these two elements is that <ptr/> is an empty element, simply marking a point from which a link is to be made, whereas <ref> may contain some text as well --- typically the text of the cross-reference itself. The <ptr/> element would be used for a cross reference which is indicated by a symbol or icon, or in an electronic text by a button.

The following two forms, for example, are equivalent:

See especially <ref target="SEC12">section 12 on page 34</ref>.
See especially <ptr target="SEC12"/>.
The value of the target attribute must be present in the current XML document. This implies that the passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a <div> element:
...see especially <ptr target="SEC12"/>.... ... <div id="SEC12">  <head>Concerning Identifiers... </head> </div>
The id attribute is global (i.e. can be used on any element), which means all elements in a document can be pointed to in this way. In the following example, a paragraph has been given an identifier so that it may be pointed at:
...this is discussed in <ref target="pspec">the paragraph on links</ref> ... <p id="pspec">Links may be made to any kind of element ...</p>

Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an <anchor/> element at the appropriate spot.

<ptr target="1234"/>.... .... <anchor id="1234"/>

4.4.2. Extended Pointers

The elements <ptr/> and <ref> can only be used for cross-references whose targets occur within the same XML document as their source. They can also refer only to XML elements. The elements discussed in this section are not restricted in these ways.

<xptr/>
defines a pointer to another location in the current document or an external document.
<xref>
defines a pointer to another location in the current document or an external document, usually modified by additional text or comment.

In addition to the attributes already discussed in section 4.4.1. Simple Cross References above, these elements share the following additional attribute, which is used to specify the target of the cross reference or link:

url
A Web URL specifying the destination

The following example shows how to link to another page and web site

See local information about <ref target="/email/clients/">email clients</ref> or go to <xptr   url="http://www.google.co.uk"   n="go to Google's web site"/>

The above example renders as follows:

See local information about email clients or go to http://www.google.co.uk

The following syntax is used to link to a specific section on another page:

<ref target="/matlab/#fault_special">faults, problems, or special requests</ref>

4.5. Addresses

The <address> element is used to mark a postal address of any kind. It contains one or more <addrLine> elements, one for each line of the address.

address
contains a postal or other address, for example of a publisher, an organization, or an individual.
addrLine
contains one line of a postal or other address.
Here is a simple example:
<address>  <addrLine>Oxford University Computing Services</addrLine>  <addrLine>13 Banbury Rd</addrLine>  <addrLine>Oxford</addrLine>  <addrLine>OX2 6NN</addrLine> </address>

4.6. Lists

4.6.1. The various kinds of lists

The element <list> is used to mark any kind of list. A list is a sequence of text items, which may be ordered, unordered, or a glossary list. Each item may be preceded by an item label (in a glossary list, this label is the term being defined):

<list>
contains any sequence of items organized as a list. Attributes include:
type
describes the form of the list. This attribute can have the following values:
  • unordered (for lists with bullet-marked items)
  • ordered (for lists with numbered or lettered items)
  • gloss (for lists consisting of a set of technical terms, each marked with a <label> element and accompanied by a gloss or definition marked as an <item>)
If the attribute is omitted, the default is for the list to be an unordered list.
rend
describes how the labels should appear. The rend attribute can have the following values:
  • no-bullets (for producing unordered lists with no bullet points)
  • lower-alpha (for producing ordered lists with labels a, b, c, ...)
  • upper-alpha (for producing ordered lists with labels A, B, C, ...)
  • lower-roman (for producing ordered lists with labels i, ii, iii, ...)
  • upper-roman (for producing ordered lists with labels I, II, III, ...)
If the attribute is omitted, the default is to produce the labels 1, 2, 3, ... (for ordered lists) or plain bullet points (for unordered lists).
<item>
contains one component of a list.
<label>
contains the label associated with an item in a list; in glossaries, marks the term being defined.

Individual list items are tagged with <item>. The first <item> may optionally be preceded by a <head>, which gives a heading for the list. The numbering of a list may be omitted (if reconstructible), indicated using the n attribute on each item, or (rarely) tagged as content using the <label> element. In order to achieve the same result with different browsers, the value of n should be greater than 0.

4.6.2. Examples of lists

Example 1

<list>  <head>An unordered list</head>  <item>First item in list</item>  <item>Second item in list</item>  <item>Third item in list</item> </list>
An unordered list
  • First item in list
  • Second item in list
  • Third item in list

Example 2

<list type="ordered">  <head>An ordered list</head>  <item>First item in list</item>  <item>Second item in list</item>  <item>Third item in list</item> </list>
An ordered list
  1. First item in list
  2. Second item in list
  3. Third item in list

Example 3

<list type="ordered">  <head>An ordered list with controlled numbering </head>  <item n="3">First item in list</item>  <item>Second item in list</item>  <item>Third item in list</item> </list>
An ordered list with controlled numbering
  1. First item in list
  2. Second item in list
  3. Third item in list

Example 4

<list type="orderedrend="lower-alpha">  <head>An ordered list with letters for labels</head>  <item>First item in list</item>  <item>Second item in list</item>  <item>Third item in list</item> </list>
An ordered list with letters for labels
  1. First item in list
  2. Second item in list
  3. Third item in list

Example 5

<list type="orderedrend="lower-alpha">  <head>An ordered list with controlled lettering </head>  <item n="9">First item in list</item>  <item>Second item in list</item>  <item>Third item in list</item> </list>
An ordered list with controlled lettering
  1. First item in list
  2. Second item in list
  3. Third item in list

Example 6

<list type="gloss">  <head>A glossary list</head>  <label>One</label>  <item>First item in list</item>  <label>Two</label>  <item>Second item in list</item>  <label>Three</label>  <item>Third item in list</item> </list>
A glossary list
One
First item in list
Two
Second item in list
Three
Third item in list

The styles should not be mixed in the same list.

Example 7

A simple two-column table may be treated as a glossary list, tagged <list type=gloss>. Here, each item comprises a term and a gloss, marked with <label> and <item> respectively.

<list type="gloss">  <head>Vocabulary</head>  <label>nu</label>  <item>now</item>  <label>lhude</label>  <item>loudly</item>  <label>bloweth</label>  <item>blooms</item>  <label>med</label>  <item>meadow</item>  <label>wude</label>  <item>wood</item>  <label>awe</label>  <item>ewe</item>  <label>lhouth</label>  <item>lows</item>  <label>sterteth</label>  <item>bounds, frisks</item>  <label>verteth</label>  <item lang="lat">pedit</item>  <label>murie</label>  <item>merrily</item>  <label>swik</label>  <item>cease</item>  <label>naver</label>  <item>never</item> </list>

The above is rendered as follows:

Vocabulary
nu
now
lhude
loudly
bloweth
blooms
med
meadow
wude
wood
awe
ewe
lhouth
lows
sterteth
bounds, frisks
verteth
pedit
murie
merrily
swik
cease
naver
never

4.6.3. Nested lists

Lists of whatever kind can, of course, nest within list items to any depth required. Here, for example, a glossary list contains two items, each of which is itself a simple list:

<list type="gloss">  <label>EVIL</label>  <item>   <list type="simple">    <item>I am cast upon a horrible desolate island, void of all hope of        recovery.</item>    <item>I am singled out and separated as it were from all the world to be        miserable.</item>    <item>I am divided from mankind &#8212; a solitaire; one banished from        human society.</item>   </list> <!-- end of first nested list -->  </item>  <label>GOOD</label>  <item>   <list type="simple">    <item>But I am alive; and not drowned, as all my ship's company were.</item>    <item>But I am singled out, too, from all the ship's crew, to be spared from        death...</item>    <item>But I am not starved, and perishing on a barren place, affording no        sustenances....</item>   </list> <!-- end of second nested list -->  </item> </list> <!-- end of glossary list -->

The above is rendered as follows:

EVIL
  • I am cast upon a horrible desolate island, void of all hope of recovery.
  • I am singled out and separated as it were from all the world to be miserable.
  • I am divided from mankind - a solitaire; one banished from human society.
GOOD
  • But I am alive; and not drowned, as all my ship's company were.
  • But I am singled out, too, from all the ship's crew, to be spared from death...
  • But I am not starved, and perishing on a barren place, affording no sustenances....

4.7. Tables

The following elements are provided for describing tables:

<table>
contains text displayed in tabular form, in rows and columns.
<row>
contains one row of a table. Attributes include:
role
indicates the kind of information held in the cells of this row. This attribute should have the value label for labels or descriptive information, and data for actual data values. If omitted, it defaults to data.
<cell>
contains one cell of a table. Attributes include:
role
indicates the kind of information held in the cell. This attribute should have the value label for labels or descriptive information, and data for actual data values. If omitted, it defaults to data.
cols
indicates the number of columns occupied by this cell. If omitted, it defaults to 1.
rows
indicates the number of rows occupied by this cell. If omitted, it defaults to 1.

The <table> element can also take the align, summary, width, border, frame, rules, cellspacing and cellpadding attributes defined in HTML, and the conversion to HTML will pass them straight through.

All tables should be given the summary attribute regardless of whether they are for data or page layout. For data tables a short summary of the table content must be added for accessibility. Where a table is used for layout, the summary attribute is included, but left empty.

Here is an example:

<table>  <head>table shows the rise and fall of mortality figures during the plague</head>  <row role="label">   <cell/>   <cell cols="3">years</cell>  </row>  <row role="label">   <cell/>   <cell>1</cell>   <cell>2</cell>   <cell>3</cell>  </row>  <row>   <cell role="label">St. Leonard's, Shoreditch</cell>   <cell>64</cell>   <cell>84</cell>   <cell>119</cell>  </row>  <row>   <cell role="label">St. Botolph's, Bishopsgate</cell>   <cell>65</cell>   <cell>105</cell>   <cell>116</cell>  </row>  <row>   <cell role="label">St. Giles's, Cripplegate</cell>   <cell>213</cell>   <cell>421</cell>   <cell>554</cell>  </row> </table>

The above is rendered as:

table shows the rise and fall of mortality figures during the plague
years
123
St. Leonard's, Shoreditch6484119
St. Botolph's, Bishopsgate65105116
St. Giles's, Cripplegate213421554

4.8. Figures and Graphics

Not all the components of a document are necessarily textual. The most straight forward text will often contain diagrams or illustrations, to say nothing of documents in which image and text are inextricably intertwined, or electronic resources in which the two are complementary.

The following tags and attributes are used to add images to web pages:

<figure>
marks the spot at which a graphic is to be inserted in a document. Attributes include:
url
The location and file name of a graphic.
width
The width to which the graphic should be scaled. If omitted, it defaults to the width of the graphic.
height
The height to which the graphic should be scaled. If omitted, it defaults to the height of the graphic.
scale
The extent which the graphic should be scaled (eg 0.5). If omitted, it defaults to 1.
<figDesc>
contains a textual description of the appearance or content of a graphic, essential for accessible graphics.

A picture is inserted into a document using the url attribute of the <figure> element:

<figure url="fezziPic.png">  <head>Mr Fezziwig's Ball</head>  <figDesc>A Cruikshank engraving showing Mr Fezziwig leading a group of    revellers.</figDesc> </figure>

Usually, a graphic will have at the least an identifying title, which should be encoded using the <head> element. Images which are given a head tag have this text automatically converted to a figure caption and are numbered sequentially throughout the document. It is also essential to include a brief description of the image using <figDesc>. If the image is difficult to describe in just a few words, an alternative page where a full account of the image can be given should be supplied: this extra information should be provided via a [d] link. These are normal url links to normal web pages. By convention the [d] link should be provided next to the image in question; users needing greater detail about a given image will click on the [d] link for more information.

If the image is for decoration only (very rare on OUCS pages), the <figDesc> element should still be included, but in this case it should be left blank. By convention the image is then considered just page decoration and unimportant to the reader.

The way text flows around an image is controlled using a rend value, as described in the Appendix B Rends section.

5. Specialised Features

5.1. Generated Divisions

Most modern document production systems have the ability to automatically generate whole sections such as a table of contents or an index. The TEI OUCS scheme provides an element to mark the location at which such a generated section should be placed.

<divGen>
indicates the location at which a textual division generated automatically by a text-processing application is to appear. Attributes include:
type
specifies what type of generated text division (e.g. index, table of contents, etc.) is to appear. Sample values include: index (an index is to be generated and inserted at this point), toc (a table of contents), figlist (a list of figures) and tablist (a list of tables).
The <divGen> element can be placed anywhere that a division element would be legal, as in the following example:
<front>  <titlePage> ... </titlePage>  <divGen type="toc"/>  <div type="Preface">   <head>Preface</head> ... </div> </front> <body> ... </body> <back>  <div>   <head>Appendix</head> ... </div>  <divGen type="indexn="Index"/> </back>

When an index or table of contents is to be encoded (rather than one being generated) for some reason, the <list> element discussed in section 4.6. Lists should be used.

Appendix A

Module
Element <TEI.2>change
Element <figure>change
Element <change>change
Element <respStmt>change
Element <Button>add
Element <Code>add
Element <Command>add
Element <Field>add
Element <Filespec>add
Element <Icon>add
Element <Input>add
Element <Keyword>add
Element <Key>add
Element <Label>add
Element <Link>add
Element <Menu>add
Element <Output>add
Element <Screen>add
Element <Program>add
Element <Prompt>add
Element <Software>add
Element <Value>add
Element <xptr/>add
Element <xref>add
Class att.globalchange
Element <teiHeader>change
Element <TEI.2>change
Element <ptr/>change
Element <table>change
Element <cell>change
Element <body>change
Element <list>change
Element <ab>change
Element <code>change
Class att.declaringdelete
Class att.handFeaturesdelete
Class att.global.linkingchange
Element <include>add
Element <fallback>add
Element <authority>change
Element <p>change
Element <abbr>change
Element <hi>change
Element <quote>change
Element <q>change
Element <item>change
Element <graphic>change
Element <lb/>change
Element <title>change
Element <div>change

Appendix A.1 Schema tei-oucs: Added components

Appendix A.1.1 <Button>

<Button> A button which a user can see in a user interface
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element Button { tei_att.global.attributes, macro.paraContent }
Example
in the amount to pay, inclusive of VAT, before clicking the <Button>Add to Basket</Button> button.

Appendix A.1.2 <Code>

<Code> Some sort of computer language code, displayed inline
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Code { tei_att.global.attributes, macro.xtext }
Example
The simplest command is <code>#include</code>

Appendix A.1.3 <Command>

<Command> The name of a command to run, such as "xmllint"
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Command { tei_att.global.attributes, macro.xtext }
Example
you must use the <Command>makeweblinks</Command> command before you can see the folders

Appendix A.1.4 <Field>

<Field> A labelled input field in a user interface
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Field { tei_att.global.attributes, macro.xtext }
Example
Finally set the <Field>Outgoing Server</Field> name.

Appendix A.1.5 <Filespec>

<Filespec> (file specification) A file or directory specification of any kind, such as index.xml, /etc/passwd or c:\windows\command.com
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element Filespec { tei_att.global.attributes, macro.paraContent }
Example
<Filespec>C:\Windows\My Documents</Filespec>

Appendix A.1.6 <Icon>

<Icon> An icon in a user interface
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Icon { tei_att.global.attributes, macro.xtext }
Example
Click on the <Icon>Send Status Report</Icon> icon

Appendix A.1.7 <Input>

<Input> Text for a user to type (displayed inline)
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.common model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: body div docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element Input { tei_att.global.attributes, macro.paraContent }
Example
Password: <Input>Your Oxford Account password</Input>

Appendix A.1.8 <Key>

<Key> A key to press, such as F1
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Key { tei_att.global.attributes, macro.xtext }
Example
Press <Key>Ctrl-A</Key> on your keyboard

Appendix A.1.9 <Keyword>

<Keyword> A keyword in some technical code the user is being asked to write or read
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Keyword { tei_att.global.attributes, macro.xtext }
Example
The attributes <Keyword>id</Keyword> and <Keyword>n</Keyword>, indeed, are so widely useful that they are allowed on any element in any TEI schema

Appendix A.1.10 <Label>

<Label> The label for a button, radio box etc, as "Press to submit form"
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address date email emph foreign graphic hi lb name note ptr ref soCalled term title
figures: figure
header: idno
linking: anchor
tagdocs: code gi ident
Declaration
element Label { tei_att.global.attributes, macro.phraseSeq }
Example
Set the <Label>Server Port</Label> to be <Input>587</Input>

Appendix A.1.12 <Menu>

<Menu> The name of a menu in a user interface, such as "File"
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Menu { tei_att.global.attributes, macro.xtext }
Example
select <Menu>Account settings</Menu> from the <Menu>Tools</Menu> menu

Appendix A.1.13 <Output>

<Output> The result of running a command, displayed verbatim in a block
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.inter
Contained by
core: desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote
linking: ab
textstructure: body div docEdition titlePart
May containCharacter data only
Declaration
element Output { tei_att.global.attributes, macro.xtext }
Example
<Output>job completed</Output>

Appendix A.1.14 <Program>

<Program> A program listing, displayed verbatim in a block
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.inter
Contained by
core: desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote
linking: ab
textstructure: body div docEdition titlePart
May contain
core: abbr address date email emph foreign graphic hi lb name note ptr ref soCalled term title
figures: figure
header: idno
linking: anchor
tagdocs: code gi ident
Declaration
element Program { tei_att.global.attributes, macro.phraseSeq }
Example
<Program>i:=0; j:=-1;</Program>

Appendix A.1.15 <Prompt>

<Prompt> The text of a program prompt in a description of its interface
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Prompt { tei_att.global.attributes, macro.xtext }
Example
Telnet prompt. E.g. <Prompt>telnet> open [hostname]</Prompt>

Appendix A.1.16 <Screen>

<Screen> A display of what appears on the screen, shown verbatim in a block
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.inter
Contained by
core: desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote
linking: ab
textstructure: body div docEdition titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element Screen { tei_att.global.attributes, macro.paraContent }
Example
Thanks!<lb/> Your work is complete.

Appendix A.1.17 <Software>

<Software> Some sort of computer program
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element Software { tei_att.global.attributes, macro.xtext }
Example
<Software>Microsoft Word</Software>

Appendix A.1.18 <Value>

<Value> The value for some request in a user interface
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.pPart.data
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element Value { tei_att.global.attributes, macro.paraContent }
Example
<Value>Times-Roman 10pt</Value>

Appendix A.1.19 <fallback>

<fallback> Wrapper for fallback elements if an XInclude fails
Namespacehttp://www.w3.org/2001/XInclude
Modulederived-module-tei-oucs
Member of
Contained by
derived-module-tei-oucs: include
May containCharacter data only
Declaration
element fallback { text }

Appendix A.1.20 <include>

<include> The W3C XInclude element
Namespacehttp://www.w3.org/2001/XInclude
Modulederived-module-tei-oucs
AttributesAttributes
hrefpointer to the resource being included
StatusOptional
Datatype
text
parse
StatusOptional
Legal values are:
xml
[Default]
text
xpointer
StatusOptional
Datatype
text
encoding
StatusOptional
Datatype
text
accept
StatusOptional
Datatype
text
accept-charset
StatusOptional
Datatype
text
accept-language
StatusOptional
Datatype
text
Member of
model.global
Contained by
core: abbr addrLine address author bibl biblScope cit citedRange date editor email emph foreign head hi item label name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell table
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: back body div docAuthor docDate docEdition docImprint docTitle front text titlePage titlePart
May contain
derived-module-tei-oucs: fallback
Declaration
element include { attribute href { text }?, attribute parse { "xml" | "text" }?, attribute xpointer { text }?, attribute encoding { text }?, attribute accept { text }?, attribute accept-charset { text }?, attribute accept-language { text }?, fallback? }

Appendix A.1.21 <xptr/>

<xptr/> (pointer) defines a pointer to another location.
Modulederived-module-tei-oucs
AttributesAttributes att.pointing (@targetLang, @target, @evaluate)
url
StatusOptional
Datatype
text
type
StatusOptional
Legal values are:
transclude
rend
StatusOptional
Datatype1–3 occurrences of 
 
separated by whitespace
Legal values are:
new
rss
rssnoimage
rssimage
rssbrief
rsssummary
rsslimit-all
rsslimit-1
rsslimit-2
rsslimit-3
rsslimit-4
rsslimit-5
rsslimit-6
rsslimit-7
rsslimit-8
rsslimit-9
rsslimit-10
Member of
model.ptrLike
Contained by
core: abbr addrLine author bibl biblScope cit citedRange date desc editor email emph foreign head hi item label monogr name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containEmpty element
Declaration
element xptr { tei_att.pointing.attributes, attribute url { text }?, attribute type { "transclude" }?, attribute rend { list { ( "new" | "rss" | "rssnoimage" | "rssimage" | "rssbrief" | "rsssummary" | "rsslimit-all" | "rsslimit-1" | "rsslimit-2" | "rsslimit-3" | "rsslimit-4" | "rsslimit-5" | "rsslimit-6" | "rsslimit-7" | "rsslimit-8" | "rsslimit-9" | "rsslimit-10" ), ( "new" | "rss" | "rssnoimage" | "rssimage" | "rssbrief" | "rsssummary" | "rsslimit-all" | "rsslimit-1" | "rsslimit-2" | "rsslimit-3" | "rsslimit-4" | "rsslimit-5" | "rsslimit-6" | "rsslimit-7" | "rsslimit-8" | "rsslimit-9" | "rsslimit-10" )?, ( "new" | "rss" | "rssnoimage" | "rssimage" | "rssbrief" | "rsssummary" | "rsslimit-all" | "rsslimit-1" | "rsslimit-2" | "rsslimit-3" | "rsslimit-4" | "rsslimit-5" | "rsslimit-6" | "rsslimit-7" | "rsslimit-8" | "rsslimit-9" | "rsslimit-10" )? } }?, empty }

Appendix A.1.22 <xref>

<xref> (reference) defines a reference to another location, possibly modified by additional text or comment.
Modulederived-module-tei-oucs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.pointing (@targetLang, @target, @evaluate)
url
StatusOptional
Datatype
text
onclick
StatusOptional
Datatype
text
Member of
model.ptrLike
Contained by
core: abbr addrLine author bibl biblScope cit citedRange date desc editor email emph foreign head hi item label monogr name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element xref { tei_att.global.attributes, tei_att.pointing.attributes, attribute url { text }?, attribute [http://www.w3.org/1999/xhtml]onclick { text }?, macro.paraContent }

Appendix A.2 Schema tei-oucs: changed components

Appendix A.2.1 <TEI.2>

<TEI.2> (TEI document) contains a single TEI-conformant document, comprising a TEI header and a text, either in isolation or as part of a <teiCorpus> element. [4. 15.1. ]
Moduletextstructure
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
Contained by
Empty element
May contain
header: teiHeader
textstructure: text
Declaration
element TEI.2 { tei_att.global.attributes, ( teiHeader, ( ( model.resourceLike+, text? ) | text ) ) }
Schematron
<s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> <s:ns prefix="date" uri="http://exslt.org/dates-and-times"/> <s:pattern name="Metadata"> <s:rule context="fileDesc">  <s:assert test="titleStmt/author[not(.='')]">You have not provided an author    name</s:assert>  <s:assert test="titleStmt/title[not(.='')]">You have not provided a title for    the document</s:assert>  <s:assert test="editionStmt/edition/date[not(.='')]">You have not provided a    date for the document</s:assert></s:rule> <s:rule context="revisionDesc">  <s:assert    test="change/date[contains(.,'$LastChangedDate:')]">You must    have a Subversion $LastChangedDate: $ field in a    revision statement</s:assert>  <s:assert    test="change/item[contains(.,'$LastChangedRevision:')]">You must    have a Subversion $LastChangedRevision: $ field in a revision statement</s:assert>  <s:assert    test="change/respStmt/name[contains(.,'$LastChangedBy:')]">You must    have a Subversion $LastChangedBy: $ field in a revision statement</s:assert></s:rule></s:pattern> <s:pattern name="Tables"> <s:rule context="table">  <s:assert test="not(parent::body)">Do not use tables to lay out the document body</s:assert></s:rule></s:pattern>
Schematron
<s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/>
Schematron
<s:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/>
Example
<TEI.2 version="5.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.2>
NoteThis element is required.

Appendix A.2.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. ]
Modulelinking
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.typed (@type, @subtype) att.fragmentable (@part)
Member of
model.pLike
Contained by
core: item note q quote
figures: cell
header: availability calendar editionStmt encodingDesc licence publicationStmt scriptNote seriesStmt sourceDesc styleDefDecl
linking: ab
textstructure: back body div front
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note p ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: ab anchor
tagdocs: code eg gi ident
Declaration
element ab { tei_att.global.attributes, tei_att.typed.attributes, tei_att.fragmentable.attributes, macro.specialPara }
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 A.2.3 <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. ]
Modulecore
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.responsibility (@cert, @resp) att.typed (type, @subtype)
typeallows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatype
data.enumerated
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]]
expand
StatusOptional
Datatype
text
Member of
model.choicePart model.pPart.editorial
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address date email emph foreign graphic hi lb name note ptr ref soCalled term title
figures: figure
header: idno
linking: anchor
tagdocs: code gi ident
Declaration
element abbr { tei_att.global.attributes, tei_att.responsibility.attributes, tei_att.typed.attribute.subtype, attribute type { data.enumerated }?, attribute expand { text }?, 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 A.2.4 att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
Moduletei
MembersButton Code Command Field Filespec Icon Input Key Keyword Label Link Menu Output Program Prompt Screen Software TEI.2 Value ab abbr addrLine address anchor author authority availability back bibl biblScope calendar change cit citedRange classRef code date desc div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor eg elementRef email emph encodingDesc figDesc fileDesc foreign front gi head ident idno keywords label licence listBibl listChange macroRef monogr name note notesStmt profileDesc ptr publicationStmt publisher ref resp respStmt revisionDesc row scriptNote series seriesStmt soCalled sourceDesc styleDefDecl teiHeader term text textClass title titlePage titlePart titleStmt xref
AttributesAttributes att.global.linking (@corresp)
id
StatusOptional
Datatype
text
lang
StatusOptional
Datatype
text
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatype
text
Valuesthe value consists of a single token which may however contain punctuation characters, whitespace or word separating characters. It need not be restricted to numbers.
NoteThe n attribute may be 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
ValuesThe value must conform to 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.
<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.
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
<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, 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.
renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
<head   rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi    rendition="#no">New Blazing-World</hi>. </head> <!-- elsewhere... --> <rendition   xml:id="sc"   scheme="css">font-variant: small-caps</rendition> <rendition   xml:id="no"   scheme="css">font-variant: normal</rendition> <rendition   xml:id="ac"   scheme="css">text-align: center</rendition>
NoteThe rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.Where both rendition and rend are supplied, the latter is understood to override or complement the former.
Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.
xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatype
data.pointer
<div   type="bibl">  <head>Bibliography</head>  <listBibl    xml:base="http://www.lib.ucdavis.edu/BWRP/Works/">   <bibl     n=" 1">    <author>     <name>Landon, Letitia Elizabeth</name>    </author>    <ref      target="LandLVowOf.sgm">     <title>The Vow of the Peacock</title>    </ref>   </bibl>   <bibl     n=" 2">    <author>     <name>Compton, Margaret Clephane</name>    </author>    <ref      target="NortMIrene.sgm">     <title>Irene, a Poem in Six Cantos</title>    </ref>   </bibl>   <bibl     n=" 3">    <author>     <name>Taylor, Jane</name>    </author>    <ref      target="TaylJEssay.sgm">     <title>Essays in Rhyme on Morals and Manners</title>    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatype
data.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
NoteThe XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

Appendix A.2.5 att.global.linking

att.global.linking defines a set of attributes for hypertextual linking.
Modulelinking
Membersatt.global[Button Code Command Field Filespec Icon Input Key Keyword Label Link Menu Output Program Prompt Screen Software TEI.2 Value ab abbr addrLine address anchor author authority availability back bibl biblScope calendar change cit citedRange classRef code date desc div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor eg elementRef email emph encodingDesc figDesc fileDesc foreign front gi head ident idno keywords label licence listBibl listChange macroRef monogr name note notesStmt profileDesc ptr publicationStmt publisher ref resp respStmt revisionDesc row scriptNote series seriesStmt soCalled sourceDesc styleDefDecl teiHeader term text textClass title titlePage titlePart titleStmt xref]
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.

Appendix A.2.6 <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. ]
Moduleheader
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.publicationStmtPart
Contained by
core: monogr
header: publicationStmt
May contain
core: abbr address date email emph foreign hi lb name note ptr ref soCalled term title
figures: figure
header: idno
linking: anchor
tagdocs: code gi ident
Legal values are:
admin@it.ox.ac.uk
apple-training@it.ox.ac.uk
buildings@it.ox.ac.uk
courses@it.ox.ac.uk
cud@it.ox.ac.uk
datacentre@it.ox.ac.uk
domain-registration@it.ox.ac.uk
erewhon@it.ox.ac.uk
greenit@it.ox.ac.uk
groupware@it.ox.ac.uk
helpcentre.manager@it.ox.ac.uk
hfs@ox.ac.uk
infosec@it.ox.ac.uk
infodev@it.ox.ac.uk
its3@it.ox.ac.uk
itsupport@ict.ox.ac.uk
itsupport@it.ox.ac.uk
licenses@it.ox.ac.uk
ltg@it.ox.ac.uk
marketing@it.ox.ac.uk
networks@it.ox.ac.uk
nsms@it.ox.ac.uk
ops@it.ox.ac.uk
oxcert@it.ox.ac.uk
oxpoints@it.ox.ac.uk
pcbreakdown@it.ox.ac.uk
podcasts@it.ox.ac.uk
recruitment@it.ox.ac.uk
registration@it.ox.ac.uk
researchsupport@it.ox.ac.uk
rts@it.ox.ac.uk
secondlife@it.ox.ac.uk
security@it.ox.ac.uk
shop@it.ox.ac.uk
sis@it.ox.ac.uk
software@it.ox.ac.uk
sysdev@it.ox.ac.uk
telecommunications@it.ox.ac.uk
thames.suite@it.ox.ac.uk
turnitin@it.ox.ac.uk
webdesign@it.ox.ac.uk
webex@it.ox.ac.uk
weblearn@it.ox.ac.uk
webmaster@it.ox.ac.uk
Declaration
element authority { tei_att.global.attributes, macro.phraseSeq.limited }
Example
<authority>John Smith</authority>

Appendix A.2.7 <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. ]
Moduletextstructure
AttributesAttributesatt.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
deflist-numbers
nonumber
number
past
redcarpet
spaceimage
onload
StatusOptional
Datatype
text
onunload
StatusOptional
Datatype
text
Member of
Contained by
textstructure: text
May contain
core: bibl cit desc divGen head label lb list listBibl note p q quote
derived-module-tei-oucs: Input Output Program Screen include
figures: figure table
linking: ab anchor
tagdocs: eg
textstructure: div docAuthor docDate
Declaration
element body { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, attribute rend { "deflist-numbers" | "nonumber" | "number" | "past" | "redcarpet" | "spaceimage" }?, attribute [http://www.w3.org/1999/xhtml]onload { text }?, attribute [http://www.w3.org/1999/xhtml]onunload { text }?, ( 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 A.2.8 <cell>

<cell> contains one cell of a table. [14.1.1. ]
Modulefigures
AttributesAttributes att.tableDecoration (@role, @rows, @cols) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
bold
label
shaded
Brown
Green
Midblue
Olive
Red
red
green
turquoise
orange
yellow
Yellow
grade1
grade2
grade3
grade4
grade5
grade6
td-centre
yes
no
width
StatusOptional
Datatype
text
align
StatusOptional
Legal values are:
right
left
top
middle
centre
center
Member of
Contained by
figures: row
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note p ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: ab anchor
tagdocs: code eg gi ident
Declaration
element cell { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.tableDecoration.attributes, attribute rend { "bold" | "label " | "shaded " | "Brown" | "Green" | "Midblue" | "Olive" | "Red" | "red" | "green" | "turquoise" | "orange" | "yellow" | "Yellow" | "grade1" | "grade2" | "grade3" | "grade4" | "grade5" | "grade6" | "td-centre" | "yes" | "no" }?, attribute width { text }?, attribute align { "right" | "left" | "top" | "middle" | "centre" | "center" }?, 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 A.2.9 <change>

<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.5. 2.4.1. ]
Moduleheader
AttributesAttributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.docStatus (@status) att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.typed (@type, @subtype)
targetpoints to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
header: listChange revisionDesc
May contain
core: date item respStmt
Declaration
element change { tei_att.ascribed.attributes, tei_att.datable.attributes, tei_att.docStatus.attributes, tei_att.global.attributes, tei_att.typed.attributes, attribute target { list { data.pointer+ } }?, ( date, respStmt, item ) }
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 A.2.10 <code>

<code> contains literal code from some formal language such as a programming language. [22.1.1. ]
Moduletagdocs
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.emphLike
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May containCharacter data only
Declaration
element code { tei_att.global.attributes, text }
Example
<code lang="JAVA"> Size fCheckbox1Size = new Size(); fCheckbox1Size.Height = 500; fCheckbox1Size.Width = 500; xCheckbox1.setSize(fCheckbox1Size); </code>

Appendix A.2.11 <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. ]
Moduletextstructure
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (subtype, @type)
Member of
model.divLike
Contained by
textstructure: back body div front
May contain
core: bibl cit desc divGen head label lb list listBibl note p q quote
derived-module-tei-oucs: Input Output Program Screen include
figures: figure table
linking: ab anchor
tagdocs: eg
textstructure: div docAuthor docDate
Declaration
element div { tei_att.global.attributes, tei_att.divLike.attributes, tei_att.typed.attribute.type, ( ( model.divTop | model.global )*, ( ( ( ( ( model.divLike | model.divGenLike ), model.global* )+ ) | ( ( ( model.common ), model.global* )+, ( ( model.divLike | model.divGenLike ), model.global* )* ) ), ( ( model.divBottom ), model.global* )* )? ) }
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 A.2.12 <figure>

<figure> groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. ]
Modulefigures
AttributesAttributes att.placement (@place) att.typed (@type, @subtype) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype1–3 occurrences of 
 
separated by whitespace
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
border
bordergrey
centre
centreimage
floatimage
floatimageRight
iconimage
image-above
inline
inlinetable
margin-right
no
noborder
nowrap
panorama
pic-left
pic-right
left
right
rightnoborder
shadow
sld
spaceimage
template-screenshot
wrap
yes
urlLocation of figure
StatusOptional
Datatype
text
widthWidth of figure
StatusOptional
Datatype
text
heightHeight of figure
StatusOptional
Datatype
text
scaleScaling of figure (values between 0 and 1)
StatusOptional
Datatype
text
Member of
model.global
Contained by
core: abbr addrLine address author bibl biblScope cit citedRange date editor email emph foreign head hi item label name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell table
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: back body div docAuthor docDate docEdition docImprint docTitle front text titlePage titlePart
May contain
core: head p
figures: figDesc
Declaration
element figure { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.placement.attributes, tei_att.typed.attributes, attribute rend { list { ( "border" | "bordergrey" | "centre" | "centreimage" | "floatimage" | "floatimageRight" | "iconimage" | "image-above" | "inline" | "inlinetable" | "margin-right" | "no" | "noborder" | "nowrap" | "panorama" | "pic-left" | "pic-right" | "left" | "right" | "rightnoborder" | "shadow" | "sld" | "spaceimage" | "template-screenshot" | "wrap" | "yes" ), ( "border" | "bordergrey" | "centre" | "centreimage" | "floatimage" | "floatimageRight" | "iconimage" | "image-above" | "inline" | "inlinetable" | "margin-right" | "no" | "noborder" | "nowrap" | "panorama" | "pic-left" | "pic-right" | "left" | "right" | "rightnoborder" | "shadow" | "sld" | "spaceimage" | "template-screenshot" | "wrap" | "yes" )?, ( "border" | "bordergrey" | "centre" | "centreimage" | "floatimage" | "floatimageRight" | "iconimage" | "image-above" | "inline" | "inlinetable" | "margin-right" | "no" | "noborder" | "nowrap" | "panorama" | "pic-left" | "pic-right" | "left" | "right" | "rightnoborder" | "shadow" | "sld" | "spaceimage" | "template-screenshot" | "wrap" | "yes" )? } }?, attribute url { text }?, attribute width { text }?, attribute height { text }?, attribute scale { text }?, ( head?, p*, figDesc? ) }
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 A.2.13 <graphic>

<graphic> indicates the location of an inline graphic, illustration, or figure. [3.9. ]
Modulecore
AttributesAttributes att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
bordergrey
centre
floatimage
inline
left
right
shadow
spaced
wrap
Member of
model.graphicLike model.titlepagePart
Contained by
core: abbr addrLine author biblScope citedRange date editor email emph foreign head hi item label name note p publisher q quote ref soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell table
header: edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePage titlePart
May contain
core: desc
Declaration
element graphic { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.media.attributes, tei_att.resourced.attributes, attribute rend { "bordergrey" | "centre" | "floatimage" | "inline" | "left" | "right" | "shadow" | "spaced" | "wrap" }?, 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 A.2.14 <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. 3.3.2. ]
Modulecore
AttributesAttributesatt.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
three
xml
QandA
bold
cite
code
green
important
inbox
Filespec
Button
Label
Program
Keyword
Value
Command
Input
Output
italic
posthidden
postshown
pullQuote
red
small
sup
sub
underline
Member of
model.hiLike
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label name note p publisher q quote ref resp soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element hi { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, attribute rend { "three" | "xml" | "QandA" | "bold" | "cite" | "code" | "green" | "important" | "inbox" | "Filespec" | "Button" | "Label" | "Program" | "Keyword" | "Value" | "Command" | "Input" | "Output" | "italic" | "posthidden" | "postshown" | "pullQuote" | "red" | "small" | "sup" | "sub" | "underline" }?, 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 A.2.15 <item>

<item> contains one component of a list. [3.7. 2.5. ]
Modulecore
AttributesAttributes att.sortable (@sortKey) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
whitebox
orangebox
turquoisebox
facebook
flickr
delicious
googlegroups
green
important
login
nav
postshown
oucs-icon
search
showall
twitter
user
youtube
outlook10-bullet
outlook-bullet
apple-bullet
entourage-bullet
ie-bullet
ff-bullet
Member of
Contained by
core: list
header: change
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note p ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: ab anchor
tagdocs: code eg gi ident
Declaration
element item { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.sortable.attributes, attribute rend { "whitebox" | "orangebox" | "turquoisebox" | "facebook" | "flickr" | "delicious" | "googlegroups" | "green" | "important" | "login" | "nav" | "postshown" | "oucs-icon" | "search" | "showall" | "twitter" | "user" | "youtube" | "outlook10-bullet" | "outlook-bullet" | "apple-bullet" | "entourage-bullet" | "ie-bullet" | "ff-bullet" }?, macro.specialPara }
Example
<list type="ordered">  <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 A.2.16 <lb/>

<lb/> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. 7.2.5. ]
Modulecore
AttributesAttributes att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
clear
Member of
model.milestoneLike
Contained by
core: abbr addrLine address author bibl biblScope cit citedRange date editor email emph foreign head hi item label listBibl name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell table
header: authority edition licence scriptNote
linking: ab
tagdocs: eg
textstructure: back body div docAuthor docDate docEdition docImprint docTitle front text titlePage titlePart
May containEmpty element
Declaration
element lb { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.edition.attributes, tei_att.spanning.attributes, tei_att.breaking.attributes, attribute rend { "clear" }?, 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 A.2.17 <list>

<list> (list) contains any sequence of items organized as a list. [3.7. ]
Modulecore
AttributesAttributes att.sortable (@sortKey) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype1–3 occurrences of 
 
separated by whitespace
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
agenda
atoz
atoz-popular
bold
box_bl
box_or
classic
fancy
index
lower-alpha
lower-roman
multicol
no-bullets
nonumbers
dlistalign
old-style
pausing
pausing
quaint
posthidden
removebutton
rss-subscribe-links
section2
saveSpace
section2
sidelist
social
spaced
topics
upper-alpha
upper-roman
typedescribes the form of the list.
StatusOptional
Datatype
data.enumerated
Legal values are:
catalogue
gloss
ordered
unordered
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
model.listLike
Contained by
core: desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: keywords licence revisionDesc scriptNote sourceDesc
linking: ab
textstructure: back body div docEdition titlePart
May contain
core: head item label
Declaration
element list { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.sortable.attributes, attribute rend { list { ( "agenda" | "atoz" | "atoz-popular" | "bold" | "box_bl" | "box_or" | "classic" | "fancy" | "index" | "lower-alpha" | "lower-roman" | "multicol" | "no-bullets" | "nonumbers" | "dlistalign" | "old-style" | "pausing" | "pausing" | "quaint" | "posthidden" | "removebutton" | "rss-subscribe-links" | "section2" | "saveSpace" | "section2" | "sidelist" | "social" | "spaced" | "topics" | "upper-alpha" | "upper-roman" ), ( "agenda" | "atoz" | "atoz-popular" | "bold" | "box_bl" | "box_or" | "classic" | "fancy" | "index" | "lower-alpha" | "lower-roman" | "multicol" | "no-bullets" | "nonumbers" | "dlistalign" | "old-style" | "pausing" | "pausing" | "quaint" | "posthidden" | "removebutton" | "rss-subscribe-links" | "section2" | "saveSpace" | "section2" | "sidelist" | "social" | "spaced" | "topics" | "upper-alpha" | "upper-roman" )?, ( "agenda" | "atoz" | "atoz-popular" | "bold" | "box_bl" | "box_or" | "classic" | "fancy" | "index" | "lower-alpha" | "lower-roman" | "multicol" | "no-bullets" | "nonumbers" | "dlistalign" | "old-style" | "pausing" | "pausing" | "quaint" | "posthidden" | "removebutton" | "rss-subscribe-links" | "section2" | "saveSpace" | "section2" | "sidelist" | "social" | "spaced" | "topics" | "upper-alpha" | "upper-roman" )? } }?, attribute type { "catalogue" | "gloss" | "ordered" | "unordered" }?, ( head?, ( item+ | ( label, item )+ ) ) }
Example
<list type="ordered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with <list type="bullets">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </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 type="ordered">   <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 type="ordered">     <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 type="ordered">     <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 type="ordered">     <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 type="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 A.2.18 <p>

<p> (paragraph) marks paragraphs in prose. [3.1. 7.2.5. ]
Modulecore
AttributesAttributes att.fragmentable (@part) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype1–∞ occurrences of 
 
separated by whitespace
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
see-all-link
QandA
action
atoz
bold
bloghead
bcopy
box
boxed
centre
right
left
centretext
clear
download
green
hi
homepagefooter
homepageheading
important
inbox
javascript
listhead
pullquote
rightfloat
question
red
removebutton
showHideMore
speciallookup
Member of
model.pLike
Contained by
core: item note q quote
figures: cell figure
header: availability calendar editionStmt encodingDesc licence publicationStmt scriptNote seriesStmt sourceDesc styleDefDecl
linking: ab
textstructure: back body div front
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element p { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.fragmentable.attributes, attribute rend { list { ( "see-all-link" | "QandA" | "action" | "atoz" | "bold" | "bloghead" | "bcopy" | "box" | "boxed" | "centre" | "right" | "left" | "centretext" | "clear" | "download" | "green" | "hi" | "homepagefooter" | "homepageheading" | "important" | "inbox" | "javascript" | "listhead" | "pullquote" | "rightfloat" | "question" | "red" | "removebutton" | "showHideMore" | "speciallookup" )+ } }?, macro.paraContent }
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 A.2.19 <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. ]
Modulecore
AttributesAttributes att.ascribed (@who) att.source (@source) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
display
eg
Member of
model.qLike
Contained by
core: cit desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote
linking: ab
textstructure: body div docEdition titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note p ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: ab anchor
tagdocs: code eg gi ident
Declaration
element q { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.ascribed.attributes, tei_att.source.attributes, attribute rend { "display" | "eg" }?, 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 A.2.20 <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. 4.3.1. ]
Modulecore
AttributesAttributes att.source (@source) att.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
display
pullquote
Member of
model.quoteLike
Contained by
core: cit desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote
linking: ab
textstructure: body div docEdition titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note p ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: ab anchor
tagdocs: code eg gi ident
Declaration
element quote { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, tei_att.source.attributes, attribute rend { "display" | "pullquote" }?, 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 A.2.21 <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. 2.2.1. 2.2.2. 2.2.5. ]
Modulecore
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
Member of
model.respLike
Contained by
core: bibl monogr series
header: change editionStmt seriesStmt titleStmt
May contain
core: name resp
Declaration
element respStmt { tei_att.global.attributes, resp?, name }
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 A.2.22 <table>

<table> contains text displayed in tabular form, in rows and columns. [14.1.1. ]
Modulefigures
AttributesAttributesatt.global (rend, @id, @lang, @n, @xml:lang, @style, @rendition, @xml:base, @xml:space) att.global.linking (@corresp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global
StatusOptional
Datatype
text
Valuesmay contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
Legal values are:
annrep
hostingcomparision
centretext
formtable
fiveyr
frame
hc_annrep
hostingcomparison
rules
stripeMe
tablesorter
td-right
align
StatusOptional
Datatype
text
summary
StatusOptional
Datatype
text
width
StatusOptional
Datatype
text
border
StatusOptional
Datatype
text
frame
StatusOptional
Datatype
text
rules
StatusOptional
Datatype
text
cellspacing
StatusOptional
Datatype
text
cellpadding
StatusOptional
Datatype
text
rowsindicates the number of rows in the table.
StatusOptional
Datatype
data.count
ValuesIf no number is supplied, an application must calculate the number of rows.
NoteRows should be presented from top to bottom.
cols(columns) indicates the number of columns in each row of the table.
StatusOptional
Datatype
data.count
ValuesIf no number is supplied, an application must calculate the number of columns.
NoteWithin each row, columns should be presented left to right.
Member of
model.listLike
Contained by
core: desc emph head hi item note p q quote ref title
derived-module-tei-oucs: Button Filespec Input Screen Value xref
figures: cell figDesc
header: licence scriptNote sourceDesc
linking: ab
textstructure: back body div docEdition titlePart
May contain
core: graphic head lb note
derived-module-tei-oucs: include
figures: figure row
linking: anchor
textstructure: docAuthor docDate
Declaration
element table { tei_att.global.attribute.id, tei_att.global.attribute.lang, tei_att.global.attribute.n, tei_att.global.attribute.xmllang, tei_att.global.attribute.style, tei_att.global.attribute.rendition, tei_att.global.attribute.xmlbase, tei_att.global.attribute.xmlspace, tei_att.global.linking.attribute.corresp, attribute rend { "annrep" | "hostingcomparision" | "centretext" | "formtable" | "fiveyr" | "frame" | "hc_annrep" | "hostingcomparison" | "rules" | "stripeMe" | "tablesorter" | "td-right" }?, attribute align { text }?, attribute summary { text }?, attribute width { text }?, attribute border { text }?, attribute frame { text }?, attribute rules { text }?, attribute cellspacing { text }?, attribute cellpadding { text }?, 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 A.2.23 <teiHeader>

<teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page prefixed to every TEI-conformant text. [2.1.1. 15.1. ]
Moduleheader
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp))
typespecifies the kind of document to which the header is attached, for example whether it is a corpus or individual text.
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.
Member of
Contained by
textstructure: TEI.2
May contain
header: encodingDesc fileDesc profileDesc revisionDesc
Declaration
element teiHeader { tei_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 A.2.24 <title>

<title> contains a title for any kind of work. [3.11.2.2. 2.2.1. 2.2.5. ]
Modulecore
AttributesAttributes att.global (@id, @lang, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp)) att.canonical (@key, @ref) att.typed (@type, @subtype)
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
m
s
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
model.emphLike model.msQuoteLike
Contained by
core: abbr addrLine author bibl biblScope citedRange date desc editor email emph foreign head hi item label monogr name note p publisher q quote ref resp series soCalled term title
derived-module-tei-oucs: Button Filespec Input Label Program Screen Value xref
figures: cell figDesc
header: authority edition licence scriptNote seriesStmt titleStmt
linking: ab
tagdocs: eg
textstructure: docAuthor docDate docEdition docImprint titlePart
May contain
core: abbr address bibl cit date desc email emph foreign graphic hi label lb list listBibl name note ptr q quote ref soCalled term title
figures: figure table
header: idno
linking: anchor
tagdocs: code eg gi ident
Declaration
element title { tei_att.global.attributes, tei_att.canonical.attributes, tei_att.typed.attributes, attribute level { "a" | "m" | "s" }?, 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 A.3 Schema tei-oucs: unchanged components

addrLine: (address line) contains one line of a postal address. [3.5.2. 2.2.4. 3.11.2.4. ]
address: contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. 2.2.4. 3.11.2.4. ]
anchor: (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. 16.4. ]
att.ascribed: provides attributes for elements representing speech or action that can be ascribed to a specific individual. [1. ]
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. ]
att.cReferencing: provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.
att.canonical: provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
att.datable: provides attributes for normalization of elements that contain dates, times, or datable events.
att.datable.w3c: provides attributes for normalization of elements that contain datable events using the W3C datatypes. [3.5.4. 13.3.6. ]
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. ]
att.dimensions: provides attributes for describing the size of physical objects.
att.divLike: provides attributes common to all elements which behave in the same way as divisions. [4. ]
att.docStatus: provides attributes for use on metadata elements describing the status of a document.
att.editLike: provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [1. ]
att.edition: provides attributes identifying the source edition from which some encoded feature derives.
att.fragmentable: groups structural elements which may be fragmented, usually as a consequence of some overlapping hierarchy.
att.internetMedia: provides attributes for specifying the type of a computer resource using a standard taxonomy.
att.media: provides attributes for specifying display and related properties of external media.
att.naming: provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. 13.3.5. ]
att.personal: (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. ]
att.placement: provides attributes for describing where on the source page or object a textual element appears. [3.4.3. 11.3.1.4. ]
att.pointing: defines a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. 3.6. ]
att.ranging: provides attributes for describing numerical ranges.
att.readFrom: groups specification elements which derive components from some external source.
att.resourced: provides attributes by which a resource (such as an externally held media file) may be located.
att.responsibility: provides attributes indicating who is responsible for something asserted by the markup and the degree of certainty associated with it. [3.4. 17.3. 13.1.1. ]
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. [1. ]
att.source: provides attributes for pointing to the source of a bibliographic reference. [3.3.3. 8.3.4. ]
att.spanning: provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [1.3.1. ]
att.styleDef: groups elements which specify the name of a formal definition language used to provide formatting or rendition information.
att.tableDecoration: provides attributes used to decorate rows or cells of a table. [14. ]
att.translatable: provides attributes used to indicate the status of a translatable portion of an ODD document.
att.typed: provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. ]
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. 2.2.1. ]
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. ]
back: (back matter) contains any appendixes, etc. following the main part of a text. [4.7. 4. ]
bibl: (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. 2.2.7. 15.3.2. ]
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.4. ]
calendar: describes a calendar or dating system used in a dating formula in the text. [2.4.4. ]
cit: (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. 4.3.1. 9.3.5.1. ]
citedRange: (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.4. ]
classRef: points to the specification for an attribute or model class which is to be included in a schema [22.4.6. ]
data.certainty: defines the range of attribute values expressing a degree of certainty.
data.count: defines the range of attribute values used for a non-negative integer value used as a count.
data.duration.iso: defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
data.duration.w3c: defines the range of attribute values available for representation of a duration in time using W3C datatypes.
data.enumerated: defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
data.language: defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. ]
data.name: defines the range of attribute values expressed as an XML Name.
data.namespace: defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
data.numeric: defines the range of attribute values used for numeric values.
data.outputMeasurement: defines a range of values for use in specifying the size of an object that is intended for display.
data.pattern: (regular expression pattern) defines attribute values which are expressed as a regular expression.
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.
data.probability: defines the range of attribute values expressing a probability.
data.replacement: defines attribute values which contain a replacement template.
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 specification.
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.
data.truthValue: defines the range of attribute values used to express a truth value.
data.versionNumber: defines the range of attribute values used for version numbers.
data.word: defines the range of attribute values expressed as a single word or token.
data.xTruthValue: (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
data.xmlName: defines attribute values which contain an XML name.
date: contains a date in any format. [3.5.4. 2.2.4. 2.5. 3.11.2.4. 15.2.3. 13.3.6. ]
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. ]
divGen: (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.8.2. ]
docAuthor: (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. ]
docDate: (document date) contains the date of a document, as given (usually) on a title page. [4.6. ]
docEdition: (document edition) contains an edition statement as presented on a title page of a document. [4.6. ]
docImprint: (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. ]
docTitle: (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. ]
edition: (edition) describes the particularities of one edition of a text. [2.2.2. ]
editionStmt: (edition statement) groups information relating to one edition of a text. [2.2.2. 2.2. ]
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. ]
eg: (example) contains any kind of illustrative example. [22.4.4. 22.4.5. ]
elementRef: points to the specification for some element which is to be included in a schema [22.2. ]
email: (electronic mail address) contains an e-mail address identifying a location to which e-mail messages can be delivered. [3.5.2. ]
emph: (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. 3.3.2. ]
encodingDesc: (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. 2.1.1. ]
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. ]
fileDesc: (file description) contains a full bibliographic description of an electronic file. [2.2. 2.1.1. ]
foreign: (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. ]
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. 4. ]
gi: (element name) contains the name (generic identifier) of an element. [22. 22.4.4. ]
ident: (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. ]
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. 2.2.5. 3.11.2.4. ]
keywords: contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. ]
label: contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. ]
licence: contains information about a licence or other legal agreement applicable to the text. [2.2.4. ]
listBibl: (citation list) contains a list of bibliographic citations of any kind. [3.11.1. 2.2.7. 15.3.2. ]
listChange: groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.5. 11.7. ]
macro.limitedContent: (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. ]
macro.paraContent: (paragraph content) defines the content of paragraphs and similar elements. [1.3. ]
macro.phraseSeq: (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. ]
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. ]
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. ]
macro.xtext: (extended text) defines a sequence of character data and gaiji elements.
macroRef: points to the specification for some pattern which is to be included in a schema [22.4.7. ]
model.addrPart: groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. ]
model.addressLike: groups elements used to represent a postal or e-mail address. [1. ]
model.availabilityPart: groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. ]
model.biblLike: groups elements containing a bibliographic description. [3.11. ]
model.biblPart: groups elements which represent components of a bibliographic description. [3.11. ]
model.choicePart: groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. ]
model.common: groups common chunk- and inter-level elements. [1.3. ]
model.dateLike: groups elements containing temporal expressions. [3.5.4. 13.3.6. ]
model.descLike: groups elements which contain a description of their function.
model.div1Like: groups top-level structural divisions.
model.divBottom: groups elements appearing at the end of a text division. [4.2. ]
model.divBottomPart: groups elements which can occur only at the end of a text division. [4.6. ]
model.divGenLike: groups elements used to represent a structural division which is generated rather than explicitly present in the source.
model.divLike: groups elements used to represent un-numbered generic structural divisions.
model.divPart: groups paragraph-level elements appearing directly within divisions. [1.3. ]
model.divTop: groups elements appearing at the beginning of a text division. [4.2. ]
model.divTopPart: groups elements which can occur only at the beginning of a text division. [4.6. ]
model.divWrapper: groups elements which can appear at either top or bottom of a textual division. [4.2. ]
model.egLike: groups elements containing examples or illustrations. [22.1.1. ]
model.emphLike: groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. ]
model.encodingDescPart: groups elements which may be used inside <encodingDesc> and appear multiple times.
model.entryPart: groups non-morphological elements appearing within a dictionary entry. [9.1. ]
model.entryPart.top: groups high level elements within a structured dictionary entry [9.2. ]
model.frontPart: groups elements which appear at the level of divisions within front or back matter. [7.1. ]
model.gLike: groups elements used to represent individual non-Unicode characters or glyphs.
model.global: groups elements which may appear at any point within a TEI text. [1.3. ]
model.graphicLike: groups elements containing images, formulae, and similar objects. [3.9. ]
model.headLike: groups elements used to provide a title or heading at the start of a text division.
model.hiLike: groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. ]
model.highlighted: groups phrase-level elements which are typographically distinct. [3.3. ]
model.imprintPart: groups the bibliographic elements which occur inside imprints. [3.11. ]
model.inter: groups elements which can appear either within or between paragraph-like elements. [1.3. ]
model.lLike: groups elements representing metrical components such as verse lines.
model.labelLike: groups elements used to gloss or explain other parts of a document.
model.limitedPhrase: groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. ]
model.linePart: groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
model.listLike: groups list-like elements. [3.7. ]
model.milestoneLike: groups milestone-style elements used to represent reference systems. [1.3. 3.10.3. ]
model.msItemPart: groups elements which can appear within a manuscript item description.
model.msQuoteLike: groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
model.nameLike: groups elements which name or refer to a person, place, or organization.
model.nameLike.agent: groups elements which contain names of individuals or corporate bodies. [3.5. ]
model.noteLike: groups globally-available note-like elements. [3.8. ]
model.oddRef: groups elements which reference declarations in some markup language in ODD documents.
model.pLike: groups paragraph-like elements.
model.pLike.front: groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. ]
model.pPart.data: groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. ]
model.pPart.edit: groups phrase-level elements for simple editorial correction and transcription. [3.4. ]
model.pPart.editorial: groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. ]
model.personPart: groups elements which form part of the description of a person. [15.2.2. ]
model.phrase: groups elements which can occur at the level of individual words or phrases. [1.3. ]
model.phrase.xml: groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. ]
model.profileDescPart: groups elements which may be used inside <profileDesc> and appear multiple times.
model.ptrLike: groups elements used for purposes of location and reference. [3.6. ]
model.publicationStmtPart: groups elements which may appear within the <publicationStmt> element of the TEI header. [2.2.4. ]
model.qLike: groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. ]
model.quoteLike: groups elements used to directly contain quotations.
model.resourceLike: groups non-textual elements which may appear together with a header and a text to constitute a TEI document. [1.3. ]
model.respLike: groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
model.segLike: groups elements used for arbitrary segmentation. [16.3. 17.1. ]
model.sourceDescPart: groups elements which may be used inside <sourceDesc> and appear multiple times.
model.teiHeaderPart: groups high level elements which may appear more than once in a TEI header.
model.titlepagePart: groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. ]
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. ]
name: (name, proper noun) contains a proper noun or noun phrase. [3.5.1. ]
note: contains a note or annotation. [3.8.1. 2.2.6. 3.11.2.8. 9.3.5.4. ]
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. 2.2. ]
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. 2.1.1. ]
ptr: (pointer) defines a pointer to another location. [3.6. 16.1. ]
publicationStmt: (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. 2.2. ]
publisher: provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. 2.2.4. ]
ref: (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. 16.1. ]
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. 2.2.1. 2.2.2. 2.2.5. ]
revisionDesc: (revision description) summarizes the revision history for a file. [2.5. 2.1.1. ]
row: contains one row of a table. [14.1.1. ]
scriptNote: describes a particular script distinguished within the description of a manuscript or similar resource. [10.7.2. ]
series: (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.11.2.1. ]
seriesStmt: (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. 2.2. ]
soCalled: contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. ]
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. ]
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. ]
term: contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. ]
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. 15.1. ]
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. ]
titlePage: (title page) contains the title page of a text, appearing within the front or back matter. [4.6. ]
titlePart: contains a subsection or division of the title of a work, as indicated on a title page. [4.6. ]
titleStmt: (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. 2.2. ]

Appendix B Rends

There are a number of different rend values that can be applied. These allow text to flow around images, aligning items to the left or right of a page etc.

Rend values available for use in OUCS documents
data
Used in tables to show which rows contain data
label
Used in tables to show which row/column contains cell labels
important
Used to make text stand out - turns it red
centre
Used to centre an image
centretext
Used to centre text
wrap
Used to wrap text around images
nosplit
Unusually this is only applied to the TEI.2 element. Used to prevent a document from spliting on the major divs when it is displayed on the web.
new
Used on links opening in a new window.
pic-left
Use to float an image to the left of the text
pic-right
Use to float an image to the right of the text
spaceimage
Adds space around an image, useful particularly for spacing images away from text in lists.

Appendix C Special Characters

Some characters must be treated specially, using character entities:

EntityCharacterDescription
&amp;&ampersand
&quot; "double quotation mark
&lt;<less-than sign
&gt; >greater-than sign
&apos;'apostrophe

Any other characters which are not on your keyboard can either be entered as numeric entities (see, eg, http://www.tedmontgomery.com/tutorial/HTMLchrc.html) or using UTF-8.

Sebastian Rahtz. Date: 2014-01-10