<refentry id="partintro.element">
<?dbhtml filename="partintro.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

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

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

<para>
<sgmltag>PartIntro</sgmltag> contains introductory text, often an overview
of the content of the <sgmltag>Part</sgmltag>.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block; &format.csuppress;
</para>
<para><sgmltag>PartIntro</sgmltag> content is often printed on a part
separator page.
</para>
</refsect2>


&partintro.parents.gen;
&partintro.children.gen;
</refsect1>
<refsect1 condition='ref.elem.attrdesc'><title>Attributes</title>
<variablelist>
<varlistentry><term>label</term>
<listitem>
<para>
<sgmltag class='attribute'>Label</sgmltag> specifies an identifying string for presentation purposes.
</para>
<para>
Generally, an explicit <sgmltag class='attribute'>Label</sgmltag> attribute is
used only if the processing system is incapable of generating the label
automatically. If present, the <sgmltag class='attribute'>Label</sgmltag> 
is normative; it will used even
if the processing system is capable of automatic labelling.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&partintro.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

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

