article thumbnail

The ongoing work of learning standards

Litmos

And then the IMS (an initiative of Educause before being spun out as an independent effort) started creating standards, as did the IEEE (Institute of Electrical and Electronics Engineers), the major body in the US responsible for computing standards. ADL decided to create a new standard, the Experience API (xAPI; originally known as Tin Can).

article thumbnail

Adapting to change: Going hybrid and supporting standards

Rustici Software

xAPI was a glimmer in the eye of ADL, Rustici and in particular Ben Clark, who was spearheading Project Tin Can development. Conversely, LTI and other IMS standards were the driving force behind most academic institutions. When I first joined Rustici in 2011, SCORM was the de facto standard for our customers.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Real (e)Learning Heroes

Clark Quinn

Several other initiatives include IEEE (which is pretty much the US based effort on electric and electronic technology standards to the international stage), and the IMS efforts from academia. The Department of Defense’s ADL initiative decided upon a version, to move things forward, and thus was born SCORM. Standards are good.

ADL 103
article thumbnail

Day 5: xAPI and more – what next for SCORM?

LearnUpon

Funnily enough, Tin Can (xAPI) , which we’ll examine next, adopts a similar approach to AICC regarding the HACP and, as a result, can track data across domains, or indeed, almost anywhere. eLearning now: Tin Can (xAPI). I’ll begin with the Tin Can API, also known as xAPI, officially released as version 1.0 in April 2015.

xapi 40
article thumbnail

Semantic Interoperability

Experience API

Because without semantic interoperability, the Experience API (xAPI) has a limited future. For us, semantic interoperability in xAPI will be achieved when there is a generally accepted information model. There’s a strong possibility that collaborative work between ADL and IMS could help a great deal.

ADL 40
article thumbnail

Semantic Interoperability

Experience API

Because without semantic interoperability, the Experience API (xAPI) has a limited future. For us, semantic interoperability in xAPI will be achieved when there is a generally accepted information model. There’s a strong possibility that collaborative work between ADL and IMS could help a great deal.

ADL 40
article thumbnail

SCORM vs. LTI: what’s the difference?

Rustici Software

If you’ve been familiar with Rustici Software for a long time, you’ll know we’ve helped people for a long time with SCORM and xAPI. It stands for Learning Tools Interoperability and it is a standard created by the IMS Global Learning Consortium. Governance: LTI is created and maintained by IMS; SCORM by ADL. What is LTI?

SCORM 53