The first thing you need to determine when asked to add SCORM conformance to a system is whether you are really developing "content" or an "LMS". You are developing content if you want to create something that is delivered to other systems. You are developing an LMS if you are creating a system to play content developed by other people. If somebody has asked you to make your LMS SCORM conformant, then they are asking you to create a system capable of importing, delivering and tracking SCORM conformant content developed by others. There are LMS's that output SCORM conformant content as well, but this is a separate capability that is usually referred to as an "authoring tool".
Developing a fully SCORM conformant LMS is no small undertaking. You should start by getting a good grasp of what SCORM is and how it operates. There is a good overview available at http://www.scorm.com/scorm-explained/. There are three high level tasks to undertake. First you will need to create an import mechanism to ingest SCORM conformant content into your system. This involves parsing an XML document called the imsmanifest and it's associated metadata to discover the structure of the content. Next you will need to develop a launch and tracking mechanism to deliver the content. The heart of this system is an ECMAScript (JavaScript) API that allows the content to persist and retrieve data according to the CMI data model. The final step is to develop an implementation of the SCORM / IMS sequencing engine that controls the navigation between parts of a SCORM conformant course (this last step is the trickiest).
In developing a SCORM conformant LMS, be sure to account for the different versions of SCORM. Also remember that not all content is created equally. SCORM is a great specification, but it only gets us about 90% of the way there. There is still some wiggle room for interpretation that you will need to account for as an LMS developer. To develop a truly compatible LMS, you not only need to develop for the letter of the specification, but also for common interpretations of the specification.
发布评论
评论（1）
当被要求向系统添加 SCORM 一致性时，您需要确定的第一件事是您是否真正在开发“内容”或“LMS”。如果您想要创建交付到其他系统的内容，那么您正在开发内容。如果您正在创建一个系统来播放其他人开发的内容，那么您正在开发 LMS。如果有人要求您使 LMS SCORM 符合要求，那么他们就是在要求您创建一个能够导入、交付和跟踪其他人开发的符合 SCORM 内容的系统。有些 LMS 也可以输出符合 SCORM 的内容，但这是一项单独的功能，通常称为“创作工具”。
开发完全符合 SCORM 标准的 LMS 并非易事。您应该首先充分掌握 SCORM 是什么及其运作方式。 http://www.scorm.com/scorm-explained/。有三项高级别任务需要承担。首先，您需要创建一个导入机制，将符合 SCORM 的内容提取到您的系统中。这涉及到解析名为 imsmanifest 的 XML 文档及其关联的元数据，以发现内容的结构。接下来，您需要开发启动和跟踪机制来交付内容。该系统的核心是 ECMAScript (JavaScript) API，它允许内容根据 CMI 数据模型保存和检索数据。最后一步是开发 SCORM/IMS 排序引擎的实现，用于控制 SCORM 一致性课程各部分之间的导航（最后一步是最棘手的）。
在开发符合 SCORM 的 LMS 时，请务必考虑到 SCORM 的不同版本。另请记住，并非所有内容都是平等创建的。 SCORM 是一个很棒的规范，但它只能帮助我们实现大约 90% 的目标。作为 LMS 开发人员，您仍然需要考虑一些解释的回旋余地。要开发真正兼容的 LMS，您不仅需要针对规范的文字进行开发，还需要针对规范的通用解释进行开发。
The first thing you need to determine when asked to add SCORM conformance to a system is whether you are really developing "content" or an "LMS". You are developing content if you want to create something that is delivered to other systems. You are developing an LMS if you are creating a system to play content developed by other people. If somebody has asked you to make your LMS SCORM conformant, then they are asking you to create a system capable of importing, delivering and tracking SCORM conformant content developed by others. There are LMS's that output SCORM conformant content as well, but this is a separate capability that is usually referred to as an "authoring tool".
Developing a fully SCORM conformant LMS is no small undertaking. You should start by getting a good grasp of what SCORM is and how it operates. There is a good overview available at http://www.scorm.com/scorm-explained/. There are three high level tasks to undertake. First you will need to create an import mechanism to ingest SCORM conformant content into your system. This involves parsing an XML document called the imsmanifest and it's associated metadata to discover the structure of the content. Next you will need to develop a launch and tracking mechanism to deliver the content. The heart of this system is an ECMAScript (JavaScript) API that allows the content to persist and retrieve data according to the CMI data model. The final step is to develop an implementation of the SCORM / IMS sequencing engine that controls the navigation between parts of a SCORM conformant course (this last step is the trickiest).
In developing a SCORM conformant LMS, be sure to account for the different versions of SCORM. Also remember that not all content is created equally. SCORM is a great specification, but it only gets us about 90% of the way there. There is still some wiggle room for interpretation that you will need to account for as an LMS developer. To develop a truly compatible LMS, you not only need to develop for the letter of the specification, but also for common interpretations of the specification.