Both think the problem must be the other’s fault. Because you know… Their product is perfect. They never have design issues. Ever. So it must be someone else’s fault.
Upon loading the zip package into the CE/Vista SCORM module, the end user saw:
The SCORM package is not compliant with SCORM Ver 1.2 Conformance Requirements. All supporting schemas must be at the root of the package; the following schemas were not found at the root: [adlcp_rootv1p2.xsd, imscp_rootv1p1p2.xsd, imsmd_rootv1p2p1.xsd] As a result, the package may not perform as desired. Are you sure you want to continue?
I actually feel bad for not immediately recognizing this meant these XSD files needed to be in the zip file. Â Blackboard ought to feel bad for having the response this means the imsmanifest.xml in the file was written for a more current version of SCORM than the rather ancient 1.2. I could understand that response if specific items in the file are only relevant in the current version. I don’t understand that response when the same file which works with Vista 3 (created about the same time as SCORM 1.2) works and Vista 8 doesn’t. Sounds more like something changed in Vista 8 to make it more strict.
Fixing the missing XSDs files resulted in a new error:
The SCORM package could not be imported because it does not comply with one or more specifications within the package. The following error was produced: **Parsing Error** Line: 7 Message: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element ‘lom’. Please inform the SCORM vendor and try again once the problem has been resolved.
Is it wrong to be excited about an error? Dropping the problematic items from the imsmanifest.xml file produces new errors. After five iterations, I don’t seem to be making much progress.
Somehow Vista 8 is calling the file where it doesn’t exist for the QuestionMark SCORM module but not other modules.
Known good SCORM module address:
The number after RelativeResourceManager typically can be found under “View File Information” in the file manager. The file name after the number is the name of a file in the zip. Copying the address for the known good let me view it. At this point it seemed logical I could just build the address to the QuestionMark zip manually and see it as a designer (maybe not as a student).Â Unfortunately, this gives me system exception errors.
In trying to solve two problems with one stone, I took the imsmanifest.xml for the known good SCORM module and just changed the href= for resource and file to use the perceptionSCO.html file name for QuestionMark. Still failed to find the file.
I removed all the variables after the perceptionSCO.htm. Now Vista finds the file. It gives me errors about not having the values in those variables, but it found it.
This is stupid.