简体   繁体   English

iframed 内容是否通过 SCORM / xAPI 与 LMS 通信?

[英]Iframed content communicate with LMS via SCORM / xAPI?

Having worked with e-learning authoring tools in the past, I'm a bit familiar with SCORM but not in great detail, and recently have heard of Tin Can / xAPI.过去使用过电子学习创作工具,我对 SCORM 有点熟悉,但不是很详细,最近听说过 Tin Can / xAPI。 In how those often relate to LMS's, I'm familiar with the concept of uploading a zipped learning object that has the code needed to communicate w/the LMS to record completions, scores, and so forth via the SCORM / xAPI specs.在这些通常与 LMS 的关系中,我熟悉上传压缩学习对象的概念,该对象具有与 LMS 通信所需的代码,以通过 SCORM / xAPI 规范记录完成、分数等。

I'm wondering whether a different setup is possible: if an LMS is said to support SCORM and/or xAPI, can a custom-programmed learning object at a URL external to an LMS (ie not an uploaded zip), typically communicate w/the LMS equally well, such as via displaying the learning object in an iframe and the learning object having SCORM or xAPI calls to the parent window?我想知道是否可以使用不同的设置:如果说 LMS 支持 SCORM 和/或 xAPI,则可以在 LMS 外部的 URL(即不是上传的 zip)上的自定义编程学习对象,通常与LMS 同样好,例如通过在 iframe 中显示学习对象和对父窗口具有 SCORM 或 xAPI 调用的学习对象? My hunch is yes, because I believe the uploaded-zip route utilizes iframes, but having little experience in custom-programming SCORM / xAPI integrations, I don't know if there's something I'm missing about cross-domain issues, limitations on SCORM / xAPI specs perhaps, etc.我的预感是肯定的,因为我相信上传的 zip 路由使用了 iframe,但是在自定义编程 SCORM / xAPI 集成方面的经验很少,我不知道我是否遗漏了跨域问题、SCORM 的限制/ xAPI 规范,等等。

If it is possible, any tips or gotchas are welcome.如果可能,欢迎提供任何提示或陷阱。

For comparable use with xAPI as the communication protocol I'd recommend considering the cmi5 profile .对于与 xAPI 作为通信协议的类似使用,我建议考虑cmi5 profile It is intended specifically for the packaging and LMS launch scenario while leveraging xAPI as its data storage and communication mechanism.它专门用于打包和 LMS 启动场景,同时利用 xAPI 作为其数据存储和通信机制。

cmi5 provides for a mechanism to launch into remotely hosted content (AU) and provides via the launch URL enough information then to communicate back to the LMS/LRS in a cross origin way. cmi5 提供了一种启动远程托管内容 (AU) 的机制,并通过启动 URL 提供足够的信息,然后以跨源方式与 LMS/LRS 通信。 xAPI is itself compatible with this approach assuming the LRS can provide the correct CORS headers (most do). xAPI 本身与这种方法兼容,假设 LRS 可以提供正确的 CORS 标头(大多数都可以)。

SCORM does not generally work (natively) in this type of setup because it is based on a JavaScript API that must be made accessible to the content itself which generally can't be accessed across different origins. SCORM 在这种类型的设置中通常(本地)不起作用,因为它基于 JavaScript API,必须使内容本身可以访问,而内容本身通常无法跨不同来源访问。 There are ways around this, but they are supplements to the core specification.有很多方法可以解决这个问题,但它们是对核心规范的补充。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM