SCORM Manifest Files

SCORM content packages contain an XML manifest file that describes the package and its contents. The manifest file is a structured inventory of the content of the package. The name of the manifest file is always imsmanifest.xml and it must appear in the root of the content package.

    Mandatory Manifest File contents:
  • Unique identifier
  • Minimal metadata describing the package and its SCORM version
  • One or more resource definitions listing all files required to launch and deliver each resource
  • One or more organizations of learning activities

    Optional Manifest File contents:
  • Sequencing information for organizations
  • More metadata for the content package, resources, and organizations

All references to files in the resources must be relative to the root of the content package. Referencing external files or absolute URLs is not allowed.

Trident will automatically create the manifest file as shown when you create a new content package project. This allows you to focus on defining and organizing the resources and activities your content package will deliver to the learner.

Manifest XML

The <manifest> element declares the manifest, its unique identifier, its version, and XML references to the schema files defining its format. The identifier attribute of the element should be globally unique. The version is arbitrary, its value space not defined by SCORM. The declaration of schema/definition files reference files in the root of the containing content package.

    <manifest> attributes:
  • identifier - required; a globally unique identifier for your content package
  • version - required; can be any value representing the content package's version

    <manifest> children:
  • <metadata> - required; defines the content package's schema and version
  • <organizations> - required; described in Organizations topic
  • <resources> - required; described in Resources topic
  • <sequencingCollection> - optional; described in Sequencing topic

The <metadata> element defines Metadata information about your content package.

<metadata> children:

  • <schema> - required; declares the manifest as conforming to the ADL SCORM schema
  • <schemaversion> - required; element declares the manifest as conforming to Content Aggregation Model (CAM) version 1.3

The <organizations> element will define your content package's Organizations. An Organization describes how resources are logically organized into a learning experience. This XML element is further described in the Organizations topic.

The <resources> element will define your content package's Resources. Resources are the content objects and files that comprise your learning objects. This XML element is further described in the Resources topic.

Code Example

The code below shows the code of an "empty" manifest file. The manifest is described as empty because it does not yet contain definitions of content resources or organizations needed to deliver it.


Next, learn more about Resources.