The grouping (4 passages, no note) of the checks in their documentation: every check page states its family, and the list of the checks is laid out by family, source checks, link checks, identifier and type checks, document checks, vocabulary and filing checks, contract checks and plugin checks. The family says which step (note: Step) of the pipeline (note: Pipeline) raises the finding and which note (note: Note) or file it points at.
Check family
Properties3
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapCheck family
Neighbourhood map Check family
Distance1 hop
73 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- CheckTermspecializes4
- Contract checksTermspecializes1
- Document checksTermspecializes1
- Identifier and type checksTermspecializes1
- Link checksTermspecializes1
- Plugin checksTermspecializes1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.