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

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

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

<para>
The <sgmltag>Phrase</sgmltag> element in DocBook has no specific semantic.
It is provided as a wrapper around a selection of words smaller than a
paragraph so that it is possible to provide an <sgmltag
class='attribute'>ID</sgmltag> or other attributes for them.
</para>

<para>
For example, if you are making note of changes to a document using one
of the effectivity attributes, you might use <sgmltag>Phrase</sgmltag> to 
mark up specific sentences with revisions.
</para>

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

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


&phrase.parents.gen;
&phrase.children.gen;
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&phrase.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

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

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

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

