xAPI’s Tipping Point for Both Community & Industry

MakingBetter

Since last year, I worked with IEEE to standardize the Experience API (xAPI) specification. Most of my work is with the IEEE-LTSC but recently a few other IEEE standards groups expressed interest in using xAPI. They’re looking at xAPI because it provides a way to share data across devices, related to people, in a way other systems can understand. This is exciting stuff for everyone with a hand in making xAPI what it is.

xapi 158

xAPI, LRS – The Interview

eLearning 24-7

xAPI and LRS (Learning Record Stores) have been in the news and frankly everywhere within the e-learning industry in the past 1.5 The name “Tin Can API” stuck around once ADL advocated to use the prototype produced out of “Project Tin Can” as the basis for the Experience API (“xAPI”). on a side note – I – me, was always told that xAPI and Tin Can are one in the same). ADL, IEEE and many people and businesses talking about this technology call it xAPI.

xapi 66

Standard Options Apply

MakingBetter

This post is for vendors, developers and implementers of the Experience API and for anyone who may one day create something with xAPI. The choices made soon will ultimately impact what you will be able to do with xAPI 3, 5 and 20 years from now. In August, 2014 I participated in one of the IEEE Learning Technology Standards Committee (LTSC) monthly meetings. The PAR wasn’t approved by the LTSC in that August meeting. xAPI is about data interoperability.