article thumbnail

What happened in 2023 and what’s next for eLearning standards

Rustici Software

We were shocked to see how many people joined Chris Tompkins and Brian Miller on “Our IEEE LTSC voting members recap 2023 and what’s next for the standards” webinar last week. The Rustici Software team regularly contributes to the evolution of the standards through involvement with the IEEE, ADL and 1EdTech eLearning standards groups.

article thumbnail

Mea culpa

Experience API

To be honest, I am struggling to discern which pieces of work would best support the xAPI community and Rustici Software. There’s good work happening at the IEEE LTSC TAG xAPI , and we’re doing a bit of it. And ADL has published new BAA requests , and we’re considering those. We’re active, yes.

Insiders

Sign Up for our Newsletter

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

article thumbnail

AICC and SCORM Compliance: The Benefits for Your e-Learning

Trivantis

That’s a bit like what was happening in the e-Learning community before SCORM was established. To solve this problem, in 1999 the government tasked a small research laboratory, ADL, to “develop common specifications and standards for e-learning.” Remember the battle between Blu-ray Discs and DVDs?

AICC 63
article thumbnail

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? 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 40
article thumbnail

Q&A - eLearning Standards Especially SCORM

Tony Karrer

There are a bunch of other standards by ADL (who is responsible for SCORM ), IMS , IEEE LTSC including CORDRAâ„¢ , LOM , Meta-data , etc. Note: ARIADNE, AICC, IEEE LTSC, and IMS all participate in ADL's work on SCORM). I've also seen it in an environment that had certain restrictions on JavaScript.

IEEE LTSC 101