On 24.06.2015, at 11:56, Thilo Goetz <[email protected]> wrote: >> Or would the issue be solvable by integrating uimaFIT into the core (e.g. to >> avoid re-approval of libraries by company legal departments)? > > I am just speaking for myself here, but I don't want more framework, I want > less. I don't want to have to use uimaFIT to help me deal with UIMA if I > could have something that doesn't require that help. Give me a simple JSON > based data format and I'll be happy. > > I know this is selfish, but unless the discussion is seriously moving in that > direction, I'm simply not interested :)
Fair enough. Marshall already did some nice work on JSON serialization, so I think there is movement into that direction. But what I don't understand is how a data format resolves to "less framework". The data format is basically addressing ingestion and export, but not processing or pipelines. Even if you have a simple data format like JSON, there's still the need to run analysis, right? Is the analysis in your scenario just a black box? And in order to apply the analysis, you'll need some kind API - how do you imagine it? Cheers, -- Richard
