Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <47442C51.6020502@michael-baessler.de>
Date: Wed, 21 Nov 2007 14:02:09 +0100
From: Michael Baessler <mba@michael-baessler.de>
Reply-To: mba@michael-baessler.de
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: uima-user@incubator.apache.org
Subject: Re: Result Specifications in CPE
References: <47441C3F.1090100@xrce.xerox.com>
In-Reply-To: <47441C3F.1090100@xrce.xerox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Aaron Kaplan wrote:
> In Section 1.5.5.4 of "UIMA Tutorial and Developers' Guides" I read:
>
>   The Default Result Specification is always used for all components 
> of a Collection Processing Engine.
>
> Why is this?  Is it just because nobody's gotten around to putting in 
> a call to setResultSpecification, or is there some fundamental reason 
> that it couldn't be done?
>
> What I would like is that when my annotator is instantiated inside a 
> CPE, it can skip generating certain annotations if no other component 
> in the CPE is going to consume them.
>
> -Aaron
I think this is a documentation issue, but I'm not quite sure. I will 
start a discussion about this on the uima-dev list.
I think when you use an aggregate AE with a capabilityLanguageFlow as 
flow constraint, a computed Result Specification is used.

If you don't use an aggregate AE as CasProcessor I think it is true, 
that the Default Result Specification is used.

We will let you know the result of the discussion on uima-dev.

-- Michael