If your cmi5 package launches but reporting still looks wrong, the problem is often scope confusion. This article explains how Assignable Units, registration, and session lifecycle work together, and why separating them is essential for correct launch behavior, resume logic, completion, and analytics.
In cmi5, package structure is part of the runtime contract. This article explains how cmi5.xml shapes LMS import, course graphs, AU launch behavior, and completion semantics before any content code runs.
cmi5 is not just xAPI packaging. It is an xAPI profile that adds rules for LMS launch, registration, session handling, allowed statements, and completion behavior so content and platforms can interoperate predictably.
xAPI solved learning event transport, but it did not define a shared LMS launch contract. This article explains why cmi5 exists, what constraints it adds, and why those constraints matter for real interoperability.
xAPI is powerful when you need flexible learning telemetry across systems, but it becomes a costly choice when the real requirement is only launch, completion, score, and bookmarking. This article explains the architectural boundary and why cmi5 matters when LMS-launched interoperability enters the picture.
xAPI support is not one feature. It can mean statement ingestion, launch, package handling, proxy delivery, reporting, or cmi5 workflow. This article shows how to evaluate each capability and ask for proof that matches your delivery model.
“HTTP success does not mean valid xAPI. Learn a layered debugging workflow for rejected statements, cmi5 contract issues, batch failures, and accepted data that still breaks reporting.
xAPI Launch is not SCORM with a new name. It is a secure startup pattern for getting runtime xAPI configuration into launched content without exposing credentials or learner identity. This article explains the flow, the architectural boundary, and why cmi5 exists.
SCORM 2004 is not the future of e-learning standards, but it is still part of the present. If you work with enterprise LMS platforms, legacy content, or structured learning paths, SCORM 2004 remains highly relevant. Not because it is modern, but because it is still deeply embedded in the ecosystem.
How SCORM shaped SCORM 2004, xAPI, and cmi5, and the lessons it left behind.