Re: [tinyTiM-discuss] tinyTiM and MIO

[Stefan L. <li...@ap...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

> I don't care. How about Writer / Reader? Maybe with "TopicMap" as
> prefix to distinguish it better from the Java io.Reader / .io.Writer:
> TopicMapReader, TopicMapWriter.

+1 great idea to use java io style names

>> then we have to talk about the interfaces. i'd prefer the tmapi-utils way
[...]

> If the user wants that the topic map is accessible under the same IRI
> as the the document IRI, she can use the document IRI to create the
> topic map.

but if i don't know the document IRI? just parsing a file from the web/p2p network.
So i think, the first style is needed for this case.


> to add more content to an *existing* topic map. Importing more topic
> map content into an existing topic map should usually be faster than
> letting the TMReader create a topic map, merge it with an existing
> topic map and to delete the topic map the TMReader has created.

OK i got your point, lets do both

read(tmsystem,input)
read(tm, input)

[...]
> After that, the topic map "tm" would contain the content from the XTM
> source and the LTM source.

but what about clashes? is there a merging? when there is a merge, then the user must clearly see it
and invoke it from outside calling tm.merge. and setting the right merge properties first.

so of there is a "hidden" merge, i would recommend only use approach a and force the user to call
merge later. If someone wants some handy shortcut methods he could write it himself. the core api
schould be atomar.

stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIa5ejbsixtqnWg1oRAs7/AJ0SYP/FSpSxYTD3Sp6oGOwFB3sIfgCfVJDh
aBLlupI9U4eSsODBxckfCtI=
=+8fb
-----END PGP SIGNATURE-----