<steps-unordered>

Like the <steps> element, the <steps-unordered> element provides the main content of a task topic, but particularly for cases in which the order of steps might vary from one situation to another. At least one <step> element is required inside the <steps-unordered> 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 unordered 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 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/ul task/steps-unordered

The <steps-unordered> element is specialized from <ul>. It is defined in the task module.

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-unordered>
   <step><cmd>In a text editor, create a new file.</cmd></step>
  </steps-unordered>
 </taskbody>
</task>

Attributes

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