Content aggregation model (CAM)

Fig 2-0-1 Example of Content Aggregation Model

Figure 2-1 is an example of CAM. Content aggregation model provides how to descript

and define a learning content, and descript how to combine different learning subject with a course. In this way, the course becomes a shareable learning resource, and can be applying into different learning management system and learning repository []. CAM includes three subjects: (1) Content Model: the definition of SCORM learning object content model.

(2) Meta-data: the information of learning elements.

(3) Content Packaging: it defines how to packaging and combine several learning element as a course structure format (CSF)

The detail of CAM can refer to the specific “SCORM Content Aggregation Model”

publish bye ADL.

We will give a brief introduction as below:

[] Advanced Distributed Learning (ADL) initiative, “SCORM Specifications – SCORM Version 1.3 Application Profile Working Draft Version 1.0”, March 26, 2003

2.3.1.1 Content model

Content model includes three kinds of learning objects, they are Asset, SCO and Content Aggregation.

A. Asset

Asset are the basic element in learning objects, they includes Movie, Text, Picture, Sound, html files which can be transfer as web client format.

Fig 2-0-2 Content Model – Asset

B. Sharable Content Object (SCO)

SCO are the collection of one or several assets, in addition, they includes the ability to communicate with LMS. SCO are the primitive learning object which can be tracking by run-time environment, and the smallest subject can be learned from LMS. A concept of SCO is showing as figure?.

Fig 2-0-3 Figure 2-3 Content Model – SCO

SCO could operate API via API Adapter (the element who implement API), at least include the API LMSInitialize (“”) and LMSFinish (“”), which is the ability to opening and closing SCO. We will illustrate the method to communication with LMS in chapter

2.4

C. Content Aggregation

As the picture ? Content Aggregation are the course structure of content, they includes several SCO or Asset, and turn into a meaningful learning unit. (e.g. a chapter in a course) They provide the LMS for designing the course material while combine with the Content Aggregation Mata-data whose descript the sequence of SCO or Asset in these learning elements, and becomes a complete course. In brief, Content Aggregation is also called Content Structure.

Fig 2-0-4 Content Model – Content Aggregation

2.3.1.2 Meta-data

The SCORM Meta-data Profiles represents a mapping and recommended usage of the IEEE Learning Technology Standards Committee (LTSC) Learning Object Metadata (LOM) elements for each of the SCORM Content Model Components. In general, guidance is provided for meta-data to be applied to Assets, SCOs, Activities, Content Organizations and Content Aggregations to describe them in a consistent fashion such that they can be identified, categorized, searched for and discovered within and across

systems to further facilitate sharing and reuse.

The mechanism for binding the Content Model components that were discussed earlier to the matching Meta-data application profile is the Content Package as described in SCORM. There are currently five places meta-data can be applied within a content package:

• Manifest: Meta-data at the manifest level describes the content package as a whole.

Meta-data placed at the manifest level is SCORM Content Aggregation Meta-data.

• Organization: Meta-data at the organization level describes the Content Organization as a whole. This may be a course, unit, lesson or any other organized instructional unit.

Meta-data placed at the organization level is SCORM Content Organization Meta-data.

• Item: Meta-data at the item level describes a nested hierarchy of Activities in a context sensitive manner. When associated with an item, the SCORM Activity Meta-data definition must be used.

• Resource: Meta-data at the resource level describes a SCO resource or an Asset resource in a context insensitive manner. This meta-data is bound by either the SCORM SCO Meta-data or Asset Meta-data definitions (Determined by the type of resource -

adlcp:scormType attribute).

• File: Meta-data at the file level describes an Asset in a context insensitive manner.

This meta-data is bound by the SCORM Asset Meta-data definition.

2.3.1.2 Content packaging

Once learning content is designed and built, there is a need to make the content available to learners, authoring tools, repositories or Learning Management Systems (LMSs). The IMS Content Packaging Specification was designed to provide a standard

way to structure and exchange learning content.

The purpose of the Content Package is to provide a standardized way to exchange learning content between different systems or tools. The Content Package also provides a place for describing the structure (or organization) and the intended behavior of a collection of learning content.

Figure 2-5 is a conceptual diagram that illustrates the components of a Content Package.

A Content Package contains two major components:

• A special XML document describing the content structure and associated resources of the package called the manifest file (imsmanifest.xml). A manifest is required to be present at the root of the content package.

• The physical files making up the content package.

Fig 2-0-5 Content packaging conceptual diagram

Figure 2-5 is also called Package Interchange File (PIF). PIF is a binding of the content package components in the form of a compressed archive file. The PIF contains the

imsmanifest.xml, all control files and the resources referenced in the content package (those that are local to the PIF, i.e., contained in the content package). SCORM recommends that content packages be created as PIFs. The PIF provides a concise Web

delivery format that can be used to transport content packages between systems.

2.3.1.3 imsmanifest.xml

As show in figure 2-5, the tag <organization> defines the relationship between course structure and each learning element hierarchy. Tag <item> is the learning element whose attribute “identifierref” map to <resource> (e.g “Ⅰ＂ in figure 2-6). Tag <resource>

point out learning element’s physical files location. Tag

<adlcp:location>something</adlcp:location> (e.g “ Ⅱ ”in figure 2-6) would link to SCO’s or Asset’s meta-data XML file. The detail argument for imsmanifest.xml can refer to the document SCORM CAM chapter 3.4[]

Ⅰ

Ⅱ

Fig 2-0-6 Overview of content packaging in the file “imsmanifest.xml”

2.3.1.4 Sequencing

For different use, it will be more powerful if providing different learning activity sequencing. IMS bring up SSS (simple sequence specification) to enhance the power of SCORM. It includes a series of different kind sequencing rule, e.g. “No Sequencing rules”, “Linear”, “Constrained”, “Knowledge paced” and “Remediation”. All of them will be described by the file “imsmanifest.xml”. In our thesis, we do not spend time to do more discussion about sequencing.