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.
The Experience API (xAPI), often called “Tin Can”, was released on April 26th, 2013. There are already over 70 adopters of xAPI and the level of industry “buzz” has been unprecedented. So what is it? Is it something you should know about? In this session we will introduce you to xAPI and show how it is impacting the learning industry. We’ll also show you the benefits of xAPI and how it can help record a wide range of learning experiences for your students. This is part 1 of a 2 part article.