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.
For about 10 years, from 2005 – 2015, much of the discussion about tracking eLearning revolved around the Shareable Content Object Reference Model (SCORM) and learning management systems (LMS).
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 :)
I'd searched everywhere for a quick reference guide to the xAPI statements that are passed for each library. Having not been able to locate one, below is a collated list of the xAPI statements for the H5P Libraries that support xAPI.
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.
Continuing on with sharing resources created in a recent course I completed on edX, here is a short video introducing how the Learning Record Store (LRS) plays a part in Experience API (xAPI).
By Marjaana Jokinen on February 20, 2019: This is the story of my learning journey teaching myself how to use xAPI. I share resources and xAPI examples that helped me get started.
Investigating further into H5P, I started playing with the ability to send xAPI statements to our LRS from Moodle. This will give us valuable Learning Analytics when we start using the tool for formative assessments.
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.
Here is a video that demonstrates xAPI (Tin Can API) in action. The video shows the integration between a Wordpress web application with Learning Locker - a Learning Record Store (LRS).
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.