804 cmi5: An Example Implementation of the New SCORM
4:00 PM - 5:00 PM Thursday, June 9
With the release of the “granite” version of cmi5, the next generation of SCORM has finally arrived. To take advantage of cmi5, you will need a new tool set in your development kit. First, you need to know how to send xAPI statements that conform to the cmi5 specification. Then you need to know how to read and write to the xAPI State and Agent services following the cmi5 rules.
In this session, you will learn how to develop cmi5-compatible content without waiting for the “rapid development” authoring tools to catch up. You will see an example cmi5 assignable unit, including free source code that you can use as the basis of your projects. You will learn the difference between “cmi5 defined”? statements and “cmi5 allowed” statements, showing examples of when each type of statement should be used. You will also learn which properties in the xAPI State document contain rules that must be followed by your cmi5 content.
In this session, you will learn:
- The difference between “cmi5 allowed” and “cmi5 defined” statements
- How the xAPI State document provides rules your content must follow
- About free source code that you can use in your cmi5 projects
discussed in this session:
Art Werkenthin, president of RISC, built his first learning management system (LMS) in 1988 and now has over 25 years’ experience working with LMS in the oil and gas, retail, finance, and other industries. Art is keenly interested in the xAPI specification, and RISC was an early adopter of this technology. Interested in expanding the xAPI to the LMS, Art has served for the past three years on the ADL cmi5 committee. In 2015, RISC demonstrated the first implementation of a cmi5 runtime engine embedded in its LMS. Art has presented on cmi5 at several conferences, including mLearnCon, DevLearn and xAPI Camp.