I’m about to publish a series of tutorials demonstrating how to build SCORM courses by hand. Some may ask: Why hand-coded, and why SCORM? Let’s address the SCORM question first. There are a dozen reasons why e-learning developers and instructional designers might scoff at SCORM: It’s outdated
SCORM requires all of the course assets to be listed as a <file> item in the <resource> node. This is not evenly enforced — some LMSs don’t care of you do it or not — but is still a good practice. If you’re anything like me,
Anyone who works with SCORM 2004 has seen something like this: With just a little effort, you can make it look like this, and still be perfectly valid: SCORM manifests are required to specify a slew of schema files via the schemaLocation attribute. Here’s what you’d typically see:
Made a minor update: scorm.quit() was setting a value (cmi.exit) but not invoking scorm.save() prior to termination. This could lead to failure to persist the value of cmi.exit in the LMS. View the latest update on GitHub Comments Bard Dale wrote on March 4, 2014 at
I was reading the SCORM 1.2 reference docs today. I wanted to copy a passage for my notes, but the PDF is password-protected and prevents anyone from copying text. (REALLY irritating, considering the ADL is a quasi-government organization and the docs should be open to all.) What to do?