CMI 5 Working Group Meeting Minutes – June 12th

cmi5 Working Group Meeting Minutes – June 12th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Dennis Hall (Learning Templates)
• David Pesce (Exputo)
• Henry Ryng (INXSOL)
• Art Werkenthin (Risc, inc)

Notes

cmi5 Narrative AU flow

The group continued to map out the flowchart for AU portion of the cmi5 narrative.

cmi5 Spec Issue - AU requirements for moveOn

While examining the AU process flow. It was determined that the AU conformance language for moveOn caused a conflict that would require a spec change. To address this issue the group agreed to the following:

1. Create a Spec Issue to address the problem in the next release of cmi5.

2. Add a new best practice to mitigate the problem in the meantime.

Proposed Update for cmi5 Section 10 - moveOn - AU Usage:

The AU MUST always respect this value and send appropriate statements (e.g. AU must send a completed statement and a passed statement if moveOn is set to “CompletedAndPassed”) If the AU is unable to act on the moveOn value provided, it MUST gracefully exit and notify the learner that it cannot proceed.

(See Issue #605 - Make AU support of moveOn criteria at runtime mandatory)

New best practice for moveOn:

Best Practice #17 - The AU should always issue statements based on moveOn provided by the LMS

The LMS administrator may change the value of moveOn after course structure import. This is the moveOn value that the LMS passes to the AU in the state document. The AU should always respect this value and send appropriate statements (e.g. AU must send a completed statement and a passed statement if moveOn is set to “CompletedAndPassed”) If the AU is unable to act on the moveOn value provided, it should gracefully exit and notify the learner that it cannot proceed.

---

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/