Hi Berin and all,

Speaking for myself, I'm content with your suggestions as they impact
Xerces.  But then I'm also content with the status quo:  it's been a long
time since there was much controversy in any part of Xerces-country, so the
old adage that if things aren't broke, don't fix 'em would seem to apply.

So, I'm happy to go in whatever direction the Board is most happy
with--especially if it doesn't involve much change.

But there was one suggestion in your proposal that I did think merited
comment.  You wrote:  "XML Commons could either become part of the Apache
Commons project, or could remain within the XML project."  As well as being
a handy repository for utilities that one often needs in an XML context,
one of the real needs that XML Commons originally sought to solve was to
ensure that products that implement API's covered by XML Commons would
co-ordinate the versions of those API's in corresponding releases.
Historically, there were often subtle differences between the API's shipped
by Xerces and Xalan that meant users would get different behaviour based on
how their classpaths happened to be ordered with respect to the jars
provided by Xerces and Xalan.  This was deemed unacceptable by both
communities, and it was one of the reasons we were so happy to see XML
Commons come along.

I'm worried that a move to Apache commons would so dilute the focus on XML
technologies that this co-ordination role would be at risk.  From private
correspondence, I know there are some folks in the Xalan community with
similar concerns.  So if it were possible to keep XML Commons within what's
left of the XML project--or, perhaps, simply hand it over to Xerces or
Xalan, themselves very basic XML technologies--I'd be much happier.

Cheers!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]




                                                                                       
                                                
                      Berin Lautenbach                                                 
                                                
                      <[EMAIL PROTECTED]        To:       [EMAIL PROTECTED], [EMAIL 
PROTECTED]                                    
                      mes.org>                 cc:                                     
                                                
                                               Subject:  Draft discussion of 
Federation proposal                                       
                      01/04/2004 06:23                                                 
                                                
                      AM                                                               
                                                
                      Please respond to                                                
                                                
                      pmc                                                              
                                                
                                                                                       
                                                
                                                                                       
                                                



Peoples,

Have put together a very rough draft of how a federation of projects
around XML might be created.

Caveat - it really is very draft, and purely there as a discussion
starter.  Feel free to either post comments/thoughts back to the list or
to edit the document directly.  (Note that this document does not yet
discuss next steps, such as agreements from each sub-project etc.)

All comments very welcome.  The board requested a proposal by the Jan
board meeting (normally around the 20th of the month), so it would be
good to move the discussion forward - whether around this or another
proposal.

http://nagoya.apache.org/wiki/apachewiki.cgi?XMLProjectPages/FederationProposal


Cheers,
             Berin



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to