SCORM is the packaging and runtime standard for e-learning content, developed by the US Department of Defense’s ADL Initiative. It defines how a course package is structured, how it is launched by a learning management system, and how it reports completion and score back through a JavaScript API.
SCORM
SCORM is the reason a course bought from one vendor plays inside another vendor’s LMS. It is old, it is a zip file with a manifest and a browser-side runtime, and it is still the lingua franca of corporate learning a quarter of a century after publication.
- Content packaging - A manifest describing structure, sequencing and resources inside a portable archive.
- A runtime API - A JavaScript interface between content and LMS for completion, score and time.
- Sequencing and navigation - Rules for how a learner moves through a package.
- Superseded but not replaced - xAPI covers what SCORM cannot, and SCORM remains the procurement default.
SCORM’s persistence is worth understanding as an API story. It solved content portability so thoroughly that the corporate learning market never needed to solve data portability, and in The State of Education & EdTech APIs that segment publishes a machine-readable contract 0% of the time with an agent-readiness of 0.0 — the only segment in the cohort at zero on both. A standard that works well enough can remove the pressure that would have produced the next one.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Education & EdTech APIs
Solved content portability so thoroughly that corporate learning never solved data portability — the segment publishes a contract 0% of the time, with an agent-readiness of 0.0.
