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

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

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

<para>
While <sgmltag>Glossary</sgmltag>s are usually limited to component or section
boundaries, appearing at the end of a <sgmltag>Book</sgmltag> or <sgmltag>Chapter</sgmltag>,
for instance, <sgmltag>GlossList</sgmltag>s can appear anywhere that the other
list types are allowed.
</para>

<para>
Using a <sgmltag>GlossList</sgmltag> in running text, instead of a
<sgmltag>VariableList</sgmltag>, for example, maintains the semantic
distinction of a Glossary. This distinction may be necessary if you
want to automatically point to the members of the list with
<sgmltag>GlossTerm</sgmltag>s in the body of the text.
</para>

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


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

<informalexample role="example-source">
<programlisting>&glosslist.example.1.txt;</programlisting>
</informalexample>

<anchor id="ex.os.glosslist.1" role="HACK-ex.out.start"/>
&glosslist.example.1.gen;
<anchor id="ex.oe.glosslist.1" role="HACK-ex.out.end"/>

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

