Structural Namespace
Core definition#
Structural frames provide schematic conceptual structures used to ground lexical meaning: containment, ordering, part–whole organization, force and transformation. Their modeling function is the criterion, not simply generality or a small FE inventory.
The conceptual dimension is topological and relational: it records organization rather than a full metric similarity space. Its two primitives are REGION (a concept modeled as a region) and LINK (a relation between regions). The layer interprets force/configuration through relations; this schematic use of “force” must not make every lexical property a maintained State condition.
See Schemas for the authoritative schema inventory and Grounding a Frame for mappings. The namespace page defines classification, not a duplicate schema catalog.
Families#
| Family | Examples | Function |
|---|---|---|
| Primitives | REGION, LINK | Conceptual regions and ties |
| Organization | DIMENSION, AXIS, SCALE, CLASS, PART_WHOLE, CONTAINER | Ordering, classifying, composing and partitioning |
| Bearer/value structure | OBJECT, VALUE; Attributes as bearer–dimension–value structure | Attribution and value positions |
| Spatial | FIGURE_GROUND | Locating a profiled region relative to a reference |
| Transformation | EVENT, AGENTIVE, UNDERGOING, EXPERIENTIAL, CHANGE and its specializations | Abstract occurrence, perspective and change structure |
| Reusable positions/routes | SOURCE, PATH, GOAL | Regions or routes named independently of a traversal |
Participation in conceptual grounding does not alone require the Structural namespace. A frame can retain lexical Attribute-family semantics while supplying a useful grounding structure. Inspect the particular frame's documented role instead of forcing a one-to-one namespace/schema correspondence.
Boundaries#
- Structural versus the Relation family: a containment schema supplies reusable structure; a lexical frame describes a holding relation among relata. Both are types of description, not a contrast between “abstract frame” and “actual sentence token.”
- Structural versus eventive: EVENT/CHANGE as schemas supply structure; lexical frames describe occurrences or transitions grounded in that structure.
- Structural versus the Attribute family and State: common bearer/value structure does not erase the distinction between plain properties, maintained conditions and resultant conditions.
- Structural versus Microframe: a schema can organize several roles and relations; a microframe reifies a particular binary relation used in that organization.
- Structural versus Class: representing a DUL class is a different modeling function.
- Structural versus Scenario: Scenario is an independent frame type. Organizing phases or perspectives does not automatically make a frame Structural, and no population claim follows from the two axes being independent.
Review diagnostics#
- Identify the frame's documented grounding/scaffolding function and the frames or elements it structures.
- Check that it represents a schematic structure rather than an ordinary lexical relation with a general definition.
- Inspect its actual schema relations and FE mappings; do not infer them from an uppercase name.
- Keep namespace semantics separate from conceptual-schema inheritance and filler restrictions.
Defer ambiguous lexical/scaffolding cases. The existence of a shared schema is not evidence that its lexical frames should merge or share a namespace.
Compatibility scope#
Lemma types do not restrict LU allocation by namespace (Lemmas §8). Whether a lexical reading belongs in a Structural frame is decided by the frame's modeling function, not by the lemma's type.