CMI 5 Working Group Meeting Minutes – November 6th - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – November 6th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Megan Bowe (Making Better)
• Yifei Dong (KeyBridge Technologies)
• Simon Hsu (KeyBridge Technologies)
• Brian Miller (Rustici Software)
• Henry Ryng (InXSOL)
• Kevin Owens (University of Texas at Austin)
• Geir Fuhre Pettersen (Conexus)
• Mike Hernandez (Design Interactive)
• Christopher Thompson (Medcom, Inc.)
• Eileen Quenin (Boeing)

Notes

cmi5 narrative presentation

The group resumed work on the cmi5 narrative (presentation): Module 1 - Conceptual Overview of cmi5 focusing on the definitions for each item on the flow chart (Components and Roles). The following is the current state of the draft:

Components

• Course Package – A ZIP with a course structure (see below) and, optionally, learning content media files.
• Course Structure - A list of assignable units (see below) and their launch parameters, with an implied sequence, representing a course.
• LMS – Learning Management System. A system that includes the capabilities to register learners, launch learning presentations, analyze and report learner performance, and track learners' progress.
• LRS – Learning Record Store. A web service that receives, stores, and retrieves xAPI statements.
• AU – Assignable Unit. A separately launchable learning content presentation. The AU is the unit of tracking and management. The AU collects data on the learner and sends it to the LMS.

Roles

• Learner – The user who is interacting with the learning content with the purpose of acquiring knowledge, skills, or abilities.
• Author - A user who assembles assignable units into a course package for consumption in the LMS. The author may also create the Assignable Units or reference them from other sources.
• Administrator – A user who ingests the course package into the LMS and provides access to the course for learners.

Process

1. Author creates one or more units of separately launchable learning content presentations (AU’s) that can communicate using cmi5.
2. Author creates a course structure XML file that references the AU’s URI location and provides Metadata for launch, description, and identification. The author also provides completion requirements rules.
3. The AU’s files may be referenced from an external host or be placed in a ZIP file along with the course structure XML.
4. Once the course package is completed, it is ready to be ingested into the LMS.
5. The administrator imports the course package either as a XML file or a ZIP file containing the XML and media files if any. (LMS copies stuff)
6. The administrator enrolls Learner(s) in the course associated with the imported course package. The enrollment is recorded in the LMS as a registration.
7. The learner initiates the launch of an AU by interacting with the LMS.
8. The LMS prepares launch data and records the launch in the LRS.
9. The LMS redirects the learner to the AU presentation.
10. The learner interacts with the AU and the AU records ____ and completion to the LRS

All Previous cmi5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

cmi5 on GitHub:

http://aicc.github.io/CMI-5_Spec_Current/