DITA Resource Center

<taskbody>

The <taskbody> element is the main body-level element inside a task topic. A task body is designed to contain information specific to completing a task, such as prerequisites, contextual information, and steps. DITA 1.2 introduced a much looser <taskbody> content model in order to allow for more variations in the structure of a task. A constraint module was also provided in order to maintain compatibility with the previous strict model; this constraint is used in the default task distributed by OASIS.

note

Beginning with DITA 1.2, the DTD and Schema packages distributed by OASIS contain two task models. The general task model allows two additional elements inside the task body (<section> and <steps-informal>); it also allows multiple instances and varying order for the <prereq>, <context>, and <section> elements. The strict task model maintains the order and cardinality of the DITA 1.0 and 1.1 <taskbody> content model. This strict task is implemented with a constraint module.

Authors that use the default task DTD or Schema provided by OASIS will continue to see the strict task model when upgrading to DITA 1.2 or DITA 1.3. Authors wishing to use the general task model will need to migrate their DITA 1.1 documents to reference the general task document type shell.

DITA document type shells that include the task module as-is, or that specialize the <task> element without specializing <taskbody>, will also need to include the strict taskbody constraint module in order to maintain the order and cardinality of prior DITA versions.

Task specializations that specialize the <taskbody> element will not be affected by the new model, although they can be updated as needed to take advantage of the new elements.

Content models

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

Inheritance

- topic/body task/taskbody

Example

See <task>.

Attributes

The following attributes are available on this element: Universal attribute group (without the Metadata attribute group), @base from the Metadata attribute group, and @outputclass.

Was this page helpful?