Eventually someone in the e-learning field is going to get slapped with a lawsuit just like Target did. If that’s what it takes to wake people up, I’m hoping it’s sooner rather than later!
SCO stands for shareable content object. If a course is not built to be shareable, it isn’t really a SCO, even if it uses SCORM for packaging. Spinning SCORM’s communication element off into its own standard — without the name SCORM — would free SCORM to truly be a Shareable Content Object Reference Model, and would free non-aggregators from having to deal with the complexities of SCORM.
A common thread in many of the posts I’ve been reading is that standards do not lead to innovation, but rather that innovation leads to standardization.
As I’ve mentioned before, it really gets in my craw that the IMS positions itself as a big player in creating and maintaining e-learning standards, yet keeps their doors closed to the public. How can it be a standard if people can’t get to it? Sheesh.
Most e-learning developers don’t care about SCORM and only (begrudingly) learn enough to get the job done. I don’t blame them. This brings up the never-ending question when it comes to using SCORM in courseware: What are you really trying to do with SCORM?
Quote: There’s something fundamentally contradictory about open standards being developed behind closed doors.
The talented Cameron Moll has posted a link to a Web Accessibility Checklist prepared by Aaron Cannon, a (blind) member of his web development team.
Here’s a quick tutorial for adding basic SCORM functionality to an existing Flash file. This tutorial aims to demonstrate just how easy it can be to add SCORM functionality to an existing Flash movie.
Please note that this tutorial uses ActionScript 3 and SCORM 1.2, but the same principles apply for ActionScript 2 and SCORM 2004.
I’m currently working on a tutorial explaining how to add SCORM code to an ordinary Flash file. Here’s a teaser: a very simple Flash movie I made using some images from NASA. It’s called PLANETS!