-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – April 1st, 2016
cmi5 Working Group Meeting Minutes – April 1st, 2016
Attendees
- Bill McDonald - cmi5 working group leader
- Andy Johnson - ADL
- Art Werkenthin - RISC
- Ben Clark - Rustici Software
- Brian Miller - Rustici Software
- Bernard Bouyt - Airbus
- Mike Kennedy - Workday
- Dennis Hall - eLearning Templates
- Ray Lowery - Pratt & Whitney
- Charles Touron - ASTC
- Henry Ryng - inXsol
- David Delgado - Incaem
Notes
Issue #424 Explicitly allow the LMS to override the masteryScore, LaunchParameters, and moveOn
Issue #378 was originally intended to address this problem, but evolved into an issue about Activity ID management. This issue was created to specifically address to the need to describe how the LMS can change course parameters and how they affect statements. The current proposal is to add language that explicitly allows the LMS to change masteryScore, LaunchParameters, and moveOn course parameters and specify that the AU must write the values in.
The changes would be as follows:
-
Section 10.0 xAPI State Data Model - Change the language for"launchParameters" and "moveOn" to indicate the that the LMS may change them.
-
Section 9.6.3 Extensions - add context entries for "launchParameters" and "moveOn"
Brian Miller will draft a pull request before the next meeting to address these items.
Issue #425 - AU May refuse to issue passed or completed when course structure is changed
This issue was created in response to the discussion about whether or not an AU can "refuse to run" (or refuse to send completed/passed statements) if it receives modified masteryScore (or other course structure parameters) that the content designer deems unacceptable for training certification/qualification reasons.
After much discussion, the group has generally agreed that there needs to be informative language for AU not issuing passed or completed statements due to modifications of the course structure parameters for that AU. The agreed that such language should be added to section 7.1 AU Statement API Requirements
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: