Experience API

The Experience API (xAPI) 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.[1] Learning experiences are recorded in a Learning Record Store (LRS). LRSs can exist within traditional learning management systems (LMSs) or on their own.[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[3]. There are several drawbacks to SCORM.[4][5] 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[6]
  • E-learning in native mobile applications[1]
  • More control over learning content[5]
  • Solid security using OAuth
  • Platform transition; e.g. start e-learning on a mobile device, finish it on a computer[6]
  • The ability to track games and simulations[2]
  • The ability to track real-world performance[7]
  • Team-based e-learning[2]
  • Tracking learning plans and goals[8]

The Experience API (Tin Can API) is an open source API. It is a Representational state transfer web service that uses JavaScript Object Notation (JSON) 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”.[5] 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

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.[2] 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.[9]

Rustici Software conducted numerous 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.[10] The moniker "Tin Can API" was derived from Project Tin Can, and is still used interchangeably with the name "Experience API".[11]

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).[12]

Current Status

The current version of the specification is 1.0.3. Released early October 2016.[13][14] There are no plans for any minor updates to the specification. [15]

Previous versions include: 1.0.2., 1.0.1.,[16] 1.0.0.[17] version 0.8 (official output of the BAA)[18] and version 0.9 (research version specification) 0.95 (second research version specification).

gollark: APipoios have probably always been kind of rare; people don't want to AP shiny new releases they can trade away.
gollark: I dream of my code working correctly right after I write it...
gollark: Hahahahanope.
gollark: Maybe raffles generally do.
gollark: *has an IOU for 30 reds now but won't get them for a while*

References
  1. Brandon, Bill. "Making History: mLearnCon 2012 Rocks Attendees". Learning Solutions Magazine. Archived from the original on 6 August 2012. Retrieved 31 July 2012.
  2. Brusino, Justin. "THE NEXT GENERATION OF SCORM: A Q&A WITH AARON SILVERS". American Society for Training and Development. Archived from the original on 22 August 2014. Retrieved 31 July 2012.
  3. Batt, Brian. "How to Explain AICC, SCORM 1.2, and SCORM 2004 to Anyone". eFront Learning. Retrieved 21 October 2015.
  4. Whitaker, Andy. "An Introduction to the Tin Can API". The Training Business. Retrieved 31 July 2012.
  5. "Saltbox Developers Discuss Tin Can". Float Mobile Learning. Retrieved 31 July 2012.
  6. "eLogic Learning Partners with Rustici Software to be an Early Adopter of the Next Generation of SCORM Standards Known as the 'Tin Can API'". SFGate. Retrieved 31 July 2012.
  7. Gautam, Amit. "Tin Can: My First Impressions From mLearnCon 2012". Upside Learning. Archived from the original on 27 August 2012. Retrieved 31 July 2012.
  8. Downes, Andrew. "I Want This: Tin Can Plans, Goals and Targets". Archived from the original on 24 July 2013. Retrieved 28 April 2013.
  9. Tillett, Jeff. "Project Tin Can – The Next Generation of SCORM". Float Mobile Learning. Retrieved 31 July 2012.
  10. "ADL Project Tin Can Research Summary". Advanced Distributed Learning. Archived from the original on 23 July 2012. Retrieved 31 July 2012.
  11. https://www.trainingindustry.com/wiki/entries/experience-api-%28tin-can-api%29.aspx
  12. "Tin Can API: Current Adopters". TinCanAPI.com. Rustici Software. Retrieved 30 July 2012.
  13. https://www.adlnet.gov/newest-version-of-xapi-version-1-0-3/
  14. https://github.com/adlnet/xAPI-Spec
  15. https://www.adlnet.gov/interviewing-xapi-spec-group-organizer/
  16. Johnson, Andy. "From ADL Team Member… Andy Johnson: Experience API (xAPI) version 1.0.1 released". ADL. Retrieved 24 April 2017.
  17. Downes, Andrew. "TinCanAPI.co.uk". Archived from the original on 22 April 2013. Retrieved 28 April 2013.
  18. "ADLnet.gov Tin Can Draft Specification". ADLnet.gov. Advanced Distributed Learning. Archived from the original on 15 September 2012. Retrieved 30 July 2012.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.