{"word_count": 316, "character_count": 3110}
After the discussion on the TEI list and the comments on the list, the post and twitter exchanges with @ttasovac, I came back to an old paper of Susanne Alt (http://hal.archives-ouvertes.fr/hal-00110971), which provides an overview of the constraints that could apply to a comprehensive representation of etymological information in a dictionary entry.Susanne uses the entry "Pamplemousse" from the TLF (Trésor de la Langue Française) to encode the following etymological information:PAMPLEMOUSSE, subst. masc. [...]Empr. au néerl. pompelmoes, fém., au sens 1 a, qui est prob. comp.de pompel «gros, enlé» et de limoes «citron» (BOULAN, p.148; KÖNIG, pp.159-160). Apparaît d’abord dans des textes fr. qui le donnent comme mot néerl.: 1665 pompelmoes (J. LE CARPENTIER, L’Ambassade de la Compagnie orientale des Provinces Unies... [trad. d’un ouvrage néerl.], II, p.88 ds ARV.); 1666 pompelmous (M. THÉVENOT, Relation de divers voyages curieux... t.3 ds KÖNIG).At the end of paper, following an in-depth discussion of etymons and links, which I advise you all to read, she suggests the following encoding:(i.e. the lexical entry pamplemousse and its direct etymon pompelmoes) of the data structure in a TeI like format. Note that the basic building blocks for the characterization of a lexical entry (&#60;form&#62; and &#60;sense&#62;) are completely reus- able for the description of an etymon, and the language has been implemented as a standardized xml:lang attribute.&#60;lexicalEntry id="LE1"&#62;&#60;form&#62;&#60;orth&#62;pamplemousse&#60;/orth&#62; ...&#60;/form&#62;&#60;sense&#62;... &#60;/sense&#62;&#60;etymology&#62; &#60;etymon id="LE2"&#62;&#60;form&#62; &#60;orth xml:lang="dutch"&#62;pompelmoes&#60;/orth&#62; &#60;pos&#62;commonNoun&#60;/pos&#62; &#60;gender&#62;feminine&#60;/gender&#62;&#60;/form&#62; &#60;sense&#62;&#60;glose&#62;Citrus maxima&#60;/glose&#62;&#60;note&#62;probablement d’origine tamoule, De Vries, Nederl&#60;/note&#62; &#60;/sense&#62;&#60;/etymon&#62; &#60;etymologicalLink source="LE2" target="LE1"&#62;&#60;etymologicalClass&#62;loan word&#60;/etymologicalClass&#62; &#60;/etymologicalLink&#62;&#60;/etymology&#62; &#60;/lexicalEntry&#62;If we "modernize" this proposal to make it as close to a TEI compliant entry, we could think of something as follows:&#60;entry xml:id="LE1"&#62;&#60;form&#62;&#60;orth&#62;pamplemousse … &#60;/form&#62;&#60;sense&#62;…&#60;etym&#62;&#60;re type="etymon" xml:id="LE2"&#62;&#60;form&#62;&#60;orth xml:lang="dutch"&#62;pompelmoes&#60;/orth&#62;&#60;gramGrp&#62;&#60;pos&#62;commonNoun&#60;/pos&#62;&#60;gen&#62;feminine&#60;/gen&#62;&#60;/gramGrp&#62;&#60;/form&#62;&#60;sense&#62;&#60;gloss&#62;Citrus maxima&#60;/gloss&#62;&#60;note&#62;probablement d’origine tamoule, De Vries, Nederl&#60;/note&#62;&#60;/sense&#62;&#60;/re&#62;&#60;link type="loanWord" target="#LE2 #LE1"/&#62;&#60;/etym&#62;&#60;/entry&#62;This is a little more ambitious than what was discussed in the previous post and related comments, but seems to follow what Toma Tasovac had in mind with an embedded entry in the description of the etymological content.