Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5978511C39 for ; Wed, 9 Apr 2014 20:15:21 +0000 (UTC) Received: (qmail 72164 invoked by uid 500); 9 Apr 2014 20:15:20 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 71939 invoked by uid 500); 9 Apr 2014 20:15:19 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 71927 invoked by uid 99); 9 Apr 2014 20:15:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 20:15:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com designates 209.85.128.171 as permitted sender) Received: from [209.85.128.171] (HELO mail-ve0-f171.google.com) (209.85.128.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 20:15:14 +0000 Received: by mail-ve0-f171.google.com with SMTP id jy13so2518090veb.2 for ; Wed, 09 Apr 2014 13:14:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=j/OV1d8X+l1PO44y3ZOT6kly6Rl+kBFcfDmlFB7uNI4=; b=Bsd5FhBNZjyn+cf84TsRdzJRfkxuqGUKN4+ktFxbyI7rkek1+5aOpaC+4jKKY3mNV2 YXtHtZKsXkGzc27fkbP+C7gCmR4PJ6UmQL9UWNpes1twfhvkjmHTCAAUVdCLkBB03yjO 1TBSsXDtqryHUnnk1mXLZdz9S98EMHLC+fASMyQK6CM36k5tgXdjqRWQROD1bLv6JAKf R60/WB+MC/ofIMmNs03F01UWh3o6vLssfyZQs1UGf0oNL9NtO7ICmvj+D8B0HUiBYUUK xnJxaAZKcZL+EWb1VnTpoWw568tPiQmE+0dLTvR6A9eKfAMIOxsgaPM/9q9JfuvuQeGu nm8Q== MIME-Version: 1.0 X-Received: by 10.58.49.10 with SMTP id q10mr10221774ven.5.1397074493718; Wed, 09 Apr 2014 13:14:53 -0700 (PDT) Received: by 10.52.97.130 with HTTP; Wed, 9 Apr 2014 13:14:53 -0700 (PDT) In-Reply-To: <20140409023434.GP6156@machine.or.cz> References: <20140409023434.GP6156@machine.or.cz> Date: Wed, 9 Apr 2014 16:14:53 -0400 Message-ID: Subject: Re: Complex architectures with multiple CASes - how to? From: Eddie Epstein To: user@uima.apache.org Content-Type: multipart/alternative; boundary=089e013a04b6ec441804f6a1c0da X-Virus-Checked: Checked by ClamAV on apache.org --089e013a04b6ec441804f6a1c0da Content-Type: text/plain; charset=ISO-8859-1 One approach is for the cas multiplier to put the question View in each search CAS, using the CasCopier, and create a second view for search result processing. Down stream annotators would then be multi-view, getting question analysis results from one view and doing search analysis in the other. Eddie On Tue, Apr 8, 2014 at 10:34 PM, Petr Baudis wrote: > Hi! > > I'd like to ask about the philosophy and typical usage patterns behind > multiple CASes, CAS multipliers and CAS mergers. > > I'm working on a simple question-answering system built on top of > UIMA and mirroring DeepQA architecture. Basically, on input I have > a CAS with the input question as a sofa, and after some processing, > a "search" CAS multiplier produces a CAS for each search result that > might contain an answer. > > > However, at this point, I may want to use an AE that needs to see both > the question CAS and the search result CAS. Typically, I could try to > align sentences, i.e. with question sofa "Who invented the transistor?" > and stand-off Focus annotation for "Who", I may want to search the > result CAS for "(\S+) invented the transistor". > > But now I'm stuck. How can I build such an AE that has access to > information in two CASes? It seems one approach is to copy featuresets > to result CAS in the multiplier. However, if the CAS sofa is different, > how can stand-off annotations (like Focus) be carried over? Also, I may > want to match parse trees instead of strings, which suddenly means > potentially a lot of data is copied, and I will need to distinguish > annotations of the question and of the searh result. A similar problem, > but in a much clumsier way, seems to arise if I were to make the > alignment AE a CAS merger. > > > I must be missing something obvious here, but reading the developer guide > back and forth doesn't help... Thanks for any hints! > > Petr Baudis > --089e013a04b6ec441804f6a1c0da--