Hi Joe,
>> So even if this isn't the situation we'd hoped for, it's the one
>> we have and its existed for long enough that I'm not persuaded it's
likely
>> to change. So I'd like to recognize it and codify it in our charter,
> If it isn't what we want, what is the advantage of institutionalizing?
What we might have wanted in the past is a set of Xerces parsers that were
architected sufficiently similarly that a committer to one could, more or
less, happily jump to the other. For reasons that are partly historical
and partly a function of the technical characteristics of the different
languages, what we have is code bases which are vastly different, and
which, I would aver, no one is capable of completely understanding.
For the benefit of new committers, and the community at large, we need to
reflect this reality. We just don't want new committers to believe the
fact that they can write do all Xerces repositories means they may do so;
we need to make clear to users that simply because something's done one way
in Xerces-x doesn't mean it can or should be done that way in Xerces-y.
> More generally: Ignoring the administrivia, what does breaking Xerces
into
> sub-projects actually buy us, versus our current practices?
Xerces is a set of subprojects, just as Xalan is. The way we're treated
within the XML project illustrates this.
Cheers!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
Joseph Kesselman
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
om> cc:
Subject: Re: [VOTE]: motion to
transform Xerces into a top-level project as a
04/01/2004 09:19 member of the "federation" of XML
projects
AM
Please respond to
xerces-j-dev
> So even if this isn't the situation we'd hoped for, it's the one
> we have and its existed for long enough that I'm not persuaded it's
likely
> to change. So I'd like to recognize it and codify it in our charter,
If it isn't what we want, what is the advantage of institutionalizing?
More generally: Ignoring the administrivia, what does breaking Xerces into
sub-projects actually buy us, versus our current practices?
(I don't have an opinion either way, yet. I'm waiting to hear a stronger
argument for restructuring.)
---------------------------------------------------------------------
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]
