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

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

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

<para>Reference pages have their own hierarchical structure. A
<sgmltag>RefSection</sgmltag> is a recursive division in a
<sgmltag>RefEntry</sgmltag>, analagous to a <sgmltag>Section</sgmltag> elsewhere
in the document.
</para>

<para>
The value of a separate hierarchical structure is that it allows
the content model of sections in reference pages to be
customized differently than the content model of sections
outside.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block;
</para>
</refsect2>

&refsection.parents.gen;
&refsection.children.gen;

</refsect1>

<refsect1 condition='ref.elem.attrdesc'><title>Attributes</title>
<variablelist>
<varlistentry><term>status</term>
<listitem>
<para><sgmltag class="attribute">Status</sgmltag> identifies the editorial or publication 
status of the <sgmltag>RefSection</sgmltag>.
</para>
<para>Publication status might be used to control formatting (for example,
printing a <quote>draft</quote> watermark on drafts) or processing (perhaps
a document with a status of <quote>final</quote> should not include any
components that are not final).
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&refsection.seealso.gen;
</refsect1>
</refentry>

