Transform Learning with a Powerful Enterprise LMS

Learn more
SCORM, xAPI, cmi5 & LTI

eLearning Standards Explained: SCORM, xAPI, cmi5, LTI, QTI and OneRoster

What each eLearning standard does, its current version, where it is supported and where it breaks, with a scenario table for choosing the right one.

Diagram-style illustration of connected arrows between learning systems, representing how eLearning standards such as SCORM, xAPI and LTI link content, tools and data

eLearning standards are the published rules that let learning content, tools and learner data move between systems without custom code. The ones that matter in 2026 are SCORM for packaged courses, xAPI for detailed activity data, cmi5 for launching xAPI content from an LMS, LTI 1.3 for plugging external tools into a platform, QTI for questions, Common Cartridge for whole courses, OneRoster for class rosters and grades, and Open Badges for credentials.

Each standard solves a different interoperability problem, so most organisations use several at once. A corporate LMS might import SCORM packages from an authoring tool, launch a proctoring service over LTI, send xAPI statements to a learning record store and issue Open Badges on completion. Choosing well is less about picking the newest standard and more about matching each one to the job it was designed for.

This guide explains what each standard does, how it works under the hood, where it is supported and where it breaks. It is written for LMS administrators, developers and buyers who need to make decisions, not memorise acronyms. Every version and date was checked against the publishing bodies (ADL, 1EdTech and IEEE) in October 2026.

The eLearning standards map: which problem each one solves

The easiest way to understand eLearning standards is to group them by the question they answer. Some describe how content is packaged, some describe how a learner's activity is recorded, and some describe how two systems talk to each other.

StandardMaintained byProblem it solvesCurrent version
SCORMADL InitiativePackage a course so any compliant LMS can launch it and record completion and scoreSCORM 1.2 and SCORM 2004 4th Edition
xAPIADL Initiative, IEEERecord any learning activity as a statement and store it in a learning record storeIEEE 9274.1.1-2023 (xAPI 2.0)
cmi5ADL InitiativeLaunch xAPI content from an LMS with agreed rules for sessions and completionQuartz edition
LTI1EdTechLaunch an external tool from inside a platform, with identity, roles and grade returnLTI 1.3 with LTI Advantage
QTI1EdTechExchange questions, tests and results between assessment systemsQTI 3.0
Common Cartridge1EdTechMove a whole course (content, assessments, tool links) between platforms1.3 in wide use, 1.4 at Candidate Final
OneRoster1EdTechExchange rosters, classes and grades between a student information system and learning toolsOneRoster 1.2
Caliper Analytics1EdTechDescribe learning events in a common format for analyticsCaliper 1.x
Open Badges1EdTechIssue portable, verifiable digital credentialsOpen Badges 3.0

Two practical rules follow from this map. First, packaging standards (SCORM, cmi5, Common Cartridge) and integration standards (LTI, OneRoster) are not alternatives to each other; they sit at different layers. Second, a vendor claiming "standards support" tells you nothing until you know which standard, which version and which part of it.

SCORM: the packaging standard that still runs most corporate courses

SCORM (Sharable Content Object Reference Model) defines a zip package and a JavaScript conversation between the content and the LMS. Authoring tools export SCORM, the LMS imports the zip, and when a learner opens the course the content looks for an API object provided by the LMS window and calls it to report progress.

The package itself is described by a file called imsmanifest.xml at the root of the zip. It lists the resources, the launch file and, in SCORM 2004, the sequencing rules that decide which part of the course a learner may open next.

SCORM 1.2 vs SCORM 2004 in one table

AreaSCORM 1.2SCORM 2004 (3rd and 4th Editions)
API callsLMSInitialize, LMSGetValue, LMSSetValue, LMSCommit, LMSFinishInitialize, GetValue, SetValue, Commit, Terminate
StatusOne element, cmi.core.lesson_status (passed, completed, failed and so on)Two elements: cmi.completion_status and cmi.success_status
Scorecmi.core.score.raw with min and maxcmi.score.scaled (-1 to 1) plus raw, min and max
Bookmark data (suspend_data)Up to 4,096 charactersUp to 64,000 characters
SequencingNone (the LMS decides navigation)Rules in the manifest control order, attempts and rollup

The split status in SCORM 2004 is the most useful difference in practice. A learner can complete a course without passing it, and SCORM 2004 records both facts separately. SCORM 1.2 forces the content to choose one value, which is why so many "completed but not passed" reporting problems trace back to 1.2 packages.

Where SCORM still fits, and where it hurts

SCORM remains the safest choice when you buy off-the-shelf courses or export from tools such as Articulate Storyline, Rise or iSpring, because almost every LMS imports it. Its limits are structural: it only tracks what happens inside a browser session launched by the LMS, it reports a small fixed set of data, and it struggles with offline and mobile use.

