article thumbnail

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). Instead, I hope they can successfully take the steps that help IEEE consider it for standardization. This is just step one of many in that regard.

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.

Insiders

Sign Up for our Newsletter

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

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. We’re talking about it here frequently, and haven’t reached consensus. We’re active, yes.

article thumbnail

What vendors can do to prepare for xAPI 2.0

Experience API

As these efforts continue, likely so will standards implementations, so it’s a good idea to track the developments of the IEEE LTSC group. ADL’s Total Learning Architecture (TLA) efforts are pushing for modernizing learning and integrating emerging technologies.

xapi 52
article thumbnail

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? 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).

IEEE LTSC 101
article thumbnail

xAPI, LRS – The Interview

eLearning 24-7

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. ADL can’t file for a trademark themselves, so for now Rustici Software is stuck with the trademark for “Tin Can.” What is Tin Can exactly?

xapi 40