<result>
The <result> element describes the
expected outcome for the task as a whole.
Rendering expectations
Implementations might want to consider having their stylesheets render a label for this element.
Specialization hierarchy
The <result> element is specialized from <section>.
It is defined in the task module.
Content model
(Text | <audio> | <dl> | <div> | <example> | <fig> | <image> | <lines> | <lq> | <note> | <object> | <ol> | <p> | <pre> | <simpletable> | <sl> | <table> | <ul> | <video> | <cite> | <include> | <keyword> | <ph> | <q> | <term> | <text> | <tm> | <xref> | <data> | <foreign> | <draft-comment> | <fn> | <indexterm> | <required-cleanup>)*
Contained by
- Text
<audio><cite><data><div><dl><draft-comment><example><fig><fn><foreign><image><include><indexterm><keyword><lines><lq><note><object><ol><p><ph><pre><q><required-cleanup><simpletable><sl><table><term><text><tm><ul><video><xref>
Contained by
Inheritance
- topic/section task/result
The <result> element is specialized from <section>. It is defined in the task module.
Attributes
The following attributes are available on this element: universal attributes.
The following attributes are available on this element: universal attributes.
Example
This section is non-normative.
In the following code sample, the author clearly communicates the expected result of successfully completing the task:
<task id="sqlj">
<title>Creating an SQLJ file</title>
<taskbody>
<!-- ... -->
<result>The <wintitle>File Created<wintle> window is displayed, and the SQLJ
file is successfully created.
</result>
</taskbody>
</task>