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

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

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

<para>
The <sgmltag>Term</sgmltag> in a <sgmltag>VarListEntry</sgmltag> identifies the 
thing that is described or defined by that entry.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block; <sgmltag>Term</sgmltag>s are usually formatted to make
them stand out with respect to the text that follows. The best
presentation depends on several factors, including the number
and length of the terms.  The <sgmltag
class='attribute'>TermLength</sgmltag> attribute on the containing
<sgmltag>VariableList</sgmltag> may influence the presentation of
<sgmltag>Term</sgmltag>s.  See <sgmltag>VariableList</sgmltag>.
</para>
</refsect2>

<refsect2 role='fu' revision="4.0"><title>&FutureChanges;</title>
<para>
<!--do not index this occurance-->
&fu.interfacedefinition;
</para>
</refsect2>


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

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

