XObjects

[Graham Moore]

bill wrote >

> But aside from SaxInput and SaxException, do we really want to mandate the
> use of SAX events? If we can find a way around that particular mandate,
> then we allow a tighter coupling between the parser and DOM construction,
> and allow for a more complete extraction of information from the document.

I think you are suggesting a tighter binding - thus more open - with parser 
events as opposed to SAX events?

I think this would be good, along the lines of more granularity, more 
control more refined implementations.

>This is where wrappers and delegation have something to offer. As long as
> the wrapper or a mixin of the aggregate are responsible for the events,
> only that code which handles the events need be vendor-specific:

>        Simple application code that implements Element can be in
>        the DOM tree directly, but would not have access to parse events.

>        Application code held by a wrapper or participating in an
>        aggregate would support an api or a design pattern (which
>        is to say, JavaBeans), which benefits indirectly from parse events.

I think where this leads us is to a situation where an application is 
effectively a LISP evaluator and the XML has become an S-Expression.

But to keep things simple the parse events should for the moment be used to 
build the DOM and its mixed-in functionality. The app thens invokes methods 
on the functional DOM.

I like the idea that XML is LISP though.

> I believe it is appropriate to support the alternatives here via the
> Bindings
> specification, on a per-element basis.
> Further, the application should be able to select different domBuilder's
> from different vendors and use them all together.

Yes and Yes.

I know this list is primarily for views but we need some confirmation of 
what we think is good or else it appears that there is no agreement and no 
common ground.

graham.

gdm at dpsl.co.uk





xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)