DOCUMENT NUMBER: CMI012
AICC Packaging Specification Version 1.0
19 September 2006
THIS DOCUMENT IS CONTROLLED BY:
AICC CMI (Computer Managed Instruction) Subcommittee ALL REVISIONS SHALL BE APPROVED
BY THE ABOVE ORGANIZATION PRIOR TO RELEASE
POINT OF CONTACT:
Scott Bergstrom AICC Administrator
P.O. Box 472
Sugar City, ID 83448-0472
Caveats...
The data contained in this document has been collected by the AICC as an information resource for computer-based training programs. Neither the AICC nor any of its members assumes nor shall any of them have any responsibility for any use by anyone for any purpose of this document or of the data which it contains.
©2006 AICC
All rights reserved.
Telephone: (208) 496-1136 E-mail: admin@aicc.org
Prepared by:
Shrikant Pattathil, Harbinger Systems Jack Hyde, AICC
Approved by: William A McDonald Date
Alteon Training
CMI Subcommittee Chairman
Approved by: Neil Cramer
Northwest Airlines AICC Chairman
To receive free notification of revisions to this document, mail or fax the following information to
Scott Bergstrom AICC Administrator
P.O. Box 472
Sugar City, ID 83448-0472
Telephone: (208) 496-1136 Internet address: admin@aicc.org
Name: | |
Title: | |
Organization: | |
Address: | |
City: | |
State: | Zip Code: |
Telephone: | Fax: |
E-mail: |
This document discusses packaging AICC courseware to facilitate moving it from one organization to another (via the Web or other media), from the holder of the courseware to a user (via any media such as a CD), or from a content server to a user (via the Web).
KEY WORDS
CMI LMS
Offline CMI Courseware transfer Mobile CBT Moving courseware
Nomadic CBT Communication, CBT Packaging Guidelines Transfer of courseware
The use of registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.
Version 1.0
19 Sept 2006
Original version
Purpose 1
Scope 1
Rationale 1
Future Versions 1
Creating Implementation 2
CMI001 AICC CMI Guidelines for Interoperability defines a way to describe a course, its structure, and how the units in the course should be sequenced. However, it does not describe a mechanism to bundle all the pieces of a course to transfer them.
Several specifications including CMI011 Package Exchange Notification Services and CMI010 Offline CMI Communication describe scenarios in which AICC courseware is transferred. In the case of PENS (Package Exchange Notification) the transfer is normally from one organization to another. In the case of Offline CMI the transfer is from an organization to a user.
This specification describes one way in which courseware materials may be bundled or packaged for transfer.
This specification defines the structure of AICC courseware packaged to facilitate its transfer. The package may be used to transfer courseware
From one organization to another (via the Web or in media such as a CD or DVD)
From one part of an organization to another part of the same organization.
From a server to a user of the courseware via the Web.
From an organization to a user via media such as CD or DVD.
This specification describes:
Rationale for packaging a course into a zip archive
Course Package Structure
Packaging a course as a ZIP archive is important for the following reasons:
Ability to download/distribute the complete course from a single web-URL or CD
Compression of course data ensures faster download and easier distribution
In future versions of this specification, other mechanisms for describing an AICC course, its structure, and its sequencing rules will be included as alternatives to zipping the current AICC course description files. An XML file describing the course and its contents is being developed by the AICC CMI subcommittee.
This conformance clause describes requirements the creating implementation (the implementation that generates the courseware package).
The creating implementation shall:
Include the following files - as defined in CMI001 - in the package.
The course description file (*.crs)
The assignable unit file (*.au)
The descriptor file (*.des)
The course structure file (*.cst)
All internal links to all pages/resources in the course may be relative or absolute. The creating implementation may include the following files defined in CMI001:
The objectives relationships file (*.ore)
The prerequisites file (*.pre)
The completion requirements file (*.cmp)
Content files. This includes assignable unit files and all of the assets required by the assignable unit files to deliver the content to a learner.
In general, the structure for a ZIP archive of a course to be downloaded/distributed is as follows:
The PKZip file shall conform to RFC 1951.
The zip file shall contain
A root folder
Course structure files (*.au,*. crs, *.cst, *.des) that are defined in CMI001
When decompressed/unzipped the course structure files shall be present in the root folder
The zip file may contain.
Subfolders for content files.
Course content files which may be local or remote. Content that is included in the zip file is considered local. All other content required for the course is considered remote.
Content files (local or remote) include html pages along with all resources i.e. scripts, style sheets, images, audio, video etc.
The local content is referenced by a relative path
The “remote” content is referenced by an absolute path (file://, http://,...)
Additional files describing the course (*.ore, *.pre, *.cmp) that are defined in CMI001. When decompressed/unzipped these additional files shall be present in the root folder
+
Course content files
HTML Files
Resource Files
ZIP
Archive
Course Structure Files
*.au, *.crs, *.cst,
*.des
The zip archive shall not be password protected.
CMI001 AICC CMI Guidelines for Interoperability version 4.0
CMI009 AICC Offline CMI Guidelines (currently in draft)
CMI011 Package Exchange Notification Services version 1.0a
HTTP: RFC 1945 – Hypertext Transfer Protocol – HTTP/1.0.