Re: Restricting an aggregate engine to a substring or mention

Hi Armin, how would you do the last step: telling the nested AE to process only the mentions of the segment type? As far as I can see, it again boils down to the point that the SegmentProcessingAE would internally create one or more new CASes or view, pass those to the nested AE, and then

AW: Restricting an aggregate engine to a substring or mention

Hi Richard, you're right. I have to use new CASes or views. Or I can use the same CAS and restrict the analysis engine to a substring. But that would imply having parameters for the substring's begin and end offsets in the analysis engine: Oh, wait a minute, wasn't that my original question?

AW: Restricting an aggregate engine to a substring or mention

Hello! I've got another maybe not so good idea. Why not pass an aggregate analysis engine as a parameter? First, build an aggregate analysis engine the usual way. Second, serialize it to an XML-string. Third, pass that string to the SegmentProcessingAE as String parameter together with another

RE: Restricting a aggregate engine to a substring or mention

Hi Armin, I'm not aware of a generic mechanism to restrict an AN's scope of processing, but I'm very new to UIMA. It seems that Petr's approach does address the general case though: if some AE doesn't support zones, create a new view containing just the content you want to have processed,

Re: Restricting a aggregate engine to a substring or mention

One other thought (probably not well-formed...): You could use 1 CAS, but multiple views. Each view can have its own subject-of-analysis. This might not work for you, though, as you might want the original subject-of-analysis in order to preserve the offset values for annotations' begin and end

Re: Restricting a aggregate engine to a substring or mention

On Tue, Jun 17, 2014 at 06:48:15PM +, Oliver Christ wrote: dkpro-core's BreakIteratorSegmenter (rather: its base class) takes the same approach. It allows you to specify that segmentation should occur within zones, defined by some other annotation type. And for most other dkpro-core's

Restricting a aggregate engine to a substring or mention

Hello! Is there an UIMA component which restricts an aggregated analysis engine to a substring of the document text or to mentions of a given annotation type? That is, is there a UIMA aquivalent to GATE's Segment Processing PR? Thanks, Armin

Restricting an aggregate engine to a substring or mention

Hello! Is there an UIMA component which restricts an aggregated analysis engine to a substring of the document text or to mentions of a given annotation type? That is, is there a UIMA aquivalent to GATE's Segment Processing PR? Thanks, Armin

Re: Restricting a aggregate engine to a substring or mention

Hi Armin, the only generic approach that I am aware of would be a CasMultiplier. Different component collections may offer alternative solutions in general or in specific components. I believe Ruta has the concept of limiting rules to certain context annotation types, but I do not know if that

Re: Restricting a aggregate engine to a substring or mention

Hi, Am 12.06.2014 17:39, schrieb Richard Eckart de Castilho: Hi Armin, the only generic approach that I am aware of would be a CasMultiplier. Different component collections may offer alternative solutions in general or in specific components. I believe Ruta has the concept of limiting