- Get Started
- Write Code
The recipes page for developers gives a great overview of what recipes are. Put simply, recipes describe what Tin Can statements are recorded for a particular type of experience. Learning designers need to know which recipes exist and what they track so that they can design learning experiences and statements to follow the recipe.
It’s really important that we all follow the same recipe when tracking the same type of experience so that 3rd party systems, such as reports, know how to handle the data. If different applications record on the same types experiences in different ways, we’d have to create custom reports for each application, defeating the point of using an interoperability specification like Tin Can. The recipes page for developers gives an example of how this can go wrong. Recipes are the solution to that problem.
This page is a high level overview of recipes that exist today. For types of learning experiences that don’t have recipes, we’d love to help you create one. Contact us.
The attendance recipe defines the statements issued for people attending an event. This can be any kind of event such as meetings, classes, conferences etc. The recipe comes in two flavors: simple and detailed. The simple recipe simply tracks that a group of people attended an event. The detailed recipe additionally tracks the following experiences:
The bookmarklet recipe defines statements that can be sent by tools that bookmark the learner’s activity on the internet. It covers the following experiences:
The checklist recipe defines statements relating to checklists for performance observation, for example, a manager assessing an employee against a set of competencies. In this recipe, the person being observed is always the actor and the observer is the instructor. The recipe tracks these experiences:
Open Badges are digital credentials awarded for achievement, engagement or improvement. The Open Badges recipe defines the statement to be sent when the learner earns an Open Badge.
There are a collection of recipes describing the statements issued by the Tin Can prototypes. These include a content launcher, a traditional e-learning course, a game of Tetris and a location based mobile game. These recipes and prototypes can be followed by real applications following a similar pattern. Together these recipes describe the following events:
The video recipe describes statements used to convey a learner’s interactions with videos. It covers the following experiences:
This page is an overview of available recipes. You can read more about recipes and how to implement them on the recipes page for developers.
We love to help people implement existing recipes and create new ones.