Hi Ted,
There was one thing in your note that I don't think anyone commented
on: the suggestion that "we might be able to put the TCK harnesses and
stuff in commons."
My understanding is that the contents of a TCK can only be exposed to
licensees of the TCK, so we can't put the TCK into commons.
Sorry if someone already commented on that, or if I misunderstood
what you were getting at.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab Tie Line 969-6044; Phone (905) 413-6044
mailto:[EMAIL PROTECTED]
"Theodore W. Leung" <[EMAIL PROTECTED]>
09/16/2002 04:54 PM
Please respond to xerces-j-dev
To: Xerces J Dev <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: JAXP 1.2
Another wrinkle to the JAXP stuff is that we (the ASF) need to be able
to pass the TCK for a JSR in order to say that we implement it. Since
JAXP is specified by a JSR, we're going to need to pass the Sun TCK --
the best time to do this work is probably when we step up to JAXP 1.2
Joe, are you folks in Xalan running the JAXP TCK?
In my mind this is a good reason to try to get the Xerces/Xalan/Commons
JAXP versions closer in sync. That way we might be able to put the TCK
harnesses and stuff in commons and have Xalan and Xerces use it from
there.
Ted
On Mon, 2002-09-16 at 09:00, Joseph Kesselman wrote:
> >What is the relation between released JAXP 1.2 [1] and Apache XML
> Commons.
> >What is relation between specification and implementation, i.e. commons
> vs. xerces and xalan?
>
> Commons is intended to contain standards based elsewhere (DOM, SAX,
JAXP,
> etc), possibly plus some shared Apache utilities.
>
> Yes, Commons and the implementations should be kept up to date as the
> standards evolve -- as time permits, which is true of any Apache
project.
> If you want it to happen faster, work to get yourself accepted as a
> committer and volunteer to help work on that task... but note that these
> projects _DO_ need to stay in synch in order to compile cleanly against
> each other.
>
> The simplest way to ensure that everything is in synch is to take the
> version of Xerces that your version of Xalan was compiled and tested
> against; check the Xalan docs for details.
>
>
> Xalan compiles directly against Commons, and in fact compiles all of
> Commons into its xml-stds.jar file. Xerces has been taking a selected
> subset of Commons as the content of its xmlParserAPIs.jar file. There's
> been some discussion of whether that subsetting is really a net win, but
I
> don't think a consensus has been reached.
>
> ______________________________________
> Joe Kesselman / IBM Research / Xalan, plus some past work on Xerces and
> Commons
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
