Experience API: Difference between revisions

Revision as of 20:50, 2 May 2024

Revision as of 10:18, 24 May 2024

Line 13:

*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>

The Experience API spec is [[open source]].<ref>{{Cite web |date=2013-07-11 |title=The Open Source Landscape |url=https://xapi.com/blog/the-open-source-landscape/ |access-date=2022-04-19 |website=xAPI.com |language=en-US}}</ref> xAPI uses a [[Restful]] web service that with [[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 space” for consuming applications.

==History==