5.2. Size-and-Shape Specifiers (SASS)
Size-and-shape specifiers (SASS) demonstrate the size and shape of an entity by indicating the outline of the entity. There are two types, namely static SASS and tracing SASS, which function quite differently in NGT. The main differences are the following.
Firstly, static SASS do not have a movement component included, while tracing SASS do. Thus, whereas the former can combine with verb stems of location and movement – like entity classifiers, the latter only combine with verbs of location, or modify nouns. Because of this movement element, tracing SASS can function as free morphemes, and, when modifying nouns, as adjectives.
Secondly, while both types visualize (part of) the outline of an entity, static SASS represent an entity through the handshape and usually emphasize size of the entity. Tracing SASS indicate the outline of an entity through the movement component and emphasize the shape of the movement.
Thirdly, the sets of handshapes that can function as a static SASS or tracing SASS are quite different. Static SASS are part of a closed group, with a limited set of handshapes, meaning that a limited set of shapes and sizes can be produced (see Table X. in MORPHOLOGY 5.1). Tracing SASS, however, can specify any shape. A star-shaped entity, for instance, cannot be represented by a static SASS (or by the >-handshape entity classifier), while a tracing SASS can definitely outline the star shape with extended index fingers:
|
|
Figure X. A tracing SASS showing a star-shaped entity
Because of these differences, I follow the mentioned studyand take static SASS together with entity classifiers, and describe these in MORPHOLOGY 5.1, and only describe tracing SASS here in MORPHOLOGY 5.2. The following handshapes can function as tracing SASS:
|
|
|
Possible handshapes for tracing SASS |
According to the Dutch study, which (type of) SASS or classifier is used is a matter of prominence from the perspective of the signer. The choice depends, for example, on the importance of the exact shapes of the entities. When the signer describes three mirrors (see Figure X.a and X.b), to take their example, there are several ways to do this:
(i) By localizing the referents through an entity classifier (see Figure X.c);
(ii) By localizing the referents and showing their shapes through tracing SASS on the dedicated locations (see Figure X.d);
(iii) By indexing the dedicated locations and using tracing SASS in a neutral location (see Figure X.e).
|
|
Gebarenfoto’s |
|
Figure X.a Three mirrors in different forms. |
X.b three mirror |
|
Figure missing |
|
x.c cl(]): ‘be.at.locationa’, cl(]): ‘be.at.locationb’, cl(]): ‘be.at.locationc’ |
|
Figure missing |
|
x.d squared.entity.at.locationa, round.entity.at.locationb, star-shaped.entity.at.locationc |
|
Figure missing |
|
x.e ixa squared.entity ixb round.entity ixc star-shaped.entity |
Thus, the functions of static and tracing SASS differ.
Like entity and handling classifiers, SASS can lexicalize and then function as a (part of a) lexeme, such as the tracing SASS originally indicating a square in swimming^pool. When the swimming pool that is referred to is round, for example, the lexicalized SASS will still be used within the compound, followed by a productive SASS indicating the round shape:
|
|
|
Video of plaatjes: rond zwembad. |