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 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.
As part of the development and introduction of xAPI into a large organisation, it can always be a challenge to provide the benefits. I'd like to share with you how I used xAPI with Articulate Storyline 360, published as SCORM and being delivered via a Learning Management System (LMS). The Learning Record Store (LRS) is Learning Locker.
I went to build my own infograph to make it easier to explain, but why reinvent the wheel! Here are a couple of infographs that explaining the xAPI a little easier to understand :)