SCORM SCORMThe greatest fear people have about online
learning is that people will be treated as machines,
that interactions will be cold and impersonal.
It’s not going to happen,
because the essential constituents of an online community are people.
ADL (Advanced Distributed Learning): http://www.adlnet.gov/
Initiative by the U.S. Department of Defense to achieve interoperability across computer and Internet-based learning courseware through the development of a common technical framework, which contains content in the form of reusable learning objects. See also SCORM and the ADL Website.
SCORM (Sharable Content Object Reference Model):
A set of specifications that, when applied to course content, produces small, reusable learning objects. A result of the Department of Defense's Advance Distributed Learning (ADL) initiative, SCORM-compliant courseware elements can be easily merged with other compliant elements to produce a highly modular repository of training materials
AICC (Aviation Industry Computer-Based Training Committee):
An international association of technology-based training professionals that develops training guidelines for the aviation industry. AICC has and is developing standards for interoperability of computer-based and computer-managed training products across multiple industries. See the AICC Website.
Learning object:
A reusable, media-independent collection of information used as a modular building block for e-learning content. Learning objects are most effective when organized by a meta data classification system and stored in a data repository such as an LCMS.
LCMS (learning content management system):
A software application (or set of applications) that manages the creation, storage, use, and reuse of learning content. LCMSs often store content in granular forms such as learning objects
What is SCORM?
The Sharable Content Object Reference Model (SCORM)
SCORM Reuse: Current Reality, Challenges, and Best Practices (Breeze - Recorded)
E-Learning Standards Frequently Asked Questions about AICC and SCORM Steve Saporta | April 1, 2002
What is the Sample Run-Time Environment?
The Sample Run-Time Environment (RTE) software provides a reference implementation of the Content Packaging and Run-Time Environment components of the SCORM. This is not meant to be a complete or robust functioning Learning Management System (LMS), but rather a single example of how the Content Packaging and RTE may be implemented within an LMS and within Sharable Content Objects (SCOs).
The SCORM Version 1.2 Sample RTE contains sample working implementations of the SCORM Content Packaging, RTE Application Program Interface and RTE Data Model as illustrated. The SCORM Version 1.3 Sample RTE should prove a useful example to content developers and LMS vendors alike.
Academic ADL Co-Lab Facilitated Online SCORM School
SCORM School 2004: November 19, 2006
1. Aggregate all resources into a Content Package: To have a SCORM compliant content package, there must be a "master" imsmanifest.xml file that contains references to all resources of your content. Absent this file, the content is not SCORM compliant and will not perform in a SCORM compliant Learning Management System (LMS). The aggregation process groups all of the content resources into one folder and creates the "master" imsmanifest.xml file. ( an example of an imsmanifest.xml file ). This can be done manually, or by using a tool supplied by the authoring vendor.
2. Add Army Meta-data: To meet Army requirements, there must be SCORM and Army meta-data.
Metadata Editor
3. Readying the package: The content package must be made into a Package Interchange File (PIF) before being transferred. This allows for ease of transfer, storage and loading into the LMS. Creation of this PIF follows SCORM guidelines.
DotNetSCORM™ - The SCORM .NET Open Source Learning Management Project
** Home ** Class
Pages ** Site Map **
David J. Hark
HARK/INTERNET-HELP, Inc.
P. O. Box 201 Shepherdstown, WV 25443-0201
304-876-2607
N8GMQ
dhark@fred.net
http://www.dhark.com
http://www.fred.net/dhark
Last updated: 26 February 2007
© 2006, 2007 David J. Hark