Sharable Content Object Reference Model

Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for web-based electronic educational technology (also called e-learning). It defines communications between client side content and a host system (called "the run-time environment"), which is commonly supported by a learning management system. SCORM also defines how content may be packaged into a transferable ZIP file called "Package Interchange Format."[1]

SCORM is a specification of the Advanced Distributed Learning (ADL) Initiative from the Office of the United States Secretary of Defense.

SCORM 2004 introduced a complex idea called sequencing, which is a set of rules that specifies the order in which a learner may experience content objects. In simple terms, they constrain a learner to a fixed set of paths through the training material, permit the learner to "bookmark" their progress when taking breaks, and assure the acceptability of test scores achieved by the learner. The standard uses XML, and it is based on the results of work done by AICC, IMS Global, IEEE, and Ariadne.

Versions

SCORM 1.1

SCORM 1.1 is the first production version. It used a Course Structure Format XML file based on the AICC specifications to describe content structure, but lacked a robust packaging manifest and support for metadata. Quickly abandoned in favor of SCORM 1.2.

SCORM 1.2

This was the first version that was widely used. It is still widely used and is supported by most Learning Management Systems.

SCORM 2004

This is the current version. It is based on new standards for API and content object-to-runtime environment communication, with many ambiguities of previous versions resolved. Includes ability to specify adaptive sequencing of activities that use the content objects. Includes ability to share and use information about the success status for multiple learning objectives or competencies across content objects and across courses for the same learner within the same learning management system. A more robust test suite helps ensure good interoperability.

SCORM 2004 editions

SCORM 2004 specification books

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.[3] 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.[4]

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]

SCORM timeline

See also

References

  1. ↑ "Technical". SCORM. Retrieved 2014-12-22.
  2. ↑ "SCORM 2004 4th Edition Version 1.1 Overview". SCORM 2004 4th Edition Version 1.1 Overview. Retrieved 3 November 2016.
  3. ↑ "SCORM – Project Tin Can: Phase 3 – Capabilities". SCORM – Project Tin Can: Phase 3 – Capabilities. Rustici Sofftware. Retrieved 27 August 2012.
  4. ↑ AICC dissolves, transfers cmi5 to ADL
  5. ↑ "Tech Overview - Tin Can API". Tech Overview - Tin Can API. Rustici Software. Retrieved 27 August 2012.
This article is issued from Wikipedia - version of the 11/4/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.