Concept idioms are reusable across contexts and can codify design expertise.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Concept Idiomframework0.803
  A reusable concept pattern applicable across contexts, with known purpose and operational principle.
• Design and engineering knowledge are not reducible to scientific principles; operational principles are needed.claim0.765
  Polanyi's argument applied to software.
• A concept should not attempt to serve two distinct purposes; this leads to conflicts and confusion.claim0.764
  No overloading criterion.
• A concept is a structure invented to give a coherent account of the immediate consequences of actions in a complex system.claim0.757
  Jackson's operational definition of a software concept.
• Concepts are not just subjective mental constructs, but are objective features of a system's design: increments of functionality that were consciously introduced by a designer to serve particular purposes.concept0.752
  Central definition from the abstract.
• How should we account for concepts having multiple forms at different levels of sophistication and exploit it in design?question0.749
  Open question about layered concept complexity.
• Concepts are the building blocks of software systems, objective features of a system’s design.claim0.745
  Asserts that concepts are not just mental but concrete design elements.
• The four concept criteria (motivation, no redundancy, no overloading, uniformity) are neither necessary nor sufficient but can explain design flaws.claim0.744
  Acknowledging the heuristic nature of the criteria.