This is an overview for the entire Learning Object. It is a specialization of a DITA concept called slscontext. It is an overview of all the content in the Learning Object. Since its purpose is to support the instruction of this learning object (as opposed to providing the instruction itself), this overview is an instructional object.
The content of the learning object should be so small and focused that you only need one objective and that objective gets authored here in the overview topic. So here it is:
After completing this section you will be able to:
This is a DITA concept information object that contains training content in support of objected of the overall Learning Object. It is an standard DITA concept topic; it is not a specialization of any DITA topic. It is a sibling information object to the others inside this Learning Object. It is sequenced as it needs to be for training flow in the information object set inside this Learning Object.
The high level course structures used in the SLS CMS define the size, shape and contents of the training deliverable. The figure shows these structures graphically and subsequent sections in this learning object will speak about some of the details.
The data model or markup used for structuring the training content of SLS CMS is that of the Darwin Information Type Architecture (DITA) 1.1.
DITA uses the term map for that XML model that collects child components which are references to topics or other (sub) maps. SLS is using two specializations of a DITA map. The top level map is called an slstdmap and defines a training deliverable (TD). The other map speciaization is to wrap a Learning Object and is called an slslearningobj. Call the top level slstdmap a chunk, or a course, a training deliverable or a TD (touchdown). Whatever term you use, it needs to be 4 hours or less in length.
As you see in the figure the slstdmap contains child groupings (<topicgroup>s) that contain pointers (using <topicref> elements) to the Learning Objects themselves. You might think of these <topicgroup>s as legacy ILT modules because they are units aggregated as a course and they themselves also collect smaller Learning Objects, which are now considered to be legacy ILT enabling objective sized content pieces.
It is important to point out the <topicref> pointing to the exercise in the topic group. These are analogous to the legacy end-of-module hands on lab exercises. They are different than the Practice <task> inside the Learning Object. (The practice task will be explained later, but for now remember it as a non-hands-on activity).
This is an information object because it contains actual training content (not support for training). It is a task or procedural in nature. It should never contain any sub tasks. If this task needs sub tasks to support it, this prerequisite relationship gets expressed in the TD map by nesting a <topicref> inside another <topicref>. The Cleaning Your Framitz task is simply another task contributing to the objective of this Learning Object.
The context of this task, Cleaning Your Framitz, would be set here followed by the steps involved with the cleaning procedure. So you might say ... The Framitz is such an integral part of your equipment, and it is so vulnerable to harsh environmental conditions, that you should develop a habit of routine maintenance and cleaning.
Perform the following steps to clean your framitz:
This is another information object which contains training content that is task or procedural in nature.
The context of this task, Replacing FRUs and CRUs, would be set here followed by the steps involved with this procedure. For example ...
As you clean your framitz you may learn that some of its FRUs and CRUs need to be replaced.
Although the new CMS system supports reuse of content at ant level, best practices indicates that reuse should be confined to just a few cases. These recommended cases are based on anticipated TD and topic repackaging scenarios.
There are three recommended levels or granularities for reuse, each serving a different purpose:
It is important to emphasize that in order for something to be reused, it must standalone and make sense instructionally. Although by nature of its part in a larger assembly, it is related to its sibling components in the assembly, it must not strictly depend on anything outside of itself for it to be successful as a training component.
Reuse at the LO level and above should be to goal.
This is a DITA reference topic. References are typically figures or tables that you anticipate reusing often. It is just another information object contributing to the overall learning integrity of this Learning Object.
The figure shows the composition of the a training deliverable and its component learning objects. Notice that the <map> element bounds all the content of the training deliverable, or chunk, and should be 4 hours or less when delivered.
This is a DITA concept or an SLS specialization of same. It supports the learning by summarizing the content of the entire Learning Object. OASIS DITA learning specialization is tending toward calling this a Summary.
The summary information for this Learning Object would be authored here.
This is another instructional object in support of the learning in this Learning Object. It is a set of paper-based exercises or activities that covers the content of the Learning Object and, as such, is not like a legacy end-of-module exercise. It is much smaller, maybe akin to a subset of the steps of a legacy end-of-module exercise but not in a hands-on environment. OASIS DITA learning specialization is tending toward calling this a Practice and so shall we to differentiate it from an exercise, the legacy end-of-module exercise that is outside any particular Learning Object. It is the hands-on activity requiring a lab environment. This larger exercise is referenced (using a topicref in the larger collection of Learning Objects in the <topicgroup> part of the course map. The activity it covers spans all the content of the Learning Objects of this topicgroup.
This is an optional instructional object, simulating the task procedures. It is a DITA concept or an SLS specialization of same.
The simulation itself would be authored here.
This is an optional instructional object, demonstrating some aspect of the LO's conteent.. It is a DITA task or an SLS specialization of same.
This is a DITA task or an SLS Specialization of same. It is a required instructional object in support of the learning of this Learning Object. It contains assessment questions covering all the content of this Learning Objective.
