Renaud,
I understand your apprehensions about UIMA-AS. One of the purposes of this
platform is to make UIMA-AS as easy to configure and deploy as UIMA core while
still leveraging the scalability features that UIMA-AS provides. If you ever
decide to move beyond the poor man’s solution let me k
@Richard,
Thanks for your explanation; it seems that it would be quite a "deep" code
change, and in my usecase not worth the trouble.
@Thomas,
Thanks for sharing your project with us. However, I looked at UIMA-AS, and
found it too complicated for my taste.
My poor-man's solution will be to show a
Renaud,
We (clinical NLP group at the University of Utah) have written a platform that
sits on top of UIMA-AS that will allow you to dynamically assign and even
generate types for annotation engines. We have a whole family of annotators
whose parameters are dynamic using this platform. We are
To my knowledge, the capabilities are part of the descriptor which must be
available before the AE is initialized. You cannot retroactively change the
descriptor of a method from within its initialize() method.
It would be nice to have something like this, though. But that would also mean
switchi
I find it very convenient to add
@TypeCapability(inputs = { TOKEN, SENTENCE, COOCCURRENCE })
so that I can ensure that dependencies are met. But sometimes, the
dependencies are dynamic (e.g. an input type capability is part of the
config of an annotator, and is loaded dynamically, see code below).