Hello all,
I'm writing specifications for a logical structMap that needs to represent milestones within a text that exists in 3 versions: individual page images, a PDF file for the whole text, and a TEI file for the whole text.
We'll want to be able to construct a link that references the correct page within a PDF file for a given <div> in the <structMap>. The HTML link is easy: <http://kb.adobe.com/selfservice/viewContent.do?externalId=317300&sliceId=2>. I'm wondering what the best way to do this in METS is, though. ftpr/area, with BEGIN and END attributes seems reasonable, but what to include for BETYPE? Nothing from the list in the Schema fits:
BYTE: a byte offset
IDREF: an XML ID value for an element in the content file
SMIL: a SMIL time value
MIDI: a MIDI time code
SMPTE-25: SMPTE time code for 25 frame/second material
SMPTE-24: SMPTE time code for 24 frame/second material
SMPTE-DF30: SMPTE time code for 30 frame/second drop frame material
SMPTE-NDF30: SMPTE time code for 30 frame/second non-drop frame material
SMPTE-DF29.97: SMPTE time code for 29.97 frame/second drop frame material
SMPTE-NDF29.97: SMPTE time code for 29.97 frame/second non-drop frame material
TIME: a simple time code of the form HH:MM:SS
TCF: a Time code Character Format value
I think I need <area> because I'm pointing to a position within a single file. Are there other options I'm not considering?
Along the same lines, is the following the best way to refer to a specific section of a TEI file, where milestone1 and milestone2 refer to elements in the TEI with id attributes having those values, respectively? This came up on a different list yesterday and this was my first pass at the problem, but something's nagging at me that this isn't the best solution:
<mets:fptr>
<mets:area FILEID="teiFile" BETYPE="IDREF" BEGIN="milestone1" END="milesone2"/>
</mets:fptr>
Thanks!
Jenn
========================
Jenn Riley
Metadata Librarian
Digital Library Program
Indiana University - Bloomington
Wells Library W501
(812) 856-5759
www.dlib.indiana.edu
Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com
|