The Experience API is a standard way of
talking about our experiences, using data.
The Experience API (xAPI)
• Can track many diﬀerent types of experiences — including things that
people do on the web, in mobile applications, with wearables, in
classrooms and in workplace environments
• Moves beyond a web-based, didactic model
• Promotes better design and technology practices
• Makes integration with other systems and practices easier
• Provides a way to gather and use more useful information.
It answers a lot of ‘How’ type questions…
• How can I inform better business decisions?
• How do I avoid locking us into a solution?
• How can I make investments in learning development last longer and
• How can I make sure what I evaluate today is useful in the future?
• How will I connect a learner’s activities across multiple applications?
How Does Experience API Work?
• People interact with “stuﬀ”
(i.e. content, apps, business systems, etc.)
• These interactions are observed and described in JSON.
• The “stuﬀ” sends the statements to a Learning Record Store.
What is a Learning Record Store, or LRS?
• It’s a database that stores activity statements - the “data”
• LRSs can be software (even hardware) that stands on its own.
• LRSs can be a part of data appliances, enterprise applications and
learning management system (LMS)
LMS vs. LRS
A Learning Record Store (LRS) addresses one capability of a typical
Learning Management System (LMS).
User Management Learning Records Scheduling
Course Management Statistics Grade Book
Tracking eLearning Content Storage Search
Assignments Sequencing Delivery
Preferences Reports Assessment
Someone Did Something
Activity Statements are “Observations”
Actor Verb Object
(To Someone) (Using Stuﬀ) (With Some Result)
"en-US": "HTML5 data attribute prototype"
"en-US": "Example generation of a passed activity using an HTML5 data attribute with unobtrusive js"