Andy Clark wrote: > 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. >
Yes. There is a lot of tree APIs around XML and it is hard to choose one of them. W3C DOM is the most used because it is standard API but it is not so much comfortable for java developers and this is reason, why there are JDOM, dom4j, etc. Those APIs are still *data* oriented only and this is reason, why we are developing *TAX*. TAX provides *structural* oriented API, because NetBeans XML module provides tree editing support and it needs more info about parsed XML and DTD documents. And this is reason why we use XNI instead of SAX for build TAX tree. > 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. You are writing about document infoset. Do you mean by this W3C XML Information Set (http://www.w3.org/TR/xml-infoset/)? This could be great but XML InfoSet does not describe all parts of XML spec, see http://www.w3.org/TR/xml-infoset/#omitted. I can imagine that relation between NTM and DOM will be same as relation between XNI and SAX. I hope, I am not too wrong. I think that XNI is event oriented API, full describing XML and DTD documents. And I also think, that NTM could be object model API for full describing those documents. And TAX does or would like to do something like this. And this is reasons why I would like to participate. We do not want to create another tree API, which will be only one of twenty similar APIs. We would like to participate on design java oriented tree API, interfaces - not implementation (as JDOM). What about some JSR? > > Do you have a link to this Tree API for XML you were > referring to? > TAX is part of NetBeans XML module. It is created as NetBeans independent library. This is short time when it was open sourced, so web pages are not too detailed, coming soon. You can look at http://xml.netbeans.org/tax/ and source code in CVS http://xml.netbeans.org/source/browse/xml/tax/. Thanks for your feedback, I appreciate it. Best regards, Libor -- Libor Kramolis | [EMAIL PROTECTED] NetBeans/Sun Microsystems, XML module | http://xml.netbeans.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
