From: Stefan L. <li...@ap...> - 2008-07-01 10:51:06
|
hi, Lars Heuer wrote: > Hi all, > > Recently, there were some bug reports which are more related to MIO than to > tinyTiM. So, the question is, if we want that MIO becomes the default import > mechanism or not. We can either fix and use tmapi-utils or we develop a > dedicated importer for tinyTiM. 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. the goal of tinyTIM was always to be as simple as possible, thats why so many students that started with topic maps used tinytim and tmapi-utils parser, cause they understood the source code. > What do you think? I am open minded, I'd use tinyTiM's MIO adaptor > for testing purposes anyway, so I don't care if the adaptor is part of > this project or if I keep it as personal project. 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. So maybe we can migrate the tmapi-utils parser to tinytim project thoughts? stefan |