Hey @Niall_Sheridan
Responce to xAPI development in Evolve.
There is a plugin for Chrome by Riptide call the “Elements xAPI inspector” which captures the xAPI enroute and analyzes them. Along those lines, I think that something could be built out that listens for submission events within an MCQ and grabs and modifies the statement right before the TinCan.js gets ready to send it. I mean in theory that is how it would/could work.
But I do totally agree that the current state of the xAPI statements, while meeting the standard, are rather lacking in detail.