Overview
The CAM according to the CAM book (specifications), the "Content Model describes the components used to build a learning experience from learning resources". It then further explains that the CAM is composed of Assets, SCO's and Content Organizations.
An Asset is a file, avi, swf and other single type of learning resource.
A SCO is a collection of these. But more importantly, it is SCORM aware. I.E. It contains javascript for communicating to the SCORM RTE.
An asset is therefore, not tracked, whereas a SCO can be.
Assets
A common question I have heard, is why do Assets get listed if they cant be tracked? The answer lies in how one can share and reuse assets. The idea is that an Asset can have metadata attached, whereby repositories can be searched for these Assets.
It is not exactly specified yet, not to my knowledge. But a standard for repository searching and indexing will probably come along in the future.
Versioning and Context are not in the specification yet.
XML
The CAM is ultimately an XML file adhering to defined schemas. It is "packaged" by naming this xml file (1 per package), imsmanifest.xml and inserted into a zip file along with all the Assets (I wont get into URI's now).
The XML schema for listing the Assets and SCO's (Sharable Content Objects) define nodes such as <resource> and <file>.
Would it have been better to name the node <file>, Asset?
Now there is nothing "wrong" with the little amount of the CAM that I have explained.
But is not exactly simple when you are dealing with multiple terms and their subtle nuances.
For example the specifications also mention terms such as 'unit', 'instructional unit', 'course' and 'lesson'.
A SCO (Sharable Content Object), by its name, one would think that it is an 'Asset', but its not.
Then there are other terms such as Activity,
Here is a little crib sheet. Let me know if you don't like the comparisons or wish to add/remove something.
Term
Equivalent Terms
Whats not
Asset (physical term)
is a Resource and/or a File
Not Tracked, Not a SCO
SCO (abstract term)
is a Resource and a File, or collection of these
is not really an Asset, unless it communicates with RTE API
Unit (generic term)
an Asset, SCO, or a Lesson
Not a Course, Lesson, Activity, Organization or Item
Lesson (abstract term)
Abstract form composed of Asset/s, Resource/s, SCO/s, Could be an Organization, Activity or Item
Not a Course, nor an Organization
Course (abstract term)
composed of Lesson/s, Asset/s, Resource/s, SCO/s
Not a Lesson
Activity (abstract term)
Is itself an Activity and is composed of, Activities, Lesson/s, Asset/s, Resource/s, SCO/s. It can also be called a 'unit of instruction'.
Is itself not Asset/s, Resource/s, SCO/s, but rather can point to
Organization (abstract term)
Is itself an Activity and is Composed of Activities
Is itself not Asset/s, Resource/s, SCO/s, but rather can point to
Organizational Item (generic term)
Is itself an Activity and is Composed of Activities
Is itself not Asset/s, Resource/s, SCO/s, but rather can point to
I would prefer the use of just two main terms, with a sub type.
SCO
1 or more physical resources
Types
Non Tracked SCO
Tracked SCO
Activity
An abstract entity, one or more nested activities, that references or includes SCO/s
used for tracking, sequencing and applying context (metadata) to the referenced SCO/s
Previous Topic
