The Experience API (xAPI), often called “Tin Can”, is a new specification for learning that allows collection of data about a wide range of learning experiences for your students. While there are many xAPI solutions, to most people the benefits of xAPI are still somewhat elusive; “it sounds good…but what does it do for me?” In this article, I’ll will show how xAPI was used to solve a real world problem. I will also show how the VTA system was integrated with a PDF Annotator application that runs in multiple environments, including an iPad or other tablet computer and desktop browsers.
With the successful roll-out of the Experience API (xAPI) the foundation for a new SCORM standard has been laid. By itself, xAPI is not a replacement for SCORM. Instead, xAPI defines communication between a learning experience and the learning record store, or LRS. While most of us agree that the majority of learning occurs outside the LMS, there is still some formal eLearning that will be maintained in the LMS, so a more modern SCORM is certainly needed. Now that ADL is taking over the cmi5 specification from the AICC, it is clear that cmi5 is the “next generation” of SCORM. This article provides an introduction to this powerful new specification.
This is part 2 of a 2 part article. In part1, we discussed the history behind xAPI, why xAPI was developed and some of the benefits assocaited with xAPI. In part 2 of this article we will learn how xAPI works, define the Learning Record Store (LRS) and dispel some of the myths about xAPI.