SCORM Followup

Publish to SCORM, by Lectora

Just a bit of followup to my last post about SCORM which, surprisingly after my post about it on Sunday, I received instruction about it on Wednesday of this week. So there are a couple of things to clarify, although I’m sure I’ve forgotten some things already (since I don’t really ‘use’ my notebook).

If you’ve forgotten, SCORM is a technical standard for web-based e-learning. It slurps up all of your files in the e-learning software of your choice (Lectora, Articulate, etc) with the appropriate SCORM-specific variables (lesson status, lesson completed etc) and AUs and makes sure it will pretty much function as expected in the LMS.

While the story I was told may have been true, it seems that the defense force was the effort who strived to create this specification. SCORM doesn’t necessarily conform to web standards, nonetheless there is a push for WCAG (web accessiblity) from more organisations now.

The latest version of SCORM is SCORM 2004, but most organisations are still running on SCORM 1.2, which is the 3rd edition. The ‘new’ version of SCORM, however, is TinCan; a sudden diversion from the usual name and actually pictured as, you guessed it, a tin can. Not many people use it however, considering it is still largely unsupported. Kind of like how IE6 and HTML5 don’t mash well.

As an aside, interestingly it seems it is also common for e-learning software to push to HTML4. Perhaps because you can be sure this is supported, yet Javascript is used widely for interaction.

TinCan was developed by a private corporation of some sort, or the army apparently, since they have the money to do so. TinCan provides the ability to track user’s interaction in depth, and deposits this information into a spreadsheet for some reason. This doesn’t seem too practical to me, but works cross-platform and is simple I suppose, which works well for non-developers who want the simple solutions.