CMI 5 Working Group Meeting Minutes – October 16th - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – October 16th

Attendees

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)
• Tracy Cowan (Southwest Airlines)
• Kevin Owens (University of Texas at Austin)
• David Pesce (Exputo)
• Geir Fuhre Pettersen (Conexus)
• David Mallette (Independent)
• Brandon Billings (SAE)
• Christopher Thompson (Medcom, Inc.)

Notes

cmi5 narrative presentation

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

Module 1 - Conceptual Overview of cmi5

The group updated the following draft outline for module 1:

Audience

• Developer (AU or LMS)
• Data Science/Engineers/Analysts (helpful)

Prerequisites

• High level understanding of what xAPI is

Problem Statement – You need a profile…

1. xAPI is broad - covers many use cases - it has:
   • data model (data structure)
   • transfer protocol
2. But, you also need :
   • Information Model (meaning is here)
   • Content Package (Course Structure, media location)
   • Launch Mechanism
3. In order to have complete interoperability

cmi5 concepts

• Intro definition (of the components/roles)
• Component Chart
  • Components
    • LMS
    • LRS
    • AU
    • Course Package
  • Roles
    • Learner
    • Author
    • Administrator
• Interaction between components
  • LMS
    • It implements (or integrates with) an LRS (Learning Record Store).
    • Ingest (course) Packages / Manifest
      • (Provides the Launch Mechanism for) Launches the content (AU – Assignable Unit)
    • Sends Parameters to AU (with state docs)
    • Evaluates the Course Structure “moveOn” (completion) rules.
    • Generates Statements (for specific events – Waived , Launch, Abandoned, Satisfied)
    • (Marks the Start of the Session)
  • Course Package/Course Structure
    • MoveOn
    • Blocks
    • Content/Learning Activity Metadata (Objectives, Title, Description, Parameters)
  • AU
    • The Learning Experience
    • Referenced in the Course Package
    • Get Launch Data & Parameters
    • Record Learner Events/Interactions
    • Determines Completion/Mastery (of itself)
    • (Marks the end of the Session)
• Launch/Fetch URL
• Session/State
• cmi5 allowed statements

cmi5 spec clarifications

The following the "LMS Usage" for the following Verb sections do not consistently reference their relationship to the moveOn rules and the Satisfied statement. Clarification language should be added to both sections to indicate the relationship (of Completed and Passed) to the moveOn/Satisfied obligations of the LMS.

• 9.3.4 Passed LMS Usage: > The LMS MUST use either "Passed" or "Completed" statements (or both) based on the "moveOn" criteria for the AU as provided in the LMS Launch Data. (See xAPI State Data Model, Section 10.0 - moveOn).
• 9.3.3 Completed - LMS Usage is "None"

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/