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. Our start point is the xAPI 1.0.3 IEEE stamping xAPI would encourage adoption, particularly outside of the US.

IEEE LTSC xAPI TAG to vote on proposing IEEE standardize xAPI

Experience API

Facts: Next week, the IEEE LTSC xAPI TAG will be taking a vote about if and which aspects of xAPI 1.0.3 to propose to the broader IEEE for consideration as a standard. Opinions (mine): Somewhat important: standardization matters in that many organizations (particularly some outside the US) will care that xAPI has (eventually) been blessed by IEEE. More important: the nexus of xAPI work is moving toward this group, and it’s active.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

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 lay out options for how we can approach standardization and the reasoning behind them. In August, 2014 I participated in one of the IEEE Learning Technology Standards Committee (LTSC) monthly meetings.

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. They’re looking at xAPI because it provides a way to share data across devices, related to people, in a way other systems can understand. This is exciting stuff for everyone with a hand in making xAPI what it is.

xapi 158

xAPI, LRS – The Interview

eLearning 24-7

xAPI and LRS (Learning Record Stores) have been in the news and frankly everywhere within the e-learning industry in the past 1.5 The name “Tin Can API” stuck around once ADL advocated to use the prototype produced out of “Project Tin Can” as the basis for the Experience API (“xAPI”). Last heard ADL calls this new standard the Experience API? (on on a side note – I – me, was always told that xAPI and Tin Can are one in the same). What is IEEE?

xapi 66

Slow Cooking – Our First Year of MakingBetter

MakingBetter

When we first launched MakingBetter on January 7, 2014, it was with the intent that we’d mostly focus our efforts on a few small projects and workshops while beginning standardization work on xAPI with IEEE-LTSC. When I was working with ADL, it was easy to talk about the potential for revolutionary performance improvement and deeper learning with the advent of xAPI. How a 13-pound brisket looks after four hours, eight hours and twelve hours.