SCORM.ing
← All Standards

cmi5

emerging

cmi5: xAPI Profile for LMS

2016

cmi5_overview.md

cmi5 is an xAPI Profile that defines how an LMS launches and tracks xAPI-based content. It was developed by the AICC (in its final major project before disbanding) and later maintained by the ADL Initiative and IEEE.

Where xAPI is intentionally open-ended — it defines how to record statements but not how to launch content or package it — cmi5 adds the structure that LMS vendors and content creators need. It specifies a launch mechanism, a defined set of "must-use" xAPI statements (launched, initialized, completed, passed, failed, terminated), and a content packaging format.

Think of cmi5 as the spiritual successor to SCORM, built on xAPI's modern foundation. It provides the interoperability guarantees that LMS buyers demand while preserving xAPI's ability to track rich, cross-platform learning experiences.

Adoption has been growing steadily, with major LMS platforms adding cmi5 support. It's widely seen as the future replacement for SCORM in traditional LMS-based training delivery.

key_features.txt

Key Features

  • [+]LMS launch mechanism for xAPI content
  • [+]Defined "must-use" xAPI statement vocabulary
  • [+]Content packaging via XML course structure
  • [+]Supports both LMS-managed and AU-managed sessions
  • [+]MasteryScore and moveOn rules for completion logic
known_limitations.txt

Limitations

  • [-]Still gaining LMS adoption
  • [-]Requires both LRS and LMS infrastructure
  • [-]More complex than SCORM 1.2 to implement
  • [-]Fewer authoring tools with native support
  • [-]Learning curve for teams transitioning from SCORM
technical_spec.json

Technical Details

data Model:

xAPI statements with cmi5-defined verbs (launched, initialized, passed, failed, completed, terminated)

communication:

xAPI REST API via LRS, with LMS providing launch URL and authentication token

packaging:

cmi5.xml course structure with Assignable Units (AUs) and Blocks

tracking:

Completion, success, score via defined xAPI statements; extensible via additional xAPI statements

historical_notes.md

Historical Context

The AICC's final gift to the eLearning industry was cmi5. Recognizing that xAPI alone wasn't enough to replace SCORM in LMS environments, the AICC working group (led by Art Rust and Bill McDonald) created a specification that bridged the gap. The name 'cmi5' is a nod to the CMI (Computer Managed Instruction) data model that has been at the heart of eLearning standards since AICC.