Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ro.franchini@gmail.com
 designates 209.85.128.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=knn2mbuEfLAG/C0oDsYD9wngrcReVSTr+hGpOeZsXhcZfxVIP48tGgL4dsEHd56DOM
         m73jP8HYiaMdWP4wnVNqQiyj+U8vuOCRGrG7OgFMEfp9HFKtyXTskIq53CyLrIhH1XPW
         nAiV7SNaYeVzYYM/2UI5hSjp5uBJ5hThPmIu8=
Message-ID: <63e2e4460812051437m4a4f1e22x9f134876d803c53e@mail.gmail.com>
Date: Fri, 5 Dec 2008 23:37:32 +0100
From: "Roberto Franchini" <ro.franchini@gmail.com>
To: uima-user@incubator.apache.org
Subject: Re: Lucene cas consumer
In-Reply-To: <4939491F.3030500@tk.informatik.tu-darmstadt.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <63e2e4460812030706n3ece1828i69b411043e710f6@mail.gmail.com>
	 <4938FA30.2090402@tk.informatik.tu-darmstadt.de>
	 <49390503.4030003@gmail.com>
	 <4939491F.3030500@tk.informatik.tu-darmstadt.de>

On Fri, Dec 5, 2008 at 4:30 PM, Christof Mueller
<mueller@tk.informatik.tu-darmstadt.de> wrote:
> J=F6rn Kottmann wrote:
>> I am also interested in a Lucene CAS consumer.
>> Maybe we can work together and set up a sandbox project ?
>>
>> J=F6rn
> Hi J=F6rn,
>
> we would be happy to contribute the code of the example Lucene CAS
> consumer as base for the sandbox project.
>
> Christof
>


I've got an index!!!!
Yes, mixing some code from the JENA lucas (I kept it in a dust corner
of my harddisk :) ), some from DK and some mine, i produce an index.
If we want to start a Lucene indexer that's not only a proof of
concept but something very useful, it should be
configurable/exetendable.
The "problem", that's the UIMA's power,  is that everyone has it's own
type system.
To produce a lucene document one extract information from some
features, applying the right analyzer. In my case I use maybe only 10%
of the annotation produced by the analysis pipeline to produce a
single lucene doc.
So we need a very highly configurable component, able to map only
certain declared features and applying the right analyzer and so on.
Mny ways are possible:
-completly programmatic: the indexer is abstract and should be
extended to implement the right mapping for a specialized typeSytem
and pipeline
-configurable: mapping rules are defined in a descriptor file; the
JENA component followed this way
-mix of the two: some mapping is configured, other are implemented

My 2=80cents.
Regards,
Roberto


--=20
Roberto Franchini
http://www.celi.it
http://www.blogmeter.it
http://www.memesphere.it
Tel +39-011-6600814
jabber:ro.franchini@gmail.com skype:ro.franchini