To be used and compatible with Learning Management Systems (LMS), ELearning modules must be published in a format that allows for progress tracking and use in those LMS platforms.
A common format modules are published in is the SCORM format, allowing for progress to be saved, and for interactions, attempts and scores to be tracked to a Learning Management System such as Spark.
Other packaging methods similar to SCORM include AICC and TinCan (xAPI) also known as the Experience API.
The Spark Platform is best compatible with TinCan, allowing you to get very granular detail in module output and tracking. Spark is compatible with SCORM 1.2 only.
TinCan (xAPI/Experience API)
TinCan is an evolution of the SCORM format, adding new capabilities and options for how we can understand what our users do and experience when accessing module content. At its simplest, it utilises the structure of a sentence to describe what someone has done, and this is recorded for each action. This includes details like accessing a page, completing an interaction, answering a question (and the answer given) and completing the module.
"I did this."
TinCan provides very granular detail and can create large volumes of recorded data, giving you the most in depth overview of what your users are doing in the training content.
The name SCORM itself stands for Sharable Content Object Reference Model. It means that SCORM is all about creating compatible elearning material that can be distributed and accessed across different Learning Management Systems. Thanks to this, SCORM packaged elearning can be transferred from a different LMS into Spark without having to re-publish the files in a different format.
Please note that Spark is only compatible with SCORM 1.2 Modules.
SCORM is a long established format, and possibly the most commonly accepted form of content delivery standard for elearning today.
There are two versions of SCORM that you can publish your module in. SCORM 1.2, or SCORM 2004. Some LMS systems support both versions of SCORM.