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

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

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

<para>
<sgmltag>Callout</sgmltag>s, such as numbered bullets, are an annotation mechanism.  In an
online system, these bullets are frequently <quote>hot,</quote> and clicking on
them sends you to the corresponding annotation.
</para>
<para>
A <sgmltag>GraphicCO</sgmltag> is a wrapper around an <sgmltag>AreaSpec</sgmltag> and
a <sgmltag>Graphic</sgmltag>.  An <sgmltag>AreaSpec</sgmltag> identifies the locations
(coordinates)
on the <sgmltag>Graphic</sgmltag> in which the callouts occur.
The <sgmltag>GraphicCO</sgmltag> may also contain the list of annotations in
a <sgmltag>CalloutList</sgmltag>, although the <sgmltag>CalloutList</sgmltag> may also
occur outside of the wrapper, elsewhere in the document.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block;
</para>
<para>
The mandatory processing expectations of a <sgmltag>GraphicCO</sgmltag> are
minimal: a system is expected to render the graphic, if possible, and the
callout list, if present.
</para>
<para>
In online environments, the processing system may be able to instantiate
the linking relationships between the callout marks on the graphic and
the annotations.  For example, an &HTML; presentation system might use the
coordinate information to construct a client-side image map.
Some processing systems may even be able to go a step further and generate
the callout marks automatically from the coordinate information.
But this level of sophistication is not mandatory.
</para>
</refsect2>

<refsect2 role='fu' revision="5.0"><title>&FutureChanges;</title>
<para>
<indexterm><primary>DocBook DTD</primary><secondary>Changes for <acronym>V5.0</acronym></secondary>
</indexterm>
In DocBook <acronym>V5.0</acronym>, <sgmltag>GraphicCO</sgmltag> will be discarded. In its
place, use <sgmltag>MediaObjectCO</sgmltag>.
</para>
</refsect2>


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

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

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

