CMI 5 Working Group Meeting Minutes – April 14th

cmi5 Working Group Meeting Minutes – April 14th, 2017

Attendees

• Bill McDonald - cmi5 working group leader
• Andy Johnson - ADL
• Ben Clark - Rustici Software
• Art Werkenthin - RISC, Inc.
• Dennis Hall - Learning Templates
• Clayton Miller - NexPort Engineering
• Henry Ryng - InXSOL
• Christopher Thompson – Medcom Inc.

Notes

cmi5 adoption/promotion

Another LMS vendor put out a press release this week for cmi5. Dennis Hall will reach out to them for inclusion in the cmi5 adoption list.

GitHub Issues with Headings

GitHub markdown is not properly displaying headings in the cmi5 spec. Andy Johnson will research this issue.

SCORM vs. cmi5 Comparison Document

The group updated the Content Launch entry for the detailed comparison table as follows:

Feature	SCORM	cmi5	Comments
Content Launch	Yes	Yes	SCORM uses a JavaScript parent/opener with JavaScript communication object/API provided by the LMS. cmi5 uses a launch URL with parameters for Web services communication. This launch mechanism does not necessarily require a browser and content can reside on different domains/platforms. Content can be launched in a mobile app with cmi5.

The group created the following section to describe Content Launch in more detail (re purposing previous table entry):

Content Launch

SCORM uses a JavaScript parent/opener with a JavaScript communication object/API provided by the LMS. The content must discover the object/API via recursively searching the browser window tree. cmi5 uses a launch URL with parameters for Web services communication. The content uses query string parameters to discover the xAPI endpoint for recording data. This method of discovery is more reliable as the query string is always available to the content.

See new draft sections here

Discussion for next week

• Expanded Definitions of SCORM vs cmi5

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/