requirements, more flexible data persistence SCORM 2004 specification books Overview – introduces SCORM and describes how the other books relate Run-Time Environment – describes runtime API and data model used for communication between content objects and learning management systems Sequencing and Navigation – describes how sequencing between learning activities is defined and interpreted 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 cmi5 planned to use xAPI as their transport standard, but AICC membership decided to dissolve the organization and transferred cmi5 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. SCORM timeline January 1999 — Executive Order 13111 signed tasking the DoD to develop common specifications and standards for e-learning across both federal and private sectors. January 2000 — SCORM Version 1.0 January 2001 — SCORM Version 1.1 October 2001 — SCORM Version 1.2 January 2004 — SCORM 2004 (1st Edition) July 2004 — SCORM 2004 (2nd Edition) June 2006 — Department of Defense Instruction (DoDI) 1322.26 Requiring DoD Use of SCORM October 2006 — SCORM 2004 (3rd Edition) March 2009 — SCORM 2004 (4th Edition) 2009 — The first three specification books were adopted as technical reports by ISO/IEC JTC1/SC36, standard number ISO/IEC TR 29163. October 2010 — ADL awards a Broad Agency Announcement to Rustici Software to conduct research and community interviews in an effort to begin the creation of the next generation of SCORM. This is called Project Tin Can. September 2011 — The initial draft