Laurent Romary

Werner Wegstein

Consistent modelling of heterogeneous lexical structures

Keywords:

Our paper outlines a proposal for the consistent modelling of heterogeneous lexical structures in semasiological dictionaries, based on the element structures described in detail in chapter 9 (Dictionaries) of the TEI Guidelines. The core of our proposal describes a system of relatively autonomous lexical -crystals‖ that can, within the constraints of the relevant element's definition, be combined to form complex structures for the description of morphological form, grammatical information, etymology, word-formation, and meaning for a lexical structure.

The encoding structures we suggest guarantee sustainability and support re-usability and interoperability of data. This paper presents case studies of encoding dictionary entries in order to illustrate our concepts and test their usability.

We comment on encoding issues involving <entry>, <form>, <etym>, and on refinements to the internal content of <sense>.

Author bios

Laurent Romary is Directeur de Recherche for INRIA (France) and guest scientist at Humboldt University (Berlin, Germany). He carries out research on the modelling of semi-structured documents, with a specific emphasis on texts and linguistic resources. He received a PhD degree in computational linguistics in 1989 and his Habilitation in 1999. During several years he launched and directed the Langue et Dialogue team at Loria (Nancy, France) and participated in several national and international projects related to the representation and dissemination of language resources and on man-machine interaction, coordinating the MLIS/DHYDRO, IST/MIAMM, and eContent/Lirics projects. He has been the editor of ISO standard 16642 (TMF -Terminological Markup Framework) and is the chairman of ISO committee TC 37/SC 4 on Language Resource Management,as well as member (2001)(2002)(2003)(2004)(2005)(2006)(2007) then chair (2008)(2009)(2010)(2011) of the TEICouncil. In the recent years, he led the Scientific Information directorate at CNRS (2005CNRS ( -2006) ) and established the Max-Planck Digital Library (Sept. 2006-Dec. 2008). He currently contributes to the establishment and coordination of the DARIAH infrastructure in Europe as transitional director.

Werner Wegstein is a retired professor of German Linguistics and Computational Philology. His publications include a scholarly edition of an Old-High German Glossary (Ph.D. 1985), the first complete reverse index to a Middle High German dictionary (1990, together with E. Koller and N.R. Wolf), a Habilitation on computer-based philology (1995), conference papers on the application of IT to medieval German (2001), and a recently co-authored work on corpus linguistics (Korpuslinguistik deutsch: synchron, diachron, kontrastiv, 2005). He hosted the <philtag> TEI workshops in Wuerzburg; is a founding member of TextGrid, the humanities partners of the German D-Grid initiative; and at present is active in a project researching the interaction between the sciences and humanities in the field of variation.

Pooling Lexical Sources:ADigital Humanities Perspective

Our paper addresses the problemof interoperability between heterogeneous data sources, an issue that has regularly been the object of many debates within the Text Encoding Initiative (TEI) community and in general within many standardisation groups providing models or formats for data interchange. At the core of the problem is the trade-off between expressivity-offering a flexible platform for representing a variety of possible structures-andprocessability-being able to predict under which conditions some data can be the object of a blind interchange, in particular in the context of them being processed randomly by a generic tool. This trade-off has no generic solution, but it regularly arises in defining the components of such an expansive modelling platform as the TEI Guidelines. The TEI specifications are an expression of a balance of interests between the many, varied use cases from the community and the need to abstract away from such examples in order to design recommendations that new users can easily understand and apply in the context of their own encoding endeavours.

Throughout the TEI Guidelinesone finds a stratification of corrections, constraints, and new features added over time, which have left some constructs ashybrid data models and which leave the user wondering which representation is the -optimal‖ one in a given context, leading to heterogeneous encoding practicein the global data space of existing TEI documents. Over the years this has become more and more an issue as documents are increasingly accessible online and scholars increasingly collaborate on projects using TEI documents. That is, the -stratification‖ of the Guidelines has worsened the problem of interoperability.

In this paper we will focus on lexical structures, which we believe represent a typical case of the interoperability problemin terms of pooling data from heterogeneous sources. We have asked ourselves whether the TEI chapter dedicated to lexical data, simply entitled -Dictionaries,‖should not be revised or at least be accompanied by further constraints on its usage so that basic operations related to the querying, displaying, or merging of lexical information could be made more straightforward.

From a digital humanities perspective, we want to understand if it is possible to find a balance between expressing precise constraints on the encoding of a primary source and leaving some freedom to the scholar who will see the encoding activity as a step in his research process. This is why we have made an attempt to identify a generic methodology for expressing encoding constraints on source texts based on the idea of local representation or crystals [START_REF] Romary | ODD as a generic specification platform[END_REF]. These crystals correspond to elementary constructs at a low level of granularity in a document, which, independently of the broader organisation of the document itself,can be used toexpress a certain concept in an extremely regular way, thus making the further reuse of this information chunk easier. In this context, interoperability is related to the capacity of a person or a toolto process encoded crystals within a document independently of its origin.

After presenting the general background for modelling and representing lexical sources we give an overview of the various crystals that form the basis of most existing types of lexical entries. For each of these crystals we make systematic recommendations with corresponding supporting arguments. In the second part of the paper we illustrate our proposals with concrete cases taken from various dictionary andlexical database projects.

Modelling Tools for Lexical Resources

The case of lexical data as presented in a dictionary offers an interesting experimental setting for studying interoperability in the context of standardisation. It is complex enough to reflect the variability which is intrinsic to the TEI Guidelines while providing a limited observational setting for studying the granular structure of lexical entries as well as the rather high internal coherence that one specific lexical source usually has. Lexical resources also reflect the variety of analytical points of view that one may have on linguistic information ranging from quite descriptive and verbose objects in the domain of standard human-oriented dictionaries to fully structured databases like those developed in the natural language processing domain.

In this paper we consider only lexical resources that are encoded semasiologically-where entries are determined according to the forms found ina language and further refined into the different senses that have been deemed relevant for this form. This word-to-sense organization is usually seen as the most appropriate for the representation of large coverage lexica, as opposed to onomasiological representations (concept-to-term), which better take into account the organisation of domain-specific vocabularies (terminologies).The semasiological perspective is usually the underlying model for traditional print dictionaries as well as for large-scale lexica in the natural-language-processing domain [START_REF] Halpern | The role of lexical resources in CJK natural language processing[END_REF]Atkins et al.2002).

There are two main international standardisation activities that are relevant for the modelling and the representation of semasiological resources: the Lexical Markup Framework (LMF) and TEI. In accordance with the modelling strategy of ISO committee TC 37, LMF (which has been standardised as ISO 24613:2008) provides a group of meta-models that can be combined to produce specific data models applicable to a wide range of lexical types or components includingmachine readable lexica, morphology, syntax, semantics, multi-word expression. Even whenthe LMF specificationprovides a possible XML serialisation, it tends to be agnostic as to the actual implementation of the models it allows one to describe. On the other hand the TEI has been seminal in offering a reference XML vocabulary for the representation of dictionaries, which is mostly compliant with LMF principles. 1However, the variety of constructions that the TEI actually allows for the representation of the same lexical phenomenoncould possibly be seen as a hindrance to the achievement of deep interoperability across heterogeneous lexical resources.

