Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 9167 invoked from network); 9 Dec 2009 17:45:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Dec 2009 17:45:31 -0000 Received: (qmail 37912 invoked by uid 500); 9 Dec 2009 17:45:30 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 37721 invoked by uid 500); 9 Dec 2009 17:45:29 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 37711 invoked by uid 99); 9 Dec 2009 17:45:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Dec 2009 17:45:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gianugo@gmail.com designates 72.14.220.154 as permitted sender) Received: from [72.14.220.154] (HELO fg-out-1718.google.com) (72.14.220.154) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Dec 2009 17:45:21 +0000 Received: by fg-out-1718.google.com with SMTP id e12so186097fga.0 for ; Wed, 09 Dec 2009 09:45:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=JsFgMabCxePL6O8Kydm1auZuNljva3H8A1gm9yoIR60=; b=BWeGLm3KL/rKAvtUbfQ+V0sRLAKtIaY3QL3o6qL3e9ZDmOWFqrqrGacqfo1gEXsXs2 1Hu/rFiNLTi0KN1etqjYBI3feCWzsII0i48sidlbKXYFI+oydEDjketTrMyRG8ltfPc1 +OeB4oIzAy0O4+0CTkfgTY3lX3Oy5UnRK+6HI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Jk72ER1lzMdGMEuQ96izVCuaPWYFr9XHkzt1PV6qOB9vqb/rNRuC6V6wppivn92jh3 LUZvc5jgZEqC47WaHU34kNDd3uIP8BcVfEQX3hbqeSO8nlIaIDlufsIZFUPxtqZvFblO KAFRuRdw3z9Q6i5uxJ074r8hCNqxyqch6QwzQ= MIME-Version: 1.0 Received: by 10.239.190.207 with SMTP id y15mr1017852hbh.151.1260380701300; Wed, 09 Dec 2009 09:45:01 -0800 (PST) In-Reply-To: References: <2CDD44F49E3D47459EB0282354AE42AE22ADC47842@DEWDFECCR05.wdf.sap.corp> Date: Wed, 9 Dec 2009 18:45:01 +0100 Message-ID: <7557e99f0912090945o49a764f9yb1c3f5010a956bc@mail.gmail.com> Subject: Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS) From: Gianugo Rabellino To: general@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Dec 9, 2009 at 6:33 PM, Bertrand Delacretaz wrote: > On Wed, Dec 9, 2009 at 6:21 PM, Goetz, Paul wrote: > >> ...Alignment >> Apache Chemistry aims to build a CMIS implementation, too. The focus for OpenCMIS is to provide a >> self-contained client library for CMIS for Java only - while Chemistry is aiming at a broader scope, as >> it started from a JCR/Jackrabbit based approach and is planning to support Javascript as well. >> As the APIs are pretty different right now, contributing the OpenCMIS code to Chemistry will >> be very hard to do - but on a mid-term perspective, we will review our options to merge >> OpenCMIS with Chemistry.... > > I'm not sure if having two podlings implementing CMIS is a good idea. I second that. Although I am, in principle, interested, I'd like to know more about what would differentiate OpenCMIS from Chemistry, and why is this duplication a good thing. From your proposal, I seem to understand you are more focused on the CMIS client side, yet I would like to understand a bit more what's missing from the client Chemistry bit. -- Gianugo --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org