1. Experience API (xAPI) Introduction
01 June 2015
Jonathan Poltrack
Director of Operations Alexandria VA Co-Lab & Technical Team Co-Lead
Problem Solutions LLC SETA Support to the Advanced Distributed Learning (ADL) Initiative
5. 5
The Legacy Model
• Content Packages
imported into LMSs
• Content duplicated in each
system
• LMSs store the content,
control access and
manage learner data
Distributed Content
7. This Works…
• For single learner-based learning content
• For asynchronous learning
• When the content is browser-based
• When the content can be physically located
in the LMS (or on the LMS domain)
• For “small” data like scores,
complete/incomplete, pass/fail
• For the common self-paced learning use
cases
9. Learning in Today’s Environment
Personalized
and Brokered
Content
•Just-in-Time
•Just-for-You
Access From
Any Device
Learn From:
•Intelligent Tutors
•Mentors and
peers via social
networks
•Self-Discovery
Learn Using:
•Games
•Virtual Worlds
•Intelligent
content
10. 10
How do I get a complete picture of my learning data?
14. Learning Management System (LMS)
User Management
Course
Management
Run-Time
Player
Scheduling
Grade Book
Search
Delivery
Learning Records
Statistics
Repository
Sequencing
Preferences AssessmentReports
What Data?
Learning Management System (LMS)
15. Learning Management System (LMS)
Learning Records
What Data?
Learning Record Store (LRS)
Jon submitted homework
from GPS location (x,y)
Jon watched WWII video
Jon Passed History 101
Jon Answered ‘A’ on Question 1 Jon completed History 101 quiz
Jon turned control switch to
50%
16. 16
• Collaboration between Google, Facebook,
Microsoft and others
• Format: <Actor> <Verb> <Object> (I did this)
• I (actor) completed (verb) the IA course (object)
• Allows reporting of experiences, not just
completions
• Jon posted a photo
• Jon liked a photo
• Jon commented on a photo
Activity Streams
Giving a 30 second briefing on the xAPI is difficult.
It supports many more use cases than legacy technologies like the SCORM.
During conferences or webinars, in papers or websites and in conversation, xAPI is described in different ways to support different use cases. This word cloud was automatically created based on the xAPI information available on ADLNet.gov. It is interesting to examine the commonly used words:
Learning – In the past, SCORM and the work around SCORM, was highly technical. Although xAPI is a technical specification, ADL and the xAPI community are focused on how to improve learning, training and performance support first, using technology assist second.
Mobile, Simulations, Games, Social – Are new types of learning “content” used today. xAPI integrates with any learning activity with access to a network. In the past, this has been limited to single learner, web-based content
Analytics, Completion, Reporting - Are words that imply the use of data after it is stored. For example, xAPI data can be used in a gradebook applications, to create custom graphs of learning data for instructors or exported as records of completion for an HR system. Securily accessing data AFTER it is first stored was never interoperable in the past.
Learner, Mentor, Teacher, Actor, Agent, Individual – Show that we are no longer just talking about the learner. We are talking about any and all learning roles, student, teacher, mentor, peer, small and large groups, etc
The legacy model used by SCORM, AICC CMI 4/HACP and others includes the concept of a “course” or “content package” that is a physical file. This file is then “imported” into a learning management system (LMS). The LMS parses the course and is then able to “understand” how to launch, sequence, and track course activities. The LMS is a core component in this architecture as it MUST contain all courses/course files, learning records, users, etc.
In this model, content is duplicated in each system, so content lifecycle can be difficult to manage. For example, if you import a course in to LMSs A, B, C, and D above and later want to change some images in the course, you must perform this update four (4) times, once in each LMS.
This model is effective in DoD and Service environments, because the LMS can be located on a security network and is largely able to stand-alone.
Legacy model is similar to MP3s, MP3 players and the associated MP3 standard
The legacy model works (and it works well) for single-learner, web-based content, managed by an LMS.
What about new devices/content modalities?
Mobile apps (Android, Apple iOS, Windows, etc.)
Smart watches (Android Wear, Apple Watch, Pebble, etc.), AR Glasses (Google Glass, Vuzix, Moverio, etc.) and other wearables (Bio Monitors, Fitness Bands, etc.)
Simulations (LVC, Full-Scale, Desktop)
Games (Xbox, PlayStation, Steam, etc)
Social Media/Learning (Twitter, G+, LinkedIn, Yammer, etc)
Virtual Reality (Oculus Rift, Samsung Gear VR, Cardboard, etc)
Today’s learning environment is much more complicated and distributed than legacy environments:
- Must support mobile, AR, VR, games, virtual worlds, ITS
Allow syncing of data when connection exists, but works when a connection is not available
Is personalized to the individual
Is seamlessly accessible on multiple devices/platforms
What can you use to store and get access to all of this data…
SCORM is effective in describing how a learner’s active session with learning content passes learning data to an LMS. However, SCORM does not currently describe
Track data from any networked platform
Traditional PC
Tablet or mobile device
AR device
VR device
Games
Simulations
Sensors/Real world activities
Actual performance after training
Etc.
After data from learning experiences is stored, it can now be acted upon. This was a limitation of legacy systems. If an interface to an external system was needed, it had to be accomplished via expensive one-off (proprietary) projects.
Now with the xAPI, this is standardized. Any system that “understands” the xAPI can share data.
Examples include assessment systems, HR systems, gradebook applications, statistical and reporting systems, etc…