CMI 5 Working Group Meeting Minutes – November 4th, 2016

cmi5 Working Group Meeting Minutes – November 4th, 2016

Attendees

• Bill McDonald - cmi5 working group leader
• Benard Bouyt - Airbus
• Andy Johnson - ADL
• Ben Clark - Rustici Software
• Henry Ryng - inXsol
• Dennis Hall - Learning Templates
• Art Werkenthin - RISC
• Bret Wienraub - Aura Software LLC
• Tom King - Blue Water

Notes

Best Practices

The group reviewed changes to the Wiki and the (issues) backlog of best practices. The following best practices were refined during the meeting (as shown below) and will be added to the "Best Practices" website page.

Common Mistakes

The group also discussed the creation of a "Common Mistakes" page based on common cmi5 implementation mistakes observed by the cmi5 working group.

PENS

Tom King, the original author of the PENS (Package Exchange Notification Services) specification is starting an new effort to update PENS to include cmi5 packages (and other needed improvements). The group is just starting and will begin scoping efforts soon. Please see the gitHub repo link below for updates and information on how to participate:

• https://github.com/ADL-AICC/PENS

---

Best Practices

---

Best Practice #3 - Always specify a moveOn criterion in the course structure for each AU

When creating a course structure, always specify a moveOn criteria for each AU. Failing to do so will result in a default of “Not Applicable”. This can have the following unintended consequences:

• If you either fail to specify moveOn criteria or specify “NotApplicable” as the move criteria for all AU’s in a course, the course will automatically being marked complete immediately upon registration of the learner (before the learner attempts a single AU).
• If at least on AU has a moveOn criteria specified (other than “NotApplicable”) then course would be completed upon completion of those AU’s
• It is considered to be a better practice to explicitly specify the moveOn for each AU in course to ensure there is no confusion over the completion requirements of a course.

Best Practice #4 - AU Best Practice for Mastery score

If the LMS issues a Mastery Score, the AU should respond in the following ways:

• If the AU has no notion of scoring, it should not issue Passed or Failed statements.
• If the AU does not have scoring or the learner does not meet the masteryScore then the AU must not issue a Passed Statement (per the defined specification).
• The AU can also refuse to execute because the mastery score issues is inconsistent with the learning design of the AU. In this situation, the AU should inform the learner why it cannot execute.

Best Practice #5 - LMS Best Practice for Mastery score

LMS should use caution when adding mastery scores to AU course structure entries if they are not present in the original course structure. (As the AU may not be designed to issue scores). It is recommended that such changes be tested prior to enrolling learners.

---

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