Update: The Output of Project Tin Can is Experience API.
Distribution of Content/Cross Domain
A drawback of traditional e-learning specs has always been the ability to host content outside of the LMS. There are some workarounds, but none of them solve the problem as well as the Tin Can API does.
The nature of the Tin Can API means that the activity lives outside of the LRS. This opens up a lot of new possiblities and business cases:
- There’s no need to import courses into LMSs anymore.
- Content creators (activity providers) have complete control over their content.
- When an activity is updated (i.e. fixed a typo, reworded a question), there’s no need to send those updates to every LMS that has your content.
- If someone is paying for access to your activity, you control how much access they have to it. Turn off access when a customer is over their limit or stops paying the bills.
- Activities don’t have to all be stored in the same repository. An activity provider can pull bits of content from disparate places.
- An activity doesn’t even have to be “content,” it can be any learning event, even one of those good ole fashioned classroom thingies.
What are your thoughts about this solution to content distribution and the cross-domain scripting limitation? If you have comments or want to shape the way that we handle this feature in the future, leave your comments below.
| <- Previous | Next -> |
| Removal of the need for a browser | Access to more data (run time data) |