[tei-council] facsimile - where to encode pages and facsimile graphics?

[Christian Wittern]

Daniel O'Donnell wrote:
> I like this.
>   

Me too.  This looks like a pretty balanced middle road between the 
re-implement-METS and hang-it-all-on-pb proposals.  And it reflects 
accurately the fact that both the <facsimile> and the <text> reflect 
different views of the same text.  For that reason, I would prefer to 
have only one <facsimile>, BTW.

All the best,

Christian
> On Fri, 2007-07-27 at 01:05 +1200, Conal Tuohy wrote:
>   
>> I want to address several aspects of the facsimile proposal, starting with this question about where the facsimile graphics should be encoded.
>>
>> I am convinced by Lou that they should not be encoded in the teiHeader. I think he's right that they deserve to be treated more like a text, and I think <gi>facsimile</gi> is a good name for the element.
>>
>> So, if have it correctly, it would be possible to have (as at present):
>>
>> TEI
>>    teiHeader
>>    text
>>
>> (for a normal transcript)
>>
>> or:
>>
>> TEI
>>    teiHeader
>>    facsimile
>>    text
>>
>> (for an edition in which the transcript is aligned with facsimile graphics. This is the main use case which Dot and I have had in mind all along)
>>
>> and, finally:
>>
>> TEI
>>    teiHeader
>>    facsimile
>>
>> (for a "purely graphical" facsimile, without any transcript at all).
>>
>> This last is an odd case, but I have seen something very like it in the wild. The now obsolete digital library software ENCompass (aka Curator) from Endeavour InfoSystems came with <soCalled>TEI</soCalled> support, but it turned out to be a highly customised variant in which a teiHeader was combined with a text consisting of a bunch of page breaks, each with a URL attribute pointing to an image. So there is a case for this already.
>>
>> I'm not sure how useful it would be to have multiple "facsimile" elements within the same TEI document. It need not require more than one such element, e.g.
>>
>> element TEI
>> {
>>    att.global.attributes,
>>    attribute version { xsd:decimal }?,
>>    ( teiHeader, facsimile?, text )
>> }
>>
>> On the other hand, I'm open-minded about this, and I would be happy with any alternative. Obviously it has to be decided one way or another, but the other parts of the facsimile model are more crucial to the actual functionality of the encoding.
>>
>> Con
>>
>>
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>     


-- 
 Christian Wittern 
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN