CMI 5 Working Group Meeting Minutes – November 2nd

cmi5 Working Group Meeting Minutes November 2nd

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Art Werkenthin (RISC, Inc)
• Dennis Hall (Learning Templates)
• Henry Ryng (InXSOL)
• Charles Touron (USARMY CAC
• Clayton Miller (Nextport)

Notes

---

cmi5 AU design Narrative

The group continued to develop the outline for the cmi5 AU design narrative. We discussed which topics would be actually demonstrated in code/exercises and which topics would only be mentioned/discussed.

Demonstrated Topics

1. cmi5's benefits
   • Extensible data model
   • Sharing data between AU’s
2. How to connect to an LRS with a cmi5 launch
   • Fetch/authentication
   • LRS Connect String
3. How to create well-formed cmi5 statements
   • Context
4. Understand the core and optional features
   • Core
     • Session Concept
     • Initialize/Terminate
   • Optional
     • Understand the difference between cmi5 allowed and cmi5 defined
     • Why cmi5 allowed statements are useful
5. Know the best practices
   • Best Practice #2 – LMS should always implement the “returnURL” (HAVE AU Implement)
   • Best Practice #4 – AU Mastery Score
   • Best Practice #6 – Always specify a moveOn criterion in the course structure for each AU
   • Best Practice #8 – In the absence of returnURL, the AU should close browser window to exit.
   • Best Practice #11 – Use “progressed” verb for indicating progress during a session.
   • Best Practice #12 – Provide registration id in all statements.

Discussed Topics

1. cmi5's benefits
   • LMS can connect to other systems (xAPI) - Data Portability
   • Eliminate Pop ups
   • Distributed Content
   • Not Browser Dependent (client agnostic)
2. Know the best practices
   • Best Practice #1 – Use of Objectives (LMS)
   • Best Practice #3 – Fetch URLs (LMS)
   • Best Practice #5 – LMS Mastery Score
   • Best Practice #9 - LMS error handling of non-conforming cmi5 statements.
   • Best Practice #10 - LMS Administrators should use caution when changing the moveOn property.
   • Best Practice #13 – LMS create “satisfied” statements for AU’s.

---

Best Practice #11 – Use “progressed” verb for indicating progress...

The group reviewed this best practice and agreed that more clarification/guidance should given as to when the progressed verb should be used. The group agreed that progress statements should be issued when a "logical increment" of AU has been completed and that the "increments" based on content design – where the content designer chooses the level of granularity. And example of a logical increment could be 10% or completing one of several topics covered in the AU.

---

cmi5 Objectives

The group discussed the best practice for tracking learning objectives using cmi5. While cmi5 does have learning objectives in the course structure, the specification is silent on how to track completion and/or mastery of learning objectives in the LRS.

The group agreed that the LMS should communicate objectives to AU using State Document (context template) and that this should be considered a best practice and a potential new feature in the next cmi5 spec release.

see issue https://github.com/AICC/CMI-5_Spec_Current/issues/589

---

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/