{ "title": "A Timeline of Learning Interoperability Standards", "subtitle": "From AICC (1988) to I2IDL (2026)", "events": [ { "id": "aicc-founded", "year": 1988, "headline": "AICC founded", "family": "AICC", "sponsor": "Aviation Industry CBT Committee", "short": "First cross-vendor CBT interoperability work.", "problem": "Airlines and simulator vendors could not share pilot training completion records across systems.", "successor_of": null, "succeeded_by": "AICC HACP", "description": "The Aviation Industry CBT Committee formed in 1988 to give airlines and simulator vendors a shared way to record pilot training across systems. AICC's working groups produced the AGRs — the Guidelines and Recommendations — that introduced the basic vocabulary (lesson_status, score, lesson_location) every later standard would inherit.", "spec_url": "https://en.wikipedia.org/wiki/Aviation_Industry_Computer-Based_Training_Committee" }, { "id": "aicc-hacp", "year": 1998, "headline": "AICC HACP", "family": "AICC", "sponsor": "Aviation Industry CBT Committee", "short": "First widely deployed course-to-LMS wire protocol.", "problem": "Courses needed a uniform way to send completion and score data back to a host system over the web.", "successor_of": "AICC AGRs", "succeeded_by": "SCORM 1.0", "description": "HACP — the HTTP-AICC Communication Protocol — is the first widely deployed wire protocol for course-to-LMS communication. It uses simple form-encoded HTTP POSTs to report lesson location, status, and score. HACP is gone from new deployments, but you'll still find it powering long-lived corporate LMSs in regulated industries.", "spec_url": "https://en.wikipedia.org/wiki/Aviation_Industry_Computer-Based_Training_Committee" }, { "id": "scorm-10", "year": 2000, "headline": "SCORM 1.0", "family": "ADL", "sponsor": "Advanced Distributed Learning (ADL)", "short": "ADL releases the first Sharable Content Object Reference Model.", "problem": "The U.S. Department of Defense needed a single reference model bundling AICC, IMS Content Packaging, and related work.", "successor_of": "AICC HACP", "succeeded_by": "SCORM 1.2", "description": "SCORM 1.0 was ADL's first attempt to bundle AICC's runtime ideas, IMS Content Packaging, and other concurrent efforts into a single reference model. The wire model was browser-locked from day one: a SCORM course is a ZIP delivered into an LMS iframe that talks to the host through a JavaScript API.", "spec_url": "https://adlnet.gov/projects/scorm/" }, { "id": "scorm-12", "year": 2001, "headline": "SCORM 1.2", "family": "ADL", "sponsor": "Advanced Distributed Learning (ADL)", "short": "The release that actually saw mass adoption.", "problem": "SCORM 1.0 was promising but immature; vendors needed a stable target.", "successor_of": "SCORM 1.0", "succeeded_by": "SCORM 2004", "description": "SCORM 1.2 became the version that everyone actually shipped. To this day, when a vendor says 'SCORM' without a version number, they almost always mean 1.2. The tradeoff: a shallow data model with about two dozen CMI elements and one implicit verb — completed.", "spec_url": "https://adlnet.gov/projects/scorm/" }, { "id": "scorm-2004", "year": 2004, "headline": "SCORM 2004", "family": "ADL", "sponsor": "Advanced Distributed Learning (ADL)", "short": "Adds sequencing/navigation; the most capable SCORM version.", "problem": "SCORM 1.2 could not express prerequisites, branching, or rich interaction types.", "successor_of": "SCORM 1.2", "succeeded_by": "xAPI 1.0", "description": "SCORM 2004 added a sophisticated sequencing-and-navigation model borrowed from IMS Simple Sequencing, expanded the data model, and tightened conformance. By every technical measure it was the better standard — and by every commercial measure many vendors kept shipping 1.2 because 'boring works.' The lesson xAPI's designers took to heart: elegance can lose to reliability.", "spec_url": "https://adlnet.gov/projects/scorm/" }, { "id": "ims-lti-10", "year": 2010, "headline": "IMS LTI 1.0", "family": "IMS", "sponsor": "IMS Global (now 1EdTech)", "short": "Learning Tools Interoperability launches; LMS-to-tool launch + roster.", "problem": "An LMS needed a standard way to hand a learner off to an external tool with identity and role pre-attached.", "successor_of": null, "succeeded_by": "LTI Advantage", "description": "LTI 1.0 solved a problem distinct from SCORM and AICC: not analytics, but launch and identity. A learner clicks a link inside Canvas, Moodle, Blackboard, or Brightspace and lands in an external tool already authenticated, with role attached. LTI 1.0 used OAuth 1.0a-signed POSTs.", "spec_url": "https://www.imsglobal.org/activity/learning-tools-interoperability" }, { "id": "project-tin-can", "year": 2012, "headline": "Project Tin Can", "family": "ADL", "sponsor": "ADL + Rustici Software", "short": "Rustici/ADL design phase for the SCORM successor.", "problem": "SCORM was browser-locked, LMS-locked, and could only really say 'completed.'", "successor_of": "SCORM 2004", "succeeded_by": "xAPI 1.0", "description": "ADL funded Rustici Software to interview practitioners and run a public design process for what came after SCORM. The project's working name — Tin Can — was a nod to the children's tin-can telephone: two cans on a string, sending learning data back and forth. The friendly 'Tin Can API' label survives in vendor marketing copy to this day.", "spec_url": "https://xapi.com/history/" }, { "id": "xapi-10", "year": 2013, "headline": "xAPI 1.0", "family": "ADL", "sponsor": "Advanced Distributed Learning (ADL)", "short": "Experience API published.", "problem": "Learning happens off-LMS, off-browser, and at much finer grain than 'completed.'", "successor_of": "SCORM 2004", "succeeded_by": "IEEE 9274.1.1", "description": "xAPI 1.0 generalized SCORM's completion/score paradigm into an Actor / Verb / Object statement model that can describe any learning experience — online or offline, on any device, against any service. This is the standard the rest of this book targets.", "spec_url": "https://github.com/adlnet/xAPI-Spec" }, { "id": "ims-caliper-10", "year": 2014, "headline": "IMS Caliper 1.0", "family": "IMS", "sponsor": "IMS Global (now 1EdTech)", "short": "IMS Global publishes a competing learning-analytics standard.", "problem": "Higher-ed institutions wanted comparable analytics across LMSs with a more constrained vocabulary than xAPI.", "successor_of": null, "succeeded_by": "IMS Caliper 1.2", "description": "Caliper is IMS Global's answer to xAPI: an open standard for emitting structured learning events. The conceptual model rhymes with xAPI's, but Caliper is more prescriptive — a small fixed set of canonical event types and a tightly constrained vocabulary, on the theory that constraint produces comparable analytics across institutions.", "spec_url": "https://www.imsglobal.org/activity/caliper" }, { "id": "cmi5-10", "year": 2016, "headline": "CMI5 1.0", "family": "ADL", "sponsor": "Advanced Distributed Learning (ADL)", "short": "An xAPI profile for LMS-launchable courses.", "problem": "LMSs wanted SCORM-like launch semantics but with rich xAPI analytics in the session.", "successor_of": "SCORM 2004", "succeeded_by": null, "description": "CMI5 is a profile on top of xAPI. It does not invent a new wire protocol; it constrains how xAPI is used so an LMS can launch a course, supply credentials, track session lifecycle, and receive completion just like it always has — while the course emits rich xAPI statements for analytics. CMI5 is the diplomat between the SCORM world and the xAPI world.", "spec_url": "https://github.com/AICC/CMI-5_Spec_Current" }, { "id": "lti-advantage", "year": 2019, "headline": "LTI Advantage", "family": "IMS", "sponsor": "1EdTech (formerly IMS Global)", "short": "IMS LTI 1.3 + extensions: NRPS, AGS, Deep Linking.", "problem": "OAuth 1.0a was aging out and LMSs needed gradebook write-back, rosters, and resource picking.", "successor_of": "IMS LTI 1.0", "succeeded_by": null, "description": "LTI Advantage modernized the launch stack onto OpenID Connect and OAuth 2.0, then added formal services: Names and Role Provisioning (the roster), Assignment and Grade Services (gradebook write-back), and Deep Linking (lets an instructor pick a specific tool resource from inside the LMS). For an intelligent-textbook architecture, LTI is how the LMS hands the learner off; xAPI is how the textbook reports back.", "spec_url": "https://www.imsglobal.org/lti-advantage-overview" }, { "id": "ieee-9274-11", "year": 2023, "headline": "IEEE 9274.1.1", "family": "ADL", "sponsor": "IEEE Learning Technology Standards Committee", "short": "xAPI ratified as an IEEE standard (October 2023).", "problem": "xAPI was a community spec; institutions wanted a formal standards body's blessing.", "successor_of": "xAPI 1.0.3", "succeeded_by": null, "description": "IEEE 9274.1.1 graduates xAPI from a community specification into a formal IEEE standard, ratified in October 2023. The wire format is essentially xAPI 1.0.3; the change is governance. The IEEE LTSC now owns the published standard, while open-source assets eventually moved to I2IDL.", "spec_url": "https://standards.ieee.org/ieee/9274.1.1/7321/" }, { "id": "i2idl-founded", "year": 2025, "headline": "I2IDL founded", "family": "I2IDL", "sponsor": "Institute for Infrastructure and Interoperable Data in Learning", "short": "Independent nonprofit takes over open-source xAPI stewardship.", "problem": "Changes at ADL left the community uncertain about the future of the xAPI Profile Server, conformance test suites, and TLA reference implementations.", "successor_of": "ADL stewardship", "succeeded_by": null, "description": "I2IDL launched in December 2025 as an independent, non-governmental, non-profit organization based in Savage, Maryland. It maintains the open-source code, conformance test suites, profile server, and Total Learning Architecture reference implementations underlying xAPI and related standards. I2IDL is explicit that it is not itself a standards body — the IEEE LTSC continues to own the ratified standards.", "spec_url": "https://www.i2idl.org/" }, { "id": "i2idl-tsc", "year": 2026, "headline": "I2IDL TSC", "family": "I2IDL", "sponsor": "Institute for Infrastructure and Interoperable Data in Learning", "short": "Inaugural 25+ member TSC announced.", "problem": "Open-source stewardship needed a transparent technical governance body.", "successor_of": null, "succeeded_by": null, "description": "I2IDL announced its inaugural Technical Steering Committee on January 30, 2026. The 25+ members are drawn from ADL, Rustici Software, the CERT Division at the Software Engineering Institute, the University of Florida, and other industry, academic, and government voices. The TSC advises on conformance testing and open-source policy.", "spec_url": "https://www.i2idl.org/" } ] }