EXPERIENCE API (XAPI) – PROJECT TIN CAN GOPALKRISHNA THAROOR – STC 2016 DISCLAIMER: “THIS CONTENT AND THE VIEWS HEREIN, ARE ONLY THAT OF THE SPEAKER, AND DOES NOT REPRESENT THE VIEWS OF THE ORGANIZATION THAT THE SPEAKER IS PART OF.” © 2016, STC INDIA CHAPTER

APPLICATION PROGRAMMING INTERFACE (API) API" stands for Application Programming Interface API is a standard that allows programs and software to speak with each other Helps to access a Web-based software application or Web tool Companies releases their API in public domain so that other developers can design products that are powered by its service A good, easy-to-use API attracts developers to create programs on your platform

PROFILE OF MODERN LEARNER

TIN CAN – ADVANCED DISTRIBUTED LEARNING (ADL) Tin Can API developed by ADL for mobile content learning platform Project name was Tin Can and now called Experience API or xAPI xAPI is considered to be next gen SCORM Helps to track and define how formal and informal eLearning sessions are tracked and measured by Learning Record Stores, or LMSs Training organizations need to track the amount of informal learning consumed to understand the needs of the learner

XAPI AND TRACKING xAPI was built to expand on that and learn even more about a user's learning behavior How many employees completed the mandatory annual compliance policy? How many employees are using the wiki to access and track operational procedures? xAPI helps organization track these instances People learn from interactions with other people, content, and beyond. These actions can happen anywhere and signal an event where learning could occur All of these can be recorded with the xAPI

XAPI SPECIFICATION xAPIs refer to a shared language for systems to communicate data about a person or a group's formal and informal learning activities The specification requires a Learning Record Store (LRS) to receive and distribute these statements To record an activity, the application sends secure statements in the form of “Noun, verb, object” or “I did this” to the LRS LRS record all of the statements made. An LRS can share these statements with other LRSs. An LRS can exist on its own, or inside an LMS Structure of the xAPI is open, statements and tracks any type of activity in any system Flexibility in type of data, helps track learning activities tied to performance indicating the real business value of learning or training initiatives

XAPI LEARNING RECORD STORE (LRS) LRS collects activity statements An LRS must accept any properly formatted data and share it with other LRSs upon proper request and authentication An LRS is defined as part of the xAPI specification Most of the hard logic for dealing with the data is put in the LRS instead of in the tools making the activity statements LRS is more complex to build than a typical database because it has to accept all the data that is received as part of a statement Source : https://www.trainingindustry.com/wiki/entries/experience-api-(tin-can-api).aspx

LEARNING ECOSYSTEM

SCORM & XAPI (TIN CAN) – COMPARISON Feature-wise xAPI scores over SCORM SCORM useful when learning happened from within office on a desktop xAPI scores as devices are multi- distributed and learning can happen from anywhere

FREEDOMS OF XAPI Statement freedom: the structure of “statements” using nouns, verbs and objects lets you record almost any activity. Examples: “I did this.” History freedom: the Tin Can API allows LRSs to talk to each other. LRSs can share data and transcripts with one another, and your experiences can follow you from one LRS (or organization) to another. Learners can even have their own “personal data lockers” with their personal learning information inside them. Device freedom: any enabled device can send Tin Can API statements (mobile phones, simulations, games, a CPR dummy) with occasional connectivity is fine. Workflow freedom: tracking learning events doesn’t have to start or end in an LMS, it can start wherever the learner is and on whatever device they choose to use. Your content isn’t tied to an LMS

TIN CAN TO XAPI – OVER THE YEARS xAPI EVOLUTION 2013 (v 1.0.1) A patch release, version 1.0.1 was released in October of 2013 Tin Can API version 1.0, launched in April of 2013. ADL’s official name for the Tin Can API is the Experience API, or xAPI. 2012 (Devlearn) DevLearn ’12 conference, version .95 of the Tin Can API was finalized and by the end of 2012, there were over 40 adopters of Tin Can. 2012 ADL and the spec community completed version .9 of the Tin Can API, and ADL announced it to the e-learning community. 15 companies/products had adopted the Tin Can API. 2010-11 Rustici Software looked at the LETSI SCORM 2.0 White Papers, and conducted extensive interviews with the e-learning industry. This Project Tin Can was the beginning of steps towards improving e-learning standards. 2010 Advanced Distributed Learning (ADL), the governing body for SCORM, issued a Broad Agency Announcement (BAA) to solidify the next-generation e-learning standard. Rustici Software was awarded the BAA, and work began. 2008 Noticeable limitations in SCORM forces Learning Education Training Systems Interoperability(LETSI) to seek ideas

BENEFITS OF XAPI Reference - https://tincanapi.com/wp-content/assets/webinar/webinar.html

Q&A THANKS FOR LISTENING