Bjoern Martin wrote: > For me it's in fact interesting as well. If I write an xml document > and convert it to another xml document, I'd appreciate it if my way of > writing empty tags would be kept as is. Just to keep it easy to read > for me.
The real discussion is whether XNI (which notifies the handlers of the XML Information Set items) should allow the handler to produce: 1) an equivalent document, 2) an equal document, or 3) something in between. To support case 1, we don't need the "emptyElement" callback. Right now, XNI is case 3. And supporting case 2 would cause the handlers method count to explode which is probably not reasonable for Xerces2. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
