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

Dot Porter dporter at uky.edu
Tue Jul 17 08:20:25 EDT 2007


---------- Forwarded message ----------
From: Dot Porter <dporter at uky.edu>
Date: Jun 21, 2007 12:22 PM
Subject: Facsimile meeting, 6/20
To: Syd Bauman <Syd_Bauman at brown.edu>, Martin Holmes
<mholmes at uvic.ca>, Conal Tuohy <conal.tuohy at gmail.com>


Hi Syd, Martin, Conal,

Here are the notes from yesterday's meeting between me, Syd and
Martin. We took a look at the facsimile odd and came up with several
recommended modifications:

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). This element would contain a pointer
to class milestoneLike, so one could point not only to <pb/> but to
other milestones as well (<cb/> for example). Presumably once the
physical bibliography work is incorporated into the TEI this kind of
functionality would be directly available there as well.
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.
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:

<pg start="#D157r">
  <graphic corresp="#D157r20" url="Bodley340_157r.jpg" coords="1,2,3,4"/>
  <graphic corresp="#D157r21" url="Bodley340_157r.jpg" coords="5,6,7,8"/>
  <graphic corresp="#D157r22" url="Bodley340_157r.jpg" coords="11,121,3,14"/>
  <graphic corresp="#D157r23" url="Bodley340_157r.jpg" coords="15,352,388,124"/>
  <graphic corresp="#D157r24" url="Bodley340_157r.jpg" coords="11,26,33,74"/>
</pg>

We didn't discuss how this might work when mapping betwen different image files.

(Martin and Syd, I didn't take very good notes of this discussion so
please chime in if I've misrepresented our discussion.)

Thanks,
Dot

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


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



More information about the tei-council mailing list
http://lists.village.virginia.edu/pipermail/tei-council/2007/007888.html
lists.village.virginia.edu
crawl=CC-MAIN-2013-20
6820
application/http; msgtype=response
sha1:K2KILQ47BWR6ZTVBSBYIAVAYCG3OCE7N
<urn:uuid:1c90efd4-66e9-4494-ac5e-badb45acda3b>
2013-05-22T13:35:53Z
128.143.20.236
sha1:RAJGI6244W4ORS2U6EGUZSEZM5TBS2LK
<urn:uuid:acf7487f-3aee-410f-9b9e-2d1fb03e3501>
http://lists.village.virginia.edu/pipermail/tei-council/2007/007888.html
response
<urn:uuid:99d9cf22-e70d-4a29-b388-c0b928aeb7d4>
robots: classic
hostname: ip-10-60-113-184.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2013-20
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for Spring 2013
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf