From: Lars H. <he...@se...> - 2008-07-02 11:59:38
|
Hi Stefan, [...] > convinced, but we need to find a name, tinytim-io or tinytim-xtm > i would prefer tinytim-xtm > what you think? IMO it would be nice if we'd create a generic API to import topic maps, independently of the concrete syntax, so I'd favour .io. Within the .io package we can provide a XTMDeserializer, LTMDeserializer, WhateverDeserializer which would implement a generic Deserializer interface. The Deserializer interface may be very primitive, just a "parse" method which takes a Stream / Reader / File / URL. Not sure if we want to provide other syntaxes != XTM, but we'd be forward-compatible. ;) If you implement the XTMDeserializer, you may want to use tinyTiM's "native" API and not TMAPI, because the the native API provides faster lookups for Topics than the TMAPI TopicsIndex. Best regards, Lars -- Semagia <http://www.semagia.com> |