Content deleted Content added
Cleanup cite template: extracted original URL from 1 ref archived at web.archive.org |
|||
Line 16:
==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.<ref>{{Cite web |date=2014-08-22 |title=The Next Generation of SCORM: A Q&A; with Aaron Silvers |url=http://www.astd.org/Publications/Newsletters/Learning-Circuits/Learning-Circuits-Archives/2012/06/The-Next-Generation-of-SCORM-a-Q-and-a-with-Aaron-Silvers |access-date=2022-09-15 |website= |archive-url=https://web.archive.org/web/20140822192026/http://www.astd.org/Publications/Newsletters/Learning-Circuits/Learning-Circuits-Archives/2012/06/The-Next-Generation-of-SCORM-a-Q-and-a-with-Aaron-Silvers |
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>
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.<ref name="ADL Project Tin Can Research Summary">{{cite web|title=ADL Project Tin Can Research Summary|url=http://www.adlnet.gov/capabilities/next-generation-scorm/tin-can#tab-research|publisher=Advanced Distributed Learning|accessdate=31 July 2012|archive-url=https://web.archive.org/web/20120723001947/http://www.adlnet.gov/capabilities/next-generation-scorm/tin-can#tab-research|archive-date=23 July 2012|url-status=dead}}</ref> The moniker "Tin Can API" was derived from Project Tin Can, and is still used interchangeably with the name "Experience API".<ref>{{cite web |url=https://www.trainingindustry.com/wiki/entries/experience-api-%28tin-can-api%29.aspx |title=Experience API (Tin Can API) {{!}} Training Industry |website=www.trainingindustry.com |url-status=dead |archive-url=https://web.archive.org/web/20130205163703/http://www.trainingindustry.com/wiki/entries/experience-api-(tin-can-api).aspx |archive-date=2013-02-05}}
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).<ref name="Tin Can API: Current Adopters">{{cite web|title=Tin Can API: Current Adopters|url=http://tincanapi.com/what-is-tin-can/adopters/|work=TinCanAPI.com|publisher=Rustici Software|accessdate=30 July 2012}}</ref>
| |||