Schema-driven data contract (Frictionless Table Schema)
Schema-driven data contract (Frictionless Table Schema)
BusDK modules interoperate through shared tabular datasets: rows plus an explicit, machine-readable schema that defines the table’s field names, types, and constraints. The schema is part of the canonical dataset and travels with the data so that independent modules — and external tools — can validate and process tables consistently without sharing code.
Schemas are expressed using Frictionless Data Table Schema (JSON). BusDK follows the upstream specification as closely as possible; any BusDK-specific semantics must be implemented as optional, namespaced extensions (for example, custom properties under a busdk:* key) that do not break compatibility with standard Table Schema tooling.
Frictionless Table Schema is a preferred implementation, not the goal itself. In BusDK terms, the data contract is ((table, schema)): each table must have a clear contract that can be validated, diffed, and evolved over time while keeping older revisions interpretable and exportable.