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

Source changed 2026-11-22 23:12:12 UTC · snapshot created 2026-11-22 23:13:03 UTC · last check 2026-11-22 23:15:15 UTC

E.10.ARCH:13 - Rationale

Repair-only trigger prose migrates into subject patterns and begins to compete with their primary EntityOfConcern and first useful moves. One symptom is a Solution dominated by warnings about descriptions and publications. F.19 removes a proposed rhetorical boundary when it lacks independent local ground for a plausible intended-reader mistake or makes no difference to understanding or use.

A warranted guard may still be misplaced. Keep it with the rule for publication pragmatics, description pragmatics, admissible use, or the neighboring subject claim it qualifies. The subject pattern’s Solution remains about its own EntityOfConcern and first useful move.

The workable split is whole-span repair in F.19, compact recognition and routing in E.10, shared ontological recovery here only when needed, and local realization only where a named semanticArea has stable row identity, a stable field set, an ontologicalNeighborhood, and a useful remaining reader use.

E.10.ARCH:13.1 - SoTA-Echoing

Practice question. When the same wording problem recurs across subject patterns, what distribution keeps the repair reusable while letting practitioners reach the exact object, relation, claim, and defining or testing rule without filling an authoring form?

Selected best-known line. Use ISO 704’s object, concept, definition, and designation discipline for terminology work; use SKOS only when a controlled-vocabulary or knowledge-organization object is current; and distribute each FPF claim to its direct subject rule through one shared trigger scan and one shared recovery architecture. Keep a local realization only when a stable recovery shape and remaining reader use recur.

Alternative or default. A central preferred-word list makes labels consistent but cannot establish obtaining relations, actual participants, claim-bearing epistemes, or direct rule ownership. Copied local warning tables stay close to each subject but duplicate recognition, drift independently, and displace the subject pattern’s working problem. The selected line keeps the useful locality of direct owners and the reuse of one shared entry.

Bounded comparison and accepted trade-off. Take the section 0 case in which MethodDescription_NormalizeCustomer says “input x is CustomerRow_17” beside normalize(x). Give each distribution the same source sentence, formula, and one applicable recovery entry. A preferred-word list can standardize the label input, but that alone leaves open whether it names an argument representation or a declared participant slot. Both a correct subject-local table and the shared architecture can recover Arg_x and its correspondence to CustomerRow_17, then state the recovered representation relation.

They yield the same sentence: “In the worked formula normalize(x), argument x represents CustomerRow_17.” Because that use is already clear here, both approaches can stop at the sentence; C.29 is needed only if a separate mathematical representation or transfer question remains.

For an unresolved recurrence, a local table offers a nearby lookup; the shared entry may require a cross-reference. In return, the shared distribution keeps the recognition and recovery rule in one maintained place, while copied tables require their copies to be kept consistent.

Adopt the shared entry with direct-known-rule bypass, accepting that possible extra lookup to avoid duplicated rule maintenance. Preserve a local realization when its stable field set and remaining use justify it. This qualitative comparison establishes the distribution choice for the stated recurring case; it claims neither measured speed nor a benefit from centralizing the subject rules themselves.

Source or practice lineSource role and contribution usedLimitSmallest reopen condition
Current FPF distribution: E.10, E.10.ARCH, E.10.LRN, E.10.DEV, E.10.ROLE, E.10.MOVE, E.4.DPF, A.6.P, A.6.F, C.2.P, C.30.P, C.30.STRAT, C.16.P, C.16.Q, A.19.SPR, F.18, F.19, E.8, E.19, E.11Governing local architecture: shared recognition, bounded recovery, DPF-local entry, direct-owner return, and practitioner bypass when the rule is already knownIt is not external evidence that the same distribution is best for every terminology systemReopen only the affected distribution step when a named pattern changes its contribution or when one recurring case cannot reach a direct claim or exact gap at comparable effort
ISO 704:2022, Terminology work — Principles and methods, edition 4, 2022-07Current external terminology-work line: preserve links among objects, concepts, definitions, and designations; adapt that object-first discipline before term formationIt does not define FPF kinds, make project relations obtain, or prescribe this framework’s pattern distributionReopen the object-first terminology contribution only if a later edition changes the used object, concept, definition, or designation relation
Miles and Bechhofer (eds.), SKOS Simple Knowledge Organization System Reference, W3C Recommendation, 18 August 2009Stable external knowledge-organization line. Use SKOS for controlled-vocabulary publication, designations, labels, and label relations when those are the actual objects; use F.18 and the relevant subject pattern for reusable FPF names and claims. SKOS concepts, notations, schemes, and mappings retain their own source meanings.It is not a universal wording-repair ontology and does not define FPF world-side kinds or direct claimsReopen only if the Recommendation or its current successor changes the label, concept-scheme, collection, or mapping contribution used here
Current E.8 and E.19 pattern-locality and primary-EntityOfConcern rules, together with the subject-pattern coverage named in E.10.ARCH:4 and E.10.ARCH:14Governing local evaluation basis: keep subject patterns centered on their working object and use an existing defining or testing rule when it already closes the claimExisting coverage does not prove that every future wording family fits this architectureReopen when subject patterns again need copied first-stage doctrine, a realization needs a different stable field set, or an existing subject rule absorbs the same entry, result, and stop

Lower only the affected row when E.10 can close it locally or a subject rule absorbs the same recovery at equal or lower effort.