The most common SCORM failures we see are long courses that lose progress because the bookmark data exceeds the 1.2 limit, content hosted on a different domain that cannot reach the LMS API, and packages exported as 2004 into an LMS whose 2004 support is partial. Moodle is a good example of the last point: it passes the SCORM 1.2 conformance tests, while its documentation says SCORM 2004 is not fully supported because sequencing and navigation are incomplete. Exporting as SCORM 1.2 is often the more reliable choice for Moodle sites.

What happened to AICC

AICC, the older aviation-industry standard, still appears as an import option in some LMS products. The committee behind it dissolved in 2014 and handed its newest work, cmi5, to ADL. Treat AICC as legacy: keep it only for old content you cannot re-export, and plan to republish that content as SCORM or cmi5.

xAPI: tracking learning that happens outside a course player

xAPI (the Experience API, once known as Tin Can) records learning as statements in an actor, verb, object form, such as "Asha completed Fire Safety Module 3" or "Ravi attempted the forklift simulation with a score of 82". Content, apps and devices send these JSON statements over HTTPS to a learning record store (LRS), which stores them and makes them available to reports and other systems.

Because the statement format is open-ended, xAPI can describe simulations, mobile apps, virtual reality, on-the-job observations and offline activity that SCORM cannot see. That flexibility is also its main risk. Two teams can describe the same activity with different verbs and the data stops being comparable. xAPI profiles exist to fix that by agreeing vocabularies for a domain, and you should decide on one before you collect data at scale.

xAPI is now an IEEE standard

The ADL Initiative's xAPI specification became IEEE 9274.1.1-2023, often called xAPI 2.0. IEEE approved it on 30 March 2023, and ADL announced in November 2023 that it had been published as an open-source IEEE standard and that the older 1.0.3 repository would be archived. LRS vendors and content tools are moving to 2.0 at their own pace, so ask which version an LRS conforms to before you buy.

What an LMS needs to "support xAPI"

Support can mean very different things. Some platforms include a full LRS. Others only send statements to an external LRS. Others can launch xAPI content but keep only a completion flag. Moodle shows why the wording matters: its core xAPI subsystem lets H5P activities report results, but the documentation is explicit that it is not a learning record store. If you need to query statements, run analytics or keep statements from many sources, plan for a separate LRS.

Choosing a learning record store

An LRS is a database with a specified API: it accepts statements, validates them, stores them and answers queries. Options range from open-source servers you host yourself to commercial services with dashboards built in. Before choosing one, decide who owns the data, how long statements must be kept, whether other systems need to read them, and which xAPI version your content sends. ADL publishes a conformance test suite for LRS products, and asking a vendor for its results is a quick way to separate full implementations from partial ones.

cmi5: xAPI with rules an LMS can rely on

cmi5 is an xAPI profile written for the LMS use case. Plain xAPI does not say how an LMS should launch content, how the content authenticates to the LRS, or what counts as finished. cmi5 answers those questions, which is why it is the closest thing to "SCORM rebuilt on xAPI".

The specification began at the AICC in 2010. When the AICC dissolved in 2014 it transferred cmi5 to ADL, and the current edition, named Quartz, was announced in June 2016. In a cmi5 course:

  • A course structure file describes the course and its assignable units (AUs), the pieces the LMS can launch.
  • The LMS launches an AU with a URL that carries the LRS endpoint, a registration and a one-time fetch address the content uses to obtain its auth token.
  • The AU sends statements with a fixed set of defined verbs: launched, initialized, completed, passed, failed, abandoned, waived, terminated and satisfied.
  • Move-on criteria set in the course decide when an AU, and then the course, is satisfied.

cmi5 fixes SCORM's cross-domain and data-size problems because content talks to the LRS over HTTPS rather than through a JavaScript object in the LMS window. Its weakness is adoption. Authoring tool support is good, LMS support is uneven, and Moodle has no cmi5 in core. Check an LMS's cmi5 support with a real package before you commit a content library to it. Our SCORM vs xAPI vs cmi5 comparison goes deeper on choosing between the three.

LTI 1.3 and LTI Advantage: plugging tools into a platform

