Remove Mashups Remove Offline Remove vendor Remove xapi

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. 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. Currently, adoption of xAPI is very LRS-centric.

Top 5 Talking Points from 2013 #LSCon

Unicorn Training

The browser v App debate seems to be moving towards the browser solution, at least for the corporate market, although if mobile is to truly transform learning for remote communities, offline will remain important for a long time yet. Or should that be XAPI? Security is a big issue in the corporate world and I picked up some useful pointers, although no definitive answers. XAPI is a standard for data transfer based on an Actor Verb Object syntax.

xapi 40