CMI 5 Working Group Meeting Minutes – December 2nd, 2016

cmi5 Working Group Meeting Minutes – December 2nd, 2016

Attendees

• Bill McDonald - cmi5 working group leader
• Bernard Bouyt - Airbus
• Dennis Hall - Learning Templates
• Art Werkenthin - RISC
• Ray Lowery - Pratt & Whitney
• David Pesce - Exputo
• Christopher Thompson - Medcom Inc
• Henry Ryng - InXSOL
• Giovanni Sorrentino - E-CO e-Learning Studio

Notes

The group discusses cmi5 adoption, best practices, and cmi5 promotion with "Why cmi5?" topics.

---

cmi5 Promotion/Adoption

The group continue to discuss the status of early cmi5 adoption with content authoring tools.

---

Best Practices

The group added a new best practice for the absence of returnURL.

Best Practice #8 – In the absence of returnURL, the AU should close browser window to exit.

If the content is not provided a “returnURL” – the best practice to exit an AU is to close the Window (window.close() or direct the learner to manually close the browser window).

---

Common cmi5 mistakes

• Mistake #1 - Disregarding the returnURL

  • Mistake: The content (AU) does not redirect the browser to the returnURL when exiting
  • Consequence: Since the best practice for LMS systems is to use the returnURL, the consequence of this mistake is rather significant, as the learner cannot return to the LMS user interface after exit. This is also a violation of the minimum conformance requirements of cmi5 and the AU is not conformant.

• Mistake #2 - Using the Activity ID as Publisher ID

  • Mistake: The content (AU) does not use the publisher ID provided in the State API in context activities of the statements it makes, incorrectly using the LMS generated Activity ID instead.
  • Consequence: The consequence of this mistake is that the data in statements are incorrectly documented. This is also a violation of the minimum conformance requirements of cmi5 and the AU is not conformant.

• Mistake #3 - Disregarding the masteryScore

  • Mistake: The content (AU) does not issue the proper statements (Passed) when the score is above the masteryScore (as provided in the State API by the LMS). Instead it uses its own internally specified score threshold to determine mastery.
  • Consequence: The consequence of this mistake is that the content is incorrectly issuing passed or failed statements. The AU is ignoring the masteryScore as provided by the LMS administrator (or course structure as it currently exists). This is also a violation of the minimum conformance requirements of cmi5 and the AU is not conformant.

• Mistake #4 - Automatic Satisfaction (Course Completion) immediately on Course Registration

  • Mistake: A course structure has not included moveOn Criteria for ANY of its AU’s.
  • Consequence: The consequence of this mistake is that the course is immediately satisfied on registration (without the learner launching ANY AUs in the course). While this does technically conform to requirements of cmi5, it is likely NOT the intent of the course designer.

• Mistake #5 - Not respecting Browse and Review Launch Modes

  • Mistake: Launch mode values (of Browse and Review) provided by the LMS in the State Document are ignored by the AU.
  • Consequence: The consequence of this mistake is that the AU incorrectly issues cmi5 statements other than initialized and terminated. This is a violation of the minimum conformance requirements of cmi5 and the AU is not conformant.

---

"Why cmi5? Topics" for cmi5 github.io website

The group discussed topics for the "Why cmi5" page on the cmi5 github.io website. These topics will serve to explain the benefits of cmi5. The group can up with the following topics at this meeting and will continue to refine them.

Why CMI5 ?

• Content As Service Scenario – You can host on external Hosts (different than LMS)
• Record what you want. (Multiple learning scenarios )
• cmi5 Session Envelope (grouped statements for launch session)
• Better Windowing on launch (Mobile)
• More Secure (fetchURL authentication)

---

All Previous cmi5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

cmi5 on GitHub:

https://github.com/AICC/CMI-5_Spec_Current