CMI 5 Working Group Meeting Minutes – December 23rd, 2016

cmi5 Working Group Meeting Minutes – December 23rd, 2016

Attendees

• Bill McDonald - cmi5 working group leader
• Andy Johnson - ADL
• Dennis Hall - Learning Templates
• Brian Miller - Rustici Software
• Freddie O'Connell - Rustici Software
• Christopher Thompson -

Notes

Best Practices

The group agreed to revisit the discussion on Course Structure/Course Package best practices

SCORM vs. cmi5

The group continued it discussion of "Why cmi5?" topics and started a detailed comparison table for SCORM vs. cmi5.

The following is an initial draft discussed during the meeting:

Feature	SCORM	cmi5	Comments (SCORM)	Comments (cmi5)	cmi5 Team Rationale
Content package	YES	YES	Zip file with XML manifest	Zip file with XML course structure XML file with or without zip	Zip is required if content being transferred
Objectives	YES	YES	Objectives Metadata that can be used for sequencing logic.	Objectives Metadata. Does not affect course behavior	The cmi5 team avoided using objectives data to affect course behavior due to complexity of logic involved and lack of consensus.
Remediation	YES	NO	Remediation can implemented by “simple sequencing” logic rules.	None.	The cmi5 team avoided this feature as it was problematic as it was overly complex to define practical norms for its use. Remediation can be accomplished in the AU (i.e. SCO)
Prerequisites	Yes	No	Prerequisites can implemented by “simple sequencing” logic rules.	cmi5 has the notion of “MoveOn” criteria for completion of individual AU or groups of AU	We avoided sequencing rules due to complexity. It was determined that prerequisites features were better left to (LMS) implementation specific feature sets. (The cmi5 team has found based on experience, that even though it is possible with SCORM, most prerequisites implementations become “custom” and interoperability was not achieved)
Content Launch	Yes	Yes	JavaScript parent/opener with JavaScript communication object/API. The LMS determines how the content is redirected/launched to (pop up window, iframe, redirect)	Launch URL with parameters for Web services communication. The course structure settings determine windowing (“own window” or “any window”)	The cmi5 team determined that a setting was need to promote interoperability at launch time for browser windows. Content interoperability with SCORM (and AICC) have been problematic to ambiguity over with Browse launch/redirect behavior by the LMS. The cmi5 approach allows a predictable means for “same window launch” (which is important for mobile device support).
Communication Interface	Yes	Yes	JavaScript communication object/API.	Restful Web Service (xAPI)	The cmi5 team chose xAPI because it is platform and browser independent. It also makes content hosting (on hosts other than the LMS much easier)

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