< Previous | Contents | Next >
COPYRIGHT, LICENSING, AND REDISTRIBUTION GUIDELINES
Copyright 2009 Advanced Distributed Learning. Some rights reserved.
SCORM® 2004 4th Edition documentation suite reprinted with permission from IEEE Std. 1484.11.1-2004 IEEE Standard for Learning Technology – Data Model for Content to Learning Management System Communication, Copyright 2004, by IEEE; IEEE Std. 1484.11.2-2003 IEEE Standard for Learning Technology – ECMAScript Application Programming Interface for Content to Runtime Services Communication, Copyright 2003, by IEEE; IEEE Std. 1484.12.1-2002 IEEE Standard for Learning Object Metadata, Copyright 2002, by IEEE; and IEEE Std.
1484.12.3-2005 IEEE Standard for Learning Technology – Extensible Markup Language (XML) Schema Definition Language Binding for Learning Object Metadata, Copyright 2005, by IEEE. The IEEE disclaims any responsibility or liability resulting from the placement and use in the described manner.
SCORM® 2004 4th Edition documentation suite contains material reprinted with permission from IMS Content Packaging v1.1.4 Copyright 2004, by IMS Global Learning Consortium (IMS GLC) and IMS Simple Sequencing v1.0 Copyright 2003, by IMS GLC. IMS Global Learning Consortium has made no inquiry into whether or not the implementation of third party material included in this document would infringe upon the intellectual property rights of any party. Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the document set forth in this document, and to provide supporting documentation to IMS. This material is being offered without any warranty whatsoever, and in particular, any warranty of non-infringement is expressly disclaimed. Any use of this material shall be made entirely at the implementer’s own risk, and neither the IMS GLC nor any of its members or submitters, shall have any liability whatsoever to any implementer or third party for any damages of any nature whatsoever, directly or indirectly, arising from the use of this material.
You may distribute this document only if the document, its images and examples are:
1. Used for non-commercial, educational, or informational purposes only.
Intact, complete and unmodified. The complete cover page, as well as the COPYRIGHT, LICENSING, AND REDISTRIBUTION GUIDELINES sections, are included.
You may reproduce this document completely or in part only if:
1. The reproduction is for non-commercial, educational, or informational purposes.
2. The source document is properly cited as follows:
Source: Advanced Distributed Learning (ADL), Sharable Content Object Reference Model (SCORM®) 2004 4th Edition Content Aggregation Model (CAM) Version 1.1, 2009.
For additional information or questions regarding copyright, distribution, or reproduction, contact:
ADL Initiative | 1901 N. Beauregard Street, Suite 600 | Alexandria, VA 22311 USA | +1.703.575.2000
Table of Contents
SECTION 1 SCORM® CONTENT AGGREGATION MODEL (CAM) OVERVIEW 1-1
1.1. Introduction to the SCORM Content Aggregation Model (CAM) Book 1-3
1.1.1. Using the SCORM CAM Book 1-3
1.1.2. Relationship with Other SCORM Books 1-4
1.2. The SCORM Content Aggregation Model 1-6
SECTION 2 THE SCORM® CONTENT MODEL 2-1
2.1. SCORM Content Model Components 2-3
2.1.2. Sharable Content Object (SCO) 2-4
2.1.4. Content Organization 2-6
2.1.5. Content Aggregation 2-7
SECTION 3 SCORM® CONTENT PACKAGING 3-1
3.1. Content Packaging Overview 3-3
3.2. Content Package Components 3-4
3.2.3. Package Interchange File (PIF) 3-6
3.3. Components of a Manifest 3-6
3.4. Building Content Packages 3-16
3.4.2. Content Package Manifest Extensions 3-47
3.4.3. Content Package Manifest Href Handling 3-48
3.5. SCORM Content Package Application Profiles 3-54
3.5.1. Resource Content Package 3-54
3.5.2. Content Aggregation Content Package 3-57
3.5.3. SCORM Content Package Application Profile Requirements 3-59
3.6. Best Practices and Practical Guidelines 3-60
3.6.1. Multiple Organizations for a Single Course 3-60
3.6.2. Using the <dependency> Element 3-61
4.2. LOM Metadata Creation 4-66
4.2.3. <lifeCycle> Element 4-77
4.2.4. <metaMetadata> Element 4-83
4.2.5. <technical> Element 4-92
4.2.6. <educational> Element 4-103
4.2.8. <relation> Element 4-116
4.2.9. <annotation> Element 4-122
4.2.10. <classification> Element 4-125
4.2.11. Common Data Types 4-133
4.3. LOM XML Schema Validation Approaches 4-138
4.3.1. Strict Schema Validation Approach 4-138
4.3.2. Custom Schema Validation Approach 4-139
4.3.3. Loose Schema Validation Approach 4-139
4.4. Metadata Extensions 4-140
4.4.1. Data Element Extension 4-141
4.4.2. Vocabulary Extension 4-142
4.5. Metadata and SCORM Content Model Components 4-143
4.5.1. Metadata Describing Content Aggregations 4-144
4.5.2. Metadata Describing Content Organizations 4-145
4.5.3. Metadata Describing Activities 4-146
4.5.4. Metadata Describing SCOs 4-147
4.5.5. Metadata Describing Assets 4-148
SECTION 5 SCORM® SEQUENCING AND PRESENTATION 5-1
5.1. Sequencing and Presentation 5-3
5.1.1. <sequencing> Element 5-3
5.1.2. <controlMode> Element 5-5
5.1.3. <sequencingRules> Element 5-7
5.1.4. <limitConditions> Element. 5-16
5.1.5. <auxiliaryResources> Element 5-17
5.1.6. <rollupRules> Element 5-17
5.1.7. <objectives> Element 5-24
5.1.8. <randomizationControls> Element 5-32
5.1.9. <deliveryControls> Element 5-34
5.1.10. <constrainedChoiceConsiderations> Element 5-35
5.1.11. <rollupConsiderations> Element 5-37
5.1.12. <objectives> Element 5-39
5.1.13. <sequencingCollection> Element 5-44
5.2. Presentation/Navigation Information 5-47
5.2.1. <presentation> Element 5-47
5.3. Relationship to Content Packaging 5-50
APPENDIX A ACRONYM LISTING................................................................................................... A-1
ACRONYM LISTING ............................................................................................................................... A-2
APPENDIX B REFERENCES............................................................................................................... B-1
REFERENCES ........................................................................................................................................... B-3 APPENDIX C DOCUMENT REVISON HISTORY............................................................................. C-1
DOCUMENT REVISION HISTORY........................................................................................................ C-2
List of Figures
Figure 2.1.1a: Examples of Assets 2-3
Figure 2.1.2a: Conceptual Makeup of a SCO 2-4
Figure 2.1.3a: Conceptual Representation of Activities 2-5
Figure 2.1.4a: Conceptual Illustration of a Content Organization 2-6
Figure 2.1.5a: Conceptual Illustration of a Content Aggregation 2-8
Figure 3.2a: Content Package Conceptual Diagram 3-4
Figure 3.3a: Components of a Manifest 3-6
Figure 3.3.2.3.1a: IMS Content Hierarchy Terminology 3-11
Figure 3.3.3a: Conceptual Illustration of Manifest Resources 3-15
Figure 3.5.1a: Example of an Asset Represented as a <file> Element 3-55
Figure 3.5.1b: Example of an Asset Represented as a <resource> Element 3-56
Figure 3.5.1c: Example of a SCO Represented as a <resource> Element 3-57
Figure 3.5.2a: Example of a Content Aggregation Content Package and its Components 3-58
Figure 4.5.1a: Application of Metadata Describing a Content Aggregation 4-144
Figure 4.5.2a: Application of Metadata Describing a Content Organization 4-145
Figure 4.5.13a: Application of Metadata Describing an Activity 4-146
Figure 4.5.4a: Application of Metadata Describing a SCO 4-147
Figure 4.5.5a: Application of Metadata Describing Assets 4-148
Figure 5.3a: Sequencing Rules and Content Packaging Structure Relationship 5-51
List of Tables
Table 3.3.2.3a: Example of Curricular Taxonomy Models 3-10
Table 3.4.1a: SCORM Content Packaging Application Profile Table Format 3-17
Table 3.4.1b: Explanation of Content Packaging Application Profile Multiplicity Requirements 3-17
Table 3.5.3a: SCORM Content Package Application Profile Manifest Element Requirements 3-59
Table 4.2a: Explanation of Multiplicity Requirements 4-67
This page intentionally left blank.