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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:50:19 UTC

F.7 - Display Source-Local Comparisons in a Concept-Set Table

Put exact local meanings and established relations side by side. The table displays the argument. Each claim needs grounds independent of its place in the table.

Type: Architectural pattern.

Status: Stable

Depends on. E.10.D1 Recovering What “Context” Means in Use; F.0.1 Source-Local Meaning Recovery; F.1 for finding and selecting sources for the question; F.2 for source-local term harvesting and normalisation; F.3 Source-Local Sense Clustering; F.17 for optional exact cells; F.5 Naming Discipline; F.9 for established relations between distinct source-local meanings and the separate claims about their bounded uses.

Coordinates with. F.4 SystemRoleKindDescription; F.6 SystemRoleAssignment and Performed-Work Attribution Check; direct Part C patterns for the compared values; C.16 for characteristics; A.6.9 when umbrella sameness wording must be repaired before a relation is asserted.

Aliases (informative). Concept-Set table; comparison grid; Giants’ table.

F.7:1 - Intent & applicability

Intent. Give a reader one compact surface for comparing exact source-local claims, optional F.17 cells, and any relations that already obtain between them. The table also shows the stated comparison or receiving use, direction, losses, evidence, and counterexamples. It makes a distributed argument readable without turning row membership into sameness or permission.

Use this when. Two or more selected sources must be compared for one named question, teaching contrast, designation choice, or receiving use, and prose alone scatters the relevant distinctions.

Do not use this when. One local claim is enough, or no receiving comparison is named. A table is optional. It creates no value, kind, relation, classification, assignment, evidence use, reliance, verdict, or authorisation.

F.7:2 - Problem frame

Four common errors in cross-source comparison are:

  1. Silent equivalence: similar labels are treated as one meaning.
  2. Loss denial: a relation that holds is shown without direction or limitation.
  3. Name inflation: a new umbrella label is coined merely because several entries share a row.
  4. Cognitive scatter: source meanings, relations, evidence, and the receiving question are separated across documents.

F.7:3 - Forces

ForceTension to resolve
Locality vs comparisonEach meaning remains source-local, yet the reader must compare them.
Didactics vs fidelityA compact row must not hide direction, loss, evidence, or a missing relation.
Simplicity vs completenessThe page should be memorable while making clear when the full proof lies elsewhere.
Similarity vs relationEntries may look alike while no identity, hierarchy, or substitution relation obtains.

F.7:4 - Core idea (didactic)

A Concept-Set row is a didactic grouping for one stated comparison or use. It contains:

  • the exact sources and editions;
  • each source-local claim, or its F.17 SchemeSenseCell when durable addressability is useful;
  • every already obtaining relation that matters here, with direction and declared loss;
  • the separate conclusion about the named receiving comparison or use;
  • the evidence or direct pattern that supports each substantive claim;
  • a counterexample or boundary showing where the comparison stops.

The word set names the entries collected for display. It does not assert that they are one value. A row can show a grounded relation, such as identity, overlap, ordering, incompatibility or disjointness. When the comparison asserts no relation, say so. A claim that a particular relation does not hold needs its own grounds.

Use F.9 only for a relation between distinct local meanings. For every other relation, cite the pattern that defines, constrains, or tests it.

F.7:5 - Minimal vocabulary

  • Local entry — an exact LocalSenseClaim or optional F.17 SchemeSenseCell, with its source and edition and effective scheme.
  • Obtaining relation — a relation already supported under its direct pattern; it is not inferred from co-placement.
  • Direction — which participant is source and which is target when the relation is asymmetric.
  • Loss or limit — what the relation or receiving use does not preserve.
  • Receiving-use conclusion — the separate claim that judges whether and how the entries and relations may be used for one named purpose.
  • Contrast row — a row that teaches a difference or an unresolved comparison and expressly asserts no sameness.
  • Characteristic — a comparandum defined by its direct characteristic pattern; a table may display measured or target values but does not define the characteristic.

F.7:6 - The table

Choose the fewest columns that make the current argument recoverable:

