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

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

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

<para>
The notion of a <sgmltag>Property</sgmltag> is very domain-dependent in computer
documentation.  Some object-oriented systems speak of properties; the
components from which <acronym>GUI</acronym>s are constructed have properties;
and one can speak of properties in very general terms; <quote>the properties
of a relational database.</quote>
</para>

<para>
You might use <sgmltag>Property</sgmltag> for any of these in your documentation.
</para>

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

<refsect2 role='fu' revision="4.0"><title>&FutureChanges;</title>
<para>
The content model of <sgmltag>Property</sgmltag> will be constrained to
<literal>(#PCDATA | Replaceable | InlineGraphic)</literal> in DocBook <acronym>V4.0</acronym>.
</para>
</refsect2>


&property.parents.gen;
&property.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>Property</sgmltag>.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&property.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

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

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

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

