Fwd: [tei-council] List of items from Berlin

[Dot Porter]

Hi Everyone,

I have to leave soon and will miss discussion of the facsimile ODD and
chapter. I sent this message to the list last night but I know at
least Conal didn't receive it (it had a hefty .zip attachment). Con
has put the files up on Trac to please refer to that - Conal, can you
send a direct link to the trac ticket?

I think Conal has done a great job with this and I hope that my
modifications are acceptable to council.

Thanks,
Dot

---------- Forwarded message ----------
From: Dot Porter <dporter at uky.edu>
Date: Jun 14, 2007 10:14 PM
Subject: Re: [tei-council] List of items from Berlin
To: Lou Burnard <lou.burnard at computing-services.oxford.ac.uk>
Cc: tei-council <tei-council at lists.village.virginia.edu>


Hello all,

On 6/12/07, Lou Burnard <lou.burnard at computing-services.oxford.ac.uk> wrote:
> > 10: Linking
> > 10.4.3: Three-way alignment. This section needs to be reexamined in
> > light of the current work on facsimile/image markup, and I am working
> > on this currently.
> >
> I see Conal has just posted a whole mass of things. Hoorah!
>
>
I've taken a look at the odd file that Conal posted and have made a
number of modifications. I wasn't able to get that original file to
validate against the tei_odds.rng that I output from Roma, so most of
the changes were just for validation (all changes are listed in the
revisionDesc). I did make two pretty substantial modifications that
are in the spirit of simplicity, and I think we'll be remiss if we
don't include these:

1) Add @url to <pb> for those instances when there is one and only one
facsimile image for each page. I also added @width and @height to <pb>
to parallel <pg>. Make it clear in the Guidelines that when one uses
@url, @width or @height on <pb> one is not to use the <pg> structures
in the header. I don't know if there is a way to enforce this in the
schema.

2) Created a new attribute @coords (based on the METS attribute of the
same name), added it to att.coordinates, which was added to <area> and
<graphic>. The datatype of this attribute is a string, simply a list
of coordinate values. I think this should function similar to above,
in that if one uses @coords one should not use the attributes
available in att.projection - but again I don't know if there is a way
to enforce this in the schema.

I output an .rng file based on the ODD and have been working with it
this evening. This is based on some work I'm already doing, and I'm
trying to see how I might fit this current work into these new
structures. The file isn't in very good shape but I attach it and the
image files it references in case anyone is interested (a lot of the
values etc. are just for show...).

I haven't had time to look at Conal's changes to the Linking chapter
text, however Syd and I will be together in Victoria next week and we
have talked about sitting down there and working on it together.

Look forward to speaking to everyone tomorrow,
Dot

Attached:

test-facsimile.xml - sample xml file, relies on fax.rng
several .jpg files, which are pointed to in the xml file
fax-dot.odd - Conal's odd with Dot's modifications
tei_odds.rng - schema against which the odd validates

>


--
***************************************
Dot Porter, University of Kentucky
#####
Program Coordinator
Collaboratory for Research in Computing for Humanities
dporter at uky.edu          859-257-9549
#####
Editorial Assistant, REVEAL Project
Center for Visualization and Virtual Environments
porter at vis.uky.edu
***************************************