-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – March 25th, 2016
cmi5 Working Group Meeting Minutes – March 25th, 2016
Attendees
- Bill McDonald - cmi5 working group leader
- Andy Johnson - ADL
- Art Werkenthin - RISC
- Ben Clark - Rustici Software
- Bernard Bouyt - Airbus
- Mike Kennedy - Workday
Notes
Issue #378 - Explicitly allow the LMS to override the "masteryScore" as defined in the course structure The group reviewed the proposal from last week and added another change to include the following language in section 13.1.4 AU Metadata :
13.1.4 AU Metadata
The data in this section are used by the LMS to locate the AU and provide launch data. AUs may also contain objectives.
Required: Yes Data type: IRI
Description: A globally unique IRI defined by content creator/publisher that the AU uses to identify itself in xAPI statement contexts. This id MUST be unique within the course structure.
Value space: Values are defined by the course designer.
A pull request was generated and applied. This issue is closed.
Issue #394 - Is "Satisfied" recorded for AU's with a "NotApplicable" "moveOn"?
Per the March 11 Meeting the the group determined that the real questions is "what events trigger the LMS to evaluate the MoveOn rules ?" During this meeting the group determined that the primary issue was determine what event(s) should trigger the LMS to evaluate course structure "moveOn" rules. For AU's with the moveOn property set to "not applicable", it was determined that the LMS MUST evaluate the moveOn rules and issue "Satisfied" statements.
The following language was proposed and agreed to:
9.6.1 registration
The value for the registration property used in the context object MUST be the value provided by the LMS. The LMS MUST generate this value and pass it to the AU via the launch URL. At the time of registration, the LMS MUST evaluate MoveOn criteria in the course structure. For example, Blocks with MoveOn criteria of “Not Applicable” in the course structure would be evaluated and could generate Satisfied statements at this time.
A pull request was generated and applied. This issue is closed.
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: