Standards of distance education scorm. TinCan

SCORM 2004 editions

• 
  3rd Edition (October 2005) – clarification of various conformance requirements and of the interaction between content objects and the runtime environment for sequencing; some new conformance requirements to improve interoperability.
  
• 
  4th Edition Released (March 31, 2009) – more stringent interoperability requirements, more flexible data persistence.^[2]
  

SCORM 2004 specification books

• 
  1. Overview – introduces SCORM and describes how the other books relate
  
• 
  2. Run-Time Environment – describes runtime API and data model used for communication between content objects and learning management systems
  
• 
  3. Sequencing and Navigation – describes how sequencing between learning activities is defined and interpreted
  
• 
  4. Compliance Requirements – detailed list of the conformance requirements that are verified by the ADL SCORM conformance test suite.
  

Experience API (Tin Can API)

The Experience API (also known as xAPI or Tin Can API) was finalized to version 1.0 in April 2013. The Experience API solves many of the problems inherent with older versions of SCORM. Just like SCORM, ADL is the steward of the Experience API. AICC with their CMI-5 planned to use xAPI as their transport standard, but AICC membership decided to dissolve the organization and transferred CMI-5 to ADL.
The Experience API (Tin Can API) is a web service that allows software clients to read and write experiential data in the form of “statement” objects. In their simplest form, statements are in the form of “I did this”, or more generally “actor verb object”. More complex statement forms can be used. There is also a built-in query API to help filter recorded statements, and a state API that allows for a sort of “scratch space” for consuming applications. Experience API statements are stored in a data store called a Learning Record Store, which can exist on its own or within a Learning Management System.^[5]