StepsThe <steps> section of a task provides
the main content of the task topic. The task is described as a series of steps
that the user must follow to accomplish the task. One or more <steps>
elements is required inside the <steps> section.
Two or more steps appear as an ordered list. A single step appears
as a paragraph. 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 formatted as uncompact (with blank lines between
each step on output).
[edit] Example
<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>
[edit] Contains
| Doctype
| Content model
|
| ditabase, task
| ( (
step) (one or more) )
|
[edit] Contained by
[edit] Inheritance:
- topic/ol task/steps
[edit] Attributes
| Name
| Description
| Data Type
| Default Value
| Required?
|
| %univ-atts; (%select-atts;, %id-atts;, %localization-atts;)
| A set of related attributes, described at %univ-atts;
| parameter entity
| PE not
applicable
| Not applicable
|
| %global-atts; (xtrf, xtrc)
| A set of related attributes, described at %global-atts;
| parameter entity
| PE not
applicable
| Not applicable
|
| class, outputclass
| Common attributes described in Other common DITA attributes
|
|
|
|
TOC: Language Specification 1.1
Parent topic: Task elements
Previous topic: context
Next topic: steps-unordered
|
|
