CMI 5 Working Group Meeting Minutes – October 4th

cmi5 Working Group Meeting Minutes – October 4th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Mark Grant (Independent)
• David Pesce (Exputo)
• Henry Ryng (inXsol)
• Dennis Hall (Learning Templates)
• Art Werkenthin (RISC, inc)

Notes

The group continued to edit the cmi5 vs "TinCan Package" document.

The group added the following to detailed section as follows:

Mastery Score The cmi5 course structure can include a mastery score for each AU. Depending on the LMS feature set, the mastery score can be overridden/modified by the LMS administrator after the course structure is imported. The TinCan package does not have definition for mastery score. The ability to set Mastery Score allows the LMS to determine passing or failure of judged activity in the AU (if the AU has scoring).

Completion Criteria cmi5 includes a “move on” criteria that defines specific verb patterns that must be received in order to receive credit for a lesson. For example, the course structure could define that a given AU requirement is satisfied if a Completed or Passed verb is sent by the AU. It is also possible to define an AU as being “optional” to the completion of a course. The TinCan package has no defined completion criteria.

Is an ADL Initiative or standards organization specification. The cmi5 specification was jointly developed by the ADL Initiative, the AICC, and other industry experts. The spec was developed through a series of open meetings and reviews over a period of several years. The cmi5 specification is a xAPI profile that is fully integrated with launch and packaging rules for LMS delivery of content. The TinCan package is an informal proposal document that was created at the initial release of the xAPI specification. It has not had formal reviews and extensive community/industry input.

Defined use of the xAPI “Result.Score” property. The cmi5 specification is a xAPI profile that defines usage of Result.Score for specific verbs including scaled, raw, min, and max values. Result.Score important for judging mastery or comprehension. The TinCan package has no rules defined for Result.Score usage.

Defined use of the xAPI “Result.Success” property. The cmi5 specification is a xAPI profile that defines usage of Result.Success for specific verbs. Result.Success important for judging mastery or comprehension. The TinCan package has no rules defined for Result.Success usage.

Defined use of xAPI “Result.Duration” property. The cmi5 specification is a xAPI profile that defines usage of Result.Duration property for specific verbs and guidance for time calculation. Result.Duration is important for calculating time spent in learning activities. The TinCan package has no rules defined for Result.Duration usage.

Defined use of the xAPI “Result.Completion” property. The cmi5 specification is a xAPI profile that defines usage of Result.Completion for specific verbs. Result.Completion is important for determining if the learner has viewed all relevant materials in an AU. The TinCan package has no rules defined for Result.Completion usage.

Ability to “waive” lessons. The cmi5 specification defines a standard verb that indicates that an AU has been satisfied by alternative means such as manual override (e.g. instructor discretion). This is very a useful feature for defining “testing out” scenarios in the LMS to skip AU’s in a course. It can also be used if the instructor has other reasons to believe (such as documentation) that the learner has already mastered the content. The TinCan package has definition of “waive” features.

---

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/