[tei-council] encoding page scans

[Lou Burnard]

> 
> <snip/> The main thing, to my
> 
>>mind, is that the guidelines should clearly document some standard
>>practice that doesn't involve treating page scans as figures, or making
>>custom extensions to the TEI schema.
>>
> 
> yes, yes, yes
> 
> 


No no no! In P5 we have a generic <graphic> and a generic <bitmap> 
element which could surely be used to mark the presence of a pagescan if 
you like. Whether you want to wrap them up in a (P5) <figure>  or in 
something else is a different question, of course. Also, at P5, you 
can't use the TEI without doing some kind of "custom extensions", so 
there's nothing to be afraid of there!




>>Dot, could you post a little example of the METS and TEI markup you are
>>using to associate an image file with a TEI page?
>>
> 

[details snipped]



> <structMap LABEL="Marginal Scholia">
>   <div LABEL="Book 4">
>     <div ID="Am.4.1">
>       <fptr>
>         <area FILEID="id-2001.01.0092" COORDS="368,842,1600,1656"/>
>       </fptr>
>       <fptr>
>         <area FILEID="id-sch-4" BEGIN="Am.4.1"/>
>       </fptr>
>     </div>
> 
> FILEID links up to the file groups; COORDS records the coordinates on
> the image file; BEGIN records the xml:id of the line in the TEI file
> (multiple lines would have both BEGIN and END).

This seems to confuse two different things: the first <fptr> is pointing 
to an area, and second one to a sequence of lines, isn't it?

In P5, you can use a URI to point in either case, so the syntax is 
likely to be a lot less verbose tho not particularly more perspicuous.

Then you could either use the corresp attribute to say that the two 
things correspond, or a standoff <link> to associate them.


>>>The UVic Image Markup Tool[2] uses
>>>SVG within the TEI body to link to both file and coordinates;
>>

I think we're using the word "link" in a different sense here. SVG is an 
XML notation, albeit from a different namespace, so you can just embed 
it within your TEI document if you like. And indeed we have examples 
which do.

>>That's an interesting example. I agree that inline SVG could be a good
>>way to mark up regions within a graphic. Just a quibble, though: in your
>>example, is the link between the graphical region and the text
>>represented by a purely conventional correspondence between the @n and
>>the @xml:id attributes? In the guidelines it suggest using a ptr to
>>provide a TEI-namespaced proxy for the SVG region, then linking the ptr
>>and the text markup with a TEI <link> element.
>>

That's sort of what I said above, except that I wasn't talking about SVG!

Another thing to throw into the pot: There are formats like DjaVu which 
embed in a single object a compressed page image and an XML transcript 
of it. Anyone got any views on how that affects these issues?

p.s. shouldnt this conversation be going on on tei-l?