uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie Epstein <eaepst...@gmail.com>
Subject Re: Sofa-unaware AEs that create new views in an AAE
Date Fri, 18 Apr 2014 13:23:50 GMT
On Thu, Apr 17, 2014 at 9:17 AM, Peter Kl├╝gl <pkluegl@uni-wuerzburg.de>wrote:

> Am 17.04.2014 15:01, schrieb Eddie Epstein:
> > Hi Peter,
> >
> > The logic is that since a sofa aware component may have one or
> > more input and/or output views, such a component needs to use
> > getView to specify which to use.
> >
> > For sofa aware delegates, sofa mapping enables the delegate to
> > hard wire input and/or output View names in annotator code (or
> > annotator config parameters) and then have the real View names
> > assigned via mapping in the aggregate.
> Is the real view name in the mapping important at all since the view get
> accessed by the implementation in the process() method?

The real view name is what will be used when the CAS is serialized
to a file or to a remote service.

> I don't see the effect of the mapping to the default input view of an
> sofa aware AE without input view capabilities at all. The mapping says
> view1 is linked, but another one arrives.

The input view for a sofa aware component is always the base CAS view,
for the reason given above.

> So, the best practice is to introduce a parameter for specifying the
> input view? In case that the AE implementation should be used several
> times in an AAE for different views.

> Peter

Many if not most view aware components I've seen do not have a single
input view.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message