Return-Path: Delivered-To: apmail-incubator-uima-user-archive@locus.apache.org Received: (qmail 88269 invoked from network); 25 Oct 2007 07:16:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Oct 2007 07:16:44 -0000 Received: (qmail 78003 invoked by uid 500); 25 Oct 2007 07:16:31 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 77986 invoked by uid 500); 25 Oct 2007 07:16:31 -0000 Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: uima-user@incubator.apache.org Delivered-To: mailing list uima-user@incubator.apache.org Received: (qmail 77977 invoked by uid 99); 25 Oct 2007 07:16:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2007 00:16:31 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of YOSIMASS@il.ibm.com designates 195.212.29.151 as permitted sender) Received: from [195.212.29.151] (HELO mtagate2.de.ibm.com) (195.212.29.151) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2007 07:16:32 +0000 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.8/8.13.8) with ESMTP id l9P7FA7s104826 for ; Thu, 25 Oct 2007 07:15:10 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l9P7FAXi1880180 for ; Thu, 25 Oct 2007 09:15:10 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l9P7FA9L013215 for ; Thu, 25 Oct 2007 09:15:10 +0200 Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l9P7FA2Z013212 for ; Thu, 25 Oct 2007 09:15:10 +0200 In-Reply-To: Subject: Re: Question on the SemanticSearch.zip - SIAPI To: uima-user@incubator.apache.org Cc: uima-user@incubator.apache.org X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006 Message-ID: From: Yosi Mass Date: Thu, 25 Oct 2007 09:12:04 +0200 X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 25/10/2007 09:15:09 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org Dear Scott, Can you please explain what you mean that the query doesn't return hits for organization.compnay annotations? You probably know that a SIAPI query returns full documents as results and not a result for each annotation so a document with and also tags under organization will be returned only once. Thanks, Yosi "Sommer, Scott (Contractor)" cc 25/10/2007 08:24 Subject Question on the SemanticSearch.zip Please respond to - SIAPI uima-user@incubat or.apache.org Hi guys, I posted a while back about about indexing using SIAPI. Since then I've managed to get the entire process of indexing and searching working pretty smoothly. However, I have a general question for anyone who is familiar with SIAPI. Basically, prior to indexing documents I have built a Index Specification Descriptor which contains the typesystem to use for indexing. My typesystem has hierachy in it, so there is stuff like organization, organization.company in there. What I was hoping for is that when I submit something like '' as the xml search fragment I would get hits for not only organization annotations but also all the child types of organization including organization.company, however, this doesn't happen. Is there anything that I can do with the Index Specification Descriptor to define a hierachy for the SIAPI indexer? Or does the indexer have no concept of hierachy? If it doesn't support hierachy typesystems, I was wondering if I can modify the xml fragment before it is submitted to basically OR all the child types. I've seen some xml fragments for omnifind which have <.or> tags in them, but I have only seen it used to filter on propertys, ie <.or>John SmithXML -Microsoft. Is there anything similar I can do with juru but on types? Finally, is there a workaround to my issue that I haven't thought of? Thanks in advance, Scott. IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.