The Experience API ( xAPI ) is an e-learning software specification that records and tracks various types of learning experiences for learning systems. Learning experiences are recorded in a Learning Record Store (LRS), which can exist within traditional learning management systems (LMSs) or on their own.
19-662: The Experience API (Tin Can API) is meant to succeed SCORM , the Sharable Content Object Reference Model, which is a standard for packaging e-learning content. The new Experience API allows trainers to deploy several new capabilities that were not supported with SCORM at the time, such as: The Experience API spec is open source . xAPI uses a Restful web service with JavaScript Object Notation (JSON) for its data format. The web service allows software clients to read and write experiential data in
38-500: A result of this SCORM 2.0 comes out. In 2011 Advanced Distributed Learning (ADL), the United States Department of Defense -sponsored stewards of SCORM, recognized the need for a newer and more capable software specification than the original SCORM specification, which was then more than ten years old. To address the need, ADL issued a Broad Agency Announcement (BAA) asking for assistance in improving SCORM, and
57-422: A result of this SCORM 2.0 comes out. In 2011 Advanced Distributed Learning (ADL), the United States Department of Defense -sponsored stewards of SCORM, recognized the need for a newer and more capable software specification than the original SCORM specification, which was then more than ten years old. To address the need, ADL issued a Broad Agency Announcement (BAA) asking for assistance in improving SCORM, and
76-401: Is a standard for packaging e-learning content. The new Experience API allows trainers to deploy several new capabilities that were not supported with SCORM at the time, such as: The Experience API spec is open source . xAPI uses a Restful web service with JavaScript Object Notation (JSON) for its data format. The web service allows software clients to read and write experiential data in
95-402: Is an e-learning software specification that records and tracks various types of learning experiences for learning systems. Learning experiences are recorded in a Learning Record Store (LRS), which can exist within traditional learning management systems (LMSs) or on their own. The Experience API (Tin Can API) is meant to succeed SCORM , the Sharable Content Object Reference Model, which
114-624: 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." 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
133-646: The BAA was awarded to Rustici Software, a Nashville-based software company experienced with SCORM. Rustici Software conducted interviews with the e-learning community to determine where to make improvements, and then developed the research version of the Experience API specification. This process was called Project Tin Can. The moniker "Tin Can API" was derived from Project Tin Can, and is still used interchangeably with
152-427: The BAA was awarded to Rustici Software, a Nashville-based software company experienced with SCORM. Rustici Software conducted interviews with the e-learning community to determine where to make improvements, and then developed the research version of the Experience API specification. This process was called Project Tin Can. The moniker "Tin Can API" was derived from Project Tin Can, and is still used interchangeably with
171-462: The BAA) and version 0.9 (research version specification) 0.95 (second research version specification). SCORM 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
190-530: The SCORM idea was workable, but it needed to be sufficiently robust for widespread implementation. This was the first version that was widely used. It is still widely used and is supported by most Learning Management Systems. 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
209-497: 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. 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
SECTION 10
#1732793409418228-529: 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 . Server software Content editing software Experience API The Experience API ( xAPI )
247-480: 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. In 2008, it was determined that the interoperability standards were too limited for SCORM. LETSI appears to request community ideas, as
266-478: 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. In 2008, it was determined that the interoperability standards were too limited for SCORM. LETSI appears to request community ideas, as
285-481: The name "Experience API". The Experience API was developed by a community working group and released as version 1.0 in April 2013. There are currently over 160 adopters (19 January 2016). The current version of the specification is “ IEEE 9274.1.1-2023 ” – also referred to as xAPI 2.0 - released 10 October 2023 by the IEEE . Previous versions include: 1.0.3, 1.0.2., 1.0.1., 1.0.0. version 0.8 (official output of
304-425: The name "Experience API". The Experience API was developed by a community working group and released as version 1.0 in April 2013. There are currently over 160 adopters (19 January 2016). The current version of the specification is “ IEEE 9274.1.1-2023 ” – also referred to as xAPI 2.0 - released 10 October 2023 by the IEEE . Previous versions include: 1.0.3, 1.0.2., 1.0.1., 1.0.0. version 0.8 (official output of
323-411: 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
342-469: 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
361-433: 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. It was the first version of SCORM. These early adoptions revealed that
#417582