SCORM, which has been the de facto standard for publishing, launching, and tracking eLearning on learning management systems, is not properly equipped to manage non-traditional learning that is mobile and informal. Experience API, or xAPI, however, provides the eLearning community an interface that is able to collect and record details from any learning experience in one central location, regardless of where the learning takes place. With xAPI’s extreme potential to improve the way learning is captured and administered, it is vital for eLearning professionals to understand: - xAPI’s capabilities for managing mobile, non-traditional learning - SCORM’s place in the future of eLearning - Integration of xAPI into HTML5 for tracking user activity within currently-adopted LMS or LRS - Real world examples of xAPI implementation

1. Experience API (xAPI) and the Future of SCORM
Mr. Jason Haag
ADL Technical Team, Mobile Lead, Research Analyst
The Tolliver Group, Inc. ADL SETA Support

2. 2
“Provide access to the highest quality
education and training, tailored to individual
needs, delivered cost effectively, anywhere
and anytime.”
- ADL Vision

3. 3
‣ ADL Initiative was established in 1999 by
Presidential Executive Order 13111.
‣ The first two ADL Co-Labs opened in Alexandria, VA
and Orlando, FL that same year.
Advanced Distributed Learning

4. 4
ADL Global Reach
Canada ADL Partnership Lab
Kingston, ON, Canada
Norway ADL
Partnership Lab
Oslo, Norway
United Kingdom
ADL Partnership Lab
Buckinghamshire,
United Kingdom
Korea ADL
Partnership Lab
Seoul, Korea
Romania ADL
Partnership Lab
Bucharest, Romania
Latin America and Caribbean Regions
ADL Partnership Lab
Mexico City, Mexico
NATO ACT ADL
Partnership Lab
Norfolk, VA
ADL
Initiative
Orlando, FL
Academic ADL Co-Lab
Madison, WI
ADL Initiative
Alexandria, VA
ADL Center for Intelligent
Tutoring Systems Research
and Development
Memphis, TN
Poland ADL
Partnership Lab
Warsaw, Poland

5. Exploring the xAPI
‣ Background
‣ Introduction to xAPI & LRS
‣ Future of SCORM & Implications
‣ Use Cases & Examples
‣ Resources
Agenda

6. Background
Sharable Content Object Reference Model (SCORM)
‣ Created to support courseware interoperability and
reusability within Learning Management Systems (LMS)s
‣ Enables self-paced instruction in a browser only
‣ Works for desktop/laptop browsers (and will work in the
future), but we now have many more use cases to support

7. The SCORM Solution
7
‣ Content Packages
imported into LMSs
‣ Content duplicated in each
system
‣ LMSs store the content,
control access and
manage learner data
Distributed Content

8. Pardigm Shift Time!!

9. Today’s Opportunity: Learning Everywhere
Credit: Liz Burow (@Burlix)

10. What is the ?
• Result of LETSI SCORM 2.0 (2008)
• Result of Project Tin Can (BAA Research 2011)
• Tracks any learning experiences, informal
learning, real-world experiences (not just
completions)
• Allows data storage AND retrieval (ex. 3rd party
reporting and analytics tools)
• Developed by open source community

11. Top 5 Requirements
1. Should support a variety of content types
2. Should be simple to implement
3. Should support offline or disconnected scenarios
4. Portable content (interoperable across platforms)
5. Improved access to run-time data (both human and
machine readable)

12. 12
‣ Initially based on Activity Streams 1.0
specification developed Google, Facebook,
Microsoft and others (2.0 is new draft W3C spec)
‣ Format: <Actor> <Verb> <Object> (I did this)
• Jason (actor) completed (verb) the IA course (object)
‣ Allows reporting of activities & experiences, not
just completions
• Jason posted a photo
• Jason liked a photo
• Jason commented on a photo
Experience API (xAPI)

