Text only | Skip links
Skip links||IT Services, University of Oxford

1. General linking, segmentation and alignment

In our encoded texts, we expect to be able to
  • put in simple links between sections of text, and point to external resources
  • link text elements to pages images;
  • represent correspondence or alignment among groups of text elements
  • synchronize elements of a text, representing temporal correspondences and alignments among text elements
  • specify that one text element is identical to or a copy of another
  • aggregate possibly noncontinguous elements
  • specify that different elements are alternatives to one another and to express preferences among the alternatives
  • store markup separately from the the data it describes
Some of these techniques we have already seen in the basic TEI work, and the discussion of names.

1.1. Simple linking

The core TEI <ptr> and <ref> elements let you do the point to point linking we are used to on web pages, relying on XML IDs for internal links:
<p>Wikipedia has a a good starter page on
<ref
   target="http://en.wikipedia.org/wiki/Maneki_Neko">
waving
   cats</ref>, with links to more esoteric resources; our own
information is section <ref target="#cats">3</ref>. Here is a video of mine:
<ref target="../Graphics/cat.avi">
  <graphic width="60pxrend="righturl="../Graphics/cat.jpg"/>
 </ref>
</p>
<div xml:id="cats">
 <head>Cats</head>
 <p>Lots of them</p>
</div>

1.2. Underlying assumptions of our linking

  • Use W3C identifying, pointing and linking mechanisms where possible
  • Use xml:id to identify an element directly
  • Use XPointer to point to elements that do not have an xml:id

1.3. Complex pointing

The standard URI scheme allows for pointing
  • to documents other than the current document
  • to a particular element in a document other than the current document using its xml:id;
but we also need to point
  • to a particular element using its position in the XML element tree (standard XPointer schemes)
  • at arbitrary content in any XML document using TEI-defined XPointer schemes

1.4. W3C XPointer schemes