LTI (Learning Tools Interoperability) is not a content format. It lets a platform such as Moodle, Canvas or Open edX open an external tool (a virtual lab, a proctoring service, a publisher's courseware, a plagiarism checker) inside a course, pass who the user is and what role they have, and receive grades back. The learner never sees a second login.

LTI 1.3 replaced the earlier versions' OAuth 1.0a signatures with modern security. A launch starts with an OpenID Connect third-party initiated login, and the platform then sends a signed JSON Web Token (the id_token) that the tool verifies with the platform's published public keys. The token carries claims such as the deployment ID, the message type, the LTI version and the user's roles.

LTI Advantage is the set of services built on 1.3:

  • Deep Linking: a teacher picks content inside the tool and the platform stores a link to exactly that item.
  • Assignment and Grade Services: the tool creates gradebook columns and posts scores back.
  • Names and Role Provisioning Services: the tool fetches the course roster so it can show class lists or group work.

The older versions are finished. 1EdTech stopped certifying LTI 1.0, 1.1, 1.2 and 2.0 after June 2021 and ended all support for them on 30 June 2022, because OAuth 1.0a is deprecated across its specifications. Major platforms have since been retiring LTI 1.1 connections. If you still run 1.1 tools, treat moving them to 1.3 as security work, not an optional upgrade. LTI also pairs naturally with single sign-on; our guide to SAML vs OIDC for LMS single sign-on explains how the identity side fits together.

QTI, Common Cartridge and OneRoster: moving questions, courses and classes

These three 1EdTech standards matter most when you change platforms or connect an LMS to school and university systems.

QTI for questions and tests

QTI (Question and Test Interoperability) describes items, sections and tests in XML so a question bank can move between systems. QTI 3.0 reached Final Release in May 2022. It reworked accessibility support, aligned the content model with HTML5 and ARIA, and is not backward compatible with QTI 2.x. In practice many LMS import tools still expect QTI 1.2 or 2.1, so test an export from your source system on the target before a migration plan relies on it.

Common Cartridge for whole courses

Common Cartridge packages a course's content, assessments and tool links into one file. Version 1.3 is the one most platforms import. Version 1.4, which 1EdTech lists at Candidate Final, adds QTI 3.0 assessments and LTI Advantage links, and includes Thin Common Cartridge, which carries only a manifest of LTI links so publishers can update content without shipping a new package. Common Cartridge is a useful starting point in an LMS migration, but it rarely carries learner data, so plan learner history separately. Our LMS migration guide covers that side.

OneRoster for rosters and grades

OneRoster exchanges users, classes, enrolments and results between a student information system and learning tools. OneRoster 1.2, released in October 2022, added user management, demographic data, preferred names, standards-based and competency-based grades, and support for sending results back to one gradebook of record. It is the standard to ask about when a school or university wants its SIS to drive LMS enrolments.

Caliper and Open Badges: analytics and credentials

Caliper Analytics is 1EdTech's model for describing learning events, such as a page viewed or an assessment submitted, as JSON-LD events grouped into metric profiles. It overlaps with xAPI in purpose. Caliper is more prescriptive and common in higher education tool ecosystems, while xAPI is more flexible and common in corporate and defence training. Many organisations never need to choose, because their platform exposes only one of them.

Open Badges describes a credential (a badge or certificate) so it can be verified outside the system that issued it. Open Badges 3.0, released on 29 May 2024, rebuilt the standard on the W3C Verifiable Credentials model, which makes badges harder to forge and easier to carry in digital wallets. It was developed alongside Comprehensive Learner Record 2.0. When an LMS says it issues "badges", ask whether they are Open Badges, which version, and whether a third party can verify them without logging in.

How to choose: standards by scenario

Most teams do not need every standard. Start from the jobs your platform must do and pick the standard designed for each one.

If you need toUseWatch out for
Import courses from authoring tools or content vendorsSCORM 1.2 or 2004Partial SCORM 2004 support, bookmark limits in 1.2, cross-domain hosting
Track simulations, apps, offline or on-the-job learningxAPI with an LRS and an agreed profileInconsistent verbs, an "xAPI support" claim that is only a completion flag
Launch modern packaged content from your LMS with reliable completioncmi5Uneven LMS support; test with a real package
Add an external tool (lab, proctoring, plagiarism, publisher content)LTI 1.3 with Advantage servicesTools still on LTI 1.1, missing grade passback or deep linking
Move a question bank between systemsQTI (check which version the target imports)QTI 3.0 is not backward compatible with 2.x
Move a course between platformsCommon Cartridge, then rebuild what does not mapLearner history does not travel in a cartridge
Let a student information system drive enrolments and gradesOneRoster 1.2CSV and REST implementations differ; confirm which one each side supports
Issue certificates others can verifyOpen Badges 3.0"Badges" that are only images on a profile page

A worked example: one platform, five standards

Here is how the standards combine in a typical mid-sized company that trains its own staff and some partner organisations. The details are illustrative, but the pattern is common in projects we deliver.

  1. Content in: the instructional design team builds courses in an authoring tool and exports SCORM 1.2 for short compliance modules and cmi5 for longer, mobile-friendly programmes. The LMS imports both.
  2. Tools in: a proctoring service and a virtual lab are added as LTI 1.3 tools. Deep Linking lets course authors place a specific lab exercise in a lesson, and Assignment and Grade Services send the lab score to the LMS gradebook.
  3. Data out: cmi5 statements and xAPI statements from a sales-practice app land in one LRS. The analytics team reports on both sources together because they agreed a profile first.
  4. People in: users and groups come from the HR system and the identity provider rather than from an eLearning standard, using SCIM provisioning and SAML or OpenID Connect sign-in.
  5. Proof out: learners who finish a certification path receive an Open Badges 3.0 credential that customers and auditors can verify without an account.

Notice what is missing. Nobody chose a single "best" standard. Each part of the platform uses the standard designed for that job, and the integration work is in making them agree on identifiers: the same user ID in the LMS, the LRS and the badge, and the same activity IDs across content versions. Getting identifiers right at the start is far cheaper than reconciling them after a year of data.

When you assess a platform or tool, turn every standards claim into a test: upload your own SCORM 2004 package and check sequencing, launch a cmi5 course and read the statements in the LRS, register an LTI 1.3 tool and confirm grades come back. Our LMS features checklist includes the demo tests for these standards alongside the other features buyers ask about.

Common mistakes with eLearning standards

  • Treating standards as interchangeable. LTI does not replace SCORM, and xAPI does not replace LTI. They solve different problems and often run side by side.
  • Accepting a logo instead of a version. "SCORM compliant" without a version, or "supports xAPI" without saying whether an LRS is included, is not an answer.
  • Collecting xAPI without a vocabulary. Agree verbs, activity IDs and a profile before content teams start sending statements, or the data cannot be combined later.
  • Leaving LTI 1.1 tools in place. Legacy LTI lost all 1EdTech support in 2022 and relies on deprecated signing. Move tools to LTI 1.3.
  • Assuming a migration format carries learners. Common Cartridge and QTI move content. Grades, attempts and certificates need their own migration plan.
  • Testing only in the authoring tool's preview. Always test packages in the target LMS, with the browser and devices your learners use.

How we can help

Standards problems usually show up as missing completions, lost bookmarks, tools that will not launch or data that cannot be reported on. We fix SCORM and cmi5 tracking, connect LTI 1.3 tools and learning record stores, and build integrations between learning platforms and student or HR systems. See our LMS integration services, or tell us what you are trying to connect and we will suggest the simplest standard-based route.

Frequently asked questions

What are the main eLearning standards?

SCORM for packaged courses, xAPI for detailed activity data, cmi5 for launching xAPI content from an LMS, LTI 1.3 for external tools, QTI for questions, Common Cartridge for whole courses, OneRoster for rosters and grades, and Open Badges for verifiable credentials.

Is SCORM outdated?

SCORM is old but not obsolete. Almost every LMS and authoring tool supports it, so it remains the safest format for packaged courses. Its limits are browser-only tracking, a small data model and weak offline support, which is where xAPI and cmi5 help.

What is the difference between xAPI and LTI?

xAPI records what a learner did and stores it in a learning record store. LTI launches an external tool inside a platform and passes identity, roles and grades. A platform can use both at once, for example launching a lab over LTI that also sends xAPI statements.

Does Moodle support xAPI and cmi5?

Moodle's core xAPI subsystem lets H5P activities report results, but Moodle's documentation says it is not a learning record store. Moodle has no cmi5 support in core, so cmi5 needs a third-party plugin or an external player.

Which version of LTI should I use?

LTI 1.3 with the LTI Advantage services. 1EdTech ended support for LTI 1.0, 1.1, 1.2 and 2.0 in June 2022 because they rely on OAuth 1.0a, which it has deprecated.

Free 30-minute consultation

Not sure where to start? Talk to an LMS engineer.

Tell us what platform you run and what you need. You’ll get honest, practical advice - even if the answer is that you don’t need us.

Sources & references

  1. SCORM - ADL Initiative
  2. SCORM Run-Time Reference - Rustici Software
  3. xAPI Officially Becomes a Published IEEE Standard - ADL Initiative
  4. cmi5 specification (current) - ADL cmi5 working group
  5. LTI security announcement and deprecation schedule - 1EdTech
  6. Finally Final: the QTI 3.0 release - 1EdTech
  7. Common Cartridge - 1EdTech
  8. New Open Badges 3.0 standard provides enhanced security and mobility - 1EdTech

Before you go - get a free LMS audit

Tell us which LMS you use and what is not working. An engineer replies within one business day.

Choose which optional cookies we may use. You can change this at any time from "Cookie preferences" in the footer. Cookie policy · Privacy policy