Hi All,
A lot of very good comments and feedback here.
Don't you think now is a good time to capture these comments in the wiki
(or somewhere else) and decide to address (or not) the most painful issues?
BR,
Stephane Bastian
Jukka Zitting wrote:
Hi,
On Mon, Dec 8, 2008 at 10:58 PM, Christopher Corbell
<[EMAIL PROTECTED]> wrote:
Unfortunately at this stage in Tika I'm not sure that fundamental changes
in basic design are possible.
I think that most parts of the design are still open at least until
Tika 1.0 after which we may want to consider adopting a strict
backwards compatibility policy at least until Tika 2.0.
It might also be good to set the user expectations correctly by
documenting that there may well be backwards-incompatible changes
during the 0.x cycle.
Currently I think that the basics of the Parser interface are already
pretty stable and well vetted, but other parts like configuration,
packaging, metadata handling, the MIME type registry, etc. could still
do with more attention before 1.0.
Perhaps this is the distinction between a "toolkit" and a "framework" -
Tika definitely seems more like the former than the latter to me.
That is pretty much the original vision for Tika, i.e. we'd rather
create a lightweight toolkit that applications can use as they see fit
instead of a framework that guides application design.
It will be interesting to see what kind of innovation can be achieved
on top of Tika, and I would very much welcome discussion about such
ideas on this list.
Hopefully this feedback has some constructive use to the community;
I've been keeping a lid on these concerns for awhile but current threads
lured me out.
Good, more opinions and ideas are always welcome!
BR,
Jukka Zitting
