xAPI's Data Interoperability Research

This board is intended to generate and prioritize thoughts and ideas about what it means for xAPI to be interoperable. What else, beyond what's in the xAPI specification, would support interoperability?

Should an LRS be able to broadcast/pre-negotiate the recipes it understands?

Ultimately, the goal is to allow technology purchasers to have up-front transparency in terms of which tools in their ecosystem can handle which kinds of events. While this might seem like purely a marketing problem to solve, there's a potential programmatic step that could be useful, in allowing LRS & other system actors to exchange information about supported recipes (or even supported syntaxes outside of xAPI).  This also could give vendors some "cover" if they are evolving systems to be ambidextrous or add more relevant recipes as they add functionality. 

  • Gravatar Dan Rinzel
  • Oct 24 2016
  • New
  • Attach files
  • Dan Rinzel commented
    October 24, 2016 17:59

    Related to, but slightly different than certification for specific recipes, this idea is about configuration-time or run-time programmatic negotiation

  • Andrew Downes commented
    October 24, 2016 19:02

    LRSs should be able to receive, store and retrieve any recipes. Supported recipes are more relevant for Learning Record Consumers. (LRS products may also incorporate LRCs, but not necessarily - for this reason negotiation is not possible.)

  • Dan Rinzel commented
    October 26, 2016 15:58

    Andrew can you dumb that down a bit for a newbie? I think maybe I'm just conflating or misusing terms. Is there an exchange between system actors in xAPI that allows one system to ask another "do you have data that conforms to/uses recipe foo?" or "which recipes to do you have data for?" and get answers?

  • Gravatar