What do you know about SCORM?

• The Sharable Content Object Reference Model defines a specific way of constructing Learning Management Systems and training content so that they work well with other SCORM conformant systems. Basically, the different versions of SCORM all govern the same two things: packaging content and exchanging data at runtime.
  
  
• Packaging content determines how a piece of content should be delivered in a physical sense. At the core of SCORM packaging is a document titled the "imsmanifest". This file contains every piece of information required by the LMS to import and launch content without human intervention. This manifest file contains XML that describes the structure of a course both from a learner’s perspective and from a physical file system perspective. Questions like, "Which document should be launched?" and "What is the name of this content?" are answered by this document.

• Runtime communication, or data exchange, specifies how the content ”talks” to the LMS while the content is actually playing. This is the part of the equation we describe as delivery and tracking.
  
  
• There are two major components to this communication. First, the content has to "find" the LMS. Once the content has found it, it can then communicate through a series of "get" and "set" calls and an associated vocabulary. Conceptually, these are things like "request the learner’s name" and "tell the LMS that the learner scored 95% on this test." Based on the available SCORM vocabulary, many rich interactive experiences can be communicated to the LMS