Comparison or useExact source-local entriesObtaining relations and directionLoss and boundaryBasis and evidenceReceiving-use conclusion

For a teaching contrast, the relation column may say none asserted and the conclusion may say keep distinct. For an F.9 relation, show its declared relation kind, direction, CL if the relation defines one, and loss. Do not compute a row-wide CL or replace the separate bounded-use claim with a table label.

Reading rules:

  1. Entries stay local. A cell cites the source’s expression and claim; it is not a translation supplied by the table.
  2. Relations stay direct. For each relation, cite the pattern that defines, constrains, or tests it and the evidence supporting the claim.
  3. Use stays separate. “These may be compared for this report” is a claim with its own basis, not a property of the row.
  4. Unknown stays unknown. A blank or unresolved relation is not an invitation to infer similarity.
  5. Loss stays visible. If the limit needs more than one line, link to the underlying relation or evidence rather than compressing it away.

F.7:7 - Conceptual construction

  • Start from a question. State the comparison or receiving use before selecting entries.
  • Bring exact local meanings. Use F.0.1, F.2, F.3, and F.17 only as needed.
  • Show established relations. Cite the direct pattern and evidence for each relation that matters.
  • State the receiving-use conclusion separately. Say what the current comparison permits, with its basis and limits.
  • Keep the row focused. Add an entry only when it changes the answer.
  • Use contrast. When no adequate relation is established, show the difference rather than forcing a unification.

F.7:8 - Invariants

  1. Exact entries. Every filled source-local cell identifies the particular source, edition and claim, or the particular F.17 cell.
  2. No row-created relation. Co-placement, matching labels, or a shared FPF designation establishes nothing about the entries.
  3. Direct relation basis. Every stated relation cites its direct pattern and available evidence; F.9 is conditional, not universal.
  4. Separate receiving use. Any conclusion about comparison, substitution, reporting, or reuse is stated and supported separately.
  5. Direction, time stance, and loss. Asymmetric relations show direction; any design-time, run-time, or other temporal difference that changes the comparison is explicit; every material limitation remains visible.
  6. No automatic closure. Relations are not completed pairwise or transitively merely to fill a row.
  7. No universal row type. A senseFamily label is not required and cannot substitute for an intensional account of what is being compared.
  8. Parsimony. Keep only entries and columns that change the current answer.
  9. Didactic bound. Split a row when its combined distinctions prevent the intended reader from recovering the comparison. Keep related claims together when their joint reading is needed.

F.7:9 - Micro-illustrations

The examples show table shapes. To use a row for a particular comparison, supply evidence for each positive relation.

F.7:9.1 - (a) Class-order comparison

Comparison or useExact source-local entriesObtaining relationsLoss and boundaryBasisConclusion
Explain two class-order notationsOWL 2 SubClassOf; FPF U.SubkindOf claimAn explicit representation or semantic relation, if established for the selected expressionsOWL profile semantics and FPF kind criteria may differC.3.1, C.29, A.6.3.RT, and cited sourcesUse one didactic gloss only within the stated notation comparison; do not include FCA order by resemblance.

F.7:9.2 - (b) Measurement comparison

Comparison or useExact source-local entriesObtaining relationsLoss and boundaryBasisConclusion
Compare values against a service targetSOSA result claim; ISO 80000 quantity value; ITIL metric valueExact measurement, scale and unit, and any source-local semantic relations that obtainComposite ITIL indices may lack unit fidelityC.16, F.9 when needed, cited observationsComparable only for the named characteristic, scale conversion, population, and window.

F.7:9.3 - (c) Contrast: process

Comparison or useExact source-local entriesObtaining relationsLoss and boundaryBasisConclusion
Prevent homonym collapseBPMN workflow graph; PROV time-bounded activity; thermodynamic trajectoryNone asserted by this rowDesign structure, occurrence, and trajectory are different subjectsF.0.1, F.3, and direct source passagesKeep distinct unless a later question establishes a specific relation.

F.7:10 - Anti-patterns & remedies

