IMS Content Packaging: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
Line 27: Line 27:


[[Image:IMS_Content_Packaging_1_1.gif]]
[[Image:IMS_Content_Packaging_1_1.gif]]
== Run Time environments ==
Usually a Content Package is imported into a [[Learning management system]], but there are also external players to be used by authors or event for off-line viewing (e.g. the "reload player").
In principle (and this is where certain [[LMS]] convey wrong information), an IMS Content is not just displayed, but it also should allow user tracking, conditional access to materials, etc.


== Tools ==
== Tools ==
Line 32: Line 38:
Editors:
Editors:


* http://www.reload.ac.uk/tools.html
* http://www.reload.ac.uk/tools.html (editor and player, make sur to pick the correct tool, i.e. don't get the Learning design tools !. These tools need Java)
* http://exelearning.org/
* http://exelearning.org/ (based on the mozilla toolkit).


See also: [[Learning management system]]s.
See also: [[Learning management system]]s.

Revision as of 15:49, 1 March 2006

Definition

IMS Content Packaging has the following objectives:

  • allow transfer of e-learning contents from one system to an other (interoperability)
  • allow to import/export contents into/from a [learning management system]. Therefore also be able to use an independent editing tool.
  • Content Packaging is an evolving standard. Make sure that you know what version you plan to build / import / export !!
  • IMS Content Packaging 1.1 is also part of ADL/SCORM 1.2 and 1.3 (2004)
    • ToDo: Specify which minor versions 1.1.*

Package architecture

A Package Interchange File (PIF) contains:

  1. A zip file that contains various elements, e.g. HTML pages, pictures, Flash Animations, PPT (whatever, the idea is that you take formats that your client can handle)
  2. A special file in the zip is the "manifest" containing:
    • a meta-data section
    • a resource list (i.e. all the other files plus resources on the Net (URLs)
    • an organizational section that describes the structure of how the elements can sequence.
  • In more technical terms: The IMS Simple Sequencing binding defines a unique namespace for sequencing elements in such a way as to permit these elements to be embedded within an IMS Content Packaging manifest file. Elements in the Simple Sequencing namespace can be considered as extending the functionality of Content Packaging to included additional sequencing information. Simple Sequencing elements are intended to be included in the <organization> element of Content Packaging, which contains items that may be recursively included to create hierarchical trees of items. This tree corresponds to the activity tree that drives sequencing.

Here is a picture taken from the [IMS Content Packaging Best Practice and Implementation Guide Version 1.1.4] of october 2004 that shows an overview of the Package Interchange File (PIF) architecture:

IMS Content Packaging 1 1.gif

Run Time environments

Usually a Content Package is imported into a Learning management system, but there are also external players to be used by authors or event for off-line viewing (e.g. the "reload player").

In principle (and this is where certain LMS convey wrong information), an IMS Content is not just displayed, but it also should allow user tracking, conditional access to materials, etc.

Tools

Editors:

See also: Learning management systems.

Links

References