Cmi5
Introduction
cmi5 is a xAPI profile, originally proposed by the AICC working group (one of the earliest actors in elearning standardization).
The specification “describes interoperable runtime communication between Learning Management Systems (LMS) and Assignable Units (AU)” (cmi5 Specification Profile for xAPI, retrieved July 2018). More precisely it defines how to use the [[xAPI] specification for the following:
- Launch by an LMS of AUs.
- Launch and runtime environment used by LMS and AUs.
- Runtime communication data and data transport between the LMS and AUs.
- LMS course definition as it pertains to runtime data used by AUs.
- LMS Course Structure Import/Export
- Reporting requirements for the LMS.
Versions:
Major versions have stone names (they might have used them alphabetical order)
- Sandstone (First version: May 15, 2015)
- Quartz (First version: June 1, 2016)
Basic mechanism
Learning objects are called Assignable Units (AU) and are defined as: “learning content presentation launched from an LMS. The AU is the unit of tracking and management. The AU collects data on the learner and sends it to the LMS.” (cmi5 specification, V. Sandstone)
A course is then defined a as a collection of AUs and its course structure is a “list of assignable units and launch parameters, with an implied sequence” (ibid)
The learning management system [LMS] is defined as “A computer system that may include the capabilities to register learners, launch learning presentations, analyze and report learner performance, and track learners' progress. LMS launching, reporting, and tracking roles are the focus of the cmi5 specification. The LMS must have an LRS as part of its implementation.”
Links
Official
Specifications
CMi5 makes the use of the following specifications:
- Experience API", version 1.0.x
- ISO/IEC 21320-1:2015 (Information technology — Document Container File — Part 1: Core)
- XML (see XML)
- JSON (see JSON)