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:35:10 UTC

SIE.7:4 - Solution

Specify semantic mapping rules separately from their implementation. Bind every rule to a receiving-use contract, the source and target schemes, accepted correspondence premises, and any identity or claim-composition premise on which that rule depends. Make selection, cardinality, conversions, defaults, errors, loss, trace, and tests explicit. Require implementations to preserve these behaviors or return a named discrepancy.

SIE.7:4.1 - Pattern-Use Unfolding

  1. Name the output claim and receiver. State the target field or proposition, its meaning, grain, interval/effectivity, and the action it supports.
  2. Bind source and target schemes. Reference the SIE.2 source rows and target interface/model definitions, editions, profiles, units, codes, identifiers, and access assumptions.
  3. Bind semantic premises. Reference accepted SIE.4 correspondence rows and every load-bearing SIE.5 identity disposition. Reference a SIE.6 composition or conflict result when the rule depends on that result. Stop on an unresolved required premise; do not require identity or claim-composition work that cannot change the rule.
  4. Specify selection and extraction. State source records, predicates, joins, windows, configuration/effectivity filters, ordering, and behavior for missing or duplicate inputs.
  5. Specify transformation. State direction, construction, decomposition, aggregation, unit/code conversion, normalization, derivation, and required external lookup. Name the authority for any conversion or code table.
  6. Specify cardinality and identity preservation. State one-to-one, one-to-many, many-to-one, or conditional behavior; keep source identifiers and disposition references when rows combine or split.
  7. Specify defaults and errors. Distinguish absent, unknown, not applicable, inaccessible, stale, incompatible, unresolved, source failure, and actual zero or empty value. Permit a default only when the contract and semantic warrant state its meaning and loss.
  8. State information loss and forbidden reuse. Name omitted distinctions, coarsening, precision, interval, provenance, or conflict and the use for which the loss is accepted.
  9. Provide trace and examples. Give stable rule identifiers, input-to-output trace positions, positive examples, boundary and counterexamples, and expected negative branches.
  10. Define implementation conformance and reopen. State observable behavior an implementation must match and source, premise, contract, or target changes that invalidate the rule.

SIE.7:4.2 - Record the Result

Mapping positionRequired content
rule and usestable rule identifier, receiver, output claim, grain, interval/effectivity
schemessource/target assets, models/schemas, editions/profiles, fields/types/relations, units/codes
semantic inputsaccepted correspondence rows and any relied-on identity dispositions or composition/conflict results, with their conditions
extractionselection, joins, filters, windows, effectivity, duplicates, missing-input behavior
transformationdirection, construction/decomposition/