#Anti-patternSymptomWhy harmfulRemedy
AP-1Row-created samenessEntries are called “the same” because they share a row.Layout is mistaken for evidence.State the established relation or mark a contrast.
AP-2Scope label as licence“Naming-only” or another row label is treated as permission.The receiving-use claim and its evidence disappear.Write the use conclusion separately.
AP-3senseFamily typingOne broad label is used instead of explaining the comparison.Hidden kinds and relations remain unnamed.State the intensional comparison and direct relation.
AP-4Temporal blurDesign descriptions and Work occurrences are treated as interchangeable.MethodDescription and Work collapse.Show the distinction and any actual relation through F.11, A.3, and A.15.
AP-5Loss denialA relation is shown without its material limitation.Readers over-transfer.Add the loss and a concrete counterexample.
AP-6Row CLA minimum or average CL is computed across heterogeneous relations.One number collapses unrelated claims.Keep CL only on the F.9 relation that declares it; assess the receiving use separately.
AP-7Overwide rowMany sources are added “for completeness”.Differences hide and the entry cost rises.Retain only answer-changing entries; split the display when needed without losing a required comparison.
AP-8Minted paraphraseA cell replaces the source expression with a new umbrella term.Provenance and locality vanish.Cite the exact local claim; put any selected designation in its own column.
AP-9Duplicate rows by wordingThe same argument is repeated under different labels.Readers infer distinct concepts where none were established.Keep one comparison and let F.5 manage aliases.
AP-10Automatic transitivityA–B and B–C are used to assert A–C.Relation composition may not hold or may add loss.State only relations whose composition is justified by their direct patterns.

F.7:11 - Worked example and application sketches

Section 11.1 supplies exact source bases for one contrast row. Sections 11.2–11.5 show further applications; complete their source-local claims, relations and evidence before treating them as finished tables.

F.7:11.1 - Actor wording across BPMN and PROV

Comparison or useExact entriesRelationBoundaryBasisConclusion
Choose a plain-language heading for a teaching paragraphBPMN 2.0.2 §9.3.1 Participant: a Collaboration element representing a PartnerEntity, PartnerRole, or both. PROV-O, 30 April 2013, §3.1 prov:Agent: something responsible for an activity, an entity’s existence, or another agent’s activity.None asserted; this is a contrast row.BPMN’s representation within a Collaboration and PROV’s responsibility meaning remain distinct.BPMN 2.0.2 §9.3.1, p. 113; PROV-O §3.1; each term is interpreted within that cited source scheme.Use Parties in the comparison as this paragraph’s heading, then retain the two source-specific sentences. This explanatory heading asserts no common kind, identity or substitutability.

F.7:11.2 - Runtime occurrence comparison

Comparison or useExact entriesRelationBoundaryBasisConclusion
Report selected PLC task runs as provenance activitiesIEC task-execution claim; PROV Activity claimA stated source-local semantic or representation relation, direction IEC → PROV, when established for those entriesPROV omits scan-cycle and scheduling semanticsF.9 or the direct representation pattern plus evidenceReport only the covered occurrence facts; do not infer that every PROV Activity is an IEC task run.

Performed-Work attribution remains an A.15.1 and F.6 claim about actual Work and system-role assignment. The table supplies neither.

F.7:11.3 - Measured value and target

Comparison or useExact entriesRelationBoundaryBasisConclusion
Judge an observed service characteristic against a targetSOSA observation and its result; ISO quantity value if used; ITIL service targetMeasurement, scale, and unit relations; F.9 only for a relation between source-local meaningsComposite KPI, sampling, and unit limitsC.16, A.10, B.3, and F.12Compare only the named characteristic, population, and window with adequate evidence.

F.7:11.4 - Class inclusion and FCA order

A contrast row may show OWL class inclusion, FPF U.SubkindOf, and FCA concept order together. FCA orders formal concepts by inclusion of their extents, equivalently reverse inclusion of their intents, within a selected formal context (Rudolph, Săcărea and Troancă, 2015, §2.1). That order does not by itself establish an OWL class axiom or an FPF subkind fact. A positive correspondence requires an explicit interpretation and grounds for the chosen domain and membership criteria.

F.7:11.5 - Role trigger word

