Return-Path: Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: (qmail 94514 invoked from network); 26 Apr 2006 17:34:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Apr 2006 17:34:12 -0000 Received: (qmail 81421 invoked by uid 500); 26 Apr 2006 17:33:57 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 81262 invoked by uid 500); 26 Apr 2006 17:33:56 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 81251 invoked by uid 99); 26 Apr 2006 17:33:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 10:33:55 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jimb@bea.com designates 63.96.162.5 as permitted sender) Received: from [63.96.162.5] (HELO ussjmh01.bea.com) (63.96.162.5) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 10:33:54 -0700 Received: from ussjfe01.amer.bea.com (ussjfe01b.bea.com [172.16.120.57]) by ussjmh01.bea.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id k3QHXQBm011286; Wed, 26 Apr 2006 10:33:33 -0700 Received: from repbex02.amer.bea.com ([10.160.26.99]) by ussjfe01.amer.bea.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 26 Apr 2006 10:32:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Subject: RE: [stax_builders] Re: StAX (JSR 173) API source license Date: Wed, 26 Apr 2006 10:32:49 -0700 Message-ID: <9186D1D624F88F469BE0CC4F2DDB970B7E4CB4@repbex02.amer.bea.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [stax_builders] Re: StAX (JSR 173) API source license Thread-Index: AcZpScV+reUoC+n5RMqLz3NxBF2qRwADFCnQ From: "Jim Barnett" To: "Guillaume Nodet" , Cc: X-OriginalArrivalTime: 26 Apr 2006 17:32:52.0706 (UTC) FILETIME=[72487420:01C66957] X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.4.26.95108 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Guillaume: Based on your and Tatu's exchange, I took a closer look at the Codehaus Sta= x homepage and agree with you that the page does not make the licensing cle= ar. On November 28, 2005, BEA's JSR Spec Lead, Ron Benson, provided Codehaus (C= hris Fry and Aleksander Slominski) with updated packages for placing on the= Codehaus StAX download page. Those packages included a "readme.txt" file = explaining the licensing and the "ASF2.0.txt" file providing the ASF 2.0 li= cense T's & C's as part of the bundle. For some reason the readme and ASF license text files were removed from the= bundle and are not provided as part of the download on the Codehaus page. = That contributes to the confusion. That said, Roy Fielding raised an excellent point with respect to the API. = It had been BEA's intention to offer both the RI jar and API jar under an = ASF 2.0 license. I am checking with Sun to verify whether we can license t= he API jar under an ASF 2.0 license consistent with our obligations under t= he JSPA. I will advise the Codehaus team and the thread on the outcome of that discu= ssion. Regards, Jim -----Original Message----- From: Guillaume Nodet [mailto:guillaume.nodet@worldonline.fr]=20 Sent: Wednesday, April 26, 2006 8:44 AM To: stax_builders@yahoogroups.com Cc: legal-discuss@apache.org Subject: Re: [stax_builders] Re: StAX (JSR 173) API source license Tatu Saloranta wrote: > --- nodetguillaume > wrote: > > > Would it be possible to clarify the license for the > > api jar on stax > > codehaus site ? > > It is said that the implementation is under ASL, but > > nothing is said > > about the spec jar. > > This would be good, but this is completely dependant > on BEA. No one else can get things resolved; and > progress has not exactly been stellar so far. ;-/ > (although other people like Alek and myself have > access to repository, we are not BEA employees, and > BEA as the spec sponsor owns many of copyrights, as > bounded by JSR/JCP process I think) Then it would be nice to say on the site that the api spec is not=20 licensed under ASL. I just need clarification for the license of the api jars available from=20 stax.codehaus.org, I did not meant any relicense (yet). > > > Also, what about the 1.0.1 jar of this api ? Is this > > an official > > update of the api ? > > No: API is identical to 1.0; but since the > implementation of one particular part of > XMLInputFactory had a bug (NullPointerException if > jaxp.properties file existed, but had no entry for > javax.xml.stream.XMLInputFactory), this was fixed in > source. Thus, a patch build. Not even obvious error(s) > were fixed (like XMLOutputFactory.newInstance(...) > return XMLInputFactory), since official release would > require official action from the WG. > > Also, I am bit puzzled by this rumor that there are > multiple incompatible versions of StAX API. I have > seen the claim multiple times... but never actual > explanation as to what is supposed to be different. Is > this just a rumour/misunderstanding, or is there an > older revision of the API floating around? > Just that it seems very unclear what the reference spec jar is, what the license for the tree different jars are, etc... Also, i ' m not even sure we can rewrite a specification jar only. The licensing terms of the RI are not very clear (for me) on that point. It seems that implementation have to pass the TCK, or something like that, but what about the api ? I think it would be easier to just rewrite it under an Apache license... Cheers, Guillaume Nodet > -+ Tatu +- > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > SPONSORED LINKS > Design software=20 > =20 > Builder software=20 > =20 > Api=20 > =20 > > Software=20 > =20 > Streaming software=20 > =20 > Forms software=20 > =20 > > > > ------------------------------------------------------------------------ > YAHOO! GROUPS LINKS > > * Visit your group "stax_builders > " on the web. >=20=20=20=20=20=20=20=20 > * To unsubscribe from this group, send an email to: > stax_builders-unsubscribe@yahoogroups.com > >=20=20=20=20=20=20=20=20 > * Your use of Yahoo! Groups is subject to the Yahoo! Terms of > Service . > > > ------------------------------------------------------------------------ > --------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See for official ASF policies and documents. --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org --=20 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.6/324 - Release Date: 4/25/2006 =20 --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.6/324 - Release Date: 4/25/2006 =20 _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See for official ASF policies and documents. --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org