Below is a list of commonly used SCORM terms and acronyms.
Advanced Distributed Learning Initiative
ADL employs a structured, adaptive, collaborative effort between the public and private sectors to develop the standards, tools and learning content for the learning environment of the future.
The ADL website can be found at www.adlnet.org.
A basic learning object (content pacakge resource) that can be delivered to a web client.
See also: Resource
Content Aggregation Model
Provides a common means for composing learning content from discoverable, reusable, sharable, and interoperable sources.
A ZIP file containing SCORM resources and described by an imsmanifest.xml file. A SCORM conformant content package can be deployed to any SCORM conformant LMS for consistent delivery to a learner.
See also: imsmanifest.xml, LMS, PIF, Resource
Integrated Development Environment
An integrated software tool-set for developers.
See also: Trident
An XML manifest file that is included with and describes a SCORM content package.
See also: Content Package
Learning Object Metadata
XML Metadata for describing learning objects in a content package.
See also: Metadata
Learning Management System
A suite of functionality designed to deliver, track, report on and manage learning content, learner progress and interactions. The term "LMS" can apply to very simple course management systems, or highly complex enterprise-wide distributed environments.
Metadata means "data about data". Metadata provides a common nomenclature enabling learning resources to be described in a common way. It can be collected in catalogs, as well as directly packaged within the learning resources it describes. Learning resources that are described with metadata can be systematically searched for and retrieved for use and reuse.
See also: LOM
Package Interchange File
A content package ZIP file.
See also: Content Package
A learning object in a content package. A resource is represented by a single launchable file and all of its file dependencies.
See also: Asset, SCO
Provides a means for interoperability between SCO-based learning content and an LMS. A run-time API, implemented by the LMS, is provided to a launched SCO by the LMS for getting and setting run-time data.
See also: LMS, SCO
Shareable Content Object
A learning object (content package resource) that when launched communicates with the learning management system via the SCORM Run-Time Environment (RTE) API. A SCO represents the lowest level of granularity of learning resources that can be tracked by an LMS using the SCORM RTE.
See also: Asset, LMS, RTE
Shareable Content Object Reference Model
A compilation of technical specifications that enable interoperability, accessibility and reusability of Web-based learning content.
SCORM defines a web-based learning Content Aggregation Model and Run-Time Environment for learning objects. At its simplest, it is a model that references a set of interrelated technical specifications and guidelines designed to meet the Department of Defense's high-level requirements for e-learning content.
Sequencing and Navigation
Rules that an LMS must follow in order to present a specific learning experience. The content developer is responsible for defining the rules to which an LMS must adhere. These rules are expressed within the organization section of a content package' manifest file.
See also: Content Package, LMS
An integrated development environment (IDE) for creating, testing, and deploying SCORM content packages. Read more about Trident at www.scormsoft.com/trident.
See also: Content Package, IDE, imsmanifest.xml
Next, learn more about Conformance.