简体繁体 English

实施 SCORM 与 xAPI 之间的技术差异是什么？

[英]what are the technical differences between implementing SCORM vs xAPI?

原文 2022-05-12 09:28:18 6 2 scorm/ xapi

I want to integrate eLearning to an existing system that I already have, I have been reading a lot about two standards SCORM and xAPI but all what I read was theoritical differences about pros and cons of each standard, anyhow I want to have a technical differences from a developper perspective about implementing those standards in the system, what are the differences by implementing those standards from a developping view?i Just want headlines of the process of developping those standards.我想将电子学习集成到我已经拥有的现有系统中，我已经阅读了很多关于 SCORM 和 xAPI 两个标准的内容，但我所阅读的只是关于每个标准的优缺点的理论差异，无论如何我想要一个技术差异从开发人员的角度来看，在系统中实施这些标准，从开发的角度实施这些标准有什么区别？我只想了解制定这些标准的过程的标题。 any references or documentation about that would also be very helpful.任何相关的参考资料或文档也将非常有帮助。 and would it be doable or logical to integrate one standard in the system and later on integrate the other one?将一个标准集成到系统中然后再集成另一个标准是否可行或合乎逻辑？ for example SCORM then later if needed I integrate xAPI?例如 SCORM，然后如果需要我集成 xAPI？

2 个解决方案

Let me start with the integration part.让我从集成部分开始。 Yes you can do SCORM and later integrate xAPI, though that might require retooling the SCORM course, or LMS to do the xAPI part.是的，您可以先完成 SCORM，然后再集成 xAPI，尽管这可能需要重组 SCORM 课程或 LMS 来完成 xAPI 部分。 This is done in practice.这是在实践中完成的。 A lot of what I do is integrate existing SCORM ecosystems with xAPI and LRSs.我所做的很多工作是将现有的 SCORM 生态系统与 xAPI 和 LRS 集成。

As for differences in SCORM and xAPI, here's some high-level info.至于 SCORM 和 xAPI 的差异，这里有一些高级信息。

SCORM is a set of specifications that defines the way to package content, the way to have your content report data, and the way an LMS launches and manages SCORM content and data. SCORM 是一组规范，定义了 package 内容的方式、内容报告数据的方式以及 LMS 启动和管理 SCORM 内容和数据的方式。 xAPI is a specification that defines a REST style API and JSON data format to track interactions/activity that happened in content. xAPI 是一种规范，它定义了 REST 样式 API 和 JSON 数据格式来跟踪内容中发生的交互/活动。
As Andrew said, SCORM content finds an embedded API object in the browser DOM and uses that to communicate very structured and specific data to an LMS.正如安德鲁所说，SCORM 内容在浏览器 DOM 中找到嵌入的 API object 并使用它来将非常结构化和特定的数据传递给 LMS。 xAPI uses a REST HTTP API to communicate various data in a well defined format. xAPI 使用 REST HTTP API 以明确定义的格式传递各种数据。
Without some creative programming, SCORM typically is content that is delivered via a browser from a Learning Management System to the client.如果没有一些创造性的编程，SCORM 通常是通过浏览器从学习管理系统交付给客户的内容。 Typically that is in the form of HTML, images, videos.通常采用 HTML、图像、视频的形式。 xAPI can be those types of things as well but since the API is HTTP/REST-like, the support of unmanaged content - simulators, phone apps, games - is a little easier. xAPI 也可以是那些类型的东西，但由于 API 是类似 HTTP/REST 的，因此对非托管内容（模拟器、电话应用程序、游戏）的支持要容易一些。
SCORM's data model is very clearly defined in the specification and not normally extended. SCORM的数据model在规范中定义的很清楚，一般不会扩展。 xAPI's data format is defined, but the actual data is much looser and open to the needs of the developer. xAPI的数据格式是有定义的，但实际的数据要宽松得多，对开发者的需求开放。
SCORM has been around since about the year 2000 in various versions. SCORM 大约从 2000 年开始就有各种版本。 It is well supported in LMSs and content development tools.它在 LMS 和内容开发工具中得到很好的支持。 And many in the eLearning space know it.在线学习领域的许多人都知道这一点。 xAPI is newer. xAPI 较新。 Support is growing as well as the number of folks who understand it, but it is still less supported than SCORM.支持以及理解它的人的数量在增加，但它仍然不如 SCORM 得到支持。
One final thing of note, SCORM specs never defined a way to get data out of the LMS once the SCO attempt has ended.最后需要注意的一点是，SCORM 规范从未定义在 SCO 尝试结束后从 LMS 中获取数据的方法。 This made reporting and metrics difficult to do without getting the LMS vendor to build those features in. xAPI defines a GET endpoint to retrieve data (This might not be performant when you might have 100ks to millions of data points, but you can get the data back out - caveats about permissions aside) Some LRS vendors do add reporting and analytics platforms, as well as some adding ways to get your data into BI or data analysis tools.如果不让 LMS 供应商在其中构建这些功能，这使得报告和指标很难完成。xAPI 定义了一个 GET 端点来检索数据（当您可能有 100ks 到数百万个数据点时，这可能不高效，但您可以获取数据退出 - 关于权限的注意事项）一些 LRS 供应商确实添加了报告和分析平台，以及一些将数据导入 BI 或数据分析工具的添加方法。

There's more you'll find as you get into the space but that's some of the things off the top of my head.当你进入这个空间时，你会发现更多，但这是我脑海中的一些事情。

I would recommend you read the xAPI spec first mainly because it is more easily consumed.我建议您先阅读 xAPI 规范，主要是因为它更容易使用。 Then look at SCORM - it has different versions (1.2, 2004 2-4th editions).然后看看SCORM - 它有不同的版本（1.2、2004 年第 2-4 版）。

As for implementing content,至于实施内容，

SCORM: Figure out the version to build to, create the SCOs (content that reports data to the LRS), have that find the API embedded in the HTML dom, use the defined methods (Initialize, Terminate, SetValue, GetValue) to communicate with the LMS, then package it all up in a zip with an XML manifest and support xml schema, deploy to the LMS. SCORM：找出要构建的版本，创建 SCO（向 LRS 报告数据的内容），找到嵌入 HTML dom 中的 API，使用定义的方法（Initialize、Terminate、SetValue、GetValue）进行通信LMS，然后是 package，它全部在 zip 中，带有 XML 清单并支持 xml 架构，部署到 LMS。
xAPI: Create your content, preferably support an xAPI launch mechanism like TinCan Launch , make REST calls to the LRS's xAPI endpoint using something like Fetch or Requests, etc, host/package/deploy as you determine. xAPI：创建您的内容，最好支持像TinCan Launch这样的 xAPI 启动机制，使用 Fetch 或 Requests 等方式对 LRS 的 xAPI 端点进行 883414288 调用，根据您的决定进行主机/打包/部署。

Looking at the specs is the driest but the authoritative way to learn about the different specs.查看规格是了解不同规格的最枯燥但最权威的方式。 There are also some very good articles and videos out there by various vendors and implementors.各种供应商和实施者也提供了一些非常好的文章和视频。

The main technical difference is that SCORM uses a javascript API to communicate between a course in a window or frame wrapped by the LMS.主要的技术差异是 SCORM 使用 javascript API 在 window 或 LMS 包装的框架中的课程之间进行通信。 xAPI uses a restful API to communicate with an LRS over HTTP. xAPI 使用 restful API 通过 HTTP 与 LRS 通信。