<refentry id="question.element" revision='3.1'>
<?dbhtml filename="question.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

<refmeta>
<indexterm><primary>elements</primary>
<secondary>question</secondary></indexterm>
<refentrytitle>question</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>question</refname>
<refpurpose>&question.purpose;</refpurpose>
</refnamediv>

&question.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>

<para>
A <sgmltag>Question</sgmltag> in a <sgmltag>QandAEntry</sgmltag> poses a question or
states a problem that is addressed by the following <sgmltag>Answer</sgmltag>(s).
<sgmltag>Answer</sgmltag>s are optional (some questions
have no answers) and may be repeated (some questions have more than
one answer).
</para>

<refsect2><title>Processing expectations</title>
<para>
<sgmltag>Question</sgmltag>s are frequently introduced with a label,
such as <quote>A:</quote>. If a <sgmltag>Question</sgmltag> has a
<literal>Label</literal> child element, the content of that
<sgmltag>Label</sgmltag> is used as the label for the
<sgmltag>Question</sgmltag>. The <sgmltag
class='attribute'>DefaultLabel</sgmltag> attribute on the nearest
ancestor <sgmltag>QandASet</sgmltag> of a <sgmltag>Question</sgmltag>
can be used to indicate that a processing application should
automatically generate a label for the <sgmltag>Question</sgmltag>.
</para>
</refsect2>


&question.parents.gen;
&question.children.gen;
</refsect1>
<refsect1><title>Examples</title>

&question.example.seealso.gen;
</refsect1>
</refentry>


