Follow-up to the xAPI ingestion layer (DEC-0064, branch feature/xapi-ingestion).
Grading already works through the custom xapi_track.php endpoint and must stay there: it ignores the statement actor and reuses the SCORM grade pipeline, whereas core_xapi binds processing to the actor identity, which does not fit our $USER-attributed model.
This issue is only about an optional core_xapi_statement_post handler (mod_exelearning\xapi\handler, h5pactivity pattern) to emit Moodle events / analytics from the same statements — not to grade. It should be pursued only if it adds real value (learning analytics, logstore signal).
Out of scope of the original xAPI ingestion PR.
Refs: FTE-007 (core_xapi analysis), AN-012 (route analysis), docs/tracking-architecture.md.
Follow-up to the xAPI ingestion layer (DEC-0064, branch
feature/xapi-ingestion).Grading already works through the custom
xapi_track.phpendpoint and must stay there: it ignores the statement actor and reuses the SCORM grade pipeline, whereascore_xapibinds processing to the actor identity, which does not fit our$USER-attributed model.This issue is only about an optional
core_xapi_statement_posthandler (mod_exelearning\xapi\handler, h5pactivity pattern) to emit Moodle events / analytics from the same statements — not to grade. It should be pursued only if it adds real value (learning analytics, logstore signal).Out of scope of the original xAPI ingestion PR.
Refs:
FTE-007(core_xapi analysis),AN-012(route analysis),docs/tracking-architecture.md.