Training: when you need to learn, how do you want to control what you get?
Bruce Esrig and John Hunt
Background
The OASIS DITA XML markup standard provides topic types such as concept, task and reference. We're looking at how to support training, inspired by the CISCO model of Reusable Learning Objects (lessons) that contain Reusable Information Objects (topics). Courses consist of modules, which consist of lessons, which consist of (groups of) topics.
Well, that's nice and structured. But enter the user ... how do they want to access and view the critical learning content they need? Is it tied to an interface? Do you go to a special browser? What controls are needed to access the right learning content? How much customization is needed, and how much memory about what the user has learned before?
Sources
Ideas
Is the SCORM model any help? The SCORM 2004 3rd Edition Documentation Suite public draft contains a set of PDFs, including a relatively brief SCORM_2004_Overview.pdf. (http://www.adlnet.gov/downloads/files/290.cfm)
Basically, the SCORM specification describes the following:
- A Content Aggregation Model (CAM), which specifies the assembling, labeling, and packaging of learning content for SCORM.
- A Run-Time Environment (RTE), which specifies the API and other methods used to launch content, communicate, track, and transfer learning data to and from the LMS.
- Sequencing and Navigation (SN), which describes sequencing and navigation characteristics, including Activity Tree, Learning Activitiies, and how to assemble content in the manifest to support them.