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:05:20 UTC

E.20:4.5 - Step 5: Keep operation-member names consistent across a suite

Use this step only when a suite or family claims that several mechanism declarations use a common vocabulary for operations, arguments or results by design. Repeated spelling by itself does not establish that claim.

  1. The suite-subject pattern SHALL name one citeable vocabulary locus and the member mechanism declarations to which the shared terms apply. That vocabulary coordinates names only; it creates no OperationDeclaration, ArgumentDeclaration, ResultDeclaration, ValueKind, binding predicate, or actual binding.

  2. Each member mechanism SHALL declare every current operation, argument, and result locally under A.6.1, including its exact meaning, ValueKind, designation rule, binding predicate, and cardinality. A cited shared term or equal spelling imports none of those semantics.

  3. When a public shared term is introduced, renamed, split, or merged, update the shared vocabulary locus and every affected declaration or alias route. When only one declaration changes meaning, keep the change local unless the intended shared denotation also changes. Apply E.20:4.9 whenever citeability changes.

The shared vocabulary keeps the suite term consistent. Each A.6.1 operation member retains its declaration-local semantics. The vocabulary supplies neither an operation position nor an actual application binding.