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

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

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

<para>
Every <sgmltag>Msg</sgmltag> has one primary message (<sgmltag>MsgMain</sgmltag>).
It may also have any number of related messages, stored in
<sgmltag>MsgRel</sgmltag> elements within the same <sgmltag>Msg</sgmltag>.
</para>
<para>
Related messages are usually messages that appear elsewhere in
response to the same event (or set of events) that triggered
the main message. For example, if a network client
produces a failure or warning message, a related message might
appear on the server console.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.context; &format.csuppress;
</para>
<para>
On the whole, the semantics of <sgmltag>MsgSet</sgmltag>
are not clearly defined.
</para>
</refsect2>


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

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

