IMS Content Packaging

Overview

Dec 5, 2005

IMS Content Packaging scope

• Source: IMS Info Model document Fig. 2.1

PACKAGE

Manifest

Meta-data

Organizations

Resources

(sub)Manifest(s)

CONTENT

(The actual Content, Media,

Assessment, Collaboration,

and other files)

PackageInterchangeFile (PIF)

Manifest ... External Packages ...

Manifest elements

• Source: IMS Info Model document Fig 4.1

Manifest

Organizations

Organization

Item

Item

Resources

Resource

Meta-data

File

Manifest

A reusable unit of instruction

Meta-data describing the package

Organizational structure for this package

A particular hierarchical organization tree

A node within a hierarchical organization

A collection of references to resources

A specific resource

Meta-data describing the resource Locally referenced files that this resource is dependent on

One-to-one One-to-one (or zero)

One-to-many (zero or more)

One-to-many (one or more)

Manifest elements

Meta-data

Dependency Reference to another resource whose files this resource depends on

Meta-data Meta-data describing the file

Meta-data Meta-data describing the organization

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

<manifest> <organizations> <organization> <item> <item identifierref=“resource1”/> <item identifierref=”SubManifest1“ > </item> <item identifierref=”resource1"/> </organization> </organizations> <resources> <resource identifier=”resource1"> … </resource> </resources> <manifest identifier=”SubManifest1"> <organizations> <organization> <item> <item identifierref=”resource2"/> <item identifierref=”resource3"/> </item> </organization> </organizations> <resources> <resource identifier=”resource2"> … </resource> <resource identifier=”resource3"> … </resource> </resources> </manifest></manifest>

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

…<resources> <resource identifier="SCO1" type="webcontent“ adlcp:scormtype="sco" href="simplest_sco.html"> <metadata> … </metadata>  <file href="simplest_sco.html"> <metadata> … </metadata> </file>   </resource> <resource identifier="SCO2" type="webcontent“ adlcp:scormtype="sco“ href="simplest_sco_reusing_script.html">  <file href="simplest_sco_reusing_script.html" />   <file href="SCORMGeneric.js" />   </resource></resources> 

Erratum

• Source: IMS Info Model document Fig 4.1

Manifest

Organizations

Organization

Item

Item

Resources

Resource

Meta-data

File

Manifest

A reusable unit of instruction

Meta-data describing the package

Organizational structure for this package

A particular hierarchical organization tree

A node within a hierarchical organization

A collection of references to resources

A specific resource

Meta-data describing the resource Locally referenced files that this resource is dependent on

One-to-one One-to-one (or zero)

One-to-many (zero or more)

One-to-many (one or more)

Manifest elements

Meta-data

Dependency Reference to another resource whose files this resource depends on

Meta-data Meta-data describing the file

Meta-data Meta-data describing the organization

Organization

Item

A particular hierarchical organization tree

A node within a hierarchical organization

Meta-data Meta-data describing the organization

Meta-data

Item

Meta-data describing the item

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”

Organization

Item

A particular hierarchical organization tree

A node within a hierarchical organization

Meta-data Meta-data describing the organization

Meta-data

Item

Meta-data describing the item

Sequencing Set of sequencing & associated rules

Presentation&Rendering

Set of presentation & rendering data(e.g. “launch” parameters)

Sequencing Set of sequencing & associated rules

Image

Binary File (swf)

MPEG

JPG

Text

Metadata

Presentation/Rendering

Sequencing

Resource

We are not defining this in our standard. Thecomposition of a resource - out side of scope of

our standard

Resource Identifier

Source: IEEE LTSCWG 11 (Schawn Thropp)

Abstract view