Education

Semantic data contracts vs schema validation

Physical schema validation checks shape and type. A semantic data contract also binds meaning to a sealed revision.

How it works

A numeric amount can still represent a different obligation or currency from what the consumer expects. A semantic contract can carry supported definition/domain and physical constraints, identify affected dependencies when meaning drifts and produce a receipt. It cannot prove business authority or invent constraints.

Illustrative explanations describe the boundary, not a customer result. For specific evidence and integration scope see the linked product page.

Physical conformance versus meaning

A record with amount 1250 can satisfy a numeric type while meaning a fee rather than principal. A semantic contract binds the field to a sealed concept and evidence-qualified definition. A later definition change can stale a validation receipt without a physical type change. Strict validation does not confer permission to act. Contract assurance.

When is a type check insufficient?

An integer can be syntactically valid while its business definition changes. A schema alone may also record descriptions and constraints; the question is whether those meanings are bound to a governed evidence-qualified revision and whether old validation becomes stale when that revision changes. The actual A→T comparator reports DEFINITION_DRIFT for an unchanged INTEGER while changing the principal amount definition; A and T are separate sealed assets. A→B changes allowed values within one asset, and the prior receipt is stale.

See the actual validation and drift evidence.

Technical note by OntoGuard · product evidence and review scope are identified in the linked materials. Publication approval pending.

Evidence and buyer questions

How does it differ from schema validation?

Physical schema validation checks types and structural constraints. Native semantic comparison can also detect business-meaning changes: the v1.89.332 Principal Amount definition changes between separately sealed assets A and T while INTEGER stays unchanged. This is not same-asset definition drift.

Inspect source or product evidence