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 25AF81749E for ; Sat, 11 Jul 2015 15:16:22 +0000 (UTC) Received: (qmail 64087 invoked by uid 500); 11 Jul 2015 15:16:21 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 64043 invoked by uid 500); 11 Jul 2015 15:16:21 -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 64032 invoked by uid 99); 11 Jul 2015 15:16:21 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jul 2015 15:16:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2F3091A6DCE for ; Sat, 11 Jul 2015 15:16:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.99 X-Spam-Level: X-Spam-Status: No, score=0.99 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id i0tjz_mnbHJc for ; Sat, 11 Jul 2015 15:16:19 +0000 (UTC) Received: from mailrelay.rz.uni-wuerzburg.de (wrz3035.rz.uni-wuerzburg.de [132.187.3.35]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 5BD7820D30 for ; Sat, 11 Jul 2015 15:16:19 +0000 (UTC) Received: from virusscan-slb.rz.uni-wuerzburg.de (localhost [127.0.0.1]) by mailrelay-slb.rz.uni-wuerzburg.de (Postfix) with ESMTP id 1D4041800920 for ; Sat, 11 Jul 2015 17:16:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan-slb.rz.uni-wuerzburg.de (Postfix) with ESMTP id 1BAC5800DA0 for ; Sat, 11 Jul 2015 17:16:19 +0200 (CEST) X-Virus-Scanned: amavisd-new at uni-wuerzburg.de Received: from mailmaster.uni-wuerzburg.de ([127.0.0.1]) by localhost (vmail002.slb.uni-wuerzburg.de [127.0.0.1]) (amavisd-new, port 10225) with ESMTP id k1-Lrd8JQPVW for ; Sat, 11 Jul 2015 17:16:19 +0200 (CEST) Received: from [192.168.0.5] (HSI-KBW-46-223-1-102.hsi.kabel-badenwuerttemberg.de [46.223.1.102]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTPSA id E14381012E10 for ; Sat, 11 Jul 2015 17:16:18 +0200 (CEST) Message-ID: <55A13339.3050603@uni-wuerzburg.de> Date: Sat, 11 Jul 2015 17:16:09 +0200 From: =?UTF-8?B?UGV0ZXIgS2zDvGds?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: Problem with matching of composite rules References: <559F8BE5.7090700@uni-wuerzburg.de> <559FCCA1.5030707@averbis.com> In-Reply-To: <559FCCA1.5030707@averbis.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit The problem was caused by two separate bugs in the rule inference. They are now fixed in the current trunk. Thanks for reporting it :-) Best, Peter Am 10.07.2015 um 15:46 schrieb Peter Klügl: > Hi, > > Am 10.07.2015 um 13:55 schrieb Andreas Weber: >> Peter Klügl writes: >>> ... in the light of current events and since you use it integrated in >>> your software: >>> Did you use an analysis engine for creating the CAS or, in case you >>> created it using a type system, did you consider the type priotities? >>> >> Hi Peter, >> >> thanks for your help. >> >> We create our CAS and annotations programmatically using our own type >> system, we don't use another UIMA annotator. >> >> I played a little bit around with type priorities (MY_ANNO > W) but >> that >> had no impact. The main problem seems to be that we have the _same_ >> annotation type at one input position. > > That shouldnt't be a problem at all ;-) > > UIMA Ruta brings its own type priorities for some special internal > types. If the priorities are missing then there could be some problems > in sequential matching. > > I'll take a look at it. > > Best, > > Peter > > >> Regards, >> Andreas >> >