Sharable Content Object Reference Model: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
Line 11: Line 11:
* Until 2000 SCORM was an acronym for "Sharable Courseware Object Reference Model".
* Until 2000 SCORM was an acronym for "Sharable Courseware Object Reference Model".


See also:
;See also (!)
* [[learning object]]s for a general discussion on modular, reusable learning contents and activities.
* [[learning object]]s for a general discussion on modular, reusable learning contents and activities.
* [[IMS Content Packaging]], the now well-established standard for assembling, distributing and running learning objects.
* [[SCORM 1.2]] for a more in-depth discussion of the most popular SCORM profile
* [[SCORM 1.2]] for a more in-depth discussion of the most popular SCORM profile
* [[standard]] for an overview on pedagogical (and other) standards.
* [[standard]] for an overview on pedagogical (and other) standards.

Revision as of 10:48, 22 December 2006

Draft

Definition

  • SCORM is a sort of "standards package" (also called "profile" or "collection of standards") to define reusable learning objects and behavior that comptabible Learning management systems must adopt. SCORM profiles are defined and promoted by the Advanced Distributed Learning (ADL) initiative by the US government, i.e. the Department of Defense (DOD). SCORM is also currently the de facto Industry Standard.
  • The Sharable Content Object Reference Model (SCORM) specifies how learning content should be coded, how others can later "discover" that content, how it fits into a sequence of learning activities, and how its appearance through the delivery media can be customized for the individual learner.
  • Here is another quote from their Web Site (feb 2006): "The Sharable Content Object Reference Model (SCORM) defines a Web-based learning "Content Aggregation Model" and "Run-Time Environment" for learning objects. At its simplest, it is a reference model that references a set of interrelated technical specifications and guidelines designed to meet DoD's high level requirements for Web-based learning content. These requirements include, but are not limited to, reusability, accessibility, durability and interoperability."
  • Until 2000 SCORM was an acronym for "Sharable Courseware Object Reference Model".
See also (!)
  • learning objects for a general discussion on modular, reusable learning contents and activities.
  • IMS Content Packaging, the now well-established standard for assembling, distributing and running learning objects.
  • SCORM 1.2 for a more in-depth discussion of the most popular SCORM profile
  • standard for an overview on pedagogical (and other) standards.

Contents of the SCORM profiles

It is quite difficult to find out which different standards (e.g. form IMS) are integrated in which SCORM profile. It is even more difficult to understand how additions by SCORM fit in.

SCORM 1.0 (January 2000)

The original version of SCORM was primarily a test version. The concept of a Sharable Content Object (SCO) was introduced and after some testing, ADL made some implementation examples available.

SCORM 1.1 (January 2001)

This profile marked the end of a first trial and error implementation phase and the beginning of the application phase. This version used a XML file based on AICC specifications for describing content structure. Also noteworthy is the change from Sharable Courseware Object Reference Model to Sharable Content Object Reference Model. This version, though improved still lacked support for metadata and was quickly replaced by SCORM 1.2.

SCORM 1.2 (October 2001)

The most important parts of this profile are the Run-Time Environment (RTE) and Content Aggregation Model (CAM).

  • The RTE specifies how content should behave once it has been launched by the LMS.
  • The CAM specifies how you should package your content so that it can be imported into an LMS. This involves creating XML files that an LMS can read and learn everything it needs about metadata describing the course, its pedagogical content elements and organization of the learning experience. SCORM 1.2 adopted the IMS Content Packaging specification and the the IMS/IEEE Learning Object Metadata Standard and it added various extensions.

SCORM 1.2 remains the most popular standard industry, although it is now replaced by SCORM SCORM 2004.

See SCORM 1.2 for a more detailed discussion of this profile.

SCORM 2004 (2004 - 2006)

There are three subversions which are quite different

  • 1st (ak Scorm 1.3),
  • 2nd
  • 3rd edition.

The current 3rd version adds to SCORM 1.2 elements like:

  • IEEE’s ECMAScript Application Programming Interface. More particularly: Content to Learning Management System (LMS) communication and Data model for content to LMS communication
  • IMS Simple Sequencing, i.e. the possibility to define learning sequences depending on the sequence of activities. It also allows for a sharing and use of information on learners status with respect to the learning objectives and competencies acquired while working through different content objects and courses, so long as they remain within the same LMS.

This more robust version should offer greater interoperability since it adopts "stronger" IEEE API and IMS sequencing standards.

A word of warning

SCORM-compatibility of an LMS means 'nothing'. You must inquire:

  • About precisely what version (and subversion) your system claims to support. Currently, most major systems can only handle SCORM 1.2. Some that claim to be SCORM 2004 compatible, will only support the 1st edition (aka SCORM 1.3).
  • Whether your system has been certified. If not, you may find try to find what exactly it claims to handle (it is perfectly possible to write a tool that will just display SCORM-packaged Content Packages that includes just assets, but no SCOs and then choke on JavaScript calls ....)
  • A tool like the Reload Editor can help you to upgrade old content packages.

Comment

By DSchneider

While SCORM represents today's main-stream e-learning that is focused on delivery of courseware it does not represent in our opinion all of what educational technology can be. The main long-term contribution of SCORM was its insistence on data standards, run-time standards (i.e. interoperability) which indeed are major issue for organizations like the US Department of Defense that sponsors over 30'000 training courses. Frustration over non existing standards also led industry and even parts of Academia to adopt various SCORM profiles.

I also disliked the technical architecture of SCORM 1.2, i.e. the API for LMS-contents interaction. SCORM 2004 with support for simple sequencing moves into the right direction. In principle, contents should as much as possible rely on clear language (as opposed to ECMAScript calls).

Tools

There are a number of tools that allow you to edit Scorm 1.2 or 1.3 compatible contents, e.g here are 2 free ones:

However, be warned about "SCORM-compatible" LMS. Full SCORM compatibility is not guaranteed even if your vendor says so. E.g. your LMS may well play contents, but not be able to provide user tracking. Only trust certified software by ADL or those you tested...

Links

Standards and Bodies

Introductions

References

  • Advanced Distributed Learning Initiative, Sharable Content Object Reference Model (SCORM), Version 1.2, The SCORM Run-Time, Environment, October 1, 2001 (available from ADL
  • Advanced Distributed Learning Initiative, Sharable Content Object Reference Model (SCORM), Version 1.2, The SCORM Content Aggregation Model, October 1, 2001 (available from ADL