Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:25:20 UTC

F.3:6 - Solution — how to think about clustering

F.3:6.1 - Consolidate aliases supported by source usage

If spelling variants, abbreviations, or explicit synonyms are interchangeable in the relevant passages and do not change a conclusion, let one LocalSenseClaim cover them.

Example: ITIL’s service-level objective and SLO may support one local claim when the cited edition uses them interchangeably.

F.3:6.2 - Split incompatible argument patterns

Split when the same head takes materially different participants or occupies a different place in the source’s propositions.

Example: in a BPMN diagram, event names a node. In a tutorial’s account of an outage, the same word can name an occurrence.

F.3:6.3 - Split divergent entailments

If one use entails occurrence in time and another entails a design structure or capability, the uses support different claims.

Example: a PROV activity is a time-bounded occurrence; that claim does not describe a static algorithmic capability.

F.3:6.4 - Prefer the coarsest adequate partition

Merge candidates when the recovered source uses establish that they are interchangeable for the receiving question and preserve every relevant conclusion. A failed attempt to fin