Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 36297 invoked from network); 8 Aug 2005 21:44:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Aug 2005 21:44:24 -0000 Received: (qmail 47109 invoked by uid 500); 8 Aug 2005 21:44:22 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 47095 invoked by uid 99); 8 Aug 2005 21:44:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 14:44:22 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.249.34.130] (HELO picanmix.dev.day.com) (212.249.34.130) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 14:44:45 -0700 Received: from eu-mail.day.com (eu-mail.dev.day.com [10.0.0.30]) by picanmix.dev.day.com (DAY) with ESMTP id j78LiI125331; Mon, 8 Aug 2005 23:44:19 +0200 (MEST) Received: from [10.2.8.76] ([10.2.8.76]) by eu-mail.day.com (Lotus Domino Release 5.0.8) with ESMTP id 2005080823441564:18787 ; Mon, 8 Aug 2005 23:44:15 +0200 In-Reply-To: <42F75510.4010908@builditglobal.com> References: <42F75510.4010908@builditglobal.com> Mime-Version: 1.0 (Apple Message framework v622) Message-Id: Cc: jackrabbit-dev@incubator.apache.org From: "Roy T. Fielding" Subject: Re: compliance certificate Date: Mon, 8 Aug 2005 14:44:27 -0700 To: Walter X-Mailer: Apple Mail (2.622) X-MIMETrack: Itemize by SMTP Server on eu-mail/Day(Release 5.0.8 |June 18, 2001) at 08/08/2005 11:44:16 PM, Serialize by Router on eu-mail/Day(Release 5.0.8 |June 18, 2001) at 08/08/2005 11:44:18 PM, Serialize complete at 08/08/2005 11:44:18 PM Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Walter, Apache Jackrabbit is an open source project. It is not a generic JCR support forum. Some of the questions you are asking are not appropriate for the jackrabbit-dev mailing list. > Finally, I would still like someone to respond to the following=20 > questions, if interested: > > Who can perform a Level One certification for us and is this possible? You can do that yourself using the TCK provided for JSR 170. Please go to the JSR 170 site and follow the download links. > Has there been any companies certified fully compliant? Companies don't get certified -- implementations do. I don't think that the information you are requesting is public knowledge. > Any specific suggestions will be helpful. Also, if there is any code=20= > that you would like me to commit to your efforts, and it will not=20 > require me releasing everything I've built, I would be more than happy=20= > to consider contributing to your efforts. I understand Day has a=20 > proprietary system, and has not contributed all their code to this=20 > open source effort, but I could be wrong. Day has many products, some of which contain parts licensed from third-parties that cannot be made open source. What Day licensed to Apache to create Jackrabbit is the heart of Day's current generation content repository (CRX) and content management system (Communiqu=E9). Those software products have many features not included in a JCR implementation, in addition to commercial support, and Day licenses that software as closed source in order to pay many of our salaries (among other things). Jackrabbit, however, is now an Apache product that combines contributions from many companies and individuals. All contributions are voluntary. I think what you should do is figure out what parts of your code *you* would want to see in some future version of jackrabbit such that it would enable you to replace your current JCR implementation with the Apache one. That would allow you to leverage all the development effort here. Cheers, Roy T. Fielding Chief Scientist, Day Software =20=