I’ve been working with xAPI since it was barely called xAPI, back when it was still “Tin Can” emerging from an ADL research project.
Over the years, I’ve implemented xAPI across multiple ecosystems: LMSs, bespoke platforms, simulations, assessment systems, and enterprise data stacks. In most cases, xAPI existed, but often only as completion noise. Data was captured, stored, and largely ignored.
That’s changing.
Not because xAPI suddenly became more popular, but because its position in the global standards ecosystem has fundamentally shifted.
And almost nobody is talking about it.
The Standards Journey xAPI Actually Took
xAPI didn’t appear inside ISO out of nowhere.
Its progression matters:
- ADL Research Specification
xAPI originated as Project Tin Can, funded by the Advanced Distributed Learning (ADL) Initiative to overcome SCORM’s limitations [adlnet.gov], [scorm.com] - Formal IEEE Standard
In 2023, xAPI was ratified as IEEE 9274.1.1-2023, formalising its data model and RESTful API for learner experience data tracking [standards.ieee.org], [ieeexplore.ieee.org] - Adopted into ISO/IEC
In 2025, that IEEE standard was adopted unchanged into the ISO/IEC catalogue as
ISO/IEC/IEEE 39274-1-1:2025 [standards.ieee.org], [iso.org]
That last step is the critical one.
Why ISO/IEC Adoption Changes the Conversation
ISO didn’t create xAPI, and that distinction matters.
ISO adopted an existing IEEE standard, recognising it as fit for inclusion in the global standards system used across engineering, data, software, safety, and governance disciplines.
This moves xAPI out of a learning‑technology niche.
It now sits alongside standards used in:
- enterprise integration
- data interoperability
- software architecture
- regulated environments
That shift changes how xAPI should be discussed.
xAPI Is No Longer “Just a Learning Standard“
Historically, xAPI has been framed as:
- a SCORM replacement
- an LMS feature
- a learner tracking mechanism
That framing is now incomplete.
With ISO/IEC alignment, xAPI is better understood as:
- a data standard
- an interoperability layer
- part of enterprise architecture
These are the same lenses applied to other ISO‑recognised data standards, not marketing language, but architectural roles.
From Platform Reports to Data Architecture
For decades, learning data has been platform‑bound:
- log into an LMS
- run a report
- export a spreadsheet
- defend it later
That isn’t a data strategy. It’s a system behaviour.
xAPI offered a different idea from the start: separate the data from the platform that generated it.
ISO/IEC adoption reinforces that principle.
Learning data can:
- live independently
- move between systems
- be governed centrally
- outlive any single platform
This is exactly how mature organisations treat other forms of enterprise data
Why This Matters in VET, RTOs, and Regulated Environments
In education and training contexts, particularly VET and RTOs, conversations often come back to:
- assessment evidence
- traceability
- audit defensibility
- system reliance risk
Saying “our LMS tracks this” is an increasingly weak position.
Being able to reference:
- an IEEE standard
- adopted into ISO/IEC
- with a defined data model and transport specification
…changes the posture of that discussion entirely [iso.org], [lrs.io]
It gives learning data a defensible standards footing, aligned with how other regulated data domains operate.
What This Looks Like in Practice
Instead of relying on:
- uploaded files
- opaque checklists
- inferred completion
Organisations can build:
- structured evidence records
- explicit links between activity and judgement
- auditable learning narratives
xAPI doesn’t solve governance, but it gives governance something solid to stand on.
Enterprise Environments Are Asking Different Questions Now
In corporate and enterprise contexts, this shift enables better questions:
- Why is learning data locked inside platforms?
- Where is our central experience data layer?
- How does learning connect to performance, safety, or capability?
Many organisations don’t yet have good answers, but the standards framework is now in place.
The Bigger Pattern
This isn’t about xAPI “winning”.
It’s about the wider movement away from:
- platform‑first thinking
- completion as success
- data trapped in tools
And toward:
- data as infrastructure
- evidence over activity
- systems that integrate rather than compete
Standards are what make that shift possible
A Quiet Signal Worth Paying Attention To
If you’re still treating learning data as something that inherently belongs to a system, now is probably the moment to rethink that assumption.
The industry isn’t shouting about this shift.
But ISO adoption is rarely noise.
It’s a signal.
Written with assistance from AI