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

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

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

<para>
<sgmltag>Hardware</sgmltag> identifies some physical component of a computer system.
Even though DocBook provides a broad range of inlines for describing the various
software components of a system, it provides relatively few for describing
hardware.
</para>
<para>
If you need to identify a number of different hardware components,
you may wish to consider extending DocBook, or at least using the
<sgmltag class="attribute">Role</sgmltag> attribute to further classify
<sgmltag>Hardware</sgmltag>.
</para>

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

<refsect2 role="fu" revision="4.0"><title>&FutureChanges;</title>
<para>
<indexterm><primary>DocBook DTD</primary><secondary>Changes for <acronym>V4.0</acronym></secondary>
</indexterm>
In DocBook <acronym>V4.0</acronym>, the content model of <sgmltag>Hardware</sgmltag> will
be constrained to <literal>(#PCDATA | Replaceable |
InlineGraphic)</literal>.
</para>
</refsect2>


&hardware.parents.gen;
&hardware.children.gen;
</refsect1>
<refsect1 condition='ref.elem.attrdesc'><title>Attributes</title>
<variablelist>
<varlistentry><term>moreinfo</term>
<listitem>
<para>
If <sgmltag class='attribute'>MoreInfo</sgmltag> is set to <literal>RefEntry</literal>,
it implies that a <sgmltag>RefEntry</sgmltag> exists which further describes the
<sgmltag>Hardware</sgmltag>.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&hardware.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

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

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

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

