[tei-council] testing facsimile

[Conal Tuohy]

-----Original Message-----
From: tei-council-bounces at lists.village.Virginia.EDU on behalf of Sebastian Rahtz
Sent: Tue 28/08/07 3:41
To: TEI Council
Subject: [tei-council] testing facsimile
 
> I have tried to apply the current draft to a real life example,
> a picture of a WW1 gravestone I took near Thiepval a couple
> of weeks ago.  Can people confirm that this is how it should be used?
> 
> I define a single surface with an associated image, then some
> zones within it. Four of those are used to link lines
> of transcribed text, and the other is used to describe a closeup
> of part of the object; only the latter has its own extra <graphic>.

That's all good as far as I can see. But what I don't understand is why you wouldn't nest the other <graphic> in its own <zone>, i.e.

<facsimile>
  <surface xml:id="grave"
       xdim="1024"
       ydim="681">
    <zone box="6 354 336 914">
      <graphic url="gravestone.jpg"/>
    </zone>
    <zone xml:id="grave-partial" box="383 182 684 356">
      <graphic url="gravestone-partial.jpg"/>
    </zone>
    <zone box="437 223 626 256" xml:id="line1"/>
    <zone box="446 251 610 282" xml:id="line2"/>
    <zone box="375 281 684 308" xml:id="line3"/>
    <zone box="390 306 674 332" xml:id="line4"/>
  </surface>
</facsimile>

 instead of 

<facsimile>
  <surface xml:id="grave"
       xdim="1024"
       ydim="681"
       box="6 354 336 914">
    <graphic url="gravestone.jpg"/>
    <zone xml:id="grave-partial" box="383 182 684 356">
      <graphic url="gravestone-partial.jpg"/>
    </zone>
    <zone box="437 223 626 256" xml:id="line1"/>
    <zone box="446 251 610 282" xml:id="line2"/>
    <zone box="375 281 684 308" xml:id="line3"/>
    <zone box="390 306 674 332" xml:id="line4"/>
  </surface>
</facsimile>

Note that in the markup I prefer, above, has a more rigid ("crystal") structure, in that a zone is always a child of a surface, and a graphic must always be nested inside a zone. So in this example the two facsimile images are encoded with parallel markup, the only difference being that one of the zones has an xml:id so it can be linked to from the transcript.

> The @xdim and @ydim on <surface> are the result of a
> longish discussion I just had with Lou about the relationship
> between the image, which shows more than the gravestone,
> and the object visible therein. The @xdim and @ydim define
> the grid on which all child <zone>s depend; the @box on
> <surface> describes the surface area.

That seems reasonable. Though shouldn't the @xdim and @ydim values of the <surface> then match the maximal coordinates in the @box attributes of the <zone> children?

Con