Overview of IMS Content Packaging

Sheila MacNeill

Complex Objects meeting 1/02/07

What is IMS Content Packaging (CP)

XML based packaging format developed by IMS Facilitate transport and reuse of web based learning

materials Aggregation of resources, structure with (rich)

description Originally based around learning materials but has

been extended and used in other areas such learner information.

Application profiles: SCORM/SCORM2004, IMS Common Cartridge

Complex Objects meeting 1/02/07

Background and overview

First released in 2001 V.1.1.4 current public release V.1.2 in development

Complex Objects meeting 1/02/07

Current status of v1.2

Public draft 1 released early 06 IMS internal draft 2 documentation complete by

early March 07 Testing and implementation by IMS members

March - November 07 Parallel IEEE LTSC standardisation process Full public release early 2008

Complex Objects meeting 1/02/07

What constitutes an IMS CP?

Manifest file (xml) with 3 main sections:

Metadata (description) Organizations (structure) Resources (stuff) (submanifests) All contained within PIF

(packaging interchange file) - commonly a zip file

Complex Objects meeting 1/02/07

Common types of packages

Simple stand alone package - all resources in interchange (zip) file, usually one level of manifest - no child manifests.

This type of package is most likely to be supported by VLEs/ learning object repositories.

SCORM packages example of this stand alone zip, but they need to package level metadata in a separate file which is linked to from the manifest. SCORM also extends support to tracking and sequencing of content.

Complex Objects meeting 1/02/07

Common types of packages cont.

Bare Manifest - doesn’t contain all resources, instead references links in a known repository.

Can be interchanged either using just the manifest file or a zip containing only the manifest.

Advantages: Same resources can be re-used many times Resources can be updated at any time Resources can be tracked (publisher/repository owner) Access can be controlled

Disadvantage: Consuming system needs reliable internet connection

Complex Objects meeting 1/02/07

Common types of packages cont.

Composite or meta-package - one step on from bare manifest, links to whole packages not just content assets.

Most likely linking to a well defined structured set of self contained packages e.g a course.

Advantages: moves notions of reusability of content forward

Disadvantages: quite a new concept, so not all systems may be able to

provide adequate functionality.

Complex Objects meeting 1/02/07

Common types of packages cont.

Archive package - gathers a number of resources and captures their basic structure (not intended to use with learners).

Typically used to exchange ‘raw’ content which can be made into a complete package at a later stage.

Complex Objects meeting 1/02/07

Common types of packages cont.

Specialized package - don’t conform to common type but are used to convey specific types of content, often inline in the manifest. Most of these packages are combinations of packages with other IMS specification content e.g. ePortfolio, QTI, Learning Design.

CP really just providing a convenient aggregation for different XML data descriptions.

Complex Objects meeting 1/02/07

EXAMPLE 1 - Simple standalone package

Complex Objects meeting 1/02/07

Complex Objects meeting 1/02/07

Complex Objects meeting 1/02/07

Complex Objects meeting 1/02/07

Complex Objects meeting 1/02/07

Complex Objects meeting 1/02/07

CP V.1.2 - updates

General clarification of information model and binding Providing alternative resources with different accessibility

characteristics Extending resource vocabulary

used to be just ‘webcontent’ and scattered IMS specific types (QTI items etc.)

now is an extensible vocabulary in a VDEX file (can be extended by anyone)

Extending organization vocabulary used to be just ‘hierarchical’ now extensible (e.g. TopicMaps, some

METS integration)

New mechanism to refer to remote manifiest structures (ipointer)

Complex Objects meeting 1/02/07

CP 1.2 Conceptual Model

Complex Objects meeting 1/02/07

EXAMPLE 2 - Linking packages using Ipointer

Complex Objects meeting 1/02/07

Example 2: linking packages

Complex Objects meeting 1/02/07

Strengths & Weaknesses of CP

Strengths: Relatively simple spec -

freely available tools for package creation

Flexibility/interoperability Widespread adoption

within education/training Successful profiling -

SCORM

Weaknesses: Complexity of spec Interoperability issues Range of interpretations of spec

- just a container or something more complex?

Lack of knowledge outwith education/elearning sector

Complex Objects meeting 1/02/07

More information

IMS Content Packaging : http://www.imsglobal.org/content/packaging/index.html

IMS Common Cartridge : http://www.imsglobal.org/commoncartridge.html

ADL/SCORM : http://www.adlnet.gov/scorm/index.cfm

JISC CETIS briefing papers: http://zope.cetis.ac.uk/static/briefings.html

RELOAD: http://www.reload.ac.uk