Update: The Output of Project Tin Can is Experience API.
Verb Variation
How do we set the standard for the verbs that are used in statements? Is a test completed or finished? Did John read chapter 1 or study chapter 1?
In the context of e-learning, completed and finished mean practically the same thing, but for reporting purposes, they’re completely different. With the Tin Can API, we’re able to group certain verbs that mean the same thing and assign different logical results for them.
We’ve created some to use, but we can’t think of every verb that will need to be used in every scenario.
Here is what we’ve come up with:
| Verb | Result |
| experienced, read, watched, studied, reviewed, learned | completion |
| attempted, performed, played, simulated, answered | completion, success, score, (interaction details) |
| completed, passed, failed | special |
| interacted | (interaction details) |
| achieved | completion, success, score, (interaction details) |
| attended | completion |
| taught (by), mentored (by) | completion |
| commented | comment |
| asked | question |
| created, authored, wrote, edited, blogged, shared, posted | completion, success, score |
Where do we go from here?
The verbs and results that we’ve put forward are the only ones that are usable right now. We’re aware that this list will grow when it needs to, and the long-term plan is for there to be a governing body that handles all verbs, verb variations, and their results.
Do you have any thoughts on how the Tin Can API should handle verb variation? Leave your comments and thoughts below.
| <- Previous | Next -> |
| Activity definition/agreement | Reporting complexity |