Update: The Output of Project Tin Can is Experience API.

next generation scorm evolution project tin can

Ready to really dive in?
View the full
Tin Can API spec.

View the Tin Can API
“quick start” guide.

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.

scorm tin can new way

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.

SCORM 2.0 next generation project tin can

Did we achieve what you wanted with this feature?

  • Miriam

    Great!!! from my point of view, this is the main issue in comparison with SCORM, and thae main weakness of SCORM.

  • Anonymous

    One limitation that should be noted of the current REST binding of the Tin Can API is that Internet Explorer does not allow authenticated cross-domain requests to be sent, and does not allow even unauthenticated cross-domain requests other than ‘GET’ or ‘POST’

    This is a limitation of the current binding. IE could be used with a SOAP binding, and we were already envisioning both a SOAP and a REST binding, we just did the REST binding first.

  • Gem

    The FAQ page states:
    “Simply upload a Tin Can course as you would a SCORM course and it will be treated the same way. More fully embracing Tin Can in your LMS requires a bit more work.”
    My question: Will plug-ins be created to interoperate “tincan.xml” into our existing software such as Captivate or Articulate in order to publish out into this new format or will the conversion process exclusively occur in-the-cloud?