How To Make Your EdTech Product xAPI Compliant

3
1895
How To Make Your EdTech Product xAPI Compliant? | Cómo Hacer Un Producto EdTech Compatible con xAPI

In an effort to increase the level of engagement with the EdTech development community, ADL has released a series of documents on the requirements for conformance and certification of learning applications. (For those who don’t know, ADL is the US government organization leading the development of specification standard xAPI.) The series will serve as a guide for prospective developers interested in building tools that support xAPI and are able to coexist in the open ecosystem of technologies used by students.

The xAPI standards allow developers to record learning and performance events that take place using their technology. The increasing availability of xAPI-compliant data from multiple sources has uncovered the need for central repositories. ADL has adopted the term “Learning Record Store” (LRS) for these repositories. An announcement in April shared a series of resources for developers of LRS to ensure products meet the specifications, most notably of all the LRS Specification Testing site at lrstest.adlnet.gov.

ADL has made available three documents that give further guidance for the compliance process of LRS:

ADL’s efforts are ongoing, which means that the current versions of the documents made available are likely to change over time. In a way, this is expected as more members of the community get involved and find ways to make the conformance process more practical.


eThink LogoThis Moodle Practice related post is made possible byeThink Education, a Certified Moodle Partner that provides a fully-managed Moodle experience including implementation, integration, cloud-hosting, and management services. To learn more about eThink, click here.


 

  • Jason Haag

    Great article and thank you for posting! The profile specification (currently) has nothing to do with LRS conformance or testing. The profile spec isn’t about the the individual learner. In a nutshell, a profile is simply about documentation. A profile is the human or machine-readable documentation of application-specific concepts, extensions, and statement templates used when implementing xAPI in a particular context.

  • Thank you for the clarification, Jason!

    I understand profiles do not have to be necessarily about individual learners.

    Wouldn’t it be fair to say, thought, that a standard xAPI Profile specification designed to be “discovered, reused, published and managed”, could be applied to the learner? I’d even dare saying this is the most straightforward use case for a xAPI Profile.

    I was focused on this page: https://github.com/adlnet/xapi-profiles/blob/master/xapi-profiles-about.md#profile

    Cheers!

  • Jason Haag

    A learner profile is something we do need but that would be a separate spec. This one is more about application profiles for xapi.