13. JSON (interchange format)
{
"actor": {
"mbox": "mailto:jason.haag.ctr@adlnet.gov",
"name": "Jason",
"objectType": "Agent"
},
"verb": {
"id": "http://adlnet.gov/expapi/verbs/skipped",
"display": {
"en-US": "skipped"
}
},
"object": {
"id": "http://adlnet.gov/expapi/activities/video",
"definition": {
"name": {
"en-US": "Misconduct in Clinical Trials"
},
"description": {
"en-US": "video on misconduct in clinical trials"
}

14. 14
Experience API (xAPI)
• Simple Statement:
Jason (actor) skipped (verb) a video on misconduct in clinical
trials (object)
• More Complex Statement (Context Activities):
in the context of [GCP Compliance Training Course], with result
[timestamp: 2015-0218T18:30:32.360Z ].

15. Learning Management System (LMS)
User Management
Course Management
Run-Time
Registration
Scheduling
Grade Book
Search
Delivery
Learning Records
Statistics
Repository
Sequencing
Preferences AssessmentReports
What is a LMS?
Learning Management System (LMS)

16. What is a LRS?
Learning Record Store (LRS)
Learning Record Store (LRS)
Learning Records

17. Reporting
Systems
Assessment
Services
Semantic
Analysis
Statistical
Services
17
Where Is The Data Stored?
LRS = Learning Record Store

18. 18
LRS Enables
‣ Graphs of learning data
‣ Learning analytics
‣ Instructor dashboards
‣ Gradebook applications
‣ Interfaces with HR (or other) systems
‣ Learning activity suggestions for review/
improvement
‣ And much more…

19. Experience
Tracking
(xAPI)
Learner
Profile
Content
Brokering
Competency
Networks
Comparing xAPI and the SCORM
Run Time
Environment (RTE)
Content
Aggregation
Model
(CAM)
Sequencing
&
Navigation
(S&N)
Training & Learning
Architecture (TLA)
Any Learning Activity"
On Any Platform
Web Browser-based
Instruction/Training

20. Comparing xAPI and the SCORM RTE
‣ Course tracking:
Bookmarking, completion,
time, pass/fail, scores
‣ Multiple scores per object,
unlimited test results and
interactions
‣ No LMS required

21. Comparing xAPI and the SCORM RTE
‣ No web browser required
‣ Supports offline scenarios
‣ Control over your content
‣ Tracks web or native apps
‣ Tracks serious games,
simulations, virtual worlds
‣ Tracks real-world, informal
learning & performance
‣ Tracks team-based learning

22. Future of SCORM
‣ No. xAPI can modernize the SCORM RTE, but doesn’t
replace the other aspects of SCORM
‣ Implication: It can easily work with SCORM. It does
not replace SCORM. New SCORM content developed
could use the xAPI for run-time tracking.
Does xAPI replace SCORM?

23. Future of SCORM
‣ No. SCORM is still useful for tracking and sharing
your web-based desktop courses.
‣ If your learners need mobile access, SCORM will not
work alone. SCORM will continue to work (durability)
in your LMS.
‣ Implication: Is your current investment in SCORM
producing good results? Are you able to accurately
measure your ROI with current LMS reports?
Does this mean all of the time and money
we invested in SCORM content will be worthless?

24. Future of SCORM
‣ Only if there is a requirement.
‣ xAPI isn’t a new version of SCORM.
‣ Need to support mobile delivery of your course?
Don’t convert. Think mobile first.
‣ Implication: Is there a need? You could easily make
your SCORM content support the xAPI. But determine
your needs. Is it for more robust reporting/analytics
or mobile? If so you will need to setup a a LRS and
also redesign your content user interface (if mobile).
Will we need to convert our training
content from SCORM to the xAPI?

25. Future of SCORM (Profile for xAPI)
Dual Tracking Strategy
http://adlnet.github.io/xAPI-SCORM-Profile
LRS Centric Strategy

26. 26
xAPI SCORM Profile
‣ Documents usage guidelines to generate
consistent and predictable Statements
‣ Contains mapping of SCORM data model
elements to xAPI
‣ Describes how to represent SCORM temporal
model in xAPI Statements
‣ Contains example Statements for typical SCORM
values

27. SCORM to xAPI Roadmap
27
SCORM
SCORM
+ xAPI
(LMS-
Centric)
SCORM
+ xAPI
(LRS-
Centric)
xAPI &
TLA
Defining a progression from SCORM to Experience API

28. Roadmap Status
28
‣ Roadmap Released in December 2014
‣ xAPI SCORM Profile Draft Released in December
2014
‣ Final release before August 2015
‣ Iterative recursive refinement based on community
feedback

29. Design Implications
Think Outside the LMS + Course Interface

30. Use Case (MOOCs)
Browser Bookmarklet (formal, informal, nonformal)

31. Use Case (Mobile Apps)
SMS Learning / notifications, Social, E-Books

32. Use Case (Games)
Gamification – BlackBerry Gamification
(OnPoint)
Game Details,
Progress & Options
Learner Status via 3
Different Leader Boards
Game List with
Progress Information

33. Use Case (Games)
Gamification – BlackBerry Gamification
(OnPoint)
Earned Badges &
Achievements
Integration to 3rd Party
Incentive Platform
Tracked Points in
Incentive Catalog
xAPI statements
sent to partner
system

34. Use Cases (Badges + Competence)
‣ CoPs integrating xAPI with Open Badges
‣ They see xAPI as complimenting Badges’ “evidence”
data (add standard meaning for objectives)
‣ Badges as indication of competency
‣ Mozilla Open Badges

35. xAPI CoP Directory
http://xapi.adlnet.gov/xapi-cop-directory/

36. Paradigm Shift
Integration with connected devices (IoT)

37. Use Case (Performance + Sensors)
‣ Procedural tasks (guided
response)
‣ Evaluation by instructor,
mentor may be required
for accurate assessment
‣ Mobile capture using
camera?
‣ Using sensors to report
xAPI Statements
‣ Potential feedback loop
Psychomotor Domain?
RFID + Arduino + ElectricImp + xAPI,
LRS

38. Android Wear (Gear Live)
Live action emergency/medical field scenarios

39. REAPER (Army / Riptide Software)
Data Mining Live Training Ranges

41. Radio Frequency Education RFED
Mobile + xAPI + RFID Tags

43. 43
Student Teacher
Student
Mentor Teacher
Practicum Professor
Literacy Experts
Lesson
Support
Learning
Outcomes
Work products:
Lesson Plan
Video of lesson
QuestionsCoaching/
Feedback

44. Adaptive Expertise (TREK)

45. PDF Annotator (RISC/Float)
RISC’s PDF Annotator

47. xAPI Resources
‣ All xAPI Resources:
http://xapi.adlnet.gov
‣ xAPI CoP Directory
http://xapi.adlnet.gov/xapi-cop-directory/
‣ SCORM Profile for xAPI
http://adlnet.github.io/xAPI-SCORM-Profile
‣ SCORM xAPI Wrapper
https://github.com/adlnet/SCORM-to-xAPI-Wrapper
‣ xAPI + Jquery Mobile: https://github.com/adlnet/xapi-jqm
‣ xAPI Design Cohort: http://www.adlnet.gov/xapi-design-cohort
‣ ADL Community Survey on SCORM & xAPI:
http://adlnet.gov/adl-community-survey

48. Thank You!
48
Jason Haag
Mobile Learning Lead
ADL Technical Team
The Tolliver Goup, Inc
jason.haag.ctr@adlnet.gov
Twitter: @mobilejson