There’s a new cowboy in town, and his name is Tin Can API!
Although, that’s what all the innovators and guru’s are trying to convince you of. SCORM and AICC are out, Tin Can API is in! But when the reality kicks in again, it seems more like the new and promising standard for learning technology in the (near) future than something that is currently the standard.
But, as you must keep up with the developments in the world of e-learning software specifications, it is important to know a bit more about this interesting new standard, which will certainly be the norm in the coming years when more and more large companies will adopt it. But not yet.
Who created it?
In 2011 Advanced Distributed Learning (ADL), the United States Department of Defense-sponsored stewards of SCORM, recognized the need for a newer and more capable software specification than the original SCORM specification. To address the need, ADL issued a Broad Agency Announcement (BAA) asking for assistance in improving SCORM, and the BAA was awarded to Rustici Software (be sure to visit their project website)
Rustici Software conducted numerous interviews with the e-learning community to determine where to make improvements and then developed the research version of the Experience API specification. This process was called Project Tin Can and the first release was in april 2013.
What is Experience API/Tin Can API?
The Experience API (also known as the Tin Can API), is an open source API (application programming interface) and is commonly considered the successor to SCORM.
SCORM has been the de facto e-learning standard for packaging e-learning content to be delivered to LMS’s. The new Experience API allows trainers to deploy several new capabilities that were not supported with SCORM, such important ones as:
- Taking e-learning outside of the web browser;
- E-learning in native mobile applications;
- More control over learning content;
- Platform transition; e.g. start e-learning on a mobile device, finish it on a computer;
- The ability to track games and simulations;
- The ability to track real-world performance;
- Tracking learning plans and goals.
How does it work?
When learners undertake learning activities, these actions can be recorded with Tin Can API. When a learning activity needs to be recorded, the application sends secure statements in the form of “Noun, verb, object” or “I did this” to a Learning Record Store (LRS). Learning Record Stores record all of the statements made. An LRS can exist on its own, or inside an LMS.
When learners undertake learning activities, these actions can be recorded with Tin Can API.