Remove Adoption Remove Analysis Remove IEEE LTSC Remove vendor

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. I’m going to ask you as vendors, entrepreneurs, developers, designers from all around the world to provide me with your counsel as I ultimately must direct the effort. In August, 2014 I participated in one of the IEEE Learning Technology Standards Committee (LTSC) monthly meetings. 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