Chapter 18 Lexical Functions: Description of Lexical Relations in a ...

—Chapter 18. Lexical Functions— 74
4. under the vocable to which the given element of an LF value belongs.
Let us consider these cases in turn.
1. Shared Values of Lexical Functions and Cross-references to a Convenient Lexical Unit of a Vocable
If the LU L1 of the vocable {L} has the same values of some LFs as L2, another LU of {L}
or of a different vocable {L´}, these values are given only under L2, with a cross-reference under
L1: ↑L2, i.e., ‘see L2’. For instance, under ESCAPEN, we find in the LF zone:
LFs S 1Perf, S 1Able 1, S usual
2, S 3, A 1: ↑ESCAPEV,
which means (the values for the LFs S 1Perf, S 1Able 1, S usual
2, S 3 and A 1 for the LU ESCAPEN are
identical to the values for the same LFs for the LU ESCAPEV).
This is a rather straightforward technical generalization.
2. Shared Values of Lexical Functions and the Generic Lexical Unit of the Semantic Field
LUs belonging to the same semantic field may have the same values for the same LFs. Of
course this is only a tendency, since there are numerous exceptions and deviations, 21 yet in some
cases this tendency is quite clear. If shared values of LFs are semantically determined—that is, if
the keywords belong to the same semantic field, the generalization can be achieved without expli-
cit cross-references. It suffices to store all common values of LFs supplied with necessary indica-
tions only once—under the generic lexical unit of the corresponding semantic field.
The methodology (proposed in Mel’čuk & Wanner 1996) runs as follows:
1) Each semantic field is identified by its generic LU—LGENER. For instance, for the field CAR,
TRUCK, BUS, CARAVAN, MOTORBIKE, ... the LGENER is MOTOR VEHICLE; this LGENER appears in the
definitions of all the LUs of the field.
2) The LGENER of a semantic field can have, in addition to its own ‘private’ entry, another one,
called ‘public’, where the shared elements of the values of the LFs associated with the indivi-
dual members of the field are stored. They are not repeated in individual entries, which thus
contain only those LF value elements which are idiosyncratic to particular LUs.
3) When the user needs the value of a particular LF f as applied to a particular LU L, he is sup-
posed to look for it in the entry of L. If, however, the value f(L) is not given in L’s entry or if it is
given only partially, it has to be looked up in the public entry of the LGENER of the corresponding
field (LGENER is specified in L’s definition). Thus, there is no need to repeat Real 1 = drive and
Real 2
= ride for every particular name of a motor vehicle: both verbs can be indicated only once,
in the ‘public’ entry of MOTOR VEHICLE. From there, they are inherited by all LUs of this field.