Content deleted Content added
JeffreHorne (talk | contribs) No edit summary |
JeffreHorne (talk | contribs) No edit summary |
||
Line 2:
The Tin Can [[API]] is an e-learning software specification that allows learning content and learning systems to speak to each other in a manner that records and tracks all types of learning experiences.<ref name="Learning Solutions Magazine">{{cite web|last=Brandon|first=Bill|title=Making History: mLearnCon 2012 Rocks Attendees|url=http://www.learningsolutionsmag.com/articles/958/|work=Making History: mLearnCon 2012 Rocks Attendees|publisher=Learning Solutions Magazine|accessdate=31 July 2012}}</ref> Learning experiences are recorded in a Learning Record Store (LRS). LRSs can exist within traditional [[Learning Management Systems]] (LMSs) or on their own.<ref name="ASTD interview with Aaron Silvers">{{cite web|last=Brusino|first=Justin|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|work=THE NEXT GENERATION OF SCORM: A Q&A WITH AARON SILVERS|publisher=American Society for Training and Development|accessdate=31 July 2012}}</ref>
The Tin Can API is commonly referred to as "The Experience API" and "Next Generation [[SCORM]]." SCORM (Sharable Content Object Reference Model) has been the de facto e-learning standard for packaging e-learning content to be delivered to LMSs. However, 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/|work=An Introduction to the 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/|work=Saltbox Developers Discuss Tin Can|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref>
*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.sfgate.com/business/prweb/article/eLogic-Learning-Partners-with-Rustici-Software-to-3662367.php|work=eLogic Learning Partners with Rustici Software to be an Early Adopter of the Next Generation of SCORM Standards Known as the 'Tin Can API'|publisher=SFGate|accessdate=31 July 2012}}</ref>
*E-learning in native mobile applications<ref name="Learning Solutions Magazine" />
*More control over learning content<ref name="Saltbox Developers Discuss Tin Can" />
*Solid security using [[Oauth]]
*Platform transition (start e-learning on a mobile device, finish it on a computer)<ref name="SFGate / eLogic Press Release" />
*The ability to track games and simulations<ref name="ASTD interview with Aaron Silvers" />
*The ability to track real-world performance<ref name="Upside Learning">{{cite web|last=Gautam|first=Amit|title=Tin Can: My First Impressions From mLearnCon 2012|url=http://www.upsidelearning.com/blog/index.php/2012/06/21/tin-can-my-first-impressions-from-mlearncon-2012/|work=Tin Can: My First Impressions From mLearnCon 2012|publisher=Upside Learning|accessdate=31 July 2012}}</ref>
*Team-based e-learning<ref name="ASTD interview with Aaron Silvers" />
The Tin Can API is an [[open source]] API. It is a [[Representational state transfer]] web service that uses [[JavaScript Object Notation]] for its data format. The web service 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”.<ref name="Saltbox Developers Discuss Tin Can" /> 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.
===History===
SCORM is over ten years old, and [[Advanced Distributed Learning]] (ADL), the stewards of SCORM, recognized the need for a newer and more capable software specification.<ref name="ASTD interview with Aaron Silvers" />
ADL issued a [[Broad Agency Announcement]] (BAA) asking for assistance in improving SCORM. The BAA was awarded to [http://scorm.com Rustici Software], a leader in the industry of e-learning interoperability software.<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/|work=Project Tin Can – The Next Generation of SCORM|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref> Rustici Software then conducted numerous interviews with the e-learning community to determine which factors were most important to improve upon, and developed the research version of the Tin Can API specification. This process was called [http://scorm.com/tincanoverview/ 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|work=ADL Project Tin Can Research Summary|publisher=Advanced Distributed Learning|accessdate=31 July 2012}}</ref>
The Tin Can API is still in development, but it is mature enough to be adopted by the e-learning industry. There are currently over 25 adopters.<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>
| |||