Re: The Road to 3.0: Feature list/signup
Hi David, On Feb 18, 2005, at 9:52 AM, David Cargill wrote: I will sign up for... Thanks for all your great contributions. For #20, I vote against. I know of a few people who are still using it (yes I prompt them to move off of it). As of 2.6.0 it is in a separate library so I don't think it that keeping it around would be so bad... Since 3.0 is our "let's break compatibility now" release, what if we were to move the "deprecated-DOM" even beyond "deprecated" to an "unsupported" status? Then we have the option to remove it completely at some future point without breaking 3.x compatibility. Lastly, I think we should move this list into releases_plan.xml so we can track it. For items that aren't signed up for we should probably continue to carry forward with no one assigned to them so they don't get lost. Done, although I didn't regenerate the html, since I don't know how. James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hi James, I will sign up for testing the infrastructure changes on AIX, OS390 and Linux using xlC. I will see if I can find someone to test OS400 as well. For #20, I vote against. I know of a few people who are still using it (yes I prompt them to move off of it). As of 2.6.0 it is in a separate library so I don't think it that keeping it around would be so bad... I would also like to add: (26) Audit of all deprecated methods. We shouldn't remove SAXParser (and DeprecatedDOM :-) )but I think we should evaluate each deprecated method to see if it can be removed. This would be larger than item 22. I would be glad to put together the list of deprecated methods and get feedback on what we should keep (if any)... (11) Audit of XML Schema support. We currently document that we support the W3C Recommendation for May 2001. I think we should move up to the W3C Recommendation of October 2004. Hopefully, we have already addressed most of the errata but without doing the work can't say for sure. This is something I will also volunteer to look at it. (12) Const signature changes. In the original thread on this subject, Alberto identified the following 3 jira bugs that need signatures updated: - XERCESC-783: DOMUserDataHandler::handle specifies src and dst as const DOMNode*, but the specs say they are DOMNode* (and the user wants to modify them) - XERCESC-1153: XMLSchemaDescriptionImpl::getLocationHints should return a const object to prevent attempts to change its state - XERCESC-1223: DOMDocument::importNode should declare the source node as const DOMNode* -> I think I can handle these as well :-) Lastly, I think we should move this list into releases_plan.xml so we can track it. For items that aren't signed up for we should probably continue to carry forward with no one assigned to them so they don't get lost. Regards, David A. Cargill XML Parser Development IBM Toronto Lab (905) 413-2371, tie 969 [EMAIL PROTECTED] James Berry <[EMAIL PROTECTED] g> To xerces-c-dev@xml.apache.org 02/17/2005 05:02 cc PM Subject Re: The Road to 3.0: Feature Please respond to list/signup xerces-c-dev Folks, I've revised the feature list/signup list following contributions from people over the last week. Thank you all for your generous contributions of future-time. Please let me know what I got wrong, or missed, or if there's places you can help. If I don't hear any more by the end of the week, we'll work to finalize the proposed feature set, then make a decision for sure on whether it's 3.0 or 2.7... As it sits, it doesn't look like we'll do (1, 2, 7, or 10). -jdb Here's a list of potential tasks. Not all of them have to happen, and they certainly won't happen if we nobody will sign-up for the tasks: CALL FOR SIGN UP: Please respond indicating whether you'll sign up for the work. If there' s something else you want to contribute, please indicate. Help is needed where there is no resource specified, or where there's a question mark. (1) Reorganization of public/private includes (2) Revisiting/sanity checking of install locations (3) Refactoring of x-platform support 3.a. Initial cut James 3.b. Basic posix support James 3.b. Mac re-port/test James 3.c. Windows re-port/test Alberto 3.d. Linux re-port/test (may survive with basic posix...) Gareth Alberto [VMWare (Red Hat 9, Red Hat 7.3) and I can add more] Scott Cantor [test] 3.e. Solaris Scott Cantor [test] 3.f. Cygwin Neil 3.g. Additional platforms... Alberto [MinGW and Interix (AKA Microsoft Services For Unix)] (4) A true autoconf-based build infrastructure James Jason Stewart Scott Cantor John Snelson (5) Add a libcurl based netaccessor? James (a
Re: The Road to 3.0: Feature list/signup
Folks, I've revised the feature list/signup list following contributions from people over the last week. Thank you all for your generous contributions of future-time. Please let me know what I got wrong, or missed, or if there's places you can help. If I don't hear any more by the end of the week, we'll work to finalize the proposed feature set, then make a decision for sure on whether it's 3.0 or 2.7... As it sits, it doesn't look like we'll do (1, 2, 7, or 10). -jdb Here's a list of potential tasks. Not all of them have to happen, and they certainly won't happen if we nobody will sign-up for the tasks: CALL FOR SIGN UP: Please respond indicating whether you'll sign up for the work. If there' s something else you want to contribute, please indicate. Help is needed where there is no resource specified, or where there's a question mark. (1) Reorganization of public/private includes (2) Revisiting/sanity checking of install locations (3) Refactoring of x-platform support 3.a. Initial cut James 3.b. Basic posix support James 3.b. Mac re-port/test James 3.c. Windows re-port/test Alberto 3.d. Linux re-port/test (may survive with basic posix...) Gareth Alberto [VMWare (Red Hat 9, Red Hat 7.3) and I can add more] Scott Cantor [test] 3.e. Solaris Scott Cantor [test] 3.f. Cygwin Neil 3.g. Additional platforms... Alberto [MinGW and Interix (AKA Microsoft Services For Unix)] (4) A true autoconf-based build infrastructure James Jason Stewart Scott Cantor John Snelson (5) Add a libcurl based netaccessor? James (as time permits) (6) DOM 3.0 support Alberto Gareth (7) XPath??? (8) XInclude Gareth Caroline Rioux Graham Innocent (9) Add a ACE-based netaccessor Alberto (as time permits) (10) Add RelaxNG support (Michael Fuller -- would provide some help) (20) Remove deprecated DOM altogether. Gareth (21) Remove and/or update deprecated enums Gareth (22) Remove non-thread-safe psvi methods. Gareth (23) Remove Mac OS Classic support James (24) Remove OS/2 (or update it) Alberto (25) Remove Borland C++ 4, CodeWarrior, VACPP40 and Unsupported from Windows platform Alberto - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hey, (8) XInclude??? I have someone in mind for this. I will give them a shout today. A joint me, Caroline Rioux (a previous contributor to xerces and long time Pathan person) and Graham Innocent (a colleague of mine at Parthenon). Gareth -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hey, What would be involved in pulling it in Jason? Gareth On 17 Feb 2005, at 5:17, Jason E. Stewart wrote: James Berry <[EMAIL PROTECTED]> writes: Please respond indicating whether you'll sign up for the work. If there' s something else you want to contribute, please indicate. Help is needed where there is no resource specified, or where there's a question mark. Hi James, One thing that still hasn't been discussed is how we intend to fold in scripting language support for Xerces, i.e. having Xerces-P become a subproject of Xerces-C. One thing this will affect is using Perl to create a complete test suite of all public classes/methods. Perl's test harness is a really good match for this - IMHO... That would mean that there would be a single unified test harness. Xerces-P is built by using SWIG to parse the Xerces-C header files and auto-build a C++ interface file between Xerces-C and Perl. If scripting language support is merged in, the only burden on Xerces-C would be to ensure that when the public API is changed (modification of old methods/classes - addition of new methods/classes) that SWIG is re-run to create a new output file. Cheers, jas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hey, On 17 Feb 2005, at 5:19, Jason E. Stewart wrote: Gareth Reakes <[EMAIL PROTECTED]> writes: I'd *like* to suggest: (10) Add RelaxNG support but for the facts that a) I don't know how keen the Xerces team is on the idea of extending support to include RelaxNG as well as W3C XML Schema, and b) while I'd certainly be willing to help, I couldn't guarantee to contribute enough time to deliver it. I support the idea. It was certainly asked for a lot when we were at XML 2004. What existing libraries does James Clark have available for this? Could an existing library be converted to this job, are is it necessary to do a complete re-write for Xerces? I would think I rewrite. At the very least we would have to map to whatever data model / event model that the library required. But why don't we ask James :) I am sure he would advise us. I will fins his mail and drop him a note tomorrow. Gareth -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Gareth Reakes <[EMAIL PROTECTED]> writes: >> I'd *like* to suggest: >> (10) Add RelaxNG support >> but for the facts that a) I don't know how keen the Xerces team is on >> the idea of extending support to include RelaxNG as well as W3C XML Schema, >> and b) while I'd certainly be willing to help, I couldn't guarantee >> to contribute enough time to deliver it. > > I support the idea. It was certainly asked for a lot when we were at > XML 2004. What existing libraries does James Clark have available for this? Could an existing library be converted to this job, are is it necessary to do a complete re-write for Xerces? Cheers, jas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
James Berry <[EMAIL PROTECTED]> writes: > Please respond indicating whether you'll sign up for the work. If > there' s something else you want to contribute, please indicate. Help > is needed where there is no resource specified, or where there's a > question mark. Hi James, One thing that still hasn't been discussed is how we intend to fold in scripting language support for Xerces, i.e. having Xerces-P become a subproject of Xerces-C. One thing this will affect is using Perl to create a complete test suite of all public classes/methods. Perl's test harness is a really good match for this - IMHO... That would mean that there would be a single unified test harness. Xerces-P is built by using SWIG to parse the Xerces-C header files and auto-build a C++ interface file between Xerces-C and Perl. If scripting language support is merged in, the only burden on Xerces-C would be to ensure that when the public API is changed (modification of old methods/classes - addition of new methods/classes) that SWIG is re-run to create a new output file. Cheers, jas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
James Berry <[EMAIL PROTECTED]> writes: > (4) A true autoconf-based build infrastructure > James > Scott Cantor > John Snelson I would like to add myself to this list. I may not have a lot of time, but since Xerces-P would need this functionality, I would like to have a bit of input. Cheers, jas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hey, I'd *like* to suggest: (10) Add RelaxNG support but for the facts that a) I don't know how keen the Xerces team is on the idea of extending support to include RelaxNG as well as W3C XML Schema, and b) while I'd certainly be willing to help, I couldn't guarantee to contribute enough time to deliver it. I support the idea. It was certainly asked for a lot when we were at XML 2004. Gareth -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hi all, Gareth Reakes <[EMAIL PROTECTED]> wrote on 02/14/2005 11:01:37 AM: > >> CALL FOR SIGN UP: > >> > >> Please respond indicating whether you'll sign up for the work. If > >> there' s something else you want to contribute, please indicate. Help > >> is needed where there is no resource specified, or where there's a > >> question mark. > >> > >> (1) Reorganization of public/private includes > >> (2) Revisiting/sanity checking of install locations > >> (3) Refactoring of x-platform support > >> 3.a. Initial cut > >> James > >> 3.b. Basic posix support > >> James > >> 3.b. Mac re-port/test > >> James > >> 3.c. Windows re-port/test > > > > > > As a Windows developer, I can work on this task (Visual C++ 6, Visual > > .NET 2003, Borland C++ 5.51) > > > >> ? > >> 3.d. Linux re-port/test (may survive with basic posix...) > >> ? > > > > > > I have some Linux platforms under VMWare (Red Hat 9, Red Hat 7.3) and I > > can add more, if needed; but I guess Gareth and other can do it better > > than me, so keep me as a backup. > > I can take linux. I'll try and help with cygwin if things don't work out of the box after Linux gets added. I'm afraid that's about as ambitious as I can be at present. :( Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
[I hope you don't mind an outsider chipping in; apologies otherwise.] On Mon, Feb 14, 2005 at 02:38:33PM +0100, Alberto Massari wrote: > At 09.02 12/02/2005 -0800, James Berry wrote: > > >[...] > >Here's a list of potential tasks. Not all of them have to happen, and they > >certainly won't happen if we nobody will sign-up for the tasks: > > [...] > > (7) XPath??? > > (8) XInclude??? > > (9) Add a ACE-based netaccessor > Alby (as time permits) I'd *like* to suggest: (10) Add RelaxNG support but for the facts that a) I don't know how keen the Xerces team is on the idea of extending support to include RelaxNG as well as W3C XML Schema, and b) while I'd certainly be willing to help, I couldn't guarantee to contribute enough time to deliver it. Michael http://www.mds.rmit.edu.au/~msf/ Multimedia Databases Group, RMIT, Australia. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
Hey, Alberto Massari wrote: At 09.02 12/02/2005 -0800, James Berry wrote: [...] Here's a list of potential tasks. Not all of them have to happen, and they certainly won't happen if we nobody will sign-up for the tasks: CALL FOR SIGN UP: Please respond indicating whether you'll sign up for the work. If there' s something else you want to contribute, please indicate. Help is needed where there is no resource specified, or where there's a question mark. (1) Reorganization of public/private includes (2) Revisiting/sanity checking of install locations (3) Refactoring of x-platform support 3.a. Initial cut James 3.b. Basic posix support James 3.b. Mac re-port/test James 3.c. Windows re-port/test As a Windows developer, I can work on this task (Visual C++ 6, Visual .NET 2003, Borland C++ 5.51) ? 3.d. Linux re-port/test (may survive with basic posix...) ? I have some Linux platforms under VMWare (Red Hat 9, Red Hat 7.3) and I can add more, if needed; but I guess Gareth and other can do it better than me, so keep me as a backup. I can take linux. 3.e. Additional platforms... ? I can test MinGW and Interix (AKA Microsoft Services For Unix). (4) A true autoconf-based build infrastructure James Scott Cantor John Snelson (5) Add a libcurl based netaccessor? James (as time permits) (6) DOM 3.0 support? Well, I started this, so I have to sign up for this ;-) I will help Alby with this. (7) XPath??? I am happy to help with this, but think it should not be done now. (8) XInclude??? I have someone in mind for this. I will give them a shout today. (9) Add a ACE-based netaccessor Alby (as time permits) (20) Remove deprecated DOM altogether. Are we sure that its OK to do this? Anyone out there need it still? Speak now, or forever use and old version. (21) Remove and/or update deprecated enums Me (22) Remove non-thread-safe psvi methods. Me (23) Remove Mac OS Classic support James (24) Remove OS/2 (or update it) (25) Remove Borland C++ 4, CodeWarrior, VACPP40 and Unsupported from Windows platform Alberto Gareth -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: The Road to 3.0: Feature list/signup
> > 3.b. Mac re-port/test > > James > > 3.c. Windows re-port/test > > > > 3.d. Linux re-port/test (may survive with basic posix...) > > ? I'll certainly sign up to test these, at least in my applications, as well as Solaris. > > (5) Add a libcurl based netaccessor? > > James (as time permits) I can review and test this as well. I'd code it, frankly, if I could get the contributor's agreement signed. -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Road to 3.0: Feature list/signup
At 09.02 12/02/2005 -0800, James Berry wrote: [...] Here's a list of potential tasks. Not all of them have to happen, and they certainly won't happen if we nobody will sign-up for the tasks: CALL FOR SIGN UP: Please respond indicating whether you'll sign up for the work. If there' s something else you want to contribute, please indicate. Help is needed where there is no resource specified, or where there's a question mark. (1) Reorganization of public/private includes (2) Revisiting/sanity checking of install locations (3) Refactoring of x-platform support 3.a. Initial cut James 3.b. Basic posix support James 3.b. Mac re-port/test James 3.c. Windows re-port/test As a Windows developer, I can work on this task (Visual C++ 6, Visual .NET 2003, Borland C++ 5.51) ? 3.d. Linux re-port/test (may survive with basic posix...) ? I have some Linux platforms under VMWare (Red Hat 9, Red Hat 7.3) and I can add more, if needed; but I guess Gareth and other can do it better than me, so keep me as a backup. 3.e. Additional platforms... ? I can test MinGW and Interix (AKA Microsoft Services For Unix). (4) A true autoconf-based build infrastructure James Scott Cantor John Snelson (5) Add a libcurl based netaccessor? James (as time permits) (6) DOM 3.0 support? Well, I started this, so I have to sign up for this ;-) (7) XPath??? (8) XInclude??? (9) Add a ACE-based netaccessor Alby (as time permits) (20) Remove deprecated DOM altogether. (21) Remove and/or update deprecated enums (22) Remove non-thread-safe psvi methods. (23) Remove Mac OS Classic support James (24) Remove OS/2 (or update it) (25) Remove Borland C++ 4, CodeWarrior, VACPP40 and Unsupported from Windows platform Alberto - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
