Return-Path: X-Original-To: apmail-ctakes-dev-archive@www.apache.org Delivered-To: apmail-ctakes-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 255FAF660 for ; Tue, 1 Oct 2013 14:41:51 +0000 (UTC) Received: (qmail 23300 invoked by uid 500); 1 Oct 2013 14:41:50 -0000 Delivered-To: apmail-ctakes-dev-archive@ctakes.apache.org Received: (qmail 23201 invoked by uid 500); 1 Oct 2013 14:41:50 -0000 Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ctakes.apache.org Delivered-To: mailing list dev@ctakes.apache.org Received: (qmail 23193 invoked by uid 99); 1 Oct 2013 14:41:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 14:41:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of richard.eckart@gmail.com designates 74.125.83.52 as permitted sender) Received: from [74.125.83.52] (HELO mail-ee0-f52.google.com) (74.125.83.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 14:41:42 +0000 Received: by mail-ee0-f52.google.com with SMTP id c41so3422702eek.25 for ; Tue, 01 Oct 2013 07:41:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=2BwLwazqG33lux8qSD862XJsybnop3yStgOXOUd+cmk=; b=lvirHw0q9awT++E36WoHr00NzFS6kbpC/zT5hLhGbrtrbab2ujVFnbNIoOd8q7K8eo Stg/qli4MRnv97boWH0iOSQXaL5ufHX369Avrv0Bbd2zeneyTwyGcR++1XOBqISXf8V6 G1HlxA0pt3rS3w8zSGMtl+7YAnplGOzhVVBXxMCbmNxvN1RHnYskVt42Jp+MJvL196lr +lv3kRGDU/JzE2xABaqQuOq44mdNwb533Cv9CtGIW3OtsSD4UnlYC7hvHWojFrCFo3aj pLv89wumK2FbqnzUT7nJ5M0vxy5Ct17gbxjB6oIBDovfmzWRkzW2OIV2bkx1ZW9CtYPd 7x4g== X-Received: by 10.15.48.67 with SMTP id g43mr46805105eew.17.1380638481966; Tue, 01 Oct 2013 07:41:21 -0700 (PDT) Received: from highfire.ukp.informatik.tu-darmstadt.de (macbook-rec.ukp.informatik.tu-darmstadt.de. [130.83.167.192]) by mx.google.com with ESMTPSA id x47sm13960762eea.16.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Oct 2013 07:41:21 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Common Type System across systems? From: Richard Eckart de Castilho In-Reply-To: Date: Tue, 1 Oct 2013 16:41:18 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: dev@ctakes.apache.org X-Mailer: Apple Mail (2.1510) X-Virus-Checked: Checked by ClamAV on apache.org At the time that Steven, Philip and I had our conversation, I committed = to do the work and to come up with a proposal. For quite some time I had = no time to work on this, but actually, an analysis the design of several = UIMA type systems has meanwhile been done. As this is part of ongoing = research, I cannot share this with the general public right now, but = will be more than happy to do it as soon as I can. I'll also still be = happy to take the lead (or at least one of the leads) on the proposal. = As for a time frame, I think getting an initial suggestion ready around = Q1 2014 is realistic.=20 In my opinion, ClearTK, cTAKES and DKPro Core all bring in distinct = design choices that should be combinable with each other for an = extensible base type system. I'd personally not suggest to take any of = the type systems as is (without modifications) as the basis for a = proposal. -- Richard=20 On 01.10.2013, at 03:17, Steven Bethard = wrote: > We (ClearTK) talked with Richard (DKPro) about doing this for ClearTK > and DKPro. Basically, both groups were all for it, but the main issue > was time. Basically you need to: >=20 > (1) Have someone inspect the various type systems closely and make a = proposal > (2) Agree on the proposal. > (3) Spend the time to re-write all the code to use the new type = system. >=20 > Step (3) is especially time consuming, but in fact, we never managed > to get the free time for step (1). >=20 > That all said, ClearTK would love to share a common type system with > other projects. >=20 > Steve >=20 >=20 > On Mon, Sep 30, 2013 at 7:38 PM, Pei Chen wrote: >> Richard, I, and few others had an interesting bar conversation... >> In the spirit of interoperability, What if we had a baseline common = type >> system that could be reused across UIMA compatible NLP systems? >> Imagine for a moment that OpenNLP, ClearTK, ClearNLP, DKPro, cTAKES = etc. if >> we could come up with a common baseline type system could be be = reused? It >> may sound like a dream, but it could be doable-- if we could factor = out and >> find the common ground? Perhaps we could start with the syntactical >> features... and then extend it for more specific domain use cases? >>=20 >> --Pei