The Experience API (xAPI) allows us to collect data about any type of learning experience or activity, but does that mean we should? Should we generate massive amounts of xAPI data for every possible type of interaction and then expect to make sense of it all later? This approach can be costly in terms of data storage, but also in terms of your time.
cmi5 is an xAPI Profile that bridges the SCORM and xAPI divide by specifying interoperability rules that inform how an LMS and xAPI activities communicate.
The Institute of Electrical and Electronics Engineers (IEEE) professional standards association is on track to release the Experience Application Programming Interface (xAPI) version 2.0 as an international standard within the next six months.