Packages, protocols, and the difference between them.
A SCORM package is a zip a learning management system imports. cmi5 is also a package specification, but the course inside it sends xAPI statements. xAPI on its own is a statement protocol with no packaging — it needs a learning record store to send to. SCORM Central builds SCORM 1.2, SCORM 2004 4th Edition, cmi5, and xAPI. AICC is not supported.
Which standard should you choose?
Start from the LMS the course has to run in; most of the decision follows from that.
- SCORM 1.2 — the safe default when the course has to import into an LMS you do not control. A compliance course sold to many customers, each on a different platform, ships as 1.2.
- SCORM 2004 — when your LMS supports it and you need completion and success tracked separately, or sequencing rules that enforce order. A certification course whose final exam unlocks only after every module is viewed needs 2004.
- cmi5 — when the LMS imports packages but you want interaction-level data rather than one status and one score. A sales onboarding course where you need to see which scenarios learners got wrong, not just whether they passed.
- xAPI — when learning happens outside an LMS course: a simulator, a mobile app, or an on-the-job checklist, each posting statements to an LRS. A forklift simulator that records every attempt alongside the classroom course.
| Standard | Form | Reports through | Status |
|---|---|---|---|
| SCORM 1.2 | Package (zip) | cmi.core.lesson_status, cmi.core.score.raw | Supported |
| SCORM 2004 4th Edition | Package (zip), single SCO | cmi.completion_status, cmi.success_status, cmi.score.scaled | Supported |
| AICC | HACP exchange | HTTP form posts, no zip import | Coming soon |
| cmi5 | Package (zip) | xAPI statements against an LRS | Supported |
| xAPI | Statement protocol, not a package | POST /xapi/statements to an LRS | Supported |
How the four standards differ in practice
The fields and limits below come from the specifications themselves: the SCORM 1.2 and SCORM 2004 4th Edition run-time books, the cmi5 specification, and xAPI 1.0.3. They are the details that decide whether a course reports correctly once it is in someone else's system.
| SCORM 1.2 | SCORM 2004 4th Ed. | cmi5 | xAPI | |
|---|---|---|---|---|
| Package | Zip with imsmanifest.xml | Zip with imsmanifest.xml | Zip with cmi5.xml | None (a tincan.xml zip by convention) |
| Launched by | The LMS, in a browser window or frame | The LMS, in a browser window or frame | The LMS, by URL with endpoint, registration and auth token | Any link, app or device with LRS credentials |
| Talks to | JavaScript API: LMSInitialize, LMSSetValue | JavaScript API: Initialize, SetValue | xAPI statements over HTTP | xAPI statements over HTTP |
| Completion | cmi.core.lesson_status | cmi.completion_status | completed verb | Whatever verb the course sends, usually completed |
| Pass or fail | Same field: passed / failed | cmi.success_status, separate from completion | passed / failed verbs | result.success |
| Score | cmi.core.score.raw with min and max | cmi.score.scaled (−1 to 1), plus raw | result.score.scaled | result.score |
| Saved state | cmi.suspend_data, 4,096 characters | cmi.suspend_data, 64,000 characters | xAPI State API | xAPI State API |
| Needs an LRS | No | No | Yes, provided by the LMS | Yes |
| Different domain from the LMS | Breaks without a proxy | Breaks without a proxy | Works | Works |
Cross-domain trouble is the most common reason a working package fails after a move to a new host; SCORM cross-domain launch explains why. For the suspend-data caps by edition, see suspend data limits.
SCORM 1.2
The most widely imported package format. Completion and score report through cmi.core.lesson_status and cmi.core.score.raw. Suspend data is capped at 4 KB on strict runtimes, which is the most common reason a 1.2 course loses its bookmark.
SCORM 1.2 data model reference →
SCORM 2004 (2nd–4th Edition)
Separates completion from success: cmi.completion_status, cmi.success_status, and a normalised cmi.score.scaled. Adds sequencing and navigation rules in the manifest and raises the suspend-data ceiling to 64 KB. SCORM Central builds 4th Edition, single-SCO packages.
SCORM 2004 data model reference → Sequencing rules →
AICC
An HTTP form-post exchange (HACP) rather than a zip import. Still requested by some regulated-industry platforms. Not in SCORM Central yet; it is on the roadmap.
cmi5
A package the LMS imports, but the course inside it sends xAPI statements to an LRS. You get packaged distribution with statement-level reporting. Requires an LRS. SCORM Central builds cmi5 packages on Starter and up. Its built-in LRS comes with Pro and Business.
xAPI
A statement protocol, not a package. A plain xAPI course is launched from a link, records interactions, paths, and durations, and posts to /xapi/statements on an LRS. Use it when you want more than a single pass or fail. SCORM Central builds xAPI output on Starter and up. Forwarding statements from its built-in LRS to yours comes with Business.
Test profiles, not compatibility promises
A profile is a saved set of runtime behaviours for a particular LMS — commit timing, suspend data ceiling, how the platform handles a missing score — that you replay your package against. A passing profile means the package behaved correctly under those conditions, not that a given vendor has certified it.
Standards questions
The spec library has the full data models, element by element.
Is SCORM 2004 better than SCORM 1.2?
What is the latest version of SCORM?
Do I need an LRS for SCORM?
Does cmi5 replace SCORM?
Start with one file.
Upload a PowerPoint, PDF, or video you already have, build it as a SCORM package, and run it in the tester to see every call it makes.
→ upload handbook.pdf rendering … 86 pages course … 1 lesson, 86 pages building … SCORM 2004 4th Ed validating … 0 errors ✓ handbook-scorm2004.zip