<steps>

The <steps> element provides the main content of a task topic. The task is described as a series of steps that the user must follow to accomplish the task. At least one <step> element is required inside the <steps> element.

Steps with only a single step might be rendered as a paragraph rather than as a list. Two or more steps should typically be rendered as an ordered list. If all of the contained steps are simple (that is, have no more than a <cmd> element each) then the step list should default to compact. Otherwise it should be rendered as expanded (with blank lines between each step).

Content models

See appendix for information about this element in OASIS document type shells.

Inheritance

- topic/ol task/steps

Example

This section is non-normative.

<task id="sqlj">
<title>Creating an SQLJ file</title>
 <taskbody>
 <context>Once you have set up SQLJ, you need to create a new SQLJ file.</context>
  <steps>
   <step>
    <cmd>In a text editor, create a new file.</cmd>
   </step>
   <step>
    <cmd>Enter the first query statement.</cmd>
   </step>
  </steps>
 </taskbody>
</task>

Content model

(<data> | <data-about>)*, (<stepsection>?<step>)+

Contained by

<taskbody>

In order
  1. Zero or more of the following
    • <data>
    • <data-about>
  2. One or more Optional <stepsection>
    1. <step>

Contained by

  • <taskbody>

Inheritance

- topic/ol task/steps

The <steps> element is specialized from <ol>. It is defined in the task module.

Attributes

The following attributes are available on this element: Universal attribute group and outputclass.