From the course: xAPI Foundations
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
The Result element
- [Instructor] The Result element is used to convey the results of the action taken. I did this and I passed. I took a quiz and I failed, etcetera. The Result element itself is purely optional. It is not required for an xAPI statement. Mostly, because it does not always make sense that an activity would have a reportable result. Similarly none of the properties within the element are individually required, they're each optional. The values for many of the properties map very closely to those in SCORM with which you may already be familiar and, if not, that's okay, they're pretty straightforward and logical. Also, when it makes sense, you can include the user selection in the result and we'll look at an example of that in this lesson. So, let's take a look at an example. Here's an example of a Result element you might get from a statement where the user took a quiz. We see the completion status if the user passed or not and his or her score all listed. Let's look at each of these…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
Building a statement: "I Did This"2m 56s
-
(Locked)
xAPI unique identifiers1m 32s
-
(Locked)
The Actor element4m 6s
-
(Locked)
The Verb element3m 36s
-
(Locked)
Where do xAPI Verbs come from?3m 14s
-
(Locked)
The Object element3m 25s
-
(Locked)
The Result element3m 35s
-
(Locked)
The Context element3m 2s
-
(Locked)
Using extensions3m
-
(Locked)
The Timestamp element2m 28s
-
-
-
-