2. xAPI Against Humanity

3. Let’s play! xAPI Against Humanity Scan the QR code.
Log in and join a room
Play 5 rounds. Vote in each.

4. What’s going on? xAPI Against Humanity
The entire game is supported by xAPI statements.
The LRS is being used as a simple data base, the game is doing all the “work”

5. On start: What’s going on? xAPI Against Humanity
First person in sends xAPI statement to create the group, with ID
What’s
going on?
Next 3 people – checks to see if a group ID is open, added to that group
Fourth person in sends xAPI statement closing the group

6. On submit: What’s going on? xAPI Against Humanity
Send an xAPI statement representing the sentence, keep the statement ID (stID) to reference it later.
What’s
going on?
Send an xAPI statement representing that player P formed the statement referenced by stID. verb: "formed"
In the context include the activity ID of the game verb (the content page where we formed this sentence), and the registration ID

7. On voting: What’s going on? xAPI Against Humanity
Retrieve and display the statements with the verb "formed", which context includes the activity ID associated with the game verb. verb:"formed", activityid (associated with the game verb), registration id, related_activities:true
What’s
going on?
Send an xAPI statement representing that player P voted the statement referenced by the ID selected sentence. verb: "voted” In the context include the activity ID of the game verb, and the registration ID. 

8. After 5 rounds: What’s going on? xAPI Against Humanity
Retrieve all the votes submitted in the room, i.e. all the statements with verb "voted", which context includes the room registration ID. verb: "voted", registration ID, related_activities: true
What’s
going on?
Calculate
Display the sentences (display attribute on the statement object), with the number of votes (and optionally the player who submitted them).

9. xAPI Against Humanity
Cool things we learned

10. Super Cool Cool things we learned xAPI Against Humanity
You can use the LRS as a simple database
Cool things we learned
You can create content with behaviours that depend on how other users have consumed/interacted with it

11. Registration IDs Cool things we learned xAPI Against Humanity
An xAPI client can use multiple registration IDs each for a different purpose: 
In the game, each room is associated with a unique registration ID
All game activities use the registration ID of the room
All other xAPI statements use the main registration ID, if any.
Cool things we learned

12. Registration IDs Cool things we learned xAPI Against Humanity
More than one xAPI client can use the same registration ID
All players in the same room use the same registration ID for their game activities. 
To poll the room activities (all players in the room) we perform a statements query that looks for activities with that registration ID. 
Cool things we learned

13. Voiding Statements Cool things we learned xAPI Against Humanity
Voiding statements came in handy:
To close a game room, i.e. avoid more people joining it we simply void the statement that opened the room.
A statement can be voided by any xAPI client, even if the client that created the original statement is another one. 
Cool things we learned

14. https://github.com/dominknow/xAPIAH
xAPI Against Humanity
Want to geek out more?