Schema Definition Languages (SDL)

Schema Definition Languages provide a structured way to define data models and ensure their integrity. They are essential in software development and support communication between different systems.

Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.

Content type

Concept

Theoretical construct: explains a term, principle, or mental model.

Classification level

Structure

What organizes, connects, or makes decisions possible.

Available perspectives

Open this building block directly in an already curated view.

360°

In brief

Schema Definition Languages (SDL) – in brief

A schema definition language formally describes the structure, types, and rules of an interface or data format so people and tools share the same contract.

Where does it come from?

SDLs emerged from the need to specify data and API contracts in machine-readable form. OpenAPI is a common format for describing HTTP APIs, including paths, operations, parameters, and schemas.

The mental model

An SDL document states which fields a message has, which types and constraints apply, and how operations are addressed. Documentation, validation, client code, and tests can be derived from it. The schema defines the contract; implementation, business semantics, and runtime conformance remain outside the document.

Key building blocks

Contract

The schema makes the allowed structure and rules of an interface explicit and machine-readable.

Toolchain

Generators, validators, and documentation can use one contract as a shared source.

Schema boundary

An SDL does not guarantee correct implementation, business semantics, or runtime availability.

When is it useful?

SDLs reduce misunderstandings between API producers and consumers and support validation and integration. They must be versioned, reviewed, and tested against real implementations.

OpenAPI Specification