Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:00:09 UTC

SIE.8:11 - SoTA-Echoing

The best-known line combines declarative mappings, virtual knowledge-graph systems, data federation, materialized integration, and operational data-product practice. The serious default alternatives are “materialize one canonical graph” and “federate everything live”. Each can be correct under conditions; each is defective as a universal answer because it hides a different set of currentness, access, provenance, and recovery obligations. SIE.8 mutates the line into a whole-arrangement choice around one semantic result.

Source lineAdopt, adapt, or rejectRole and limit
Ontop virtual-KG lineadaptDemonstrates query-time virtual realization over mappings; it does not make virtual RDF mandatory or supply source access and receiving acceptance.
R2RMLadaptSupplies one declarative mapping form usable in virtual or materialized arrangements; relational/RDF technology is optional.
Data on the Web Best PracticesadaptContributes access, version, provenance, reuse, and persistence questions; Web publication is not required.
universal canonical graphreject as defaultMaterialization is one candidate and cannot transfer source authority or erase incompatibility.
universal live federationreject as defaultQuery-time access does not guarantee freshness, availability, permitted disclosure, or reproducibility.

Reopen when source access or replication rights change, measured latency/availability defeats the use, refresh/invalidation fails, mapping or source semantics change, security/provenance conditions change, or a new candidate materially improves the comparison.