ModSax Suggestion

[MikeDacon at aol.com]

Hi Dave,

In a message dated 3/5/99 5:40:50 PM Eastern Standard Time, db at eng.sun.com
writes:
> Interesting suggestion for a big hole in the parts of
>  the Java API set that are more or less "standard" at
>  this poit -- SAX and DOM.
>  
>  One comment though:  I've found that it's important to
>  be able to have options controlling how the DOM tree is
>  built.  For example, whether to discard ignorable spaces,
>  or do namespace conformance enforcement, or try to get
>  CDATA sections (comments, etc).
>  

I agree with that.  I think all that is possible while still retaining 
a minimalist design philosophy.  Something like:

void setDOMFeature(String feature, boolean val);
boolean get DOMFeature(String feature);

That way via an extensible common set of text properties we
can add properties as the need arises without expanding the API.

Looking forward to progress on the Java XML API.  BTW, Dave,
are you going to do a "Birds of a Feather" session on XML at this years
JavaOne?  I think that could be valuable.

Best wishes,

 - Mike
-----------------------------------------------
Michael C. Daconta
Author of Java 2 and JavaScript for C/C++ Programmers
Author of C++ Pointers and Dynamic Memory Management
Sun Certified Java Programmer and Developer
http://www.gosynergy.com


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/ and on CD-ROM/ISBN 981-02-3594-1
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)