SCORM vs xAPI vs H5P: Which Content Standard for HK e-Learning?
A practical comparison of SCORM 1.2, SCORM 2004, xAPI and H5P for Hong Kong e-Learning teams — what each standard stores, when each fails, and how Drupal LMS supports all of them.
Key facts about content standards
- SCORM, xAPI or H5P?
- All three, for different purposes. SCORM packages a course, xAPI records learning that happens outside a package, and H5P is a browser-based authoring format for interactive activities.
- SCORM 1.2 or SCORM 2004?
- 1.2 for legacy libraries and the broadest authoring-tool compatibility. 2004 for completion status, richer sequencing and interaction-level response data.
- Does Drupal LMS include an LRS?
- LMS Xapi ships a minimalistic LRS for scores and activity states — enough for statement capture and reporting inside your own infrastructure, not a full commercial LRS with longitudinal analytics.
- Is H5P free to author?
- Yes. H5P content is authored and edited in the browser with no desktop authoring licence cost.
- What is the most common Hong Kong mistake?
- Collecting xAPI statements without deciding where they are stored, how long they are kept and who can read them — a personal-data exposure under the PDPO.
- Who is this page for?
- Hong Kong e-Learning teams and HR learning-content owners choosing content standards.
The short answer
These are not competing products. They solve different problems, and a serious Hong Kong e-Learning estate uses all three. SCORM packages a course. xAPI records what a learner did outside a packaged course. H5P is a content authoring format for interactive activities that live inside a page rather than a package.
SCORM = "here is a course, tell me the score." xAPI = "here is what the learner actually did." H5P = "here is an interactive activity I can edit in the browser."
SCORM: the packaging standard
SCORM is a specification for packaging e-learning content. A SCORM package is a zip file containing a manifest and assets. When the LMS launches it, the content runs inside an API the LMS exposes, and the package reports completion, score and suspend data back.
Two versions matter commercially:
- SCORM 1.2 — the long-standing default. Broadest authoring-tool compatibility worldwide. Limited data model: essentially completion, score and suspend state.
- SCORM 2004 — richer sequencing, multiple objectives, completion status, interaction data and correct/incorrect response detail. Requires authoring tools and LMS support that handle it.
For Hong Kong organisations migrating an existing content library, SCORM compatibility is what lets you bring your assets with you. That is the practical reason it appears on every serious vendor comparison table, including Opigno Enterprise, which explicitly states SCORM 1.2 and 2004 support alongside Articulate Storyline and Adobe Captivate.
Where SCORM struggles is anything outside the package boundary. If learning happens in a workplace, in a meeting, or across systems, SCORM has nowhere to put the evidence. That is the gap xAPI was designed to fill.
xAPI: the statement standard
xAPI (also known as Tin Can API) records statements: actor, verb, object, in context, timestamped. A statement is a small structured record of one learning-relevant event.
{
"actor": { "name": "Employee 4711" },
"verb": { "id": "http://adlnet.gov/expapi/verbs/completed",
"display": { "en-US": "completed" } },
"object": { "id": "https://lms.example/xapi/courses/safety-101",
"definition": { "name": { "en-US": "Workplace Safety 101" } } },
"result": { "completion": true, "success": true },
"context": { "contextActivities": { "parent": [ /* course */ ] } },
"timestamp": "2026-10-12T09:41:07Z"
}The important architectural point: xAPI statements go to an LRS (Learning Record Store), not only to the LMS. That decouples the recording of learning from the delivery of courses, which is exactly what you want when learning is not course-shaped.
Drupal LMS ships LMS Xapi, which provides an activity-answer plugin, a field formatter for any entity type, support for importing xAPI packages (for example from Articulate 360), and what the project describes as a minimalistic LRS for storing scores and activity states. Being honest about scope: a minimalistic LRS is enough for statement capture and reporting inside your own infrastructure — it is not a full commercial LRS with longitudinal analytics, and we would scope that separately if you need it.
The xapi_tincan activity type appears in Drupal LMS, so xAPI content can be consumed as a normal activity inside a course.
H5P: the content authoring standard
H5P is a separate category: an open-source library of interactive content types, authored and edited in the browser. It covers interactive video, quizzes, branching scenarios, presentations, drag-and-drop, timelines, flashcards and more.
For schools, H5P is arguably the highest-leverage of the three, because it removes the authoring licence cost. Teachers produce interactive content themselves instead of buying a desktop authoring tool per seat. For corporate training, it is the fastest route to a knowledge check embedded inside a lesson rather than bolted on as a separate worksheet.
Drupal LMS integrates it via LMS H5P, which plugs into Drupal H5P to expose that library. Note the naming distinction worth remembering: Drupal LMS H5P is the LMS integration module; Drupal H5P is the underlying content framework.
Choosing per content type
| Content situation | Use | Why |
|---|---|---|
| Existing Storyline or Captivate library | SCORM 1.2 or 2004 | Assets are already packaged; no rebuild required |
| Formal course with completion evidence | SCORM 2004 | Completion status, score, sequencing |
| Interactive exercise inside a lesson | H5P | Authored in-browser, no desktop licence, embeddable |
| Offline or isolated-network exam | SCORM 1.2 (delivered locally) | Runs without connectivity; Drupal LMS exam delivery supports isolated workstations |
| Workplace learning, meetings, supervisor coaching | xAPI | Records events outside a package |
| Blended learning across systems | xAPI to an LRS | Decouples record from delivery |
| Regulated certification with expiry | SCORM + platform records | Assessment evidence plus certification cycle management |
Pitfalls we see in Hong Kong projects
SCORM 2004 without authoring-tool support
The content declares 2004 sequencing but the authoring tool only emits 1.2 semantics. The course launches, but resume-data and objective tracking behave unexpectedly. Check the authoring tool version at purchase time, not at upload time.
xAPI statements with no LRS plan
Collecting statements without deciding where they are stored, how long they are retained and who can read them creates a personal-data exposure under the PDPO. Decide retention and access before the first statement is written, not after.
H5P treated as a substitute for instructional design
An interactive video is not a course. H5P activities need learning objectives, sequencing and an assessment plan behind them. This is precisely where our courseware service exists — the platform makes producing content cheap, but someone still has to design it.
No standard solves the real problem, which is that content designed without a learning objective produces activity data without competence change. Standards move the data; they do not move the outcome.
If your content strategy is "we will standardise on SCORM 2004 and everything will be interoperable," you have solved packaging and nothing else.
Questions about content standards
Which standard should we standardise on?
It depends on the content, and the honest answer is that you will end up using more than one. SCORM 1.2 and 2004 for packaged, assessable, completion-tracked e-learning; H5P for interactive content authored in the browser; xAPI for granular statements about activity that happen outside the LMS, including real-world work. The article maps content type to standard.
Can we keep using SCORM if we move platforms?
Yes — that is the point of the standard. SCORM packages are portable, so content moves between platforms that both support it. This is why we recommend standards-based content and YAML course packages even when the current platform is not in doubt: it is what keeps a later migration cheap.
Does xAPI come with a record store?
Yes. LMS Xapi provides xAPI package support along with a minimalistic LRS for storing scores and activity states. For most Hong Kong organisations that is enough to start; a full LRS is a separate decision with its own operational implications, and we will advise on it rather than default you into it.
What usually goes wrong in content standard projects?
The most common failure is authoring content inside a proprietary tool and then discovering the export path is limited or lossy. The second is assuming a standard solves the assessment design. The article covers the pitfalls we see in Hong Kong projects, including what to check before you commit to a tool.
Can you migrate content from a commercial authoring tool?
Frequently yes, but the answer depends entirely on the export path from that tool, which we verify against a sample of your actual content during scoping rather than from a documentation page. Where content is cleanly exportable it usually converts; where it is not, we will tell you whether to convert, rebuild or leave it in place.
Migrating an existing content library?
Send us a sample SCORM package or an H5P library and we will tell you what comes across cleanly, what needs conversion, and what should be rebuilt instead of migrated.