Return-Path: Mailing-List: contact general-help@xml.apache.org; run by ezmlm Delivered-To: mailing list general@xml.apache.org Received: (qmail 25330 invoked from network); 28 Feb 2001 07:32:09 -0000 Received: from lotus2.lotus.com (192.233.136.8) by h31.sny.collab.net with SMTP; 28 Feb 2001 07:32:09 -0000 Received: from internet1.lotus.com (internet1 [9.95.4.235]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id CAA20673 for ; Wed, 28 Feb 2001 02:37:24 -0500 (EST) From: Scott_Boag@lotus.com Received: from cammail04.lotus.com (CAMMAIL04.lotus.com [9.95.4.116]) by internet1.lotus.com (8.9.3/8.9.3) with ESMTP id CAA02180 for ; Wed, 28 Feb 2001 02:31:46 -0500 (EST) Subject: RE: Volunteers: First - cut - Deadline 2nd of March To: general@xml.apache.org X-Mailer: Lotus Notes Release 5.0.1 July 16, 1999 Message-ID: Date: Wed, 28 Feb 2001 02:35:31 -0500 X-MIMETrack: Serialize by Router on CAMMAIL04/CAM/M/Lotus(Release 5.0.6a |January 17, 2001) at 02/28/2001 02:27:47 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Kelly Campbell wrote: > Another thing I would like to promote as XML projects is UI tools for > working with XML, XSL, etc. I would like to see UI tools also. It seems like the classes of projects that xml.apache.org should handle are: 1) Low-level processing components that have XML as their base: Parser, XSLT processor, Soap, XLink, FOP, etc. AND AN XML DATABASE! 2) User level utilities that are enablers of XML: XML Editor, XSLT Editor, LinkMaker, Schema Editor (examples from the top of my head). 3) XML-specific testing aids, i.e. DOM comparitor, encoding tests, HTML comparitor? These might work in conjunction with a more general test infrastructure. 4) Cocoon because it is already here and because it is Cocoon. But Cocoon seems to me to go beyond pure XML specificity, and is more at the application level, so it's a bit on the borderline. See below about subjectivity. What did I miss? Shared utility infrastructure?? Psuedo-standard interfaces? Dirk-Willem van Gulik (vaio) wrote: > 2. Work with the ASF board to re-define it's current charter. > Right now it is too narrow and only covers XML parsers! While this is something that the PMC needs to do, I think now is a good time to have a general discussion. I believe the charter definition will continue to be somewhat subjective. As I said when the original PMC was first started, if the whole world is using XML (in spite of http://www.zdnet.com/zdnn/stories/comment/0,5859,2689765,00.html), then what is not an XML project? I believe we want to stick to pipe components that implement horizontal XML related standards, and probably UI editors for these standards, but that is my opinion... most people have one. -scott