Shane Curcuru wrote: > Let's work on this discussion for a bit and get more participants. If > needed we might cross-post once to general@xml to get more folks to > come look over here (I was impressed you all actually subscribed! I > thought it was still edwin and sam and me!) I'm glad there's interest > here, it will remind me to come back to visit more from the many > emergencies at work...
I concur mostly with you, Shane: xml-commons shouldn't become a repository of useful pieces of code (but another subproject like "xml-tools" might, that's not a bad idea) but more of "glue code" between the different xml.apache.org subprojects. xml-commons should prevent subprojects to reinvent the wheel and provide a common repository of shared code (hence the name). This should, as you mentioned, help the individual subprojects to interact more closely. IMHO all subprojects should search for pieces of code that can be "outsourced" to xml-commons. A repository of XML and XSL tools, maybe called "xml-tools", should be kept separate from xml-commons. I see xml-commons as a inter-xml.apache.org project, and a tool collection definitely would target more on users than on xml.apache.org subprojects. And if something from xml-tools becomes used by some xml.apache.org subprojects it always can be moved over to xml-commons. Since I kind of propose another xml.apache.org subproject I crosspost this to [EMAIL PROTECTED] *ducks and runs* > <eof aka="mailto:[EMAIL PROTECTED]"; > BartSays="Nobody reads these anymore."/> So, why are you Reply-To-ing there? ;=D Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
