For the last two years the xAPI specification has largely gone unchanged. Its resilience and stability enables what those of us who work with xAPI are clearly feeling: this thing is starting to take off. It didn’t start out as a sure thing; there were major obstacles in our path.
In terms of xAPI support, Lectora offers a lot right out of the box. Lectora has the ability to assign statement generation to any object within a page using a trigger. Each page also generates its own statement without having to do anything other than set the output type for publishing. [Read more…]
Adobe Captivate will publish content to xAPI version 1.0. Captivate will publish statements that are readable using the slide name. For the most part with Captivate you are tracking very similar things to SCORM with the xAPI output. Captivate uses ADL registered verbs for its output. [Read more…]
Articulate Storyline 2 will publish content to xAPI version 1.0. It is recommended to get update 5 for Storyline 2 as it will publish the xAPI statement using Name instead of ID which makes the statement human readable and much easier to parse in the visualizations that will be created from the data. [Read more…]
xAPI Camp: Autodesk – San Francisco – February 11, 2015
xAPI Camp: JISC – London – April 22, 2015
xAPI Camp Learning Solutions – Orlando – March 15
xAPI Camp mLearnCon – Austin – June 7, 2015