1. UWE Bristol First steps with XAPI Presentation by Name : Matt Cownie, Jonathan Wright Title : Manager, Learning and Educational Technologies

2. Minimal Background Rustici were commissioned by ADL to work on the next generation of SCORM standard. The aspect they worked was originally called the Tin Can Api and rustici have a site http://tincanapi.com that has lots of useful supporting information. Since competing the project ADL have taken ownership and renamed it to XAPI, the project site is here http://www.adlnet.gov/tla/experience-api. http://tincanapi.com http://www.adlnet.gov/tla/experience-api Currently, using the search terms “Tin Can API” can be more productive in discovering articles and implementation related details than “XAPI”. This should change as XAPI becomes a generally accepted moniker. Can make things a little confusing. As does the legacy of SCORM. Key point : XAPI is all about tracking (and sharing) what a learner has done, its not about moving e-learning content between systems (content brokering).

3. XAPI - Everything’s a Statement Actor, Verb, Object Leaner, Completed, Virtual Patient

4. Some Key Concepts (for VP’s) Actorthe learner Activity (13)http://adlnet.gov/expapi/activities/ e.g. performance, question, simulation, etc Statementlearning event - an activity has happened Verb (25) http://www.adlnet.gov/expapi/verbs/ e.g. answered, asked, attempted, etc UUIDUnique ID for an actor, statement or registration e.g. virtual patient ID (we used GUID’s for prototype) URInew Activity("http://uchoose.uwe.ac.uk/" + vpID ) contextActivitiesgroup related ‘stuff’ together e.g. Activities related to a VP Extensionadditional granularity of an activity or statement Registrationsession

5. Step 1- code first statement = actor + canned verb +activity Standard Activity Type

6. XAPI - Public LRS http://tincanapi.com/public-lrs/ generated this statement in the LRS filter by Learner

7. statement = actor + activity + canned verb JSON is transport layer

8. XAPI - Activity Streams An Actor (learner) playing a virtual patient (an activity) generates a series of events (more activities) which produces an activity stream. XAPI uses statements to record these events to the Learning Record System. However an activity stream can contain a whole slew of events, learning or otherwise (e.g. BB social). In order to analyze and report on the activities related to a particular virtual patient case the statements need tagging so that they can be grouped together in meaningful ways. Firstly - we need to add context to each statement. Individual Statements can be linked together using a Registation UUID which is “An instance of a learner undertaking a particular learning activity.”

9. Step 2 - lets do it again how do i differentiate between attempts? AKA Session Add Session ID filter by Learner

10. Session ID filter by Session ID

11. Step 3 - start thinking What does it mean to ‘play’ a Virtual Patient? (can get fuzzy) Stream of specific activities we might want to track VP activitytrack with?XAPI feature starting a casestartedstandard verb changes to counter valuesEXTENSIONNOT score MCQcmi.interactionfrom SCORM node visits (navigation events)experienced?standard verb watching multimediaexperiencedstandard verb rules firing (probably not?)EXTENSION completing a casecompletedstandard verb data Item requestsasked? time spent in each nodeduration or EXTENSIONattribute of a Result, which is an attribute of a Statement “The Score Object SHOULD NOT be used for scores relating to progress or completion.”

12. XAPI - Extension (Anchors) Counter + Value Anchor used for namespace mechanism Counter + Value Deliberate Mistake?

13. XAPI - Activity Streams again grouping statements together by session (and sorting by timestamp) is very simplistic. To be able to generate sophisticated reporting we need to export some meaning to LRS.

14. XAPI - ContextActivities XAPI provides four possibilities - ‘parent’, ‘grouping’, ‘category’, and ‘other’ Parent - model the Virtual Patient as parent activity and set that as the context for all subsequent related activities. Further granularity would be a video and MCQ with a node as parent activity. Grouping - might want to group an activity within the VP with related activities in same VP or other VPs Category - “Category SHOULD be used to indicate a "profile" of xAPI behaviors” - e.g. PhysicalExam, Medication? Other - none of the above, perhaps supporting learning material or making a branching decision?

15. XAPI Profile for VP’s? A profile is a mechanism for a community of practice to create and share a common data model when the default definitions are insufficient to meet their needs. e.g. a Public Registry to promote community sharing e.g. the Virtual Patient community the profile would be common for all VP’s reuse ADL predefined verbs or agree on VP specific ones? reuse ADL Simulation activity or define set of VP related activities?

16. Our Questions 1.Virtual Patient Profile (common for all VP’s) ? 2.Different VP design may require different levels of tracking granularity or should ‘everything’ be tracked and granularity be applied when reporting? 3.could branching points or critical decision points be their own activity type? 4.track rules? 5.anchors - need best practice guidance 6.context activities - best practice for tagging 7.URI’s ? http://uchoose.uwe.ac.uk/Player/Journey/BeginJourney?labyrinthId=388 Unique per domain. Would a single registry of public shared cases be something to aspire to? (content brokering)

17. Next Steps populate an LRS and prototype some reports against the data - can we generate meaningful analysis of what it means to play a virtual patient from data written to the LRS?