@garemoko I do see it as another layer. Way back when I was collecting user voice feedback we had people saying "I want to get at my SCORM runtime data".... which in TinCan lead to the idea that we need to enable getting data back out.

I'm pleased with how useful the query API which started with that idea has become, but I think we're biting off more than we can chew if we expect that API to directly drive a reporting UI (well). So, I've always maintained that this API should be targeted at systems designed to pull substantial slices of an LRSs data, and those applications would in turn have associated UI to display the data, or serve other front ends designed to work with them. I do see this secondary system as something that could also potentially benefit from some standardization, but I'd like to see the 1.0 LRSs in the wild a bit before we tackle that.

Even if you accept the above, there is the question of where exactly to draw the line. Would people want reporting systems to only ingest statements about activities with a particular type? Maybe, but I'm a little doubtful -- though I do thin it will frequently be a requested way to pull data from this sort of system.