Remove Adoption Remove Community Remove Emergent Remove IEEE LTSC

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. Meanwhile different needs among xAPI adopters in the learning technology business are becoming clearer. What’s emerging are learning activities that look a lot more like work or straight up computing.

xapi 158

Standard Options Apply

MakingBetter

In August, 2014 I participated in one of the IEEE Learning Technology Standards Committee (LTSC) monthly meetings. Once the request is made and approved by IEEE’s New Standards Committee, we begin the last leg of a journey that started with friends riding roller coasters in Cedar Point amusement park in Sandusky, OH back in 2009. The PAR wasn’t approved by the LTSC in that August meeting. Currently, adoption of xAPI is very LRS-centric.

xAPI, LRS – The Interview

eLearning 24-7

In 2003, the eLearning startup I worked for shuttered its doors as our customers moved to adopt SCORM, and we had no idea how to do that. ADL, IEEE and many people and businesses talking about this technology call it xAPI. The nature of mobile devices became too complex too quickly to wrangle a solution that industry could adopt. was so popular and so adopted that people weren’t even bothering with SCORM 2004. I was told xAPI is in IEEE’s hands?

xapi 68