You know, I started with our runtimes using all the latest and greatest stuff but i find we have less problems and calls if we take more of the functionality internal. Not a surprise that the Easy Bake software we talked about usually produce a single sco pkg. It’s kind of like .eps files. Encapsulate postscript gave art the ability to have print instructions embedded in it so pagemaker, quark, etc could a) not worry about it and b) not screw them up. This was back in the days of quark 2 and 3. It just gave the printer more flexability in their preflight software. And reduced the corruption potential of the file.

Not sure if that’s the issue you were going at but if we could better separate the advanced scorm stuff where the LMS couldn’t mess it up that may be a start.

I’d like to help you out but I am not a writer by any means and not sure where to start.

Yeah the different levels of 1.2 are rough, i thought datafromlms was in all levels but i should double check. But with the CMS stuff it may be we need to apply some stricter manifest and/or pkg structure that are based on CMS standards. And the test suite would need to test for it.

I’m just rambling now, so i’ll stop…

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-learningspec

I would assert that by lacking any definitions around presentation of content, SCORM has really failed in delivering Sequencing and Navigation (though the guy that led that effort is really a genius, in my personal esteem). If you’re talking about SCORM 1.2, then you’re probably noticing the ill effects of having there different levels of conformance for certification in SCORM 1.2 — that are invisible to most people who just aren’t in that know. They got it right with SCORM 2004 — but made adoption impossibly hard with a Sequencing and Navigation spec that’s really hard to implement — let alone implement interoperably.

SCORM 2.0 definitely has to address the universal nature of interoperability; I personally think it has to address it from the business need of content that endures but with systems that may be transient. From a pure content development perspective, I’ve been thinking about approaching a CMS requirement as a white paper topic if only to publish “content” as XML with an LMS-provided “skin” to content — which helps to solve presentation issues.

But I’m also really interested in some learning 2.0/web 2.0 topics I want to write on.

Maybe I need to post my interests to the blog and see if I can get takers for collaboration on one or more topics. I can get some ideas started as white papers, but I’d really like these ideas to be vetted and improved with the perspective of others.