From: Lars H. <he...@se...> - 2008-07-01 13:17:52
|
Hi Stefan, > i would prefer to "fix" the tmapi-utils parser. Not just fixing it, > but using latest StAX parser and api. This design is easier to > understand compared to a callback-handler / stackusing parser. Okay, no problem. Will you fix it? Should be straight forward, since we have a CXTM serializer. Just import every topic map from <http://cxtm-tests.cvs.sourceforge.net/cxtm-tests/cxtm-tests/xtm1/in/> and <http://cxtm-tests.cvs.sourceforge.net/cxtm-tests/cxtm-tests/xtm2/in/> and check if the output is identical to the output in the "baseline" directory. I have a TestCase impl. that does the work more or less automatically, I'll contribute it this week to the CXTM subproject. > i think the adapter (not the mio libraries) could stay as a part of > the project, for example as tinytim-mio-xtm and tinytim-mio-cxtm, > but we need to provide a very very simple way of parsing and writing > xtm 1.0/2.0 wihtin the project, with all sources. Hmm... . The CXTM package has nothing to do with MIO. And we need just one "tinytim-mio" package, since you need only one concrete adapter to "parse" every syntax you can think of. ;) Proposal: * Leave tinytim-cxtm as it is * Leave the MapInputHandler in the tinytim-io package or put it into a new package "tinytim-mio". * Replace TopicMapImporter with something that does not use MIO Reasonable? Best regards, Lars -- Semagia <http://www.semagia.com> |