-
Notifications
You must be signed in to change notification settings - Fork 11
Experience API (xAPI) Statements
The default analysis expects to receive the data as Experience API (xAPI) traces, so called, statements. xAPI statements represent learning activities and have three main fields:
- Actor: who performed the action.
- Verb: the action performed.
- Object: the target on which the action is performed.
The statements can also have additional fields such as the result of the activity (including score, if the activity was successful or not) or the timestamp.
For instance, Figure 1 depicts an xAPI statement representing that the example learner (actor) has answered (verb) the example activity (object) with successful result and score 80.
Figure 1: Example of Experience API (xAPI) statement.
Specifically for educational or serious games, a Experience API Serious Games (xAPI-SG) Profile has been developed. The complete profile can be accessed at: xAPI-SG Profile. Further details about the xAPI-SG Profile can be found in this article: Applying standards to systematize learning analytics in serious games.
Some of the most common events that can be traced are summarized on Figure 2, retrieved from the article Integrating learning analytics into a game authoring tool.
Figure 2: summary of some events that can be traced using the trackers, their causes and xAPI fields.
- Home
- Game developers Guide
- Analytics developers Guide
- Analytics users Guide
- System Overview
- Tracker
- A2
- Analytics Real-time
- Analytics Front-end
- Analytics Back-end
- Game Storage Server
- Upgrading RAGE Analytics
- Wiki Style Guide