fpf.tools
Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading
Source · lines 1294–1307

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:10:10 UTC

SIE.7:11 - SoTA-Echoing

The best-known line combines declarative mapping languages, model transformation, traceability, and representation-preservation checks. The serious default is code-first ETL. Code is necessary in many realizations, but as the sole specification it hides semantic premises and loss. SIE.7 adapts the line into a technology-independent, receiving-use mapping contract with explicit negative states.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF A.6.3.RTadoptGoverns preservation through representation transition; it does not specify this domain mapping.
R2RMLadaptDemonstrates declarative relational-to-RDF mapping structures; RDF and relational sources are optional technology families.
OMG QVT 1.3adaptContributes model-query/view/transformation and trace forms; MOF/QVT is not mandatory.
PROV-OadaptSupports derivation and activity/agent/entity trace; provenance does not prove semantic preservation.
code-first ETL as sole contractreject as sufficientExecution can be tested only against an independently recoverable rule, loss, and branch contract.

Reopen when an input or target scheme changes, a correspondence/identity/composition premise changes, a counterexample defeats the rule, the receiver changes accepted loss, or implementations cannot satisfy the preservation predicate.