In this paper we take as astarting point the positions described by LMFandthe latest release of TEI Guidelines2 in order to provide further insights into how to build lexical resources or dictionaries relying on a systematic use of standardised constructs. The work presented here is also based upon some core principles that have systematically guided our work, both theoretically but also practically,through the in-depth presentation ofexamples that have served as experimental background for testing our proposals.Even thoughthe present work is not about modelling XML structures at large, several of these principles are derived from a more global concept of the kind of semantics that XML constructs convey and the way to actually reflect this in the design of XML formats.

With this perspective in mind, two generic constraints that affect the organisation and semantics of lexical structures can be stated:  Semantic grouping: Features that jointly convey a given meaning in a lexical entryshould be systematically grouped together, even when only one such feature occurs andeven at the cost of favouring more deeply-structured representations.  Hierarchical dependency:Features, or groups thereof, which qualify a given level (for instance, an entry), are considered to be inherited by subcomponents (typically the senses) of the lexical entry unless otherwise stated [START_REF] Ide | A Formal Model of Dictionary Structure and Content[END_REF]. (Here and below, we use -level‖ to refer to a hierarchical relationship within the data structure.)

From these constraints we will progressively derive specific recommendationsforthe local organisation of lexical entries as guided by acrystal-based analysis. Comparing these with real data, and in particular with legacy dictionaries, we will try to understand possible transition schemes from weakly structured data to more standardized constructs.

Core Proposals:Towards a Systematic Description of Lexical Crystals

Crystals as Coherent Sub-structures

Introducing the concept of crystals in data modelling in general and in the TEI Guidelines in particular reflects the needto describe data structures that act as scaffolding for a coherent group of components (or elements in XML terminology). More precisely, a crystal can be defined as an independent group of connected elements (a clique) with semantic coherence. A typical example of a crystal is a structured bibliographical entry using the TEI's <biblStruct> element. This element contains internal structure (comprising<analytic>, <monogr> with <imprint>, and <series>), can be inserted at various places within the TEI architecture, and can be further expanded by other components or crystals (for example, <author>).

Without introducing any specific formalism here, we mightdefine a crystal by:  The set of mandatory and optional components that may occur in the crystal  The structural organization of the crystal, stating in particular the hierarchical relations between components  The anchor points of the crystal(<analytic>, <monogr> with <imprint>, and <series>), where it can be further expanded  The global semantics of the crystal, in complement to the specific semantics of its component elements A crystal is thus a modelling tool that can be used to provide a coherent description of a subset taken from a more complex data model (as is typically the case with the TEI Guidelines). To illustrate this, we will briefly demonstrate how the TEI Guidelines chapter on dictionaries can serve as a basis for implementingLMF,and point out some consequences this could have on the data architecture that we recommend for certainTEI elements.

As a starting point, let us consider the LMF subset depicted in Figure 1, which implements the semasiological view of a lexical entry. This UML diagram states that a Lexical Entry is characterised by at least one Form component to which a hierarchically embedded series of Sense components may be associated. The Form component is further refined by means of an optional Form Representation component, which can be used to represent the various concrete implementations of a lexical form (e.g. phonetic, graphical, etc.). Finally, each component of the meta-model (corresponding here to a UML class) can be further characterised by properties attached to each of them. Transposed tothe TEI world, the LMF metamodel can be expressed as a TEI crystal rooted on the <entry> element. This crystal, depicted in Figure 2, states that the minimal lexical entry in a sense as defined by TEI uses the <entry>, <form> and <sense> elements, with <form> being further decomposed by means of a series of elements implementing the Form Representation component of LMF. 3 The picture also introduces three new classes, which could gather up all further descriptive elements needed to refine <entry>, <form>, and <sense>: model.entryDesc, model.formDesc, and model.senseDesc.

This first presentation of the TEI lexical entry as a crystal illustrates how this concept may help in describing complex structures that rely on constraints that go beyond (and deeper) than what we normally express by means of DTDs or schemas. Even though we do not systematically analyse the equivalences between LMF and the TEI in the following section, we hope that the preceding explanation will help the reader understand the logic behind the various constraints explained in

Lexical Entry

Form Sense Form Representation subsequent sections. In a pattern analogous to the internal structure of the <cit> element, we see the organisation of the various elements of this lexical entry crystal as a combination of a structuraldescription (direct dependency of one element onanother) and a descriptive dimension(further constraints applicable to the group of elements).

Morphographical Descriptions

In a semasiologically structured lexical entry, form information gives one or more realisations of a word-whether graphical, phonetical or iconical (by means of a picture or drawing)-which can be used to find the corresponding lexical unit. Such informationmay comprise abstract identifiers for the headword, namely the lemma, morphological components or categories (such as the consonantal pattern in Arabic), or any inflectional variant that can be associated with the entry.

The central issue in describing the corresponding morphographical crystal is that it should be based upon an abstract representation of Form as a component, which in turn groups together all the possible realisations of the corresponding form (the Form Representation component in LMF), as well as the associated constraints. In terms of good practices, one should thus refrain from providing a form representation (realisation) in isolation and always include it within an embedding <form> element4 .Unless there is only one form associated with a given lexical entry, the form type (such as a lemma or inflected form) should be providedto ensure its univocal identification.

As a consequence, the minimal structure associated witha TEI-encoded lexical entry-where the only information given is that of a lemma (here, the French wordchat; (en) cat)-should be encoded as follows: On this basis, additional variants of the form (such as pronunciation) can be added to the same form container, together with complementary information characterising them. For instance, when more than oneorthographyis used to provide the form, the appropriate @type attribute should be used to qualify the corresponding orthography. In the following example, the lemma for the Korean word -치다‖ (chida; (en) to hit) is provided in Hangul orthography ((ko) 한글) orthography together with a Romanized form.

<entry> <form type="lemma"> <orth>chat</orth> </form> </entry>
<form type="lemma"> <orth type="한글">치다</orth> <orth type="romanized">chida</orth> </form>

As a next step, we advocate the definition of stable values for the @type attribute on <orth>, adopting ISO 15924 to refer to the script.

When alternative forms are provided, indicating, for example, inflectional variation, then the variants should be encodedin fullin order to reflect linguistic differences. For instance, the example provided in Annex B of LMF (clergyman) is reformulated in TEI as follows:

Grammatical Information

Grammatical information may appear at various points within a dictionary entry;it is there to provide additional information aboutthe core objects comprising the entry. In the lexicographic tradition grammatical information qualifies the lemma, or rather, since the lemma is just a code representing the entry as a whole, syncretises the grammatical features that apply by default to all possible occurrences of the word. However, the grammatical informationcan also occur at many other possible levels of the entry, qualifying inflected forms in a more precise way (as in the -clergyman‖ example above), indicating specific constraints associated to a sense, or even qualifying the occurrence within an example of phrasal expression. As a whole, a grammatical crystal defined according to these principles may be used at any place where the usage of a word is described.

