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.
The Experience API (xAPI for short) is far more than just an update to SCORM, the popular standard for tracking data from a learning management system. xAPI opens up a whole new world of possibilities for learning analytics. Examples of what real organizations are doing with it in real-life situations make it easier to grasp the scale of this advance and apply the learnings to your own situation.
The Experience API or xAPI for short; is a specification document created by a consortium of learning experts led by the Advanced Distributed Learning Initiative (ADL), which is a US Government Programme. Whilst the document was being formed its prototype name was ‘project Tin Can’, but these days it is known by its official name, xAPI.
Dans cet épisode je décrypte les tendances en terme de "Learning Analytics" en abordant notamment la question du standars xAPI et des LRS (Learning Record Store).
The Experience Application Programming Interface (xAPI) is a learning technology specification that enables data encoding, transport, and exchange across a wide variety of activities, experiences, and devices.