Namespace: |
|
Type: |
|
Content: |
complex, 10 attributes, 11 elements |
Defined: |
globally in taskMod.xsd; see XML source |
Includes: |
declaration of 1 attribute |
Referenced: |
by 1 location |

XML Representation Summary |
|||||||||||||||||||||||||||||||
<taskbody |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
> |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
</taskbody> |
|||||||||||||||||||||||||||||||
Attribute |
Type / Value |
Default |
Required? |
Declared In |
Description |
|
xs:string
|
no |
||||
|
xs:string
|
no |
||||
|
xs:NMTOKEN
|
no |
||||
|
xs:string
|
no |
||||
|
yesno-att.class : ("yes" | "no" | "-dita-use-conref-target")
|
no |
||||
|
xs:language
|
no |
In due course, we should install the relevant ISO 2- and 3-letter codes as the enumerated possible values . . .
|
|||
|
dir-atts.class : ("ltr" | "rtl" | "lro" | "rlo" | "-dita-use-conref-target")
|
no |
||||
|
xs:string
|
no |
||||
|
xs:string
|
no |
||||
|
xs:string
|
"- topic/body task/taskbody " |
no |
The class attribute supports specialization. »
|
Component |
Type / Value |
Occurs |
Nillable? |
Declared In |
Description |
|
1..1 |
||||||
0..1 |
no |
The pre-requisite (<prereq>) section of a task should document things the user needs to know or do before starting the current task. »
|
||||
0..1 |
no |
The <context> section of a task provides background information for the task. »
|
||||
0..1 |
||||||
1..1 |
no |
The <steps> section of a task provides the main content of the task topic. »
|
||||
1..1 |
no |
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. »
|
||||
0..1 |
no |
The <result> element describes the expected outcome for the task as a whole.
|
||||
0..1 |
no |
The <example> element is a section with the specific role of containing examples that illustrate or support the current topic. »
|
||||
0..1 |
no |
The <postreq> element describes steps or tasks that the user should do after the successful completion of the current task. »
|
||||
0..∞ |
||||||
1..1 |
no |
The <data> element represents a property within a DITA topic or map. »
|
||||
1..1 |
no |
The <data-about> element identifies the subject of a property when the subject isn't associated with the context in which the property is specified. »
|
||||
1..1 |
no |
The <foreign> element is an open extension that allows information architects to incorporate existing standard vocabularies for non-textual content. like MathML and SVG, as inline objects. »
|
||||
1..1 |
no |
The <unknown> element is an open extension that allows information architects to incorporate xml fragments that does not necessarily fit into an exisitng DITA use case. »
|
||||
|
Type Derivation Tree
taskbody.class (extension)
|
XML schema documentation generated with FlexDoc/XML 1.15 using FlexDoc/XML XSDDoc 3.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit. |