9 Dictionaries
內容
This chapter defines a module for encoding lexical resources of all kinds, in particular human-oriented monolingual and multilingual dictionaries, glossaries, and similar documents. The elements described here may also be useful in the encoding of computational lexica and similar resources intended for use by language-processing software; they may also be used to provide a rich encoding for wordlists, lexica, glossaries, etc. included within other documents. Dictionaries are most familiar in their printed form; however, increasing numbers of dictionaries exist also in electronic forms which are independent of any particular printed form, but from which various displays can be produced.
Both typographically and structurally, print dictionaries are extremely complex. Such lexical resources are moreover of interest to many communities with different and sometimes conflicting goals. As a result, many general problems of text encoding are particularly pronounced here, and more compromises and alternatives within the encoding scheme may be required in the future.36 Two problems are particularly prominent.
First, because the structure of dictionary entries varies widely both among and within dictionaries, the simplest way for an encoding scheme to accommodate the entire range of structures actually encountered is to allow virtually any element to appear virtually anywhere in a dictionary entry. It is clear, however, that strong and consistent structural principles do govern the vast majority of conventional dictionaries, as well as many or most entries even in more ‘exotic’ dictionaries; encoding guidelines should include these structural principles. We therefore define two distinct elements for dictionary entries, one (entry) which captures the regularities of many conventional dictionary entries, and a second (entryFree) which uses the same elements, but allows them to combine much more freely. It is however recommended that entry be used in preference to entryFree wherever possible. These elements and their contents are described in sections 9.2 The Structure of Dictionary Entries, 9.6 Unstructured Entries, and 9.4 Headword and Pronunciation References.
Second, since so much of the information in printed dictionaries is implicit or highly compressed, their encoding requires clear thought about whether it is to capture the precise typographic form of the source text or the underlying structure of the information it presents. Since both of these views of the dictionary may be of interest, it proves necessary to develop methods of recording both, and of recording the interrelationship between them as well. Users interested mainly in the printed format of the dictionary will require an encoding to be faithful to an original printed version. However, other users will be interested primarily in capturing the lexical information in a dictionary in a form suitable for further processing, which may demand the expansion or rearrangement of the information contained in the printed form. Further, some users wish to encode both of these views of the data, and retain the links between related elements of the two encodings. Problems of recording these two different views of dictionary data are discussed in section 9.5 Typographic and Lexical Information in Dictionary Data, together with mechanisms for retaining both views when this is desired.
To deal with this complexity, and in particular to account for the wide variety of linguistic contexts within which a dictionary may be designed, it can be necessary to customize or change the schema by providing more restriction or possibly alternate content models for the elements defined in this chapter. Section 9.3.2 Grammatical Information illustrates this with the provision of a closed set of values for grammatical descriptors.
This chapter contains a large number of examples taken from existing print dictionaries; in each case, the original source is identified. In presenting such examples, we have tried to retain the original typographic appearance of the example as well as presenting a suggested encoding for it. Where this has not been possible (for example in the display of pronunciation) we have adopted the transliteration found in the electronic edition of the Oxford Advanced Learner's Dictionary. Also, the middle dot in quoted entries is rendered with a full stop, while within the sample transcriptions hyphenation and syllabification points are indicated by a vertical bar |, regardless of their appearance in the source text.
TEI: Dictionary Body and Overall Structure¶9.1 Dictionary Body and Overall Structure
Overall, dictionaries have the same structure of front matter, body, and back matter familiar from other texts. In addition, this module defines entry, entryFree, and superEntry as component-level elements which can occur directly within a text division or the text body.
The following tags can therefore be used to mark the gross structure of a printed dictionary; the dictionary-specific tags are discussed further in the following section.
- text 包含一份任何種類的文本,無論是單一或複合的,例如詩詞或戲劇、散文集、小說、字典、或是文集範例。
- front (正文前資訊) 包含位於文件最前端、正文之前的項目 (標頭、題名頁、前言、獻詞等) 。
- body (正文) 單篇文章的整體部分,不包含正文前及正文後資訊。
- back (正文後資訊) 在正文之後,包含附錄等。
- div (文本區段) 文本的正文前資訊、正文、及正文後資訊的分段。
- entry 包含字典中一個結構完善的辭條項目。
- entryFree 所包含的辭條項目未必符合元素entry該有的限制條件。
- superEntry 匯集一組同形異義字的連續辭條。
As members of the classes att.entryLike and att.sortable, entry and entryFree share the following attributes:
- att.entryLike 匯集不同格式的字典辭條
type 指出複合類型字典中的辭條類型。 被推薦的值包含: 1] main; 2] hom (homograph); 3] xref (cross reference); 4] affix; 5] abbr (abbreviation); 6] supplemental; 7] foreign - att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content.
sortKey supplies the sort key for this element in an index, list or group which contains it.
The front and back matter of a dictionary may well contain specialized material such as lists of common and proper nouns, grammatical tables, gazetteers, a ‘guide to the use of the dictionary’, etc. These should be tagged using elements defined elsewhere in these Guidelines, chiefly in the core module (chapter 3 Elements Available in All TEI Documents) together with the specialized dictionary elements defined in this chapter.
<div>
<head>English-French</head>
<entry>
<form>
<orth>cat</orth>
</form>
<!-- ... -->
</entry>
<entry>
<form>
<orth>dog</orth>
</form>
<!-- ... -->
</entry>
<entry>
<form>
<orth>horse</orth>
</form>
<!-- ... -->
</entry>
</div>
<div>
<head>French-English</head>
<entry>
<form>
<orth>chat</orth>
</form>
<!-- ... -->
</entry>
<entry>
<form>
<orth>chien</orth>
</form>
<!-- ... -->
</entry>
<entry>
<form>
<orth>cheval</orth>
</form>
<!-- ... -->
</entry>
</div>
</body>
In a print dictionary, the entries are typically typographically distinct entities, each headed by some morphological form of the lexical item described (the headword), and sorted in alphabetical order or (especially for non-alphabetic scripts) in some other conventional sequence. Dictionary entries should be encoded as distinct successive items, each marked as an entry or entryFree element. The type attribute may be used to distinguish different types of entries, for example main entries, related entries, run-on entries, or entries for cross-references, etc.
Some dictionaries provide distinct entries for homographs, on the basis of etymology, part-of-speech, or both, and typically provide a numeric superscript on the headword identifying the homograph number. In these cases each homograph should be encoded as a separate entry; the superEntry element may optionally be used to group such successive homograph entries. In addition to a series of entry elements, the superEntry may contain a preliminary form group (see section 9.3.1 Information on Written and Spoken Forms) when information about hyphenation, pronunciation, etc., is given only once for two or more homograph entries. If the homograph number is to be recorded, the global attribute n may be used for this purpose. In some dictionaries, homographs are treated in distinct parts of the same entry; in these cases, they may be separated by use of the hom element, for which see section 9.2.1 Hierarchical Levels.
A sort key, given in the sortKey attribute, is often required for superentries and entries, especially in cases where the order of entries does not follow the local character-set collating sequence (as, for example, when an entry for ‘3D’ appears at the place where ‘three-D’ would appear).
<entry>
<form>
<orth>manifestation</orth>
<!-- demonstration -->
</form>
</entry>
<entry>
<form>
<orth>émeute</orth>
<!-- riot -->
</form>
</entry>
<superEntry>
<entry type="hom" n="1">
<form>
<orth>grève</orth>
<!-- strike -->
</form>
</entry>
<entry type="hom" n="2">
<form>
<orth>grève</orth>
<!-- shore -->
</form>
</entry>
</superEntry>
</body>
TEI: The Structure of Dictionary Entries¶9.2 The Structure of Dictionary Entries
A simple dictionary entry may contain information about the form of the word treated, its grammatical characterization, its definition, synonyms, or translation equivalents, its etymology, cross-references to other entries, usage information, and examples. These we refer to as the constituent parts or constituents of the entry; some dictionary constituents possess no internal structure, while others are most naturally viewed as groups of smaller elements, which may be marked in their own right. In some styles of markup, tags will be applied only to the low-level items, leaving the constituent groups which contain them untagged. We distinguish the class of top-level constituents of dictionary entries, which can occur directly within the entry element, from the class of phrase-level constituents, which can normally occur only within top-level constituents. The top-level constituents of dictionary entries are described in section 9.2.2 Groups and Constituents, and documented more fully, together with their phrase-level sub-constituents, in section 9.3 Top-level Constituents of Entries.
In addition, however, dictionary entries often have a complex hierarchical structure. For example, an entry may consist of two or more sub-parts, each corresponding to information for a different part-of-speech homograph of the headword. The entry (or part-of-speech homographs, if the entry is split this way) may also consist of senses, each of which may in turn be composed of two or more sub-senses, etc. Each sub-part, homograph entry, sense, or sub-sense we call a level; at any level in an entry, any or all of the constituent parts of dictionary entries may appear. The hierarchical levels of dictionary entries are documented in section 9.2.1 Hierarchical Levels.
TEI: Hierarchical Levels¶9.2.1 Hierarchical Levels
The outermost structural level of an entry is marked with the elements entry or entryFree. The hom element marks the subdivision of entries into homographs differing in their part-of-speech. The sense element marks the subdivision of entries and part-of-speech homographs into senses; this element nests recursively in order to provide for a hierarchy of sub-senses of any depth. It is recommended to use the sense element even for an entry that has only one sense to group together all parts of the definition relating to the word sense since this leads to more consistent encoding across entries. All of these levels may each contain any of the constituent parts of an entry. A special case of hierarchical structure is represented by the re (related entry) element, which is discussed in section 9.3.6 Related Entries. Finally, the element dictScrap may be used at any point in the hierarchy to delimit parts of the dictionary entry which are structurally anomalous, as further discussed in section 9.6 Unstructured Entries.
- entry 包含字典中一個結構完善的辭條項目。
- entryFree 所包含的辭條項目未必符合元素entry該有的限制條件。
- hom (同形義異字) 匯集辭條中一個同形義異字的相關資訊。
- sense 匯集辭條中一個字義的所有相關資訊(定義、範例、翻譯等)。
level 說明該字義在辭條中的層次。 - dictScrap 字典辭條的片段,包含自由組合的詞組層次字典元素。
<hom n="1">
<sense n="1">
<!-- ... -->
</sense>
<sense n="2">
<!-- ... -->
</sense>
</hom>
<hom n="2">
<sense n="1">
<sense n="a">
<!-- ... -->
</sense>
<sense n="b">
<!-- ... -->
</sense>
</sense>
<sense n="2">
<!-- ... -->
</sense>
<sense n="3">
<!-- ... -->
</sense>
</hom>
</entry>
<entry n="1" type="hom">
<sense n="1">
<!-- ... -->
</sense>
<sense n="2">
<!-- ... -->
</sense>
</entry>
<entry n="2" type="hom">
<sense n="1">
<sense n="a">
<!-- ... -->
</sense>
<sense n="b">
<!-- ... -->
</sense>
</sense>
<sense n="2">
<!-- ... -->
</sense>
<sense n="3">
<!-- ... -->
</sense>
</entry>
</superEntry>
The hierarchic structure of a dictionary entry is enforced by the structures defined in this module. The content model for entry specifies that entries do not nest, that homographs nest within entries, and that senses nest within entries, homographs, or senses, and may be nested to any depth to reflect the embedding of sub-senses. Any of the top-level constituents (def, usg, form, etc.) can appear at any level (i.e., within entries, homographs, or senses).
TEI: Groups and Constituents¶9.2.2 Groups and Constituents
As noted above, dictionary entries, and subordinate levels within dictionary entries, may comprise several constituent parts, each providing a different type of information about the word treated. The top-level constituents of dictionary entries are:
- information about the form of the word treated (orthography, pronunciation, hyphenation, etc.)
- grammatical information (part of speech, grammatical sub-categorization, etc.)
- definitions or translations into another language
- etymology
- examples
- usage information
- cross-references to other entries
- notes
- entries (often of reduced form) for related words, typically called related entries
Any of the hierarchical levels (entry, entryFree, hom, and sense) may contain any of these top-level constituents, since information about word form, particular grammatical information, special pronunciation, usage information, etc., may apply to an entire entry, or to only one homograph, or only to a particular sense. The examples below illustrate this point.
The following elements are used to encode these top-level constituents:
- form (形式資訊群) 匯集一個標題字在書寫及發音形式方面的所有資訊。
- gramGrp (文法資訊群) 匯集文字的型態及句法資訊,例如詞性、性別、單複數、格、或屈折變化種類。
- def (定義) 包含詞條中的定義文。
- cit 從其他文件中引用的內容,並包含引用來源的書目參照資料。
- usg (字詞使用資訊) 包含辭條中的使用資訊。
- xr (交互參照) 包含一字詞、句子、或圖象,用以參照到相同文本或不同文本中的其他位置。
- etym (詞源) 包含詞源學資訊。
- re (相關辭條) 和標題字相關聯的字典辭條,像是包括在一個更大辭條中的複合片語或衍生字。
- note 包含附註或註釋。
<form>
<orth>competitor</orth>
<hyph>com|peti|tor</hyph>
<pron>k@m"petit@(r)</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<def>person who competes.</def>
</entry>
<form>
<orth>disproof</orth>
<pron notation="ipa">dɪsˈpru:v</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>facts that disprove something</def>
</sense>
<sense n="2">
<def>the act of disproving</def>
</sense>
</entry>
For ease of processing of such entries containing multiple senses along with those containing only a single sense, it is recommended to use sense in all entries to wrap those elements relating to a particular word sense.
<form>
<orth>bray</orth>
<pron>breI</pron>
</form>
<hom>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense>
<def>cry of an ass; sound of a trumpet.</def>
</sense>
</hom>
<hom>
<gramGrp>
<pos>vt</pos>
<subc>VP2A</subc>
</gramGrp>
<sense>
<def>make a cry or sound of this kind.</def>
</sense>
</hom>
</entry>
/k@"ri:n/
vt,vi 1 [VP6A] turn (a ship) on one side for cleaning, repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side. OALD<form>
<orth>careen</orth>
<hyph>ca|reen</hyph>
<pron>k@"ri:n</pron>
</form>
<gramGrp>
<pos>vt</pos>
<pos>vi</pos>
</gramGrp>
<sense n="1">
<gramGrp>
<subc>VP6A</subc>
</gramGrp>
<def>turn (a ship) on one side for cleaning, repairing, etc.</def>
</sense>
<sense n="2">
<gramGrp>
<subc>VP6A</subc>
<subc>VP2A</subc>
</gramGrp>
<def>(cause to) tilt, lean over to one side.</def>
</sense>
</entry>
/@"band@n/
v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the burning ship. 2 …abandon 2 n [U] the state when one's feelings and actions are uncontrolled; freedom from control...LDOCE<form>
<orth>abandon</orth>
<hyph>a|ban|don</hyph>
<pron>@"band@n</pron>
</form>
<entry n="1">
<gramGrp>
<pos>v</pos>
<subc>T1</subc>
</gramGrp>
<sense n="1">
<def>to leave completely and for ever … </def>
</sense>
<sense n="2"/>
</entry>
<entry n="2">
<gramGrp>
<pos>n</pos>
<subc>U</subc>
</gramGrp>
<sense>
<def>the state when one's feelings and actions are uncontrolled; freedom
from control…</def>
</sense>
</entry>
</superEntry>
TEI: Top-level Constituents of Entries¶9.3 Top-level Constituents of Entries
This section describes the top-level constituents of dictionary entries, together with the phrase-level constituents peculiar to each.
- the form element, which groups orthographic information and pronunciations, is described in section 9.3.1 Information on Written and Spoken Forms
- the gramGrp element, which groups elements for the grammatical characterization of the headword, is described in section 9.3.2 Grammatical Information
- the def element, which describes the meaning of the headword, is described in section 9.3.3 Sense Information
- the etym element and its special phrase-level elements are documented in section 9.3.4 Etymological Information
- the cit element and its specific applications are described in section 9.3.3 Sense Information and section 9.3.5 Other Information
- the usg, lbl, xr, and note elements are described in section 9.3.5 Other Information
- the re element, which marks nested entries for related words, is described in section 9.3.6 Related Entries
TEI: Information on Written and Spoken Forms¶9.3.1 Information on Written and Spoken Forms
Dictionary entries most often begin with information about the form of the word to which the entry applies. Typically, the orthographic form of the word, sometimes marked for syllabification or hyphenation, is the first item in an entry. Other information about the word, including variant or alternate forms, inflected forms, pronunciation, etc., is also often given.
The following elements should be used to encode this information: the form element groups one or more occurrences of any of them; it can also be recursively nested to reflect more complex sub-grouping of information about word form(s), as shown in the examples.
- form (形式資訊群) 匯集一個標題字在書寫及發音形式方面的所有資訊。
type 形式的類型有單一字彙、複合字等。 被推薦的值包含: 1] simple; 2] lemma; 3] variant; 4] compound; 5] derivative; 6] inflected; 7] phrase - orth (拼字形式) 提供字典標題字的拼字形式。
type 提供拼字的類型。 extent [att.partials] indicates whether the pronunciation or orthography applies to all or part of a word. 被推薦的值包含: 1] full (full form); 2] pref (prefix); 3] suff (suffix); 4] inf (infix); 5] part (partial) - pron (發音) 包含該字的一種或多種發音方法。
extent [att.partials] indicates whether the pronunciation or orthography applies to all or part of a word. 被推薦的值包含: 1] full (full form); 2] pref (prefix); 3] suff (suffix); 4] inf (infix); 5] part (partial) - hyph (連字符號) 包含一個標題字的連字符號形式,或者以其他形式呈現的連字符號資訊。
- syll (音節劃分) 包含標題字的音節劃分。
- stress 包含個別標明的標題字重音模式。
- lbl (標籤) 包含字詞形式、範例、翻譯、或其他資訊的標籤,例如縮寫、省略、字面、約略、同義等。
In addition to those listed above, the following elements, which encode morphological details of the form, may also occur within form elements:
- gram (文法資訊) 在字典辭條或專有名詞檔案中,包含某一術語、單字或字彙形式的相關文法資訊。
type 用合適的分類方法將不同的文法資訊加以分類-若是專門術語,可參照 ISO 12620 所指定資料元素類別。 實例值包含: 1] pos (part of speech); 2] gen (gender); 3] num (number); 4] animate; 5] proper - gen (性別) 說明字彙項目的性別。
- number 指出單複數形式。
- case 包含文法上格的資訊。
- per (人稱) 包含字典中有屈折變化單字的人稱形式 (第一、第二、第三等) 。
- tns (時態) 說明某屈折形式的時態。
- mood 包含動詞語氣資訊 (例如直述、假設、祈使語氣等) 。
- iType (屈折變化種類) 指明單字的屈折變化種類。
type 若需要區別曲折變化種類的一般縮寫指標 (例:inv) 以及其他指標,像是詞形變化模式的特殊代碼等,則在此說明指示標記類型。 實例值包含: 1] abbrev; 2] verbTable - pos (詞性) 指明標題字的詞性 (名詞、動詞、形容詞等)
- subc (次要分類) 包含次要分類資訊 (及物 / 不及物、可數 / 不可數等)
- colloc (組合字) 包含標題字的組合字。
Of these, the gram element is most general, and all of the others are synonymous with a gram element with appropriate values (gen, number, case, etc.) for the type attribute.
The use of these elements as children of form is deprecated; instead, they should always be children of a gramGrp within form when describing that particular form of the word.
Different dictionaries use different means to mark hyphenation, syllabification, and stress, and they often use some unusual glyphs (e.g., the ‘middle dot’ for hyphenation). All of these glyphs are in the Unicode character set, as discussed in Character References. When transcribing representations of pronunciation the International Phonetic Alphabet should be used. It may be convenient (as has been done in the text of this chapter) to use a simple transliteration scheme for this; such a scheme should however be properly documented in the header.
<orth>doom-laden</orth>
</form>
<orth>soucoupe</orth>
<pron>sukup</pron>
</form>
For a variety of reasons including ease of processing, it may be desired to split into separate elements information which is collapsed into a single element in the source text; orthography and hyphenation may for example be transcribed as separate elements, although given together in the source text. For a discussion of the issues involved, and of methods for retaining both the presentation form and the interpreted form, see section 9.5 Typographic and Lexical Information in Dictionary Data.
<orth>area</orth>
<hyph>ar|ea</hyph>
<syll>ar|e|a</syll>
</form>
<orth>brag</orth>
</form>
<gramGrp>
<pos>vb</pos>
</gramGrp>
<form type="inflected">
<orth>brags</orth>
<orth>bragging</orth>
<orth>bragged</orth>
</form>
[ORifje]
(7) vt … [C/R]<orth>horrifier</orth>
<pron>ORifje</pron>
<gramGrp>
<iType type="vbtable">7</iType>
<!-- ... -->
</gramGrp>
</form>
<!-- ... -->
<form type="abbrev">
<orth>MTBF</orth>
</form>
<form type="full">
<lbl>abbreviation for</lbl>
<orth>mean time between failures</orth>
</form>
</entry>
<orth>biryani</orth>
<orth>biriani</orth>
<pron notation="ipa">ˌbɪrɪˈa:nɪ</pron>
</form>
<orth>mackle</orth>
<pron notation="ipa">ˈmækᵊl</pron>
</form>
<form>
<orth>macule</orth>
<pron notation="ipa">ˈmækju:l</pron>
</form>
<orth>hospitaller</orth>
<form>
<usg type="geo">US</usg>
<orth>hospitaler</orth>
</form>
<pron notation="ipa">ˈhɒspɪtələ</pron>
</form>
TEI: Grammatical Information¶9.3.2 Grammatical Information
The gramGrp element groups grammatical information, such as part of speech, subcategorization information (e.g., syntactic patterns for verbs, count/mass distinctions for nouns), etc. It can contain any of the morphological elements defined in section 9.3.1 Information on Written and Spoken Forms for form and can appear as a child of entry, form, sense, cit, or any other element containing content about which there is grammatical information. For example, in the entry ‘pinna (ˈpɪnə)
n, pl -nae (-ni:) or -nas CED’, the word defined can be either singular or plural; the ‘pl.’ specification applies only to the inflected forms provided. Compare this with ‘pants (paents) pl. n.’, where ‘pl.’ applies to the headword itself.
<orth>médire</orth>
</form>
<gramGrp>
<pos>v</pos>
<subc>t ind</subc>
<colloc>de</colloc>
</gramGrp>
<orth>médire</orth>
</form>
<gramGrp>
<gram type="pos">v</gram>
<gram type="subc">t ind</gram>
<gram type="collocPrep">de</gram>
</gramGrp>
<orth>isotope</orth>
</form>
<gramGrp>
<pos>adj</pos>
</gramGrp>
<gramGrp>
<pos>n</pos>
<gen>m</gen>
</gramGrp>
<form>
<orth>wits</orth>
<pron notation="ipa">wɪts</pron>
</form>
<gramGrp>
<number>pl</number>
<pos>n</pos>
</gramGrp>
<sense n="1">
<gramGrp>
<number>sometimes singular</number>
</gramGrp>
<def>the ability to reason and act, esp quickly …</def>
</sense>
</entry>
TEI: Sense Information¶9.3.3 Sense Information
Dictionaries may describe the meanings of words in a wide variety of different ways—by means of synonyms, paraphrases, translations into other languages, formal definitions in various highly stylized forms, etc. No attempt is made here to distinguish all the different forms which sense information may take; all of them may be tagged using the def element described in section 9.3.3.1 Definitions.
As a special case it is frequently desirable to distinguish the provision of translation equivalents in other languages from other forms of sense information; the use of <cit type="translation"> (which groups a translation equivalent with related information such as its grammatical description) for this purpose is described in section 9.3.3.2 Translation Equivalents.
TEI: Definitions¶9.3.3.1 Definitions
Dictionary definitions are those pieces of prose in a dictionary entry that describe the meaning of some lexical item. Most often, definitions describe the headword of the entry; in some cases, they describe translated texts, examples, etc.; see <cit type="translation">, section 9.3.3.2 Translation Equivalents, and <cit type="example">, section 9.3.5.1 Examples. The def element directly contains the text of the definition; unlike form and gramGrp, it does not serve solely to group a set of smaller elements. The close analysis of definition text, such as the tagging of hypernyms, typical objects, etc., is not covered by these Guidelines.
<form>
<orth>demigod</orth>
<pron> … </pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<sense n="a">
<def>a being who is part mortal, part god.</def>
</sense>
<sense n="b">
<def>a lesser deity.</def>
</sense>
</sense>
<sense n="2">
<def>a godlike person.</def>
</sense>
</entry>
<form>
<orth>rémoulade</orth>
<pron>Remulad</pron>
</form>
<gramGrp>
<pos>n</pos>
<gen>f</gen>
</gramGrp>
<cit type="translation" xml:lang="en">
<quote>remoulade</quote>
<quote>rémoulade</quote>
<def>dressing containing mustard and herbs</def>
</cit>
</entry>
TEI: Translation Equivalents¶9.3.3.2 Translation Equivalents
Multilingual dictionaries contain information about translations of a given word in some source language for one or more target languages. Minimally, the dictionary provides the corresponding translation in the target language; other material, such as morphological information (gender, case), various kinds of usage restrictions, etc., may also be given. If translation equivalents are to be distinguished from other kinds of sense information, they may be encoded using <cit type="translation">. The global xml:lang attribute should be used to specify the target language.
As in monolingual dictionaries, the sense element is used in multilingual dictionaries to group information (forms, grammatical information, usage, translation(s), etc.) about a given sense of a word where necessary. Information about the individual translation equivalents within a sense is grouped using <cit type="translation">. This information may include the translation text (tagged q or quote), morphological information (gen, case, etc.), usage notes (usg), translation labels (lbl), and definitions (def).When bibliographic data is provided, the quote element should be used.
<form>
<orth>dresser</orth>
</form>
<sense n="a">
<sense>
<usg type="dom">Theat</usg>
<cit type="translation" xml:lang="fr">
<quote>habilleur</quote>
<gramGrp>
<gen>m</gen>
</gramGrp>
</cit>
<cit type="translation" xml:lang="fr">
<quote>-euse</quote>
<gramGrp>
<gen>f</gen>
</gramGrp>
</cit>
</sense>
<sense>
<usg type="dom">Comm</usg>
<form type="compound">
<orth>window <oRef/>
</orth>
</form>
<cit type="translation" xml:lang="fr">
<quote>étalagiste</quote>
<gramGrp>
<gen>mf</gen>
</gramGrp>
</cit>
</sense>
<cit type="example">
<quote>she's a stylish <oRef/>
</quote>
<cit type="translation" xml:lang="fr">
<quote>elle s'habille avec chic</quote>
</cit>
</cit>
<xr type="see">V. <ref target="#hair">hair</ref>
</xr>
</sense>
<sense n="b">
<usg type="category">tool</usg>
<sense>
<usg type="hint">for wood</usg>
<cit type="translation" xml:lang="fr">
<quote>raboteuse</quote>
<gramGrp>
<gen>f</gen>
</gramGrp>
</cit>
</sense>
<sense>
<usg type="hint">for stone</usg>
<cit type="translation" xml:lang="fr">
<quote>rabotin</quote>
<gramGrp>
<gen>m</gen>
</gramGrp>
</cit>
</sense>
</sense>
</entry>
<!-- ... -->
<entry xml:id="hair">
<sense>
<!-- ... -->
</sense>
</entry>
<!-- ... -->
<cit type="translation" xml:lang="en">
<quote>OAS</quote>
<def>illegal military organization supporting French rule of
Algeria</def>
</cit>
</entry>
havdaˈla;
Yiddish havˈdɔlə)
n Judaism the ceremony marking the end of the sabbath or of a festival, including the blessings over wine, candles and spices [literally: separation] CED<form>
<orth>havdalah</orth>
<orth>havdoloh</orth>
<gramGrp>
<gram type="pos">n</gram>
</gramGrp>
</form>
<sense>
<usg type="dom">Judaism</usg>
<def>the ceremony marking the end of the sabbath or of a festival,
including the blessings over wine, candles and spices</def>
</sense>
<cit type="translation" xml:lang="en">
<usg type="style">literally</usg>
<quote>separation</quote>
</cit>
</entry>
TEI: Etymological Information¶9.3.4 Etymological Information
The element etym marks a block of etymological information. Etymologies may contain highly structured lists of words in an order indicating their descent from each other, but often also include related words and forms outside the direct line of descent, for comparison. Not infrequently, etymologies include commentary of various sorts, and can grow into short (or long!) essays with prose-like structure. This variation in structure makes it impracticable to define tags which capture the entire intellectual structure of the etymology or record the precise interrelation of all the words mentioned. It is, however, feasible to mark some of the more obvious phrase-level elements frequently found in etymologies, using tags defined in the core module or elsewhere in this chapter. Of particular relevance for the markup of etymologies are:
- etym (詞源) 包含詞源學資訊。
- lang (語言名稱) 在詞源學或其他語言學相關訊息中所提到的語言。
- date 包含任何格式的日期表示。
- mentioned 標誌被提到的但意義上不被使用的字句。
- gloss 標明用來為另一個字詞下定義或提供註解的字詞。
- pron (發音) 包含該字的一種或多種發音方法。
- usg (字詞使用資訊) 包含辭條中的使用資訊。
- lbl (標籤) 包含字詞形式、範例、翻譯、或其他資訊的標籤,例如縮寫、省略、字面、約略、同義等。
As in other prose, individual word forms mentioned in an etymological description are tagged with mentioned elements. Pronunciations, usage labels, and glosses can be tagged using the pron, usg, and gloss elements defined elsewhere in these Guidelines. In addition, the lang element may be used to identify a particular language name where it appears, in addition to using the xml:lang attribute of the mentioned element.
<form>
<orth>abismo</orth>
</form>
<etym>del <lang>gr.</lang>
<mentioned>a</mentioned> priv. y <mentioned>byssos</mentioned>,
<gloss>fondo</gloss>
</etym>
<!-- ... -->
</entry>
\'n(y)üm\
n [F, fr. ML pneuma, neuma, fr. Gk pneuma breath — more at pneumatic]: any of various symbols used in the notation of Gregorian chant … [WNC]<!-- ... -->
<etym>
<lang>F</lang> fr. <lang>ML</lang>
<mentioned>pneuma</mentioned>
<mentioned>neuma</mentioned> fr. <lang>Gk</lang>
<mentioned>pneuma</mentioned>
<gloss>breath</gloss>
<xr type="etym">more at <ptr target="#pneumatic"/>
</xr>
</etym>
<sense>
<def>any of various symbols used in the notation of Gregorian chant
<!-- ... -->
</def>
</sense>
</entry>
<!-- ... -->
<entry xml:id="pneumatic">
<etym>
<!-- ... -->
</etym>
</entry>
TEI: Other Information¶9.3.5 Other Information
TEI: Examples¶9.3.5.1 Examples
Dictionaries typically include examples of word use, usually accompanying definitions or translations. In some cases, the examples are quotations from another source, and are occasionally followed by a citation to the author.
The <cit type="example"> element contains usage examples and associated information; the example text itself should be enclosed in a q or quote element. The cit element associates a quotation with a bibliographic reference to its source.
- q (引用的言詞、思想、或文字) 包含標記為 (看似) 引用自他處的內容;在敘述文中,此元素用來標記直接或間接敘述;在字典中,用來標記實例或編者設計的範例;在寫本描述或其他上層資訊中,用來標記由來源文本中所摘錄的引文。
- quote (引文) 包含敘述者或作者引用自文本以外來源的字 (句) 詞或段落。
- cit 從其他文件中引用的內容,並包含引用來源的書目參照資料。
Examples frequently abbreviate the headword, and so their transcription will frequently make use of the oRef element described below in section 9.4 Headword and Pronunciation References.
<quote>the multiplex eye of the fly.</quote>
</cit>
<usg type="colloc">
<oRef type="cap"/> and <mentioned>any</mentioned> are used with
<mentioned>more</mentioned>
</usg>
<cit type="example">
<quote>Give me <oRef/> more</quote>
<pron extent="part">s@'mO:(r)</pron>
</cit>
</sense>
<!-- ... -->
<cit type="translation" xml:lang="en">
<quote>to horrify</quote>
</cit>
<cit type="example">
<quote>elle était horrifiée par la dépense</quote>
<cit type="translation" xml:lang="en">
<quote>she was horrified at the expense.</quote>
</cit>
</cit>
</entry>
<usg type="time">Vx.</usg>
<def>Vaillance, bravoure (spécial., au combat)</def>
<cit type="example">
<quote>La valeur n'attend pas le nombre des années</quote>
<bibl>
<author>Corneille</author>
</bibl>
</cit>
</sense>
TEI: Usage Information and Other Labels¶9.3.5.2 Usage Information and Other Labels
Most dictionaries provide restrictive labels and phrases indicating the usage of given words or particular senses. Other phrases, not necessarily related to usage, may also be attached to forms, translations, cross-references, and examples. The following elements are provided to mark up such labels:
As indicated in the following section (9.3.5.3 Cross-References to Other Entries), the lbl element may be used for any kind of significative phrase or label within the text. The usg element is a specialization of this to mark usage labels in particular. Usage labels typically indicate
- temporal use (archaic, obsolete, etc.)
- register (slang, formal, taboo, ironic, facetious, etc.)
- style (literal, figurative, etc.)
- connotative effect (e.g. derogatory, offensive)
- subject field (Astronomy, Philosophy, etc.)
- national or regional use (Australian, U.S., Midland dialect, etc.)
Many dictionaries provide an explanation and/or a list of such usage labels in a preface or appendix. The type of the usage information may be indicated in the type attribute on the usg element. Some typical values are:
- geo
- geographic area
- time
- temporal, historical era (‘archaic’, ‘old’, etc.)
- dom
- domain
- reg
- register
- style
- style (figurative, literal, etc.)
- plev
- preference level (‘chiefly’, ‘usually’, etc.)
- acc
- acceptability
- lang
- language for foreign words, spellings pronunciations, etc.
- gram
- grammatical usage
In addition to this kind of information, multilingual dictionaries often provide ‘semantic cues’ to help the user determine the right sense of a word in the source language (and hence the correct translation). These include synonyms, concept subdivisions, typical subjects and objects, typical verb complements, etc. These labels may also be marked with the usg element; sample values for the type attribute in these cases include:
- syn
- synonym given to show use
- hyper
- hypernym given to show usage
- colloc
- collocation given to show usage
- comp
- typical complement
- obj
- typical object
- subj
- typical subject
- verb
- typical verb
- hint
- unclassifiable piece of information to guide sense choice
<orth>colour</orth>
<form>
<usg type="geo">US</usg>
<orth>color</orth>
</form>
</form>
[palEt]
nf (a) (Peinture: lit, fig) palette. (b) (Boucherie) shoulder. (c) (aube de roue) paddle; (battoir à linge) beetle; (Manutention, Constr) pallet. CR<usg type="dom">Peinture</usg>
<usg type="style">lit</usg>
<usg type="style">fig</usg>
<cit type="translation" xml:lang="en">
<quote>palette</quote>
</cit>
</sense>
<sense n="b">
<usg type="dom">Boucherie</usg>
<cit type="translation" xml:lang="en">
<quote>shoulder</quote>
</cit>
</sense>
<sense n="c">
<sense>
<usg type="syn">aube de roue</usg>
<cit type="translation" xml:lang="en">
<quote>paddle</quote>
</cit>
</sense>
<sense>
<usg type="syn">battoir à linge</usg>
<cit type="translation" xml:lang="en">
<quote>beetle</quote>
</cit>
</sense>
<sense>
<usg type="dom">Manutention</usg>
<usg type="dom">Constr</usg>
<cit type="translation" xml:lang="en">
<quote>pallet</quote>
</cit>
</sense>
</sense>
<cit type="translation" xml:lang="en">
<quote>reseating</quote>
<quote>rebottoming</quote>
<usg type="hint">with straw</usg>
</cit>
</entry>
TEI: Cross-References to Other Entries¶9.3.5.3 Cross-References to Other Entries
Dictionary entries frequently refer to information in other entries, often using extremely dense notations to convey the headword of the entry to be sought, the particular part of the entry being referred to, and the nature of the information to be sought there (synonyms, antonyms, usage notes, etymology, an illustration, etc.)
Cross-references may be tagged in dictionaries using the ref and ptr elements defined in the core module (section 3.6 Simple Links and Cross-References). In addition, the xr element may be used to group all the information relating to a cross-reference.
- xr (交互參照) 包含一字詞、句子、或圖象,用以參照到相同文本或不同文本中的其他位置。
- ref 標明與其他位置互相參照的符號,或許包含附加的文字或註解。
- ptr 標明一個與其他位置相連結的指標。
- lbl (標籤) 包含字詞形式、範例、翻譯、或其他資訊的標籤,例如縮寫、省略、字面、約略、同義等。
<form>
<orth>glee</orth>
</form>
<xr>Compare <ptr target="#madrigal.1"/>
</xr>
</entry>
<entry xml:id="madrigal.1">
<form>
<!-- ... -->
</form>
</entry>
<lbl>Syn. de</lbl>
<ref>hôtellerie (sens 1)</ref>.
</xr>
<form>
<orth>rose</orth>
</form>
<xr type="inflectedForm">
<lbl>the past tense of</lbl>
<ref target="#rise">rise</ref>
</xr>
</entry>
<!-- ... -->
<entry xml:id="rise">
<form>
<orth>rise</orth>
</form>
<!-- main entry for "rise" as verb -->
</entry>
<lbl>syn see</lbl>
<ref target="#adverse">adverse</ref>
</xr>
<!-- ... -->
<entry xml:id="adverse">
<form>
<orth>adverse</orth>
</form>
<!-- list of synonyms for "adverse" -->
</entry>
<lbl type="sense-restriction">sphère</lbl>
</xr>
<usg type="dom">imprim</usg>
<def>Donner a (une ligne) une longeur convenable au moyen de
<ref target="#blanc-2.1.3">blancs (2, sens 1, 3)</ref>
</def>
</sense>
<entry xml:id="blanc" n="2">
<!-- ... -->
<sense n="1">
<!-- ... -->
<def xml:id="blanc-2.1.3">...</def>
<!-- ... -->
</sense>
<!-- ... -->
</entry>
TEI: Notes within Entries¶9.3.5.4 Notes within Entries
Dictionaries may include extensive explanatory notes about usage, grammar, context, etc. within entries. Very often, such notes appear as a separate section at the end of an entry. The standard note element should be used for such material.
- note 包含附註或註釋。
(ˈnaɪðə, ˈni:ðə)
determiner 1a not one nor the other (of two); not either: neither foot is swollen … usage A verb following a compound subject that uses neither… should be in the singular if both subjects are in the singular: neither Jack nor John has done the work CED<form type="contraction">
<orth>neither</orth>
<pron notation="ipa">ˈnaɪðə</pron>,
<pron notation="ipa">ˈni:ðə</pron>
</form>
<!-- ... -->
<cit type="example">
<quote>neither foot is swollen</quote>
</cit>
<note type="usage">A verb following a compound subject
that uses <hi rend="italic">neither</hi>… should be
in the singular if both subjects are in the singular:
<hi rend="italic">neither Jack nor John has done the work</hi>
</note>
</entry>
The formal declaration for note is given in section 3.8 Notes, Annotation, and Indexing.
TEI: Related Entries¶9.3.6 Related Entries
The re element encloses a degenerate entry which appears in the body of another entry for some purpose. Many dictionaries include related entries for direct derivatives or inflected forms of the entry word, or for compound words, phrases, collocations, and idioms containing the entry word.
Related entries can be complex, and may in fact include any of the information to be found in a regular entry. Therefore, the re element is defined to contain the same elements as an entry element, with the exception that it may not contain any nested re elements.
(ˈbɛvɪ)
informal n, pl -vies 1 a drink, esp an alcoholic one: we had a few bevvies last night 2 a session of drinking. ▷ vb -vies, -vying, -vied (intr) 3 to drink alcohol [probably from Old French bevee, buvee, drinking] > 'bevvied adj CED<form>
<orth>bevvy</orth>
<pron notation="ipa">ˈbɛvɪ</pron>
</form>
<usg type="reg">informal</usg>
<hom>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>a drink, esp. an alcoholic one: we had a few bevvies last night.</def>
</sense>
</hom>
<!-- ... sense 2 ... -->
<hom>
<gramGrp>
<pos>vb</pos>
</gramGrp>
<sense n="3">
<def>to drink alcohol</def>
</sense>
</hom>
<etym>probably from <lang>Old French</lang>
<mentioned>bevee</mentioned>, <mentioned>buvee</mentioned>
<gloss>drinking</gloss>
</etym>
<re type="derived">
<form>
<orth>bevvied</orth>
</form>
<gramGrp>
<pos>adj</pos>
</gramGrp>
</re>
</entry>
TEI: Headword and Pronunciation References¶9.4 Headword and Pronunciation References
Examples, definitions, etymologies, and occasionally other elements such as cross-references, orthographic forms, etc., often contain a shortened or iconic reference to the headword, rather than repeating the headword itself. The references may be to the orthographic form or to the pronunciation, to the form given or to a variant of that form. The following elements are used to encode such iconic references to a headword:
- oRef (拼字參照) 在字典範例中,參照出標題字的拼字形式。
type 指出為參照出標題字所做的印刷修飾。 實例值包含: 1] cap (capital); 2] noHyph (no hyphen) - pRef (發音參照) 在字典範例中,參照出標題字的發音形式。
These elements all inherit the following attributes from the class att.pointing which may optionally be used to resolve any ambiguity about the headword form being referred to.
- att.pointing 定義一組與其他元素相連結的所有元素皆使用的屬性,連結是使用ㄧ個或多個統一資源識別符 (URI) 參照。
target 用一個或多個統一資源識別符參照 (URI References) 來說明參照所指位置。
Headword references come in a variety of formats:
- ~
- indicates a reference to the full form of the headword
- pref~
- gives a prefix to be affixed to the headword
- ~suf
- gives a suffix to be affixed to the headword
- A~
- gives the first letter in uppercase, indicating that the headword is capitalized
- pref~suf
- gives a prefix and a suffix to be affixed to the headword
- a.
- gives the initial of the word followed by a full stop, to indicate reference to the full form of the headword
- A.
- refers to a capitalized form of the headword
The oRef element should be used for iconic or shortened references to the orthographic form(s) of the headword itself. It is an empty element and replaces, rather than enclosing, the reference. Note that the reference to a headword is not necessarily a simple string replacement. In the example ‘colour1, (US = color) …~ films; ~ TV; Red, blue and yellow are ~s.’ OALD, the tilde stands for either headword form (colour, color).
</def>
<form>
<orth xml:id="di-o1">vag-</orth>
<orth xml:id="di-o2">vago-</orth>
</form>
<def>vagus nerve</def>
<cit type="example">
<quote>
<oRef target="#di-o1" type="noHyph"/>al</quote>
<quote>
<oRef target="#di-o2" type="noHyph"/>tomy</quote>
</cit>
</entry>
<quote>Mr Burton <oRef type="pt">took</oRef> us for French</quote>
</cit>
<quote>was quite <oRef type="pp">
<oRef/>n</oRef> with him</quote>
</cit>
<quote>it's easy to <oRef next="#ov2" xml:id="ov1">mix</oRef>
her <oRef prev="#ov1" xml:id="ov2">up</oRef> with her sister</quote>
</cit>
/,aw'duhv
(Fr O:r dœvr)/ n, pl hors d'oeuvres also hors d'oeuvre /'duhv(z)
(Fr ~)/ NPEG<orth>hors d'oeuvre</orth>
<pron>%aU"dUv</pron>
<form>
<usg type="lang">Fr</usg>
<pron xml:id="di-p2">OR d0vR</pron>
</form>
</form>
<form type="inflected">
<number>pl</number>
<orth>hors d'oeuvres</orth>
<orth>hors d'oeuvre</orth>
<pron extent="part">"dUv(z)</pron>
<form>
<usg type="lang">Fr</usg>
<pron>
<pRef target="#di-p2"/>
</pron>
</form>
</form>
Because headword and pronunciation references can occur virtually anywhere in an entry, the oRef and pRef elements may appear within any other element defined for dictionary entries.
Since existing printed dictionaries use different conventions for headword references (swung dash, first letter abbreviated form, capitalization, or italicization of the word, etc.) the exact method used should be documented in the header.
TEI: Typographic and Lexical Information in Dictionary Data¶9.5 Typographic and Lexical Information in Dictionary Data
Among the many possible views of dictionaries, it is useful to distinguish at least the following three, which help to clarify some issues raised with particular urgency by dictionaries, on account of the complexity of both their typography and their information structure.
- (a) the typographic view—the two-dimensional printed page, including information about line and page breaks and other features of layout
- (b) the editorial view—the one-dimensional sequence of tokens which can be seen as the input to the typesetting process; the wording and punctuation of the text and the sequencing of items are visible in this view, but specifics of the typographic realization are not
- (c) the lexical view—this view includes the underlying information represented in a dictionary, without concern for its exact textual form
For example, a domain indication in a dictionary entry might be broken over a line and therefore hyphenated (‘naut-’ ‘ical’); the typographic view of the dictionary preserves this information. In a purely editorial view, the particular form in which the domain name is given in the particular dictionary (as ‘nautical’, rather than ‘naut.’, ‘Naut.’, etc.) would be preserved, but the fact of the line break would not. Font shifts might plausibly be included in either a strictly typographic or an editorial view. In the lexical view, the only information preserved concerning domain would be some standard symbol or string representing the nautical domain (e.g. ‘naut.’) regardless of the form in which it appears in the printed dictionary.
In practice, publishers begin with the lexical view—i.e., lexical data as it might appear in a database—and generate first the editorial view, which reflects editorial choices for a particular dictionary (such as the use of the abbreviation ‘Naut.’ for ‘nautical’, the fonts in which different types of information are to be rendered, etc.), and then the typographic view, which is tied to a specific printed rendering. Computational linguists and philologists often begin with the typographic view and analyse it to obtain the editorial and/or lexical views. Some users may ultimately be concerned with retaining only the lexical view, or they may wish to preserve the typographic or editorial views as a reference text, perhaps as a guard against the loss or misinterpretation of information in the translation process. Some researchers may wish to retain all three views, and study their interrelations, since research questions may well span all three views.
In general, an electronic encoding of a text will allow the recovery of at least one view of that text (the one which guided the encoding); if editorial and typographic practices are consistently applied in the production of a printed dictionary, or if exceptions to the rules are consistently recorded in the electronic encoding, then it is in principle possible to recover the editorial view from an encoding of the lexical view, and the typographic view from an encoding of the editorial view. In practice, of course, the severe compression of information in dictionaries, the variety of methods by which this compression is achieved, the complexity of formulating completely explicit rules for editorial and typographic practice, and the relative rarity of complete consistency in the application of such rules, all make the mechanical transformation of information from one view into another something of a vexed question.
This section describes some principles which may be useful in capturing one or the other of these views as consistently and completely as possible, and describes some methods of attempting to capture more than one view in a single encoding. Only the editorial and lexical views are explicitly treated here; for methods of recording the physical or typographic details of a text, see chapter 11 Representation of Primary Sources. Other approaches to these problems, such as the use of repetitive encoding and links to show their correspondences, or the use of feature structures to capture the information structure, and of the ana and inst attributes to link feature structures to a transcription of the editorial view of a dictionary, are not discussed here (for feature structures, see chapter 18 Feature Structures. For linkage of textual form and underlying information, see chapter 17 Simple Analytic Mechanisms).
TEI: Editorial View¶9.5.1 Editorial View
Common practice in encoding texts of all sorts relies on principles such as the following, which can be used successfully to capture the editorial view when encoding a dictionary:
- All characters of the source text should be retained, with the possible exception of rendition text (for which see further below).
- Characters appearing in the source text should typically be given as character data content in the document, rather than as the value of an attribute; again, rendition text may optionally be excepted from this rule.
- Apart from the characters or graphics in the source text, nothing else should appear as content in the document, although it may be given in attribute values.
- The material in the source text should appear in the encoding in the same order. Complications of the character sequence by footnotes, marginal notes, etc., text wrapping around illustrations, etc., may be dealt with by the usual means (for notes, see section 3.8 Notes, Annotation, and Indexing).37
In a very conservative transcription of the editorial view of a text, rendition characters (e.g. the commas, parentheses, etc., used in dictionary entries to signal boundaries among parts of the entry) and rendition text (for example, conjunctions joining alternate headwords, etc.) are typically retained. Removing the tags from such a transcription will leave all and only the characters of the source text, in their original sequence.38
<form>
<orth>pinna</orth>
<pron notation="ipa">ˈpɪnə</pron>
</form>
<gramGrp>
<pos>n</pos>, </gramGrp>
<form type="inflected">
<number>pl</number>
<form>
<orth type="lat" extent="part">-nae</orth>
<pron extent="part">(-ni:)</pron>
</form> or <orth type="std" extent="part">-nas</orth>
</form>
<sense n="1">1 <def>any leaflet of a pinnate compound leaf</def>
</sense>
<sense n="2">2 <usg type="dom">zoology</usg>
<def>a feather, wing, fin, or similarly shaped part</def>
</sense>
<sense n="3">3 <xr type="syn">
<lbl>another name for</lbl>
<ref target="#auricle.2">auricle (2)</ref>
</xr>
</sense>
<etym>[<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>,
<gloss>fin</gloss>]</etym>
</entry>
<entry xml:id="auricle.2">
<form>
<!-- ... -->
</form>
</entry>
A somewhat simplified encoding of the editorial view of this entry might exploit the fact that rendition text is often systematically recoverable. For example, parentheses consistently appear around pronunciation in this dictionary, and thus are effectively implied by the start- and end-tags for pron.39 In such an encoding, removing the tags should exactly reproduce the sequence of characters in the source, minus rendition text. The original character sequence can be recovered fully by replacing tags with any rendition text they imply.
- parentheses appear around pron elements
- commas appear before inflected forms
- the word ‘or’ appears before alternate forms
- brackets appear around the etymology
- full stops appear after pos, inflection information, and sense numbers
- senses are numbered in sequence unless otherwise specified using the global n attribute
<form>
<orth>pinna</orth>
<pron>"pIn@</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<form type="inflected">
<number>pl</number>
<form>
<orth type="lat" extent="part">-nae</orth>
<pron extent="part">-ni:</pron>
</form>
<orth type="std" extent="part">-nas</orth>
</form>
<sense n="1">
<def>any leaflet of a pinnate compound leaf.</def>
</sense>
<sense n="2">
<usg type="dom">Zoology</usg>
<def>a feather, wing, fin, or similarly shaped part.</def>
</sense>
<sense n="3">
<xr type="syn">
<lbl>another name for</lbl>
<ref>auricle (sense 2).</ref>
</xr>
</sense>
<etym>
<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>, <gloss>fin</gloss>
</etym>
</entry>
When rendition text is omitted, it is recommended that the means to regenerate it be fully documented, using the tagUsage element of the TEI header.
If rendition text is used systematically in a dictionary, with only a few mistakes or exceptions, the global attribute rend may be used on any tag to flag exceptions to the normal treatment. The values of the rend attribute are not prescribed, but it can be used with values such as no-comma, no-left-paren, etc. Specific values can be documented using the rendition element in the TEI header.
<form>
<orth>biryani</orth>
<orth>biriani</orth>
<pron rend="noleftparen">%bIrI"A:nI</pron>
</form>
<def>any of a variety of Indian dishes … </def>
<etym>from <lang>Urdu</lang>
</etym>
</entry>
TEI: Lexical View¶9.5.2 Lexical View
If the text to be interchanged retains only the lexical view of the text, there may be no concern for the recoverability of the editorial (not to speak of the typographic) view of the text. However, it is strongly recommended that the TEI header be used to document fully the nature of all alterations to the original data, such as normalization of domain names, expansion of inflected forms, etc.
In an encoding of the lexical view of a text, there are degrees of departure from the original data: normalizing inconsistent forms like ‘nautical’, ‘naut’., ‘Naut.’, etc., to ‘nautical’ is a relatively slight alteration; expansion of ‘delay -ed -ing’ to ‘delay, delayed, delaying’ is a more substantial departure. Still more severe is the rearranging of the order of information in entries; for example:
- reorganizing the order of elements in an entry to show their relationship, as in where in a strictly lexical view one might wish to group ‘clem’ and ‘clam’ with their respective inflected forms.
- splitting an entry into two separate entries, as in celi.bacy /"selIb@sI/ n [U] state of living unmarried, esp as a religious obligation. celi.bate /"selIb@t/ n [C] unmarried person (esp a priest who has taken a vow not to marry). OALDFor some purposes, this entry might usefully be split into an entry for ‘celibacy’ and a separate entry for ‘celibate’.
- abbreviated forms have been silently expanded
- some forms have been moved to allow related forms to be grouped together
- the part of speech information has been moved to allow all forms to be given together
- the cross-reference to ‘auricle’ has been simplified
<form>
<orth>pinna</orth>
<pron>"pIn@</pron>
<form type="inflected">
<number>pl</number>
<form>
<orth type="lat">pinnae</orth>
<pron>'pIni:</pron>
</form>
<orth type="std">pinnas</orth>
</form>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>any leaflet of a pinnate compound leaf.</def>
</sense>
<sense n="2">
<usg type="dom">Zoology</usg>
<def>a feather, wing, fin, or similarly shaped part.</def>
</sense>
<sense n="3">
<xr type="syn">
<ptr target="#auricle.2"/>
</xr>
</sense>
<etym>
<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>, <gloss>fin</gloss>
</etym>
</entry>
Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of lexical databases, or uses the typographic/editorial view approach and needs to communicate the sometimes informally stated values for the particular descriptive features, the issue of ‘interoperability’ of the content and of the container objects becomes relevant, in view of the growing tendency to interlink pieces of information across Internet resources. In such cases, it becomes crucial to be able to encode the fact that whether the information on, for instance, the value of the grammatical category of Number is provided as "sg.", "sing.", "Singular", or equivalently "poj." in Polish, or "Ez." in German, etc., what is actually referred to is always the same grammatical value that can be rendered with a plethora of markers, depending on the publisher, language, or lexicographic tradition. In order to signal that this variety of surface markers in fact indicate the same underlying value, it is possible to align them with an external inventory of standardized values. The TEI provides means to align grammatical categories as well as their content with the ISOcat reference, which is a Web implementation of ISO 12620.
<!--...-->
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos dcr:datcat="http://www.isocat.org/datcat/DC-1345"
dcr:valueDatcat="http://www.isocat.org/datcat/DC-1230">adj</pos>
</gramGrp>
<!--...-->
</entry>
TEI: Retaining Both Views¶9.5.3 Retaining Both Views
It is sometimes desirable to retain both the lexical and the editorial view, in which case a potential conflict exists between the two. When there is a conflict between the encodings for the lexical and editorial views, the principles described in the following sections may be applied.
TEI: Using Attribute Values to Capture Alternate Views¶9.5.3.1 Using Attribute Values to Capture Alternate Views
If the order of the data is the same in both views, then both views may be captured by encoding one ‘dominant’ view in the character data content of the document, and encoding the other using attribute values on the appropriate elements. If all tags were to be removed, the remaining characters would be those of the dominant view of the text.
The attribute class att.lexicographic is used to provide attributes for use in encoding multiple views of the same dictionary entry. These attributes are available for use on all elements defined in this chapter when the base module for dictionaries is selected.
When the editorial view is dominant, the following attributes may be used to capture the lexical view:
- att.lexicographic 定義一組全域屬性值,可用於字典的基礎標籤組之元素上。
norm (normalized) 提供一規格化形式的資訊,其來源文件為非規格化形式 split 提供一合併形式的split值列表
When the lexical view is dominant, the following attributes may be used to record the editorial view:
- att.lexicographic 定義一組全域屬性值,可用於字典的基礎標籤組之元素上。
orig (original) 當該元素未出現於來源文件中,提供其原文字串或空白字串。 mergedIn gives a reference to another element, where the original appears as a merged form.
One attribute is useful in either view:
- att.lexicographic 定義一組全域屬性值,可用於字典的基礎標籤組之元素上。
opt (optional) 指出該元素是否必備
<orth>delay</orth>
<form type="inflected">
<orth norm="delayed" extent="part">-ed</orth>
<tns norm="pst,pstp"/>
</form>
<form type="inflected">
<orth norm="delaying" extent="part">-ing</orth>
<tns norm="prsp"/>
</form>
</form>
<orth>delay</orth>
<form type="inflected">
<orth orig="-ed">delayed</orth>
<tns orig="">pst</tns>
<tns orig="">pstp</tns>
</form>
<form type="inflected">
<orth orig="-ing">delaying</orth>
<tns orig="">prsp</tns>
</form>
</form>
<orth split="thyrostimuline, thyréostimuline">thyr(é)ostimuline</orth>
<pron split="tiRostimylin, tiReostimylin">tiR(e)ostimylin</pron>
</form>
<orth xml:id="dic-o1"
orig="thyr(é)ostimuline">thyrostimuline</orth>
<pron xml:id="dic-p1"
orig="tiR(e)ostimylin">tiRostimylin</pron>
</form>
<form>
<orth mergedIn="#dic-o1">thyréostimuline</orth>
<pron mergedIn="#dic-p1">tiReostimylin</pron>
</form>
<orth next="#dict-o2" xml:id="dict-o1">thyr</orth>
<orth next="#dict-o3" prev="#dict-o1"
xml:id="dict-o2" opt="true">é</orth>
<orth prev="#dict-o2" xml:id="dict-o3">ostimuline</orth>
<pron next="#dict-p2" xml:id="dict-p1">tiR</pron>
<pron next="#dict-p3" prev="#dict-p1"
xml:id="dict-p2" opt="true">e</pron>
<pron prev="#dict-p2" xml:id="dict-p3">ostimylin</pron>
</form>
Note that this transcription preserves both the lexical and editorial views in a single encoding. However, it has the disadvantage that the strings corresponding to entire words do not appear in the encoding uninterrupted, and therefore complex processing is required to retrieve them from the encoded text. The use of the opt attribute is recommended, however, when long spans of text are involved, or when the optional part contains embedded tags.
For example, the following gives two definitions in one text: ‘picture drawn with coloured chalk made into crayons’, and ‘coloured chalk made into crayons’:
<def>coloured
chalk made into crayons</def>
<def>picture drawn with coloured chalk
made into crayons</def>
</sense>
<def next="#d2" xml:id="d1" opt="true">picture drawn
with</def>
<def prev="#d1" xml:id="d2">coloured chalk made into
crayons</def>
</sense>
TEI: Recording Original Locations of Transposed Elements¶9.5.3.2 Recording Original Locations of Transposed Elements
The attributes described in the previous section are useful only when the order of material is the same in both the editorial and the lexical view. When the two views impose different orders on the data, the standard linking mechanisms may be used to show the original location of material transposed in an encoding of the lexical view.
If the original is only slightly modified, the anchor element may be used to mark the original location of the material, and the location attribute may be used on the lexical encoding of that material to indicate its original location(s). Like those in the preceding section, this attribute is defined for the attribute class att.lexicographic:
- att.lexicographic 定義一組全域屬性值,可用於字典的基礎標籤組之元素上。
opt (optional) 指出該元素是否必備
<orth>pinna</orth>
<pron notation="ipa">ˈpɪnə</pron>
<anchor xml:id="p01"/>
<form type="inflected">
<number>pl</number>
<form>
<orth extent="part">-nae</orth>
<pron extent="part">-ni:</pron>
</form>
<orth extent="part">-nas</orth>
</form>
</form>
<gramGrp>
<pos location="#p01">n</pos>
</gramGrp>
TEI: Unstructured Entries¶9.6 Unstructured Entries
The content model for the entry element provides an entry structure suitable for many average dictionaries, as well as many regular entries in more exotic dictionaries. However, the structure of some dictionaries does not allow the restrictions imposed by the content model for entry. To handle these cases, the entryFree and dictScrap elements are provided to support much wider variation in entry structure. The dictScrap element offers less freedom, in that it can only contain phrase level elements, but it can itself appear at any point within a dictionary entry where any of the structural components of a dictionary entry are permitted. As such, it acts as a container for otherwise anomalous parts of an entry.
The entryFree element places no constraints at all upon the entry: any element defined in this chapter, as well as all the normal phrase-level and inter-level elements, can appear anywhere within it. With the entryFree element, the encoder is free to use any element anywhere, as well as to use or omit grouping elements such as form, gramGrp, etc.
<form>
<orth>demigod</orth>
<hyph>demi|god</hyph>
<pron>"demIgQd</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<def>one who is partly divine and partly human</def>
<def>(in Gk myth, etc) the son of a god and a mortal woman, eg
<mentioned>Hercules</mentioned>
</def>
<pron>"h3:kjUli:z</pron>
</entryFree>
<orth>biryani</orth> or <orth>biriani</orth>
<pron notation="ipa">(ˌbɪrɪˈa:nɪ)</pron>
<def>any of a variety of Indian dishes …</def>
<etym>[from <lang>Urdu</lang>]</etym>
</entryFree>
<dictScrap>
<orth>biryani</orth> or <orth>biriani</orth>
<pron notation="ipa">(ˌbɪrɪˈa:nɪ)</pron>
<def>any of a variety of Indian dishes …</def>
<etym>[from <lang>Urdu</lang>]</etym>
</dictScrap>
</entry>
TEI: The Dictionary Module¶9.7 The Dictionary Module
The module defined in this chapter makes available the following components:
- 組件 dictionaries: 紙本字典
- 被定義的元素: case colloc def dictScrap entry entryFree etym form gen gram gramGrp hom hyph iType lang lbl mood number oRef orth pRef per pos pron re sense stress subc superEntry syll tns usg xr
- 被定義的分類: att.entryLike att.lexicographic model.entryLike model.formPart model.gramPart model.lexicalRefinement model.morphLike model.ptrLike.form
The selection and combination of modules to form a TEI schema is described in 1.2 Defining a TEI Schema.