{"id":4531,"date":"2015-05-27T09:59:13","date_gmt":"2015-05-27T14:59:13","guid":{"rendered":"https:\/\/stagingps.paradisosolutions.com\/blog\/?p=4531"},"modified":"2020-07-28T10:32:14","modified_gmt":"2020-07-28T15:32:14","slug":"tin-can-api-evolution-scorm","status":"publish","type":"post","link":"https:\/\/stagingps.paradisosolutions.com\/blog\/tin-can-api-evolution-scorm\/","title":{"rendered":"Tin Can API, the evolution of SCORM"},"content":{"rendered":"

Tin Can API<\/a><\/span>, also known as Experience API or xAPI, is generally considered to be the successor to SCORM<\/a><\/span>, and expands the ability of the organizations that use it to gather data about the experiences, both offline and online, experiences that are quantifiable, trackable and shareable. Tin Can API means there is less reliance on an LMS<\/a><\/span> as these experiences are stored in a Learning Record Store, or LRS. This opens up a wealth of new possibilities for organizations, allowing them to accurately measure employee development and even tie it to performance. But how does this relative newcomer differ from what is already out there?<\/span><\/p>\n

SCORM \u2013 the precursor to Tin Can API<\/strong><\/span><\/h4>\n

The Shareable Content Object Reference Model \u2013 SCORM \u2013 has been the industry standard for over 15 years and has served as the foundation for many an LMS across its lifetime. Originally developed by Advanced Distributed Learning (ADL), an initiative of the Unite States Department of Defense, SCORM was designed to standardize and modernize their training courses. It is a set of standards and specifications for developing web-based educational technology, standards developed by the ADL which had always to adhere strictly to SCROM\u2019s requirements, these being \u201caccessible, reusable, inoperable, and durable content and systems\u201d. SCORM ensures that content and data that is shared across different systems all adhere to the same model. SCORM\u2019s many versions and tweaks over the years gradually gave learning providers more and more control over how and where their content is used, allowing them to better track learner progress and set specific objectives, while also giving learning providers the ability to track the progress of their students. Interoperability was increased, and today almost every LMS and e-learning authoring tool is SCORM compliant, allowing the users of SCORM authoring tools<\/a> <\/span>to write content for LMSs.<\/span><\/p>\n

Advantages of Tin Can API<\/strong><\/span><\/h4>\n

Despite the obvious advantages SCORM gives an organization, its scope is somewhat outdated given how much information can now be gathered about an e-learner, both offline and online. Whereas before the tracking was limited to specific achievements \u2013 course progress, completion\/incompletion, pass\/fail etc. \u2013 with Tin Can API the ability to track becomes much more granular, and data can be collected a number of ways, on desktops or mobile devices and in whatever form the learning activity takes. All of this adds up to give a much clearer and deeper overall picture of a learner\u2019s progress. Tin Can API generates \u201cstatements\u201d in the form of noun-verb-object, and these statements are sent to an LRS (more about this below). This LRS can be integrated with an LMS, allowing Tin Can API to perform everything that a SCORM compliant LMS can do, and much, much more. Have a look at Paradiso Solutions\u2019 Tin Can in a Nutshell<\/a> for a quick overview of its features.<\/span><\/p>\n

Some of the many benefits of Tin Can API are:<\/span><\/p>\n