One callable unit (4 passages, no note) of an API (note: API): a method (28 passages, no note) and a path in an OpenAPI contract (note: Contract), a port and an operation name in a WSDL. The build (note: Build) imports (25 passages, no note) every operation of a declared contract as an endpoint entity with the properties (note: Attribute) the contract states (36 passages, no note). An author (note: Author) who has business to explain writes an operation note; the build attaches it to the imported (27 passages, no note) operation on its declared identifier (note: Identifier), then on its method and path, then on its title, and the note (note: Note) becomes the single page of the operation, showing its own markdown (note: Markdown), the properties of the contract and its own links.
Operation
Properties4
- Application
- Concordance command line
- Domain
- Inference
- Status
- valid
- Broader term
- inference/model/entity.md
4 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapOperation
Neighbourhood map Operation
Distance1 hop
82 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ContractTermgeneralizes38
- LinkTermspecializes14
- EntityTermspecializes12
- APITermspecializes26
- Contract checksTermspecializes1
- AttributeTermspecializes14
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.