DictionaryBinding#
This page is generated from the code and must not be edited by hand.
What the Dictionary made of one component, held apart from the component.
The token and its meaning sit at different distances from the bytes. A filename was read literally off the filesystem, and that is what Component records, at LITERAL. Resolving md to a sense is interpretation of meaning rather than form, which is the definition of SEMANTIC, the last rung of the ladder. One record carrying one tier for both said a Dictionary interpretation was as certain as a stat call.
This record carries nothing read from the filesystem. No raw value, no normalized value, no magnitude, no occurrence count. Every literal is one primary-key join away on component_id. That keeps observations and interpretations apart by construction rather than by discipline.
One row per component, always written when the binder ran, including when it declined. Absence of a row is then never a fact about a component: it can only mean the binder did not run, and the run record says so. That is what keeps “not examined” distinct from “examined and found nothing”, which must stay distinct and a bare null cannot express.
Fields#
Field |
Type |
Required |
If left out |
|---|---|---|---|
|
whole number |
no |
|
|
list of |
no |
|
|
text |
yes |
|
|
text |
yes |
|
|
text or null |
no |
|
|
text |
yes |
|
|
|
no |
|
|
|
yes |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
text |
yes |
|
|
text |
yes |
|
|
text |
yes |
|
|
text |
no |
|
|
text or null |
no |
|
|
|
no |
|
|
whole number or null |
no |
|
|
|
no |
|
|
whole number or null |
no |
|
|
|
no |
|
|
|
no |
|
|
text or null |
no |
|
|
text or null |
no |
|
|
text or null |
no |
|
The types named above are described on the shared types page: BindingAlternative, BindingMethod, DictionaryOrigin, DictionaryStatus, ExtractionTier, MatchQuality, ResolutionStatus, Scope, SourceScope.