Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 18941 invoked from network); 14 Aug 2006 02:09:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Aug 2006 02:09:28 -0000 Received: (qmail 65654 invoked by uid 500); 14 Aug 2006 02:09:28 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 65299 invoked by uid 500); 14 Aug 2006 02:09:26 -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 65288 invoked by uid 99); 14 Aug 2006 02:09:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Aug 2006 19:09:26 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [66.112.202.2] (HELO mail.devtech.com) (66.112.202.2) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Aug 2006 19:09:26 -0700 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.3.0rc2) with SMTP ID 270 for ; Sun, 13 Aug 2006 22:09:05 -0400 (EDT) From: "Noel J. Bergman" To: Subject: RE: Specifications as (part of) ASF projects Date: Sun, 13 Aug 2006 22:09:03 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <44DFD4B3.1020307@pobox.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Geir Magnusson Jr wrote: > Noel J. Bergman wrote: >> Geir Magnusson Jr wrote: >>> Noel J. Bergman wrote: >>>> Wait ... why can't a specification be a releasable, just like a >>>> codebase? The only issue, as I see it, would be enforcement of >>>> compliance. And Roy even put forward a proposed license amendment >>>> for such things. >>> Which license amendment? The license amendment that I'm thinking of = was >>> specific to JCP TCKs and how derivative works of a TCK can't be used = for >>> compatibility - it had nothing to do w/ enforcement of compliance = with a >>> spec. > Not for the past 6 years. Would love the chance, and still waiting for = someone to get clueful about migrating Outlook in its entirety, and not = just a piece here and there. I've got >4.5GB of mail to migrate, plus = 1000s of contact and calendar entries. > > The JSR licemse, not the TCK license. =20 > I don't remember a JSR license. I was referring to = http://www.apache.org/licenses/proposed/JSR-LICENSE-2.0.txt, which could = be adapted for the purpose. > > what else would you call the clauses forbidding the use of the > > trademark names, references to the specification, and restricted=20 > > name space unless the code passed the TCK? > Dunno, but different than enforced compliance. Denying implementers the ability to use the specification's restricted = name space, which effects the use of the API; make any reference to the = specification; or use the trademark(s) is probably about right when = dealing with Open Source. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org