|
Please wait ......
IMS Simple Sequencing - Overview
Terms of use
X
Terms of use
These contents have been obtained from the IMS web site and edited for presentation. Please refer to the IMS web site for additional information on terms of use.
Print
IMS Global Learning Consortium
|
The IMS Simple Sequencing Specification defines a method for representing the intended behavior of an authored learning experience such that any learning technology system (LTS) can sequence discrete learning activities in a consistent way. The specification defines the required behaviors and functionality that conforming systems must implement. It incorporates rules that describe the branching or flow of instruction through content according to the outcomes of a learner's interactions with content. The first version of the specification was released to the public in March 2003.IMS Simple Sequencing |
Terms of use
X
These contents have been obtained from the IMS web site and edited for presentation. Please refer to the IMS web site for additional information on terms of use.
Print
Introduction
The "IMS Simple Sequencing Specification" defines a method for representing the intended behavior of an authored learning experience such that any learning technology system (LTS) can sequence discrete learning activities in a consistent way. A learning designer or content developer declares the relative order in which elements of content are to be presented to the learner and the conditions under which a piece of content is selected, delivered, or skipped during presentation.
This specification defines the required behaviors and functionality that conforming systems must implement. It incorporates rules that describe the branching or flow of learning activities through content according to the outcomes of a learner's interactions with content. This representation of intended instructional flow may be created manually or with authoring systems that produce output that conforms to this specification. While learning content developers need to know how to create and describe content sequences, authoring systems may hide the details of the models presented in this specification. The representation of sequencing may be interchanged between systems designed to deliver instructional activities to learners. The components of an LTS used to execute the specified rules and behaviors, when content is delivered to a learner, are referred to in this specification as a 'sequencing engine'.
Simple Sequencing recognizes only the role of the learner and does not define sequencing capabilities that utilize or are dependent on other actors, such as instructors, mentors, or peers. This specification does not prohibit usage in contexts involving other actors; however, it does not define the roles of other actors or sequencing behaviors that result from participation of other actors.
Simple Sequencing is labeled as simple because it includes a limited number of widely used sequencing behaviors, not because the specification itself is simple. Simple Sequencing is not all-inclusive. In particular, Simple Sequencing does not address, but does not necessarily preclude, artificial intelligence-based sequencing, schedule-based sequencing, sequencing requiring data from closed external systems and services (e.g., sequencing of embedded simulations), collaborative learning, customized learning, or synchronization between multiple parallel learning activities. |
Specification Components
The specification includes the formal definition of a set of Behavior Models and Information Models and describes the Overall Sequencing Process as a combination of those models. |
The various steps in the sequencing process
|
|
The different defined models are:- Sequencing Definition Model - The information model in Simple Sequencing used to describe the desired sequencing behavior.
- Tracking Model - The information model in Simple Sequencing used to record information about the results of a learner's interactions with activities, and the learner's record for objectives (e.g., completion, measure) to control the selection and sequencing of other activities.
- Activity State Model - The information model in Simple Sequencing used to record information about the state or status of a learner's interactions with an activity and a set of global attributes for activities.
- Navigation Behavior Model - The Simple Sequencing process that evaluates a navigation request and determines the sequencing and termination requests that should be processed to identify and deliver content to the learner.
- Termination Behavior Model - The Simple Sequencing process that evaluates a termination request to end an attempt on an activity.
- Rollup Behavior Model - The Simple Sequencing process that computes the results data for an activity from the results data from the children of the activity.
- Selection and Randomization Behavior Model - The Simple Sequencing process that selects and reorders a subset of activities.
- Sequencing Behavior Model - The Simple Sequencing process that evaluates a sequencing request in terms of the content model described by the activity tree and determines what actual content object should be delivered to the learner.
- Delivery Behavior Model - The Simple Sequencing process that validates that the learning resources for the identified activity may be delivered, i.e., all of the conditions that apply to the delivery of the content for the activity and attempt still hold.
|
Terms of use
X
These contents have been obtained from the IMS web site and edited for presentation. Please refer to the IMS web site for additional information on terms of use.
Print
General Information
Version: 1.0
Release Date: 3 March 2003
Status: Final Specification
Editors: Mark Norton (IMS), Angelo Panar (ADL)
Electronic Version:
This version of the IMS Simple Sequencing specification is composed of three documents:- IMS Simple Sequencing Information and Behavior Model (HTML)
- IMS Simple Sequencing XML Binding (HTML)
- IMS Simple Sequencing Best Practice and Implementation Guide (HTML)
|
Tracking of changes
This is the first Final Version of the specification. Many changes were made to the first drafts (Public Draft 0.7.5 released in April 2002 and Public Draft 1.0 released in October 2002) in order to resolve various technical issues. |
| First draft of the IMS Simple Sequencing Specification (0.7.5 Public Draft) was released to the public in April 12, 2002. After an intermediate version (1.0 Public Draft), released in October 2002, the first Final Version come into view in March 2003. |
Terms of use
X
These contents have been obtained from the IMS web site and edited for presentation. Please refer to the IMS web site for additional information on terms of use.
Print
Other IMS specifications
The IMS Simple Sequencing Specification is related to other IMS specifications, both complete and in-progress. This specification is intended to be consistent with these other initiatives wherever possible, in order to reduce redundancy and confusion between specifications. The related specifications are:- IMS Content Package Specification - the IMS Simple Sequencing Specification was developed to allow sequencing descriptions to be embedded within a IMS Content Packaging manifest file using the XML namespace extension set aside for IMS Simple Sequencing.
- IMS Question and Test Interoperability Specification - the IMS QTI Specification defines the structures used to support the exchange of question and test data.
- IMS Reusable Definition of Competency or Educational Objective Specification - the IMS RDCEO Specification defines structures which allow competency and educational objectives to be defined in a simple and interoperable manner.
- IMS Learning Design Specification - the Learning Design Specification provides information about learning resources, learning roles, and high level sequencing.
|
Advanced Distributed Learning (ADL) Initiative
The Advanced Distributed Learning Co-labs (ADL) are developing an application profile for the training needs of their community which includes Simple Sequencing and defines extensions to it to handle navigation requests, user interface interactions, specifications for communication between client and server, and other considerations. |
|