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.
Experience data is an important part of a learning ecosystem, but where it fits and what it connects to can vary widely. Here are a handful of examples.
While there was certainly a big conversation around the strategy of xAPI, there are still many tactical questions that audiences were asking. As a presenter and an attendee, these are the top five tactical questions I heard most from attendees along with some helpful answers and resources.
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.
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).
What should you do when you uncover an issue with your live xAPI data? In this xAPI Governance post, we show you how to clean your data when issues arise.
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.