Thanks for the helpful responses here. My apologies for resurrecting an old thread...
There seem to be a lot of questions and some misunderstanding around xAPI and how it fits in with LMS systems. The linked suggestion is a good example of this. An LMS is not meant to function as an LRS, although there are some functions in the two systems that might intersect. This excerpt from xapi.com says it succinctly (emphasis mine):
"The LRS is the heart of any xAPI ecosystem, receiving, storing and returning xAPI statements. You’ll need an LRS in order to do anything with xAPI. Every other tool which sends or retrieves learning activity data will interact with the LRS as the central store."
So an LRS is a kind of business intelligence tool for education. It collects, stores, and analyses learning events from a wide range of learning tools, not limited to the LMS. It is perhaps helpful to understand the working assumption of the designers of xAPI, that education happens in many different places, decentralised from the LMS. So the LRS and xAPI are designed to federate learning from the confines of the LMS.
It seems to me that we should be encouraging Instructure to add to Canvas the ability to send xAPI event data to an LRS for analysis. I rather surprised that Canvas does not already have any function in this regard. Canvas DOES support receipt of results from an external tool like H5P or similar into Canvas, but this is quite limited and is in no way coordinate with a complete xAPI ecosystem. Moodle, Blackboard, Totara, Sakai, and many other LMS's already support xapi, so it is bizarre to me that Instructure have not begun to implement what many expect to be an industry standard protocol.
I hope this helps to bring some clarity to the conversation.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.