thanks for the info.

i was afraid this might happen, so i’ve been considering modifying the wrapper to include an “override” setting that lets you programatically select which version of SCORM your course is using.

i’ll see if i can get it done later today or maybe tomorrow.

It wouldn’t even import the AS3/2004 demo file. I’m fairly certain that the 2004 features of this LMS are limited - I’m only just now starting to look into them.

Good catch on the zip file. I knew about it but thought I had fixed it.

RE: the api, the SCORM 1.2 RTE documentation states that the SCORM 1.2 API should be named API, while the SCORM 2004 documentation states the SCORM 2004 API should be named API_1484_11.

The ADL’s SCORM 1.2 documentation (SCORM_1.2_RunTimeEnv.PDF, section 3.3.5.1) states: “The API adapter must be accessible via the DOM as an object named ‘API’.”

The ADL’s SCORM 2004 documentation (SCORM_RunTimeEnv.PDF, section 3.2.1) states: “To provide for an interoperable means to locate the API Instance, the LMS’s API Instance must be accessible via the DOM as an object named API_1484_11.”

Why API_1484_11? “SCORM describes the IEEE 1484.11.2-2003 Standard for Learning Technology - ECMAScript Application Programming Interface for Content to Runtime Services Communication as used in SCORM.” (emphasis added)

The imsmanifest.xml file informs the LMS which version of SCORM will be used for a course.

There *is* the possibility an LMS that supports both SCORM 1.2 and SCORM 2004 will make both versions of the API visible to the course, but I don’t think this is the intended behavior, and this can only be tested by taking the wrapper from LMS to LMS.

I’ll certainly test this as much as I can. If you (or anyone reading this) finds this to be the case, please let me know!

You send there cmi.completion_status, shoud be cmi.core.lesson_status, like the code at http://pipwerks.com/lab/scorm/wrapper/1.2/index.html .

Than the first found (win.API_1484_11) will be used for communication, and in case you have SCORM 1.2 package, and you are sending SCORM 1.2 commands, than this communication fails.

Maybe a switch for LMS SCORM API search direction could help.