Show NIST RBAC role as a permission grouping. Beside it, show the local claim that identifies a system-role kind whose members are Systems. Mark them distinct subjects. Use E.10.ROLE to recover other uses such as relation participation or signature position. Shared spelling alone gives no basis for assigning one senseFamily.

F.7:12 - Reasoning with a comparison row

  1. Name the comparison. What question or receiving use makes the row worth having?
  2. Recover each entry. Cite its exact source, scheme, expression, and local claim.
  3. List only obtaining relations. For each, state direction when relevant, the pattern that defines, constrains, or tests it, the supporting evidence, the loss, and any temporal difference that changes the comparison.
  4. Judge the use separately. Explain what the named use may conclude and why.
  5. Expose absence. When no relation is established, say so and use a contrast row.
  6. Resist closure. Do not invent missing pairwise or transitive relations.
  7. Adding a source. Include it only when its claim or relation changes the answer, then re-evaluate the conclusion for this use.
  8. Keep evidence visible. A table cell never replaces the evidence-use or reliance relation.

F.7:13 - Relations

Builds on:

  • Use F.1 for the exact source cut and receiving question, and use F.2 and F.3 for exact expressions and source-local claims.
  • Use F.17 only when durable local-meaning addresses are needed.
  • Use F.5 for selected designations without making them the values being named.
  • When the relation is between distinct source-local meanings, use F.9 to define and test it for those meanings and to state the separate bounded-use claim. A table creates none of these facts.

Constrains:

  • F.4 may cite a table for reader navigation, but the direct kind description and C.3 membership criterion remain the basis for a local system-role-kind claim.
  • F.6 may reuse a designation from the table; the row supplies neither classification, assignment, Work, nor performed-work attribution.

Used by. Part C patterns may use the table as a didactic comparison surface. B.3 may rely only on exact evidence and obtaining relations, never on row position or a computed row score.

F.7:14 - Migration notes

  1. Relation changes. Update the exact relation cell and re-evaluate only the receiving-use conclusions that depended on it.
  2. New source. Do not auto-expand rows; add it only if it changes the stated comparison.
  3. Local claim splits. Replace the old entry with the relevant child claim or split the comparison.
  4. Use widens. Re-evaluate the new use directly; a former row label grants no promotion.
  5. Designation changes. Update F.5 wording without changing source-local entries or relations.
  6. Edition changes. Recover the successor claim and recheck affected relations; preserve the earlier source identity where historical claims remain relevant.

F.7:15 - Acceptance tests

F.7:15.1 - Static conformance

  • SCR-F7-S01 (exact entries). Every local entry identifies an exact claim or F.17 cell and its source and edition.
  • SCR-F7-S02 (no row-created fact). No relation or permission is inferred from co-placement, label similarity, or layout.
  • SCR-F7-S03 (relation basis). Every positive relation cites the pattern that defines, constrains, or tests it, states direction where relevant, and cites its evidence.
  • SCR-F7-S04 (receiving use). The row states the practical use conclusion separately from the relation between the entries and gives the grounds for that use.
  • SCR-F7-S05 (loss disclosure). Material limitations and counterexamples remain visible.
  • SCR-F7-S06 (parsimony). Every extra entry changes the current comparison or use.

F.7:15.2 - Regression

  • RSCR-F7-E01 (relation drift). A changed relation triggers re-evaluation of dependent use conclusions, not a global row score.
  • RSCR-F7-E02 (sense split). A split local claim leaves no ambiguous cell reference.
  • RSCR-F7-E03 (use integrity). No consumer treats a row label as licence outside the stated conclusion.
  • RSCR-F7-E04 (no stealth growth). New entries create no silent relation, closure, or widened use.

F.7:16 - Didactic distillation

“A Concept-Set table displays a comparison. Put exact source-local claims in it and show established relations with direction and loss. State separately what the named comparison or use may conclude and why. Row position, shared labels or a row-wide CL do not establish those relations or warrant their use. Where no relation is established, show a contrast. The layout helps readers inspect the supplied reasoning.”

F.7:End

Referenced in the corpus

37 literal mentions in other sections. Read their context to establish the relation.