From Learning Solutions Magazine by Art Werkenthin
The cmi5 specification working group recently completed a two-day meeting at the AdvancedDistributed Learning initiative (ADL) Co-lab facility in Alexandria, VA on April 15 & 16, 2015. The purpose of the meeting was to finalize a draft release of the cmi5 specification and set target dates for initial release.
The cmi5 specification is an Experience API (xAPI) protocol, designed as the “use case” for xAPI in learning management systems (LMS). The specification defines how learning content is imported, launched, and tracked by the LMS using an xAPI learning record store (LRS).
The meeting also had daily web conferences to inform the larger community on the specification and solicit feedback.
As a result of this meeting, the initial draft release will be named “cmi5 Sandstone.” It is planned for release in early May 2015. Sandstone is intended to be a release for developers to validate with working implementations and/or prototypes. The first release of the completed standard is planned for September 2015.
You may have noticed a change in the branding of the spec name: it has evolved from CMI-5 to cmi5. cmi5 versions will be named after geologic rocks for version identification.
Below are a few results from the two-day meeting (source: ADL cmi5 group meeting minutes; see the link at the end of this article).
Satisfied verb for blocks and course
As a result of discussions during the onsite meeting, it was agreed that a verb was needed to record complete/passed (i.e., “satisfied”) to the LRS for a course and for individual blocks within a course. This addresses the “rollup” issue for recording at course or block level. The “Satisfied” verb will be used in a statement written by the LMS to the LRS when all assignable units (AUs) in a block or course are satisfied based on their “moveOn” criterion. Block Id’s were also added to the course structure to support the recording of “Satisfied” statements.
Remove verbs—Suspend and Resume
It was determined during the meeting that “Suspend” and “Resume” verbs were unnecessary given the function of the State API and the other statements recorded during an AU session.
Given some of the issues and uncertainty surrounding Oauth (open standard for authentication), it was determined that cmi5 will only use “basic authentication” (using the Fetch URL) for the initial release. Future releases will include other authentication methods (including OAuth).
There were other changes to the specification; these are included in the full meeting notes (see link below).
For more information on cmi5, please see the following: https://github.com/AICC/CMI-5_Spec_Current
For the full meeting notes, please see the following: https://github.com/AICC/CMI-5_Spec_Current/wiki/CMI-5-Working-Group-Meeting-Minutes-%28Washington,-DC%29-–-April-15-16th,-2015