CMI 5 Working Group Meeting Minutes – December 4th

cmi5 Working Group Meeting Minutes – December 4th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Dennis Hall (Learning Templates)
• Art Werkenthin (RISC, Inc)
• Megan Bowe (Making Better)
• Allyssa Thompson (KeyBridge Technologies)
• Simon Hsu (KeyBridge Technologies)
• Brian Miller (Rustici Software)
• Henry Ryng (InXSOL)
• Geir Fuhre Pettersen (Conexus)
• Kevin Owens (University of Texas at Austin)

Notes

cmi5 narrative presentation

The group resumed work on the cmi5 narrative (presentation): Module 1 - Conceptual Overview of cmi5 adding the following section:

Introduction

The following document provides high-level description of cmi5. For specific details see the cmi5 specification.

cmi5 is a "profile" for using the xAPI specification with traditional learning management (LMS) systems.

Since the xAPI specification is highly generalized to support many different use cases, a set of "extra rules" (called a "profile") is needed to ensure interoperability for a given use case. The cmi5 profile ensures plug and play interoperability between learning content and LMS systems.

The use case that the cmi5 profile is specifically designed for is one where the learner launches the learning content/activity from the LMS user interface.

Why cmi5 ?

cmi5 provides rules for using xAPI with an LMS. It is a key component of an xAPI based learning ecosystem and an excellent starting point for organizations that wish to adopt xAPI.

cmi5 provides the following functionality :

• Richer Data Collection - Record any data you want (and get it back!) - You are not limited to a "list" of data collected. cmi5 is open-ended on the data you can collect.

• Share Data more easily - cmi5 uses a web service (xAPI) and data structure that allows easy integration with other systems/applications.

• Distributed Content - cmi5 content can reside anywhere, it allows for content as a service.

• Elimination of "Pop-up" Windows - Eliminates pop-up blocker headaches.

• Mobile app launch support - cmi5 content does not require a browser. Content could be a mobile app.

• Complete course definition:
  • Clearly defined rules that define completion criteria, such as a mastery score.
  • Multi-lesson packages.
  • Title and objectives definition
  • Nested blocks of lessons.

See complete document below:

• http://aicc.github.io/CMI-5_Spec_Current/flows/cmi5-overview.html

---

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/