m.margolin@utoronto.ca a écrit :
Hi everybody,
1. <div> vs. <seg> My suggestion to use <seg> for diplomatic parts encoding is based solely on the TEI definition stating that <seg> marks a text fragment and that exactly what the diplomatic part is. On the other hand <div> is more generic by definition and may contain some meta data along with the text. I think that we should always seek the balance between specific and generic. The prize of being to generic would be a performance penalty on the any kind of information retrievals. On the other hand any attempt to enumerate content of the data (for example to use precisely named element inside of the <tenor> can lead to making encoding to restrictive and essentially not applicable. Therefore I suggest to use <div type=document> instead of <document> , keep <tenor> because of its unambiguous meaning and use <seg> to encode any diplomatic part on any level.
The <seg> element isn't accurate, because it can't contain the <p> element. Though you can have several paragraphs in a diplomatic part. For the <div type=document>, i prefer the <text> element as I explain in my preceding mail. The advantage of this element is you can have a <text> element for each charter. If you have one single document, you have this structure : <tei.2> <teiHeader> <teiHeader> <text> <front> Metadata and analysis of the charter </front> <body> List of witnesses and bibliography and the edited text of charter </body> <back> appended document </back> </teI.2> If you have a cartulary, you can use the <group> element instead of <body>, so you have : <tei.2> <teiHeader> </teiHeader> <front> Introduction and presentation of cartulary </front> <group> <text> .....The same structure for on charter </text> .... Much as <text> element as charter </group> <back> appended documents for the cartulary </back> </tei.2> Gautier