LegacyFacsimileMarkup

From TEIWiki
Revision as of 16:57, 1 March 2006 by Dot.porter (talk | contribs)
Jump to navigation Jump to search

This page includes some examples of different approaches for facsimile (image-based) markup.

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>,

, etc. from the TEI core tag sets.

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 because of differences between textual structure and physical structure may cause overlapping elements they need not be used.

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.

Optional recommendation is to define a new attribute, "url", to directly associate a <figure> with its corresponding image file

<pb n="16"/>
<figure n="16" url="http://image.ox.ac.uk/images/bodleian/msjunius11/16.jpg">
    <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" 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>
</figure>

This approach is simple, though it is not practical if one has multiple images of the same page in various resolutions.

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

Method used by the UVic Image Markup Tool: Annotate images

Using METS with TEI to link text and images