CMI 5 Working Group Meeting Minutes – October 3rd, 2014

Attendees

(If anyone was missed please let me know)

Notes

“cmi.mode” applicability

The group reviewed the applicability of “cmi.mode” in CMI-5 and generally agreed that it would be useful. The following was agreed:

1 - a “mode” element will be added to the State API (written by the LMS to LRS just prior to launch).

2 - the “mode” element will have 2 possible values: “Normal”, “Browse”, and “Review”.

3 - the meaning of “Normal, “Browse, and Review” will be similar to SCORM

“Normal” – the LMS is indicating to content that completion related data must be recorded from the learner session.
“Browse” – the LMS is indicating to content that completion related data must NOT be recorded from the learner session.
The content is expected to provide an experience that allows the user to “look around” without judgment.
“Review” – the LMS is indicating to content that completion related data must NOT be recorded from the learner session.
The content is expected to provide an experience that allows the user to “revisit/review” already completed material.

4 - The compliance requirements for “mode” are as follows:

LMS Obligation - must set the mode value in the State API (written by the LMS to LRS just prior to launch). – Most cases value will be “Normal”
AU Obligation – Normal mode – AU must record Started and Exited Verb Statements (and MAY record any other CMI-5 verbs)
AU Obligation – Review & Browse modes – AU must NOT record any CMI-5 specific verb statements EXCEPT for “Started” and “Exited”.

LaunchMethod

The group reaffirmed that the LMS is required to support both launch methods ("NewWindow", "ExistingWindow") when launching content.

CMI-5 “To-Do” list:

Fetch URL (For Basic Authentication)
Update CourseStructure XSD
Normalize conformance Language to “Must” (from “Shall”). (i.e. Must, Should, May is the conformance vocabulary)
Update Conformance Section (done last)

Provide feedback