Libor Kramolis wrote: > I would like to ask you, what did you mean by that. Do you have any proposal > or plan about it? What is it? What it will be? What I can imagine about NTM
I was just highlighting the fact that XNI may be extended in the future by adding "extension" packages for doing various things related to or optimized for the XNI framework. As an example, I used a "native" tree API. However, I don't have any ideas or plans at the moment for inventing such a thing; there's plenty of work remaining for the XNI Core and Parser Configuration framework. > name is something like java oriented and extended DOM. If it is right I > would like to participate on it. We developed own Tree API for XML (TAX) in > XML module for NetBeans and we could share experiences. There are a lot of various tree APIs around. The most common one being the W3C DOM, of course. But other examples would be DOM4J which is an alternative, Java-only tree API; and even Xalan has their own internal tree model which they call DTM. And there could still be others. Of course, if we were to work on a general tree model as an XNI extension, then the goals I would have are: to be complete in terms of the document infoset; have high- performance in creation, access, and memory-usage; and be easily extendable. Not an easy task, that's for sure which is probably why there are so many different tree models out there. Do you have a link to this Tree API for XML you were referring to? -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
