Option 1 - by foot:
I guess the uimaFIT JCasIterator should continue to read CAS by CAS
from the reader. However, for each CAS read by the reader, it should be
able to return 0-x CASes. Currently it can only return 1 because it
calls engine.process(jCas) on each engine in turn. To return 0-x,
Hi, we're now starting the EUMSSI project, which deals with integrating
annotation layers coming from audio, video and text analysis.
We're thinking to base it all on UIMA, having different views with
separate audio, video, transcribed text, etc. sofas. In order to align
the different views
Why is it bad if you cannot inherit from Annotation? The getCoveredText() will
not work anyway if you are working with audio/video data.
-- Richard
On 04.12.2013, at 12:31, Jens Grivolla j+...@grivolla.net wrote:
Hi, we're now starting the EUMSSI project, which deals with integrating
True, but don't things like selectCovered() etc. expect Annotations (to
match on begin/end)? So using Annotation might make it easier in some
cases to select the annotations we're interested in.
-- Jens
On 04/12/13 15:35, Richard Eckart de Castilho wrote:
Why is it bad if you cannot inherit
We (a group at the University of Utah) are also implementing a web based
validation system to display UIMA output and allow users to validate the
annotations.
We¹d be happy to collaborate with other groups if others are interested.
-Ryan
On 12/3/13, 3:13 AM, Frank Enders
selectCovered() and friends expect annotations (or AnnotationFS), yes. Anyway,
I don't want to convince you to deviate from your idea. Frame offsets sound
very reasonable. Just trying to discuss potential implications and confusions
(e.g. getCoveredText() not working).
Also, can I have
Echoing Richard,
1) It would perhaps make more sense to be more direct about each of the
different types of data. UIMA built-in only the most popular things - and
Annotation was one of them.
Annotation derives from Annotation-base, which just defines an associated Sofa /
view.
So it would make
:)
Btw. the indexing system in UIMA didn't appear extensible to me last
time I checked. Considering somebody would introduce a x/y coordinates
scheme for image data. This would call for some spatial index, e.g. a
k-d tree. While it is possible to define different indexes of the bag,
set, and
Option 2 - let UIMA do the heavy lifting
An alternative and much simple approach might be to create an aggregate which
does not only contain the engines, but also the reader. Then you don't have
to
worry about the reader anymore at all. Just create a UIMA JCasIterator and
poll CASes
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 class, I also declared an
implementation
10 matches
Mail list logo
