The Output of Project Tin Can is Experience API (xAPI).
For the most current and up to date information about xAPI, please visit xAPI.com.
The information on this page documents the Project Tin Can research project and is available for archival/historical purposes only.
The Tin Can API brings forth a lot of new possibilities and changes that the e-learning community has been asking for. There are far too many new features to list here, so we narrowed it down here to the top requests. Click on each request to see a more detailed description and give your input/thoughts in the comments section for each.
- It needs to be simpler
- Removal of the need for an internet browser
- Distribution of content/cross domain
- Access to more data (run time data)
- Need to be able to use “user defined variables” in content
- Learning that’s not initiated in an LMS
- Simulations and serious games
- Track real-world activities, not just digital ones
- Need to track offline or long running content
- Platform transition (computer to mobile device, etc.)
- Better interoperability (several new benefits in this category)
- SCORM user interface requirements don’t achieve interoperability
- Instructors/others need to observe/interact during training
- Collaboration and team-based learning
- “I want to do my own sequencing”
- We need security/authentication
- Need to be able to “tag” content with skills (better organization)
While there are some major advantages with the Tin Can API, we’re aware that there are some weaknesses. Most of these weaknesses can be solved with collaboration and agreement among the e-learning community. Continue to the weaknesses page to see what we’ve identified so far.