Hi,
Am 04.12.2013 18:33, schrieb Sebastian:
Hi,
I'm highly interested in ruta, and its potential applications in industrial
applications. Right know I'm trying to create a simple toy condition
extension that is simply a case insensitive INLIST condition. It is
completely based on the
Sorry, I read over the mention that it is only a toy extension... so
maybe ignore the advice with the actions ;-)
Can you check whether there is a Type in the typesystem with the short
name MonthsList?
Best,
Peter
Am 05.12.2013 09:58, schrieb Peter Klügl:
Hi,
Am 04.12.2013 18:33, schrieb
I agree that it might make more sense to model our needs more directly
instead of trying to squeeze it into the schema we normally use for text
processing. But at the same time I would of course like to avoid having
to reimplement many of the things that are already available when using
I forgot to say that the text analysis view(s) will necessarily have to
use character offsets so that we can obtain the coveredText, which means
that all resulting annotations will also use character offsets. The
merged view will need to use time-based offsets which means that we have
to
No, the issue is still open.
When I start working on one of the issues that are still recorded on Google
Code, I open a corresponding issue on the Apache Jira and add a link to each of
them, pointing to each other. I also set the ASFJira flag on the Google Code
tracker to true.
-- Richard
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
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
Peter Klügl pkluegl@... writes:
Hi,
Am 04.12.2013 18:33, schrieb Sebastian:
Hi,
I'm highly interested in ruta, and its potential applications in
industrial
applications. Right know I'm trying to create a simple toy condition
extension that is simply a case insensitive INLIST
On 05/12/13 10:04, Jens Grivolla wrote:
I agree that it might make more sense to model our needs more directly
instead of trying to squeeze it into the schema we normally use for text
processing. But at the same time I would of course like to avoid having
to reimplement many of the things
Am 05.12.2013 14:43, schrieb Sebastian:
Peter Klügl pkluegl@... writes:
Hi,
Am 04.12.2013 18:33, schrieb Sebastian:
Hi,
I'm highly interested in ruta, and its potential applications in
industrial
applications. Right know I'm trying to create a simple toy condition
extension that is
On 2013-12-04 12:33, Sebastian wrote:
Hi,
I'm highly interested in ruta, and its potential applications in industrial
applications. Right know I'm trying to create a simple toy condition
extension that is simply a case insensitive INLIST condition. It is
completely based on the InListCondition
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
12 matches
Mail list logo
