CMI 5 Working Group Meeting Minutes – July 19th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – July 19th
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Florian Tolk (ADL)
- Art Werkenthin (RISC, Inc.)
- Mark Grant (Independent)
- Christopher Thompson (Medcom, Inc.)
- Dennis Hall (Learning Templates)
- Attendee List Being compiled....
Notes
cmi5 vs TinCan "Package" comparison document
The group continued to revise the executive summary portion of the document. Current draft is as follows:
Executive Summary
The most commonly used mechanism for deploying xAPI-based learning content with a LMS does not have interoperability beyond launch and access to the LRS by the content –more is needed for practical implementation. The cmi5 specification addresses this need and is therefore recommended by the US Dept. of Defense (See DoDI 1322.26 - https://adlnet.gov/dodi/dodi-xapi)
The xAPI specification makes no mention of the LMS as it was intended to track training activities beyond the LMS. In the absence of a defined specification for packaging and launching xAPI activities from an LMS, early in life cycle of xAPI (2013) a quasi-defacto mechanism was created to fill the void. This mechanism is based on a document called “Incorporating a TinCan LRS into an LMS” (https://github.com/RusticiSoftware/launch/blob/master/lms_lrs.md). While the TinCan packaging mechanism is very thinly defined and is not an ADL specification, it has been widely adopted in the Learning industry.
To address this, ADL and the Aviation Industry Computer-Based Training Committee (AICC) jointly created the cmi5 specification. ADL actively maintains cmi5 as an xAPI profile that defines how the "LMS launches content" should be implemented using the Experience API (xAPI) as the content-to-LMS communication layer. cmi5 provides many elements that the TinCan package does not support:
- Consistent rules that define completion criteria, such as a mastery score.
- Defined tracking of results.
- Defined method to launch content without a pop-up window.
- Multi-lesson packages.
- Nested blocks of lessons.
- Complete course definition, including title and objectives.
- Built-in mechanism for support of distributed content.
Please Note: There has been some confusion on the use of the terms “xAPI” vs. “TinCan” with relation to the packaging of xAPI content for an LMS. This package is not defined in the xAPI Specification and the only known documentation of this package is in the “TinCan” document discussed above. Therefore, for the remainder of this document we will refer to that package as “TinCan”.
cmi5 Registration Clarified Definition
The group agreed on the following revised language to clarify the definition of "Registration" in the cmi5 spec.
Registration: An enrollment instance of a learner in a course. (a registration ID uniquely identifies this). The registration ID persists throughout the course progress to completion and during review of a completed course. A new registration is created for new enrollment instances (such as recurrent courses or re-taking courses).
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: