Wikipedia

Experience API: Difference between revisions

Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Vtraster (talk | contribs)
49 edits
→Current Status: fixed access date
m add link
 
(41 intermediate revisions by 32 users not shown)
Line 1:
{{Multiple issues|
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.<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>▼
{{Update|date=April 2022}}
{{Primary sources|date=April 2022}}
}}
▲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 allvarious types of learning experiences for learning systems.<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|archive-url=https://web.archive.org/web/20120806005118/http://www.learningsolutionsmag.com/articles/958/|archive-date=6 August 2012|url-status=dead}}</ref> Learning experiences are recorded in a [[Learning Record Store]] (LRS)., LRSswhich can exist within traditional [[Learninglearning Managementmanagement Systemssystem]]s (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|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|archive-date=22 August 2014|url-status=dead}}</ref>
 
==Summary==
The Experience API (Tin Can API) is commonlymeant consideredto the successor tosucceed [[SCORM]],<ref>{{cite news | url=https://aristeksystems.com/blog/elearning-standards-2022/#scorm| SCORMtitle=The Experience API (SCORM)| accessdate=2017-04-22}}</ref> the Sharable Content Object Reference Model), haswhich been theis de facto e-learninga standard for packaging e-learning content to be delivered to LMSs,.<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=eFrontelearningfreak|date=18 April 2011 Learning|accessdate=21 October 2015}}</ref> butThe therenew areExperience severalAPI drawbacksallows trainers to deploy several new capabilities that were not supported with SCORM. at the time,<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 |archive-date=10 March 2013 |archive-url=https://web.archive.org/web/20130310050538/http://www.thetrainingbusiness.com/softwaretools/tin-can-api/ |url-status=dead }}</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> The new Experience API allows trainers to deploy several new capabilities that were not supported with SCORM, such as:
 
*TakingRecording e-learning outsidefrom ofnon-browser theactivities, websuch browseras games and [[Simulation|simulations]].<ref name="SFGate / eLogic Press Release">{{cite web |title=(press release) 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.sfgateprweb.com/businessreleases/prwebscorm/articlee-learning/eLogic-Learning-Partners-with-Rustici-Software-to-3662367prweb9610860.phphtm |workpublisher=eLogicSFGate Learning|accessdate=31 PartnersJuly with2012 Rustici|archive-date=30 SoftwareJuly to2012 be|archive-url=https://web.archive.org/web/20120730094316/http://www.prweb.com/releases/SCORM/e-learning/prweb9610860.htm an|url-status=dead Early}}</ref><ref Adoptername="ASTD ofinterview thewith NextAaron GenerationSilvers" of/><ref SCORMname="Upside StandardsLearning">{{cite Knownweb|last=Gautam|first=Amit|title=Tin asCan: theMy 'TinFirst CanImpressions API'From mLearnCon 2012|url=http://www.upsidelearning.com/blog/index.php/2012/06/21/tin-can-my-first-impressions-from-mlearncon-2012/|publisher=SFGateUpside Learning|accessdate=31 July 2012|archive-url=https://web.archive.org/web/20120827182001/http://www.upsidelearning.com/blog/index.php/2012/06/21/tin-can-my-first-impressions-from-mlearncon-2012/|archive-date=27 August 2012|url-status=dead}}</ref>
*EPlatform transition; e.g. start e-learning inon nativea [[mobile applicationsdevice]], finish it on a computer<ref name="SFGate / eLogic Press Release" /><ref name="Learning Solutions Magazine" />
*More control overTeam-based e-learning content<ref name="SaltboxASTD Developersinterview Discusswith TinAaron CanSilvers" />
*Tracking learning plans and goals<ref>{{cite web|last=Downes|first=Andrew|title=I Want This: Tin Can Plans, Goals and Targets|url=http://tincanapi.co.uk/pages/I_Want_This.html|accessdate=28 April 2013|archive-url=https://web.archive.org/web/20130724021542/http://tincanapi.co.uk/pages/I_Want_This.html|archive-date=24 July 2013|url-status=dead}}</ref>▼
*Solid security using [[Oauth]]
*Platform transition; e.g. 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" />
▲*Tracking learning plans and goals<ref>{{cite web|last=Downes|first=Andrew|title=I Want This: Tin Can Plans, Goals and Targets|url=http://tincanapi.co.uk/pages/I_Want_This.html|accessdate=28 April 2013}}</ref>
 
The Experience API (Tin Can API)spec is an [[open source]].<ref>{{Cite APIweb |date=2013-07-11 |title=The Open Source Landscape |url=https://xapi.com/blog/the-open-source-landscape/ It|access-date=2022-04-19 is|website=xAPI.com |language=en-US}}</ref> xAPI uses a [[Representational state transferRestful]] [[web service]] that useswith [[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”.<ref name="Saltbox Developers Discuss Tin Can" /><ref>{{Citation |title=Ali Shahrazad & Russell Duhon of Saltbox Talk about Tin Can Alley at mLearnCon 2012 |url=https://www.youtube.com/watch?v=0bsx3QoloNs |language=en |access-date=2022-04-19}}</ref> 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“[[scratch space”space]]” for consuming applications.
 
==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 |archive-date=22 August 2014 |url-status=dead}}</ref>
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 [http://scorm.com 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/|work=Project Tin Can – The Next Generation of SCORM|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref>▼
 
▲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 [http://scorm.com 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/|work=Project Tin Can – The Next Generation of SCORM|publisher=Float Mobile Learning|accessdate=31 July 2012}}</ref>
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 [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 moniker "Tin Can API" was derived from Project Tin Can, and is still used interchangeably with the name "Experience API".<ref>https://www.trainingindustry.com/wiki/entries/experience-api-%28tin-can-api%29.aspx</ref>▼
 
▲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 [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|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}}</ref>
The Experience API was developed by a community working group (https://github.com/adlnet/xAPI-Spec/blob/master/CONTRIBUTING.md) 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>▼
 
▲The Experience API was developed by a community working group (https://github.com/adlnet/xAPI-Spec/blob/master/CONTRIBUTING.md) 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|archive-date=22 July 2012|archive-url=https://web.archive.org/web/20120722052825/http://tincanapi.com/what-is-tin-can/adopters/|url-status=dead}}</ref>
==Current Status==▼
 
▲==Current Statusstatus==
The current version of the specification is [https://github.com/adlnet/xAPI-Spec/blob/1.0.3/xAPI.md 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>
The current version of the specification is “[https://standards.ieee.org/ieee/9274.1.1/7321/ IEEE 9274.1.1-2023]” – also referred to as xAPI 2.0 - released 10 October 2023 by the [[IEEE]].<ref>{{Cite web|url=https://adlnet.gov/news/2023/11/22/xAPI-Officially-Becomes-a-Published-IEEE-Standard/|title=xAPI officially Becomes a Published IEEE Standard}}</ref><ref>{{Cite web|url=https://opensource.ieee.org/xapi/xapi-base-standard-documentation|title = xapi-base-standard-documentation|website = [[IEEE]]|access-date = 2 May 2024}}</ref>
 
Previous versions include: [https://github.com/adlnet/xAPI-Spec/tree/1.0.23, 1.0.2]., [http://www.adlnet.gov/wp-content/uploads/2013/10/xAPI_v1.0.1-2013-10-01.pdf 1.0.1].,<ref>{{cite web|last=Johnson|first=Andy|title=From ADL Team Member…Member... Andy Johnson: Experience API (xAPI) version 1.0.1 released|url=http://www.adlnet.gov/experience-api-xapi-version-1-0-1-released/|publisher=ADL|accessdate=24 April 2017}}</ref>
[https://github.com/adlnet/xAPI-Spec/blob/1.0.0/xAPI.md 1.0.0].<ref>{{cite web|last=Downes|first=Andrew|title=TinCanAPI.co.uk|url=http://www.tincanapi.co.uk|accessdate=28 April 2013|archive-url=https://web.archive.org/web/20130422072822/http://tincanapi.co.uk/|archive-date=22 April 2013|url-status=dead}}</ref>
[http://www.adlnet.gov/resources/Tin_Can_Draft_Specification?type=technical_documentation version 0.8] (official output of the BAA)<ref name="ADLnet.gov Tin Can Draft Specification">{{cite web|title=ADLnet.gov Tin Can Draft Specification|url=http://www.adlnet.gov/resources/Tin_Can_Draft_Specification?type=technical_documentation|work=ADLnet.gov|publisher=Advanced Distributed Learning|accessdate=30 July 2012}}<|archive-url=https://web.archive.org/web/20120915112512/ref> and [http://tincanapiwww.com/developersadlnet.gov/resources/docsTin_Can_Draft_Specification?type=technical_documentation|archive-downloadsdate=15 September 2012|url-status=dead}}</ref> and version 0.9] (research version specification)
[http://tincanapi.wikispaces.com/file/view/Tin+Can+API+v0.95.pdf/365362588/Tin%20Can%20API%20v0.95.pdf 0.95] (second research version specification).
 
==Implementations==
 
{| class="wikitable"
|+ Client Libraries
|-
! Name !! Language !! Licence
|-
| [https://github.com/BerryCloud/xapi-java xAPI-Java] || Java || Apache-2.0 license
|-
| [https://www.xapijs.dev xAPI.js] || JavaScript || MIT license
|-
| [https://rusticisoftware.github.io/TinCanPHP/ TinCanPHP] || PHP || Apache-2.0 license
|}
 
==References==
Line 36 ⟶ 50:
 
==External links==
* {{Official website}}
* [https://www.adlnet.gov/adl-research/performance-tracking-analysis/experience-api/ ADL's official website]
* [http://experienceapi.com Rustici Software's website]
 
{{DEFAULTSORT:Experience API}}
[[Category:Application programming interfaces]]
Retrieved from "https://en.wikipedia.org/wiki/Experience_API"