Remove ADL Remove Adoption Remove Apache Remove Security

What is the plan for DISC, xAPI, and ADL?

MakingBetter

Towards the end of last year, our big announcement was the formation of the not-for-profit Consortium formed to handle the governance and address the evolution of xAPI with/for ADL. xAPI, being open-source and licensed as Apache 2.0, doesn’t require ADL’s permission for us to do this. We’ve worked out the details of what we’re going to take on with ADL so the connections between DISC and ADL can be very explicit, very concrete and very visible.

ADL 126

With Gratitude…

MakingBetter

There are a myriad of reasons why 2015 was good for Megan and I, but the one reason that stands out is the incredible gains in xAPI’s adoption that happened this year. We know there’s been incredible growth in xAPI adoption. We know projects are already being planned for the beginning of 2016 at a scale that equals the whole of xAPI adoption in 2015. xAPI is so successful that it’s actually becoming a challenge for ADL to support it to the scale it now demands.

xapi 126

xAPI, LRS – The Interview

eLearning 24-7

Aaron, can you tell me a little bit about your background and how you became involved with ADL? 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. Two months after my layoff, a company called CTC recruited me to work for ADL. I worked with ADL from 2003-2006 and participated in the Technical Working Group afterwards. Last heard ADL calls this new standard the Experience API? (on

xapi 79