Hi Matt,
Thanks for giving us a basic overview of the current SCORM implementation; this looks like it covers most basic course scenarios.
SCORM 1.2. is still very much the most dominant method for tracking and I feel the adapt project should be moving forward with this for the first release. But it looks like this has already been decided :)
Thinking about SCORM, even if we are not considering it in the core, I think we should think about ways in which we can extend the basic functions if possible, allowing “hooks” if you wish (not sure if this is the correct phrase). Essentially if a developer (bespoke) wants to push data to the suspend_data variable, he/she should be able to. Likewise retrieve this data. Just a thought as there is often the requirement to push data which needs to be saved for returning visitors.
AICC we see used very rarely, but as Sven said is something that can be looked at in the long run.
SCORM 2004, again I’ve personally only come across a handful of client’s who have adopted this. But I would certainly say this could be something that we should look at supporting next. If from what Matt has mentioned is possible then this might be a small story to add to the project at a later date just to limit its barrier to the market for some users.
Have people seen many organisations adopting TIN-CAN LMS functionality? Although there is lots of hype about this, prioritising it due to the buzz phrase might gain it good ground in the market place, but will it be used by many, could we maybe put the efforts elsewhere on the outset to support 2004, and AICC maybe, just a thought?
Alan