[tinyTiM-discuss] tinyTiM and MIO

[Lars H. <he...@se...>]

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.

The advantage of MIO is, that it is independent of a particular syntax. A small
tinyTiM-related adaptor interprets the events from a MIO deserializer and
translates them into tinyTiM's Topic Maps constructs. If someone writes
a MIO deserializer for syntax XY it is immediately usable by tinyTiM.

The disadvantage of MIO is, that it is not controlled by this project, but it
is an independent project controlled by me. ;) The license shouldn't be
be a problem, because MIO will be released under a Sleepycat-style
license, maybe the API will be published in the future under another
license to support a more widely adoption, but the first versions will use
the Sleepycat lic. and the first deserializers will use that license also.

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.

Sleepycat Lic.: <http://opensource.org/licenses/sleepycat.php>

Best regards,
Lars
-- 
Semagia
<http://www.semagia.com/>