The notation for grammatical features within human-oriented dictionaries varies greatly: a given grammatical constraint can, for instance, be represented by a prototypical morpheme (e.g. der/die/das to indicate grammatical gender in German) or by means of a descriptive phrase (used in the plural form). At best idiosyncratic codes are used (e.g. masc., fém.), though they are not always consistently applied within a single dictionary, let alone across dictionaries.There is no doubt that such a situation prevents one from querying lexical entries that includegrammatical constraints in a coherent way. It is therefore a priority to establish requirements for the representation of grammatical featureswhich in a way that is both standard and yet preserves the initial editorial choices. As a basis for such recommendations we recommend that TEI-based encoding of dictionary entries should be in keeping with the following elementary principles:

 Grammatical features should systematically be embedded within a <gramGrp> container element, even if only one feature is presentand even if the grammatical information is split up so that more than one <gramGrp> container may be necessary.  Whereas one should be flexible with the textual content of a grammatical descriptor, it is of utmost importance to normalize the intended value by means of a @norm attribute.

For instance, when a value for the grammatical gender is given by means of a determiner, the @norm attribute will provide the reference value (e.g. as a code from the ISOcat data category registry5 ).

Depending on the encoder's editorial choices, a minimal encoding might look likethe following example:

<form type="lemma"> <gramGrp> <gen norm="feminine">die</gen> </gramGrp> <orth>Katze</orth> </form> Amore elaborate encoding scheme could lead to the following lemma structure: <form type="lemma"> <form type="marker"> <gramGrp> <pos norm="determiner"/> <gen norm="feminine"/> </gramGrp> <orth>die</orth> </form> <form type="head"> <gramGrp> <pos norm="noun"/> <gen norm="feminine"/> </gramGrp> <orth>Katze</orth> </form> </form>

In general such grammatical descriptions should be thought of as being equivalent to the provision of feature structuresand thus mappable onto an <fs> element. For instance, the preceding minimal encoding example (omitting the orthographic form) isequivalent to: <fs> <f name="gender"><symbol value="feminine"/></gen> </fs>

The next stage in providing a recommendation is to make sure that values for the @norm attribute are stable within a project and when possible across projects. We recommend two complementary strategies:

 For a given project, document and publicize the values used for the norm attribute so that the community may be aware of possible discrepancies  Relate such values to entries in the ISOcat data category registry so that they are mapped onto standardized conceptual references.

It should be noted that at the time of writing there is an item on the TEI Council agenda to better integrate mechanisms available in ISO 12620:2009 (the standard which defines the structure of ISOcat) within the TEI architecture to facilitate such mappings. We can thus expect that these recommendations may become in due course standard practice within the TEI community.

Senses as Systematic Entry Points

The representation level introduced by the Sense component in LMF and its counterpart <sense> in the TEIGuidelines is an essential concept implementing the semasiological perspective of a dictionary. Still, a -lazy‖ encoding style for dictionary entries could lead to the idea that such a structure is superfluous when, for instance, a word can directly be described at the same level as the morphological and grammatical information by a simple definition or a translation that is a child of <entry>. Indeed, it is often the case in the simplest forms of legacy lexical structures that senses are not explicitly separated out in the microstructure of the entry. We consider this as bad practice and recommend that<sense>be used to enclose all descriptors that describe the signified (as opposed to the signifier, that is the <form>,in the Saussurian sense).

As can be observed from the variety of constraints that may apply to a <sense> element within a lexical entry, the underlying understanding of the semasiological model extends to the organisation of senses that do not rely on strict semantic criteria [START_REF] Ide | A Formal Model of Dictionary Structure and Content[END_REF]. This is not so much of a paradox when we think of the numerous ways by which semantic variation may be observed, among which we can include pure morpho-syntactic or syntactic markers.As a result, we consider that <sense> should be used to describe any subdivision reflecting avariation in usage for a given word. In an extreme case, applying automatic collocation extraction tools (Kilgarriff and Tugwell 2002) may result in generating lexical entries automatically where senses correspond to the various collocation classes that the tool has determined.

We thus see the sense component in LMF and the <sense>element in TEI as a generic container organizing the further description of a signifier, which may contain information related to:

 The actual syntactico-semantic restriction applicable to the sense being described,for instance by means of further grammatical constraints, a definition, or some usage restriction  The provision of further illustrative information, in particular contextualised examples or translations (see the section on the <cit> element below)  Relational information referring to external information expressing the same meaning, either within another lexical entry or an external ontological reference (such asin the lexical database project WordNet, described by [START_REF] George | WordNet Then and Now[END_REF]).

In order to actually facilitate further querying, it is important that each feature intended to be associated with a sense shall be precisely typed. Precise typingrequires that clearly defined typologies be associated with elements such as <usg>and<cit>. Furthermore, dictionary projects should be able to document precisely how much restrictive or illustrative information is inherited along embedded senses. For instance, a clear editorial strategy should state whether grammatical constraints replace or complete existing ones at a higher level of a sense hierarchy.

<cit>: A Generic Linguistic QuotationTool

The <cit> element in TEI P5 is the result of a merger of several constructs from former editions of the TEI chapter on dictionaries that had been created to handle examples and translations in dictionary entries. The underlying aim of the new framework was twofold. On the one hand, the objective was to provide greater coherence to the way language excerpts appear not only in dictionaries but in textual content in general. On the other hand,the TEI Council wanted to design a sound framework for dealing with additional references or constraints provided in a lexical entry to compliment the quoted object itself, taking into account that such refinements may lead to recursive constructs.In terms of interoperability across TEI-based applications, the main vision behind the <cit> element, and the crystal it shapes, is to provide entry points for generic searches for quoted language in texts, from the point of view both of the full-text contentandof providing a systematized representation of constraints associated with the full text.

Language quotations in text may indeed take many different forms. In dictionaries the most basic quotation is simply a phrase or sentence exemplifying the headword. Most of the times this quotation does not appear alone but is refined according to two main axes:

 Indication of the source of the quotation, for instance the following from P5 2.0.0: 'La valeur n'attend pas le nombre des années' (Corneille)  Provision of usage information, stating constraints that the example is bound by, such as domain or pronunciation, as in the following from P5 2.0.0: some … 4. (S~ and any are used with more): Give me ~ more/s@'mO:(r)/

In the case of multilingual dictionaries,language quotations are similarly used to provide equivalences for the entry (or sub-sense thereof) in the target language. In a way that is similar to the monolingual case, further refinement of the encoding structure of a quotation may indicate some source or usage information, but it may also document the target language proper. A usual case here is the indication of the grammatical gender of a noun equivalent in the target language.

Quotation constructs are not covered in LMF but can easily be modelled as an extension to the LMF core packages. Figure 3 is a simple representation for such an extension. The approach is similar to that we advocate above for grammatical information in relation to senses,in which the quoted text is embedded in a quotation construct even if no refinement is actually stated.  The refinement of a quotation can be instantiated as a bibliographic reference (using an element from model.biblLike), as a pointer or external reference to a constraint (using an element frommodel.ptrLike), as specific lexicographic features such as grammatical constraints (using an element from model.entryPart),or through the inclusion of feature structures in <cit>accidental by design-which are part ofmodel.global. It should be noted that a refinement can actually be an embedded<cit> (by virtue of the inclusion ofmodel.entryPart in the content model of <cit>),thus offering, for example, a natural way to provide a translation of a quotation Note that the TEI Guidelines already systematize the values of the @type attribute to -example‖ and -translation‖ for use in dictionaries.

