Content deleted Content added
history |
|||
Line 2:
==Summary==
The Experience API (Tin Can API) is meant to succeed [[SCORM]],<ref>{{cite web | url=https://aristeksystems.com/blog/elearning-standards-2022/#scorm| title=The Experience API (SCORM)| accessdate=2017-04-22}}</ref> the Sharable Content Object Reference Model, which has been the de facto e-learning standard for packaging e-learning content.<ref>{{cite web|last1=Batt|first1=Brian|title=How to Explain AICC, SCORM 1.2, and SCORM 2004 to Anyone|url=http://www.elearningfreak.com/featured/how-to-explain-aicc-scorm-12-and-scorm-2004-to-anyone/|website=eFront Learning|accessdate=21 October 2015}}</ref> There are several drawbacks to SCORM.<ref name="The Training Business (Andy)">{{cite web|last=Whitaker|first=Andy|title=An Introduction to the Tin Can API|url=http://www.thetrainingbusiness.com/softwaretools/tin-can-api/|publisher=The Training Business|accessdate=31 July 2012}}</ref><ref name="Saltbox Developers Discuss Tin Can">{{cite web|title=Saltbox Developers Discuss Tin Can|url=http://floatlearning.com/2012/07/saltbox-developers-discuss-tin-can/|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref> The new Experience API allows trainers to deploy several new capabilities that were not supported with SCORM, such as:
*Taking e-learning outside of the web browser<ref name="SFGate / eLogic Press Release">{{cite web|title=eLogic Learning Partners with Rustici Software to be an Early Adopter of the Next Generation of SCORM Standards Known as the 'Tin Can API'|url=http://www.prweb.com/releases/scorm/e-learning/prweb9610860.htm|publisher=SFGate|accessdate=31 July 2012}}</ref>
Line 17:
==History==
In 2008, it was determined that the interoperability standards were too limited for SCORM. LETSI appears to request community ideas, as 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.<ref name="ASTD interview with Aaron Silvers" /> To address the need, ADL issued a [[Broad Agency Announcement]] (BAA) asking for assistance in improving SCORM, and the BAA was awarded to Rustici Software, a Nashville-based software company experienced with SCORM.<ref name="Float Mobile Tim and Aaron Videos">{{cite web|last=Tillett|first=Jeff|title=Project Tin Can – The Next Generation of SCORM|url=http://floatlearning.com/2012/04/project-tin-can-the-next-generation-of-scorm/|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref>
Line 24 ⟶ 26:
==Current Status==
The current version of the specification is 1.0.3. Released early October 2016.<ref>https://www.adlnet.gov/newest-version-of-xapi-version-1-0-3/</ref><ref>https://github.com/adlnet/xAPI-Spec</ref> There are no plans for any minor updates to the specification. <ref>https://www.adlnet.gov/interviewing-xapi-spec-group-organizer/</ref>
| |||