[tei-council] Fwd: Facsimile meeting, 6/20

Lou Burnard lou.burnard at computing-services.oxford.ac.uk
Tue Jul 17 09:48:01 EDT 2007


> 
> 1) The header <pg> element is very specific to a codex structure. We
> discussed changing this element to something more general such as
> <sourceImage> or even <sourceMedia> (which leaves the door open to
> other media besides image files).

I agree that <pg> is too specific. This is why I proposed a generic 
<zone> element which simply identifies a 2-d space.


> 2) We also discussed making a @sourceMedia or @sourceImage attribute
> available to milestoneLike elements (not only <pb/>) in the text. This
> could allow for two-way linking (so we could link from the text into
> the header), but would also serve the same purpose as @URL - to link
> to external files.

I think all we need is the existing global @corresp attribute -- though 
if you want to define a more specialised global attribute meaning "this 
text transcribes this zone" that's OK by me... you could call it @facs 
or @transcr or something

> 3) In the ODD file with my modifications (though I'm not sure for
> Conal's file that I modified), <area> is nested within <pg> along with
> <graphic>. There is no clear relationship between the <graphic> and
> <area> elements except that they are within the same <pg>. We
> recommend removing <area> from <pg> and instead allowing several
> <graphic> tags which could point to the same image, but with different
> coordinate values attached. So if I want to store coordinates for
> every line on a manuscript page, I have a separate <graphic> for each
> line, each with different coordinates attached:

I think this is a mistake, because now I can't easily distinguish 
graphics which identify the same zone but with different properties such 
as scale or resolution from graphics which identify different zones.

> 
>



More information about the tei-council mailing list