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 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, IEEE LTSC, and Ariadne.
SCORM was designed to be web-based and utilizes JavaScript to facilitate communication between the client side content and the run-time environment. Each SCORM version specifies the methods that the run-time environment should support and how those methods should behave. Content launched by the run time environment can then call those methods utilizing JavaScript.
Versionsedit
SCORM 1.1edit
It was the first version of SCORM. These early adoptions revealed that the SCORM idea was workable, but it needed to be sufficiently robust for widespread implementation.[2][3]
SCORM 1.2edit
This was the first version that was widely used. It is still widely used and is supported by most Learning Management Systems.
SCORM 2004edit
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 editionsedit
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[4]
SCORM 2004 specification booksedit
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)edit
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.[5] 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.[6]
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.[7]
SCORM timelineedit
January 1999 — Executive Order 13111 signed tasking the DoD to develop common specifications and standards for e-learning across both federal and private sectors.[8]
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 of the next generation of SCORM (named the Tin Can API) is released.
June 2012 — .9 version of the Tin Can API is released.
August 2012 — .95 version of the Tin Can API is released.
April 2013 — 1.0.0 version of the Tin Can API is released, project name was changed to "Experience API" or xAPI, but many still refer to it as the Tin Can API.
^""SCORM Explained 101: An introduction to SCORM"". scorm.com.
^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 2004 4th Edition Version 1.1 Overview". SCORM 2004 4th Edition Version 1.1 Overview. Retrieved 2017-05-22.
^"SCORM – Project Tin Can: Phase 3 – Capabilities". Rustici Software. Retrieved 27 August 2012.
^. Archived from the original on 2007-11-11. Retrieved 2007-10-31. AICC dissolves, transfers cmi5 to ADL
^"Tech Overview - Tin Can API (also known as Experience API or xAPI)". What is xAPI aka the Experience API or Tin Can API. Rustici Software. Retrieved 8 September 2020.
^Lundy, James (10 April 2003). "SCORM Standard Unites E-Learning Software and Content". Gartner Research. Retrieved 26 September 2017.
sharable, content, object, reference, model, this, article, needs, additional, citations, verification, please, help, improve, this, article, adding, citations, reliable, sources, unsourced, material, challenged, removed, find, sources, news, newspapers, books. This article needs additional citations for verification Please help improve this article by adding citations to reliable sources Unsourced material may be challenged and removed Find sources Sharable Content Object Reference Model news newspapers books scholar JSTOR May 2017 Learn how and when to remove this message 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 IEEE LTSC and Ariadne Contents 1 Technology 2 Versions 2 1 SCORM 1 1 2 2 SCORM 1 2 2 3 SCORM 2004 2 3 1 SCORM 2004 editions 2 3 2 SCORM 2004 specification books 2 4 Experience API Tin Can API 3 SCORM timeline 4 Compatible software 5 See also 6 References 7 External linksTechnology editSCORM was designed to be web based and utilizes JavaScript to facilitate communication between the client side content and the run time environment Each SCORM version specifies the methods that the run time environment should support and how those methods should behave Content launched by the run time environment can then call those methods utilizing JavaScript Versions editSCORM 1 1 edit It was the first version of SCORM These early adoptions revealed that the SCORM idea was workable but it needed to be sufficiently robust for widespread implementation 2 3 SCORM 1 2 edit This was the first version that was widely used It is still widely used and is supported by most Learning Management Systems SCORM 2004 edit 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 edit 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 4 SCORM 2004 specification books edit 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 edit 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 5 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 6 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 7 SCORM timeline editJanuary 1999 Executive Order 13111 signed tasking the DoD to develop common specifications and standards for e learning across both federal and private sectors 8 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 of the next generation of SCORM named the Tin Can API is released June 2012 9 version of the Tin Can API is released August 2012 95 version of the Tin Can API is released April 2013 1 0 0 version of the Tin Can API is released project name was changed to Experience API or xAPI but many still refer to it as the Tin Can API Compatible software editServer software Moodle Sakai free community source educational software platform 9 Content editing software Scenari Articulate Storyline Articulate Rise ISpring Suite Adobe CaptivateSee also editAuthoring tool Computer aided instruction Educational technology LETSIReferences edit Technical Specification 4th Ed SCORM Retrieved 2017 05 22 SCORM Explained 101 An introduction to SCORM scorm com 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 2004 4th Edition Version 1 1 Overview SCORM 2004 4th Edition Version 1 1 Overview Retrieved 2017 05 22 SCORM Project Tin Can Phase 3 Capabilities Rustici Software Retrieved 27 August 2012 AICC Aviation Industry CBT Committee Archived from the original on 2007 11 11 Retrieved 2007 10 31 AICC dissolves transfers cmi5 to ADL Tech Overview Tin Can API also known as Experience API or xAPI What is xAPI aka the Experience API or Tin Can API Rustici Software Retrieved 8 September 2020 Lundy James 10 April 2003 SCORM Standard Unites E Learning Software and Content Gartner Research Retrieved 26 September 2017 Sakai integration scorm com External links editOfficial website Retrieved from https en wikipedia org w index php title Sharable Content Object Reference Model amp oldid 1165799513, wikipedia, wiki, book, books, library,
