A domain the build proposes from the neighbourhood rather than reads from the configuration, for a corpus nobody filed yet. Every term with a note of its own whose distinct neighbours, over the typed links and the co-occurrences, reach min_neighbours is a pivot; every note no frontmatter, folder or glob files that lies within radius edges of a pivot is a candidate for a domain named after it, attached to the closest pivot, at equal distance to the one of highest degree. A stopword or a term the lock rejects never pivots. The proposal reads as one I-DOMAIN-SUGGESTED finding per reached note and as a section of the build log; nothing is assigned unless the configuration says so, because a growing corpus (note: Corpus) moves its pivot (14 passages, no note)s. A proposal is promoted by declaring the domain, or by naming the note under domains in the lock, and every entity records the origin of its domain: frontmatter, folder, glob, unclassified, lock or inferred.
Emergent domain
Properties4
- Application
- Concordance command line
- Domain
- Typing and filing
- Status
- valid
- Broader term
- ingestion/typing/domain.md
4 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapEmergent domain
Neighbourhood map Emergent domain
Distance1 hop
51 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Co-occurrenceTermspecializes1
- LinkTermspecializes3
- NeighbourhoodTermspecializes1
- StopwordTermspecializes1
- ConfigurationTermspecializes2
- LockTermspecializes3
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.