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

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

&errortype.synopsis.gen;

<refsect1 condition='ref.description'><title>Description</title>

<para>The <sgmltag>ErrorType</sgmltag> element identifies a class of error.  The
exact classifications are naturally going to vary by system, but
<quote>recoverable</quote> and <quote>fatal</quote> are two possibilities.
</para>

<para>DocBook provides four elements for identifying the parts of an error message:
<sgmltag>ErrorCode</sgmltag>, for the alphanumeric error code (e.g., <quote>-2</quote>);
<sgmltag>ErrorName</sgmltag>, for the symbolic name of the error
(e.g., <quote>ENOENT</quote>);
<sgmltag>ErrorText</sgmltag>, for the text of the error message (e.g., <quote>file
not found</quote>); and
<sgmltag>ErrorType</sgmltag>, for the error type (e.g., <quote>recoverable</quote>).
</para>

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


&errortype.parents.gen;
&errortype.children.gen;
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&errortype.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

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

