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. Others track activity on websites, simulations, and sensors. Organizations interested in counting on xAPI for their business needs must have a way to know the tools work.

xapi 158

Q&A - eLearning Standards Especially SCORM

Tony Karrer

Here's a recent one to get me started: Is it mandatory to use SCORM while developing an E-learning Software? You want to implement your courseware to the SCORM standard if you plan to have it launched and/or tracked under an LMS. One case is building a one-off course that needs simple tracking/reporting and will never run under an LMS. If you won't ever need to run it under an LMS, then SCORM is overhead you don't need (see Tracking Without an LMS ).

Standard Options Apply

MakingBetter

In August, 2014 I participated in one of the IEEE Learning Technology Standards Committee (LTSC) monthly meetings. This particular one was special, as we were formally reviewing the Project Authorization Request (PAR) for the Experience API to become a formal standards project. The PAR wasn’t approved by the LTSC in that August meeting. WiFi ” is essentially a set of IEEE standards — its project number is 802.11.

xAPI, LRS – The Interview

eLearning 24-7

My job was to help author SCORM 2004, focusing on how to develop content that would work in SCORM systems. Project Tin Can” was the name Rustici Software came up with to describe the work ADL contracted them to do. Tin Can” is a trademarked name owned by Rustici Software.

xapi 104