On 15.09.2017, at 09:28, Nicolas Paris <[email protected]> wrote: > > - UIMA-AS is another way to program UIMA
Here you probably meant uimaFIT. > - UIMA-FIT is complicated > - UIMA-FIT only work with UIMA ... and I suppose you mean UIMA-AS here. > - UIMA only focuses on text Annotation Yep. Although it has also been used for other media, e.g. video and audio. But the core UIMA framework doesn't specifically consider these media. People who apply it UIMA in the context of other media do so with custom type systems. > - UIMA is not good at: > - text transformation It is not straight-forward but possible. E.g. the text normalizers in DKPro Core make use of either different views for different states of normalization or drop the original text and forward the normalized text within a pipeline by means of a CAS multiplier. > - read data from source in parallel > - write data to folder in parallel Not sure if these two are limitations of the framework rather than of the way that you use readers and writers in the particular scale-out mode you are working with. > - machine learning interface UIMA doesn't offer ML as part of the core framework because that is simply not within the scope of what the UIMA framework aims to achieve. There are various people who have built ML around UIMA, e.g. ClearTK (http://cleartk.github.io/cleartk/) or DKPro TC (https://dkpro.github.io/dkpro-tc/) - and as you did, it can be combined in various ways with ML frameworks that specialize specifically on ML. Cheers, -- Richard