Given the variety of possible cases where <cit> may be used and the potentially infinite combinations of refinement, it may be difficult to provide clear requirements for its application. Basically a proper usage of <cit> should allow a human reader or a processor to identify one quoted object and treat all other components as refinementsin which semantics are understood in a conjunctive way (in other words, all refinements applyen bloc to the quoted object). By default the quoted object should bethe first child of the <cit> element or, in general, the first child that is a member of either model.qLike or model.egLike.

Although the second part of this paperprovides several applications of <cit> in the context of our observational corpus, we can illustrate here some basic usages of this element from examples available in the TEI Guidelines.

In the following prototypical case,a simple example for the headword is associated with a refinement giving the pronunciation of part of the quoted text:

<cit type="example"> <quote>Give me <oRef/> more</quote> <pron extent="part">s@'mO:(r)</pron> </cit>

The next example illustrates the representation of a translation refined with a grammatical feature:

<cit type="translation" xml:lang="fr"> <quote>habilleur</quote> <gramGrp> <gen>m</gen> </gramGrp> </cit>

Finally, we cannot resist presenting a recursive case where the embedded <cit> is used as an additional descriptive element for the quoted text at the higher level:

<cit type="example"> <quote>she was horrified at the expense.</quote> <cit type="translation" xml:lang="fr"> <quote>elle était horrifiée par la dépense.</quote> </cit> </cit>

Illustrated Guidelines for Early Printed Dictionaries Lexicographical Justification

We tested our encoding concepts using printed dictionaries from the second half of the 18th century for two reasons. First, in the history of English lexicography the early 18th century marks the beginning of modern dictionary practice (Landau 2001, 60-66). Samuel Johnson's Dictionary of the English Language, first published in 1755, perfectly embodies these advances in lexicography.

Johnson is the first English lexicographer to include thousands of other quoted -‗authorities' within his text as illustrations of word use‖ (Reddick 1996, 9). His dictionary also brought together -for the first time key conventions for future dictionary presentation: the folio 6 design is a system of typography that displays the structure of each entry, though there are inconsistencies of abbreviation and ambiguities‖ (Luna 2005, 193). Thusthis dictionary offers an ideal testbed to study problems in providing a consistent encoding in P5 of a source document that offers notational inconsistencies. Second, because Johann Christoph Adelung 7 translated Samuel Johnson's dictionary into German (Adelung 1783-1796), Johnson's dictionary opens up additional perspectives for the study of bilingual lexicographical resources in the 18th century and research into the history of revision and the reuse of dictionaries.

We test our modelling of lexicographic structures with three samples fromJohnson's monolingual dictionary representing the most frequent word-classes: the adjective ABLE, the verb To APPLAUD,and all entries for the noun APPLE (the use of all caps versus small caps by Johnson is explained below). We further compare Johnson's apple entries with the section of apple entries in Adelung's bilingual English-German translation of Johnson's dictionary. To illustrate the differing encoding structures of bilingual German-English dictionaries we use Eber's entry FÄHIG, the equivalent of ABLE. As a source for this entry, Ebers obviously used only the German-French dictionary of Christian Friedrich Schwan (Schwan 1782), so we include Schwan's entry FAEHIG in order to illustrate dictionary reuse across languages in the 18th century. The images of the encoded pages are givenas a supplement to this article.

Typographic Analysis and Text Encoding

Luna begins his essay on the typographic design of Johnson's dictionary with some reflexions on how a typographer would analyse a dictionary: "In particular, how does a typographer look at a dictionary that is also a cultural artifact, as Samuel Johnson's Dictionary of the English Language undoubtedly is?" (2005,175). Building on a more wide-ranging definition of typography as -configuration of verbal graphic language,‖ Luna concludes, "the main concern of this essay is not the quality of the printing, nor the nature of the paper, nor even the origin of the founts of type used to compose the Dictionary, 6 Paul Luna's analyses here the typography of Johnson's folio edition of his dictionary (in opposition to different typography and text structure in the quarto and octavo editions). Folio is the old measure of size of a book and an indispensable term for research on Johnson's dictionaries. 7 Since Adelung's name does not appear on the title page nor elsewhere in the front matter, his role as a translator is little-known. It is worth mentioning the publication context. Adelung studied and translated Johnson's dictionary while working on the two editions of his own German dictionaries. The first volume of his translation, containing the letters A to J, was published in 1783. This was after nearly three years of work-according to his preface (p.xii)-and before he finished the fifth and last volume of the first edition of his German dictionary which he had started in 1773 (Adelung 1774(Adelung -1786)). Thirteen years later, in 1796, he published the second volume of his translation with the letters K to Z, after having finished the first two volumes of the second and final edition of his German dictionary (Adelung 1793(Adelung -1801)). Against this background future research into structural relations between Johnson's Dictionary of the English Language and Adelung's German dictionaries looks promising.

Almost at the same time Johannes Ebers used Adelung's lexicographical materials to compile a German-English counterpart in three volumes with a very elaborate title New and Complete Dictionary of the German and English Languages composed chiefly after the German Dictionaries of Mr.

Adelung and of Mr. Schwan ... [START_REF] Ebers | New and Complete Dictionary of the German and English Languages composed chiefly after the German Dictionaries of Mr[END_REF].

but how its visual presentation reflects the structure of the text, its usability, and perhaps even its compiler's intentions" (2005,175).

This concept comes very close to what a TEI encoding of a dictionary in an adequate granularity should achieve: reflecting the structure of the encoded text, facilitating re-usability in electronic form and-at its best-assisting in the detection of the author's intentions. In order to put our aim of a consistent modelling of heterogeneous structures into practice, we follow some basic principles.

We adopt a conservative editorial view for our literal transcription (see section 9.5.1 of P5) and try to keep the latter close to the printed original: we do not add any character to the original text or delete it,we transcribe the text in the order in which it appears in the source, we preserve the linear structures of the text with <pb>, <cb> and <lb>, and we retain the end-of-line hyphenation (see section 3.2.2 of P5). With such orthographical variation within the texts of the dictionaries, this makes transcription much easier. For clarity and to ensure a consistent encoding we encode only a few structurally important typographic features (significant use of typeface and italics) at the level of the lexical entry. 8

Encoding Practise at the <entry>level

With re-usability, interoperability, and sustainability of the dictionary entries in mind, we use two attributes to refine the <entry>element: @xml:id to guarantee a robust and reliable non-ambiguous identification and @type for classification of the entries.

The @xml:id attribute is composed of four parts, each separated by a dot: 1. two initials of the author's name and a combination of six letters or numbers to identify the encoded edition precisely 2. four digits for the year of publication 3. six digits for the running number of the entry (given as a random value in the examples) 4. the lemma, transcribed in lower case only and with any incidental spaces replaced by underlines.

Thus our sample entry ABLE in Samuel Johnson's dictionary is assigned the @xml:id 'sjdict1f.1755.000123.able'. In the first part, -sj‖ is taken from Samuel Johnson, -dict‖ reflects the title Dictionary of the English Language, and -1‖ indicates the edition and -f‖ the format folio (because edition and format are both rather important for a precise identification of the different printed editions of Johnson's dictionary). They are not necessary for Adelung (Henne 2001, 170), Ebers [START_REF] Lewis | Die Wörterbücher von Johannes Ebers. Studien zur frühen englisch-deutschen Lexikographie[END_REF], and Schwan.

