Salut Gautier, hello to everybody, the more I think about your concept the more I like it: It seems to fit perfectly to the TEI concept to take the single charter as a single text maybe being part of corpus (<group>) maybe not. Therefore I would suggest to the TEI to allow a type-attribute for the <text>-element. I'm less happy with your suggestion to encode the metadata as a <front>-element. It is right that one can take the regestum as some front matter to the charter in a scholarly edition. But talking about works like the Regesta imperii they would contain only front matters - and some front matter to the collection of front matters. I think the metadata is more something like the <msDescription>. It contains text representing real world informations on the charter or - to acuminate it - just representing the charter itself as many historians would take the abstract for the charter itself. So I would follow the suggestion of Michael Margolin to make the distinction between metadata (<regestum>) and text (<tenor>) with dedicated elements: <text type="document"> <body> <regestum> abstract, witnesslist, <listBibl type="...">, diplomatic analysis ... </regestum> <tenor> <div type="protocol"> <div type="Invocatio">In nomine sanctae et individuae trinitatis</div> <div type="Intitulatio">Heinricus <cl type="clausula devotionis">divina favente clementia</cl> romanorum imperator</div> ... </div> ... </tenor> </body> </text> But I'm willing to change my mind :-) Best wishes Georg On 9 Nov 2004 at 19:28, Gautier Poupeau wrote:
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
_________________________________________________________ Historisches Seminar Abteilung Geschichtliche Hilfswissenschaften Ludwig-Maximilians-Universität Muenchen Postadresse: Geschwister-Scholl-Platz 1, D-80539 Muenchen Bueroadresse: Amalienstr. 52, Zi. 211 T: ++49-89-2180 3784 F: ++49-89-21 80 2084 e-mail: G.Vogeler@lmu.de http://www.geschichte.uni-muenchen.de/ghw/personen_vogeler.shtml Moderator von der Virtual Library Geschichtliche Hilfswissenchaften (http://www.vl-ghw.lmu.de)