Should AtkDocument use GdomeDocument ?

[Bill Haneman <bill haneman ireland sun com>]

Hi:

I think that we have completed our definitions of interfaces needed
for accessibility support, with one exception: we have received much
support for an AtkDocument interface that exposes a w3c-type DOM, for
those accessible components that naturally deal with DOMs internally
such as widgets displaying XML/HTML content, possibly others. 
Probably an HTML plugin of any sort will want to implement
AtkDocument, the Mozilla gecko engine will export something that will
be bridged to the same interface in the GNOME Accessibility SPI.

So, my question has to do with the best way to do this in GTK+.  I am
a little reluctant to introduce a dependency on gdome, though gdome
seems the natural way of exposing DOM in Gnome.  I am soliciting
opinions on how we should define the datatypes and methods in
AtkDocument - if we had access to a C definition of DOM, we could just
have a single method, getDocument (), and have all the rest of the
functions defined elsewhere.  I suppose my question is, what level of
dependency on gdome2 is deemed acceptable, should we use libxml2
instead (somehow?), and to the extent that we need to hide our use of
gdome2 in our implementation library, how can we do this in the ATK+
headers ?

TIA,

Bill


--------------
Bill Haneman
Gnome Accessibility / Batik SVG Toolkit
Sun Microsystems Ireland