If you've been moving around the eLearning space lately you've probably seen reference to the Tin Can API, usually within the context mobile. At LearnUpon, we're asked about SCORM and the Tin Can API all the time. Those who are new to eLearning want to understand the difference. All of these can be recorded with the Experience API. We called this process Project Tin Can because it was meant to be a two-way conversation between us .
Tin Can, Experience API, xAPI – three names for the same thing. It's all very confusing and can be frustrating so this page aims to help you understand. The short. The Tin Can API has emerged as the new standard for delivering eLearning. Often described as the next evolution of SCORM, what exactly is. The Experience API (xAPI), is an e-learning software specification that allows learning content The Experience API (Tin Can API) is meant to succeed SCORM, the Sharable Content Object Reference Model, which has been the de facto.
Tin-Can API is the next evolution of the clunky and rigid SCORM specification. Tin-Can records learning in the form of “Action Statements” For example: “John . This white paper provides technical information to help LMS developers implement Tin Can API (xAPI) in their learning management systems to. Project Tin Can started in as a research project awarded to Rustici Software by ADL. The output of Project Tin Can is the Experience API or xAPI. What is SCORM and Tin Can API and how/why should we utilize them in Once the content has found it, it can then communicate through a series of “get” and. All of these can be recorded with the Experience API. We called this process Project Tin Can because it was meant to be a two-way conversation between us .