IEEE LTSC xAPI TAG A-OK

Experience API

Shelly Blake-Plock announced last night via LinkedIn that he would be leading a Technical Advisory Group (TAG) for IEEE LTSC (Learning Technologies Standards Committee). In his own words, Shelly describes the work in this way: Our initial purpose is to create an IEEE technical report as a reference and implementation guide for xAPI 1.0.3. IEEE stamping xAPI would encourage adoption, particularly outside of the US.

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. This is important as xAPI moves into standardization and wider adoption.

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. I worked with business analysts, IT and communications teams on governance for these new technologies. I was told xAPI is in IEEE’s hands?

xapi 104