We use the TEI @type attributes of <entry> to distinguish typographically or verbally marked types of entries and map them onto corresponding identifiers of the ISOcat data category registry. The @type attribute used on <entry>belongs to the attribute class att.entryLike, which includes a list of suggested 8 We do not encode the two typefaces for Latin script used by German printers of Adelung's and Ebers' dictionaries because there is a fixed relation between language (encoded using @xml:lang) and the typeface: for German texts the Fraktur variant is used, whereas for other languages Antiqua is used. We only encode exceptions to this rule, such as in Schwan's German-French dictionary, where ISO 15924 codes are used for the representation of names of scripts. We do not encode the indentation and alignment structure, nor do we encode italics in the contexts of part-of-speech labels (in a <pos> element), of cited forms in <etym> (if printed in italics), of the lemmata used in illustrative quotations (in a <cit> element), or of the names of authors and their works in the sources for the illustrative quotations (in a <bibl> element). values for @type.For the entries in Johnson's Dictionarywe had to add some more fine-grain distinctionsto the list of suggested values.

An occasional user of Johnson's Dictionary may be puzzled about the typesetting of entry headwords. Thus APPLAUD and APPLE are in full caps, while APPLAUSE and APPLE TREE are in small caps. Now and then, however, entries appear typeset in italic capital letters, e.g. ABORIGINES and ABRACADABRA. In his preface Johnson explains the background for these marked differences, which for him reflect basic lexicographical distinctions: "In the investigation both of the orthography and signification of words, their ETYMOLOGY was necessarily to be considered, and they were therefore to be divided into primitives and derivatives. A primitive word, is that which can be traced no further to any English root; ... Derivatives, are all those that can be referred to any word in English of greater simplicity." (1755, 3f.) Thus primitives or roots are marked by full caps and the derivatives by small caps. Furthermore, the entries in italic capital letters indicate foreign words used in the English language (Luna 2005, 181).

As Luna notices (2005, 196 fn. 24), this distinction of entries echoes a completely different way of organizing a dictionary: word-families, represented by roots (in alphabetical order), followed by their derivatives (ordered non-alphabetically into morphological or etymological groups). Since Johnson used a single alphabetical order for all entries, this organizing principle is no longer clearly visible. It is only faintly reflected in the differentiation of the lemmas. But it is still implicitand that is why we think it should be encoded explicitly as a significant feature of the dictionary structure. Accordingly, we map the entries representing lexical units in Johnson's Dictionary onto the ISOcat identifiers /root/or/derivation/ and use/foreign/ to indicate foreign words respectively. Two examples: ABLE and APPLEof Love.

<entry xml:id="sjdict1f.1755.000123.able" type="Root"> <form type="lemma" norm="able"> <lb/><orth rend="allcaps">A'BLE</orth><pc>.</pc> <gramGrp><pos norm="adjective">adj.</pos></gramGrp> </form> <entry xml:id="sjdict1f.1755.000346.apple_of_love" type="Phrase"> <form type="lemma" norm="apple of love"> <lb/><orth><hi rend="smallcaps">APPLE</hi><hi rend="italics">of Love</hi></orth><pc>.</pc> <gramGrp><pos norm="noun"/></gramGrp> </form> <sense> <cit type="Encyclopedic_Information"> <quote><lb/>Apples of love are of three sorts; ... <bibl><author>Mortimer</author>'s <title>Husbandry</title>.</bibl> </cit> </sense> </entry>

The typography of the entry APPLEof Love-small caps for apple though belonging to the rootentries, italics for of love, and the word class information missing from the source (though supplied in the encoding)-indicates uncertainty about the word status of the entry. Furthermore, the classification as type phrase may require some explanation. Valerie Adams comments in her introduction to wordformation on the distinction between words and phrases: -Certain noun-preposition-noun phrases also show their incomplete unification by the possibility of pluralizing the first noun" (1976,9). Since the illustrative quotation of Mortimer's book on Husbandry starts with the plural form -apples‖, we regard the type -Phrase‖ here as justified and did not consider alternative ISOcat options.

The <form>Block

The <form>element is designed to contain information on the written form (encoded using <orth>) and, if present, the spoken form (encoded using <pron>) of one lemma. We use<form> with two attributes: a @type attribute to distinguish the lemma from any given inflected forms and @norm attribute to even out any orthographic variation, such as the use of upper or lower case, hyphenation, or special markers to indicate the stress position within the orthographic representation of the lemma. The <form> block contains a number of elements including <orth> and <gramGrp>; the TEI<stress> element, designed for stress patterns given separately, is not applicable here, apart from the fact that we did not want to split up the orthographic representation any further or change it.

Within <orth>typographic details are stored in a @rend attribute. In Johnson's Dictionary we use it to store his typographic differentiation of the printed entries: that is, his distinction between allcaps and small caps. In Schwan's dictionary it is used to distinguish two different orthographic representations of the German lemma, the first with Antiquacapital letters only, the second with upper and lower case, depending on the German orthography, and using aFrakturtypeface.

We use <gramGrp> to collect grammatical information such as part-of-speech (in a <pos> element) or gender (in a <gen> element). Quite often grammatical information precedes or follows the orthographic representation of the entry, such as the infinitive marker To in entries for verbs in Johnson's dictionary or the determiner der, die, das in German noun entries. We capture this information with a <gram> element and a @type attribute containing the appropriate ISOcat value. Without exception we store all elements that interpret grammatical features like <pos>,<gen>,or <gram>within <gramGrp> element, once again using a @norm attribute to map the different grammatical descriptions given in the dictionaries toan ISOcat entry. This way we avoid conflicts with the order of text on the printed page and can adjust inconsistencies like missing word class information, such as by adding an empty <pos> element with a @norm attribute based on information collected elsewhere in the entry. One example is Johnson's entry APPLAUD that requires two <gramGrp> elements to capture the grammatical information: <pb n="148"/><cb n="APP"/> <entry xml:id="sjdict1f.1755.000234.applaud" type="Root"> <lb/><form type="lemma" norm="applaud"> <gramGrp><gram type="infinitiveParticle">To</gram></gramGrp> <orth rend="allcaps">APPLA'UD</orth><pc>.</pc> <gramGrp><pos norm="verb">v.a.</pos></gramGrp> </form> <etym> <pc>[</pc><mentioned xml:lang="la">applaudo</mentioned><pc>,</pc> <lang><abbr>Lat.</abbr></lang><pc>]</pc> </etym> <lb/><sense> <num>1.</num> <def>To praise by clapping the hand.</def> </sense> <lb/><sense> <num>2.</num> <def>To praise in general.</def> </sense> <cit type="example"> <lb/><quote>I would applaud thee to the very echo, <lb/>That should applaud again.</quote> <bibl><author><abbr>Shakesp.</abbr></author><title>Macbeth</title>.</bibl> </cit> <cit type="example"> <lb/><quote>Nations unborn your mighty names shall sound, <lb/>And worlds applaud that must not yet be found!</quote> <bibl><author>Pope</author>.</bibl> </cit> </entry> Our use of <pc> is governed by the principle that we avoid punctuation marks as delimiters of text in elements within <form> and within <etym>; this is for ease of reusability and searching.

