To understand how cmi5 and xAPI are related it is important first to understand what an xAPI Profile is. Because of the modularity and flexibility that xAPI was designed specifically to make possible, it became necessary for users of xAPI to create shared, referenceable ways to define how they were applying xAPI. For example, let’s say that one group in an organization builds robots and another group builds software. These are two very differently defined versions of “build,” and it is very important for us to understand which one we are referring to when we look at our data. This is where an xAPI Profile comes in — it allows us to define the set of rules or the lens through which we need to be able to look at and interpret our xAPI data. It provides a way to make sure that the xAPI data we create reflects the learner activity we intend to capture in a unified, specified way and that throughout the industry, within an organization, or for a specific task, shared practices in xAPI data design are followed. xAPI Profiles are shared, publicly referenceable, openly usable set of rules for applying xAPI in a given situation. As an xAPI Profile, cmi5 serves as the definition of interoperable communication between an LMS and a Learning Record Store, making it possible to collect LMS based learning activity in xAPI format. Cmi5 was created in collaboration between the AICC (Aviation Industry Computer-Based Training Committee) and ADL and can be used as a transitional step on the way from SCORM to xAPI. Cmi5 enables data portability and interoperability with other xAPI systems because data created using cmi5 is in xAPI format.
- Learn more about xAPI Profiles directly from ADL in the xAPI Profiles GitHub documentation.
- Learn more about the features and benefits of cmi5 in comparison to SCORM.
- Learn more about the transition from SCORM to cmi5 to xAPI in this article on “What is cmi5 and how does it relate to SCORM and AICC?”