xAPI

xAPI = TinCan

xAPI (Experience API), or TinCan, or TinCan API, is a modern standard for interoperability in terms of tracking learning.

A relatively high-level explanation is available here: https://xapi.com/overview/

But in short, the idea is to use what had been learnt with SCORM and try to extend the scope to register more learning activities from students, which require the universalization of the language used to describe "outcomes" in the learning activities.

This includes recording activities that have been undertaken outside the typical LMS. For example, watching a YouTube tutorial or reading a blog post by a matter expert, or reading a scientific paper, can all be considered learning activities.

How to register activities ?

The idea of xAPI only works if a lot of players in the field start supporting it. This is why progress is slow (so far). It needs massive adoption to be useful.

So there are a few ways you (as a learner) could register activities:

• by learning inside an LMS if ** that LMS includes a LRS ** that LMS enables you to export your learning activities to a LRS of your choice
• by using a plugin in your browser that allows you to register your preferred LRS and then mark any page as a learning activity you want to report
• by visiting a website/web app/mobile app that explicitly allows you to register your learning activities in a LRS of your choice (for example offering a form or a button that allows you to indicate the URL of your LRS)
• by using any desktop application that offers you to register an LRS to keep track of your activity

CMI5: xAPI is not SCORM

One common misconseption is that xAPI is a new version of SCORM that will replace it. This is NOT the case. Although a subset of xAPI, called CMI5, is meant to be a reasonable substitute to SCORM, there has initially been very little people that understood that, and very little sign of improvement over time.

As such, if you WANT something similar to SCORM, you have to focus on xAPI's CMI5 subset. Not the whole xAPI

LRS

xAPI requires one very important element to work: a Learning Record Store (or LRS), that is a central database (or rather "table") that will store "statements" in the form of a gramatically-structured language like "I did this" (noun + verb + object), where the verb can be different actions taken over learning objects.

This LRS is not necessarily centralized: you could register all your activities in several LRS or you could (ideally) export all your learning records from one LRS to another (for example when you change companies).

Registering everyting

Of course, the

What is all the fuss about?

xAPI is not an incredible invention. It is a functional and relatively easy to implement system and protocol that, if implemented correctly and massively, will enable the portability of your learning profile. This could become a substitute of your CV, and enable you to keep improving it naturally over time.

Examples and references

• OpenLRS (now rebranded OpenLRW for Learning Record Warehouse because it includes more standards) is a Java-based LRS under the Educational Community License
• TraxLRS is a PHP/Laravel LRS developed under the EUPL 1.2 License
• Mylk is a European project meant at testing the implementation of a LRS and reducing the barrier to the adoption of the technology. A test website is available at https://mylk-check.com/. Sadly, it seems to be down at the time of writing, but we know the team behind it and they were probably preparing a new version.
• LRS-Bundle is a PHP/Symfony bundle to manage both an LRS and CMI5, but it is unfinished work.

xAPI in Chamilo

We intend to develop support for xAPI (an integrated LRS + the possibility to export activities to an external LRS) for Chamilo 2.0. This will also include support for CMI5.