In testing our encoding concept we encountered some phenomena-word class in grammar and hyphenation in orthography-which prompted us to reinforce our aim of consistently modelling heterogenous lexicographical data through normalization. The first case has to do with an old problem of word classes: the categories of adjective and adverb in German. Ebers defines the part-of-speech information in his entry fähig with the abridged terms in Latin adj. et adv. This concept-one word, two word classes-is not compatible with the present-day understanding of word classes in German: since adverbs in German are never inflected and fähig is capable of inflection, this word is generally regarded as an adjective in any present-day dictionary of German. Of course, we do not alter Ebers' word class definition, but we suggest resolving the word class conflict in this and in comparable cases by standardizing the value of the @norm attribute on<pos>, using the ISOcat value /adjective/ only. Ebers' example entry fähig in abridged form: <entry xml:id="jedictge.1796.000999.fähig" type="main"> <form xml:lang="de" type="lemma" norm="fähig"> <lb/><orth>Fähig</orth><pc>,</pc> <gramGrp> <pos norm="adjective" xml:lang="la">adj. et adv.</pos> </gramGrp> </form> <sense> ... </sense> </entry>

The second phenomenon has to do with hyphenation, an old problem primarily but not only in the English language. First, consider Johnson's noun compounds with apple in abridged form: <entry xml:id="sjdict1f.1755.000347.apple-graft" type="derivation"> <form type="lemma" norm="apple graft"> <lb/><orth rend="smallcaps">APPLE-GRAFT</orth><pc>.</pc> <gramGrp><pos norm="noun">n.s.</pos></gramGrp> </form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.009999.graft">graft</mentioned> <pc>.]</pc> </etym> <sense> ... </sense> </entry> <entry xml:id="sjdict1f.1755.000348.apple-tart" type="derivation"> <form type="lemma" norm="apple tart"> <lb/><orth rend="smallcaps">APPLE-TART</orth><pc>.</pc> <gramGrp><pos norm="noun"/></gramGrp> </form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned> <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.029999.tart">tart</mentioned> <pc>.]</pc> </etym> <sense> ... </sense> </entry> <entry xml:id="jdict1f.1755.000349.apple_tree" type="derivation"> <form type="lemma" norm="apple tree"> <lb/><orth rend="smallcaps">APPLE TREE</orth><pc>.</pc> <gramGrp><pos norm="noun"><abbr>n.s.</abbr></pos></gramGrp> </form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned> <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.039999.tree">tree</mentioned> <pc>.]</pc> </etym> <sense> ... </sense> </entry <entry xml:id="jdict1f.1755.000350.apple_woman" type="derivation"> <form type="lemma" norm="apple woman"> <lb/><orth rend="smallcaps">APPLE WOMAN</orth><pc>.</pc> <gramGrp><pos norm="noun"><abbr>n.s.</abbr></pos></gramGrp> </form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned> <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.049999.woman">woman</mentioned> <pc>.]</pc> </etym> <sense> ... </sense> </entry> Apart from the special case -APPLEof love,‖ both -APPLE-GRAFT‖ and -APPLE-TART‖ are hyphenated, whereas -APPLE TREE‖ and -APPLE WOMAN‖ are spelled as two separate words. There is no consistent distinction here between open (word-spaced) and hyphenated compounds. Noel Osselton gives a compact résumé of -variation of hyphenated compounds‖in entries and their steady downgrading in the second half of the dictionary from the letter M onwards (2005). Against this background we have usedthe @norm attribute of <form> in order to provide the best support for search procedures: we have retained the original hyphenated and open compound spellings from Johnson's text but have encoded the open or word-spaced form on the @norm attribute as the standardized form.

