Like the <steps> element, the <steps-unordered> section of a task provides the main content of the task topic, but particularly for cases in which the order of steps may vary from one situation to another. One or more steps is required inside the <steps-unordered> section.
Two or more steps appear as an unordered 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 list should default to compact. Otherwise it should be formatted as uncompact (with blank lines between each step on output).
<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>
|ditabase, task||( ( step) (one or more) )|
- topic/ul task/steps-unordered
|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|
Return to main page.
OASIS DITA Version 1.1 Language Specification -- OASIS Standard, 1 August 2007
Copyright © OASIS Open 2005, 2007. All Rights Reserved.