CONCEPT Cited by 1 source
Semantic interoperability¶
Definition¶
Semantic interoperability is the property that two systems can exchange data and preserve its meaning — not just its shape. Syntactic interoperability only guarantees "both sides can parse the bytes"; semantic interoperability adds "both sides agree on what those bytes mean."
In practice this requires a shared conceptual vocabulary — a domain model — that both sides map their local representations onto, so that equivalent concepts resolve to the same nodes regardless of which system is the origin.
Why UDA treats it as a hard requirement¶
Netflix's UDA post states the requirement explicitly: "We needed a data catalog unified with a schema registry, but with a hard requirement for semantic integration. Connecting business concepts to schemas and data containers in a graph-like structure, grounded in strong semantic foundations, naturally led us to consider a knowledge graph approach." (Source: sources/2025-06-14-netflix-model-once-represent-everywhere-uda)
Without it, the four UDA pain points — duplicated models, inconsistent terminology, data-quality discrepancies, limited connectivity — persist even with a schema registry, because a schema registry only ensures syntactic consistency of individual systems' contracts.
What it takes to achieve¶
The UDA recipe — and the general recipe inherited from semantic-web research — is:
- Shared conceptual vocabulary — one domain model per concept, agreed across systems.
- Explicit mappings from every system's local representation to the shared vocabulary.
- A graph substrate in which both concepts and mappings are first-class addressable data.
- Monotonic / conservative extension — adding new vocabulary can't break prior mappings.
- Resolution mechanism — a way to follow references across modular units. For UDA that's the named-graph-first info model (concepts/named-graph).
Contrast with syntactic interoperability¶
| Layer | Question answered | Tool |
|---|---|---|
| Syntax | Can the other side parse my bytes? | Avro / Protobuf / JSON Schema |
| Semantics | Does the other side interpret them the same way? | Shared domain model + mappings |
An engineering org that only enforces syntactic interoperability
still ends up with three systems that all publish valid
{actorId: string} messages but disagree on whether actor means
cast member, voice actor, or body double.
Seen in¶
- sources/2025-06-14-netflix-model-once-represent-everywhere-uda — Netflix UDA names semantic interoperability as the load- bearing requirement that pushed the design towards a knowledge graph over RDF + SHACL.
Related¶
- systems/netflix-uda · systems/netflix-upper — the platform + authoring language that serve this goal.
- concepts/knowledge-graph — the structural substrate UDA chose.
- concepts/domain-model — the shared-vocabulary primitive.
- concepts/named-graph — the modular unit UDA stacks for resolution.
- concepts/rdf — the triple model UDA builds on.
- concepts/conservative-extension — the composition-safety property.
- patterns/model-once-represent-everywhere · patterns/schema-transpilation-from-domain-model — the patterns that operationalise semantic interoperability in UDA.