Please visit SCORM SCOBot Runtime APIs for the latest info.
Lets take a look at implementing SCORM on your LMS.
SCORM (Shareable Content Object Reference Model) was designed for the portability of shareable content objects (SCOs). We will take a closer look at 3 key areas to make this easier to digest. Once we get the general overview, we'll go a little further with some high level technical implementation. There is roughly 400 pages of whitepaper specification documents between both versions of SCORM. Ok ready? Lets go!
Content can be hand crafted, it can also be generated from templates, forms, and csv/excel. This is often blended with media (movies, audio, images). This can range from activities, games, quiz, surveys, quizzes which all can be reported on.
A zip file us used to bundle the files with a required manifest file. This manifest lists out things needed to inform the Learning Management System of the version of SCORM to use, Title, and Item(s) of content objects or Assets to launch. This is all described in XML which employs the ability to support a one-to-many relationship.
This enables the portability of taking content from one platform to another.
Learning Management Systems commonly act as a portal for administrators and students.
SCORM packages are imported, parsed and added for assignment.
The LMS has the responsibility to expose SCORM Runtime APIs, set the student attempt data model and support the student as they interact with the content submitting data, committing it and retrieving it.
Please visit the main page for more info.
Follow twitter for updates: @cybercussion
Check SCOBot (SCORM 2004, 1.2 Content API): SCOBot
Or visit cybercussion.com for more tools and support.