+1 to Joern's comment and more generally to a sort of general purpose / common TS.
My 2 cents, Tommaso Il giorno ven 9 set 2016 alle ore 13:57 Joern Kottmann <[email protected]> ha scritto: > I personally think that we depend way too much on particular type systems > in UIMA. I really hope we can solve this to some degree in UIMA 3, if I > today > write code using JCAS I am totally stuck with the TS I use, reusing any of > that > code with a different TS is impossible. > > The best you can do is using just the CAS, but then it is still difficult > to support > multiple type systems (e.g. complex configuration, various styles) and > allow > reusing of the component in different systems. > > Jörn > > On Tue, Aug 30, 2016 at 7:57 PM, Richard Eckart de Castilho < > [email protected]> > wrote: > > > On 30.08.2016, at 16:39, Peter Klügl <[email protected]> wrote: > > > > > > If there no standard type system, then people have two options: create > > > their own one or reuse an existing type system of a component > > > repository, e.g., DKPro Core. As far as I know LiMoSINe [1] moved from > > > their own type system to DKPro Core (I waiting for some text to put on > > > our external resources page - in case they read this). I also was > > > thinking about switching our NLP components to the DKPro Core type > > > system, but there are several issues preventing that, first of all that > > > I cannot build it :-/ > > > > /me Apache/UIMA hat off, DKPro Core hat on > > > > Ok... I am finally addressing this annoying Windowsisim... > > > > https://github.com/dkpro/dkpro-core/issues/414 > > > > Btw. feel free to submit issues for DKPro Core type system improvements. > > We actually do evolve the TS - trying to avoid breaking changes... > > > > Cheers, > > > > -- Richard >
