"The Dude abides. I don't know about you, but I take comfort in that. It's good knowin' he's out there, the Dude, takin' her easy for all us sinners. Shoosh."
It's good to see that you're going public with your plans for and knowledge about SCORM, Ernie. These are important (and complex) matters that we'll want to get right - with a little help from our friends; the TAB, the UAB, and the community at large. And they're exciting matters, too. Standardized handling and sharing of content is really cool. Looking forward to helping you out in any way we can, dude.
What specifically is it we all want to see here? A new SCORM package? Or a complete rewrite of File Storage so that it becomes a full-fledged front end to CR, handling the "SCORM Repository" (storing, importing, and exporting) plus other content? This issue now appears to be part of the (not quite so radical) revamp of File Storage that Carl has called for. Don has suggested that File Storage may have to be rewritten from scratch. What gives?
The upcoming OpenACS4.x/dotLRN Curriculum package will eventually fit into this picture by providing sequencing - the engine plus the setting up of the tree of activities with their particular metadata (what could be called "course management" if that term wasn't already used for the file storage of SCORM content). The UI for this latter sequence (or curriculum or course) design part will benefit from the valuable input of über course designer Michael Feldstein, we hope.
"Welp, that about does her, wraps her all up."
