Your training, in a format you can take anywhere.
The Open Workout Schema records what someone did: a workout, its exercises and sets, where the record came from, and which numbers were inferred. Any app can write it, any assistant can read it, and the person keeps the log.
Honest numbers
A set holds what the person stated, in the unit they gave. Anything inferred is listed in estimates by JSON pointer, so a number's standing travels with it.
Provenance on every record
source says which app or assistant wrote it and the record's ID there; merged_sources keeps both when two apps describe the same session.
One language for exercises
Each entry names its exercise by an Open Exercise ID and says whether the match is sure, close, the person's own, or unmatched.
Documents
- workout
- One workout: exercise entries with their sets, plus where the record came from. Draft; may change until v1.
- program
- What a workout or multi-week program prescribes: weeks, then days, then slots. A single workout has one week with one day. A prescription, never performed work: loads are rules, not weights. Draft; may change until v1.
Use it
- workout.json, JSON Schema (draft 2020-12), at its
$id - program.json, JSON Schema (draft 2020-12), at its
$id - The MCP tool profile: 20 tools, generated from the reference server
- An example workout and an example program
go run github.com/openexercise/open-workout/cmd/ows@latest validate my-workout.json