This article is dauntingly technical, but it's a great read, clearly illustrating why SCORM cannot be deployed in a multi-domain environment. In a nutshell, the SCORM API interfaces (commonly known as the 'wrapper') require that the learning object and the LMS communicate with each other using Javascript or a similar technology. But security restrictions have for the last decade prohibited cross-domain communication between these scripts. So SCORM won't work across domains. As Stephen Lanahas comments, "More importantly though, the architectural aproach of SCORM actually prevents utilization of distributed content repositories across organizations / enterprises, more or less killing the B2B potential for the entire technology in question (Learning Onjects)." It's a rookie mistake and I'm surprised it got through the technical reviews. But the solution outlined in this paper is straightforward: as AICC does, use HTTP calls to establish communications between the learning object and the LMS. Simple. Too simple, apparently, for SCORM.
Today: 4 Total: 90 [Direct link] [Share]
