程序员指南：SCORM用户手册（第10版）

需积分: 9 38 浏览量更新于2024-07-26 收藏 2.7MB PDF 举报

SCORM（Sharable Content Object Reference Model）用户指南针对程序员提供了一份详尽的参考文档，该指南于2011年9月15日发布，版本为10。这份文档主要讲解如何利用SCORM进行eLearning项目的开发、管理与通信，包括从入门到高级主题的全面覆盖。在"Getting Started with SCORM"部分，开发者可以了解到编程过程中的步骤，以及如何构建第一个SCORM兼容课程。其中解释了SCORM的基本术语，如内容包（Content Package）、学习管理系统（LMS）管理和通信机制等。 "Course Structure & Organization"深入讨论了SCORM课程的构成，如资产（Assets）、可共享内容对象（Sharable Content Objects，SCOs）的概念，以及课程的组织结构和内容聚合方式。这部分强调了课程设计时的逻辑布局和内容模块化。 "Understanding the SCORM API"是关键章节，它详细介绍了SCORM 2004 API（应用程序接口），帮助开发者理解如何通过API实现课程控制、状态跟踪和评分等功能。同时，文档还涵盖了CMIS（Course Management Information Set）数据模型，这是SCORM与LMS交互的基础。 "Sequencing & Navigation"和"Control Modes"探讨了课程导航和顺序控制策略，确保学习体验的连贯性和交互性。"Navigation"章节关注如何设计顺畅的课程导航路径，而"Sequencing"则强调了如何组织和控制SCOs的展示顺序。 "Tracking across SCOs using Global Objectives"讨论了如何通过全局目标（Global Objectives）来跟踪学员在不同内容对象中的进度，这对于评估和报告至关重要。"Rollups"涉及汇总学习数据，"Exiting SCOs and Courses"则处理课程结束和退出SCOs时的行为处理。此外，资源部分提供了ADL SCORM资源概述，包括开发工具和资源库，以及实用的开发人员"Cookbook"，包含具体实例和技巧。"Bookmarking"关注如何处理课程中的书签功能，而"Prerequisites"则列出了学习本指南所需的前置知识。评估部分深入探讨了SCORM课程中的测试和评估设计，"The Menu SCO"介绍菜单式内容对象的作用，"Sequencing Collections"则讲解了批量顺序控制的应用。最后，文档还附有SCORM术语的" Glossary"，以及SCORM 2004 API的示例代码，方便开发者查阅。整份指南以详细目录索引结束，便于快速查找特定主题。 SCORM Users Guide for Programmers为程序员提供了全面的指南，使他们能够高效地创建、管理和优化符合SCORM标准的在线学习内容，确保与各种LMS平台的良好集成。

SCORM Best Practices Guide for Programmers

Course Structure & Organization - Introduction

and store learners’ performance data for the SCORM-conformant content organizations,

and it might also store and manage the scheduling and completed work accomplished on

the test course and public roadways.

SCORM Best Practices Guide for Programmers

Course Structure & Organization - Content Packages

3. Content Packages

3.1 Introduction

All SCORM content is ultimately placed in a “content package.” The content package is a .zip

file, sometimes called a Package Interchange File (PIF), that contains everything needed to

deliver content to learners via a SCORM 2004 conformant (see Glossary of SCORM

Terminology for a definition) LMS. As the programmer on your team, you are typically

responsible for creating the SCORM content package.

There are tools available to create content packages or you may choose to create them from

scratch. Some authoring tools will create the entire content package after you load your

SCOs and assets into the tool. The ADL version of the RELOAD is an example of such a tool.

RELOAD provides a graphical interface for creating a content package and managing

sequencing and other values contained in the manifest file that is described below. Ensure

that the tools you select match the knowledge, skill, and ability levels of the team members

who will use them. This guide will not go into much detail on tools as there are many

variations in functionality.

3.2 When to Implement

SCORM does not dictate how learning content is organized. A content package may consist

of a single SCO or may be an organization of hundreds of SCOs. It really depends on the

design and how the course will be used and shared across organizations. It's also important

to understand how your target LMS organizes content. Most LMSs allow registrations at the

content package level and many allow the creation of a curriculum by combining content

packages.

3.3 How to Implement

3.3.1 Components of a Content Package

A SCORM content package contains two principal parts:

The XML manifest file that describes

All of the SCOs or assets you want to include in the package

A representation of the content structure diagram created (called the

organization)

The sequencing rules

Metadata for the SCOs, aggregations, and the package itself

All of the actual SCO and asset files for the content package.

SCORM Best Practices Guide for Programmers

Course Structure & Organization - Content Packages

for details of how this section is structured. At its simplest and most common form, it only

contains the schema and schemaVersion elements:

<schema>ADL SCORM</schema>

<schemaversion>2004 4th Edition</schemaversion>

</metadata>

Additional metadata regarding the organization, activities, and assets in the course may be

referenced in the manifest file. This metadata is typically provided to you by the ISD (see

Glossary of SCORM Terminology). For further reading on how to reference metadata in the

manifest file, see CAM 4.5 or the section that describes the Content Aggregation Model

(CAM) Book in this document.

Organizations

The organization consists of multiple activities (SCO or aggregation) represented by item

elements. This structured representation of the content is typically called the "Activity

Tree." Inside the organization and item is where all the sequencing (see Sequencing &

Navigation) is defined.

The XML structure of an organization is below.

<organization identifier="ORG-SAMPLE"

adlseq:objectivesGlobalToSystem="false">

<title>Sample Aggregation</title>

<title>Sample SCO</title>

</item>

<title>Another Sample SCO</title>

</item>

</organization>

</organizations>

Resources

SCORM content typically consists of web-delivered assets. These assets may be HTML,

images, Flash objects, audio, video, etc. All of these assets are listed in the resources section

of the manifest file. A resource is a grouping of related assets. There are two types of

resources: SCO resources and asset resources. This is designated by the adlcp:scormType

attribute in a resource. A SCO resource contains the starting or "launch" point for a SCO

along with a list of files and dependencies used by the SCO, while an asset resource

Note: The schemaVersion designates the SCORM version and many LMSs read this

value to determine which SCORM engine to apply during the runtime of a course.

SCORM Best Practices Guide for Programmers

Course Structure & Organization - Content Packages

provides supporting

materials which could also

support other SCOs. The

href attribute in the

resource element is used to

determine which file is

initially delivered to the

learner. If a set of assets is

shared by multiple SCOs,

then an asset resource

listing may be created to

remove repetition of assets

in the manifest file. The

asset resource is

referenced using the

dependency element. The following code shows a simple example of a manifest file having a

resource for a SCO (SCO-RESOURCE) that has a dependency on another resource (LESSON-

COMMON).

<title>Example Course</title>

<title>Example SCO</title>

</item>

</organization>

</organizations>

<resource identifier="SCO-RESOURCE" adlcp:scormType="sco" type="webcontent"

href="load.html" >

</resource>

<resource identifier="LESSON-COMMON" adlcp:scormType="asset"

type="webcontent" >

</resource>

</resources>

3.3.2 Content

SCORM does not dictate the format of the content of a SCO. It is typically standard web

content that can be delivered in a web browser.

Best Practice: Using dependencies is useful to reduce redundancy in the manifest file

and keep it better organized.

Best Practice: An important attribute of the

organization element is the

adlseq:objectivesGlobalToSystem. This tells the

LMS how to scope the global objectives in the course.

Global objectives are programmer-specified variables

stored on the LMS which can be read and written by a

SCORM 2004 course (see section on Tracking across

SCOs using Global Objectives). Typically, it is a best

practice to contain them in the content package and

therefore a value of "false" should be used. The

default is "true," so it's important to explicitly define

this.

剩余101页未读，继续阅读

东海凡狼

粉丝: 6
资源: 9

程序员指南：SCORM用户手册（第10版）

SCORM_Users_Guide_for_Programmers

SCORM_Users_Guide_for_ISDs

scorm user guide

scorm.zip_SCORM_SCORM标准_acorm_清除scorm记录

SCORM RunTimeEnv

Scorm.zip_Knowledge_SCORM

scorm:解析和创建 SCORM 包

scorm:向Elefant CMS添加SCORM支持

Scorm自定义播放器

SCORM 2004 RTE

最新资源