CMI 5 Working Group Meeting Minutes – June 19th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – June 19th
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Florian Tolk (ADL)
- Mike Hernandez (ADL)
- Dennis Hall (Learning Templates)
- Henry Ryng (INXSOL)
- Art Werkenthin (Risc, inc)
- Scott Powers (Meridian Knowledge Solutions)
- Alan Mustafa (The American University of Kurdistan)
Notes
cmi5 Spec Issue - AU requirements for moveOn
The group discussed comments made on Issue #605 (Make AU support of moveOn criteria at runtime mandatory) and determined that the spec proposal should instead focus adding a new AU metadata element to the course structure. The new element would be called moveOnAllowed and it would define a list of moveOn criteria that the AU is capable of handling. The LMS could use moveOnAllowed to prevent LMS admin users from changing moveOn criteria in a manner that could prevent course/block satisfaction rules from ever being met.
The group also agreed to rewrite Best Practice #17 – The AU should always issue statements based on moveOn provided by the LMS to reflect this.
Andy Johnson proposed new verbiage for Best Practice #17 is as follows:
Best Practice #17 –The AU should be designed with flexibility to meet a variety of moveOn criteria.
The LMS administrator may change the value of moveOn after acquisition of the course and before or after the course structure import. This is the moveOn value the LMS passes to the AU in the state document. However, the AU should be designed to always send cmi5 defined completed, cmi5 defined passed, and cmi5 defined failed whenever appropriate to the content. For example, completion criteria may include viewing of all content. The AU should anticipate that alternate values for the moveOn criteria other than those for which it was designed could occur (e.g. an AU should design to allow a moveOn criteria of “CompletedAndPassed” even if the environment it was designed only has a moveOn criteria of “Passed”). If an AU is unable to act on the moveOn criteria provided, it should already know this from the course structure metadata “moveOn Allowed”, which specifies the possible modalities of the AU. If it does launch and cannot act on the moveOn criteria provided, it should gracefully exit and notify the learner that it cannot proceed. Issuing “passed” or “failed” Statements without specific assessment may be done at the discretion of the developer, but is not an overall best practice.
The new verbiage for Best Practice #17 and the new proposal for issue #605 will be discussed at the next meeting.
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: