IMS Content Packaging: Difference between revisions
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
IMS Content Packaging has the following objectives: | IMS Content Packaging has the following objectives: | ||
* allow transfert of [[e-learning]] contents from one system to an other ( | * allow transfert 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 indepenant editing tool. | * allow to import/export contents into/from a [learning management system]. Therefore also be able to use an indepenant editing tool. | ||
Revision as of 18:37, 24 February 2006
Definition
IMS Content Packaging has the following objectives:
- allow transfert 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 indepenant editing tool.
- IMS Content Packaging is also part of ADL/SCORM 1.2 and 1.3 (2004)
Package architecture
- 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)
- 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.
Tools
Editors:
See also: Learning management systems.