CMI 5 Working Group Meeting Minutes – October 23rd - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – October 23rd

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Dennis Hall (LearningTemplates)
• Megan Bowe (Making Better)
• Yifei Dong (KeyBridge Technologies)
• Simon Hsu (KeyBridge Technologies)
• Brian Miller (Rustici Software)
• Tammy Rutherford (Rustici Software)
• Tim Edwards (Rustici Software)
• Henry Ryng (InXSOL)
• Kevin Owens (University of Texas at Austin)
• David Pesce (Exputo)
• Geir Fuhre Pettersen (Conexus)
• 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
  • Launch/Fetch URL (Launch Mechanism)
    • Launch URL provides connectivity to the LRS
    • LRS location (end point)
    • User Identifier (Learner provided by the LMS)
    • Activity ID (provided by the LMS to identify the AU)
    • Registration (enrollment in a course)
  • Fetch URL
    • Provided in the Launch URL
    • Used to retrieve authorization to connect to the LRS
    • One time use
• Session/State (Session Management)
  • A period of time marked by the launch of an AU (Learning Activity) until its termination.
  • Session is identified by an ID provided from the LMS via a State Document.
  • All statements made during the sessions are marked with this ID.
  • All statements made by the AU must follow the template provided
• cmi5 allowed statements
  • There are some statements that are required by cmi5 (and some that have specific usage rules for cmi5)
  • However, the AU can send additional statements outside the scope of these defined statements provided they have the session id (and context)
  • This allows content developers to record any verbs desired and still be interoperable. (inherently extensible)

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/