IMS Content Packaging Overview Dec 5, 2005

IMS Content Packaging scope Source: IMS Info Model document Fig. 2.1

Manifest elements Source: IMS Info Model document Fig 4.1

Currently The only defined organization type is acyclic graph (tree) –But other types are possible The only defined resource type is “web content” –But other types are possible The only defined binding is XML Extensibility placeholders in all elements

… … Dereferencing & Mapping An organization element is a structured map of resources. The resources element an unstructured collection of resource descriptors. An item in an organization may reference either a resource descriptor, or a sub-manifest. In the IMS Simple Sequencing and SCORM profiles of IMS CP, only leaf items may reference a resource or sub-manifest. Source: IEEE LTSC WG 11 (Schawn Thropp, Claude Ostyn)

Resource Actually a “digital descriptor for a resource” In current version, resource is always “web content” Has an identifier (scope = manifest) May have its own metadata Resource element contains an inventory of files and/or “dependency” references to other resources “Launchable” resources have an attribute whose value is a URL –URL is typically relative to package “root” –URL may be fully qualified == external resource –URL may have parameters “Not launchable” resources are typically used for shared assets

… …

Erratum Source: IMS Info Model document Fig 4.1 The summary diagram in the IMS CP Information Model document is incomplete. An item may in fact also have meta-data

Profiles of IMS CP: Simple Sequencing & SCORM Source: IEEE LTSC WG 11 (Claude Ostyn) Simple Sequencing adds rules to Organization and items. Each item represents an activity. SCORM 1.2 adds some presentation data options and specifies mandatory elements when metadata is present. SCORM 2004 builds on SCORM 1.2 and adds Simple Sequencing”

Source: IEEE LTSC WG 11 (Schawn Thropp) Abstract view