tei_simple.odd

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="file:/home/lou/Public/TEI/P5/p5odds.rnc" type="application/relax-ng-compact-syntax"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>An Introduction to TEI Simple</title>
      </titleStmt>
      <publicationStmt>
        <p>For distribution from TEI </p>
      </publicationStmt>
      <sourceDesc>
        <p>Derived from TEI Lite <!-- insert guff here --></p>
      </sourceDesc>
    </fileDesc>
    <encodingDesc>
      <p>The following definitions provide support for the style of rendition URI recommended by the
        Simple documentation. For them to be effective in a given document, it will be necessary to
        include in that document a prefix definition which specifies the location of the Simple
        documentation (i.e. the present document) in its <att>replacementPattern</att> attribute. A
        suggested URI is given below.</p>
      <listPrefixDef>
        <prefixDef ident="simple" matchPattern="[a-z]+"
          replacementPattern="http://www.tei-c.org/Simple/tei_simple.odd/#$1"/>
      </listPrefixDef>
      <tagsDecl>
        <rendition xml:id="allcaps">text-transform: uppercase;</rendition>
        <rendition xml:id="blackletter">font-family: fantasy;</rendition>
        <rendition xml:id="bold">font-weight: bold;</rendition>
        <rendition xml:id="bottombraced">padding-bottom: 2pt; border-bottom: dashed gray
          2pt;</rendition>
        <rendition xml:id="block">display:block;</rendition>
        <rendition xml:id="boxed">padding: 2pt; border: solid black 1pt;</rendition>
        <rendition xml:id="centre">text-align: center;</rendition>
        <rendition xml:id="cursive">font-family: cursive;</rendition>
        <rendition xml:id="doublestrikethrough">text-decoration: line-through; color:
          red;</rendition>
        <rendition xml:id="doubleunderline">text-decoration: underline; color: red;</rendition>
        <rendition xml:id="dropcap">font-size : 6em; font-family: cursive; font-weight : bold;
          vertical-align: top; height: 1em; line-height: 1em; float : left; width : 1em; color :
          #c00; margin: 0em; padding: 0px;</rendition>
        <rendition xml:id="float">float:right; display: block; font-size: smaller; clear: right;
          padding: 4pt; width: 15%; </rendition>
        <rendition xml:id="hyphen"/>
        <rendition xml:id="inline">display:inline;</rendition>
        <rendition xml:id="italic">font-style: italic;</rendition>
        <rendition xml:id="justify">text-align: justify;</rendition>
        <rendition xml:id="larger">font-size: larger;</rendition>
        <rendition xml:id="left">text-align: left;</rendition>
        <rendition xml:id="leftbraced">padding-left: 2pt; border-left: dotted gray 2pt; </rendition>
        <rendition xml:id="letterspace">letter-spacing: 0.5em;</rendition>
        <rendition xml:id="literal">font-family:monospace; white-space:pre;</rendition>
        <rendition xml:id="normalstyle">font-style:roman;</rendition>
        <rendition xml:id="normalweight">font-weight:normal;</rendition>
        <rendition xml:id="right">text-align: right;</rendition>
        <rendition xml:id="rightbraced">padding-right: 2pt; border-right: dotted gray 2pt; </rendition>
        <rendition xml:id="rotateleft">-webkit-transform: rotate(90deg); transform:
          rotate(90deg);</rendition>
        <rendition xml:id="rotateright">-webkit-transform: rotate(-90deg); transform:
          rotate(-90deg);</rendition>
        <rendition xml:id="rules">border: 1px solid black; padding:
          2px;border-collapse:collapse;border-spacing:0;</rendition>
        <rendition xml:id="smallcaps">font-variant: small-caps;</rendition>
        <rendition xml:id="smaller">font-size: smaller;</rendition>
        <rendition xml:id="strikethrough">text-decoration: line-through;</rendition>
        <rendition xml:id="subscript">vertical-align: bottom; font-size: smaller;</rendition>
        <rendition xml:id="superscript">vertical-align: super; font-size: smaller;</rendition>
        <rendition xml:id="topbraced">padding-top: 2pt; border-top: dotted gray 2pt; </rendition>
        <rendition xml:id="typewriter">font-family:monospace;</rendition>
        <rendition xml:id="underline">text-decoration: underline;</rendition>
        <rendition xml:id="wavyunderline">text-decoration: underline; text-decoration-style:
          wavy;</rendition>
      </tagsDecl>
    </encodingDesc>
    <revisionDesc>
      <change when="2016-07-28">Check procmodtab; do att classes; re-insert valLists; add some graphics; proofread first half</change>
      <change when="2016-07-23">Rerun checks: remove space</change>
      <change when="2016-07-23">Beef up facsimile</change>
      <change when="2016-07-18">Add some prose at front; add particDesc listPerson and person </change>
      <change when="2016-06-29">Add JC hack for rendition; drastically revise proc mod
        section</change>
      <change when="2016-06-28">Add hdr sections on listPrefixDef, tagUsage, abstract, postscript,
        xenodata</change>
      <change when="2016-06-22">Continue adding discussions for all textual elements</change>
      <change when="2016-06-01"> Various minor tweaks to former Lite material. </change>
      <change when="2016-05-31">Rewrite Jane Eyre discussion a bit. Revise mentions of resourceLike
        elts. Remove weird PIs in valLists. Revise q/quote section to make sense.</change>
      <change when="2016-05-19">Remove initial project desc, XML intro, Simple propaganda, etc. Roll
        up sleeves. </change>
    </revisionDesc>
  </teiHeader>
  <text>
    <front>
      <head>Preface</head>
      <p>This document is the formal specification for TEI Simple, an entry-level customization of
        the Text Encoding Initiative (TEI) Guidelines, intended to be generally useful to a large
        variety of encoders attempting to cope with the standardized representation in digital form
        of a large variety of documents.</p>
      <p>The document is intended to be generally comprehensible and accessible, but does assume
        some knowledge of XML (the encoding language used by the TEI), and of the way it is used by
        the TEI. Further information on both these topics are available from many places, not least
        the TEI's own web site at http://www.tei-c.org.</p>
      <p>The TEI Simple schema was first elaborated as a part of a project funded by the Mellon
        Foundation (2012-2014). The project sought to define a new <soCalled>highly-constrained and
          prescriptive subset </soCalled>of the Text Encoding Initiative (TEI) Guidelines suited to
        the representation of early modern and modern books, a formally-defined set of processing
        rules which permit modern web applications to easily present and analyze the encoded texts,
        mapping to other ontologies, and processes to describe the encoding status and richness of a
        TEI digital text. Its choice of elements reflected the practices followed in the encoding of
        large-scale literary archives, notably those produced by the Text Creation Partnership.
        Practice of other comparable archives such as the German Text Archive was also taken into
        account.</p>
      <p>The most distinctive feature of TEI Simple is its use of the TEI processing model, which
        provides explicit and recommended options for the display or processing of every textual
        element. Programmers developing systems to handle texts encoded with TEI Simple do not have
        to look beyond this when building stylesheets or other components. This greatly reduces the
        complexity of developing applications that will work reliably and consistently for many
        users and across large corpora of documents.</p>
      <p>The TEI Simple schema and the Processing Model were first defined by a working group led by
        Martin Mueller (Northwestern University) and Sebastian Rahtz (Oxford University). Major
        contributions to the project were made by Magdalena Turska (Oxford University), James
        Cummings (Oxford University), and Brian Pytlik Zillig. The changes to the TEI scheme needed
        to support the processing model were reviewed and approved by the TEI Technical Council for
        inclusion in release 3.0.0 of TEI P5 in February 2016. The present document was extensively
        revised and extended by Lou Burnard in July 2016 for submission to the TEI Council. </p>
    </front>
    <body>
      <!--  <xi:include href="out/elementList.xml"/> -->
      <div xml:id="Simple-eg">
        <head>A Short Example</head>
        <p>We begin with a short example. How should we go about transferring into a computer a
          passage of prose, such as the start of the last chapter of Charlotte Bronte's novel
            <title>Jane Eyre</title>? We might start by simply copying what we see on the printed
          page, typing it in such a way that what appears on the screen looks as similar as
          possible, for example, by retaining the original line breaks, by introducing blanks to
          represent the layout of the original headings, page breaks, and paragraphs, and so forth.
          Of course, the possibilities are limited by the nature of the computer program we use to
          capture the text: it may not be possible for example to reflect accurately the typographic
          characteristics of our source with all such software. Some characters in the printed text
          (such as the accented letter <mentioned>a</mentioned> in <mentioned>faàl</mentioned> or
          the long dash) may not be available on the keyboard; some typographic distinctions (such
          as that between small capitals and full capitals) may not be readily accessible. Our first
          attempt tries to mimic the appearance of the former, and simply ignores the latter.</p>
        <p>
          <eg xml:space="preserve">
                                CHAPTER 38

READER, I married him. A quiet wedding we had: he and I, the par-
son and clerk, were alone present. When we got back from church, I
went into the kitchen of the manor-house, where Mary was cooking
the dinner, and John cleaning the knives, and I said --
  'Mary, I have been married to Mr Rochester this morning.' The
housekeeper and her husband were of that decent, phlegmatic
order of people, to whom one may at any time safely communicate a
remarkable piece of news without incurring the danger of having
one's ears pierced by some shrill ejaculation and subsequently stunned
by a torrent of wordy wonderment. Mary did look up, and she did
stare at me; the ladle with which she was basting a pair of chickens
roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the
polishing process; but Mary, bending again over the roast, said only --
   'Have you, miss? Well, for sure!'
   A short time after she pursued, 'I seed you go out with the master,
but I didn't know you were gone to church to be wed'; and she
basted away. John, when I turned to him, was grinning from ear to
ear.
   'I telled Mary how it would be,' he said: 'I knew what Mr Ed-
ward' (John was an old servant, and had known his master when he
was the cadet of the house, therefore he often gave him his Christian
name) -- 'I knew what Mr Edward would do; and I was certain he
would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!' and he politely pulled his forelock.
   'Thank you, John. Mr Rochester told me to give you and Mary
this.'
   I put into his hand a five-pound note.  Without waiting to hear
more, I left the kitchen. In passing the door of that sanctum some time
after, I caught the words --
   'She'll happen do better for him nor ony o' t' grand ladies.' And
again, 'If she ben't one o' th' handsomest, she's noan faa\l, and varry
good-natured; and i' his een she's fair beautiful, onybody may see
that.'
   I wrote to Moor House and to Cambridge immediately, to say what
I had done: fully explaining also why I had thus acted. Diana and

                            474

                 JANE EYRE                      475

Mary approved the step unreservedly. Diana announced that she
would just give me time to get over the honeymoon, and then she
would come and see me.
   'She had better not wait till then, Jane,' said Mr Rochester, when I
read her letter to him; 'if she does, she will be too late, for our honey-
moon will shine our life long: its beams will only fade over your
grave or mine.'
   How St John received the news I don't know: he never answered
