DefiningImageAccess/Standard/SCORM
From ImageWeb
| DefiningImageAccess/Standard/SCORM | |
|---|---|
| Link:=http://www.adlnet.gov/scorm/index.cfm}} | |
| Status:=Active}} | |
| JISCProject:=False}} | |
| Focus:=Describing Digital Objects}} | |
| [[ReferencedBy::{{{ReferencedBy}}}]]}} | |
| [[PublishedBy::{{{PublishedBy}}}]]}} | |
| [[UsedBy::{{{UsedBy}}}]]}} | |
| [[DescribedBy::{{{DescribedBy}}}]]}} | |
| [[Partner::{{{Partner}}}]]}} | |
| [[Contact::{{{Contact}}}]]}} | |
SCORM
Shareable Content Object Reference Model
"... a collection of standards and specifications for web-based e-learning. It defines communications between client side content and a host system called the run-time environment (commonly a function of a learning management system). SCORM also defines how content may be packaged into a transferable ZIP file.
SCORM is a specification of the Advanced Distributed Learning (ADL) Initiative, which comes out of the Office of the Secretary of Defense."
SCORM claims to be a collection of existing web standards, selected and profiles to support the requirements of learning objects, by which I assume the mean online courses and training material. From the SCORM overview document, these underlying standards appear to be:
- IEEE Data Model For Content Object Communication
- IEEE ECMAScript Application Programming Interface for Content to Runtime Services Communication
- IEEE Learning Object Metadata (LOM)
- IEEE Extensible Markup Language (XML) Schema Binding for Learning Object Metadata Data Model
- IMS Content Packaging
- IMS Simple Sequencing.
The only one of these that appears to have any remote bearing on our work is the Learning Object Model XML binding. Overall, I find the specification reeks of committee over-design and form-filling, and very little on communicating the essential technical ideas (as one might expect from a military/government sponsored project).
