Experience API: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Removed parameters. | You can use this bot yourself. Report bugs here. | Activated by Neko-chan | Category:Application programming interfaces | via #UCB_Category
WikiCleanerBot (talk | contribs)
m v2.03b - Bot T20 CW#61 - WP:WCW project (Reference before punctuation)
Line 2:
 
==Summary==
The Experience API (Tin Can API) is meant to succeed [[SCORM]], 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>