From general-returnhalljames@example.net Fri Apr 01 01:08:40 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 68622 invoked from network); 1 Apr 2005 01:08:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2005 01:08:40 -0000 Received: (qmail 87907 invoked by uid 500); 1 Apr 2005 01:08:38 -0000 Delivered-To: halljames@example.net Received: (qmail 87850 invoked by uid 500); 1 Apr 2005 01:08:38 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Delivered-To: moderator for halljames@example.net Received: (qmail 52551 invoked by uid 99); 31 Mar 2005 16:41:08 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Date: Thu, 31 Mar 2005 08:41:20 -0800 From: Eduardo Pelegri-Llopart <halljames@example.net> Subject: Re: Donation of JAXP 1.3 Sources to Apache In-reply-to: <halljames@example.net> To: "Geir Magnusson Jr." <halljames@example.net> Cc: halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, Jeff Suttor <halljames@example.net>, halljames@example.net, halljames@example.net, halljames@example.net, halljames@example.net, halljames@example.net Message-id: <halljames@example.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) References: <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks. It is good to see this issue moving forward. - eduard/o Geir Magnusson Jr. wrote: > > On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote: > >> xml-common, xerces & xalan communities, >> >> I have learnt that legal issues regarding donation has been resolved >> and latest version of CCLA has been signed. >> So would like to make the actual code grant of JAXP 1.3 APIs + >> implementation ASAP. I will start the preparation >> today and will be back with actual code grant with in 2 days. > > > I have that CCLA (picked it up on a visit to Sun) and will be forwarding > to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the ASF. > > geir > --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Fri Apr 01 09:42:48 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 33665 invoked from network); 1 Apr 2005 09:42:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2005 09:42:48 -0000 Received: (qmail 44362 invoked by uid 500); 1 Apr 2005 09:42:46 -0000 Delivered-To: halljames@example.net Received: (qmail 44255 invoked by uid 500); 1 Apr 2005 09:42:45 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Delivered-To: moderator for halljames@example.net Received: (qmail 30476 invoked by uid 99); 1 Apr 2005 05:52:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Date: Fri, 01 Apr 2005 11:22:46 +0530 From: Neeraj Bajaj <halljames@example.net> Subject: Re: Donation of JAXP 1.3 Sources to Apache In-reply-to: <halljames@example.net> To: halljames@example.net Cc: halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, Jeff Suttor <halljames@example.net>, halljames@example.net, halljames@example.net, halljames@example.net, halljames@example.net Reply-to: halljames@example.net Message-id: <halljames@example.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) References: <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Geir Magnusson Jr. wrote: > > On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote: > >> Excellent news! Thank to Sun folk and Geir for picking up the ball >> on this one. >> >> Note: once the papers are in the Hallowed Halls, I presume that >> Neeraj will get some consensus from xml-commons, xalan-dev, and >> xerces-j-dev as to how to actually check this in? > > > There is no need to wait until Hall Hallowed-ness has been achieved. > I have received them on behalf of the ASF, and don't let the process > hold things up. Great... Thanks Geir. No more held up is good - Neeraj --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Sun Apr 03 12:03:14 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 33988 invoked from network); 3 Apr 2005 12:03:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2005 12:03:13 -0000 Received: (qmail 95929 invoked by uid 500); 3 Apr 2005 12:03:12 -0000 Delivered-To: halljames@example.net Received: (qmail 95579 invoked by uid 500); 3 Apr 2005 12:03:09 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Delivered-To: moderator for halljames@example.net Received: (qmail 36082 invoked by uid 99); 3 Apr 2005 07:40:54 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Date: Sun, 03 Apr 2005 13:10:57 +0530 From: Neeraj Bajaj <halljames@example.net> Subject: Re: Donation of JAXP 1.3 Sources to Apache In-reply-to: <halljames@example.net> To: halljames@example.net Cc: halljames@example.net, halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, Jeff Suttor <halljames@example.net>, halljames@example.net, halljames@example.net, halljames@example.net, Janet Breuer <halljames@example.net> Reply-to: halljames@example.net Message-id: <halljames@example.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) References: <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello All, I sent the mail below with JAXP 1.3 APIs source code attached as zip but mail bounced back with the following message <error> ----- The following addresses had permanent fatal errors ----- <halljames@example.net> (reason: 552 ZIP attachments are not accepted here.) </error> What should i do now ? Is there a way to upload sources on Apache server somewhere ? Can anyone guide me what is the procedure for such code grants ? I am looking help from the active committers of Xerces & Xalan community to help put it in a a branch and make it work there. As i think due to large number of changes it would be a considerable amount of work. This will also help the committers & community to have a look at the code before it is merged into the main stream work. I think i have commit access at xml-commons so i can commit the sources in xml-commons branch or main trunk (and create branch for old jaxp sources ). What is the opinion of community ? I can start this as soon as i get a consensus from the community. My preference is to put the sources on xml-commons main trunk. Please let me know how should i proceed. Thanks, - Neeraj Hello All, *Sun Microsystems donates the source code of JAXP 1.3 APIs + implementation to Apache XML.* JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is significant advancement over JAXP 1.2 and adds whole lot of new functionalities. * New Schema Validation Framework * New Object Model neutral XPath APIs * New Java datatypes which maps to XML Schema Datatypes. * Reuse parser instance * Security enhancements * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX 2, XML 1.1 and XInclude) *JAXP 1.3 APIs source code is attached with this mail. * Due to large size of code base i will be sending different mails for the source code of Xerces & Xalan. I have attached the original mail where i proposed the process of upgrading xml-commons to JAXP 1.3 APIs and integrating this donation into the main stream work of Xerces & Xalan. There was a general consensus to my proposal and we can discuss more about the technicalities of merging with in the appropriate (Xml-commons, Xerces, Xalan) community. Let's upgrade to JAXP 1.3 :-) - Neeraj Neeraj Bajaj wrote: > > > Geir Magnusson Jr. wrote: > >> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote: >> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball >>> on this one. >>> >>> Note: once the papers are in the Hallowed Halls, I presume that >>> Neeraj will get some consensus from xml-commons, xalan-dev, and >>> xerces-j-dev as to how to actually check this in? >> >> >> >> >> There is no need to wait until Hall Hallowed-ness has been achieved. >> I have received them on behalf of the ASF, and don't let the process >> hold things up. > > > > > Great... Thanks Geir. No more held up is good > > - Neeraj > > --------------------------------------------------------------------- > To unsubscribe, e-mail: halljames@example.net > For additional commands, e-mail: halljames@example.net > ------------------------------------------------------------------------ Subject: Donation of JAXP 1.3 Sources to Apache From: Neeraj Bajaj <halljames@example.net> Date: Tue, 12 Oct 2004 17:32:14 +0530 To: halljames@example.net CC: xerces-j-dev <halljames@example.net>, xerces-j-user <halljames@example.net>, halljames@example.net, halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, Jeff Suttor <halljames@example.net>, "norman.walsh" <halljames@example.net>, halljames@example.net Hello All, As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP 1.3 adds lots of new features in the area of XML processing. It introduces new Schema independent validation framework which decouples the validation as a process independent from parsing. It allows to compile Schema to an immutable memory representation of Grammar which can validate different instances of XML document thus greatly improving the performance of XML processing. XPath language provides a simple, concise syntax for accessing individual parts of an XML document. JAXP 1.3 defines XPath APIs which provides access to the XPath evaluation environment and expression results independent of the underlying data object model. JAXP 1.3 also adds new Datatypes to the Java platform which maps to some of the W3C XML Schema Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds the ability to reset XML Parser and Transformer instance , allowing application to reuse the same instance to process multiple XML documents. This also helps in increasing XML processing performance. JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML 1.1, XInclude. *Sun Microsystems would like to donate JAXP 1.3 sources (API s + Reference Implementation) to Apache. * /Details of JAXP 1.3 sources to be donated:/ JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference Implementation). RI has been done using Xerces/Xalan as code base. RI contains the implementation of newly introduced Validation Framework [2], XPath APIs [3] , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer Reset changes, Secured XML Processing changes. Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude already exist on Apache Xerces. So in the next section I have also proposed the way to merge rest of the JAXP 1.3 RI changes into Apache Xerces & Xalan project. I have also suggested where implementation component should reside i.e. Xerces or Xalan. Any idea or feedback for the smoother and expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces & Xalan is very welcome. *JAXP 1.3 APIs: * JAXP APIs has been at xml-commons for a long time as these set of APIs are used by many different projects. With JSR 206 declared as final and many new standards emerging, we should update xml-commons to JAXP 1.3 APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk and apply a tag. *JAXP 1.3 RI: (Implementation components that should be part of Xerces)* JAXP 1.3 RI contains the implementation of following packages javax.xml.datatype javax.xml.validation javax.xml.parsers ( reset(), xinclude, etc.) which should halljames@example.net. I propose that we create a branch, and merge JAXP 1.3 RI changes into that branch. This will help other Xerces active committers to have a chance to look at it before these changes being finally committed to main trunk. This process would require merging changes to the branch and then committing changes to main trunk, i seek help of active Xerces committers. *JAXP 1.3 RI: (Implementation components that should be part of Xalan)* JAXP 1.3 RI also has the implementation of newly developed XPath (javax.xml.xpath.*) APIs which i think, should be part of Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes done in "javax.xml.transform" package for ex. now application can use the same Transformer instance by invoking reset(). I propose the same for the Xalan/XSLTC project that we create a branch and JAXP 1.3 Reference Implementation changes are put there. This will help other Xalan active committers to have a chance to look at it before these changes being finally committed to main trunk. Again i seek help of Xalan committers for this process. As always, all feedbacks are more than welcome. Thanks, Neeraj [1] http://www.jcp.org/en/jsr/detail?id=206 [2] http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html [3] http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html [4] http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Sun Apr 03 15:03:29 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 57191 invoked from network); 3 Apr 2005 15:03:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2005 15:03:28 -0000 Received: (qmail 22698 invoked by uid 500); 3 Apr 2005 15:03:26 -0000 Delivered-To: halljames@example.net Received: (qmail 22591 invoked by uid 500); 3 Apr 2005 15:03:26 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 22577 invoked by uid 99); 3 Apr 2005 15:03:26 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from i.meepzor.com (HELO Boron.MeepZor.Com) (83.161.120.155) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 03 Apr 2005 08:03:23 -0700 Received: from [83.161.120.155] (dsl093-240-231.ral1.dsl.speakeasy.net [83.161.120.155]) by Boron.MeepZor.Com (8.12.8/8.12.8) with ESMTP id j33F3AK5003278; Sun, 3 Apr 2005 11:03:11 -0400 Message-ID: <halljames@example.net> Date: Sun, 03 Apr 2005 11:02:53 -0400 From: Rodent of Unusual Size <halljames@example.net> Reply-To: halljames@example.net Organization: The Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: halljames@example.net Subject: Re: [VOTE] Graduate Derby from the incubator References: <halljames@example.net> <halljames@example.net> In-Reply-To: <halljames@example.net> X-Enigmail-Version: 83.161.120.155 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- Ted Leung wrote: > > -1 > > I am surprised that people think the committer diversity issues are not > an issue for graduation. If Derby's destination was to be a TLP, I would agree completely, and not even have started this. As it is, however, it's headed to join an existing TLP -- the DB project. If a podling is destined the become a TLP, it obviously needs to demonstrate conformance and viability across all aspects. If it's going to become part of an existing TLP, however, I think the emphasis is (or should be) much more on making sure the contribution is safe (IP issues) and that the people will fit into the Apache milieu. Growing the committer list is something I think is reasonable to pass over to the parent TLP, at least once the podling has shown that it's willing to acquire diversity. The TLP will be providing some diversity of its own, since it has a PMC of which the podling's PPMC will only be a part, and the TLP will provide continuance of the oversight begun in the incubator. I *don't* think it's the job of the incubator to duplicate work the TLPs can and do handle themselves. The incubator's unique added-value is vetting the contribution and educating the community coming to Apache as a blob rather than as individuals. If a TLP starts up its own new package, does any of it have to go through the incubator? No, because the code will be starting with the right IP and the committers are already part of the Apache environment. The incubator's task is to make sure that something coming in from outside can mesh as well as something started from inside. An internally-started package can fail due to lack of diversity (among other things) just as much as one coming from outside. At least one person from the DB PMC has voted in favour of graduation, which I hope means that the project understands the issues of assuming oversight and feels comfortable doing so. Having more people from the DB PMC/project weigh in on the vote would be nice. :-) I'm in favour of graduation because I don't think there's anything more the incubator can do for Derby aside from erecting obstacles for the package and a group of people who have already demonstrated that they mesh well with our methodology. However, I think I'm too close to the issue, which is why I'm not voting. At least not yet. - -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQlAFnJrNPMCpn3XdAQFuCAP/at0nKxCTslUa3OyNlzdz7fYEQNpLHl1g 2372J+LaNxgrSzHxWbvXytekxeE3G98oT2ympTa9thk7kVAtrqlKxD1Ozb3aolnh Witb1zwp4g/IJZNMV1H6nEdZ54Buoojw4V80NZ0XHbWla8popV/ieXrl1NhzXCJb iN/oVEnGvrU= =bMaV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Sun Apr 03 15:51:18 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 63168 invoked from network); 3 Apr 2005 15:51:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2005 15:51:17 -0000 Received: (qmail 63188 invoked by uid 500); 3 Apr 2005 15:51:16 -0000 Delivered-To: halljames@example.net Received: (qmail 63088 invoked by uid 500); 3 Apr 2005 15:51:15 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 63075 invoked by uid 99); 3 Apr 2005 15:51:15 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from pointer.webappcabaret.net (HELO pointer.webappcabaret.net) (83.161.120.155) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 03 Apr 2005 08:51:14 -0700 Received: (qmail 16549 invoked by uid 98); 3 Apr 2005 08:51:11 -0700 Received: from unknown (HELO ?83.161.120.155?) (halljames@example.net@83.161.120.155) by localhost with SMTP; 3 Apr 2005 08:51:11 -0700 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <halljames@example.net> References: <halljames@example.net> <halljames@example.net> <halljames@example.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <halljames@example.net> Content-Transfer-Encoding: 7bit From: Brian McCallister <halljames@example.net> Subject: Re: [VOTE] Graduate Derby from the incubator Date: Sun, 3 Apr 2005 11:51:10 -0400 To: halljames@example.net X-Mailer: Apple Mail (2.619.2) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Apr 3, 2005, at 11:02 AM, Rodent of Unusual Size wrote: > At least one person from the DB PMC has voted in favour of graduation, > which I hope means that the project understands the issues of > assuming oversight and feels comfortable doing so. Having more > people from the DB PMC/project weigh in on the vote would be > nice. :-) DB PMC hat on: The only thing weighing on me about graduating Derby is that all the committers, but one, work for the same employer. There are a number of other folks under consideration, but they aren't committers (yet, hopefully). Ken makes a good point about it not being a TLP, and the DB PMC prodding the developer community growth. I have to agree with this argument, especially when I put it next to the DdlUtils project (commons-sql) with, er, two committers. Derby depends on nothing else at Apache (except ant for its build), and is depended on by nothing halljames@example.net. This is *good* from a technical point of view, but is a weakness from a community health point of view. To use DdlUtils as an example again, despite that project having only two (active) committers on the project, another Db project, OJB is dependent on the project (which is a big chunk of the reason we want to get it out of the commons sandbox), and has a strong motivation therefore to keep it going. OJB has a pretty good sized committer base, and has already pushed past the ~retirement of the initial project leader (who still pokes his head in on big design issues, but is otherwise pretty much inactive). So, despite DdlUtils having a small committer base when aiming for the same level in the ASF hierarchy (subproject), it has a much larger developer community strongly motivated to maintain it, even if they are not committers on it now. Derby has a much larger committer base, but that committer base is rather homogenous by ASF standards. No other ASF projects I am aware of (except maybe Geronimo?) actually use Derby right now, or use it in such a way that swapping out to HSQLDB isn't trivial. This lack of dependency is good, technically, but does not build a strong community support system (if all the BeanUtils committers were hit by trucks, there is no real doubt that other Struts folks would step in immediately). DB PMC hat off: I don't doubt the long-term viability of Derby. It is a great project which works well, and has a responsive and growing developer community. Even if the IBM committers were to be informed they were no longer allowed to contribute under terms of their employment, I am confident that despite the slowdown that would occur, the developer community would step up (the db pmc would just need to do more work in the interim). I don't know "official ASF policy" on subproject acceptance (if there even is such a thing), so have timeboxed my voting decision so that I can learn more before having to chime in =) -Brian --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Sun Apr 03 21:03:18 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 57859 invoked from network); 3 Apr 2005 21:03:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2005 21:03:18 -0000 Received: (qmail 14776 invoked by uid 500); 3 Apr 2005 21:03:15 -0000 Delivered-To: halljames@example.net Received: (qmail 14683 invoked by uid 500); 3 Apr 2005 21:03:15 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Delivered-To: moderator for halljames@example.net Received: (qmail 2708 invoked by uid 99); 3 Apr 2005 20:50:05 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) In-Reply-To: <halljames@example.net> To: halljames@example.net Cc: halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, halljames@example.net, halljames@example.net, Janet Breuer <halljames@example.net>, Jeff Suttor <halljames@example.net>, halljames@example.net, halljames@example.net, halljames@example.net MIME-Version: 1.0 Subject: Re: Donation of JAXP 1.3 Sources to Apache X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: <halljames@example.net> From: Michael Glavassevich <halljames@example.net> Date: Sun, 3 Apr 2005 16:49:57 -0400 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 6.53HF247 | January 6, 2005) at 04/03/2005 16:50:00, Serialize complete at 04/03/2005 16:50:00 Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Neeraj, +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and making a branch for the old JAXP sources on the current main trunk. There exists a branch called tck-jaxp-1_2_0 where fixes and other updates have been applied to the JAXP 1.2 sources. This is the branch we've used for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a similar branch will exist for 1.3. Neeraj Bajaj <halljames@example.net> wrote on 04/03/2005 03:40:57 AM: > Hello All, > > I sent the mail below with JAXP 1.3 APIs source code attached as zip but > mail bounced back with the following message > > <error> > ----- The following addresses had permanent fatal errors ----- > <halljames@example.net> > (reason: 552 ZIP attachments are not accepted here.) > </error> > > What should i do now ? Is there a way to upload sources on Apache > server somewhere ? > Can anyone guide me what is the procedure for such code grants ? > > I am looking help from the active committers of Xerces & Xalan community > to help put it in a > a branch and make it work there. As i think due to large number of > changes it would be a considerable > amount of work. This will also help the committers & community to have a > look at the code before > it is merged into the main stream work. > > I think i have commit access at xml-commons so i can commit the sources > in xml-commons branch > or main trunk (and create branch for old jaxp sources ). What is the > opinion of community ? I can > start this as soon as i get a consensus from the community. My > preference is to put the sources on > xml-commons main trunk. > > Please let me know how should i proceed. > > Thanks, > > - Neeraj > > > Hello All, > > *Sun Microsystems donates the source code of JAXP 1.3 APIs + > implementation to Apache XML.* > JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is > significant advancement over JAXP 1.2 and adds whole lot of new > functionalities. > > * New Schema Validation Framework > * New Object Model neutral XPath APIs > * New Java datatypes which maps to XML Schema Datatypes. > * Reuse parser instance > * Security enhancements > * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX > 2, XML 1.1 and XInclude) > > *JAXP 1.3 APIs source code is attached with this mail. * > > Due to large size of code base i will be sending different mails for the > source code of Xerces & Xalan. > > I have attached the original mail where i proposed the process of > upgrading xml-commons to JAXP 1.3 APIs and > integrating this donation into the main stream work of Xerces & Xalan. > There was a general consensus to my proposal > and we can discuss more about the technicalities of merging with in the > appropriate (Xml-commons, Xerces, Xalan) > community. > > Let's upgrade to JAXP 1.3 :-) > > - Neeraj > > > > Neeraj Bajaj wrote: > > > > > > > Geir Magnusson Jr. wrote: > > > >> > >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote: > >> > >>> Excellent news! Thank to Sun folk and Geir for picking up the ball > >>> on this one. > >>> > >>> Note: once the papers are in the Hallowed Halls, I presume that > >>> Neeraj will get some consensus from xml-commons, xalan-dev, and > >>> xerces-j-dev as to how to actually check this in? > >> > >> > >> > >> > >> There is no need to wait until Hall Hallowed-ness has been achieved. > >> I have received them on behalf of the ASF, and don't let the process > >> hold things up. > > > > > > > > > > Great... Thanks Geir. No more held up is good > > > > - Neeraj > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: halljames@example.net > > For additional commands, e-mail: halljames@example.net > > > > ------------------------------------------------------------------------ > > Subject: > Donation of JAXP 1.3 Sources to Apache > From: > Neeraj Bajaj <halljames@example.net> > Date: > Tue, 12 Oct 2004 17:32:14 +0530 > > To: > halljames@example.net > CC: > xerces-j-dev <halljames@example.net>, xerces-j-user > <halljames@example.net>, halljames@example.net, > halljames@example.net, Eduardo Pelegri-Llopart > <halljames@example.net>, Jeff Suttor <halljames@example.net>, > "norman.walsh" <halljames@example.net>, halljames@example.net > > > Hello All, > > > As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP > 1.3 adds lots of new features in the area of XML processing. > It introduces new Schema independent validation framework which > decouples the validation as a process independent from parsing. > It allows to compile Schema to an immutable memory representation of > Grammar which can validate different instances of XML document thus > greatly improving the performance of XML processing. XPath language > provides a simple, concise syntax for accessing individual parts of an > XML document. JAXP 1.3 defines XPath APIs which provides access to the > XPath evaluation environment and expression results independent > of the underlying data object model. JAXP 1.3 also adds new Datatypes to > the Java platform which maps to some of the W3C XML Schema > Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds > the ability to reset XML Parser and Transformer instance , allowing > application to reuse the same instance to process multiple XML > documents. This also helps in increasing XML processing performance. > JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML > 1.1, XInclude. > > *Sun Microsystems would like to donate JAXP 1.3 sources (API s + > Reference Implementation) to Apache. * > > > /Details of JAXP 1.3 sources to be donated:/ > > JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference > Implementation). RI has been done using > Xerces/Xalan as code base. RI contains the implementation of newly > introduced Validation Framework [2], XPath APIs [3] > , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer > Reset changes, Secured XML Processing changes. > Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude > already exist on Apache Xerces. So in the next > section I have also proposed the way to merge rest of the JAXP 1.3 RI > changes into Apache Xerces & Xalan project. I have also > suggested where implementation component should reside i.e. Xerces or > Xalan. Any idea or feedback for the smoother and > expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces & > Xalan is very welcome. > > > > *JAXP 1.3 APIs: * > > JAXP APIs has been at xml-commons for a long time as these set of APIs > are used by many different projects. > With JSR 206 declared as final and many new standards emerging, we > should update xml-commons to JAXP 1.3 > APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk > and apply a tag. > > > *JAXP 1.3 RI: (Implementation components that should be part of Xerces)* > > > JAXP 1.3 RI contains the implementation of following packages > > javax.xml.datatype > javax.xml.validation > javax.xml.parsers ( reset(), xinclude, etc.) > > which should halljames@example.net. > > I propose that we create a branch, and merge JAXP 1.3 RI changes into > that branch. This will help > other Xerces active committers to have a chance to look at it before > these changes being finally > committed to main trunk. This process would require merging changes to > the branch and then committing > changes to main trunk, i seek help of active Xerces committers. > > > *JAXP 1.3 RI: (Implementation components that should be part of Xalan)* > > > JAXP 1.3 RI also has the implementation of newly developed XPath > (javax.xml.xpath.*) APIs which i think, should be part of > Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes > done in "javax.xml.transform" package > for ex. now application can use the same Transformer instance by > invoking reset(). > > I propose the same for the Xalan/XSLTC project that we create a branch > and JAXP 1.3 Reference Implementation changes are > put there. This will help other Xalan active committers to have a chance > to look at it before these changes being finally > committed to main trunk. Again i seek help of Xalan committers for this > process. > > > As always, all feedbacks are more than welcome. > > > Thanks, > Neeraj > > > [1] http://www.jcp.org/en/jsr/detail?id=206 > [2] > http://java.sun.com/j2se/1.5. > 0/docs/api/javax/xml/validation/package-summary.html > [3] > http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html > [4] > http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package- > summary.html > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: halljames@example.net > For additional commands, e-mail: halljames@example.net > Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: halljames@example.net E-mail: halljames@example.net --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Mon Apr 04 01:00:27 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 78661 invoked from network); 4 Apr 2005 01:00:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Apr 2005 01:00:25 -0000 Received: (qmail 80880 invoked by uid 500); 4 Apr 2005 01:00:23 -0000 Delivered-To: halljames@example.net Received: (qmail 80832 invoked by uid 500); 4 Apr 2005 01:00:23 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 80816 invoked by uid 99); 4 Apr 2005 01:00:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from suntzu.lyra.org (HELO suntzu.lyra.org) (83.161.120.155) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 03 Apr 2005 18:00:21 -0700 Received: from suntzu.lyra.org (localhost.localdomain [83.161.120.155]) by suntzu.lyra.org (8.12.11/8.12.11) with ESMTP id j340oIZ6013809 for <halljames@example.net>; Sun, 3 Apr 2005 17:50:18 -0700 Received: (from gstein@localhost) by suntzu.lyra.org (8.12.11/8.12.11/Submit) id j340oI3A013807 for halljames@example.net; Sun, 3 Apr 2005 17:50:18 -0700 X-Authentication-Warning: suntzu.lyra.org: gstein set sender to halljames@example.net using -f Date: Sun, 3 Apr 2005 17:50:17 -0700 From: Greg Stein <halljames@example.net> To: halljames@example.net Subject: Re: [VOTE] Graduate Derby from the incubator Message-ID: <halljames@example.net> References: <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <halljames@example.net> User-Agent: Mutt/1.4.1i X-URL: http://www.lyra.org/greg/ X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sun, Apr 03, 2005 at 11:51:10AM -0400, Brian McCallister wrote: > On Apr 3, 2005, at 11:02 AM, Rodent of Unusual Size wrote: > > >At least one person from the DB PMC has voted in favour of graduation, > >which I hope means that the project understands the issues of > >assuming oversight and feels comfortable doing so. Having more > >people from the DB PMC/project weigh in on the vote would be > >nice. :-) While that is great, it is really the Incubator's job to assess whether the project is Right And Proper for the ASF. Community issues *are* one of the items they review -- it's been on the checklist since day one. I think it would be imprudent to make exceptions because a target PMC "says it is fine with them." I *can* see both sides of the issue. I do recognize that a PMC is ultimately responsible for the community issues. But that has always been for existing projects. We already know there is an issue here, so why not deal with it now? >... > Derby depends on nothing else at Apache (except ant for its build), and > is depended on by nothing halljames@example.net. This is *good* from a > technical point of view, but is a weakness from a community health > point of view. This worries me even more. How is the DB PMC going to expand the community if it appears nobody else is "nearby" ? And why is graduation needed to fix the community? Why not now? Why not within the Incubator? Finally, I usually worry about PMC's oversight of sub-projects. If there is more than one developer list under a PMC, then you explicitly have partitioned communities. How is an existing PMC's community going to help grow another community if they are separated like that? To some extent, a PMC should be providing oversight to a *single* community. We've already seen problems with PMCs trying to review too many distinct communities. It just doesn't work. I realize that the DB PMC isn't an "umbrella" in the same sense as XML or Jakarta, but that is merely because it has fewer projects. It still has separate communities, and derby-dev will just be another one. Cheers, -g -- Greg Stein, http://www.lyra.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Mon Apr 04 03:40:22 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 806 invoked from network); 4 Apr 2005 03:40:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Apr 2005 03:40:22 -0000 Received: (qmail 88118 invoked by uid 500); 4 Apr 2005 03:40:20 -0000 Delivered-To: halljames@example.net Received: (qmail 88073 invoked by uid 500); 4 Apr 2005 03:40:19 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 88056 invoked by uid 99); 4 Apr 2005 03:40:19 -0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=RCVD_IN_NJABL_PROXY X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from Unknown (HELO f1.bali.ac) (83.161.120.155) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 03 Apr 2005 20:40:18 -0700 Received: from clt-5-162.netcompartner.com ([83.161.120.155]) (authenticated bits=0) by f1.bali.ac (8.12.8/8.12.8) with ESMTP id j343nxVp031313 for <halljames@example.net>; Mon, 4 Apr 2005 11:50:10 +0800 From: Niclas Hedhman <halljames@example.net> To: halljames@example.net Subject: Re: [VOTE] Graduate Derby from the incubator Date: Mon, 4 Apr 2005 11:39:59 +0800 User-Agent: KMail/1.7.1 References: <halljames@example.net> <halljames@example.net> <halljames@example.net> In-Reply-To: <halljames@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <halljames@example.net> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Monday 04 April 2005 08:50, Greg Stein wrote: > Finally, I usually worry about PMC's oversight of sub-projects. If there > is more than one developer list under a PMC, then you explicitly have > partitioned communities. How is an existing PMC's community going to help > grow another community if they are separated like that? To some extent, a > PMC should be providing oversight to a *single* community. Yes. Start the path to TLP-only and drop partitioning of communities. Problem of information overload will occur for the Board, but it can streamline its reporting and command chains through delegation and other mechanisms. Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Mon Apr 04 10:02:04 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 83624 invoked from network); 4 Apr 2005 10:02:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Apr 2005 10:02:04 -0000 Received: (qmail 88424 invoked by uid 500); 4 Apr 2005 10:02:00 -0000 Delivered-To: halljames@example.net Received: (qmail 88119 invoked by uid 500); 4 Apr 2005 10:01:57 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Delivered-To: moderator for halljames@example.net Received: (qmail 52699 invoked by uid 99); 4 Apr 2005 05:07:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Date: Mon, 04 Apr 2005 10:37:18 +0530 From: Neeraj Bajaj <halljames@example.net> Subject: Re: Donation of JAXP 1.3 Sources to Apache In-reply-to: <halljames@example.net> To: halljames@example.net Cc: halljames@example.net, halljames@example.net, Eduardo Pelegri-Llopart <halljames@example.net>, halljames@example.net, halljames@example.net, Janet Breuer <halljames@example.net>, Jeff Suttor <halljames@example.net>, halljames@example.net Reply-to: halljames@example.net Message-id: <halljames@example.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) References: <halljames@example.net> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks Michael for your response. I was just wondering what would be idle time to wait before i start work on this ? Does anyone has an opinion, Is there any other list where i should send this mail before making changes ? - Neeraj Michael Glavassevich wrote: >Hi Neeraj, > >+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and >making a branch for the old JAXP sources on the current main trunk. > >There exists a branch called tck-jaxp-1_2_0 where fixes and other updates >have been applied to the JAXP 1.2 sources. This is the branch we've used >for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a >similar branch will exist for 1.3. > >Neeraj Bajaj <halljames@example.net> wrote on 04/03/2005 03:40:57 AM: > > > >>Hello All, >> >>I sent the mail below with JAXP 1.3 APIs source code attached as zip but >> >> > > > >>mail bounced back with the following message >> >><error> >> ----- The following addresses had permanent fatal errors ----- >><halljames@example.net> >> (reason: 552 ZIP attachments are not accepted here.) >></error> >> >>What should i do now ? Is there a way to upload sources on Apache >>server somewhere ? >>Can anyone guide me what is the procedure for such code grants ? >> >>I am looking help from the active committers of Xerces & Xalan community >> >> > > > >>to help put it in a >>a branch and make it work there. As i think due to large number of >>changes it would be a considerable >>amount of work. This will also help the committers & community to have a >> >> > > > >>look at the code before >>it is merged into the main stream work. >> >>I think i have commit access at xml-commons so i can commit the sources >>in xml-commons branch >>or main trunk (and create branch for old jaxp sources ). What is the >>opinion of community ? I can >>start this as soon as i get a consensus from the community. My >>preference is to put the sources on >>xml-commons main trunk. >> >>Please let me know how should i proceed. >> >>Thanks, >> >>- Neeraj >> >> >>Hello All, >> >>*Sun Microsystems donates the source code of JAXP 1.3 APIs + >>implementation to Apache XML.* >>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is >>significant advancement over JAXP 1.2 and adds whole lot of new >>functionalities. >> >>* New Schema Validation Framework >>* New Object Model neutral XPath APIs >>* New Java datatypes which maps to XML Schema Datatypes. >>* Reuse parser instance >>* Security enhancements >>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX >> >> > > > >>2, XML 1.1 and XInclude) >> >>*JAXP 1.3 APIs source code is attached with this mail. * >> >>Due to large size of code base i will be sending different mails for the >> >> > > > >>source code of Xerces & Xalan. >> >>I have attached the original mail where i proposed the process of >>upgrading xml-commons to JAXP 1.3 APIs and >>integrating this donation into the main stream work of Xerces & Xalan. >>There was a general consensus to my proposal >>and we can discuss more about the technicalities of merging with in the >>appropriate (Xml-commons, Xerces, Xalan) >>community. >> >>Let's upgrade to JAXP 1.3 :-) >> >>- Neeraj >> >> >> >>Neeraj Bajaj wrote: >> >> >> >>>Geir Magnusson Jr. wrote: >>> >>> >>> >>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote: >>>> >>>> >>>> >>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball >>>>>on this one. >>>>> >>>>>Note: once the papers are in the Hallowed Halls, I presume that >>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and >>>>>xerces-j-dev as to how to actually check this in? >>>>> >>>>> >>>> >>>> >>>>There is no need to wait until Hall Hallowed-ness has been achieved. >>>>I have received them on behalf of the ASF, and don't let the process >>>>hold things up. >>>> >>>> >>> >>> >>>Great... Thanks Geir. No more held up is good >>> >>>- Neeraj >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: halljames@example.net >>>For additional commands, e-mail: halljames@example.net >>> >>> >>> >>------------------------------------------------------------------------ >> >>Subject: >>Donation of JAXP 1.3 Sources to Apache >>From: >>Neeraj Bajaj <halljames@example.net> >>Date: >>Tue, 12 Oct 2004 17:32:14 +0530 >> >>To: >>halljames@example.net >>CC: >>xerces-j-dev <halljames@example.net>, xerces-j-user >><halljames@example.net>, halljames@example.net, >>halljames@example.net, Eduardo Pelegri-Llopart >><halljames@example.net>, Jeff Suttor <halljames@example.net>, >>"norman.walsh" <halljames@example.net>, halljames@example.net >> >> >>Hello All, >> >> >>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP >> >> > > > >>1.3 adds lots of new features in the area of XML processing. >>It introduces new Schema independent validation framework which >>decouples the validation as a process independent from parsing. >>It allows to compile Schema to an immutable memory representation of >>Grammar which can validate different instances of XML document thus >>greatly improving the performance of XML processing. XPath language >>provides a simple, concise syntax for accessing individual parts of an >>XML document. JAXP 1.3 defines XPath APIs which provides access to the >>XPath evaluation environment and expression results independent >>of the underlying data object model. JAXP 1.3 also adds new Datatypes to >> >> > > > >>the Java platform which maps to some of the W3C XML Schema >>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds >>the ability to reset XML Parser and Transformer instance , allowing >>application to reuse the same instance to process multiple XML >>documents. This also helps in increasing XML processing performance. >>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML >> >> > > > >>1.1, XInclude. >> >>*Sun Microsystems would like to donate JAXP 1.3 sources (API s + >>Reference Implementation) to Apache. * >> >> >>/Details of JAXP 1.3 sources to be donated:/ >> >>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference >>Implementation). RI has been done using >>Xerces/Xalan as code base. RI contains the implementation of newly >>introduced Validation Framework [2], XPath APIs [3] >>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer >>Reset changes, Secured XML Processing changes. >>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude >>already exist on Apache Xerces. So in the next >>section I have also proposed the way to merge rest of the JAXP 1.3 RI >>changes into Apache Xerces & Xalan project. I have also >>suggested where implementation component should reside i.e. Xerces or >>Xalan. Any idea or feedback for the smoother and >>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces & >>Xalan is very welcome. >> >> >> >>*JAXP 1.3 APIs: * >> >>JAXP APIs has been at xml-commons for a long time as these set of APIs >>are used by many different projects. >>With JSR 206 declared as final and many new standards emerging, we >>should update xml-commons to JAXP 1.3 >>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk >>and apply a tag. >> >> >>*JAXP 1.3 RI: (Implementation components that should be part of >> >> >Xerces)* > > >>JAXP 1.3 RI contains the implementation of following packages >> >>javax.xml.datatype >>javax.xml.validation >>javax.xml.parsers ( reset(), xinclude, etc.) >> >>which should halljames@example.net. >> >>I propose that we create a branch, and merge JAXP 1.3 RI changes into >>that branch. This will help >>other Xerces active committers to have a chance to look at it before >>these changes being finally >>committed to main trunk. This process would require merging changes to >>the branch and then committing >>changes to main trunk, i seek help of active Xerces committers. >> >> >>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)* >> >> >>JAXP 1.3 RI also has the implementation of newly developed XPath >>(javax.xml.xpath.*) APIs which i think, should be part of >>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes >>done in "javax.xml.transform" package >>for ex. now application can use the same Transformer instance by >>invoking reset(). >> >>I propose the same for the Xalan/XSLTC project that we create a branch >>and JAXP 1.3 Reference Implementation changes are >>put there. This will help other Xalan active committers to have a chance >> >> > > > >>to look at it before these changes being finally >>committed to main trunk. Again i seek help of Xalan committers for this >> >> > > > >>process. >> >> >>As always, all feedbacks are more than welcome. >> >> >>Thanks, >>Neeraj >> >> >>[1] http://www.jcp.org/en/jsr/detail?id=206 >>[2] >>http://java.sun.com/j2se/1.5. >>0/docs/api/javax/xml/validation/package-summary.html >>[3] >> >> >> >http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html > > >>[4] >>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package- >>summary.html >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: halljames@example.net >>For additional commands, e-mail: halljames@example.net >> >> >> > >Michael Glavassevich >XML Parser Development >IBM Toronto Lab >E-mail: halljames@example.net >E-mail: halljames@example.net > >--------------------------------------------------------------------- >To unsubscribe, e-mail: halljames@example.net >For additional commands, e-mail: halljames@example.net > > > --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Mon Apr 04 13:57:35 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 50463 invoked from network); 4 Apr 2005 13:57:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Apr 2005 13:57:34 -0000 Received: (qmail 76063 invoked by uid 500); 4 Apr 2005 13:56:28 -0000 Delivered-To: halljames@example.net Received: (qmail 75924 invoked by uid 500); 4 Apr 2005 13:56:26 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 75897 invoked by uid 99); 4 Apr 2005 13:56:26 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from chi.mobile-health-diary.com (HELO chi.mobile-health-diary.com) (83.161.120.155) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 04 Apr 2005 06:56:25 -0700 Received: (qmail 18334 invoked from network); 4 Apr 2005 13:56:22 -0000 Received: from ool-43560634.dyn.optonline.net (HELO ?83.161.120.155?) (halljames@example.net) by b014.internal.mobile-health-diary.com with SMTP; 4 Apr 2005 13:56:22 -0000 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <halljames@example.net> References: <halljames@example.net> <halljames@example.net> <halljames@example.net> <halljames@example.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <halljames@example.net> Content-Transfer-Encoding: 7bit From: Geir Magnusson Jr. <halljames@example.net> Subject: Re: [VOTE] Graduate Derby from the incubator Date: Mon, 4 Apr 2005 09:56:23 -0400 To: halljames@example.net X-Mailer: Apple Mail (2.619) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Apr 3, 2005, at 11:51 AM, Brian McCallister wrote: > Derby depends on nothing else at Apache (except ant for its build), > and is depended on by nothing halljames@example.net. This is *good* from a > technical point of view, but is a weakness from a community health > point of view. Geronimo uses it. -- Geir Magnusson Jr +1-914-664-6866 halljames@example.net --------------------------------------------------------------------- To unsubscribe, e-mail: halljames@example.net For additional commands, e-mail: halljames@example.net From general-returnhalljames@example.net Mon Apr 04 14:39:06 2005 Return-Path: <general-returnhalljames@example.net> Delivered-To: halljames@example.net Received: (qmail 63344 invoked from network); 4 Apr 2005 14:39:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Apr 2005 14:39:06 -0000 Received: (qmail 55197 invoked by uid 500); 4 Apr 2005 14:39:04 -0000 Delivered-To: halljames@example.net Received: (qmail 54915 invoked by uid 500); 4 Apr 2005 14:39:03 -0000 Mailing-List: contact halljames@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:halljames@example.net> List-Unsubscribe: <mailto:halljames@example.net> List-Post: <mailto:halljames@example.net> List-Id: <general.incubator.apache.org> Reply-To: halljames@example.net Delivered-To: mailing list halljames@example.net Received: (qmail 54899 invoked by uid 99); 4
{'source': 'Apache Software Foundation Public Mail Archives'}