I think there is a third possibility, where the objects in the DOM tree
are wrappers for application objects. These wrapper objects, then,
are responsible for connecting the data held by the DOM with the
processing capabilities of the application objects.
The wrappers serve as the glue that lets us preserve the reusability
of application components, allows them an independent inheritance,
and maintains their independence from the XML markup.
Creation of such wrappers could be driven by the XSchema for the
markup language and reflection on the application classes, but should
accept input to support non-obvious mappings.
This is what I'm trying to drive towards with coins.
Bill