Taleem JSON Schema

The Taleem schema defines what a presentation is.

It is a structural contract that describes the shape of a Taleem deck, independent of how that deck is rendered, browsed, or played.

What the Schema Defines

The schema specifies:

• the overall structure of a deck
• the order of slides
• the available slide types
• the data fields each slide type accepts

If a JSON file follows this schema, it is a valid Taleem deck.

What the Schema Does Not Define

The schema does not include:

• layout or visual styling
• CSS or themes
• animation or transitions
• playback or timing behavior
• application or UI logic

These concerns belong to the renderer and the application, not the data format.

Pure Data Only

The Taleem schema contains only data.

There are no functions, callbacks, or executable logic. This allows the same deck to be reused across different environments without modification.

Explicit Slide Types

Every slide declares its type explicitly.

Each type accepts a fixed and known set of fields. Unknown or malformed data is rejected rather than guessed.

This keeps rendering predictable and prevents silent layout drift.

Validation

A deck is considered valid only if it conforms fully to the schema.

There are no partial modes, fallbacks, or best-effort rendering. Invalid data is treated as an error.

Why This Matters

Treating presentation content as structured data makes it possible to:

• generate decks programmatically
• render the same content in multiple ways
• keep systems deterministic and testable
• evolve renderers without rewriting content

The schema is the foundation that allows Taleem Player to remain stable while applications and renderers change over time.