CMI 5 Working Group Meeting Minutes – October 9th

cmi5 Working Group Meeting Minutes – October 9th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Art Werkenthin (RISC, inc)
• Megan Bowe (Making Better)
• Yifei Dong (KeyBridge Technologies)
• Simon Hsu (KeyBridge Technologies)
• Brian Miller (Rustici Software)
• Henry Ryng (InXSOL)
• Tracy Cowan (Southwest Airlines)
• Kevin Owens (University of Texas at Austin)
• David Pesce (Exputo)
• Geir Fuhre Pettersen (Conexus)
• David Mallette

Notes

cmi5 narrative presentation

The group resumed work on the cmi5 narrative (presentation) and re-defined the high level course outline as follows:

• Module 1 - Conceptual Overview of cmi5
• Module 2 - AU Implementation - Based on cmi5 Implementation Flow for an LMS
• Module 3 - LMS Implementation - Based on cmi5 Implementation Flow for an AU

The audience for the presentation is as follows:

• Tool Developers (AU or LMS) - Primary Audience
• Data Science/Engineers/Analysts - Secondary Audience

The "Prerequisites" for understanding the presentation are a high level understanding of what xAPI is. (The presentation may provide references to existing background information sources on xAPI)

Module 1 - Conceptual Overview of cmi5

The group defined the following draft outline for module 1:

1. Problem Statement - How to use xAPI
   • xAPI covers many use cases
   • You need a profile to use xAPI because it is very broad
2. xAPI has the following:
   • data model (data structure)
   • transfer protocol
3. In order to have "complete interoperability", you also need the following (which cmi5 provides) :
   • Information Model (the "meaning" is here)
   • Content Package (Course Structure, Media location)
   • Launch Mechanism (including authorization)
4. cmi5 concepts
   • LMS
   • AU
   • Course Structure
     • MoveOn
     • Blocks
     • Metadata (Objectives, Title, Description, Parameters)
   • Launch/Fetch URL
   • Session/State
   • cmi5 allowed statements

Objectives

The group reviewed the best practice for AU's to report on objectives.

Best Practice #1 – Use of Objectives (Since Objectives usage outside of course structure is not defined.)

Objectives are defined for the course structure, but there is no language in the specification concerning their usage in statements. If an AU is using Objectives in statements, the best practice is to add the objective (with the same objective id provided in the course structure) to the context activities “parent” property as an activity type of (http://adlnet.gov/expapi/activities/objective) from the ADL vocabulary.

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/