In his translation of Johnson's apple entries, Adelung takes a different view. He unifies the hyphenated spelling for all the apple compounds, downgrades the hybrid entry Apple of love to appear as a form mentioned within the base entry apple,and adds more compounds, taken from other sources mentioned in the introduction: <entry xml:id="jagkwbed.1783.000999.apple" type="main"> <form xml:lang="en" type="lemma" norm="apple"> <lb/><orth>'Apple</orth><pc>,</pc> <gramGrp> <pos norm="noun" xml:lang="la">subst.</pos> </gramGrp> <pc>(</pc><pron>äpp'l</pron><pc>,</pc> </form> <etym><mentioned><lang xml:lang="ang">angels.</lang> <lang xml:lang="nds">niederd.</lang>aep-<lb/>pel</mentioned> <pc>,</pc><mentioned><lang xml:lang="de">deutsch</lang> Apfel</mentioned> <pc>.</pc><pc>)</pc> </etym> <sense xml:lang="de"> <num>1)</num> <def>Die Frucht des <lb/>Apfelbaumes,</def> <cit type="translation"><quote>der Apfel.</quote></cit> </sense> <sense xml:lang="de"> <num>2)</num> <cit type="Encyclopedic_Information"> <quote>Wegen eini-<lb/>ger Ähnlichkeit in der Gestalt ...</quote> </cit> <cit type="Encyclopedic_Information"> <quote><mentioned xml:lang="en">The Apple of love, Love-apple</mentioned> o-<lb/>der <mentioned xml:lang="en">Wolf's Peach</mentioned>, <cit type="translation" xml:lang="de"><quote>Liebesapfel</quote> </cit> <term xml:lang="la">Lycoper-<lb/>sicon<name nymRef="Linné">Linn.</name> </term>auch wohl eine Art des <term xml:lang="la">Sola-<lb/>num</term>; <mentioned xml:lang="en">the Mad-apple</mentioned>, </sense> <sense xml:lang="de"> <num>3)</num> <usg>Figürlich,</usg><def>die Pupille in dem Auge,</def> <cit type="translation"><quote>der <lb/>Augapfel,</quote></cit> <xr type="synonym "><lbl>welcher wohl auch <ref xml:lang="en" target="#adwbeng1.1783.009999.eye-ball"> Eye-ball</ref> ge-<lb/>nannt wird.</lbl> </xr> </sense> </entry> <entry xml:id="jagkwbed.1783.001000.apple-coar" type="main"> <form xml:lang="en" type="lemma" norm="apple coar"> <lb/><orth>'Apple-coar</orth><pc>,</pc> <gramGrp<pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <etym><lbl>von</lbl> <mentioned xml:lang="en" corresp="#jagkwbed.1783.000999.apple"> apple 1)</mentioned> </etym> <sense> <def>der Griebs oder Gröbs in dem Apfel.</def> </sense> </entry> <entry xml:id="jagkwbed.1783.001001.apple-graft" type="main"> <form xml:lang="en" type="lemma" norm="apple graft"> <lb/><orth>'Apple-graft</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001002.apple-loft" type="main"> <form xml:lang="en" type="lemma" norm="apple loft"> <lb/><orth>'Apple-loft</orth><pc>,</pc> <gramGrp<pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001003.apple-monger" type="main"> <form xml:lang="en" type="lemma" norm="apple monger"> <lb/><orth>'Apple-monger</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001004.apple-paring" type="main"> <form xml:lang="en" type="lemma" norm="apple paring"> <lb/><orth>'Apple-paring</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001005.apple-roaster" type="main"> <form xml:lang="en" type="lemma" norm="apple roaster"> <lb/><orth>'Apple-roaster</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed1.1783.001006.apple-squire" type="main"> <form xml:lang="en" type="lemma" norm="apple squire"> <lb/><orth>'Apple-squire</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001007.apple-tart" type="main"> <form xml:lang="en" type="lemma" norm="apple tart"> <lb/><orth>'Apple-tart</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001008.apple-thorn" type="main"> <form xml:lang="en" type="lemma" norm="apple thorn"> <lb/><orth>'Apple-thorn</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001009.apple-tree" type="main"> <form xml:lang="en" type="lemma" norm="apple tree"> <lb/><orth>'Apple-tree</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> <entry xml:id="jagkwbed.1783.001010.apple-woman" type="main"> <form xml:lang="en" type="lemma" norm="apple woman"> <lb/><orth>'Apple-woman</orth><pc>,</pc> <gramGrp><pos norm="noun" xml:lang="la">subst.</pos></gramGrp> </form> <sense>...</sense> </entry> These examples illustrate that, despite differences in detail, the <entry> and <form>information can be encoded using the same pattern. Missing standard information (like wordclass) can be supplied without modification of the transcription of the printed text. Even if the encoding cuts into typographical structures (such as<pron> in Adelung's dictionary), it does not corrupt the transcription.

<etym>Between Etymology and Word-Formation

As noted above, Johnson emphasized the importance of etymology in his preface. Accordingly, he openshis dictionary with a grammar, and in the introduction to the chapter Of DERIVATIONJohnson explains, "That the English language may be more easily made understood, it is necessary to enquire how its derivative words are deduced from their primitives, and how the primitives are borrowed from other languages" (1755, 47). In compound word entries he uses square brackets following the part-ofspeech information to mark the root components of the compound-his derivatives (for example, in APPLE-GRAFT: [from apple and graft]); for root entries he provides information about related words in Indo-European, Romance or Germanic languages, if necessary with an English translation (for example, in ABLE: [habile, Fr. habilis, Lat. Skilful, ready.]). In accordance with Johnson's method,we use the <etym>element for both cases. The <etym> element requires no additional attribute to distinguish these two cases since its content structure clearly indicates to what type of entry a given <etym> belongs and how it isto be interpreted: <entry xml:id="sjdict1f.1755.000123.able" type="Root"> <form>...</form> <etym><pc>[</pc> <mentioned xml:lang="fr" >habile</mentioned><pc>,</pc> <lang><abbr>Fr.</abbr></lang> <mentioned xml:lang="la">habilis</mentioned><pc>,</pc> <lang><abbr>Lat.</abbr></lang> <lb/><gloss xml:lang="en">Skilful<pc>,</pc> ready<pc>.</pc> </gloss><pc>]</pc> </etym>

In the encoding of the entry ABLE above, the content of <etym> consists of two <mentioned> elements,each with a <lang> and possibly a<gloss>, meaningit must be a root entry.

<entry xml:id="sjdict1f.1755.000347.apple-graft" type="derivation"> <form>...</form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.009999.graft">graft</mentioned> <pc>.]</pc> </etym>

In the encoding of the entry APPLE-GRAFT, the content of <etym> consists of two <mentioned> elements, eachwith a @corresp attribute that points to other entries within the same dictionary, indicating a derivation. While the effort of identifying the target entry and inserting the corresponding @xml:id attribute is not insignificant, from our point of view the resulting network of linked entries is worth the effort.

Stepwise Refinement of <sense>: <num>,<def>, and <gramGrp> with <gram>

The function of <sense> as a container for the semasiological information of dictionary entries was explained the first half of this paper. Some sections of the encoding of ABLE can illustrate the flexibility of the concept of crystals for the encoding of complex semantic structures. The first step of refinement adds <num>elements to label the different <sense>s.

<entry xml:id="sjdict1f.1755.000123.able" type="Root"> <form> ... </form> <etym> ... </etym> <sense> <lb/><num>1.</num> <def>...</def><cit>...</cit><cit>...</cit> </sense> <sense> <lb/><num>2.</num> <def>Having power sufficient; enabled.</def> <cit type="example"> <lb/><quote>All mankind acknowledge themselves able and sufficient to <lb/> do many things, which actually they never do. </quote> <bibl><author>South</author>'s <title>Serm.</title></bibl> </cit> </sense> <sense> <lb/><num>3.</num> <gramGrp> <gram type="syntax">Before a verb, with the participle <hi rend="italics">to</hi></gram> </gramGrp>, <def>it signifies generally hav-<lb/>ing the power</def>; <gramGrp> <gram type="syntax">before a noun, with <hi rend="italics">for</hi></gram> </gramGrp>, <def> it means <hi>qualified</hi></def>. <!--instances of <cit type="example"> omitted for brevity --> </sense>

In a second step-<num>3.</num>-one <sense>-element is used to combine the morpho-syntactic features -able + to before a verb" in the <gramGrp>container with the semasiological definition -signifies generally having the power‖ contained in the <def>element. In a different construction with able, the morpho-syntactic feature -before a noun, with for‖ in <gramGrp> and <gram> is connected with the definition ‗it means qualified' in <def>.While we usually find grammatical information in a kind of shorthand in the source, which is likewise encoded briefly: <gramGrp><pos norm="noun">n.s.</pos></gramGrp>.

for ABLE we have a discursive example, which as such is interesting not only in its own right but also because itcombinestwoclearly distinct syntactic structuresand divergent semantic paraphrases into one sense. The <cit>examples that follow in sense number 3 repeat the structures and illustrate both usages:

<cit type="example"> <lb/><quote>Wrath is cruel, and anger is outrageous; but who is able <lb/> to stand before envy?</quote> <bibl><title>Prov.</title> <biblScope type="part">xxvii.</biblScope> <biblScope type="ll">4.</biblScope> </bibl> </cit> <cit type="example"> <lb/><quote>There have been some inventions also, which have been <lb/>able for the utterance of articulate sounds, as the speaking of <lb/>certain words.</quote> <bibl><author> Wilkin</author>'s <title>Mathematical Magic</title>. </bibl> </cit>

The phrases able to and able for are marked by italics in the print dictionary, but this was not captured in the encoding. Furthermore, while the refinement of the encoding could be extended to word level <cit type="translation" xml:lang="fr"> <quote>réhabi-<lb/>liter qq. un.</quote></cit> </sense> </entry> With the exception of two phrases--Dinge, die nicht jedermann zu verstehen fähig ist‖ and -Er ist nicht fähig euch in geringsten zu schaden‖-Ebers has copied the German text of Schwan's dictionary and replaced the French translation equivalents by English ones. The encoding problems remain the same and we think that the solution we propose is adequate.

Conclusion

Above we applied our encoding suggestions for the <form>block to Johnson's entry To APPLAUD but did not comment on the unusual structure of the elements <sense> and <cit>: two numbered senses, followed by two quotations. A look at the last edition (the fourth folio edition of 1773), which was considerably revised and prepared for publication by Johnson himself, can make the author's original intentions clearer. Thanks to Anne McDermott's excellent CD-ROM edition, published in 1996, we have access to an SGML encoding of the texts of both the first and fourth folio editions and can not only compare the texts themselves but also the change over the years from TEI P3 SGML of 1994 to the current P5 using XML Schema:

First folio edition [TEI P5]:

<entry xml:id="sjdict1f.1755.000234.applaud" type="Root" > <lb/><form type="lemma" norm="applaud"> <gram type="infinitiveParticle">To</gram> <orth rend="allcaps">APPLA'UD</orth><pc>.</pc> <gramGrp><pos norm="verb">v.a.</pos></gramGrp> </form> <etym> <pc>[</pc><mentioned xml:lang="la">applaudo</mentioned><pc>,</pc> <lang><abbr>Lat.</abbr></lang><pc>]</pc> </etym> <lb/><sense> <num>1.</num> <def>To praise by clapping the hand.</def> </sense> <lb/><sense> <num>2.</num> <def>To praise in general.</def> </sense> <cit type="example"> <lb/><quote>I would applaud thee to the very echo, <lb/>That should applaud again.</quote> <bibl><author><abbr>Shakesp.</abbr></author><title>Macbeth</title>.</bibl> </cit> <cit type="example"> <lb/><quote>Nations unborn your mighty names shall sound, <lb/>And worlds applaud that must not yet be found!</quote> <bibl><author>Pope</author>.</bibl> </cit> </entry>

Ann McDermott Fourth folio edition [TEI P3 SGML]:

<ENTRYFREE ID="J4APPLAUD-1" N="1999" TYPE="4">IV <FORM> <HI REND="ital">To</HI><HI REND="acp">APPLA'UD.</HI> </FORM>

Figure 1 :

 1 Figure 1: The Lexical Entry sub-structure of the LMF core package

Figure 2 :

 2 Figure 2:The ideal element-class organisation of a TEI lexical entry

Figure 3 :

 3 Figure 3: An LMF extension for quotations represented in a dictionaryIn the TEI Guidelines, the quotation construct is implemented by means of the <cit> element, which has the following characteristics: The quoted object may be realized not only by means of a <quote> or <q>(both from the model.qLike class) but also as a more elaborated construct such as an XML object (<egXML>, a member ofmodel.egLike)

Some LMF packages, such as the description of subcategorisation frames, do not yet have any equivalence in the TEI vocabulary, but the TEI extension mechanisms do facilitate the description of such extensions.

Note that some of the changes proposed in this paper (in particular regarding the systematic use of <sense>) have already been integrated into the December 2011 release (2.0.0, Laurentian).

Ideally, this should correspond to model.formPart, but in the current version of the TEI Guidelines this class is cluttered with other components which are there for purely syntactic (practical) reasons. We would limit this class to form <orth>, <pron>, <hyph>, <syll>, and <stress>.

Even if this is not allowed in the <entry> element, form representations still appear in : cit, dictScrap, entryFree, and nym, because of theirs membership to model.entryPart.

http://www.isocat.org/

and features of a fine-grain morpho-syntactical analysis, this is beyond what we want to illustrate in this paper. Therefore we have just encoded to support analysis of syntax.

Bilingual Dictionaries: AShift of Perspective

The consistent modelling of heterogeneous lexical structurescan be extended to the more complex structures we find in the two bilingual dictionaries, Adelung's English-German translation of Johnson's dictionary (1783Johnson's dictionary ( -1796) ) and Ebers' New and Complete Dictionary of the German and EnglishLanguages(1796), compiled using Adelung's and Schwan's lexicographical materials. Nevertheless a comparable precision in the encoding can be achieved. Let us first compare the entry Apple-tart in Johnson's dictionary and Adelung's translation: <entry xml:id="sjdict1f.1755.000348.apple-tart" type="derivation"> <form type="lemma" norm="apple tart"> <lb/><orth rend="smallcaps">APPLE-TART</orth><pc>.</pc> <gramGrp><pos norm="noun"/></gramGrp> </form> <etym><pc>[</pc>from <mentioned corresp="#sjdict1f.1755.000345.apple">apple</mentioned> <lbl>and</lbl> <mentioned corresp="#sjdict1f.1755.029999.tart">tart</mentioned> <pc>.]</pc> </etym> <sense> <def>A tart made of apples.</def> <cit type="example"> <lb/><quote>What, up and down carv'd like an apple-tart.</quote> <lb/><bibl><author>Shakespeare</author>'s <title>Taming of the Shrew</title>. </bibl> </cit> </sense> </entry> <entry xml:id="jagkwbed.1783.001007.apple-tart" type="main"> <form xml:lang="en" type="lemma" norm="apple tart"> <lb/><orth>'Apple-tart</orth><pc>,</pc> <gramGrp><pos norm="noun"xml:lang="la">subst.</pos></gramGrp> </form> <sense xml:lang="de"> <def>eine Torte von Ä-<lb/>pfeln,</def> <cit type="translation"><quote>eine Äpfeltorte.</quote></cit> </sense> </entry>

In contrast to Johnson, Adelung, meeting the requirements of an English-German dictionary, left out the <etym>element on word-formation and the Shakespeare quotation and added the word-class information. He translated Johnson's definition of apple-tart almost literally into German and then added the slightly strange German compound Äpfeltorte.

The encoding of the translation becomes more complex because of the mix of two languages which requires an additional control of the extension and inheritance of the @xml:lang attribute. The use of the German plural form Äpfelin Äpfeltortemay have been inspired by Johnson's plural definition and the fact that a decent apple-tart requires more than one apple. Ten years later, in Adelung's monolingual German dictionary, the entry shows no umlaut and the definition is derived from a recipe that puts the sliced apples on top (1793-1801, vol.1, 412).

In a final look at Ebers' German-English dictionary, the randomly chosen sample entry fähig shows the problems in encoding bilingual dictionaries when translation from mother-tongue into a foreign language is involved.

<PB SIG="Bb2r" MACFILE=":4:100:148.CAL" PCFILE="4\100\148.CAL"> <POS><HI REND="ital">v.a.</HI></POS> <ETYM>[<HI REND="ital">applaudo,</HI> Lat.]</ETYM> <SENSE N="1"> <DEF> <NUM>1.</NUM> To praise by clapping the hand. </DEF> <EG TYPE="verse"> <QUOTE> <L>I would <HI REND="ital">applaud</HI> thee to the very echo,</L> <L>That should <HI REND="ital">applaud</HI> again.</L> </QUOTE> <AUTHOR><HI REND="ital">Shakesp.</HI></AUTHOR> <TITLE><HI REND="ital">Macbeth.</HI></TITLE> </EG> </SENSE> <SENSE N="2"> <DEF> <NUM>2.</NUM> To praise in general. </DEF> <EG TYPE="verse"> <QUOTE> <L>Nations unborn your mighty names shall sound,</L> <L>And worlds <HI REND="ital">applaud</HI> that must not yet be sound!</L> </QUOTE> <AUTHOR><HI REND="ital">Pope.</HI> </AUTHOR> </EG> </SENSE> </ENTRYFREE> We can conclude: 1. The transcription of the entry APPLAUD in the SGML version of the fourth folio edition shows clearly that Johnson had intended to illustrate each definition with an illustrative quotation, as elsewhere in the dictionary, and that theunusual structure of the first folio text-two numbered senses, followed by two quotations-is simply a typesetting error.

2. Both encodings have many structural features in common: with the exception of <cit> and <pc> all elements used in our encoding were available in TEI P3, whereas the mechanisms usable at the attribute level are not comparable. But the main difference is the style of the encoding: although the SGML version is very close to the typography of the text, our encoding, using crystals, aims more at interpreting typographical detail in order to capture lexicographic and linguistic data and to constrain encoding options in favour of robust interoperability and reusability of resources.