element
Identify elements by position within parent, recursively.
xpointer
The rich scheme including XPaths and ranges described in the XPointer Recommendation
xmlns
Bind a prefix for use in subsequent pointer parts e.g. xmlns(xs=http://www.w3.org/2001/XMLSchema)

1.5. Text for XPointer examples

<text>
 <body>
<!-- seven divs here -->
  <div xml:id="lastterm">
   <p></p>
   <p></p>
   <p>
    <emph>'But'</emph>, said <name key="Stalky">Stalky</name>,
       ‘come to think of it, we've done more giddy jesting
       with the Sixth since we've been passed over than any
       one else in the last seven years.’</p>
  </div>
 </body>
</text>

1.6. Examples for XPointer schemes

element():
<ptr target="stalky.xml#element(lastterm)"/>
<ptr target="stalky.xml#element(1/1/8)"/>
xpointer() and xmlns():
<ptr
  target="stalky.xml#xmlns(t=http://www.tei-c.org/ns/1.0) xpointer(/t:TEI/t:text/t:body/t:div[8])"/>
<ptr
  target="stalky.xml#xmlns(t=http://www.tei-c.org/ns/1.0) xpointer(/t:TEI/t:text//t:p[t:name[.='Stalky']])"/>

1.7. A daily use for XPointer

The W3C XInclude specification is a good way to write composite documents; the <include> element's href attribute allows for XPointers:

<div>
 <p><xi:include href="stalky.xml#
   xmlns(t=http://www.tei-c.org/ns/1.0)
   xpointer(/t:TEI/t:text//t:p[t:name[.='Beetle']])"/></p>
</div>

1.8. The TEI linking module

The linking module provides a generic <link> to let you specify a point to point relationship between two or more elements, using multiple values for the target attribute:
<quote>
 <p xml:id="report1">"In our report of the wedding of
 <persName>Mr. Lee Kwee Law</persName> to <persName>Miss Chan Siew
     Cheen</persName> we inadvertently left out the following, who also
   sent presents:——"—<title>Straits Echo.</title>
 </p>
</quote>
<p xml:id="comment1">And then they inadvertently left them
out again.</p>
<link targets="#report1 #comment1"/>
Note that this is establishing a connection, not a direction.

1.9. Groups of links

<linkGrp> is provided to group together sets of <link>s. In the following example, it allows for stand-off notes, and characterisation of those notes:
<l xml:id="l2.79">A place there is, betwixt earth, air and seas</l>
<l xml:id="l2.80">Where from Ambrosia, Jove retires for ease.</l>
<l xml:id="l2.88">Sign'd with that Ichor which from Gods distills.</l>
<note xml:id="n2.79">
 <bibl>Ovid Met. 12.</bibl>
 <quote xml:lang="la">
  <l>Orbe locus media est,
     inter terrasq; fretumq;</l>
  <l>Cœlestesq; plagas —</l>
 </quote>
</note>
<note xml:id="n2.88"> Alludes to <bibl>Homer, Iliad 5</bibl>
</note>
<linkGrp type="imitationnotes">
 <link targets="#n2.79 #l2.79"/>
 <link targets="#n2.88 #l2.88"/>
</linkGrp>

1.10. Segmenting text, and marking arbitrary points within documents

The linking module adds three useful new elements:
<ab>
marks an block of text with no special semantic interpretation
<seg>
marks a range of text with no special semantic interpretation
<anchor>
marks an arbitrary point in the text
The first two have helpful type and subtype attributes.

1.11. Marking points

<anchor> is comparable to an HTML anchor:
<p>He was merely working up to a peroration,
and the boys knew it; but McTurk cut through the frothing sentence, the others
echoing:</p>
<p><anchor xml:id="MTa"/>I appeal to the Head,
sir.’</p>
<p>‘I appeal to the head, sir.’</p>
<p>‘I appeal to the Head, sir.’<anchor xml:id="Sa"/>
</p>
<p>It was their unquestioned right. Drunkenness meant expulsion after a
public flogging. They had been accused of it. The case was the Head's, and the Head's
alone.</p>
<span from="#MTato="#Sa">the verbal appeal</span>

1.12. Anonymous blocks

In this inscription, there are separate lines, but they are not poetry, or paragraphs, so we isolate them with <ab> (or if we didn't want to encapsulate them we could use <lb/>):
<div>
 <ab>JOSEPH STORY</ab>
 <ab>ONLY SON OF</ab>
 <ab>WILLILAM W. AND EMELYN STORY</ab>
 <ab>BORN MAY 3rd 1847</ab>
 <ab>AT BOSTON U.S.A</ab>
 <ab>DIED NOV. 23rd 1853</ab>
 <ab>AT ROME</ab>
</div>

1.13. Segments

There are more specific elements elsewhere in the TEI for marking sentences, words and characters, but sometimes we need to mark an arbitrary span, using <seg>:

<q>Don't say <q>
  <seg type="stutter">I-I-I</seg>'m afraid,</q> Melvin, just say <q>I'm afraid.</q>
</q>

1.14. Correspondence and alignment

First, consider the representation of a manuscript page:

1.15. Manuscript Text

<ab xml:id="N6">
 <lb/>and hat hire don in obedience ðe cnoweð hire manere
<lb/>and hire strencðe. he mai ðe vttre riwle chaungen efter
<lb/>wisdom alse he isihð te inre mai beon best iholden.
<anchor xml:id="N_6"/>
 <lb/>Non ancre bi mine rede ne schal makien professiun.
<lb/>þet is. bihoten ase hest.
</ab>

1.16. Correspondence and alignment (cont.)

Now let us look at an edited version and a translation:
<p xml:id="edited_6">Nan ancre bi mi read ne schal makien professiun—þet is, bihaten ase
heast—bute þreo þinges, þet beoð obedience, chastete, ant
stude-steaðeluestnesse
<!-- ... -->
</p>
<p xml:id="translated_6">My advice is that no anchoress should make
profession—that is, bind herself to a vow—of more than three things,
which are obedience, chastity, and stability of abode
<!-- ... -->
</p>

1.17. Correspondence and alignment (cont.)

We can express a relationship between the texts as follows:
<linkGrp type="translations">
 <link targets="#edited_6 #translated_6"/>
<!-- … -->
</linkGrp>
<linkGrp type="editions">
 <link targets="#N-f2r #N6"/>
<!-- … -->
</linkGrp>
meaning ‘this paragraph in the translated edition corresponds to text at that anchor in the original’.

There are many other ways of dealing with material like this!

1.18. Synchronizing time-based material

If you are linking together sequences which are aligned by time, there is a special stand-off linking element <when>, grouped inside a <timeline>. It has attributes:
absolute
an absolute time for the event
interval
the length of the gap since the last event
unit
the unit of time in which the interval value is expressed
since
a link to the previous event
<timeline xml:id="tl1origin="#w0unit="ms">
 <when xml:id="w0absolute="11:30:00"/>
 <when xml:id="w1interval="unknownsince="#w0"/>
 <when xml:id="w2interval="100since="#w1"/>
 <when xml:id="w3interval="200since="#w2"/>
 <when xml:id="w4interval="150since="#w3"/>
</timeline>

These <when> objects can be used in a <link> to associate points in time with points in the text.

1.19. Marking interpretations

The <interp> element is used to store an interpretation of some kind about a text. It can appear anywhere and either
  • points to text segments to which it applies, using the inst attribute
or
  • is pointed at from text segments to which it applies, using the ana attribute

For grouping sets of similar interpretations, we can use <interpGrp>

1.20. Example of marking simple interpretation

A few days ago the Crown Prince of Schlossrattenheim had an accident with his aeroplane, which overturned near Schutzmeer. Fortunately his Royal Highness fell on a retired Wuerst-haendler who was walking on the beach.

The Crown Prince's devotion to his beloved subjects is well known, and this tactful deed was only another instance of it.

<p xml:id="cp1ana="#IR">The Crown Prince's devotion to his beloved
subjects is well known, and this tactful deed was only
another instance of it.</p>
<interp xml:id="IR">Irony</interp>

1.21. Segmentation for part of speech analysis

Exeter College Oxford which has just celebrated its six hundredth anniversary is not the only college which bears the same name as that of a city

<w ana="#NP0">Exeter</w>
<w ana="#NN1">College</w>
<w ana="#NP0">Oxford</w>
<w ana="#DTQ">which</w>
<w ana="#VHZ">has</w>
<w ana="#AV0">just</w>
<w ana="#VVN">celebrated</w>
<w ana="#DPS">its</w>
<w ana="#CRD">six</w>
<w ana="#ORD">hundredth</w>
<w ana="#NN1">anniversary</w>
<w ana="#VBZ">is</w>
<w ana="#XX0">not</w>
<w ana="#AT0">the</w>
<w ana="#AJ0">only</w>
<w ana="#NN1">college</w>
<w ana="#DTQ">which</w>
<w ana="#VVZ">bears</w>
<w ana="#AT0">the</w>
<w ana="#DT0">same</w>
<w ana="#NN1">name</w>
<w ana="#CJS">as</w>
<w ana="#DT0">that</w>
<w ana="#PRF">of</w>
<w ana="#AT0">a</w>
<w ana="#NN1">city</w>

1.22. Interpretation group

<interpGrp type="POS">
 <interp xml:id="AJ0">adjective (unmarked) (e.g. GOOD, OLD)</interp>
 <interp xml:id="AT0">article (e.g. THE, A, AN)</interp>
 <interp xml:id="AV0">adverb (unmarked) (e.g. OFTEN, WELL, LONGER, FURTHEST)</interp>
 <interp xml:id="CJS">subordinating conjunction (e.g. ALTHOUGH, WHEN)</interp>
 <interp xml:id="CRD">cardinal numeral (e.g. 3, FIFTY-FIVE, 6609) (excl ONE)</interp>
 <interp xml:id="DPS">possessive determiner form (e.g. YOUR, THEIR)</interp>
 <interp xml:id="DT0">general determiner (e.g. THESE, SOME)</interp>
 <interp xml:id="DTQ">wh-determiner (e.g. WHOSE, WHICH)</interp>
 <interp xml:id="NN1">singular noun (e.g. PENCIL, GOOSE)</interp>
 <interp xml:id="NN2">plural noun (e.g. PENCILS, GEESE)</interp>
 <interp xml:id="NP0">proper noun (e.g. LONDON, MICHAEL, MARS)</interp>
 <interp xml:id="NULL">the null tag (for items not to be tagged)</interp>
 <interp xml:id="ORD">ordinal (e.g. SIXTH, 77TH, LAST)</interp>
 <interp xml:id="PRF">the preposition OF</interp>
 <interp xml:id="VBZ">-s form of the verb "BE", i.e. IS, 'S</interp>
 <interp xml:id="VHZ">-s form of the verb "HAVE", i.e. HAS, 'S</interp>
 <interp xml:id="VVN">past participle form of lex. verb (e.g. TAKEN, LIVED)</interp>
 <interp xml:id="VVZ">-s form of lexical verb (e.g. TAKES, LIVES)</interp>
 <interp xml:id="XX0">the negative NOT or N'T</interp>
</interpGrp>

1.23. Aggregating non-contiguous elements

The <join> element is used like <link>, pointing to 2 or more identified fragments of text. It claims that they could be joined to create a new virtual element (the result attribute). <joinGroup> is provided to aggregate <join>s.

1.24. <join> example

<lg>
 <l>
  <seg xml:id="L1">E</seg>lizabeth it is in vain you say</l>
 <l>"<seg xml:id="L2">L</seg>ove not" — thou sayest it in so sweet a way:</l>
 <l>
  <seg xml:id="L3">I</seg>n vain those words from thee or L.E.L.</l>
 <l>
  <seg xml:id="L4">Z</seg>antippe's talents had enforced so well:</l>
 <l>
  <seg xml:id="L5">A</seg>h! if that language from thy heart arise,</l>
 <l>
  <seg xml:id="L6">B</seg>reath it less gently forth — and veil thine eyes.</l>
 <l>
  <seg xml:id="L7">E</seg>ndymion, recollect, when Luna tried</l>
 <l>
  <seg xml:id="L8">T</seg>o cure his love — was cured of all beside —</l>
 <l>
  <seg xml:id="L9">H</seg>is follie — pride — and passion — for he died.</l>
</lg>
<p>
 <join
   targets="#L1 #L2 #L3 #L4 #L5 #L6 #L7 #L8 #L9result="name">

  <desc>The beloved's name</desc>
 </join>
</p>
(from Edgar Allan Poe).

2. A special case of linking: facsimiles

Increasingly people want to do not just 'text' editions but text editions with facing page (or otherwise linked) facsimile images. Indeed, some people want to just have images and create and electronic facsimile (perhaps with a view to later eventual transcription). The <facsimile> element (a sibling of <teiHeader> and <text> is provided to accommodate this desire.

2.1. Digital Facsimiles

  • <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text
  • <surface> defines a written surface in terms of a rectangular coordinate space
    • start points to an element which encodes the starting position of the text
  • <zone> defines a rectangular area contained within a <surface> element
  • Global facs (facsimile) points directly to an image, or to a part of a facsimile element which corresponds with this element.

2.2. Simplest case: 1:1 mapping with facs

If a digital text contains one image per page or column (or similar unit), and no more complex mapping between text and image is envisaged, then the facs attribute may be used to point directly to a graphic resource.
<text>
 <body>
  <pb facs="147_13.jpgn="13"/>
  <div>
   <head>ESSENCE OF PARLIAMENT.</head>
   <p>
<!-- Page 13 continues -->
   </p>
   <pb facs="147_14.jpgn="14"/>
   <p>Business done. -- The Commons still...
<!-- Page 14 continues -->
   </p>
  </div>
 </body>
</text>

2.3. Using facs in conjunction with <facsimile>, <surface>, and <zone>

Using these attributes and elements together enables an editor to
  • associate multiple images with each page
  • record arbitrary planar coordinates of textual elements on any kind of surface and link such elements to digital facsimile images of them

2.4. <facsimile>

The facsimile element is used to represent a digital facsimile. It appears within a TEI document along with, or instead of, the text element introduced in section 5 Default Text Structure. When this module is selected therefore, a legal TEI document may thus comprise any of the following:
  • a TEI Header and a text element
  • a TEI Header and a facsimile element
  • a TEI Header, a facsimile element, and a text element

2.5. <facsimile> Example in Context

<TEI>
 <teiHeader>
<!-- teiHeader here -->
 </teiHeader>
 <facsimile>
  <graphic url="147_13.jpgxml:id="p1"/>
  <graphic url="147_14.jpgxml:id="p2"/>
  <graphic url="147_15.jpgxml:id="p3"/>
 </facsimile>
 <text>
  <body>
<!-- body here -->
  </body>
 </text>
</TEI>

2.6. <surface>

The <surface> element may be used to indicate that there are two image files corresponding with the same area of the work:
<facsimile>
 <surface>
  <graphic url="147_13.jpg"/>
  <graphic url="147_13-huge.jpg"/>
 </surface>
 <graphic url="147_14.jpg"/>
 <graphic url="147_15.jpg"/>
 <graphic url="147_16.jpg"/>
</facsimile>

2.7. dimensions

The actual dimensions of the object represented are not documented by the surface element; instead, the surface is located within an abstract coordinate space, which is defined by the following attributes, supplied by the att.coordinated class:
  • ulx gives the x coordinate value for the upper left corner of a rectangular space
  • uly gives the y coordinate value for the upper left corner of a rectangular space.
  • lrx gives the x coordinate value for the lower right corner of a rectangular space.
  • lry gives the y coordinate value for the lower right corner of a rectangular space.

2.8. Example drawing rectangles

2.9. <surface> Example

<facsimile>
 <surface
   ulx="0"
   uly="0"
   lrx="700"
   lry="1000">

<!-- ... -->
 </surface>
</facsimile>

2.10. <zone> in <surface>

To describe the whole image, we will also need to define a zone of interest which represents an area inside this surface. This zone of interest can be defined by a <zone> element, within which we can place the <graphic>:

<facsimile>
 <surface
   ulx="0"
   uly="0"
   lrx="993"
   lry="1639">

  <zone
    ulx="93"
    uly="681"
    lrx="967"
    lry="1568">

   <graphic url="147_13.jpg"/>
  </zone>
 </surface>
</facsimile>

2.11. <desc>

The <desc> element may also be used within either <surface> or <zone> to provide some further information about the area being defined.

2.12. <desc> Example

<facsimile>
 <surface
   ulx="0"
   uly="0"
   lrx="993"
   lry="1639">

  <desc>Printed page</desc>
  <zone
    ulx="96"
    uly="89"
    lrx="750"
    lry="657">

   <desc>Cartoon</desc>
   <graphic url="147_13.jpg"/>
  </zone>
  <zone
    ulx="95"
    uly="681"
    lrx="990"
    lry="1568">

   <desc>Text section</desc>
   <graphic url="147_13.jpg"/>
  </zone>
 </surface>
</facsimile>

2.13. More uses for <zone>

In addition to acting as a container for <graphic> elements, <zone> elements may also be used to select parts of each surface for analytical purposes.

<facsimile>
 <surface
   ulx="0"
   uly="0"
   lrx="993"
   lry="1639">

  <desc>main text</desc>
  <zone
    ulx="393"
    uly="681"
    lrx="967"
    lry="890">

   <desc>Cartoon</desc>
   <graphic url="147_13.jpg"/>
  </zone>
  <zone
    ulx="507"
    uly="596"
    lrx="704"
    lry="768">

   <desc>Artist's signature</desc>
  </zone>
 </surface>
</facsimile>

2.14. Linking transcription and facsimile

  1. give each relevant part of the facsimile an identifier
  2. using the facs attribute, point from the transcription into the <facsimile>

2.15. Linking transcription and facsimile: <facsimile>

<facsimile>
 <surface
   ulx="0"
   uly="0"
   lrx="993"
   lry="1639">

  <graphic url="147_10.jpg"/>
  <zone
    xml:id="cartoonfacs"
    ulx="96"
    uly="89"
    lrx="950"
    lry="657">

   <desc>Cartoon</desc>
  </zone>
  <zone
    xml:id="textfacs"
    ulx="93"
    uly="681"
    lrx="967"
    lry="1568">

   <desc>Text section</desc>
  </zone>
 </surface>
</facsimile>

2.16. Linking transcription and facsimile: text

<body>
 <pb n="p10"/>
 <div facs="#cartoonfacs">
  <figure>
<!-- cartoon info here -->
  </figure>
 </div>
 <div facs="#textfacs">
  <head>THE WALKERS</head>
  <lg>
   <l>There were eight pretty walkers...</l>
  </lg>
 </div>
</body>

2.17. Pointing from <facsimile> to transcription with start attribute

It is also possible to point in the other direction, from a <surface> or <zone> to the corresponding text. This is the function of the start attribute, which supplies the identifier of the element containing the transcribed text found within the <surface> or <zone> concerned.

2.18. start attribute example: <facsimile>

<facsimile>
 <surface
   start="#p10"
   ulx="0"
   uly="0"
   lrx="993"
   lry="1639">

  <zone
    xml:id="cartoonfacs2"
    ulx="96"
    uly="89"
    lrx="950"
    lry="657">

   <desc>Cartoon</desc>
   <graphic url="147_10.jpg"/>
  </zone>
 </surface>
</facsimile>

2.19. start attribute example: text

<body>
 <pb xml:id="p10n="10"/>
 <div>
  <figure>
<!-- cartoon info here -->
  </figure>
 </div>
 <div>
  <head>THE WALKERS</head>
  <lg>
   <l>There were eight pretty walkers...</l>
  </lg>
 </div>
</body>

2.20. Gravestone Example: <facsimile>

<facsimile>
 <surface
   xml:id="grave"
   ulx="0"
   uly="0"
   lrx="355"
   lry="678">

  <graphic url="gravestone-cropped.jpg"/>
  <zone
    ulx="83"
    uly="223"
    lrx="272"
    lry="256"
    xml:id="line1"/>

  <zone
    ulx="92"
    uly="251"
    lrx="256"
    lry="282"
    xml:id="line2"/>

  <zone
    ulx="21"
    uly="281"
    lrx="330"
    lry="308"
    xml:id="line3"/>

  <zone
    ulx="36"
    uly="306"
    lrx="320"
    lry="332"
    xml:id="line4"/>

  <zone
    ulx="85"
    uly="535"
    lrx="249"
    lry="556"
    xml:id="line5"/>

  <zone
    ulx="97"
    uly="556"
    lrx="241"
    lry="576"
    xml:id="line6"/>

  <zone
    ulx="58"
    uly="577"
    lrx="281"
    lry="595"
    xml:id="line7"/>

  <zone
    ulx="68"
    uly="595"
    lrx="271"
    lry="613"
    xml:id="line8"/>

 </surface>
</facsimile>

2.21. Gravestone Example: text

<div facs="#grave">
 <p>Private Moulds' gravestone</p>
 <div>
  <ab>
   <s facs="#line1">12851 PRIVATE</s>
   <lb/>
   <s facs="#line2">H. MOULDS</s>
   <lb/>
   <s facs="#line3">NORTHAMPTONSHIRE REGT.</s>
   <lb/>
   <s facs="#line4">23RD JULY 1916 AGED 21</s>
  </ab>
  <ab>
   <s facs="#line5">LOVING SON OF </s>
   <lb/>
   <s facs="#line6">MRS MOULDS</s>
   <lb/>
   <s facs="#line7">PETERBORO, ENGLAND</s>
   <lb/>
   <s facs="#line8">FOR EVER WITH US</s>
   <lb/>
  </ab>
 </div>
</div>

3. Introducing the Image Markup Tool

3.1. IMT: main window

IMTmain window:

3.2. IMT: annotation window

IMTannotation window:

3.3. Loading and Using Images

Loading Images:
  • File / New: starts new image
  • File / Import: option of keeping existing annotations and applying to new image
Using Images:
  • Zooming: scale toolbar box, or Control + mousewheel
  • Scrolling: mousewheel (up/down); Shift + mousewheel (left-right), or scrollbars

3.4. Defining and Editing Categories

  • IMT makes you sort your annotations into categories (but which and how many are up to you!)
  • You use the 'category manager' to create categories where you can define:
    • an xml:id for identification
    • a title/description of the category
    • a colour for the annotation lines on the image
    • a shape: rectangle (default and only one used in web view), ellipse, cross or spiral

3.5. Adding and Deleting Annotation Areas

  • Click on 'Annotations / New annotation' (or button), and a resizable shape will appear on the image
  • You can resize and move the area with the mouse
  • The area, when selected, will have a white bounding box -- otherwise it will be the colour of its category
  • The shape depends on the defined shape in the category you've chosen
  • To delete, select it and then click on 'Annotations / Delete annotation' or button -- the associated annotations will also be deleted

3.6. Adding Annotation Text

  • When an annotation is added, it has the last category you used
  • You can change this to any other category
  • You can provide an annotation title (stored as tei:head)
  • You can provide some text (any tei:div content, tei:p default)
  • You can change the generated xml:id with the ID button

3.7. Hiding and Showing Annotations

  • You can hide and show annotations in the annotations window
  • You can select either individual annotations to display
  • Or you can choose not to display a whole category of annotations
  • This is useful when working with lots of overlapping annotations

3.8. Creating a "Web View"

  • As an example IMT produces a 'web view'
  • This includes a web page, with slightly shrunk image, where your annotations appear as mouse-over outlines with boxes displaying the annotations
  • Double-clicking on an annotation area produces a zoomed in version of the image for that area
  • This is really just a proofing tool, but has been used by some as the basis for annotated facsimiles

3.9. Punch

3.10. Two examples

Since Punch has so many cartoons, mixed in with text, the output from the IMT can be used with great effect. For example: http://tei.oucs.ox.ac.uk/Oxford/2009-04-galway/Punch-IMT/p15-imt.xhtml and http://www.rch.uky.edu/Pembroke25/IMT/3r/3r.htm uses a customised IMT Web View to provide both line-by-line transcriptions and editorial notes.

3.11. IMT Schemas

It is important quickly to note that IMT XML files are pure TEI P5 XML. The RELAX NG schema is available with the installed program, as is the TEI ODD file that Roma uses to generate this schema.

4. Conclusions

The linking and transcr modules provides a wide range of tools to let you describe relationships between parts of your text. If you use these techniques, remember:
  • You should work out a naming scheme to assign ID attributes. You will need a lot of them
  • There are often several ways to do things; use the more specialized markup when you can to make it easier for others to read. Don't rely on type attributes with undefined meanings everywhere
  • Control your vocabulary for token attributes like type
  • The TEI only takes you as far as markup. Implementing all this to make a fancy interactive text exploration web site may be a lot of work.


TEI@Oxford. Date: 2010-07
Copyright University of Oxford