the letter in which I communicated it: yet six months after he wrote
to me, without, however, mentioning Mr Rochester's name or allud-
ing to my marriage. His letter was then calm, and though very serious,
kind. He has maintained a regular, though not very frequent correspond-
ence ever since: he hopes I am happy, and trusts I am not of those who
live without God in the world, and only mind earthly things.

      </eg>
        </p>
        <p>This transcription suffers from a number of shortcomings: <list>
            <item>the page numbers and running titles are intermingled with the text in a way which
              makes it difficult for software to distinguish them;</item>
            <item>no distinction is made between single quotation marks and apostrophe, so it is
              difficult to be certain exactly which passages are in direct speech;</item>
            <item>the preservation of the copy text's hyphenation means that simple-minded search
              programs will not find words broken across a line;</item>
            <item>the accented letter in <mentioned>faàl</mentioned> and the long dash have been
              rendered by ad hoc keying conventions which follow no standard pattern and will be
              processed correctly only if the transcriber remembers to mention them in the
              documentation;</item>
            <item>paragraph divisions are marked only by the use of white space, and hard carriage
              returns have been introduced at the end of each line. Consequently, if the size of
              type used to display the text changes, reformatting will be problematic.</item>
          </list></p>
        <p>We now present the same passage, as it might be encoded in TEI Simple. As we shall see,
          there are many ways in which this encoding could be extended, but as a minimum, the TEI
          approach allows us to represent the following distinctions in a standardised way: <list>
            <item>Paragraph and chapter divisions are now marked explicitly by means of tags rather
              than implicitly by white space.</item>
            <item>Apostrophes are retained, but the quotation marks indicating direct speech have
              been removed, and direct speech is now marked explicitly by means of a tag. </item>
            <item>The accented letter and the long dash are accurately represented, using the
              appropriate Unicode character.</item>
            <item>Page divisions have been marked with an empty <gi>pb</gi> tag; the page heading
              and running text have been suppressed. </item>
            <item>The lineation of the original has also been suppressed and words broken by
              typographic accident at the end of a line have been re-assembled without
              comment.</item>
            <item>For convenience of proof reading, a new line has been introduced at the start of
              each paragraph, but the indentation is removed.</item>
          </list>
          <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <pb n="474"/>
            <div type="chapter" n="38">
              <p>Reader, I married him. A quiet wedding we had: he and I, the parson and clerk, were
                alone present. When we got back from church, I went into the kitchen of the
                manor-house, where Mary was cooking the dinner, and John cleaning the knives, and I
                said —</p>
              <p><q>Mary, I have been married to Mr Rochester this morning.</q> The housekeeper and
                her husband were of that decent, phlegmatic order of people, to whom one may at any
                time safely communicate a remarkable piece of news without incurring the danger of
                having one's ears pierced by some shrill ejaculation and subsequently stunned by a
                torrent of wordy wonderment. Mary did look up, and she did stare at me; the ladle
                with which she was basting a pair of chickens roasting at the fire, did for some
                three minutes hang suspended in air, and for the same space of time John's knives
                also had rest from the polishing process; but Mary, bending again over the roast,
                said only —</p>
              <p><q>Have you, miss? Well, for sure!</q></p>
              <p>A short time after she pursued, <q>I seed you go out with the master, but I didn't
                  know you were gone to church to be wed</q>; and she basted away. John, when I
                turned to him, was grinning from ear to ear. <q>I telled Mary how it would be,</q>
                he said: <q>I knew what Mr Edward</q> (John was an old servant, and had known his
                master when he was the cadet of the house, therefore he often gave him his Christian
                name) — <q>I knew what Mr Edward would do; and I was certain he would not wait long
                  either: and he's done right, for aught I know. I wish you joy, miss!</q> and he
                politely pulled his forelock.</p>
              <p><q>Thank you, John. Mr Rochester told me to give you and Mary this.</q></p>
              <p>I put into his hand a five-pound note. Without waiting to hear more, I left the
                kitchen. In passing the door of that sanctum some time after, I caught the words
                —</p>
              <p><q>She'll happen do better for him nor ony o' t' grand ladies.</q> And again, <q>If
                  she ben't one o' th' handsomest, she's noan faàl, and varry good-natured; and i'
                  his een she's fair beautiful, onybody may see that.</q></p>
              <p>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
                explaining also why I had thus acted. Diana and <pb n="475"/> Mary approved the step
                unreservedly. Diana announced that she would just give me time to get over the
                honeymoon, and then she would come and see me.</p>
              <p><q>She had better not wait till then, Jane,</q> said Mr Rochester, when I read her
                letter to him; <q>if she does, she will be too late, for our honeymoon will shine
                  our life long: its beams will only fade over your grave or mine.</q></p>
              <p>How St John received the news I don't know: he never answered the letter in which I
                communicated it: yet six months after he wrote to me, without, however, mentioning
                Mr Rochester's name or alluding to my marriage. His letter was then calm, and though
                very serious, kind. He has maintained a regular, though not very frequent
                correspondence ever since: he hopes I am happy, and trusts I am not of those who
                live without God in the world, and only mind earthly things.</p>
            </div></egXML></p>
        <p>This encoding is expressed in TEI XML, a very widely used and standardised method of
          representing information about a document within the document itself. The transcribed
          words are complemented by special flags within angle brackets, called <term>tags</term>,
          which both characterise and mark the beginning and end of a string of characters. For
          example, each paragraph is marked by a tag <tag>p</tag> at its start, and another
            <tag>/p</tag> at its end. We don't elaborate further on the syntax of TEI XML here.
            <note place="foot">Reference XML tutorials here</note>
        </p>
        <p>Aside from its syntax, it is important to note that this particular encoding represents a
          set of choices or priorities. We have chosen to prioritize and simplify representation of
          the words of the text over representation of the typographic layout associated with them
          in this source document. This makes it easier for a computer to answer questions about the
          words in the document than about its typesetting, reflecting our research priorities. This
          priority also leads us to suppress end-of-line hyphenation. Conceivably Brontë (or her
          printer) intended the word <q>honeymoon</q> to appear as <q>honey-moon</q> on its second
          appearance, though this seems unlikely: our decision to focus on Brontë's text, rather
          than on the printing of it in this particular edition, makes it impossible to be certain.
          Similarly, our decision makes it impossible to use this transcription as a means of
          statistically analysing hyphenation practice. An encoding makes explicit all and only
          those textual features of importance to the encoder.</p>
        <p> It is not difficult to think of ways in which the encoding of even this short passage
          might readily be extended to address other research priorities. For example: <list
            type="simple">
            <item>a regularized form of the passages in dialect could be provided; </item>
            <item>footnotes glossing or commenting on any passage could be added;</item>
            <item>pointers linking parts of this text to others could be added;</item>
            <item>proper names of various kinds could be distinguished from the surrounding
              text;</item>
            <item>names could be classified as personal, geographical, or institutional</item>
            <item>detailed bibliographic information about the text's provenance and context could
              be prefixed to it;</item>
            <item>a linguistic analysis of the passage into sentences, clauses, words, etc., could
              be provided, each unit being associated with appropriate category codes;</item>
            <item>the text could be segmented into narrative or discourse units;</item>
            <item>systematic analysis or interpretation of the text could be included in the
              encoding, with potentially complex alignment or linkage between the text and the
              analysis, or between the text and one or more translations of it;</item>
            <item>passages in the text could be linked to images or sound held on other
              media.</item>
          </list></p>
        <p>In the remainder of this document, we present a number of TEI-recommended ways of
          supporting these and other encoding requirements. These ways generally involve the
          application of specific TEI XML elements, selected from the full range of possibilities
          documented in the TEI <title>Guidelines</title>. Like every other TEI project, TEI Simple
          proposes a view of the TEI Guidelines. This document defines and documents that view. </p>
      </div>
      <div xml:id="Simple-struc">
        <head>The Structure of a TEI Simple Document</head>
        <p>A TEI-conformant text contains (a) a <term>TEI header</term> (marked up as a
            <gi>teiHeader</gi> element) and (b) one or more representations of a text. These
          representations may be of three kinds: a transcribed text, marked up as a <gi>text</gi>
          element; a collection of digital images representing the text, marked up using a
            <gi>facsimile</gi> element; or a literal transcription of one or more documents
          instantiating the text, marked up using the <gi>sourceDoc</gi> element.</p>
        <p>These elements are combined together to form a single <gi>TEI</gi> element, which must be
          declared within the TEI <term>namespace</term>, and therefore usually takes the form
            <tag>TEI xmlns="http://www.tei-c.org/ns/1.0"</tag>
          <note place="foot">A <term>namespace</term> is an XML concept. Its function is to identify
            the vocabulary from which a group of element names are drawn, using a standard
            identifier resembling a web address. The namespace for TEI elements is
              <code>http://www.tei-c.org/ns/1.0</code></note>.</p>
        <p>Some aspects of the TEI header are described in more detail in section <ptr
            target="#Simple-header"/>. In what follows, we will focus chiefly on the use of the
            <gi>text</gi> element, though we describe one way of using the <gi>facsimile</gi>
          element in combination with it or alone in section <ptr target="#Simple-fax"/>. </p>
        <p>A text may be <term>unitary</term> (a single work) or <term>composite</term> (a
          collection of single works, such as an anthology). In either case, the text may have
          optional <term>front</term> or <term>back</term> matter such as title pages, prefaces,
          appendixes etc. We use the term <term>body</term> for whatever comes between these in the
          source document. We discuss various kinds of composite text in section <ptr
            target="#Simple-composite"/> below.</p>
        <p>A unitary text will be encoded using an overall structure like this: <egXML
            xmlns="http://www.tei-c.org/ns/Examples"><TEI>
              <teiHeader><!-- [ TEI Header information ]  --></teiHeader>
              <text>
                <front><!-- [ front matter ... ] -->
                </front>
                <body>
                  <!-- [ body of text ... ]  -->
                </body>
                <back><!--  [ back matter ...  ] -->
                </back>
              </text>
            </TEI></egXML></p>


        <p>In each of the following sections we include a short list of the TEI
            <term>elements</term> under discussion, along with a brief description, and in most
          cases an example of how they are used. Throughout the text, element names are linked to
          tjheir detailed reference documentation, as given in the TEI <title>Guidelines</title>.
          Note that most of the examples provided by the reference documentation, and all of the
          links, are not specific to TEI Simple. </p>
        <p>For example, here are the elements discussed so far: <specList>
            <specDesc key="TEI"/>
            <specDesc key="teiHeader"/>
            <specDesc key="text"/>
            <specDesc key="facsimile"/>
          </specList></p>
      </div>

      <div xml:id="Simple-body">
        <head>Encoding the Body</head>
        <p>As indicated above, a unitary text is encoded by means of a <gi>text</gi> element, which
          may contain the following elements: <specList>
            <specDesc key="front"/>
            <specDesc key="group"/>
            <specDesc key="body"/>
            <specDesc key="back"/>
          </specList> Elements specific to front and back matter are described below in section <ptr
            target="#Simple-fronbac"/>. In this section we discuss the elements making up the body
          of a text. A text must always have a body.</p>
        <div xml:id="divs">
          <head>Text Division Elements and Global Attributes</head>
          <p>The body of a prose text may be just a series of paragraphs or similar blocks of text,
            or these may be grouped together into chapters, sections, subsections, etc. The
              <gi>div</gi> element is used to represent any such grouping of blocks. <specList>

              <specDesc key="div" atts="type"/>
            </specList>
          </p>
          <p>The <att>type</att> attribute on the <gi>div</gi> element may be used to supply a
            conventional name for this category of text division in order to distinguish them.
            Typical values might be <q>book</q>, <q>chapter</q>, <q>section</q>, <q>part</q>,
              <q>poem</q>, <q>song</q>, etc. TEI Simple does not constrain the range of values that
            may be used here. </p>
          <p>A <gi>div</gi> element may itself contain further, nested, <gi>div</gi>s, thus
            mimicking the traditional structure of a book, which can be decomposed hierarchically
            into units such as parts, containing chapters, containing sections, and so on. TEI texts
            in general conform to this simple hierarchic model.</p>
          <p> Here as elsewhere the <att>xml:id</att> attribute may be used to supply a unique
            identifier for the division, which may be used for cross references or other links to
            it, such as a commentary, as further discussed in section <ptr target="#Simple-ptrs"/>.
            It is good practice to provide an <att>xml:id</att> attribute for every major structural
            unit in a text, and to derive its values in some systematic way, for example by
            appending a section number to a short code for the title of the work in question, as in
            the examples below. </p>
          <p>The <att>n</att> attribute may be used to supply (additionally or alternatively) a
            short mnemonic name or number for a division, or any other element. 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 <att>n</att> attribute is the
            place to record it; unlike the identifier supplied by <att>xml:id</att>, it does not
            need to be unique.</p>
          <p>The <att>xml:lang</att> attribute may be used to specify the language of the division.
            Languages are identified by an internationally defined code, as further discussed in
            section <ptr target="#z636"/> below.</p>
          <p>The <att>rendition</att> attribute may be used to supply information about the
            rendition (appearance) of a division, or any other element, as further discussed in
            section <ptr target="#Simple-hilites"/> below. Note that this attribute is used to
            describe the appearance of the <emph>source</emph> text, rather than the appearance of
            any intended output when the encoded text is displayed. The two may of course be
            similar, or identical, but the TEI does not assume or require this.</p>
          <p> These four attributes, <att>xml:id</att>, <att>n</att>, <att>xml:lang</att>, and
              <att>rendition</att> are so widely useful that they are allowed on any element in any
            TEI schema: they are called <term>global attributes</term>. Other attributes defined in
            the TEI Simple schema are discussed in section <ptr target="#xatts"/>.</p>
          <p>As noted above, the value of every <att>xml:id</att> attribute must be unique within a
            document. One simple way of ensuring this is to make it reflect the hierarchic structure
            of the document. For example, Smith's <title>Wealth of Nations</title> as first
            published consists of five books, each of which is divided into chapters, while some
            chapters are further subdivided into parts. We might define <att>xml:id</att> values for
            this structure as follows: <egXML xmlns="http://www.tei-c.org/ns/Examples"><body>
                <div xml:id="WN1" n="I" type="book">
                  <div xml:id="WN101" n="I.1" type="chapter">
                    <!-- ... -->
                  </div>
                  <div xml:id="WN102" n="I.2" type="chapter">
                    <!-- ... -->
                  </div>
                  <!-- ... -->
                  <div xml:id="WN110" n="I.10" type="chapter">
                    <div xml:id="WN1101" n="I.10.1" type="part">
                      <!-- ... -->
                    </div>
                    <div xml:id="WN1102" n="I.10.2" type="part">
                      <!-- ... -->
                    </div>
                  </div>
                  <!-- ... -->
                </div>
                <div xml:id="WN2" n="II" type="book">
                  <!-- ... -->
                </div>
              </body></egXML></p>
          <p>A different numbering scheme may be used for <att>xml:id</att> and <att>n</att>
            attributes: this is often useful where a canonical reference scheme is used which does
            not tally with the structure of the work. For example, in a novel divided into books
            each containing chapters, where the chapters are numbered sequentially through the whole
            work, rather than within each book, one might use a scheme such as the following: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><body>
                <div xml:id="TS01" n="1" type="volume">
                  <div xml:id="TS011" n="1" type="chapter">
                    <!-- ... -->
                  </div>
                  <div xml:id="TS012" n="2" type="chapter">
                    <!-- ... --></div>
                </div>
                <div xml:id="TS02" n="2" type="volume">
                  <div xml:id="TS021" n="3" type="chapter">
                    <!-- ... --></div>
                  <div xml:id="TS022" n="4" type="chapter">
                    <!-- ... --></div>
                </div>
              </body></egXML> Here the work has two volumes, each containing two chapters. The
            chapters are numbered conventionally 1 to 4, but the <att>xml:id</att> values specified
            allow them to be regarded additionally as if they were numbered 1.1, 1.2, 2.1, 2.2.</p>
        </div>
        <div xml:id="h25">
          <head>Headings and Closings</head>
          <p>Every <gi>div</gi> may have a title or heading at its start, and (less commonly) a
            trailer such as <q>End of Chapter 1</q> at its end. The following elements may be used
            to transcribe them: <specList>
              <specDesc key="head"/>
              <specDesc key="trailer"/>
            </specList> Some other elements which may be found at the beginning or ending of text
            divisions are discussed below in section <ptr target="#h52"/>.</p>
          <p>Whether or not headings and trailers are included in a transcription is a matter for
            the individual transcriber to decide. Where a heading is completely regular (for example
              <q>Chapter 1</q>) or may be automatically constructed from attribute values (e.g.
              <code>&lt;div type="chapter" n="1"&gt;</code>), it may be omitted; where it contains
            otherwise unrecoverable text it should always be included. For example, the start of
            Hardy's <title>Under the Greenwood Tree</title> might be encoded as follows: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><div xml:id="UGT1" n="Winter" type="Part">
                <div xml:id="UGT11" n="1" type="Chapter">
                  <head>Mellstock-Lane</head>
                  <p>To dwellers in a wood almost every species of tree ... </p>
                </div>
              </div></egXML></p>
        </div>
        <div xml:id="vedr">
          <head>Textual Components</head>
          <p>In prose texts such as the Bronte example above, the divisions are generally composed
            of paragraphs, represented as <gi>p</gi> elements, though in some circumstances it may
            be preferred to use the <soCalled>anonymous block</soCalled> element <gi>ab</gi>. In
            poetic or dramatic texts different elements are used, representing verse lines and
            stanzas in the first case, and individual speeches or stage directions in the second. : <specList>
              <specDesc key="p"/>
              <specDesc key="ab"/>
              <specDesc key="l"/>
              <specDesc key="lg"/>
              <specDesc key="sp"/>
              <specDesc key="speaker"/>
              <specDesc key="stage"/>
            </specList>
          </p>
          <p>We discuss each of these kinds of component separately below.</p>
          <div>
            <head>Verse</head>
            <p>Here, for example, is the start of a poetic text in which verse lines and stanzas are
              tagged: <egXML xmlns="http://www.tei-c.org/ns/Examples"><lg n="I">
                  <l>I Sing the progresse of a deathlesse soule,</l>
                  <l>Whom Fate, with God made, but doth not controule,</l>
                  <!-- ... -->
                  <l>A worke t'out weare Seths pillars, bricke and stone,</l>
                  <l>And holy writs excepted) made to yeeld to none,</l></lg></egXML></p>
            <p>Note that the <gi>l</gi> element marks verse lines, not typographic lines: as
              elsewhere the original lineation of the source text is not therefore preserved by by
              this encoding. The <gi>lb</gi> element described in section <ptr target="#Simple-pln"
              /> might additionally be used to mark typographic lines if so desired. </p>

            <p>In a poetic text it may also be considered useful to identify the rhymes, for which
              the following element may be used: <specList>
                <specDesc key="rhyme" atts="label"/>
              </specList> The following example shows how this element might be used both to
              identify rhyming words or word parts and to assign each rhyme to a part of a rhyming
              pattern by means of its <att>label</att> attribute. The rhyming pattern here is
              specified by the <att>rhyme</att> attribute supplied on the <gi>lg</gi> representing
              the stanza within which the pattern operates. <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><lg rhyme="ABCCBBA">
                  <l>The sunlight on the <rhyme label="A">garden</rhyme></l>
                  <l><rhyme label="A">Harden</rhyme>s and grows <rhyme label="B">cold</rhyme>,</l>
                  <l>We cannot cage the <rhyme label="C">minute</rhyme></l>
                  <l>Wi<rhyme label="C">thin it</rhyme>s nets of <rhyme label="B">gold</rhyme>
                  </l>
                  <l>When all is <rhyme label="B">told</rhyme>
                  </l>
                  <l>We cannot beg for <rhyme label="A">pardon</rhyme>.</l>
                </lg>
              </egXML> The <att>rhyme</att> attribute may be used independently of the
                <gi>rhyme</gi> element, or in combination with it, as above. </p>

          </div>
          <div>
            <head>Drama</head>
            <p>A dramatic text contains speeches, which may be in prose or verse, and will also
              contain stage directions. The <gi>sp</gi> element is used to represent each identified
              speech. It contains an optional speaker indication, marked with the <gi>speaker</gi>
              element, which can be followed by one or more <gi>l</gi> or <gi>p</gi> elements,
              depending on whether the speech is considered to be in prose or in verse. Stage
              directions, whether within or between speeches, are marked using the <gi>stage</gi>
              element. </p>
            <p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
                <sp><speaker>Vladimir</speaker><p>Pull on your trousers.</p></sp>
                <sp><speaker>Estragon</speaker><p>You want me to pull off my trousers?</p></sp>
                <sp><speaker>Vladimir</speaker><p>Pull <emph>on</emph> your trousers.</p></sp>
                <sp><speaker>Vladimir</speaker><p><stage>(realizing his trousers are down)</stage>.
                    True</p></sp>
                <stage>He pulls up his trousers</stage>
                <sp><speaker>Vladimir</speaker><p>Well? Shall we go?</p></sp>
                <sp><speaker>Estragon</speaker><p>Yes, let's go.</p></sp>
                <stage>They do not move.</stage>
              </egXML>
            </p>

            <p>In a verse drama, it is quite common to find that verse lines are split between
              speakers. The easiest way of encoding this is to use the <att>part</att> attribute to
              indicate that the lines so fragmented are incomplete: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><div type="Act" n="I">
                  <head>ACT I</head>
                  <div type="Scene" n="1">
                    <head>SCENE I</head>
                    <stage rendition="#italic"> Enter Barnardo and Francisco, two Sentinels, at
                      several doors</stage>
                    <sp>
                      <speaker>Barn</speaker>
                      <l part="Y">Who's there?</l>
                    </sp>
                    <sp>
                      <speaker>Fran</speaker>
                      <l>Nay, answer me. Stand and unfold yourself.</l>
                    </sp>
                    <sp>
                      <speaker>Barn</speaker>
                      <l part="I">Long live the King!</l>
                    </sp>
                    <sp>
                      <speaker>Fran</speaker>
                      <l part="M">Barnardo?</l>
                    </sp>
                    <sp>
                      <speaker>Barn</speaker>
                      <l part="F">He.</l>
                    </sp>
                    <sp>
                      <speaker>Fran</speaker>
                      <l>You come most carefully upon your hour.</l>
                    </sp>
                    <!-- ... -->
                  </div>
                </div></egXML> The value of the <att>part</att> attribute may indicate just that the
              element bearing it is a fragment rather than a complete verse line
                (<code>part="Y"</code>); alternatively it may indicate whether this is an initial
              (I), medial (M) or F (final) fragment. </p>
            <p>The same mechanism may be applied to stanzas which are divided between two speakers:
                <egXML xmlns="http://www.tei-c.org/ns/Examples"><div>
                  <sp>
                    <speaker>First voice</speaker>
                    <lg type="stanza" part="I">
                      <l>But why drives on that ship so fast</l>
                      <l>Withouten wave or wind?</l>
                    </lg>
                  </sp>
                  <sp>
                    <speaker>Second Voice</speaker>
                    <lg part="F">
                      <l>The air is cut away before.</l>
                      <l>And closes from behind.</l>
                    </lg>
                  </sp>
                  <!-- ... -->
                </div></egXML>
            </p>
            <p>The <gi>sp</gi> element can also be used for dialogue presented in a prose work as if
              it were drama, as in the next example, which also demonstrates the use of the
                <att>who</att> attribute to bear a code identifying the speaker of the piece of
              dialogue concerned: <egXML xmlns="http://www.tei-c.org/ns/Examples"><div>
                  <sp who="#OPI">
                    <speaker>The reverend Doctor Opimian</speaker>
                    <p>I do not think I have named a single unpresentable fish.</p>
                  </sp>
                  <sp who="#GRM">
                    <speaker>Mr Gryll</speaker>
                    <p>Bream, Doctor: there is not much to be said for bream.</p>
                  </sp>
                  <sp who="#OPI">
                    <speaker>The Reverend Doctor Opimian</speaker>
                    <p>On the contrary, sir, I think there is much to be said for him. In the first
                      place....</p>
                    <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the
                      present I will forbear.</p>
                  </sp>
                </div></egXML> Here the <att>who</att> attribute values (<code>#OPI</code> etc.) are
              links, pointing to items in a list of the characters in the novel. In the case of a
              play, this list of characters might appear in the original source as a cast list or
              dramatic personae, which might be marked up using the <gi>castList</gi> element
              described in section <ptr target="#specfronbac"/> below. Such a list would not, of
              course, be appropriate to provide descriptive information about each character, much
              of which does not appear in the original source. Instead a <gi>particDesc</gi>
              (participant description) element should be provided in the TEI Header, as further
              discussed in section <ptr target="#particdesc"/> below. </p>

          </div>
          <div xml:id="abseg">
            <head>Other Kinds of Text Block</head>
            <p>As mentioned above, the <gi>ab</gi> element should be used for blocks of text which
              are not clearly paragraphs, verse lines, or dramatic speeches. Typical examples
              include the canonical verses of the Bible, and the textual blocks of other ancient
              documents which predate the invention of the paragraph, such as Greek inscriptions or
              Egyptian hieroglyphs. The element is also useful as a means of encoding more
              specialised kinds of textual block, such as the question and answer structure of a
              catechism, or the highly formalised substructure of a legal document (if <gi>div</gi>
              is not considered appropriate for these). In more modern documents, it can be used to
              encode semi-organized or fragmentary materials such as an artist's notebook or work in
              progress; or to faithfully capture the substructure of a file produced by an OCR
              sysytem. </p>
          </div>
        </div>

        <div xml:id="Simple-pln">
          <head>Page and Line Numbers</head>
          <p>Page and line breaks etc. may be marked with the following elements. <specList>
              <specDesc key="pb"/>
              <specDesc key="lb"/>
              <specDesc key="cb"/>
              <specDesc key="milestone"/>
              <specDesc key="fw"/>
            </specList> The <gi>pb</gi>, <gi>cb</gi>, and <gi>lb</gi> elements are special cases of
            a general class of elements known as <term>milestone</term>s because they mark reference
            points within a text. The generic <gi>milestone</gi> element can mark any kind of
            reference point: for example, a column break, the start of a new kind of section not
            otherwise tagged, a change of author or style, or in general any significant change in
            the text not enclosed by an XML element. Unlike other elements, milestone elements do
            not enclose a piece of text and make an assertion about it; instead they indicate a
            point in the text where something changes, as indicated by a change in the values of the
            milestone's attributes <att>unit</att>, which indicates the <q>something</q> concerned,
            and <att>n</att> which indicates the new value. </p>
          <p>The <gi>lb</gi>, <gi>cb</gi>, and <gi>pb</gi> elements are shortcuts or <term>syntactic
              sugar</term> for <tag>milestone unit="line"/</tag>
            <tag>milestone unit="column"/</tag> and <tag>milestone unit="page"/</tag> respectively. </p>

          <p>When working from a paginated original, it is often useful to record its pagination,
            whether to simplify later proof-reading. or to align the transcribed text with a set of
            page images, as further discussed below.</p>
          <p> Because <gi>pb</gi> and other milestone elements are empty, they may be placed freely
            within or between other elements. However, it is recommended practice always to put them
            at the <emph>beginning</emph> of whatever unit it is that their presence implies, and
            not to nest them within elements contained by that unit. For example, in the following
            example a page break occurs between two lines of a poem: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <l>Mary had a little lamb</l>
              <pb n="13"/>
              <l>Its fleece was white as snow</l>
            </egXML> The <gi>pb</gi> element should be placed ahead of all the text encoded on the
            13th page. Contrast this with the following less accurate encoding: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <l>Mary had a little lamb</l>
              <l><pb n="13"/>Its fleece was white as snow</l>
            </egXML> This is less accurate because it implies that the second verse line actually
            begins before the page break. </p>
          <p>Similar considerations apply to line breaks (<gi>lb</gi>), though these are less
            frequently considered useful when encoding modern printed textual sources. When
            transcribing manuscripts or early printed books, however, it is often helpful to retain
            them in an encoding, if only to facilitate alignment of transcription and original. Like
              <gi>pb</gi>, the <gi>lb</gi> element should appear <emph>before</emph> the text of the
            line whose start it signals.</p>

          <p>If features such as pagination or lineation are marked for more than one edition, the
            edition in question may be specified by the <att>ed</att> attribute. For example, in the
            following passage we indicate where the page breaks occur in two different editions
              (<val>ED1</val> and <val>ED2</val>) <egXML xmlns="http://www.tei-c.org/ns/Examples"
                ><p>I wrote to Moor House and to Cambridge immediately, to say what I had done:
                fully explaining also why I had thus acted. Diana and <pb ed="ED1" n="475"/> Mary
                approved the step unreservedly. Diana announced that she would <pb ed="ED2" n="485"
                />just give me time to get over the honeymoon, and then she would come and see
                me.</p></egXML></p>
          <p>When transcribing from a paginated source, the encoder must decide whether to suppress
            such features as running titles, page signatures, catch words etc., to replace them by a
            simplified representation using the <gi>pb</gi> element, perhaps using the <att>n</att>
            attribute to preserve some of the information, or to preserve them entirely using the
              <gi>fw</gi> element. The latter strategy is appropriate in encodings which aim to
            retain as much information as possible about the original typography; it will however
            make more complex the processing of the source for other purposes, as in the following
            example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><l>He also fix'd the wandering
                QUEEN OF NIGHT,</l>
              <fw type="sig">Ii 2</fw>
              <fw type="catch">Whether</fw>
              <pb n="244"/>
              <l>Whether she wanes into a scanty orb</l>...<!-- Thomson, Seasons, 1730-->
            </egXML>
          </p>
          <p>As noted above, the <gi>pb</gi> element is also used to align parts of a transcription
            with a digital image of the page concerned. This may be done in a very simple but
            inflexible way by using the <att>facs</att> attribute to point to each page image
            concerned <egXML xmlns="http://www.tei-c.org/ns/Examples"><p>I wrote to Moor House and
                to Cambridge immediately, to say what I had done: fully explaining also why I had
                thus acted. Diana and <pb ed="ED1" n="475" facs="ed1p475.png"/> Mary approved the
                step unreservedly... </p></egXML> The <att>facs</att> attribute can supply (as here)
            a filename, or any other form of URI, if for example the page image is stored remotely.
            One drawback of this simplistic approach is that there must be exactly one image file
            per page of text. It is not therefore suitable in the case where the available page
            images represent double page spreads, or where there are multiple images of the same
            page (for example at different resolutions). </p>
          <p>A more powerful approach, discussed in section <ptr target="#simple-fax"/> below, is to
            use the <gi>facsimile</gi> element to define the organisation of the set of images
            representing the text, and then use the <att>facs</att> attribute to point to individual
            components of that representation. </p>
        </div>
        <div xml:id="Simple-hilites">
          <head>Marking Highlighted Phrases</head>
          <div xml:id="faces">
            <head>Changes of Typeface, etc.</head>
            <p>Highlighted words or phrases are those made visibly different from the rest of the
              text, typically by a change of type font, handwriting style, ink colour etc., which is
              intended to draw the reader's attention to some associated change.</p>
            <p>The global <att>rendition</att> attribute can be attached to any element, and used
              wherever necessary to specify details of the highlighting used for it in the source.
              For example, a heading rendered in bold might be tagged <tag>head
                rendition="simple:bold"</tag>, and one in italic <tag>head
                rendition="simple:italic"</tag>.</p>
            <p>The values used for the <att>rendition</att> attribute point to definitions provided
              for the formatting concerned. These definitions are typically provided by a
                <gi>rendition</gi> element in the document's Header, as further discussed in section
                <ptr target="#hdr-rend"/>. </p>
            <p>It is not always possible or desirable to interpret the reasons for such changes of
              rendering in a text. In such cases, the element <gi>hi</gi> may be used to mark a
              sequence of highlighted text without making any claim as to its status. <specList>
                <specDesc key="hi"/>
              </specList></p>
            <p>In the following example, the use of a distinct typeface for the subheading and for
              the included name are recorded but not interpreted: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><p><hi rendition="simple:blackletter">And
                    this Indenture further witnesseth</hi> that the said <hi
                    rendition="simple:italic">Walter Shandy</hi>, merchant, in consideration of the
                  said intended marriage ...</p></egXML></p>
            <p>Alternatively, where the cause for the highlighting can be identified with
              confidence, a number of other, more specific, elements are available. <specList>
                <!-- <specDesc key="emph"/>-->
                <specDesc key="foreign"/>
                <!--<specDesc key="gloss"/>-->
                <specDesc key="label"/>
                <!--<specDesc key="mentioned"/>-->
                <!--<specDesc key="term"/>-->
                <specDesc key="title"/>
              </specList></p>
            <p>Some features (notably quotations <!--and glosses--> titles, and foreign words) may
              be found in a text either marked by highlighting, or with quotation marks. In either
              case, the element <gi>q</gi>
              <!--and
       <gi>gloss</gi>--> (as discussed in the following section) should be
              used. Again, the global <att>rendition</att> can be used to record details of the
              highlighting used in the source if this is thought useful. </p>
            <p>As an example of the elements defined here, consider the following sentence: <q
                rendition="simple:display">On the one hand the <hi rendition="simple:italic"
                  >Nibelungenlied</hi> is associated with the new rise of romance of twelfth-century
                France, the <hi rendition="simple:italic">romans d'antiquité</hi>, the romances of
                Chrétien de Troyes, and the German adaptations of these works by Heinrich van
                Veldeke, Hartmann von Aue, and Wolfram von Eschenbach.</q> Interpreting the role of
              the highlighting, the sentence might be encoded as follows : <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><p>On the one hand the
                    <title>Nibelungenlied</title> is associated with the new rise of romance of
                  twelfth-century France, the <foreign>romans d'antiquité</foreign>, the romances of
                  Chrétien de Troyes, ...</p></egXML> Describing only the appearance of the
              original, it might be encoded like this: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><p>On the one hand the <hi
                    rendition="simple:italic">Nibelungenlied</hi> is associated with the new rise of
                  romance of twelfth-century France, the <hi rendition="simple:italic">romans
                    d'antiquité</hi>, the romances of Chrétien de Troyes, ...</p></egXML></p>
          </div>
          <div xml:id="z635">
            <head>Quotations and Related Features</head>
            <p>Like changes of typeface, quotation marks are conventionally used to denote several
              different features within a text, of which the most frequent is quotation, though many
              other features are possible. The full Guidelines provide additional elements such as
                <gi>mentioned</gi> or <gi>said</gi> to distinguish some of these features. In TEI
              Simple however, we use the <gi>quote</gi> element for quotation only, and the
                <gi>q</gi> element for all other material found within quotation marks in the text<specList>
                <specDesc key="q"/>
                <specDesc key="quote"/>
                <!--specDesc key="said"/-->
                <!--specDesc key="mentioned"/>-->
                <!--specDesc key="soCalled"/>-->
                <!--<specDesc key="gloss"/>-->
              </specList>
            </p>
            <p>Here is a simple example of a quotation: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><p>Few dictionary makers are likely to
                  forget Dr. Johnson's description of the lexicographer as <quote>a harmless
                    drudge.</quote></p></egXML>
            </p>
            <p>As elsewhere, the way that a citation or quotation was printed (for example,
                <term>in-line</term> or set off as a <hi>display</hi> or <hi>block quotation</hi>),
              may be represented using the <att>rendition</att> attribute. This may also be used to
              indicate the kind of quotation marks used.</p>
            <p>Direct speech interrupted by a narrator can be represented simply by ending the
                <gi>q</gi> element and beginning it again after the interruption, as in the
              following example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><p><q>Who-e debel
                    you?</q> — he at last said — <q>you no speak-e, damme, I kill-e.</q> And so
                  saying, the lighted tomahawk began flourishing about me in the dark.</p></egXML>
              If it is important to convey the idea that the two <gi>q</gi> elements together make
              up a single speech, the linking attributes <att>next</att> and <att>prev</att> may be
              used, as described in section <ptr target="#xatts"/>.</p>
            <p>Direct speech may be accompanied by a reference to the source or speaker, using the
                <att>who</att> attribute, whether or not this is explicit in the text, as in the
              following example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><q who="#Wilson"
                  >Spaulding, he came down into the office just this day eight weeks with this very
                  paper in his hand, and he says:—<q who="#Spaulding">I wish to the Lord, Mr.
                    Wilson, that I was a red-headed man.</q></q></egXML> This example also
              demonstrates how quotations may be embedded within other quotations: one speaker
              (Wilson) quotes another speaker (Spaulding).</p>
            <p>The creator of the electronic text must decide whether quotation marks are replaced
              by the tags or whether the tags are added and the quotation marks kept. If the
              quotation marks are removed from the text, the <att>rendition</att> attribute may be
              used to record the way in which they were rendered in the copy text.</p>
            <!-- example please -->
          </div>
          <div xml:id="z636">
            <head>Foreign Words or Expressions</head>
            <p>Words, phrases, or longer stretches of test that are not in the main language of the
              texts may be tagged as such in one of two ways. The global <att>xml:lang</att>
              attribute may be attached to any element to show that it uses some other language than
              that of the surrounding text. Where there is no applicable element, the element
                <gi>foreign</gi> may be used, again using the <att>xml:lang</att> attribute. For
              example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><p>John has real <foreign
                    xml:lang="fr">savoir-faire</foreign>.</p><p>Have you read <title xml:lang="de"
                    >Die Dreigroschenoper</title>?</p></egXML></p>
            <p>As these examples show, the <gi>foreign</gi> element should not be used to tag
              foreign words if some other more specific element such as <gi>title</gi>, or
                <gi>div</gi> applies. </p>
            <p>The value of the <att>xml:lang</att> attribute on an element applies hierarchically
              to everything contained by that element, unless overridden:</p>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <div xml:lang="la">
                <s>Pars haec Latine composita est.</s>
                <s xml:lang="en">Except that this sentence is in English.</s>
                <s>Vita brevis, ars longa.</s>
              </div>
            </egXML>
            <p>Here we specify that the whole <gi>div</gi> element uses the language with the coded
              identifier <q>la</q> i.e., Latin. Since it is contained by that <gi>div</gi> there is
              no need to supply this information again for the first <gi>s</gi> element. The second
                <gi>s</gi> element however overrides this value, and indicates that its content is
              in English (the language with identifier <code>en</code>). The third <gi>s</gi>
              element is again in Latin.</p>
            <p>The codes used to identify languages, supplied on the <att>xml:lang</att> attribute,
              are defined by an international standard <note place="foot">The relevant Internet
                standard is <title>Best Current Practice 47</title> (<ptr
                  target="http://tools.ietf.org/html/bcp47"/>). The authoritative list of registered
                subtags is maintained by IANA and is available at <ptr
                  target="http://www.iana.org/assignments/language-subtag-registry"/>. For a general
                overview of the construction of language tags, see <ptr
                  target="http://www.w3.org/International/articles/language-tags/"/>, and for a
                practical step-by-step guide, see <ptr
                  target="http://www.w3.org/International/questions/qa-choosing-language-tags"
                />.</note>, as further explained in the relevant section of the TEI Guidelines. Some
              simple example codes for a few languages are given here: <table>
                <row>
                  <cell>zh</cell>
                  <cell>Chinese</cell>
                  <cell>grc</cell>
                  <cell>Ancient Greek</cell>
                </row>
                <row>
                  <cell>en</cell>
                  <cell>English</cell>
                  <cell>el</cell>
                  <cell>Greek</cell>
                </row>
                <row>
                  <cell>enm</cell>
                  <cell>Middle English</cell>
                  <cell>ja</cell>
                  <cell>Japanese</cell>
                </row>
                <row>
                  <cell>fr</cell>
                  <cell>French</cell>
                  <cell>la</cell>
                  <cell>Latin</cell>
                </row>
                <row>
                  <cell>de</cell>
                  <cell>German</cell>
                  <cell>sa</cell>
                  <cell>Sanskrit</cell>
                </row>
              </table>
            </p>
          </div>
        </div>
        <div xml:id="Simple-notes">
          <head>Notes</head>
          <p>A note is any additional comment found in a text, marked in some way as being out of
            the main textual stream. A note is always attached to some part of the text, implicitly
            or explicitly: we call this its target, or its <term>point of attachment</term>. The
            element <gi>note</gi> should be used to mark any kind of note whether it appears as a
            separate block of text in the main text area, at the foot of the page, at the end of the
            chapter or volume, in the margin, or in some other place. <specList>
              <specDesc key="note"/>
            </specList>
          </p>
          <p>Notes may be in a different hand or typeface, may be authorial or editorial, and may
            have been added later. The attributes <att>type</att> and <att>resp</att> can be used to
            distinguish between different kinds of notes or identify their authors.</p>
          <p>In a printed or written text, the <term>point of attachment</term> for a note is
            typically represented by a siglum such as an alphanumerical or other character, often in
            superscripted form. When encoding such a text, it is conventional to replace this siglum
            by a note element containing the annotation itself, as in the following example: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <p>...some text <note xml:id="n7">a note about some text</note> .... </p>
            </egXML></p>

          <p>An alternative approach is to encode the point of attachment wherever it appears in the
            text, using for example the <gi>ref</gi> element discussed in the next section, and to
            place the <gi>note</gi> element anywhere convenient. The two can then be associated by
            using the <att>target</att> attribute on the <gi>ref</gi> element to point to the
              <gi>note</gi> element, as in the following example, in which the superscripted 7
            indicating the point of attachment has been retained as part of the encoding: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <p>...some text <ref target="#n7" rendition="simple:superscript">7</ref> .... <note
                  xml:id="n7">a note about some text</note></p>
            </egXML>
          </p>
          <p>It may however be problematic to determine the precise position of the attachment
            point, particularly in the case of marginal notes. A marginal note may also be hard to
            distinguish from a label or subheading which introduces the text with which it is
            associated. Where the purpose of the note is clearly to label the associated text,
            rather than to comment on it, the element <gi>label</gi> may be preferable. Where it is
            clearly a subheading attached to a distinct subdivision, it may be preferable to start a
            new element <gi>div</gi> and encode the subheading as a <gi>head</gi>. Note however that
            a <gi>head</gi> cannot be inserted anywhere except at the beginning of a <gi>div</gi>.
            And where (as in some Early Modern English plays) marginal annotation is systematically
            used to identify speakers, it may be better to represent these using the
              <gi>speaker</gi> element introduced above. In cases of doubt, the encoder should
            decide on a clear policy and preferably document it for the use of others. </p>
        </div>
        <div xml:id="Simple-ptrs">
          <head>Cross References and Links</head>
          <p>Any kind of cross reference or link found at one point in a text which points to
            another part of the same or another document may be encoded using the
            <gi>ref</gi>element discussed in this section. Implicit links (such as the association
            between two parallel texts, or that between a text and its interpretation) may be
            encoded using the linking attributes discussed in section <ptr target="#xatts"/>.</p>
          <div xml:id="ptrs">
            <head>Simple Cross References</head>
            <p><specList>
                <specDesc key="ref"/>

              </specList>
            </p>
            <p>Usually, the presence of a cross-reference or link will be indicated by some text or
              symbol in the source being encoded, which will then become the content of the
                <gi>ref</gi> element. Occasionally, however, and frequently in the case of a born
              digital document, the exact form and appearance of the cross reference text will be
              determined dynamically by the software processing the document. In such cases, the
                <gi>ref</gi> element will have no content, and serve simply to mark a point from
              which a link is to be made, along with the target of the link. </p>
            <p>The following two forms, for example, are logically equivalent : <egXML
                xmlns="http://www.tei-c.org/ns/Examples">See especially <ref target="#SEC12">section
                  12 on page 34</ref>.</egXML>
              <egXML xmlns="http://www.tei-c.org/ns/Examples">See especially <ref target="#SEC12"
                />.</egXML> In both cases, there is a cross reference from the position in the
              source document immediately following the word <mentioned>especially</mentioned> to
              whatever element in the encoded document has the identifier <ident>SEC12</ident>. In
              the first case, the encoder has supplied the required form of the cross reference
                <soCalled>section 12 on page 34</soCalled>; in the second, the task of generating an
              appropriate form of cross reference has been left to the formatting software. Perhaps
              the pagination and section numbers of the document in question are not yet determined;
              perhaps the cross reference sould be replaced by a big red button. In either case,
              however, the value of the <att>target</att> attribute must be the identifier of some
              other element within the current document. Since the passage or phrase being pointed
              at must bear an identifier, it must be an element of some kind. In the following
              example, the cross reference is to a <gi>div</gi> element: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"> ... see especially <ref target="#SEC12"/>.
                ... <div xml:id="SEC12">
                  <head>Concerning Identifiers</head>
                  <!-- ... -->
                </div></egXML>
            </p>
            <p>Because the <att>xml:id</att> attribute is global, any element in a TEI document may
              be pointed to in this way. In the following example, a paragraph has been given an
              identifier so that it may be pointed at: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"> ... this is discussed in <ref
                  target="#pspec">the paragraph on links</ref> ... <p xml:id="pspec">Links may be
                  made to any kind of element ...</p></egXML></p>
            <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 <gi>anchor</gi> element at the appropriate spot. If the target is some
              sequence of words not otherwise tagged, the <gi>seg</gi> element may be used to mark
              them. These two elements are described as follows: <specList>
                <specDesc key="anchor"/>
                <specDesc key="seg"/>
              </specList>
            </p>
            <p>In the following example, <gi>ref</gi> elements have been used to represent points in
              this text which are to be linked in some way to other parts of it; in the first case
              to a point, and in the second, to a sequence of words: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"> Returning to <ref target="#ABCD">the point
                  where I dozed off</ref>, I noticed that <ref target="#EFGH">three words</ref> had
                been circled in red by a previous reader</egXML></p>
            <p>This encoding requires that elements with the specified identifiers
                (<code>ABCD</code> and <code>EFGH</code> in this example) are to be found somewhere
              else in the current document. Assuming that no element already exists to carry these
              identifiers, the <gi>anchor</gi> and <gi>seg</gi> elements may be used: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"> .... <anchor type="bookmark" xml:id="ABCD"
                /> .... ....<seg type="target" xml:id="EFGH"> ... </seg> ...</egXML></p>
            <p>The <att>type</att> attribute should be used (as above) to distinguish amongst
              different purposes for which these general purpose elements might be used in a text.
              Some other uses are discussed in section <ptr target="#xatts"/> below.</p>
          </div>
          <div xml:id="xptrs">
            <head>Pointing to other documents</head>
            <p>So far, we have shown how the <gi>ref</gi> element may be used for cross-references
              or links whose targets occur within the same document as their source. The element may
              also be used to refer to elements in any other XML document or resource, such as a
              document on the web, or a database component. This is possible because the value of
              the <att>target</att> attribute may be any valid <term>universal resource
                indicator</term> (URI)<note place="foot">A full definition of this term, defined by
                the W3C (the consortium which manages the development and maintenance of the World
                Wide Web), is beyond the scope of this tutorial: however, the most frequently
                encountered version of a URI is the familiar <soCalled>URL</soCalled> used to
                indicate a web page, such as <code>http://www.tei-c.org/index.xml</code></note>. </p>
            <p>A URI may reference a web page or just a part of one, for example
                <code>http://www.tei-c.org/index.xml#SEC2</code>. The hash sign indicates that what
              follows it is the identifier of an element to be located within the XML document
              identified by what precedes it: this example will therefore locate an element which
              has an <att>xml:id</att> attribute value of <val>SEC2</val> within the document
              retrieved from <code>http://www.tei-c.org/index.xml</code>. In the examples we have
              discussed so far, the part to the left of the sharp sign has been omitted: this is
              understood to mean that the referenced element is to be located within the current
              document.</p>
            <p>It is also possible to define an abbreviated form of the URI, using a predefined
                <term>prefix</term> separated from the rest of the code by a colon, as for example
                <code>cesr:SEC2</code>. This is known as a <term>private URI</term>, since the
              prefix is not standardized (except that the prefix <code>xml:</code> is reserved for
              use by XML itself). A <gi>prefixDef</gi> element should be supplied within the TEI
              Header specifying how the prefix (here <code>cesr</code>) should be translated to give
              a full URL for the link. This is particularly useful if a document contains many
              references to an external document such as an authority file. </p>
            <p>Parts of an XML document can be specified by means of other more sophisticated
              mechanisms using a language called Xpointer, also defined by the W3C. This is useful
              when, for example, the elements to be linked to do not bear identifiers. Further
              information about this and other forms of link addressing is provided in <ref
                target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html">chapter 16 of
                the TEI Guidelines</ref> but is beyond the scope of the present document.</p>

          </div>
          <div xml:id="xatts">
            <head>Special Kinds of Linking</head>
            <p>The following special purpose <term>linking</term> attributes are defined for every
              element in the TEI Simple schema: <list type="gloss">
                <label><att>ana</att></label>
                <item>links an element with its interpretation.</item>
                <label><att>corresp</att></label>
                <item>links an element with one or more other corresponding elements.</item>
                <label><att>next</att></label>
                <item>links an element to the next element in an aggregate.</item>
                <label><att>prev</att></label>
                <item>links an element to the previous element in an aggregate.</item>
              </list></p>
            <p>The <att>ana</att> (analysis) attribute is intended for use where a set of abstract
              analyses or interpretations have been defined somewhere within a document, as further
              discussed in section <ptr target="#Simple-anal"/>. For example, a linguistic analysis
              of the sentence <q>John loves Nancy</q> might be encoded as follows: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><seg type="sentence" ana="#SVO">
                  <seg type="lex" ana="#NP1">John</seg>
                  <seg type="lex" ana="#VVI">loves</seg>
                  <seg type="lex" ana="#NP1">Nancy</seg>
                </seg></egXML> This encoding implies the existence elsewhere in the document of
              elements with identifiers <val>SVO</val>, <val>NP1</val>, and <val>VV1</val> where the
              significance of these particular codes is explained. Note the use of the <gi>seg</gi>
              element to mark particular components of the analysis, distinguished by the
                <att>type</att> attribute.</p>
            <p>The <att>corresp</att> (corresponding) attribute provides a simple way of
              representing some form of correspondence between two elements in a text. For example,
              in a multilingual text, it may be used to link translation equivalents, as in the
              following example <egXML xmlns="http://www.tei-c.org/ns/Examples">
                <seg xml:lang="fr" xml:id="FR1" corresp="#EN1">Jean aime Nancy</seg>
                <seg xml:lang="en" xml:id="EN1" corresp="#FR1">John loves Nancy</seg></egXML></p>
            <p>The same mechanism may be used for a variety of purposes. In the following example,
              it has been used to represent the correspondences between <q>the show</q> and
                <q>Shirley</q>, and between <q>NBC</q> and <q>the network</q>: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><p><title xml:id="shirley">Shirley</title>,
                  which made its Friday night debut only a month ago, was not listed on <name
                    xml:id="nbc">NBC</name>'s new schedule, although <seg xml:id="network"
                    corresp="#nbc">the network</seg> says <seg xml:id="show" corresp="#shirley">the
                    show</seg> still is being considered.</p></egXML></p>
            <p>The <att>next</att> and <att>prev</att> attributes provide a simple way of linking
              together the components of a discontinuous element, as in the following example:
                <egXML xmlns="http://www.tei-c.org/ns/Examples"><q xml:id="Q1a" next="#Q1b">Who-e
                  debel you?</q> — he at last said — <q xml:id="Q1b" prev="#Q1a">you no speak-e,
                  damme, I kill-e.</q> And so saying, the lighted tomahawk began flourishing about
                me in the dark.</egXML></p>
          </div>


        </div>
      </div>

      <div xml:id="Simple-edit1">
        <head>Editorial Interventions</head>
        <p>The process of encoding an electronic text has much in common with the process of editing
          a manuscript or other text for printed publication. In either case a conscientious editor
          may wish to record both the original state of the source and any editorial correction or
          other change made in it. The elements discussed in this and the next section provide some
          facilities for meeting these needs.</p>
        <div>
          <head>Correction and Normalization</head>
          <p>The following elements may be used to mark <term>correction</term>, that is editorial
            changes introduced where the editor believes the original to be erroneous: <specList>
              <specDesc key="corr"/>
              <specDesc key="sic"/>
            </specList>
          </p>
          <p>The following elements may be used to mark <term>normalization</term>, that is
            editorial changes introduced for the sake of consistency or modernization of a text: <specList>
              <specDesc key="orig"/>
              <specDesc key="reg"/>
            </specList></p>
          <p>Consider, for example, the following famous passage as it appears in the first quarto
            printing of Shakespeare's <title>Henry V</title>: <figure>
              <graphic url="../Images/tableofgreenfields.png" width="400px" height="100px"/>
              <head type="legend">Detail from <title>Henry V</title>, first quarto (1600)</head>
            </figure> in particular the phrase we might transcribe directly as <eg> ... for his Nose
              was as sharp as a Pen, and a Table of green feelds</eg>
          </p>
          <p>A modern editor might wish to make a number of interventions here, specifically to
            modernize (or normalise) the Elizabethan spellings of <mentioned>a'</mentioned> and
              <mentioned>feelds</mentioned> for <mentioned>he</mentioned> and
              <mentioned>fields</mentioned> respectively. They might also want to emend
              <mentioned>table</mentioned> to <mentioned>babbl'd</mentioned>, following an editorial
            tradition that goes back to the 18th century Shakespearian scholar Lewis Theobald. The
            following encoding would then be appropriate: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">... for his Nose was as sharp as a Pen and
                <reg>he</reg>
              <corr resp="#Theobald">babbl'd</corr> of green <reg>fields</reg></egXML></p>
          <p>A more conservative or source-oriented editor, however, might want to retain the
            original, but at the same time signal that some of the readings it contains are in some
            sense anomalous: <egXML xmlns="http://www.tei-c.org/ns/Examples">... for his Nose was as
              sharp as a Pen, and <orig>a</orig>
              <sic>Table</sic> of green <orig>feelds</orig></egXML></p>
          <p>Finally, a modern digital editor may decide to combine both possibilities in a single
            composite text, using the <gi>choice</gi> element. <specList>
              <specDesc key="choice"/>
            </specList> This allows an editor to indicate where alternative encodings are possible:
              <egXML xmlns="http://www.tei-c.org/ns/Examples">... for his Nose was as sharp as a
              Pen, and <choice><orig>a</orig><reg>he</reg></choice>
              <choice><corr resp="#Theobald">babbl'd</corr><sic>Table</sic></choice> of green
                  <choice><orig>feelds</orig><reg>fields</reg></choice>
            </egXML></p>
        </div>
        <div xml:id="Simple-edit2">
          <head>Omissions, Deletions, and Additions</head>
          <p>In addition to correcting or normalizing words and phrases, editors and transcribers
            may also supply missing material, omit material, or transcribe material deleted or
            crossed out in the source. In addition, some material may be particularly hard to
            transcribe because it is hard to make out on the page. The following elements may be
            used to record such phenomena: <specList>
              <specDesc key="add"/>
              <specDesc key="gap"/>
              <specDesc key="del"/>
              <specDesc key="unclear"/>
              <specDesc key="supplied"/>
              <specDesc key="subst"/>
            </specList>
          </p>
          <p>These elements may be used to record changes made by an editor, by the transcriber, or
            (in manuscript material) by the author or scribe. For example, if the source for an
            electronic text read <q>The following elements are provided for for simple editorial
              interventions.</q> then it might be felt desirable to correct the obvious error, but
            at the same time to record the deletion of the superfluous second
              <mentioned>for</mentioned>, thus: <egXML xmlns="http://www.tei-c.org/ns/Examples">The
              following elements are provided for <del resp="#LB">for</del> simple editorial
              interventions.</egXML> The attribute value <code>#LB</code> on the <att>resp</att>
            attribute is used to point to a fuller definition (typically in a <gi>respStmt</gi>
            element) for the person or other agency responsible for correcting the duplication of
              <mentioned>for</mentioned>.</p>
          <p>If the source read <q>The following elements provided for simple editorial
              interventions.</q> (i.e. if the word <mentioned>are</mentioned> had been inadvertently
            dropped) then the the scholar identified as LB might choose to encode the corrected text
            as follows: <egXML xmlns="http://www.tei-c.org/ns/Examples">The following elements <add
                resp="#LB">are</add> provided for simple editorial interventions.</egXML></p>
          <p>These elements may also be used to record the actual writing process, for example to
            record passages which have been deleted, added, corrected etc. whether by the author of
            a literary text or by a scribe copying out a manuscript. An analysis of such documentary
            modifications may be essential before a reading text can be presented, and is clearly of
            importance in the editorial process. </p>
          <p>The example is taken from the surviving authorial manuscript of a poem by the English
            writer Wilfred Owen, a part of which is shown here: </p>
          <figure>
            <graphic url="../Images/PHowen.png" width="400px" height="100px"/>
            <head type="legend">Detail from <title>Dulce et decorum est</title> autograph manuscript
              in the English Faculty Library, Oxford University. </head>
          </figure>
          <p>Owen first wrote <q>Helping the worst amongst us</q>, but then deleted it, adding
              <q>Dragging the worst amongt us</q> over the top. In the same way, he revised the
            phrase <q>half&#x2013;blind</q> by deleting the <q>half&#x2013;</q> and adding
              <q>all</q> above it. In the last line, he started a word beginning <q>fif</q> before
            deleting it and writing the word <q>five&#x2013;nines</q>. We can encode all of this as
            follows: </p>
          <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <l>And towards our distant rest began to trudge,</l>
            <l><subst><del>Helping the worst amongst us</del>
                <add>Dragging the worst amongt us</add>
              </subst>, who&#x2019;d no boots </l>
            <l>But limped on, blood&#x2013;shod. All went lame; <subst>
                <del status="shortEnd">half&#x2013;</del>
                <add>all</add></subst> blind;</l>
            <l>Drunk with fatigue ; deaf even to the hoots</l>
            <l>Of tired, outstripped <del>fif</del> five&#x2013;nines that dropped behind.</l>
          </egXML>
          <p>The tags <gi>add</gi> and <gi>del</gi> elements are used to enclose passages added or
            deleted respectively. Additional attributes are available such as <att>resp</att> to
            indicate responsibility for the modification, or <att>place</att> to indicate where in
            the text (for example, above or below the line) the modification has been made. Where
            the encoder wishes to assert that the addition and deletion make up a single editorial
            act of substitution, these elements can be combined within a <gi>subst</gi> element as
            shown above.</p>
          <p>A very careful examination of Owen&#x2019;s second modification shows that he really
            did write <q>amongt</q> rather than <q>amongst</q>, presumably in error. An equally
            careful editor wishing to restore the missing <q>s</q> might use the <gi>supplied</gi>
            element to indicate that they have done so:</p>
          <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <add>Dragging the worst among<supplied resp="#ED">s</supplied>t us</add>
          </egXML>
          <p>Here the <att>resp</att> attribute has been used to indicate that the <val>S</val> was
            not supplied by Owen but by someone else, specifically the person documented elsewhere
            by an element with the identifier <val>ED</val>. </p>

          <p>Similarly, the <gi>unclear</gi> and <gi>gap</gi> elements may be used together to
            indicate the omission of illegible material; the following example also shows the use of
              <gi>add</gi> for a conjectural emendation: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">One hundred &amp; twenty good regulars joined
              to me <unclear><gap reason="indecipherable"/></unclear> &amp; instantly, would aid me
              signally <add hand="#ed">in?</add> an enterprise against Wilmington.</egXML></p>
          <p>The <gi>del</gi> element marks material which is deleted in a source, but has been
            transcribed as part of the electronic text all the same, while <gi>gap</gi> marks the
            location of source material which is omitted from the electronic text, whether it is
            legible or not. A language corpus, for example, might omit long quotations in foreign
            languages. The <gi>desc</gi> element can be used inside the <gi>gap</gi> element to
            provide a brief characterisation of the omitted material, as in the following examples:
              <egXML xmlns="http://www.tei-c.org/ns/Examples"><p> ... An example of a list appearing
                in a fief ledger of <name type="place">Koldinghus</name>
                <date>1611/12</date> is given below. It shows cash income from a sale of
                honey.</p><gap extent="50 lines"><desc>quotation from ledger (in
                Danish)</desc></gap><p>A description of the overall structure of the account is once
                again ... </p></egXML></p>
          <p>Language corpora (particular those constructed before the widespread use of scanners)
            often systematically omit figures and mathematics: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><p>At the bottom of your screen below the
                mode line is the <term>minibuffer</term>. This is the area where Emacs echoes the
                commands you enter and where you specify filenames for Emacs to find, values for
                search and replace, and so on. <gap reason="graphic"><desc>diagram of Emacs
                    screen</desc></gap>
              </p></egXML></p>

        </div>
        <div>
          <head>Abbreviations and their Expansion</head>
          <p>Like names, dates, and numbers, abbreviations may be transcribed as they stand or
            expanded; they may be left unmarked, or encoded using the following elements: <specList>
              <specDesc key="abbr"/>
              <specDesc key="expan"/>
            </specList>
          </p>
          <p>The <gi>abbr</gi> element is useful as a means of distinguishing semi-lexical items
            such as acronyms or jargon: <egXML xmlns="http://www.tei-c.org/ns/Examples">Every
              manufacturer of <abbr>3GL</abbr> or <abbr>4GL</abbr> languages is currently nailing on
                <abbr>OOP</abbr> extensions</egXML>
          </p>
          <p>The <att>type</att> attribute may be used to distinguish types of abbreviation by their
            function. </p>
          <p>The <gi>expan</gi> element is used to mark an expansion supplied by an encoder. This
            element is particularly useful in the transcription of manuscript materials. For
            example, the character p with a bar through its descender as a conventional
            representation for the word <val>per</val> is commonly encountered in Medieval European
            manuscripts. An encoder may choose to expand this as follows: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><expan>per</expan></egXML>
          </p>

          <p>To record both an abbreviation and its expansion, the <gi>choice</gi> element mentioned
            above may be used to group the abbreviated form with its proposed expansion: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <choice><abbr>wt</abbr><expan>with</expan></choice>
            </egXML>
          </p>
          <p>The elements <gi>expan</gi> and <gi>abbr</gi> should contain a full word, or the
            abbreviated form of a full word respectively. If it is required to tag smaller
            components of an abbreviated word, the following elements are also available in TEI
            Simple: <specList>
              <specDesc key="am"/>
              <specDesc key="ex"/>

            </specList> For a fuller discussion of abbreviations and the intricacies of representing
            them consult the section on <ref
              target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHAB"
              >Abbreviations and Expansion</ref> in the <title>Guidelines</title>. </p>
        </div>
      </div>
      <div xml:id="Simple-names">
        <head>Names, Codes, and Numbers</head>
        <p>The TEI scheme defines elements for a large number of <soCalled>data-like</soCalled>
          features which may appear almost anywhere within almost any kind of text. These features
          may be of particular interest in a range of disciplines; they all relate to objects
          external to the text itself, such as the names of persons and places, strings of code,
          formulae, or numbers and dates. These items may also pose particular problems for natural
          language processing (NLP) applications. The elements described here, by making such
          features explicit, reduce the complexity of processing texts containing them.</p>
        <div xml:id="nomen">
          <head>Names and Referring Strings</head>
          <p>A <term>referring string</term> is any phrase which refers to some person, place,
            object, etc. A <term>name</term> is a referring string which contains proper nouns and
            honorifics only. Two elements are provided to mark such strings: <specList>
              <specDesc key="rs"/>
              <specDesc key="name"/>
            </specList>
          </p>
          <p>The <att>type</att> attribute is used to distinguish amongst (for example) names of
            persons, places and organizations, where this is possible: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><q>My dear <name type="person">Mr.
                  Bennet</name>, </q> said his lady to him one day, <q>have you heard that <name
                  type="place">Netherfield Park</name> is let at last?</q></egXML>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">It being one of the principles of the
                <name type="organization">Circumlocution Office</name> never, on any account
              whatsoever, to give a straightforward answer, <name type="person">Mr Barnacle</name>
              said, <q>Possibly.</q></egXML></p>
          <p>As the following example shows, the <gi>rs</gi> element may be used for a reference to
            a person, place, etc, which does not contain a proper noun or noun phrase. <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><q>My dear <name type="person">Mr.
                  Bennet</name>,</q> said <rs type="person">his lady</rs> to him one
            day...</egXML></p>

          <p>Simply tagging something as a name is rarely enough to enable automatic processing of
            personal names into the canonical forms usually required for reference purposes. The
            name as it appears in the text may be inconsistently spelled, partial, or vague.
            Moreover, name prefixes such as <mentioned>van</mentioned> or <mentioned>de
              la</mentioned>, may or may not be included as part of the reference form of a name,
            depending on the language and country of origin of the bearer.</p>
          <p>The <att>ref</att> attribute provides a way of linking a name with a description of the
            object being named, and may thus act as a normalized identifier for it. It is also very
            useful as a means of gathering together all references to the same individual or
            location scattered throughout a document: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><q>My dear <name type="person" ref="#BENM1"
                  >Mr. Bennet</name>, </q> said <rs type="person" ref="#BENM2">his lady</rs> to him
              one day, <q>have you heard that <name type="place" ref="#NETP1">Netherfield
                  Park</name> is let at last?</q></egXML></p>
          <p>The values used for the <att>ref</att> attribute here (<code>#BENM1</code> etc.) are
            pointers; in this case indicating an element with the identifier <code>BENM1</code> etc.
            somewhere in the current document, though any form of URI could be used. The element
            indicated will typically (for a person) be a <gi>person</gi> element, listed within a
              <gi>particDesc</gi> element, or (for a place) a <gi>place</gi> element, listed within
            a <gi>settingDesc</gi> element in the TEI Header, as further discussed in <ptr
              target="#profDesc"/> below.</p>
          <p>This use should be distinguished from the case of the <gi>reg</gi> (regularization)
            element, which provides a means of marking the standard form of a referencing string as
            demonstrated below: <egXML xmlns="http://www.tei-c.org/ns/Examples"><name type="person"
                key="WADLM1"><choice><sic>Walter de la Mare</sic><reg>de la Mare,
                  Walter</reg></choice></name> was born at <name key="Ch1" type="place"
                >Charlton</name>, in <name key="KT1" type="county">Kent</name>, in 1873.</egXML></p>

        </div>
        <div xml:id="code">
          <head>Formulae, codes, and special characters</head>
          <p>The following elements may be useful when marking up sequences of text that represent
            mathematical expressions, chemical formulae, and the like: <specList>
              <specDesc key="formula"/>
              <specDesc key="g"/>
            </specList>
          </p>
          <p>In many cases, a simple Unicode character suffices to represent the superscript or
            subscript digits and other symbols which may appear inside a mathematical formula:
              <egXML xmlns="http://www.tei-c.org/ns/Examples"><formula>E=mc²</formula></egXML> In
            other more complex cases, the encoder may choose to use a different XML scheme (such as
            MathML) to encode the content of a formula, or a non-XML notation. These possibilities
            are not discussed further here. </p>
          <p>The <gi>g</gi> element is useful in the case that no Unicode character exists to
            represent the character or glyph required. Its <att>ref</att> attribute can be used to
            point to a definition of the symbol intended, while its content (if any) represents a
            Unicode approximation to it: <egXML xmlns="http://www.tei-c.org/ns/Examples">...Thereto
                <g ref="#air">[air]</g> and ... </egXML> The TEI header provides a number of
            additional elements (not further discussed here) for the definition of such non-Unicode
            characters. These appear within the <gi>charDecl</gi> element of the TEI Header. For the
            preceding example, we might provide a definition for the symbol concerned like this:
              <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <char xml:id="air">
                <charName>ALCHEMICAL SYMBOL FOR AIR</charName>
                <mapping type="standard">🜁</mapping>
              </char></egXML> Further details of these and related elements are provided in section
              <ptr target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/WD.html#D25-20"/> of
            the TEI Guidelines. </p>
          <p>The following elements are useful for stretches of code or similar formal language
            appearing within a text: <specList>
              <specDesc key="code"/>
              <specDesc key="email"/>
            </specList>
          </p>
          <egXML xmlns="http://www.tei-c.org/ns/Examples"> This can be expressed in XML as follows :
              <code>&amp;lt;date notBefore="2016-06-23"/></code> Contact the author at
              <email>lou.burnard@gmail.com</email>
          </egXML>
          <p>Note in this example that characters which have a syntactic function in XML (such as
            the ampersand or the angle bracket) must be represented within a Simple document by
            means of an entity reference such as <code>&amp;lt;</code> or <code>&amp;amp;</code>. </p>
          <p>The element <gi>ref</gi> discussed in section <ptr target="#Simple-ptrs"/> should be
            used to represent a coded reference such as a link given as a URL within a text, either
            as content or as an attribute value: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <p>Further discussion of <ref target="http://www.tei-c.org/">the Text Encoding
                  Initiative website</ref> may be found at <ref>http://www.tei-c.org/</ref></p>
            </egXML></p>
        </div>
        <div>
          <head>Dates and Times</head>
          <p>The following elements are provided for the detailed encoding of times and dates: <specList>
              <specDesc key="date"/>
              <specDesc key="time"/>
            </specList>
          </p>
          <p>These elements have a number of attributes which can be used to provide normalised
            versions of their values in various ways. <specList>
              <specDesc key="att.datable" atts="period when notBefore notAfter"/>
            </specList> The <att>when</att> attribute specifies a normalized form for the date or
            time, using one of the standard formats defined by ISO 8601. Partial dates or times
            (e.g. <q>1990</q>, <q>September 1990</q>, <q>twelvish</q>) can be expressed by omitting
            a part of the value supplied, as in the following examples: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><date when="1980-02-21">21 Feb
                1980</date><date when="1990">1990</date><date when="1990-09">September
                1990</date><date when="--09">September</date><date when="2001-09-11T12:48:00">Sept
                11th, 12 minutes before 9
            am</date></egXML><!--Note in the last example the use of a
            normalized representation for the date string which includes a time: this example could
            thus equally well be tagged using the <gi>time</gi> element.-->
          </p>
          <p>These attributes are typically used to make a date or time more easily processable, as
            in the following examples: <egXML xmlns="http://www.tei-c.org/ns/Examples">Given on the
                <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand
                Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of
                the University the Eighty-Sixth.</date></egXML>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <l>specially when it's nine below zero</l>
              <l>and <time when="15:00:00">three o'clock in the afternoon</time></l>
            </egXML> They are also useful in cases where the date concerned is uncertain or only
            vaguely specified: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <p>... <date period="secondEmpire">during the second empire</date></p></egXML>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <date notAfter="1946-12-09" notBefore="1946-11-01">in the weeks shortly before my
                birth</date></egXML></p>
        </div>
        <div>
          <head>Numbers and measurements</head>
          <p>Like dates, both numbers and quantities can be written with either letters or digits
            and may therefore need to be normalised for ease of processing. Their presentation is
            also highly language-dependent (e.g. English <mentioned>5th</mentioned> becomes Greek
              <mentioned>5.</mentioned>; English <mentioned>123,456.78</mentioned> equals French
              <mentioned>123.456,78</mentioned>). </p>
          <p>The following elements are provided for the detailed encoding of numbers and
            quantities: <specList>
              <specDesc key="num" atts="type value"/>
              <specDesc key="measure" atts="quantity unit commodity"/>
            </specList>
          </p>

          <p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><num value="33"
                >xxxiii</num><num type="cardinal" value="21">twenty-one</num><num type="percentage"
                value="10">ten percent</num><num type="percentage" value="10">10%</num><num
                type="ordinal" value="5">5th</num></egXML>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <measure quantity="40" unit="hogshead" commodity="rum">2 score hh rum</measure>
              <measure quantity="1" unit="dozen" commodity="blooms">1 doz. roses</measure>
              <measure quantity="1" unit="count" commodity="blooms">a yellow tulip</measure>
            </egXML>
          </p>
        </div>
      </div>
      <div xml:id="Simple-lists">
        <head>Lists</head>
        <p>The element <gi>list</gi> is used to mark any kind of <term>list</term>. A list is a
          sequence of text items, which may be numbered, bulleted, or arranged as a glossary list.
          Each item may be preceded by an item label (in a glossary list, this label is the term
          being defined): <specList>
            <specDesc key="list"/>
            <specDesc key="item"/>
            <specDesc key="label"/>
          </specList>
        </p>
        <p>Individual list items are tagged with <gi>item</gi>. The first <gi>item</gi> may
          optionally be preceded by a <gi>head</gi>, which gives a heading for the list. The
          numbering of items within the list may be omitted, indicated using the <att>n</att>
          attribute on each item, or (rarely) tagged as content using the <gi>label</gi> element.
          The following are all thus equivalent: <egXML xmlns="http://www.tei-c.org/ns/Examples"><list>
              <head>A short list</head>
              <item>First item in list.</item>
              <item>Second item in list.</item>
              <item>Third item in list.</item>
            </list><list>
              <head>A short list</head>
              <item n="1">First item in list.</item>
              <item n="2">Second item in list.</item>
              <item n="3">Third item in list.</item>
            </list><list>
              <head>A short list</head>
              <label>1</label>
              <item>First item in list.</item>
              <label>2</label>
              <item>Second item in list.</item>
              <label>3</label>
              <item>Third item in list.</item>
            </list></egXML> The styles should not be mixed in the same list.</p>
        <p>A simple two-column table may be treated as a <term>glossary list</term>, tagged
            <tag>list type="gloss"</tag>. Here, each item comprises a <term>term</term> and a
            <term>gloss</term>, marked with <gi>label</gi> and <gi>item</gi> respectively. These
          correspond to the elements <gi>term</gi> and <gi>gloss</gi>, which can occur anywhere in
          prose text. <egXML xmlns="http://www.tei-c.org/ns/Examples"><list type="gloss">
              <head>Vocabulary</head>
              <label xml:lang="enm">nu</label>
              <item>now</item>
              <label xml:lang="enm">lhude</label>
              <item>loudly</item>
              <label xml:lang="enm">bloweth</label>
              <item>blooms</item>
              <label xml:lang="enm">med</label>
              <item>meadow</item>
              <label xml:lang="enm">wude</label>
              <item>wood</item>
              <label xml:lang="enm">awe</label>
              <item>ewe</item>
              <label xml:lang="enm">lhouth</label>
              <item>lows</item>
              <label xml:lang="enm">sterteth</label>
              <item>bounds, frisks</item>
              <label xml:lang="enm">verteth</label>
              <item xml:lang="la">pedit</item>
              <label xml:lang="enm">murie</label>
              <item>merrily</item>
              <label xml:lang="enm">swik</label>
              <item>cease</item>
              <label xml:lang="enm">naver</label>
              <item>never</item>
            </list></egXML></p>
        <p>Where the internal structure of a list item is more complex, it may be preferable to
          regard the list as a <term>table</term>, for which special-purpose tagging is defined
          below (<ptr target="#Simple-tables"/>). </p>
        <p>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: <egXML xmlns="http://www.tei-c.org/ns/Examples"><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 — a solitaire; one banished from human
                    society.</item>
                </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></item>
            </list></egXML></p>
        <!-- <p>A list need not necessarily be displayed in list format. For example, <egXML
            xmlns="http://www.tei-c.org/ns/Examples"><p>On those remote pages it is written that
              animals are divided into <list type="runOn">
                <item n="a">those that belong to the Emperor,</item>
                <item n="b"> embalmed ones, </item>
                <item n="c"> those that are trained, </item>
                <item n="d"> suckling pigs, </item>
                <item n="e"> mermaids, </item>
                <item n="f"> fabulous ones, </item>
                <item n="g"> stray dogs, </item>
                <item n="h"> those that are included in this classification, </item>
                <item n="i"> those that tremble as if they were mad, </item>
                <item n="j"> innumerable ones, </item>
                <item n="k"> those drawn with a very fine camel's-hair brush, </item>
                <item n="l"> others, </item>
                <item n="m"> those that have just broken a flower vase, </item>
                <item n="n"> those that resemble flies from a distance.</item>
              </list></p></egXML></p>-->
        <p>Lists of bibliographic items should be tagged using the <gi>listBibl</gi> element,
          described in the next section.</p>
      </div>
      <div xml:id="Simple-bibls">
        <head>Bibliographic Citations</head>
        <p>It is often useful to distinguish bibliographic citations where they occur within texts
          being transcribed for research, if only so that they will be properly formatted when the
          text is printed out. The element <gi>bibl</gi> is provided for this purpose. Where the
          components of a bibliographic reference are to be distinguished, the following elements
          may be used as appropriate. It is generally useful to distinguish at least those parts
          (such as the titles of articles, books, and journals) which will need special formatting.
          The other elements are provided for cases where particular interest attaches to such
          details. <specList>
            <specDesc key="bibl"/>
            <specDesc key="author"/>
            <specDesc key="biblScope"/>
            <specDesc key="date"/>
            <specDesc key="editor"/>
            <specDesc key="publisher"/>
            <specDesc key="pubPlace"/>
            <specDesc key="relatedItem"/>
            <specDesc key="title"/>
          </specList></p>
        <p>Consider, for example the following editorial note: <q rend="display">He was a member of
            Parliament for Warwickshire in 1445, and died March 14, 1470 (according to Kittredge,
              <title>Harvard Studies</title> 5. 88ff).</q> This might be encoded as follows: <egXML
            xmlns="http://www.tei-c.org/ns/Examples">He was a member of Parliament for Warwickshire
            in 1445, and died March 14, 1470 (according to <bibl><author>Kittredge</author>,
                <title>Harvard Studies</title> 5. 88ff</bibl>).</egXML></p>
        <p>The bibliographic elements listed above are particularly useful in a born digital
          document which contains a bibliography encoded using the <gi>listBibl</gi> element.
          Entries in the bibliography should be given an identifier, which can then be used as the
          target of cross references from elsewhere in the document: <egXML
            xmlns="http://www.tei-c.org/ns/Examples">
            <p>Perec citing, amongst others <ref target="#MK_73">Sturm und Drang, 1973</ref>,
              concludes ... </p>
          </egXML>
        </p>
        <p> A <gi>bibl</gi> element may contain simply text, with possibly a few of its components
          distinguished by tagging, and much use of conventionalised punctuation, as in this
          example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <bibl xml:id="MK_73">Sturm, U. &amp; Drang, F. : <title>Musikalische
              Katastrophe</title>. (Berlin, W. de Gruyter, 1973)</bibl>
          </egXML> Alternatively, each of the components of the bibliographic reference may be
          clearly distinguished by tagging; in this case there is no requirement for
          conventionalised punctuation, since the processor will be able to generate this
          appropriately. <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <bibl xml:id="MK73"><author>Sturm, U.</author>
              <author>Drang, F.</author>
              <title xml:lang="de" level="m">Musikalische Katastrophe </title>
              <pubPlace>Berlin</pubPlace>
              <publisher>W. de Gruyter</publisher>
              <date>1973</date></bibl>
          </egXML>
        </p>
        <p>The element <gi>biblFull</gi> is also provided for convience in cases where bibliographic
          citations following a more sophisticated model have been used; it is permitted only in the
          TEI Header. <!--A third bibliographic element
          <gi>biblStruct</gi>, is provided only by the full TEI Guidelines. -->
          <specList>
            <specDesc key="biblFull"/>
            <!-- <specDesc key="imprint"/>
        -->
            <specDesc key="listBibl"/>
          </specList>
        </p>
        <p>The <gi>listBibl</gi> element is used to group lists of bibliographic citations. It may
          contain a series of <gi>bibl</gi><!--, <gi>biblStruct</gi>,--> or <gi>biblFull</gi>
          elements. </p>
      </div>
      <div xml:id="Simple-tables">
        <head>Tables</head>
        <p>The following elements are provided for the description of tabular matter, commonly found
          in many kinds of narrative text. Note that TEI Simple provides no sophisticated ways of
          describing the detailed layout of a table beyond its organization into rows and columns.<specList>
            <specDesc key="table"/>
            <specDesc key="row"/>
            <specDesc key="cell"/>
          </specList></p>
        <p>The <att>role</att> attribute may be used on either <gi>cell</gi> or <gi>row</gi>to
          indicate the function of a cell, or of a row of cells. Its values should be taken from the
          following list: <list type="gloss">
            <label>data</label>
            <item>data cell</item>
            <label>label</label>
            <item>label cell</item>
            <label>sum</label>
            <item>row or column sum data</item>
            <label>total</label>
            <item>table total data</item>
          </list>
          <!-- this ought to be a <specDesc key="cell" vals="role"/> of course -->
        </p>
        <p>For example, Defoe uses mortality tables like the following in the <title level="m"
            >Journal of the Plague Year</title> to show the rise and ebb of the epidemic:<egXML
            xmlns="http://www.tei-c.org/ns/Examples"><p>It was indeed coming on amain, for the
              burials that same week were in the next adjoining parishes thus:— <table rows="5"
                cols="4">
                <row role="data">
                  <cell role="label">St. Leonard's, Shoreditch</cell>
                  <cell>64</cell>
                  <cell>84</cell>
                  <cell>119</cell>
                </row>
                <row role="data">
                  <cell role="label">St. Botolph's, Bishopsgate</cell>
                  <cell>65</cell>
                  <cell>105</cell>
                  <cell>116</cell>
                </row>
                <row role="data">
                  <cell role="label">St. Giles's, Cripplegate</cell>
                  <cell>213</cell>
                  <cell>421</cell>
                  <cell>554</cell>
                </row>
              </table></p><p>This shutting up of houses was at first counted a very cruel and
              unchristian method, and the poor people so confined made bitter lamentations. ...
            </p></egXML></p>
      </div>
      <div xml:id="Simple-figs">
        <head>Figures and Graphics</head>
        <p>Not all the components of a document are necessarily textual. The most straightforward
          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. </p>
        <p>The encoder may simply record the presence of a graphic within the text, possibly with a
          brief description of its content, and may also provide a link to a digitized version of
          the graphic, using the following elements: <specList>
            <specDesc key="graphic"/>
            <specDesc key="figure"/>
            <specDesc key="figDesc"/>
          </specList></p>
        <p>Any textual information accompanying the graphic, such as a heading and/or caption, may
          be included within the <gi>figure</gi> element itself, in a <gi>head</gi> and one or more
            <gi>p</gi> elements, as also may any text appearing within the graphic itself. It is
          strongly recommended that a prose description of the image be supplied, as the content of
          a <gi>figDesc</gi> element, for the use of applications which are not able to render the
          graphic, and to render the document accessible to vision-impaired readers. (Such text is
          not normally considered part of the document proper.)</p>
        <p>The simplest use for these elements is to mark the position of a graphic and provide a
          link to it, as in this example; <egXML xmlns="http://www.tei-c.org/ns/Examples"><pb
              n="412"/><figure>
              <graphic url="images/p412fig.png"/>
            </figure><pb n="413"/></egXML> This indicates that the graphic contained by the file
            <ident>p412fig.png</ident> appears between pages 412 and 413. </p>
        <p>The <gi>graphic</gi> element can appear anywhere that textual content is permitted,
          within but not between paragraphs or headings. In the following example, the encoder has
          decided to treat a specific printer's ornament as a heading: <egXML
            xmlns="http://www.tei-c.org/ns/Examples"><head><graphic
                url="http://www.iath.virginia.edu/gants/Ornaments/Heads/hp-ral02.gif"
            /></head></egXML>
        </p>
        <p>More usually, a graphic will have at the least an identifying title, which may be encoded
          using the <gi>head</gi> element, or a number of figures may be grouped together in a
          particular structure, as in the following example: <figure>
            <graphic url="../Images/fezziPic.png"/>
            <head><title>Mr Fezziwig's Ball</title>: illustration by George Cruikshank from Dickens'
                <title>A Christmas Carol</title> (1843) </head>
          </figure> The <gi>figure</gi> element provides a means of wrapping one or more such
          elements together as a kind of graphic <soCalled>block</soCalled>. It may also include a
          brief description of the image. <egXML xmlns="http://www.tei-c.org/ns/Examples"><figure>
              <graphic url="images/fezzipic.png"/>
              <head>Mr Fezziwig's Ball</head>
              <figDesc>A Cruikshank engraving showing Mr Fezziwig leading a group of
                revellers.</figDesc>
            </figure></egXML></p>
        <p>These cases should be carefully distinguished from the case where an encoded text is
          complemented by a collection of digital images, maintained as a distinct resource. The
            <att>facs</att> attribute may be used to associate any element in an encoded text with a
          digital facsimile of it. In the simplest case, the <att>facs</att> attribute on the
            <gi>pb</gi> element may be used to supply a location for an image file corresponding
          with that point in the text: <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <text>
              <pb facs="page1.png" n="1"/>
              <!-- text contained on page 1 is encoded here -->
              <pb facs="page2.png" n="2"/>
              <!-- text contained on page 2 is encoded here -->
            </text>
          </egXML> This method is only appropriate in the simple case where each digital image file
            <ident>page1.png</ident> etc. corresponds with a single transcribed and encoded page. If
          multiple images are provided for each page, or more detailed alignment of image and
          transcription is required, for example because the image files actually represent double
          page spreads, more sophisticated mechanisms are needed, as further discussed in <ptr
            target="#Simple-fax"/> below. </p>
      </div>
      <div xml:id="Simple-anal">
        <head> Analysis</head>
        <div>
          <head>Orthographic Sentences</head>
          <p>Interpretation typically ranges across the whole of a text, with no particular respect
            to other structural units. A useful preliminary to intensive interpretation is therefore
            to segment the text into discrete and identifiable units, each of which can then bear a
            label for use as a sort of <soCalled>canonical reference</soCalled>. To facilitate such
            uses, these units may not cross each other, nor nest within each other. They may
            conveniently be represented using the following element: <specList>
              <specDesc key="s"/>
            </specList></p>
          <p>As the name suggests, the <gi>s</gi> element is most commonly used (in linguistic
            applications at least) for marking <term>orthographic sentences</term>, that is, units
            defined by orthographic features such as punctuation. For example, the passage from
              <title>Jane Eyre</title> discussed earlier might be divided into s-units as
              follows:<egXML xmlns="http://www.tei-c.org/ns/Examples"><pb n="474"/><div
                type="chapter" n="38">
                <p><s n="001">Reader, I married him.</s><s n="002">A quiet wedding we had:</s><s
                    n="003">he and I, the parson and clerk, were alone present.</s><s n="004">When
                    we got back from church, I went into the kitchen of the manor-house, where Mary
                    was cooking the dinner, and John cleaning the knives, and I said —</s></p>
                <p><q><s n="005">Mary, I have been married to Mr Rochester this morning.</s></q> ...
                </p>
              </div></egXML> Note that <gi>s</gi> elements cannot nest: the beginning of one
              <gi>s</gi> element implies that the previous one has finished. When s-units are tagged
            as shown above, it is advisable to tag the entire text end-to-end, so that every word in
            the text being analysed will be contained by exactly one <gi>s</gi> element, whose
            identifier can then be used to specify a unique reference for it. If the identifiers
            used are unique within the document, then the <att>xml:id</att> attribute might be used
            in preference to the <att>n</att> attribute used in the above example.</p>
        </div>
        <div>
          <head>Words and punctuation</head>
          <p>Tokenization, that is, the identification of lexical or non-lexical tokens within a
            text, is a very common requirement for all kinds of textual analysis, and not an
            entirely trivial one. The decision as to whether, for example, <q>can't</q> in English
            or <q>du</q> in French should be treated as one word or two is not simple. Consequently
            it is often useful to make explicit the preferred tokenization in a marked up text. The
            following elements are available for this purpose: <specList>
              <specDesc key="w"/>
              <specDesc key="c"/>

              <specDesc key="pc"/>
            </specList></p>
          <p>For example, the output from a part of speech tagger might be recorded in TEI Simple as
            follows: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <s n="1">
                <w ana="#NP0">Marley</w>
                <w ana="#VBD">was</w>
                <w ana="#AJ0">dead</w><pc>:</pc>
                <w ana="#TO0">to</w>
                <w ana="#VBB">begin</w>
                <w ana="#PRP">with</w>
                <pc ana="#SENT">.</pc>
              </s></egXML>
          </p>
          <p>In this example, each token in the input has been decorated with an automatically
            generated part of speech code, using the <att>ana</att> attribute discussed in section
              <ptr target="#xatts"/> above. The system has also distinguished between tokens to be
            treated as words (tagged <gi>w</gi>) and tokens considered to be punctuation (tagged
              <gi>pc</gi>). It may also sometimes be useful to distinguish tokens which consist of a
            single letter or character: the <gi>c</gi> element is provided for this purpose.
            <!-- some crazy people mark up interword space with a c: shd that be mentioned? -->
          </p>
          <p>The <gi>w</gi> also provides for each word to be associated with a root form or lemma,
            either explicitly using the <att>lemma</att> attribute, or by reference, using the
              <att>lemmaRef</att> attribute, as in this example: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">...<w ana="#VBD" lemma="be"
                lemmaRef="http://www.myLexicon.com/be">was</w> ... </egXML>
          </p>
        </div>
        <div>
          <head>General-Purpose Interpretation Elements</head>
          <p>The <gi>w</gi> element is a specialisation of the <gi>seg</gi> element which has
            already been introduced for use in identifying otherwise unmarked targets of cross
            references and hypertext links (see section <ptr target="#Simple-ptrs"/>); it can be
            used to distinguish any portion of text to which the encoder wishes to assign a
            user-specified <att>type</att> or a unique identifier; it may thus be used to tag
            textual features for which there is no other provision in the published TEI
            Guidelines.</p>
          <p>For example, the Guidelines provide no <soCalled>apostrophe</soCalled> element to mark
            parts of a literary text in which the narrator addresses the reader (or hearer)
            directly. One approach might be to regard these as instances of the <gi>q</gi> element,
            distinguished from others by an appropriate value for the <att>who</att> attribute. A
            possibly simpler, and certainly more general, solution would however be to use the
              <gi>seg</gi> element as follows: <egXML xmlns="http://www.tei-c.org/ns/Examples"><div
                type="chapter" n="38">
                <p><seg type="apostrophe">Reader, I married him.</seg> A quiet wedding we had:
                  ...</p>
              </div></egXML> The <att>type</att> attribute on the <gi>seg</gi> element can take any
            value, and so can be used to distinguish phrase-level phenomena of any kind; it is good
            practice to record the values used and their significance in the header or in the
            documentation of the encoding system. <!-- mention ODD! --></p>


        </div>
      </div>
      <div>
        <head>Common attributes</head>
        <p>Some attributes are available on many elements, though not on all. These attributes are
          defined using a TEI attribute class, a concept which is discussed further in the TEI
          Guidelines. We list here some attribute classes which have been adapted or customized for
          use in TEI Simple. </p>
        <p>The elements <gi>add</gi>, <gi>figure</gi>, <gi>fw</gi>, <gi>label</gi>, <gi>note</gi>
          and <gi>stage</gi> all take the attribute <att>place</att> to indicate whereabouts on the
          page they appear. In TEI Simple the possible values for this attribute are limited as
          indicated below: <specList>
            <specDesc key="att.placement" atts="place"/>
            <!-- stylesheets currently dont allow me to display valList here -->
          </specList>
          <list type="gloss">
            <label>above</label>
            <item>above the line</item>
            <label>below</label>
            <item>below the line</item>
            <label>top</label>
            <item>at the top of the page</item>
            <label>top-right</label>
            <item>at the top right of the page</item>
            <label>top-left</label>
            <item>at the top left of the page</item>
            <label>top-centre</label>
            <item>at the top center of the page</item>
            <label>bottom-right</label>
            <item>at the bottom right of the page</item>
            <label>bottom-left</label>
            <item>at the bottom left of the page</item>
            <label>bottom-centre</label>
            <item>at the bottom centre of the page</item>
            <label>bottom</label>
            <item>at the foot of the page</item>
            <label>tablebottom</label>
            <item>underneath a table</item>
            <label>margin-right</label>
            <item>in the right-hand margin</item>
            <label>margin</label>
            <item>in the outer margin</item>
            <label>margin-inner</label>
            <item>in the inner margin</item>
            <label>margin-left</label>
            <item>in the left-hand margin</item>
            <label>opposite</label>
            <item>on the opposite, i.e. facing, page.</item>
            <label>overleaf</label>
            <item>on the other side of the leaf.</item>
            <label>overstrike</label>
            <item>superimposed on top of the current context</item>
            <label>end</label>
            <item>at the end of the volume.</item>
            <label>divend</label>
            <item>at the end the current division.</item>
            <label>parend</label>
            <item>at the end the current paragraph.</item>
            <label>inline</label>
            <item>within the body of the text.</item>
            <label>inspace</label>
            <item>in a predefined space, for example left by an earlier scribe.</item>
            <label>block</label>
            <item>formatted as an indented paragraph</item>
          </list>
        </p>
        <p>The elements <gi>add</gi>, <gi>am</gi>, <gi>corr</gi>, <gi>date</gi>, <gi>del</gi>,
            <gi>ex</gi>, <gi>expan</gi>, <gi>gap</gi>, <gi>name</gi>, <gi>reg</gi>, <gi>space</gi>,
            <gi>subst</gi>, <gi>supplied</gi>, <gi>time</gi> and <gi>unclear</gi> all use the
          attribute <att>unit</att> to indicate the units in which the size of the feature concerned
          is expressed. In TEI simple the possible values for this attribute are limited as
          indicated below: <specList>
            <specDesc key="att.dimensions" atts="unit"/>
            <!-- stylesheets currently dont allow me to display valList here -->
          </specList>
          <list type="gloss">
            <label>chars</label>
            <item>characters</item>
            <label>lines</label>
            <item>lines</item>
            <label>pages</label>
            <item>pages</item>
            <label>words</label>
            <item>words</item>
            <label>cm</label>
            <item>centimetres</item>
            <label>mm</label>
            <item>millimetre</item>
            <label>in</label>
            <item>inches</item>
          </list></p>
        <p>Very many TEI elements take the value <att>type</att> (see the specification for
            <ident>att.typed</ident> for a full list). In most cases, no constraint is placed on the
          possible values for this attribute. In the case of the element <gi>name</gi> however, the
          possible values for this attribute are limited as indicated below: <specList>
            <specDesc key="name" atts="type"/>
            <!-- stylesheets currently dont allow me to display valList here -->
          </specList>
          <list type="gloss">
            <label>person</label>
            <item/>
            <label>forename</label>
            <item/>
            <label>surname</label>
            <item/>
            <label>personGenName</label>
            <item/>
            <label>personRoleName</label>
            <item/>
            <label>personAddName</label>
            <item/>
            <label>nameLink</label>
            <item/>
            <label>org</label>
            <item/>
            <label>country</label>
            <item/>
            <label>placeGeog</label>
            <item/>
            <label>place</label>
            <item/>
          </list></p>
      </div>

      <div xml:id="Simple-composite">
        <head>Composite and floating texts</head>
        <p>A composite text, like a simple text, has an optional front and back. In between however,
          instead of a single body, it contains one or more discrete texts, each with its own
          optional front and back matter. The following elements are provided to handle composite
          texts of various kinds. <specList>
            <specDesc key="group"/>
            <specDesc key="floatingText"/>
            <specDesc key="teiCorpus"/>

          </specList>
        </p>
        <p> A typical example might be an anthology containing several distinct works, or any other
          kind of collection, encoded using an overall structure like this: <egXML
            xmlns="http://www.tei-c.org/ns/Examples"><TEI>
              <teiHeader>
                <!--[ header information for the composite ]-->
              </teiHeader>
              <text>
                <front>
                  <!--[ front matter for the composite  ]-->
                </front>
                <group>
                  <text>
                    <front>
                      <!--[ front matter of first text ]-->
                    </front>
                    <body>
                      <!--[ body of first text  ]-->
                    </body>
                    <back>
                      <!--[ back matter of first text ]-->
                    </back>
                  </text>
                  <text>
                    <front>
                      <!--[ front matter of second text]-->
                    </front>
                    <body>
                      <!--[ body of second text  ]-->
                    </body>
                    <back>
                      <!--[ back matter of second text ]-->
                    </back>
                  </text>
                  <!--[ more texts or groups of texts here ]-->
                </group>
                <back>
                  <!--[ back matter for the composite  ]-->
                </back>
              </text>
            </TEI></egXML></p>
        <p>A different kind of composite text occurs when one text is embedded within another, as
          for example in the <title>Arabian Nights</title> or similar collections of stories, or in
          other cases where one narrative is interrupted by another. The element
            <gi>floatingText</gi> may be preferred to encode such materials as the following: <egXML
            xmlns="http://www.tei-c.org/ns/Examples">
            <p>The Gentleman having finish'd his Story, Galecia waited on him to the Stairs-head;
              and at her return, casting her Eyes on the Table, she saw lying there an old dirty
              rumpled Book, and found in it the following story: </p>
            <floatingText>
              <body>
                <p> IN the time of the Holy War when Christians from all parts went into the Holy
                  Land to oppose the Turks; Amongst these there was a certain English Knight...</p>
                <!-- rest of story here -->
                <p>The King graciously pardoned the Knight; Richard was kindly receiv'd into his
                  Convent, and all things went on in good order: But from hence came the Proverb, We
                  must not strike <hi>Robert</hi> for <hi>Richard.</hi>
                </p>
              </body>
            </floatingText>
            <pb n="43"/>
            <p>By this time Galecia's Maid brought up her Supper; after which she cast her Eyes
              again on the foresaid little Book, where she found the following Story ....</p>
          </egXML>
        </p>
        <p>Note that there is only a single TEI Header for composite texts of either kind, since the
          assumption is that the composite is at some level describable as a single work. However,
          it is also possible to define a composite of complete TEI texts, each with its own header.
          Such a collection is known as a <term>TEI corpus</term>, and must itself have a header:
            <egXML xmlns="http://www.tei-c.org/ns/Examples"><teiCorpus><teiHeader>
                <!--[header information for the corpus]--></teiHeader><TEI>
                <teiHeader><!--[header information for first text]--></teiHeader>
                <text>
                  <!--[first text in corpus]-->
                </text>
              </TEI><TEI>
                <teiHeader><!--[header information for second text]--></teiHeader>
                <text>
                  <!--[second text in corpus]-->
                </text>
              </TEI></teiCorpus></egXML> It is also possible to create a composite of corpora --
          that is, one <gi>teiCorpus</gi> element may contain many nested <gi>teiCorpus</gi>
          elements rather than many nested <gi>TEI</gi> elements, to any depth considered
          necessary.</p>
      </div>

      <div xml:id="Simple-fronbac">
        <head>Front and Back Matter</head>
        <div>
          <head>Front Matter</head>
          <p>For many purposes, particularly in older texts, the preliminary material such as title
            pages, prefatory epistles, etc., may provide very useful additional linguistic or social
            information.The TEI Guidelines provide a set of recommendations for distinguishing the
            textual elements most commonly encountered in front matter, which are summarized
            here.</p>
          <div xml:id="h51">
            <head>Title Page</head>
            <p>The start of a title page should be marked with the element <gi>titlePage</gi>. All
              text contained on the page should be transcribed and tagged with the appropriate
              element from the following list: <specList>
                <specDesc key="titlePage"/>
                <specDesc key="docTitle"/>
                <specDesc key="titlePart"/>
                <specDesc key="byline"/>
                <specDesc key="docAuthor"/>
                <specDesc key="docDate"/>
                <specDesc key="docEdition"/>
                <specDesc key="docImprint"/>
                <specDesc key="epigraph"/>
              </specList></p>
            <p>Typeface distinctions should be marked with the <att>rendition </att> attribute when
              necessary, as described above though a very detailed description of the letter spacing
              and sizing used in ornamental titles is not easily done. Changes of language should be
              marked by appropriate use of the <att>xml:lang</att> attribute or the <gi>foreign</gi>
              element, as necessary. Names of people, places, or organizations, may be tagged using
              the <gi>name</gi> element wherever they appear if no other more specific element is
              available.</p>
            <p>Two example title pages follow: <egXML xmlns="http://www.tei-c.org/ns/Examples"><titlePage>
                  <docTitle>
                    <titlePart type="main"> PARADISE REGAIN'D. A POEM In IV <hi>BOOKS</hi>. </titlePart>
                    <titlePart> To which is added <title>SAMSON AGONISTES</title>. </titlePart>
                  </docTitle>
                  <byline>The Author <docAuthor>JOHN MILTON</docAuthor></byline>
                  <docImprint><name>LONDON</name>, Printed by <name>J.M.</name> for <name>John
                      Starkey</name> at the <name>Mitre</name> in <name>Fleetstreet</name>, near
                      <name>Temple-Bar.</name></docImprint>
                  <docDate>MDCLXXI</docDate>
                </titlePage></egXML><egXML xmlns="http://www.tei-c.org/ns/Examples"><titlePage>
                  <docTitle>
                    <titlePart type="main"> Lives of the Queens of England, from the Norman
                      Conquest;</titlePart>
                    <titlePart type="sub">with anecdotes of their courts. </titlePart>
                  </docTitle>
                  <titlePart>Now first published from Official Records and other authentic documents
                    private as well as public.</titlePart>
                  <docEdition>New edition, with corrections and additions</docEdition>
                  <byline>By <docAuthor>Agnes Strickland</docAuthor></byline>
                  <epigraph>
                    <q>The treasures of antiquity laid up in old historic rolls, I opened.</q>
                    <bibl>BEAUMONT</bibl>
                  </epigraph>
                  <docImprint>Philadelphia: Blanchard and Lea</docImprint>
                  <docDate>1860.</docDate>
                </titlePage></egXML></p>
            <p>As elsewhere, the <att>ref</att> attribute may be used to link a name with a
              canonical definition of the entity being named. For example: <egXML
                xmlns="http://www.tei-c.org/ns/Examples">
                <byline>By <docAuthor><name ref="http://en.wikipedia.org/wiki/Agnes_Strickland"
                      >Agnes Strickland</name></docAuthor></byline>
              </egXML></p>
          </div>
          <div xml:id="h52">
            <head>Prefatory Matter</head>
            <p>Major blocks of text within the front matter should be marked using <gi>div</gi>
              elements; the following suggested values for the <att>type</att> attribute may be used
              to distinguish various common types of prefatory matter: <list type="gloss">
                <label>preface</label>
                <item>A foreword or preface addressed to the reader in which the author or publisher
                  explains the content, purpose, or origin of the text</item>
                <label>dedication</label>
                <item>A formal offering or dedication of a text to one or more persons or
                  institutions by the author.</item>
                <label>abstract</label>
                <item>A summary of the content of a text as continuous prose</item>
                <label>ack</label>
                <item>A formal declaration of acknowledgment by the author in which persons and
                  institutions are thanked for their part in the creation of a text</item>
                <label>contents</label>
                <item>A table of contents, specifying the structure of a work and listing its
                  constituents. The <gi>list</gi> element should be used to mark its
                  structure.</item>
                <label>frontispiece</label>
                <item>A pictorial frontispiece, possibly including some text.</item>
              </list></p>
            <p>Where other kinds of prefatory matter are encountered, the encoder is at liberty to
              invent other values for the <att>type</att> attribute.</p>
          </div>
          <div xml:id="h52x">
            <head>Liminal elements</head>
            <p>All text divisions, whether in front matter or elsewhere, may begin and end with one
              or more components which we term <term>liminal elements</term>, because they begin or
              end the division. A typical example is a heading or title of some kind which should be
              tagged using the <gi>head</gi> element; but there are many other possibilities: <specList>
                <specDesc key="salute"/>
                <specDesc key="signed"/>
                <specDesc key="byline"/>
                <specDesc key="dateline"/>
                <specDesc key="argument"/>
                <specDesc key="cit"/>
                <specDesc key="imprimatur"/>
                <specDesc key="opener"/>
                <specDesc key="closer"/>
                <specDesc key="postscript"/>
              </specList></p>

            <p>As an example, the beginning and end of the dedication to Milton's
                <title>Comus</title> might be marked up as follows: <egXML
                xmlns="http://www.tei-c.org/ns/Examples">
                <div type="dedication">
                  <head>To the Right Honourable <name>JOHN Lord Viscount BRACLY</name>, Son and Heir
                    apparent to the Earl of Bridgewater, &amp;c.</head>
                  <salute>MY LORD,</salute>
                  <p>THis <hi>Poem</hi>, which receiv'd its first occasion of Birth from your Self,
                    and others of your Noble Family .... and as in this representation your
                    attendant <name>Thyrsis</name>, so now in all reall expression</p>
                  <closer>
                    <salute>Your faithfull, and most humble servant</salute>
                    <signed>
                      <name>H. LAWES.</name>
                    </signed>
                  </closer>
                </div></egXML></p>
          </div>

        </div>
        <div>
          <head>Back Matter</head>
          <div>
            <head>Structural Divisions of Back Matter</head>
            <p>Because of variations in publishing practice, back matter can contain virtually any
              of the elements listed above for front matter, and the same elements should be used
              where this is so. Additionally, back matter may contain the following types of matter
              within the <gi>back</gi> element. Like the structural divisions of the body, these
              should be marked as <gi>div</gi> elements, and distinguished by the following
              suggested values of the <att>type</att> attribute: <list type="gloss">
                <label>appendix</label>
                <item>An ancillary self-contained section of a work, often providing additional but
                  in some sense extra-canonical text.</item>
                <label>glossary</label>
                <item>A list of terms associated with definition texts (‘glosses’): this should be
                  encoded as a <tag>list type="gloss"</tag> element</item>
                <label>notes</label>
                <item>A section in which textual or other kinds of notes are gathered
                  together.</item>
                <label>bibliogr</label>
                <item>A list of bibliographic citations: this should be encoded as a
                    <gi>listBibl</gi>
                </item>
                <label>index</label>
                <item>Any form of pre-existing index to the work (An index may also be generated for
                  a document by using the <gi>index</gi> element described above).</item>
                <label>colophon</label>
                <item>A statement appearing at the end of a book describing the conditions of its
                  physical production.</item>
              </list></p>
          </div>
          <div xml:id="specfronbac">
            <head>Specialised Front and Back Matter</head>
            <p>TEI Simple also provides elements for some additional components of front or back
              matter which are characteristic of particular kinds of text, in particular old play
              texts. These often include lists of dramatis personae and notes about the setting of a
              play, for which the following elements are provided: <specList>
                <specDesc key="castList"/>
                <specDesc key="castItem"/>
                <specDesc key="castGroup"/>
                <specDesc key="role"/>
                <specDesc key="roleDesc"/>
                <specDesc key="actor"/>
                <specDesc key="set"/>

              </specList></p>
            <p>Note that these elements are intended for use in marking up cast lists and setting
              notes as they appear in a source document. They are not intended for use when marking
              up definitive lists of the different roles identified in a play, except in so far as
              that may have been their original purpose.</p>
            <p>The following example shows one way of encoding the last part of Shakespeare's
                <title>Tempest</title>, as printed in the first folio: </p>
            <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <back>
                <div type="epilogue">
                  <head>Epilogue, spoken by Prospero.</head>
                  <sp>
                    <l>Now my Charmes are all ore-throwne,</l>
                    <l>And what strength I have's mine owne</l>
                    <l>As you from crimes would pardon'd be,</l>
                    <l>Let your Indulgence set me free.</l>
                  </sp>
                  <stage>Exit</stage>
                </div>
                <set>
                  <p>The Scene, an un-inhabited Island.</p>
                </set>
                <castList>
                  <head>Names of the Actors.</head>
                  <castItem>Alonso, K. of Naples</castItem>
                  <castItem>Sebastian, his Brother.</castItem>
                  <castItem>Prospero, the right Duke of Millaine.</castItem>
                  <!-- etc -->
                </castList>
                <trailer>FINIS</trailer>
              </back>
            </egXML>
            <!--   <p>The full Guidelines also provide ways of encoding information about particular
                performances of a play (using the <gi>performance</gi> element) and full details of
                the roles, or actors involved but these are not included in TEI Simple.</p>-->
          </div>
        </div>
      </div>
      <div xml:id="Simple-fax">
        <head>Encoding a digital facsimile </head>
        <p>The following elements may be used to encode a text represented by a collection of
          digital images, either alone or in conjunction with a textual transcription. <specList>
            <specDesc key="facsimile"/>
            <!--  <specDesc key="surfaceGrp"/>
         -->
            <specDesc key="surface"/>
            <specDesc key="zone"/>
            <!--<specDesc key="line"/>-->
          </specList>
        </p>
        <p>As mentioned in section <ptr target="#Simple-figs"/> above, a TEI Simple document may
          reference a set of page images, alone, or in combination with a transcription. For ease of
          management, it is strongly recommended that the <gi>graphic</gi> elements representing
          those page images be grouped together within a <gi>facsimile</gi> element, as in the
          following example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><facsimile><graphic
                url="page1.png" xml:id="page1"/>
              <graphic url="page2.png" xml:id="page2"/></facsimile></egXML> If a transcription is
          supplied in addition, the <att>xml:id</att> values can be used to align the page breaks
          within it with the relevant image, rather than using the URL given on the <gi>graphic</gi>
          element. <egXML xmlns="http://www.tei-c.org/ns/Examples"><text>
              <!-- ...-->
              <pb facs="#page1"/>
              <!-- text contained on page 1 -->
              <pb facs="#page2"/>
              <!-- text contained on page 2 -->
              <!-- ...-->
            </text>
          </egXML>
        </p>
        <p>The <gi>surface</gi> element is useful in two situations: when it is desired to group
          different images of the same page, for example of different resolutions; and when it is
          desired to align parts of a page image with parts of a transcription. The <gi>zone</gi>
          element is used to define (and hence provide an identifier for) the location of a part of
          an image with reference to the surface on which it appears. </p>
        <p>In this example, a thumbnail and a high resolution image are associated with the same
          surface: <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <facsimile>
              <surface>
                <graphic xml:id="page1T" url="thumbs/page1.png"/>
                <graphic xml:id="page1" url="page1.png"/>
              </surface>
            </facsimile></egXML></p>
        <p>In this example, the <gi>head</gi> element in the transcription is aligned with the top
          half of a square image: <egXML xmlns="http://www.tei-c.org/ns/Examples">
            <facsimile>
              <surface ulx="1" uly="1" lrx="4" lry="4">
                <graphic url="page1.png" xml:id="page1"/>
                <zone xml:id="topHalfP1" ulx="1" uly="1" lrx="2" lry="4"/>
              </surface>
            </facsimile>
            <text>
              <!-- ... -->
              <pb facs="#page1"/>
              <head facs="#topHalfP1">Text of Heading</head>
              <!-- ...-->
            </text>
          </egXML>
        </p>
        <p>A more detailed explanation of the use of these attributes and other associated elements
          is given in the full Guidelines. </p>
      </div>
      <div xml:id="Simple-header">
        <head>The Electronic Title Page</head>
        <p>Every TEI text has a header which provides information analogous to that provided by the
          title page of printed text. The header is introduced by the element <gi>teiHeader</gi> and
          has four major parts: <specList>
            <specDesc key="fileDesc"/>
            <specDesc key="encodingDesc"/>
            <specDesc key="profileDesc"/>
            <specDesc key="revisionDesc"/>
          </specList></p>
        <p> A corpus or collection of texts with many shared characteristics may have one header for
          the corpus and individual headers for each component of the corpus. In this case the
            <att>type</att> attribute indicates the type of header. <tag>teiHeader
            type="corpus"</tag> introduces the header for corpus-level information.</p>
        <p>Some of the header elements contain running prose which consists of one or more
            <gi>p</gi>s. Others are grouped: <list>
            <item>Elements whose names end in <mentioned>Stmt</mentioned> (for statement) usually
              enclose a group of elements recording some structured information.</item>
            <item>Elements whose names end in <mentioned>Decl</mentioned> (for declaration) enclose
              information about specific encoding practices.</item>
            <item>Elements whose names end in <mentioned>Desc</mentioned> (for description) contain
              a prose description.</item>
          </list></p>
        <div>
          <head>The File Description</head>
          <p>The <gi>fileDesc</gi> element is mandatory. It contains a full bibliographic
            description of the file with the following elements: <specList>
              <specDesc key="titleStmt"/>
              <specDesc key="editionStmt"/>
              <specDesc key="extent"/>
              <specDesc key="publicationStmt"/>
              <specDesc key="seriesStmt"/>
              <specDesc key="notesStmt"/>
              <specDesc key="sourceDesc"/>
            </specList></p>
          <p> A minimal header has the following structure: <egXML
              xmlns="http://www.tei-c.org/ns/Examples"><teiHeader>
                <fileDesc>
                  <titleStmt>
                    <!-- bibliographic description of the digital resource -->
                  </titleStmt>
                  <publicationStmt>
                    <!-- information about how the resource is distributed -->
                  </publicationStmt>
                  <sourceDesc>
                    <!-- information about the sources from which the digital resource is derived -->
                  </sourceDesc>
                </fileDesc>
              </teiHeader></egXML></p>
          <div>
            <head>The Title Statement</head>
            <p>The following elements can be used in the <gi>titleStmt</gi>: <specList>
                <specDesc key="title"/>
                <specDesc key="author"/>
                <specDesc key="sponsor"/>
                <specDesc key="funder"/>
                <specDesc key="principal"/>
                <specDesc key="respStmt"/>
              </specList></p>
            <p> The title of a digital resource derived from a non-digital original may be similar
              to that of its source but should be distinct from it, for example: <eg>[title of
                source]: a machine readable transcription</eg> or <eg> [title of source]: TEI XML
                edition</eg> or <eg> A machine readable version of: [title of source]</eg>
            </p>
            <p>Several specialised elements may be used to indicate specific responsibilities for
              the content of the work, such as <gi>author</gi>, <gi>editor</gi>, <gi>principal</gi>,
                <gi>funder</gi>, etc. The generic <gi>respStmt</gi> element is provided for other
              statements of responsibility. It contains the following subcomponents: <specList>
                <specDesc key="resp"/>
                <specDesc key="name"/>
              </specList> Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><titleStmt>
                  <title>Two stories by Edgar Allen Poe encoded using TEI Simple </title>
                  <author>Poe, Edgar Allen (1809-1849)</author>
                  <respStmt>
                    <resp>compiled by</resp>
                    <name>James D. Benson</name>
                  </respStmt>
                </titleStmt></egXML></p>
          </div>
          <div>
            <head>The Edition Statement</head>
            <p>The <gi>editionStmt</gi> groups information relating to one edition of the digital
              resource (where <mentioned>edition</mentioned> is used as elsewhere in bibliography),
              and may include the following elements: <specList>
                <specDesc key="edition"/>
                <specDesc key="respStmt"/>
              </specList></p>
            <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><editionStmt><edition n="U2"
                    >Third draft, substantially revised <date>1987</date>
                  </edition></editionStmt></egXML></p>
            <p>Determining exactly what constitutes a new edition of an electronic text is left to
              the encoder.</p>
          </div>
          <div>
            <head>The Extent Statement</head>
            <p>The <gi>extent</gi> statement describes the approximate size of the digital
              resource.</p>
            <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><extent>15 Mb
                </extent></egXML></p>
          </div>
          <div>
            <head>The Publication Statement</head>
            <p>The <gi>publicationStmt</gi> is mandatory. It may contain a simple prose description
              or groups of the elements described below: <specList>
                <specDesc key="publisher"/>
                <specDesc key="distributor"/>
                <specDesc key="authority"/>
              </specList></p>
            <p>At least one of these three elements must be present, unless the entire publication
              statement is in prose. The following elements may occur within them: <specList>
                <specDesc key="pubPlace"/>
                <specDesc key="address"/>
                <specDesc key="addrLine"/>
                <specDesc key="idno"/>
                <specDesc key="availability"/>
                <specDesc key="licence"/>
                <specDesc key="date"/>
              </specList></p>
            <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><publicationStmt>
                  <publisher>University of Victoria Humanities Computing and Media
                    Centre</publisher>
                  <pubPlace>Victoria, BC</pubPlace>
                  <date>2011</date>
                  <availability status="restricted">
                    <licence target="http://creativecommons.org/licenses/by-sa/3.0/"> Distributed
                      under a Creative Commons Attribution-ShareAlike 3.0 Unported License
                    </licence>
                  </availability>
                </publicationStmt></egXML></p>
          </div>
          <div>
            <head>Series and Notes Statements</head>
            <p>The <gi>seriesStmt</gi> element groups information about the series, if any, to which
              a publication belongs. It may contain <gi>title</gi>, <gi>idno</gi>, or
                <gi>respStmt</gi> elements.</p>
            <p>The <gi>notesStmt</gi>, if used, contains one or more <gi>note</gi> elements which
              contain a note or annotation. Some information found in the notes area in conventional
              bibliography has been assigned specific elements in the TEI scheme.</p>
          </div>
          <div>
            <head>The Source Description</head>
            <p>The <gi>sourceDesc</gi> is a mandatory element which records details of the source or
              sources from which the computer file is derived. It may contain simple prose or a
              bibliographic citation, using one or more of the following elements: <specList>
                <specDesc key="bibl"/>
                <specDesc key="listBibl"/>
              </specList></p>
            <p>Examples: <egXML xmlns="http://www.tei-c.org/ns/Examples"><sourceDesc>
                  <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton
                    Facsimile, 1968)</bibl>
                </sourceDesc></egXML>
              <egXML xmlns="http://www.tei-c.org/ns/Examples"><sourceDesc>
                  <bibl>
                    <author>CNN Network News</author>
                    <title>News headlines</title>
                    <date>12 Jun 1989</date>
                  </bibl>
                </sourceDesc></egXML></p>
          </div>
        </div>
        <div>
          <head>The Encoding Description</head>
          <p>The <gi>encodingDesc</gi> element specifies the methods and editorial principles which
            governed the transcription of the text. Its use is highly recommended. It may be prose
            description or may contain more specialised elements chosen from the following list: <specList>
              <specDesc key="projectDesc"/>
              <specDesc key="samplingDecl"/>
              <specDesc key="editorialDecl"/>
              <specDesc key="tagsDecl"/>
              <specDesc key="refsDecl"/>
              <specDesc key="listPrefixDef"/>
              <specDesc key="prefixDef"/>
              <specDesc key="classDecl"/>
            </specList></p>
          <div>
            <head>Project and Sampling Descriptions</head>
            <p>Examples of <gi>projectDesc</gi> and <gi>samplingDesc</gi>: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><encodingDesc>
                  <projectDesc>
                    <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990. </p>
                  </projectDesc>
                </encodingDesc></egXML>
              <egXML xmlns="http://www.tei-c.org/ns/Examples"><encodingDesc>
                  <samplingDecl>
                    <p>Samples of 2000 words taken from the beginning of the text</p>
                  </samplingDecl>
                </encodingDesc></egXML></p>
          </div>
          <div>
            <head>Editorial Declarations</head>
            <p>The <gi>editorialDecl</gi> contains a prose description of the practices used when
              encoding the text. Typically this description should cover such topics as the
              following, each of which may conveniently be given as a separate paragraph. <list
                type="gloss">
                <label>correction </label>
                <item>how and under what circumstances corrections have been made in the
                  text.</item>
                <label>normalization</label>
                <item>the extent to which the original source has been regularized or
                  normalized.</item>
                <label>quotation</label>
                <item>what has been done with quotation marks in the original -- have they been
                  retained or replaced by entity references, are opening and closing quotes
                  distinguished, etc. </item>
                <label>hyphenation</label>
                <item>what has been done with hyphens (especially end-of-line hyphens) in the
                  original -- have they been retained, replaced by entity references, etc.</item>
                <label>segmentation</label>
                <item>how has the text has been segmented, for example into sentences, tone-units,
                  graphemic strata, etc.</item>
                <label>interpretation</label>
                <item>what analytic or interpretive information has been added to the text. </item>
              </list></p>
            <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><editorialDecl><p>The part
                    of speech analysis applied throughout section 4 was added by hand and has not
                    been checked.</p><p>Errors in transcription controlled by using the WordPerfect
                    spelling checker.</p><p>All words converted to Modern American spelling using
                    Webster's 9th Collegiate dictionary.</p></editorialDecl></egXML></p>
            <p>The full TEI Guidelines provide specialised elements for each of the topics above;
              these are not however included in TEI Simple.</p>
          </div>
          <div xml:id="hdr-rend">
            <head>Tagging Declaration</head>
            <p>When it does not consist simply of a prose description, the <gi>tagsDecl</gi> element
              may contain a number of more specialised elements providing additional information
              about how the document concerned has been marked up. The following elements may be
              used <specList>
                <specDesc key="rendition"/>
                <specDesc key="namespace"/>
                <specDesc key="tagUsage"/>
              </specList>
            </p>
            <p>Here is a simple example, showing how these elements may be used. It indicates the
              number of times the elements <gi>hi</gi> and <gi>title</gi> from the TEI name space
              have been used in the document. It also documents how the way that the source document
              was originally printed has been represented using TEI tagging: <egXML
                xmlns="http://www.tei-c.org/ns/Examples">
                <tagsDecl partial="true">
                  <rendition xml:id="rend-bo">font-weight:bold</rendition>
                  <rendition xml:id="rend-it" selector="hi, title">font-style:italic</rendition>
                  <namespace name="http://www.tei-c.org/ns/1.0">
                    <tagUsage gi="hi" occurs="467"/>
                    <tagUsage gi="title" occurs="45"/>
                  </namespace>
                </tagsDecl>
              </egXML>
            </p>
            <p>The <gi>rendition</gi> elements here contain fragments expressed in the W3C standard
              Cascading Stylesheets language (CSS). Their function here is to associate the
              particular styles concerned with an identifier (for example <ident>rend-bo</ident>)
              which can then be pointed to from elsewhere within the document by means of the
                <att>rendition</att> attribute mentioned in section <ptr target="#faces"/> above. To
              indicate, for example, that a particular name in the document was rendered in a bold
              font it might be tagged <tag>name rendition="#rend-bo"</tag>. The <att>selector</att>
              attribute used in the preceding example is used to indicate once for all a default
              rendition value to be associated with several elements: in this example, unless
              otherwise indicated, it is assumed that the content of each <gi>hi</gi> and each
                <gi>title</gi> element was originally rendered using an italic font. </p>
            <p>For TEI Simple, a large set of such rendition definitions has been predefined. The
              encoder is not therefore required to supply any detailed declarations, but can refer
              to the predefined list using the following list: <list type="gloss">
                <label>simple:allcaps</label>
                <item>all capitals</item>
                <label>simple:blackletter</label>
                <item>black letter or gothic typeface</item>
                <label>simple:bold</label>
                <item>bold typeface</item>
                <label>simple:bottombraced</label>
                <item>marked with a brace under the bottom of the text</item>
                <label>simple:boxed</label>
                <item>border around the text</item>
                <label>simple:centre</label>
                <item>centred</item>
                <label>simple:cursive</label>
                <item>cursive typeface</item>
                <label>simple:display</label>
                <item>block display</item>
                <label>simple:doublestrikethrough</label>
                <item>strikethrough with double line</item>
                <label>simple:doubleunderline</label>
                <item>underlined with double line</item>
                <label>simple:dropcap</label>
                <item>initial letter larger or decorated</item>
                <label>simple:float</label>
                <item>floated out of main flow</item>
                <label>simple:hyphen</label>
                <item>with a hyphen here (eg in line break)</item>
                <label>simple:inline</label>
                <item>inline rendering</item>
                <label>simple:justify</label>
                <item>justified text</item>
                <label>simple:italic</label>
                <item>italic typeface</item>
                <label>simple:larger</label>
                <item>larger type</item>
                <label>simple:left</label>
                <item>aligned to the left or left-justified</item>
                <label>simple:leftbraced</label>
                <item>marked with a brace on the left side of the text</item>
                <label>simple:letterspace</label>
                <item>larger-than-normal spacing between letters, usually for emphasis</item>
                <label>simple:literal</label>
                <item>fixed-width typeface, spacing preserved</item>
                <label>simple:normalstyle</label>
                <item>upright shape and default weight of typeface</item>
                <label>simple:normalweight</label>
                <item>normal typeface weight</item>
                <label>simple:right</label>
                <item>aligned to the right or right-justified</item>
                <label>simple:rightbraced</label>
                <item>marked with a brace to the right of the text</item>
                <label>simple:rotateleft</label>
                <item>rotated to the left</item>
                <label>simple:rotateright</label>
                <item>rotated to the right</item>
                <label>simple:smallcaps</label>
                <item>small caps</item>
                <label>simple:smaller</label>
                <item>smaller type</item>
                <label>simple:strikethrough</label>
                <item>strike through</item>
                <label>simple:subscript</label>
                <item>subscript</item>
                <label>simple:superscript</label>
                <item>superscript</item>
                <label>simple:topbraced</label>
                <item>marked with a brace above the text</item>
                <label>simple:typewriter</label>
                <item>fixed-width typeface, like typewriter</item>
                <label>simple:underline</label>
                <item>underlined with single line</item>
                <label>simple:wavyunderline</label>
                <item>underlined with wavy line</item>
              </list>
            </p>
            <p>The <code>simple:</code> prefix used here must be mapped to a location at which the
              full rendition declaration can be found, by default the XML source of the present
              document.</p>
            <p> Full details of the way these elements may be used are provided in the relevant
              section of the TEI Guidelines (<ptr
                target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD57"/>)</p>

          </div>
          <div xml:id="refsdecl">
            <head>Reference, Prefix, and Classification Declarations</head>
            <p>The <gi>refsDecl</gi> element is used to document the way in which any standard
              referencing scheme built into the encoding works. In its simplest form, it consists of
              prose description.</p>
            <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><refsDecl><p>The
                      <att>n</att> attribute on each <gi>div</gi> contains the canonical reference
                    for each division in the form XX.yyy where XX is the book number in roman
                    numeral and yyy is the section number in arabic.</p><p>Milestone tags refer to
                    the edition of 1830 as E30 and that of 1850 as E50. </p></refsDecl></egXML></p>
            <p>The <gi>listPrefixDef</gi> element contains one or more <gi>prefixDef</gi> elements,
              each defining a prefix which has been used to abbreviate references to other
              documents, for example as the value of a <att>target</att> or other pointing
              attribute. The definition provides information about how the prefix can be translated
              automatically into a full URL, as in the following example: <egXML
                xmlns="http://www.tei-c.org/ns/Examples">
                <listPrefixDef>
                  <prefixDef ident="psn" matchPattern="([A-Z]+)"
                    replacementPattern="http://www.example.com/personography.xml#$1"/>
                </listPrefixDef></egXML>
            </p>
            <p>In this case, a pointer value in the form <code>psn:MDH</code> would be translated to
                <code>http://www.example.com/personography.xml#MDH</code>. </p>
            <p>The <gi>classDecl</gi> element groups together definitions or sources for any
              descriptive classification schemes or <term>taxonomies</term> used by other parts of
              the header. These schemes may be defined in a number of different ways, using one or
              more of the following elements: <specList>
                <specDesc key="taxonomy"/>
                <specDesc key="bibl"/>
                <specDesc key="category"/>
                <specDesc key="catDesc"/>
              </specList></p>
            <p> In the simplest case, the taxonomy may be defined by a bibliographic reference, as
              in the following example: <egXML xmlns="http://www.tei-c.org/ns/Examples"
                    ><classDecl><taxonomy xml:id="LC-SH"><bibl>Library of Congress Subject Headings
                    </bibl></taxonomy></classDecl></egXML></p>
            <p>Alternatively, or in addition, the encoder may define a special purpose
              classification scheme, as in the following example: <egXML
                xmlns="http://www.tei-c.org/ns/Examples"><taxonomy xml:id="B"><bibl>Brown
                    Corpus</bibl><category xml:id="B.A"><catDesc>Press Reportage</catDesc><category
                      xml:id="B.A1"><catDesc>Daily</catDesc></category><category xml:id="B.A2"
                        ><catDesc>Sunday</catDesc></category><category xml:id="B.A3"
                        ><catDesc>National</catDesc></category><category xml:id="B.A4"
                        ><catDesc>Provincial</catDesc></category><category xml:id="B.A5"
                        ><catDesc>Political</catDesc></category><category xml:id="B.A6"
                        ><catDesc>Sports</catDesc></category></category><category xml:id="B.D"
                      ><catDesc>Religion</catDesc><category xml:id="B.D1"
                      ><catDesc>Books</catDesc></category><category xml:id="B.D2"
                        ><catDesc>Periodicals and tracts</catDesc></category></category>
                </taxonomy></egXML></p>
            <p>Linkage between a particular text and a category within such a taxonomy is made by
              means of the <gi>catRef</gi> element within the <gi>textClass</gi> element, as
              described in the next section.</p>
          </div>
        </div>
        <div xml:id="profDesc">
          <head>The Profile Description</head>
          <p>The <gi>profileDesc</gi> element gathers together information about various descriptive
            aspects of a text. It has the following optional components: <specList>
              <specDesc key="creation"/>
              <specDesc key="abstract"/>
              <specDesc key="particDesc"/>
              <specDesc key="settingDesc"/>
              <specDesc key="langUsage"/>
              <specDesc key="textClass"/>
            </specList></p>
          <p>The <gi>creation</gi> element documents where a work was created, even though it may
            not have been published or recorded there.</p>
          <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><creation><date when="1992-08"
                  >August 1992</date><name type="place">Taos, New
            Mexico</name></creation></egXML></p>
          <p>The <gi>abstract</gi> element may be used to provide a brief summary or abstract of the
            document concerned: it is most usually applied to texts born digital: <egXML
              xmlns="http://www.tei-c.org/ns/Examples">
              <profileDesc>
                <abstract>
                  <p>This paper is a draft studying various aspects of using the TEI as a reference
                    serialization framework for LMF. Comments are welcome to bring this to a useful
                    document for the community. </p>
                </abstract>
              </profileDesc>
            </egXML>
          </p>
          <p>The <gi>particDesc</gi> element is used to list descriptive information about the real
            or fictional participants in a text, for example the characters in a novel or a play. It
            contains at least one <gi>listPerson</gi> element, which contains individual
              <gi>person</gi> elements <specList>
              <specDesc key="listPerson"/>
              <specDesc key="person"/>
            </specList> For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <profileDesc>
                <particDesc>
                  <listPerson>
                    <person xml:id="OPI"><p><name>Dr Opimian</name> : named for the famous Roman
                        fine wine.</p></person>
                    <person xml:id="GRM"><p><name>Mr Gryll</name> : named for the mythical Gryllus,
                        one of Ulysses' sailors transformed by Circe into a pig, who argues that he
                        was happier in that state than as a man.</p></person>
                  </listPerson>
                </particDesc></profileDesc>
            </egXML></p>
          <p>In the same way, the <gi>settingDesc</gi> element can be used to list descriptive
            information about the real or fictional places mentioned in a text. It contains at least
            one <gi>listPlace</gi> element, which contains individual <gi>place</gi> elements. <specList>
              <specDesc key="listPlace"/>
              <specDesc key="place"/>
            </specList> For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <profileDesc>
                <settingDesc>
                  <listPlace>
                    <head>Houses mentioned in <title>Pride and Prejudice</title></head>
                    <place xml:id="NETF1"><p><name>Netherfield Park</name> : home of the
                        Bingleys</p></place>
                    <place xml:id="PEMB1"><p><name>Pemberley</name> : home of Mr Darcy</p></place>
                  </listPlace>
                </settingDesc></profileDesc>
            </egXML></p>
          <p>The full Guidelines provide a rich range of additional elements to define more
            structured information about persons and places; these are not however available in TEI
            Simple.</p>
          <p>The <gi>langUsage</gi> element is useful where a text contains many different
            languages. It may contain <gi>language</gi> elements to document each particular
            language used: <specList>
              <specDesc key="language"/>
            </specList> For example, a text containing predominantly text in French as spoken in
            Quebec, but also smaller amounts of British and Canadian English might be documented as
            follows: <egXML xmlns="http://www.tei-c.org/ns/Examples"><langUsage>
                <language ident="fr-CA" usage="60">Québecois</language>
                <language ident="en-CA" usage="20">Canadian business English</language>
                <language ident="en-GB" usage="20">British English</language>
              </langUsage>
            </egXML>
          </p>
          <p>The <gi>textClass</gi> element classifies a text. This may be done with reference to a
            classification system locally defined by means of the <gi>classDecl</gi> element, or by
            reference to some externally defined established scheme such as the Universal Decimal
            Classification. Texts may also be classified using lists of keywords, which may
            themselves be drawn from locally or externally defined control lists. The following
            elements are used to supply such classifications: <specList>
              <specDesc key="classCode"/>
              <specDesc key="catRef"/>
              <specDesc key="keywords"/>
            </specList>
          </p>
          <p>The simplest way of classifying a text is by means of the <gi>classCode</gi> element.
            For example, a text with classification 410 in the Universal Decimal Classification
            might be documented as follows: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <classCode scheme="http://www.udc.org">410</classCode>
            </egXML>
          </p>
          <p>When a classification scheme has been locally defined using the <gi>taxonomy</gi>
            element discussed in the preceding subsection, the <gi>catRef</gi> element should be
            used to reference it. To continue the earlier example, a work classified in the Brown
            Corpus as <code>Press reportage - Sunday</code> and also as <code>Religion</code> might
            be documented as follows: <egXML xmlns="http://www.tei-c.org/ns/Examples">
              <catRef target="#B.A3 #B.D"/>
            </egXML>
          </p>
          <p>The element <gi>keywords</gi> contains a list of keywords or phrases identifying the
            topic or nature of a text. As usual, the attribute <att>scheme</att> identifies the
            source from which these terms are taken. For example, if the LC Subject Headings are
            used, following declaration of that classification system in a <gi>taxonomy</gi> element
            as above : <egXML xmlns="http://www.tei-c.org/ns/Examples"><textClass><keywords
                  scheme="#LCSH"><list>
                    <item>English literature -- History and criticism -- Data processing.</item>
                    <item>English literature -- History and criticism -- Theory etc.</item>
                    <item>English language -- Style -- Data processing.</item>
                  </list></keywords></textClass></egXML></p>
          <p>Multiple classifications may be supplied using any of the mechanisms described in this
            section.</p>
        </div>
        <div>
          <head>Other forms of metadata</head>
          <p>The TEI Header was one of the first attempts to provide a full range of metadata
            elements, but it is by no means the only standard now used for this purpose. To
            facilitate the management of large digital collections and to simplify interoperability
            of TEI and non-TEI resources, the following element may be found useful: <specList>
              <specDesc key="xenoData"/>
            </specList></p>
          <p>A typical use for this element might be to store a set of descriptors conforming to the
            Dublin Core standard in the Header rather than to generate them automatically from the
            corresponding TEI elements. For examples and discussion, see the TEI Guidelines at <ptr
              target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD9"/></p>
        </div>
        <div>
          <head>The Revision Description</head>
          <p>The <gi>revisionDesc</gi> element provides a change log in which each significant
            change made to a text may be recorded. It is always the last element in a
              <gi>teiHeader</gi> and contains the following elements: <specList>
              <specDesc key="change"/>
              <specDesc key="listChange"/>
            </specList>
          </p>
          <p>Each <gi>change</gi> element contains a brief description of a significant change. The
            attributes <att>when</att> and <att>who</att> may be used to identify when the change
            was carried out and the person responsible for it. </p>
          <p>It is good practice (but not required) to group changes together within a
              <gi>listChange</gi> element. </p>
          <p>Example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><revisionDesc>
                <listChange>
                  <change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
                  <change when="1991-11-02" who="#MSM"> completed first draft </change>
                </listChange>
              </revisionDesc></egXML></p>
          <p>In a production environment it will usually be found preferable to use some kind of
            automated system to track and record changes. Many such <term>version control
              systems</term>, as they are known, can also be configured to update the TEI Header of
            a file automatically. </p>
        </div>
      </div>
      <div xml:id="processingmodel">
        <head>The Simple Processing Model</head>
        <p>Unlike most other TEI customizations, TEI Simple includes documentation of the intended
          processing associated with the majority of elements. As noted above, the TEI provides
          components such as the <att>rendition</att> attribute to indicate the appearance of
          particular parts of a document in the non-digital source from which it is derived. With
          TEI Simple, it is also possible to indicate how in general an element should be processed,
          in particular its intended appearance when processed for display on a screen or on paper.
          This ability derives from a number of capabilities recently added to the TEI architecture
          for the specification of processing, which were developed as part of the project that
          defined the TEI Simple schema.</p>

        <p> The key feature of this <soCalled>processing model</soCalled> is a notation that allows
          the encoder to associate each element with one or more categories, which we call its
            <term>behaviour</term>s. In addition, the processing model indicates how the element
          should be rendered, possibly differently in differing circumstances, using the W3C
          Cascading Stylesheets Standard (CSS) mentioned above. It is consequently much easier to
          develop processors for documents conforming to TEI Simple, since the complexity of the
          task is much reduced.</p>

        <p>Twenty-five different behaviours are currently defined by the TEI processing model. Their
          names indicate informally the categorisation concerned, and should be readily
          comprehensible for most programmers. The following table indicates the TEI Simple elements
          associated with each. </p>

        <table>
          <row role="label">
            <cell>Behaviour</cell>
            <cell>Used by</cell>
            <cell>Effect</cell>
          </row>
          <row>
            <cell>alternate</cell>
            <cell>choice date</cell>
            <cell>support display of alternative visualisations, for example by displaying the
              preferred content, by displaying both in parallel, or by toggling between the
              two.</cell>
            <!-- document(model.xml)/elementSpec/attList/attDef[@ident='behaviour']/valList/valItem[@ident='{../cell[1]}']/desc -->
          </row>
          <row>
            <cell>anchor</cell>
            <cell>anchor </cell>
            <cell>create an identifiable anchor point in the output. </cell>
          </row>
          <row>
            <cell>block</cell>
            <cell>address addrLine argument back body byline closer dateline div docTitle epigraph
              figure floatingText formula front fw group head imprimatur l lg listBibl note opener
              postscript q quote role roleDesc salute signed sp speaker spGrp stage titlePage
              titlePart trailer </cell>
            <cell>create a block structure</cell>
          </row>

          <row>
            <cell>body</cell>
            <cell>text </cell>
            <cell>create the body of a document</cell>
          </row>
          <row>
            <cell>break</cell>
            <cell>cb lb pb</cell>
            <cell>create a line, column, or page break according to the value of
              <ident>type</ident></cell>
          </row>

          <row>
            <cell>cell</cell>
            <cell>cell </cell>
            <cell>create a table cell</cell>
          </row>
          <row>
            <cell>cit</cell>
            <cell>cit </cell>
            <cell>show the content, with an indication of the source</cell>
          </row>
          <row>
            <cell>document</cell>
            <cell>TEI </cell>
            <cell>start a new output document</cell>
          </row>
          <row>
            <cell>glyph</cell>
            <cell>g </cell>
            <cell>show a character by looking up reference to a chardesc at the given URI</cell>
          </row>
          <row>
            <cell>graphic</cell>
            <cell>graphic </cell>
            <cell>if <ident>url</ident> is present, use it to display graphic, else display a
              placeholder image. </cell>

          </row>
          <row>
            <cell>heading</cell>
            <cell>head </cell>
            <cell>creates a heading.</cell>
          </row>
          <row>
            <cell>index</cell>
            <cell>body </cell>
            <cell>generate list according to type.</cell>
          </row>
          <row>
            <cell>inline</cell>
            <cell>abbr actor add am author bibl biblScope c choice code corr date del desc docAuthor
              docDate docEdition docImprint editor email ex expan figDesc figure foreign formula fw
              g gap handShift hi label measure milestone name note num orig pc q quote ref reg
              relatedItem rhyme rs s salute seg sic signed subst supplied time title unclear w </cell>
            <cell>creates inline element out of content if there's something in
                <gi>outputRendition</gi>, use that formatting; otherwise just show text of selected
              content.: </cell>
          </row>
          <row>
            <cell>link</cell>
            <cell>ref </cell>
            <cell>create hyperlink.</cell>
          </row>
          <row>
            <cell>list</cell>
            <cell>castGroup castList list listBibl </cell>
            <cell>create a list.</cell>
          </row>

          <row>
            <cell>listItem</cell>
            <cell>bibl castItem item </cell>
            <cell>create a list item.</cell>
          </row>
          <row>
            <cell>metadata</cell>
            <cell>teiHeader </cell>
            <cell>create metadata section.</cell>
          </row>
          <row>
            <cell>note</cell>
            <cell>note </cell>
            <cell>create a note, often out of line, depending on the value of place; could be
              margin, footnote, endnote, inline.</cell>
          </row>
          <row>
            <cell>omit</cell>
            <cell>author editor publisher pubPlace profileDesc revisionDesc encodingDesc </cell>
            <cell>
              <hi>do nothing, do not process children: </hi>
            </cell>
          </row>
          <row>
            <cell>paragraph</cell>
            <cell>ab p</cell>
            <cell>create a paragraph out of content.</cell>
          </row>
          <row>
            <cell>row</cell>
            <cell>row </cell>
            <cell>create a table row:</cell>
          </row>
          <row>
            <cell>section</cell>
            <cell>div </cell>
            <cell>create a new section of the output document</cell>
          </row>
          <row>
            <cell>table</cell>
            <cell>table </cell>
            <cell>create a table</cell>
          </row>
          <row>
            <cell>text</cell>
            <cell>title</cell>
            <cell>create literal text</cell>
          </row>
          <row>
            <cell>title</cell>
            <cell>fileDesc </cell>
            <cell>create document title</cell>
          </row>
        </table>
        <p>Full documentation of the processing model is provided in section <ptr
            target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html#TDPM"/> of the TEI
          Guidelines, and we do not describe it further here. </p>
      </div>


      <div>
        <head>The TEI Simple schema</head>
        <schemaSpec ident="teisimple" start="TEI teiCorpus">
          <specGrpRef target="#base"/>
          <specGrpRef target="#header"/>
          <specGrpRef target="#header2"/>
          <!--specGrpRef target="#transcr"/-->
          <specGrpRef target="#simpleFax"/>
          <specGrpRef target="#attclasses"/>
          <specGrpRef target="#modelclasses"/>
          <specGrpRef target="#simpleelements"/>
          <specGrpRef target="#simpleelementspm"/>
          <specGrpRef target="#simplechanges"/>
          <!--specGrpRef target="#rendition"/-->
        </schemaSpec>
        <div>
          <head>Summary</head>
          <p>The TEI Simple schema defines a total of 166 elements, of which 56 appear in the TEI
            Header alone. Processing Models are defined for most of the elements. </p>
          <p>The schema uses the whole of the TEI base module, the whole of the TEI gaiji module,
            and the whole of the header module, with the exception of about 24 elements considered
            to be of specialised interest only.</p>
          <specGrp xml:id="base">
            <moduleRef key="tei"/>
          </specGrp>


          <specGrp xml:id="header">

            <p>The header is defined by exclusion: this means that we may need to revisit this list
              should any new elements be added to the Header in the future.</p>

            <moduleRef key="header"
              except="appInfo application cRefPattern calendar calendarDesc 
              correction correspAction correspContext correspDesc geoDecl hyphenation interpretation 
              normalization punctuation quotation refState  scriptNote 
              segmentation styleDefDecl stdVals typeNote"/>
            <moduleRef key="gaiji"/>
            <moduleRef key="corpus" include="particDesc settingDesc"/>
            <p>We include particDesc from the corpus module, but remove it from the model.listLike
              class so that it can only appear inside profileDesc.</p>
            <elementSpec ident="particDesc" module="corpus" mode="change">
              <classes>
                <memberOf key="att.global"/>
              </classes>
            </elementSpec>
            <!-- 
            <moduleRef key="header"/>
            <!-\- <elementRef key="att"/>-\->
            <elementRef key="analytic"/>
            <elementRef key="biblFull"/>
            <!-\- used by bibl -\->
            <elementRef key="biblStruct"/>
            <elementRef key="change"/>
            <elementRef key="charDecl"/>
            <elementRef key="charProp"/>
            <!-\- <elementRef key="editor"/>
          -\->
            <elementRef key="editorialDecl"/>
            <!-\- <elementRef key="email"/>
         -\->
            <elementRef key="encodingDesc"/>
            <elementRef key="extent"/>
            <elementRef key="fileDesc"/>
            <!-\- <elementRef key="gi"/>
          -\->
            <elementRef key="glyph"/>
            <elementRef key="glyphName"/>
            <elementRef key="idno"/>
            <elementRef key="imprint"/>
            <elementRef key="keywords"/>
            <elementRef key="licence"/>
            <elementRef key="listChange"/>
            <elementRef key="listPerson"/>
            <elementRef key="localName"/>
            <elementRef key="monogr"/>
            <!-\-    <elementRef key="msDesc"/>
            <elementRef key="msIdentifier"/>-\->
            <elementRef key="person"/>
            <!-\-  <elementRef key="physDesc"/>
         -\->
            <elementRef key="profileDesc"/>
            <elementRef key="publicationStmt"/>
            <!-\- <elementRef key="relatedItem"/>-\->
            <!-\- allowed in bibl -\->
            <!-\-  <elementRef key="repository"/>
          -\->
            <elementRef key="resp"/>
            <elementRef key="respStmt"/>
            <elementRef key="sourceDesc"/>
            <!-\-   <elementRef key="tag"/>-\->
            <elementRef key="teiHeader"/>
            <elementRef key="term"/>
            <elementRef key="textClass"/>
            <!-\-<elementRef key="textDesc"/>-\->
            <elementRef key="titleStmt"/>
            <!-\- <elementRef key="typeDesc"/>
            <elementRef key="val"/>
            <elementRef key="value"/>-\->-->
          </specGrp>

          <specGrp xml:id="header2">
            <!-- <p>Elements which are only intended to be used in the header are banned from the
                <gi>text</gi>, using a Schematron rule.</p>-->
            <p>A schematron rule is provided to prevent some elements which could otherwise appear
              in either header and text from appearing in the latter. </p>
            <elementSpec ident="text" mode="change">
              <constraintSpec xmlns="http://www.tei-c.org/ns/1.0"
                xmlns:XSL="http://www.w3.org/1999/XSL/Transform" ident="headeronlyelement"
                scheme="isoschematron">
                <constraint>
                  <!-- <rule xmlns="http://purl.oclc.org/dsdl/schematron"
                    context="tei:att | tei:biblFull | tei:biblStruct | tei:change | tei:charDecl | tei:charProp | tei:editor
                    | tei:editorialDecl | tei:email | tei:encodingDesc | tei:extent | tei:fileDesc | tei:gi | tei:glyph | tei:glyphName | 
                    tei:idno | tei:imprint | tei:keywords | tei:licence | tei:listChange | tei:listPerson | tei:localName | tei:monogr | 
                    tei:msDesc | tei:msIdentifier | tei:person | tei:physDesc | tei:profileDesc | tei:publicationStmt | tei:relatedItem | 
                    tei:repository | tei:resp | tei:respStmt | tei:sourceDesc | tei:tag | tei:teiHeader | tei:term | tei:textClass | tei:textDesc 
                    | tei:titleStmt | tei:typeDesc | tei:val | tei:value">-->
                  <rule xmlns="http://purl.oclc.org/dsdl/schematron" context=" tei:biblFull ">
                    <report test="ancestor::tei:text">Error: The element <name/> is not permitted
                      outside the header</report>
                  </rule>
                </constraint>
              </constraintSpec>
            </elementSpec>
          </specGrp>
        </div>
        <!-- <div>
          <head>Transcription</head>
          <p>In order to support the <gi>sourcedoc</gi> and <gi>facsimile</gi> elements, the basic
            transcriptional elements are loaded, and two attribute classes.</p>
            <specGrp xml:id="transcr">
            <elementRef key="damage"/>
            <elementRef key="damageSpan"/>
            <elementRef key="facsimile"/>
            <elementRef key="line"/>
            <elementRef key="listTranspose"/>
            <elementRef key="metamark"/>
            <elementRef key="mod"/>
            <elementRef key="redo"/>
            <elementRef key="restore"/>
            <elementRef key="retrace"/>
            <elementRef key="sourceDoc"/>
            <elementRef key="surface"/>
            <elementRef key="surfaceGrp"/>
            <elementRef key="surplus"/>
            <elementRef key="transpose"/>
            <elementRef key="undo"/>
            <elementRef key="zone"/>
            <classRef key="att.coordinated"/>
            <classRef key="att.global.change"/>
          </specGrp>
        </div>-->
        <div>
          <head>Add support for facsimile</head>
          <specGrp xml:id="simpleFax">
            <elementRef key="facsimile"/>
            <elementRef key="surface"/>
            <elementRef key="zone"/>
            <classRef key="att.coordinated"/>
          </specGrp>
        </div>
        <div>
          <head>Attribute classes</head>
          <specGrp xml:id="attclasses">
            <p>The <term>tei</term> module brings with it a default set of attribute classes. We
              need some more specialist ones from other modules</p>
            <classRef key="att.global.analytic"/>
            <classRef key="att.global.facs"/>
            <classRef key="att.milestoneUnit"/>
            <classRef key="att.global.linking"/>
            <p>We delete some classes which are not used at all.</p>
            <classSpec type="atts" ident="att.datcat" mode="delete"/>
            <classSpec type="atts" ident="att.declarable" mode="delete"/>
            <classSpec type="atts" ident="att.declaring" mode="delete"/>
            <classSpec type="atts" ident="att.ranging" mode="delete"/>
            <classSpec type="atts" ident="att.divLike" mode="delete"/>

            <p>We delete some attributes from global linking.</p>
            <classSpec type="atts" ident="att.global.linking" mode="change">
              <attList>
                <attDef ident="sameAs" mode="delete"/>
                <attDef ident="synch" mode="delete"/>
                <attDef ident="copyOf" mode="delete"/>
                <attDef ident="exclude" mode="delete"/>
                <attDef ident="select" mode="delete"/>
              </attList>
            </classSpec>
            <p>We simplify the att.canonical class by removing @key</p>
            <classSpec type="atts" ident="att.canonical" mode="change">
              <attList>
                <attDef ident="key" mode="delete"/>
              </attList>
            </classSpec>
            <p>We simplify the att.editLike class </p>
            <classSpec type="atts" ident="att.editLike" mode="change">
              <attList>
                <attDef ident="evidence" mode="delete"/>
                <attDef ident="instant" mode="delete"/>
              </attList>
            </classSpec>
            <p>URLs have a constraint that a local pointer must have a corresponding ID.</p>
            <classSpec type="atts" ident="att.pointing" mode="change">
              <attList>
                <attDef ident="target" mode="change">
                  <constraintSpec ident="validtarget" scheme="isoschematron">
                    <constraint>
                      <rule xmlns="http://purl.oclc.org/dsdl/schematron" context="tei:*[@target]">
                        <let name="results"
                          value="for $t in  tokenize(normalize-space(@target),'\s+') return starts-with($t,'#') and not(id(substring($t,2)))"/>
                        <report test="some $x in $results  satisfies $x"> Error: Every local pointer
                          in "<value-of select="@target"/>" must point to an ID in this document
                            (<value-of select="$results"/>)</report>
                      </rule>
                    </constraint>
                  </constraintSpec>
                </attDef>
              </attList>
            </classSpec>
            <p>Constrained value lists are added to attribute classes where possible.</p>
            <classSpec type="atts" mode="change" ident="att.placement">
              <attList>
                <attDef ident="place" mode="change">
                  <valList type="closed" mode="replace">
                    <valItem ident="above">
                      <desc>above the line</desc>
                    </valItem>
                    <valItem ident="below">
                      <desc>below the line</desc>
                    </valItem>
                    <valItem ident="top">
                      <desc>at the top of the page</desc>
                    </valItem>
                    <valItem ident="top-right">
                      <desc>at the top right of the page</desc>
                    </valItem>
                    <valItem ident="top-left">
                      <desc>at the top left of the page</desc>
                    </valItem>
                    <valItem ident="top-centre">
                      <desc>at the top center of the page</desc>
                    </valItem>
                    <valItem ident="bottom-right">
                      <desc>at the bottom right of the page</desc>
                    </valItem>
                    <valItem ident="bottom-left">
                      <desc>at the bottom left of the page</desc>
                    </valItem>
                    <valItem ident="bottom-centre">
                      <desc>at the bottom centre of the page</desc>
                    </valItem>
                    <valItem ident="bottom">
                      <desc>at the foot of the page</desc>
                    </valItem>
                    <valItem ident="tablebottom">
                      <desc>underneath a table</desc>
                    </valItem>
                    <valItem ident="margin-right">
                      <desc>in the right-hand margin</desc>
                    </valItem>
                    <valItem ident="margin">
                      <desc>in the outer margin</desc>
                    </valItem>
                    <valItem ident="margin-inner">
                      <desc>in the inner margin</desc>
                    </valItem>
                    <valItem ident="margin-left">
                      <desc>in the left-hand margin</desc>
                    </valItem>
                    <valItem ident="opposite">
                      <desc>on the opposite, i.e. facing, page.</desc>
                    </valItem>
                    <valItem ident="overleaf">
                      <desc>on the other side of the leaf.</desc>
                    </valItem>
                    <valItem ident="overstrike">
                      <desc>superimposed on top of the current context</desc>
                    </valItem>
                    <valItem ident="end">
                      <desc>at the end of the volume.</desc>
                    </valItem>
                    <valItem ident="divend">
                      <desc>at the end the current division.</desc>
                    </valItem>
                    <valItem ident="parend">
                      <desc>at the end the current paragraph.</desc>
                    </valItem>
                    <valItem ident="inline">
                      <desc>within the body of the text.</desc>
                    </valItem>
                    <valItem ident="inspace">
                      <desc>in a predefined space, for example left by an earlier scribe.</desc>
                    </valItem>
                    <valItem ident="block">
                      <desc>formatted as an indented paragraph</desc>
                    </valItem>
                  </valList>
                </attDef>
              </attList>
            </classSpec>
            <classSpec type="atts" ident="att.dimensions" mode="change">
              <attList>
                <attDef ident="unit" mode="change">
                  <valList mode="add" type="closed">
                    <valItem ident="chars">
                      <desc>characters</desc>
                    </valItem>
                    <valItem ident="lines">
                      <desc>lines</desc>
                    </valItem>
                    <valItem ident="pages">
                      <desc>pages</desc>
                    </valItem>
                    <valItem ident="words">
                      <desc>words</desc>
                    </valItem>
                    <valItem ident="cm">
                      <desc>centimetres</desc>
                    </valItem>
                    <valItem ident="mm">
                      <desc>millimetre</desc>
                    </valItem>
                    <valItem ident="in">
                      <desc>inches</desc>
                    </valItem>
                  </valList>
                </attDef>
                <attDef ident="precision" mode="delete"/>
              </attList>
            </classSpec>
            <classSpec type="atts" ident="att.global.rendition" mode="change">
              <constraintSpec ident="renditionpointer" scheme="isoschematron">
                <constraint>
                  <rule xmlns="http://purl.oclc.org/dsdl/schematron" context="tei:*[@rendition]">
                    <let name="results"
                      value="for $val in tokenize(normalize-space(@rendition),'\s+') return starts-with($val,'simple:')        or        (starts-with($val,'#')        and        //tei:rendition[@xml:id=substring($val,2)])"/>
                    <assert test="every $x in $results satisfies $x"> Error: Each of the rendition
                      values in "<value-of select="@rendition"/>" must point to a local ID or to a
                      token in the Simple scheme (<value-of select="$results"/>)</assert>
                  </rule>
                </constraint>
              </constraintSpec>
              <constraintSpec ident="corresppointer" scheme="isoschematron">
                <constraint>
                  <rule xmlns="http://purl.oclc.org/dsdl/schematron" context="tei:*[@corresp]">
                    <let name="results"
                      value="for $t in tokenize(normalize-space(@corresp),'\s+') return starts-with($t,'#') and not(id(substring($t,2)))"/>
                    <report test="some $x in $results  satisfies $x"> Error: Every local pointer in
                        "<value-of select="@corresp"/>" must point to an ID in this document
                        (<value-of select="$results"/>)</report>
                  </rule>
                </constraint>
              </constraintSpec>
              <attList>
                <attDef ident="rend" mode="delete"/>
                <attDef ident="style" mode="delete"/>
                <attDef ident="rendition" mode="change">
                  <valList mode="add" type="semi">
                    <valItem ident="simple:allcaps">
                      <desc>all capitals</desc>
                    </valItem>
                    <valItem ident="simple:blackletter">
                      <desc>black letter or gothic typeface</desc>
                    </valItem>
                    <valItem ident="simple:bold">
                      <desc>bold typeface</desc>
                    </valItem>
                    <valItem ident="simple:bottombraced">
                      <desc>marked with a brace under the bottom of the text</desc>
                    </valItem>
                    <valItem ident="simple:boxed">
                      <desc>border around the text</desc>
                    </valItem>
                    <valItem ident="simple:centre">
                      <desc>centred</desc>
                    </valItem>
                    <valItem ident="simple:cursive">
                      <desc>cursive typeface</desc>
                    </valItem>
                    <valItem ident="simple:display">
                      <desc>block display</desc>
                    </valItem>
                    <valItem ident="simple:doublestrikethrough">
                      <desc>strikethrough with double line</desc>
                    </valItem>
                    <valItem ident="simple:doubleunderline">
                      <desc>underlined with double line</desc>
                    </valItem>
                    <valItem ident="simple:dropcap">
                      <desc>initial letter larger or decorated</desc>
                    </valItem>
                    <valItem ident="simple:float">
                      <desc>floated out of main flow</desc>
                    </valItem>
                    <valItem ident="simple:hyphen">
                      <desc>with a hyphen here (eg in line break)</desc>
                    </valItem>
                    <valItem ident="simple:inline">
                      <desc>inline rendering</desc>
                    </valItem>
                    <valItem ident="simple:justify">
                      <desc>justified text</desc>
                    </valItem>
                    <valItem ident="simple:italic">
                      <desc>italic typeface</desc>
                    </valItem>
                    <valItem ident="simple:larger">
                      <desc>larger type</desc>
                    </valItem>
                    <valItem ident="simple:left">
                      <desc>aligned to the left or left-justified</desc>
                    </valItem>
                    <valItem ident="simple:leftbraced">
                      <desc>marked with a brace on the left side of the text</desc>
                    </valItem>
                    <valItem ident="simple:letterspace">
                      <desc>larger-than-normal spacing between letters, usually for emphasis</desc>
                    </valItem>
                    <valItem ident="simple:literal">
                      <desc>fixed-width typeface, spacing preserved</desc>
                    </valItem>
                    <valItem ident="simple:normalstyle">
                      <desc>upright shape and default weight of typeface</desc>
                    </valItem>
                    <valItem ident="simple:normalweight">
                      <desc>normal typeface weight</desc>
                    </valItem>
                    <valItem ident="simple:right">
                      <desc>aligned to the right or right-justified</desc>
                    </valItem>
                    <valItem ident="simple:rightbraced">
                      <desc>marked with a brace to the right of the text</desc>
                    </valItem>
                    <valItem ident="simple:rotateleft">
                      <desc>rotated to the left</desc>
                    </valItem>
                    <valItem ident="simple:rotateright">
                      <desc>rotated to the right</desc>
                    </valItem>
                    <valItem ident="simple:smallcaps">
                      <desc>small caps</desc>
                    </valItem>
                    <valItem ident="simple:smaller">
                      <desc>smaller type</desc>
                    </valItem>
                    <valItem ident="simple:strikethrough">
                      <desc>strike through</desc>
                    </valItem>
                    <valItem ident="simple:subscript">
                      <desc>subscript</desc>
                    </valItem>
                    <valItem ident="simple:superscript">
                      <desc>superscript</desc>
                    </valItem>
                    <valItem ident="simple:topbraced">
                      <desc>marked with a brace above the text</desc>
                    </valItem>
                    <valItem ident="simple:typewriter">
                      <desc>fixed-width typeface, like typewriter</desc>
                    </valItem>
                    <valItem ident="simple:underline">
                      <desc>underlined with single line</desc>
                    </valItem>
                    <valItem ident="simple:wavyunderline">
                      <desc>underlined with wavy line</desc>
                    </valItem>
                  </valList>
                </attDef>
              </attList>
            </classSpec>
          </specGrp>
        </div>
        <div>
          <head>Model classes</head>
          <specGrp xml:id="modelclasses">
            <p>The following unused model classes are removed.</p>
            <!-- why is this needed? the ODD processor should do it for you-->
            <classSpec type="model" ident="model.entryPart" mode="delete"/>
            <classSpec type="model" ident="model.placeNamePart" mode="delete"/>
            <classSpec type="model" ident="model.placeStateLike" mode="delete"/>
            <classSpec type="model" ident="model.egLike" mode="delete"/>
            <classSpec type="model" ident="model.offsetLike" mode="delete"/>
            <classSpec type="model" ident="model.pPart.msdesc" mode="delete"/>
            <classSpec type="model" ident="model.oddDecl" mode="delete"/>
            <classSpec type="model" ident="model.specDescLike" mode="delete"/>
            <classSpec type="model" ident="model.entryPart" mode="delete"/>
            <classSpec type="model" ident="model.placeNamePart" mode="delete"/>
            <classSpec type="model" ident="model.placeStateLike" mode="delete"/>
            <classSpec type="model" ident="model.certLike" mode="delete"/>
            <classSpec type="model" ident="model.glossLike" mode="delete"/>
          </specGrp>
        </div>
        <div>
          <head>Elements</head>
          <p>The main part of Simple is the set of selected elements.</p>
          <specGrp xmlns="http://www.tei-c.org/ns/1.0"
            xmlns:XSL="http://www.w3.org/1999/XSL/Transform" xml:id="simpleelements">
            <elementRef key="ab"/>
            <elementRef key="abbr"/>
            <elementRef key="actor"/>
            <elementRef key="add"/>
            <elementRef key="address"/>
            <elementRef key="addrLine"/>
            <!-- elementRef key="addSpan"/-->
            <elementRef key="am"/>
            <elementRef key="anchor"/>
            <elementRef key="argument"/>
            <elementRef key="author"/>
            <elementRef key="back"/>
            <elementRef key="bibl"/>
            <elementRef key="biblScope"/>
            <!-- added for bibl -->
            <elementRef key="body"/>
            <elementRef key="byline"/>
            <elementRef key="c"/>
            <elementRef key="castGroup"/>
            <elementRef key="castItem"/>
            <elementRef key="castList"/>
            <elementRef key="cb"/>
            <elementRef key="cell"/>
            <elementRef key="choice"/>
            <elementRef key="cit"/>
            <elementRef key="closer"/>
            <elementRef key="code"/>
            <elementRef key="corr"/>
            <elementRef key="date"/>
            <elementRef key="dateline"/>
            <elementRef key="del"/>
            <elementRef key="desc"/>
       
            <elementRef key="div"/>
            <elementRef key="docAuthor"/>
            <elementRef key="docDate"/>
            <elementRef key="docEdition"/>
            <elementRef key="docImprint"/>
            <elementRef key="docTitle"/>
            <elementRef key="editor"/>
            <!-- added for bibl -->
            <elementRef key="email"/>
            <!-- added for bibl -->
            <elementRef key="epigraph"/>
            <elementRef key="ex"/>
            <elementRef key="expan"/>
            <elementRef key="figDesc"/>
            <elementRef key="figure"/>
            <elementRef key="floatingText"/>
            <elementRef key="foreign"/>
            <elementRef key="formula"/>
            <elementRef key="front"/>
            <elementRef key="fw"/>
            <elementRef key="g"/>
            <elementRef key="gap"/>
            <elementRef key="graphic"/>
            <elementRef key="group"/>
            <!-- elementRef key="handShift"/-->
            <elementRef key="head"/>
            <elementRef key="hi"/>
            <elementRef key="imprimatur"/>
            <elementRef key="item"/>
            <elementRef key="l"/>
            <elementRef key="label"/>
            <elementRef key="lb"/>
            <elementRef key="lg"/>
            <elementRef key="list"/>
            <elementRef key="listBibl"/>
            <elementRef key="listPerson"/>
            <elementRef key="listPlace"/>

            <elementRef key="measure"/>
            <elementRef key="milestone"/>
            <elementRef key="name"/>
            <elementRef key="note"/>
            <elementRef key="num"/>
            <elementRef key="opener"/>
            <elementRef key="orig"/>
            <elementRef key="p"/>
            <elementRef key="pb"/>
            <elementRef key="pc"/>
            <elementRef key="person"/>
            <elementRef key="place"/>

            <elementRef key="postscript"/>
            <elementRef key="publisher"/>
            <elementRef key="pubPlace"/>
            <elementRef key="q"/>
            <elementRef key="quote"/>
            <elementRef key="ref"/>
            <elementRef key="reg"/>
            <elementRef key="relatedItem"/>
            <elementRef key="resp"/>
            <elementRef key="respStmt"/>
            <!-- allowed in bibl -->
            <elementRef key="rhyme"/>
            <!-- restored under protest -->
            <elementRef key="role"/>
            <elementRef key="roleDesc"/>
            <elementRef key="row"/>
            <elementRef key="rs"/>
            <elementRef key="s"/>
            <elementRef key="salute"/>
            <elementRef key="seg"/>
            <elementRef key="set"/>
            <elementRef key="sic"/>
            <elementRef key="signed"/>
            <elementRef key="sp"/>
            <!--elementRef key="space"/-->
            <elementRef key="speaker"/>
            <!--elementRef key="spGrp"/-->
            <elementRef key="stage"/>
            <elementRef key="subst"/>
            <elementRef key="supplied"/>
            <elementRef key="table"/>
            <elementRef key="TEI"/>
            <elementRef key="teiCorpus"/>
            <elementRef key="text"/>
            <elementRef key="time"/>
            <elementRef key="title"/>
            <elementRef key="titlePage"/>
            <elementRef key="titlePart"/>
            <elementRef key="trailer"/>
            <elementRef key="unclear"/>
            <elementRef key="w"/>
            <elementSpec module="core" ident="desc" mode="change">
              <classes mode="replace">
                <memberOf key="att.global"/>
                <memberOf key="model.descLike"/>
              </classes>
            </elementSpec>
          </specGrp>
          <specGrp xml:id="simpleelementspm">
            <p>Processing Models are defined for all textual elements. </p>
            <!-- currently missing models: body, facsimile,  surface, teiCorpus, zone -->
            <elementSpec ident="ab" mode="change">
              <model behaviour="paragraph"/>
            </elementSpec>
            <elementSpec ident="abbr" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="actor" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="add" mode="change">
              <model behaviour="inline">
                <outputRendition>color: green; text-decoration: underline;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="address" mode="change">
              <model behaviour="block">
                <outputRendition>margin-top: 2em; margin-left: 2em; margin-right: 2em;
                  margin-bottom: 2em;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="addrLine" mode="change">
              <model behaviour="block">
                <outputRendition>white-space: nowrap;</outputRendition>
              </model>
            </elementSpec>
            <!--  <elementSpec ident="addSpan" mode="change">
              <model behaviour="anchor">
                <param name="id" value="@xml:id"/>
              </model>
            </elementSpec>-->
            <elementSpec ident="am" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="anchor" mode="change">
              <model behaviour="anchor">
                <param name="id" value="@xml:id"/>
              </model>
            </elementSpec>
            <elementSpec ident="argument" mode="change">
              <model behaviour="block">
                <outputRendition>margin-bottom: 0.5em;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="author" mode="change">
              <model predicate="ancestor::teiHeader" behaviour="omit"/>
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="back" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="bibl" mode="change">
              <constraintSpec mode="add" ident="noEmptyBibl" scheme="isoschematron">
                <constraint>
                  <assert xmlns="http://purl.oclc.org/dsdl/schematron"
                    test="child::* or child::text()[normalize-space()]" role="ERROR"> Element
                    "<name/>" may not be empty. </assert>
                </constraint>
              </constraintSpec>
              <model predicate="parent::listBibl" behaviour="listItem"/>
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="biblScope" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="body" mode="change">
              <modelSequence>
                <model behaviour="index">
                  <param name="type" value="'toc'"/>
                </model>
                <model behaviour="block"/>
              </modelSequence>
            </elementSpec>
            <elementSpec ident="byline" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="c" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="castGroup" mode="change">
              <model predicate="child::*" behaviour="list">
                <desc>Insert list. </desc>
                <param name="content" value="castItem|castGroup"/>
              </model>
            </elementSpec>
            <elementSpec ident="castItem" mode="change">
              <model behaviour="listItem">
                <desc>Insert item, rendered as described in parent list rendition. </desc>
              </model>
            </elementSpec>
            <elementSpec ident="castList" mode="change">
              <model predicate="child::*" behaviour="list" useSourceRendition="true">
                <param name="content" value="castItem"/>
                <outputRendition>list-style: ordered;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="cb" mode="change">
              <model behaviour="break">
                <param name="type" value="'column'"/>
                <param name="label" value="@n"/>
              </model>
            </elementSpec>
            <elementSpec ident="cell" mode="change">
              <model behaviour="cell">
                <desc>Insert table cell. </desc>
              </model>
            </elementSpec>
            <elementSpec ident="choice" mode="change">
              <constraintSpec ident="choiceSize" scheme="isoschematron" mode="add">
                <constraint>
                  <assert xmlns="http://purl.oclc.org/dsdl/schematron" test="count(*) &gt; 1"
                    role="ERROR"> Element "<name/>" must have at least two child elements.</assert>
                </constraint>
              </constraintSpec>
              <constraintSpec ident="choiceContent" scheme="isoschematron" mode="add">
                <constraint>
                  <assert xmlns="http://purl.oclc.org/dsdl/schematron"
                    test="(tei:corr or tei:sic or tei:expan or     tei:abbr or tei:reg or tei:orig) and ((tei:corr and tei:sic) or (tei:expan     and tei:abbr) or (tei:reg and tei:orig))"
                    role="ERROR"> Element "<name/>" must have corresponding corr/sic, expand/abbr,
                    reg/orig </assert>
                </constraint>
              </constraintSpec>
              <model output="plain" predicate="sic and corr" behaviour="inline">
                <param name="content" value="corr[1]"/>
              </model>
              <model output="plain" predicate="abbr and expan" behaviour="inline">
                <param name="content" value="expan[1]"/>
              </model>
              <model output="plain" predicate="orig and reg" behaviour="inline">
                <param name="content" value="reg[1]"/>
              </model>
              <model predicate="sic and corr" behaviour="alternate">
                <param name="default" value="corr[1]"/>
                <param name="alternate" value="sic[1]"/>
              </model>
              <model predicate="abbr and expan" behaviour="alternate">
                <param name="default" value="expan[1]"/>
                <param name="alternate" value="abbr[1]"/>
              </model>
              <model predicate="orig and reg" behaviour="alternate">
                <param name="default" value="reg[1]"/>
                <param name="alternate" value="orig[1]"/>
              </model>
            </elementSpec>
            <elementSpec ident="cit" mode="change">
              <model predicate="child::quote and child::bibl" behaviour="cit">
                <desc>Insert citation </desc>
              </model>
            </elementSpec>
            <elementSpec ident="closer" mode="change">
              <model behaviour="block">
                <outputRendition>margin-top: 1em; margin-left: 1em; margin-left:
                  1em;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="code" mode="change">
              <model behaviour="inline">
                <outputRendition>font-family:monospace</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="corr" mode="change">
              <model predicate="parent::choice and count(parent::*/*) gt 1" behaviour="inline">
                <desc>simple inline, if in parent choice. </desc>
              </model>
              <model behaviour="inline">
                <outputRendition scope="before">content: '[';</outputRendition>
                <outputRendition scope="after">content: ']';</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="date" mode="change">
              <model output="print" predicate="text()" behaviour="inline"/>
              <model output="print" predicate="@when and not(text())" behaviour="inline">
                <param name="content" value="@when"/>
              </model>
              <model output="web" predicate="@when" behaviour="alternate">
                <param name="default" value="."/>
                <param name="alternate" value="@when"/>
              </model>
              <model predicate="text()" behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="dateline" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="del" mode="change">
              <model behaviour="inline">
                <outputRendition> text-decoration: line-through;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="desc" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="div" mode="change">
              <model predicate="@type='title_page'" behaviour="block">
                <outputRendition>border: 1px solid black; padding: 5px;</outputRendition>
              </model>
              <model behaviour="section" predicate="parent::body or parent::front or parent::back"/>
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="docAuthor" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="docDate" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="docEdition" mode="change">
              <!-- removed this and similar: the elements doc* are not permitted in teiHeader 
                model predicate="ancestor::teiHeader" behaviour="omit">
                <desc>Omit if located in teiHeader. </desc>
              </model-->
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="docImprint" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="docTitle" mode="change">
              <model behaviour="block" useSourceRendition="true">
                <outputRendition>font-size: larger;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="editor" mode="change">
              <model predicate="ancestor::teiHeader" behaviour="omit"/>
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="email" mode="change">
              <model behaviour="inline">
                <outputRendition>font-family:monospace</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="epigraph" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="ex" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="expan" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="figDesc" mode="change">
              <model behaviour="inline">
                <outputRendition scope="before">content: '[..';</outputRendition>
                <outputRendition scope="after">content: '..]';</outputRendition>
                <outputRendition>color: grey;font-style:italic;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="figure" mode="change">
              <model predicate="head or @rendition='simple:display'" behaviour="block"/>
              <model behaviour="inline">
                <outputRendition> display: block; border-top: solid 1pt blue; border-bottom: solid
                  1pt blue; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="floatingText" mode="change">
              <model behaviour="block">
                <outputRendition> margin: 6pt; border: solid black 1pt; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="foreign" mode="change">
              <model behaviour="inline">
                <outputRendition>font-style:italic;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="formula" mode="change">
              <model predicate="@rendition='simple:display'" behaviour="block"/>
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="front" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="fw" mode="change">
              <model predicate="ancestor::p or ancestor::ab" behaviour="inline"/>
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="g" mode="change">
              <model predicate="not(text())" behaviour="glyph">
                <param name="uri" value="@ref"/>
              </model>
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="gap" mode="change">
              <content>
                <elementRef key="desc" minOccurs="0" maxOccurs="1"/>
              </content>
              <attList>
                <attDef ident="hand" mode="delete"/>
              </attList>
              <model predicate="desc" behaviour="inline">
                <outputRendition>color: grey;</outputRendition>
              </model>
              <model predicate="@extent" behaviour="inline">
                <param name="content" value="@extent"/>
                <outputRendition scope="before">content: '[..';</outputRendition>
                <outputRendition scope="after">content: '..]';</outputRendition>
                <outputRendition>color: grey;</outputRendition>
              </model>
              <model behaviour="inline">
                <outputRendition scope="before">content: '[...]';</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="graphic" mode="change">
              <model behaviour="graphic">
                <param name="url" value="@url"/>
                <param name="width" value="@width"/>
                <param name="height" value="@height"/>
                <param name="scale" value="@scale"/>
                <param name="title" value="desc"/>
              </model>
            </elementSpec>
            <elementSpec ident="group" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="handShift" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="head" mode="change">
              <model predicate="parent::figure" behaviour="block">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
              <model predicate="parent::table" behaviour="block">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
              <model predicate="parent::lg" behaviour="block">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
              <model predicate="parent::list" behaviour="block">
                <outputRendition>font-weight: bold;</outputRendition>
              </model>
              <model predicate="parent::div" behaviour="heading">
                <param name="level" value="count(ancestor::div)"/>
              </model>
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="hi" mode="change">
              <model predicate="@rendition" behaviour="inline" useSourceRendition="true">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
              <model predicate="not(@rendition)" behaviour="inline">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="imprimatur" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="item" mode="change">
              <model behaviour="listItem"/>
            </elementSpec>
            <elementSpec ident="l" mode="change">
              <model behaviour="block" useSourceRendition="true">
                <outputRendition> margin-left: 1em; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="label" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="lb" mode="change">
              <model behaviour="break" useSourceRendition="true">
                <param name="type" value="'line'"/>
                <param name="label" value="@n"/>
              </model>
            </elementSpec>
            <elementSpec ident="lg" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="list" mode="change">
              <model predicate="@rendition" behaviour="list" useSourceRendition="true">
                <param name="content" value="item"/>
              </model>
              <model predicate="not(@rendition)" behaviour="list">
                <param name="content" value="item"/>
              </model>
            </elementSpec>
            <elementSpec ident="listBibl" mode="change">
              <model predicate="bibl" behaviour="list">
                <param name="content" value="bibl"/>
              </model>
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="measure" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="milestone" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="name" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="note" mode="change">
              <model predicate="@place" behaviour="note">
                <param name="place" value="@place"/>
                <param name="label" value="@n"/>
              </model>
              <model predicate="parent::div and not(@place)" behaviour="block">
                <outputRendition>margin-left: 10px;margin-right: 10px;
                  font-size:smaller;</outputRendition>
              </model>
              <model predicate="not(@place)" behaviour="inline">
                <outputRendition scope="before">content:" [";</outputRendition>
                <outputRendition scope="after">content:"] ";</outputRendition>
                <outputRendition>font-size:small;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="num" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="opener" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="orig" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="p" mode="change">
              <model behaviour="paragraph" useSourceRendition="true">
                <outputRendition>text-align: justify;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="pb" mode="change">
              <constraintSpec ident="pbposition" scheme="isoschematron">
                <constraint>
                  <report xmlns="http://purl.oclc.org/dsdl/schematron"
                    test="parent::*/text() and not           (preceding-sibling::text() and           following-sibling::text())"
                    >please make sure pb elements are not at the start or end of mixed content
                  </report>
                </constraint>
              </constraintSpec>
              <model behaviour="break" useSourceRendition="true">
                <param name="type" value="'page'"/>
                <param name="label"
                  value="(concat(if(@n) then concat(@n,' ') else '',if(@facs) then
                  concat('@',@facs) else ''))"/>
                <outputRendition> display: block; margin-left: 4pt; color: grey; float: right; </outputRendition>
                <outputRendition scope="before">content: '[Page ';</outputRendition>
                <outputRendition scope="after">content: ']';</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="pc" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="postscript" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="publisher" mode="change">
              <model predicate="ancestor::teiHeader" behaviour="omit">
                <desc>Omit if located in teiHeader. </desc>
              </model>
            </elementSpec>
            <elementSpec ident="pubPlace" mode="change">
              <model predicate="ancestor::teiHeader" behaviour="omit">
                <desc>Omit if located in teiHeader. </desc>
              </model>
            </elementSpec>
            <elementSpec ident="q" mode="change">
              <model predicate="l" behaviour="block" useSourceRendition="true">
                <outputRendition>margin-left: 10px; margin-right: 10px; </outputRendition>
              </model>
              <model predicate="ancestor::p or ancestor::cell" behaviour="inline"
                useSourceRendition="true">
                <outputRendition scope="before">content: '‘';</outputRendition>
                <outputRendition scope="after">content: '’';</outputRendition>
              </model>
              <model behaviour="block" useSourceRendition="true">
                <outputRendition>margin-left: 10px; margin-right: 10px; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="quote" mode="change">
              <model predicate="ancestor::p" behaviour="inline" useSourceRendition="true">
                <desc>If it is inside a paragraph then it is inline, otherwise it is block
                  level</desc>
                <outputRendition scope="before">content: '‘';</outputRendition>
                <outputRendition scope="after">content: '’';</outputRendition>
              </model>
              <model behaviour="block" useSourceRendition="true">
                <desc>If it is inside a paragraph then it is inline, otherwise it is block
                  level</desc>
                <outputRendition>margin-left: 10px; margin-right: 10px; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="ref" mode="change">
              <model behaviour="inline" predicate="not(@target)"/>
              <model predicate="not(text())" behaviour="link">
                <param name="content" value="@target"/>
                <param name="link" value="@target"/>
              </model>
              <model behaviour="link">
                <param name="link" value="@target"/>
              </model>
            </elementSpec>
            <elementSpec ident="reg" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="relatedItem" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="rhyme" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="role" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="roleDesc" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="row" mode="change">
              <model predicate="@role='label'" behaviour="row">
                <outputRendition>font-weight: bold;</outputRendition>
              </model>
              <model behaviour="row">
                <desc>Insert table row. </desc>
              </model>
            </elementSpec>
            <elementSpec ident="rs" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="s" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="salute" mode="change">
              <model predicate="parent::closer" behaviour="inline"/>
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="seg" mode="change">
              <model behaviour="inline" useSourceRendition="true"/>
            </elementSpec>
            <elementSpec ident="sic" mode="change">
              <model predicate="parent::choice and count(parent::*/*) gt 1" behaviour="inline"/>
              <model behaviour="inline">
                <outputRendition scope="before">content: '{';</outputRendition>
                <outputRendition scope="after">content: '}';</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="signed" mode="change">
              <model behaviour="block" predicate="parent::closer">
                <outputRendition> text-align: right; </outputRendition>
              </model>
              <model behaviour="inline">
                <outputRendition> font-style: italic; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="sp" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <!--elementSpec ident="space" mode="change">
              <model behaviour="inline"/>
            </elementSpec-->
            <elementSpec ident="speaker" mode="change">
              <model behaviour="block">
                <outputRendition> font-style:italic; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="spGrp" mode="change">
              <model behaviour="block"/>
            </elementSpec>
            <elementSpec ident="stage" mode="change">
              <model behaviour="block">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="subst" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="supplied" mode="change">
              <model predicate="parent::choice" behaviour="inline"/>
              <model predicate="@reason='damage'" behaviour="inline">
                <outputRendition scope="before">content:"&lt;";</outputRendition>
                <outputRendition scope="after">content:"&gt;";</outputRendition>
              </model>
              <model predicate="@reason='illegible' or not(@reason)" behaviour="inline">
                <outputRendition scope="before">content:"[";</outputRendition>
                <outputRendition scope="after">content:"]";</outputRendition>
              </model>
              <model predicate="@reason='omitted'" behaviour="inline">
                <outputRendition scope="before">content:"(";</outputRendition>
                <outputRendition scope="after">content:")";</outputRendition>
              </model>
              <model behaviour="inline">
                <outputRendition scope="before">content:"{";</outputRendition>
                <outputRendition scope="after">content:"}";</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="table" mode="change">
              <model behaviour="table">
                <outputRendition> font-size: smaller; background-color: #F0F0F0; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="fileDesc" mode="change">
              <model behaviour="title">
                <param name="content" value="titleStmt"/>
              </model>
            </elementSpec>
            <elementSpec ident="profileDesc" mode="change">
              <model behaviour="omit"/>
            </elementSpec>
            <elementSpec ident="revisionDesc" mode="change">
              <model behaviour="omit"/>
            </elementSpec>
            <elementSpec ident="encodingDesc" mode="change">
              <model behaviour="omit"/>
            </elementSpec>
            <elementSpec ident="teiHeader" mode="change">
              <attList>
                <attDef ident="type" mode="delete"/>
              </attList>
              <!-- remove deprecated attribute -->
              <model behaviour="metadata"/>

            </elementSpec>
            <elementSpec ident="TEI" mode="change">
              <model behaviour="document"/>
            </elementSpec>
            <elementSpec ident="text" mode="change">
              <model behaviour="body">
                <outputRendition> max-width: 80%; margin: auto; font-family: Verdana, Tahoma,
                  Geneva, Arial, Helvetica, sans-serif; </outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="time" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
            <elementSpec ident="title" mode="change">
              <modelSequence predicate="parent::titleStmt/parent::fileDesc">
                <model predicate="preceding-sibling::title" behaviour="text">
                  <param name="content" value="' — '"/>
                </model>
                <model behaviour="inline">
                  <outputRendition>color: red; font-size: 2em;</outputRendition>
                </model>
              </modelSequence>
              <model predicate="not(@level) and parent::bibl" behaviour="inline"/>
              <modelSequence predicate="@level='m' or not(@level)">
                <model behaviour="inline">
                  <outputRendition>font-style: italic;</outputRendition>
                </model>
                <!--     <model predicate="ancestor::biblStruct or       ancestor::biblFull" behaviour="text">
           -->
                <model predicate="ancestor::biblFull" behaviour="text">
                  <param name="content" value="', '"/>
                </model>
              </modelSequence>
              <modelSequence predicate="@level='s' or @level='j'">
                <model behaviour="inline">
                  <outputRendition>font-style: italic;</outputRendition>
                </model>
                <model predicate="following-sibling::* and     (  ancestor::biblFull)"
                  behaviour="text">
                  <param name="content" value="', '"/>
                </model>
              </modelSequence>
              <modelSequence predicate="@level='u' or @level='a'">
                <model behaviour="inline">
                  <outputRendition>font-style: italic;</outputRendition>
                </model>
                <model predicate="following-sibling::* and     (    ancestor::biblFull)"
                  behaviour="text">
                  <param name="content" value="'. '"/>
                </model>
              </modelSequence>
              <model behaviour="inline">
                <outputRendition>font-style: italic;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="titlePage" mode="change">
              <model behaviour="block" useSourceRendition="true">
                <outputRendition> text-align: center;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="titlePart" mode="change">
              <model behaviour="block" useSourceRendition="true"/>
            </elementSpec>
            <elementSpec ident="trailer" mode="change">
              <model behaviour="block">
                <outputRendition>color: green;</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="unclear" mode="change">
              <attList>
                <attDef ident="hand" mode="delete"/>
              </attList>
              <model behaviour="inline">
                <outputRendition scope="after">content: ' [?] ';</outputRendition>
              </model>
            </elementSpec>
            <elementSpec ident="w" mode="change">
              <model behaviour="inline"/>
            </elementSpec>
          </specGrp>
          <specGrp xml:id="simplechanges">
            <p>Constrained value lists are added for some elements</p>
            <elementSpec ident="formula" mode="change">
              <attList>
                <attDef ident="notation" mode="change">
                  <valList mode="add" type="semi">
                    <valItem ident="TeX">
                      <desc>Using TeX or LaTeX notation</desc>
                    </valItem>
                  </valList>
                </attDef>
              </attList>
            </elementSpec>
            <elementSpec ident="name" mode="change">
              <attList>
                <attDef ident="type" mode="change">
                  <valList mode="add" type="closed">
                    <valItem ident="person"/>
                    <valItem ident="forename"/>
                    <valItem ident="surname"/>
                    <valItem ident="personGenName"/>
                    <valItem ident="personRoleName"/>
                    <valItem ident="personAddName"/>
                    <valItem ident="nameLink"/>
                    <valItem ident="org"/>
                    <valItem ident="country"/>
                    <valItem ident="placeGeog"/>
                    <valItem ident="place"/>
                  </valList>
                </attDef>
              </attList>
            </elementSpec>
            <elementSpec ident="cell" mode="change">
              <attList>
                <attDef ident="role" mode="change">
                  <valList mode="add" type="closed">
                    <valItem ident="data">
                      <desc>data cell</desc>
                    </valItem>
                    <valItem ident="label">
                      <desc>label cell</desc>
                    </valItem>
                    <valItem ident="sum">
                      <desc>row or column sum data</desc>
                    </valItem>
                    <valItem ident="total">
                      <desc>table total data</desc>
                    </valItem>
                  </valList>
                </attDef>
              </attList>
            </elementSpec>
            <elementSpec ident="row" mode="change">
              <attList>
                <attDef ident="role" mode="change">
                  <valList mode="add" type="closed">
                    <valItem ident="data">
                      <desc>data cell</desc>
                    </valItem>
                    <valItem ident="label">
                      <desc>label cell</desc>
                    </valItem>
                    <valItem ident="sum">
                      <desc>row or column sum data</desc>
                    </valItem>
                    <valItem ident="total">
                      <desc>table total data</desc>
                    </valItem>
                  </valList>
                </attDef>
              </attList>
            </elementSpec>
          </specGrp>

        </div>
      </div>
    </body>
  </text>
</TEI>