Now that Tin Can is out, I bet you're ready to see some statements in your LRS. We are too! We just added functionality to SCORM Cloud that generates Tin Can statements from SCORM registrations delivered via SCORM Cloud. Pretty cool huh? Here's the skinny:

• Deliver your SCORM content via SCORM Cloud as you do today (invites, Dispatch, API launches etc)
• SCORM date (completion, time, score, etc) is available via Reportage or API calls- just like it is today
• Tin Can statements are also generated and sent to the LRS associated with the app for the registration. So, if you sent an invite from your SCORM Cloud app, then you'll want to check out the LRS for your SCORM Cloud app to see that statement. 

To see your statements follow the steps below

1. Go to the Apps tab on the left menu
2. Select the Tin Can Statement Viewer link from the middle of the page (in the Project Tin Can banner)
3. Select the app you want to view
4. Voila- All of your statements are there- both Tin Can and SCORM generated statements.

We are pleased to announce that the latest version of SCORM Driver now supports Tin Can API Version 1.0!What does this mean?

• You can use your content to generate Tin Can statements that get stored in a Learning Record Store (this can be general e-learning content, or content that’s already been SCORM-ified.)
• Your content can live outside of an LMS and report Tin Can statements to a Learning Record Store (this opens up a LOT of new possibilities for e-learning!)
• You can now use SCORM Engine to host your SCORM courses, and deliver Tin Can statements to any LRS. Remain in control of your content.

If you are a current SCORM Driver customer, contact us about getting the latest version of SCORM Driver that lets you add Tin Can support to your content.

If you want to learn more about SCORM Driver drop us a note at info@scorm.com

As part of the Tin Can API, you define your own activities, activity types, verbs, extensions and attachments as part of statements. All of these require identifiers that should resolve to a URL that provides all of the spec-required metadata for each. There should be a a place where everyone in the community can find identifiers that have already been defined. It creates problems if there are many different identifiers for a verb, activity, attachment or extension that mean the exact same thing. This makes Tin Can data very hard to work with. Data normalization is hard, and we all need to use a registry in order to work with Tin Can data well.

Learn more here- http://tincanapi.com/registry/

Tin Can 1.0 is here and available in SCORM Cloud!

What is the Tin Can API?

The Tin Can API is an evolution of SCORM, a previous standard managed by ADL. Tin Can allows experiences of all kinds to be tracked using statements of a simple <subject> <verb> <object> form (e.g., “I did this”) that are then stored in a well-specified learning record store (LRS). Records of these learning activities are no longer confined to a single learning management system (LMS). Reporting systems can be granted access to all of the statements and can report against any combination of actors, verbs, and objects that they choose.

How does it work with SCORM Cloud?

In conjunction with the release of the open Tin Can standard, all of Rustici Software’s products fully support the 1.0 specification, as well as offering backward compatibility with the beta versions of the API. With SCORM Cloud you can now:

• Import, deliver and track Tin Can 1.0 activities- just like you do with your SCORM and AICC content

• Receive Tin Can 1.0 statements in your hosted LRS available in your SCORM Cloud account

• Backward compatibility to handle .90 and .95 statement, while also converting them to 1.0 statements