LegacyFacsimileMarkup
This page includes some examples of different approaches for facsimile (image-based) markup.
Contents
Draft Recommendations for TEI Digital Facsimiles
http://users.ox.ac.uk/~lou/wip/digfax.html
This document, authored by Richard Gartner and Lou Burnard and last updated in 2001, outlines ways to use TEI to represent three types of digital objects:
- complete digital transcriptions of the content of manuscript or print originals (possibly including illustrations as well as text)
- collections of digitized page images (digital facsimiles) intended for use as surrogates for complete manuscript or print originals
- digital objects (digital editions) combining both page facsimiles and transcriptions, possibly also including layers of editorial annotation
The authors attempt to address these areas of concern:
- the need to distinguish images of a manuscript or print source from images located within it;
- the need to support multiple formats of a single image;
- the need to associate metadata at different levels (e.g. collection level, item level);
- the need to associate transcription and facsimile in a standard way;
- the need to define practices which can be used equally well in both SGML and XML environments;
- the desire to avoid special purpose rules which assume nonstandard or ad hoc processing rules.
Case 1: Transcription
Updated to cite chapters in P5:
The content of a transcription should be marked up as a single <TEI> element using the standard TEI elements <text>, <body>,
Follow the Guidelines chapters 18 Transcription of Primary Resources and 13 Manuscript Description.
If the source contains "significant illustrative material", use <figure> (and children) from Guidelines chapter 22 Tables, Formulae, and Graphics to insert illustrations in their proper location in the transcript.
<lb n="12"/>feond mid his geferum eallum. Feollon þa ufon
<lb n="13"/>of heofnum þurhlonge swa þreo niht and da
<lb n="14"/>gas, þa englas of heofnum on helle, and heo ealle
<lb n="15"/>forsceop drihten to deoflum.
<figure>
<head>Fall of the Angels</head>
<figDesc>Above, God, cross-nimbed, beardless, and holding a closed book, accompanied by three angels,
turns and gestures toward three angels on the left, one of whom (Lucifer?) holds a palm frond
...</figDesc>
</figure>
<pb n="17"/>
Case 2: Digital Facsimile
Should be marked as a separate <TEI> element. TEI structural tags may be used, but need not be, especially if differences between textual structure and physical structure cause overlap.
Each distinct image making up the facsimile should be encoded as a <figure> element, arranged in the normal reading sequence of the facsimile. The appropriate milestone element (<pb/> or <cb/> should be used at the appropriate place in the facsimile.
<pb n="16"/>
<figure n="16">
<figDesc>[Page 16: 15 lines of text followed by image of "Fall of Angels" (Ohlgren 16.11)]</figDesc>
</figure>
<pb n="17"/>
<figure n="17">
<figDesc>[Page 17: 15 lines of text followed by image of "Fall of Angels" (Ohlgren 16.12)]</figDesc>
</figure>
<figure> elements may be self-nested to show that one image logically contains others (in cases where two image fit together to form one larger image).
<figure n="16">
<figDesc>
<figure>
<figDesc>[Page 16: 15 lines of text (detail of upper part)]</figDesc>
</figure>
<figure>
<figDesc>[Page 16: Image of "Fall of Angels" (Ohlgren 16.11) (detail of lower part)</figDesc>
</figure>
</figDesc>
</figure>
3: Techniques for Referencing Images
Recommends declaring the file containing the image as an external entity and then referencing that entity using the "entity" attribute in <figure>. This approach depends on the use of the DTD (no longer practical given the TEI's move towards using the RelaxNG schema), and relies on an attribute that is no longer included in P5.
In TEI P5 there are also two new elements, <graphic> and <binaryObject> which may be used to represent image references or images respectively. These permit the encoding of figures containing multiple images, for example. The <graphic> element has a "url" attribute which enables the association of a <figure> with its corresponding image file. The recommendations in Gartner and Burnard need to be revised substantially in this respect.
<pb n="16"/>
<figure n="16">
<figDesc>[Page 16: 15 lines of text followed by image of "Fall of Angels" (Ohlgren 16.11)]</figDesc>
<graphic url="http://image.ox.ac.uk/images/bodleian/msjunius11/16.jpg"/>
</figure>
<pb n="17"/>
<figure n="17" url="http://image.ox.ac.uk/images/bodleian/msjunius11/17.jpg">
<figDesc>[Page 17: 15 lines of text followed by image of "Fall of Angels" (Ohlgren 16.12)]</figDesc>
<graphic url="http://image.ox.ac.uk/images/bodleian/msjunius11/17.jpg"/>
</figure>
This approach is simple, though it is not practical if one has multiple images of the same page in various resolutions
<figure> <head>Figure One: The View from the Bridge</head> <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc> <graphic url="http://www.somewhere.eu/fig1.png" scale="0.5"/> </figure>
Other options mentioned in the recommendation: Xlink or Xinclude.
4: Aligning transcription and fascimile
P5 methods for aligning TEI documents (see Chapter 14 Linking, Segmentation, and Alignment).
Method used by the Edition Production Technology (EPT): Link text and images
The EPT (now EPPT: http://beowulf.engl.uky.edu/~eft/EPPT-Demo.html) uses a system combining a Image Catalog combined with a special attribute for coordinates to enable linking between text and image.
Image Catalog
The Image Catalog is a simple XML file that consists of lists of image files organized by category. There is one category for every set of image files for a given source.
- daylight (images taken under regular lighting)
- ultraviolet (images taken under ultraviolet lighting)
- microfilm (images scanned from microfilm)
Categories are assigned unique IDs.
Within each category, the user associates each file with an ID that is unique within the category. IDs will repeat across categories. Essentially, these IDs associate the files with the same object, which may be represented by multiple images.
<category name="daylight" id="d"> <file name="aih0244-JPG.jpg" id="5v" /> <file name="aih0245-JPG.jpg" id="6r" /> <file name="aih0242-JPG.jpg" id="6v" /> </category> <category name="ultraviolet" id="u"> <file name="uv-5v.jpg" id="5v" /> <file name="uv-6r.jpg" id="6r" /> <file name="uv-6v.jpg" id="6v" /> </category> <category name="microfilm" id="m"> <file name="mf-5v.jpg" id="5v" /> <file name="mf-6r.jpg" id="6r" /> <file name="mf-6v.jpg" id="6v" /> </category>
The file IDs from image catalog are then associated with an attribute within the text markup itself. The attribute used is configured by the user; for the Electronic Boethius, we used the attribute n in the element <fol> (folio). The content for each folio is thus associated with the correct image files (from every category):
<fol n="5v">
points to
<daylight><file id="5v"/>
and
<ultraviolet><file id=“5v”/>
and
<microfilm><file id=“5v”/>
Attribute for Coordinates
To store coordinates from an image that correspond with a given piece of XML content, the EPT simply allows the user to assign an attribute (Electronic Boethius uses coords). In whatever elements that attribute is defined, the coordinates, selected by the editor, are automatically entered by the software. The ID assigned to the categories in the Image Catalog are appended to the beginning of the coordinates.
<damage coords="d:1058,738,1093,798">
Method used by the UVic Image Markup Tool: Annotate images
The UVic Image Markup Tool (http://www.tapor.uvic.ca/~mholmes/image_markup/) uses TEI, modified to allow for the inclusion of SVG, to create a system for annotating images.
Simplified example from the IMT web:
<TEI>
<teiHeader>
<!-- ...header content... -->
</teiHeader>
<text>
<body>
<!-- ...TEI content... -->
<div type="imtAnnotatedImage">
<svg>
<!-- ...svg content... -->
<image>
<!-- Image file is linked in here -->
</image>
<rect>
<!-- Annotation area on the image defined here -->
</rect>
</svg>
<div type="imtAnnotationLayer">
<!-- Annotation content goes here -->
</div>
</div>
<!-- ...TEI content... -->
</body>
</text>
</TEI>
Using this system, a user can annotate many sections of a single image. Unlike the EPT system described above, in which the coordinates are stored directly in the element, here the image coordinates are stored in a separate section and linked to the annotations using unique IDs (svg:id in <rect>) to link the areas to the annotation content (n in <div type="imtAnnotatedImage" xml:id="NB-B-17328">
<svg xmlns="http://www.w3.org/2000/svg">
<image xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="NB-B-17328.jpg" width="5060" height="6025"/>
<title>NB-B-17328.jpg</title>
<desc>5060 x 6025</desc>
<rect svg:id="NB-B-17328_0" x="4287" y="1412" width="580" height="426" style="3" color="#ff0000"/>
<rect svg:id="NB-B-17328_1" x="4067" y="2019" width="720" height="747" style="3" color="#ff0000"/>
</svg>
<div type="imtAnnotationLayer" n="NB-B-17328_0">
<head>la chandelle allume la découverte.</head>
<p>Il a trouvé la cache.</p>
</div>
<div type="imtAnnotationLayer" n="NB-B-17328_1">
<head>le couvercle de la malle</head>
<p>Il est pris sans vert</p>
</div>
=Using METS to link text and image=
here
