xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Elena Litani <elit...@ca.ibm.com>
Subject TCK compliance [was: is there such a thing as a common xml-apis.jar]
Date Thu, 07 Nov 2002 15:54:50 GMT
JAXP 1.2 conformance section states that all implementations of JAXP
need to be conformant to the following specifications: XML 1.0 Rec., SAX
2.0, XSLT 1.0, and DOM Level 2 Core.

So what happens when new versions of the specifications come out, i.e.
XML 1.1 (CR), SAX 2.0.1, XSLT 2.0 and DOM Level 3 Core? 

Is there any process (at Apache or at Sun) that allows endorsing the new
versions of the external standards, so that implementations can stay
compliant to JAXP?

Thank you, 
-- 
Elena Litani / IBM Toronto

-------- Original Message --------
Subject: Re: is there such a thing as a common xml-apis.jar
Date: 06 Nov 2002 11:08:06 -0800
From: Costin Manolache <cmanolache@yahoo.com>
Reply-To: general@xml.apache.org
To: general@xml.apache.org
References: <OFDDDC6A54.09E13C1A-ON85256C69.0065A04C@torolab.ibm.com>

Did anyone checked the license on jaxp ? 

I know some JSRs do not allow distribution of modified ( incomplete ) 
APIs.

I think someone should check that.

It may help to have some link to point that if people want a 
'JAXP' implementation they need to download both xalan and xerces
( or just xalan - as it includes both ). Xerces distribution only
has 1/2 of JAXP.

Costin 

On Wed, 2002-11-06 at 10:37, neilg@ca.ibm.com wrote:
> Hi folks,
> 
> No confusion would have arisen, of course, if somebody at maven hadn't
> decided to rename xmlParserAPIs (or reformat xml-apis).  Does anyone have
> contacts in the maven world who could straighten this out?
> 
> Personally, I believe that were Xerces to start shipping the transform
> interfaces, confusion would simply migrate from lists like this to Xerces
> lists...  In the final analysis there's no way to demonstrate this one way
> or the other except by trying the experiment--and then there's no way back.
> So unless there were some really compelling reason to change, I for one
> wouldn't want to see Xerces change in the near future.
> 
> But there are lots of other xerces committers.  :)  If folks want to lobby,
> xerces-j-dev is the place to go.
> 
> Cheers,
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone:  905-413-3519, T/L 969-3519
> E-mail:  neilg@ca.ibm.com
> 
> 
> 
> 
> |---------+---------------------------->
> |         |           Joe Germuska     |
> |         |           <Joe@Germuska.com|
> |         |           >                |
> |         |                            |
> |         |           11/06/2002 01:09 |
> |         |           PM               |
> |         |           Please respond to|
> |         |           general          |
> |         |                            |
> |---------+---------------------------->
>   >---------------------------------------------------------------------------------------------------------------------------------------------|
>   |                                                                                 
                                                           |
>   |       To:       general@xml.apache.org                                          
                                                           |
>   |       cc:                                                                       
                                                           |
>   |       Subject:  Re: is there such a thing as a common xml-apis.jar              
                                                           |
>   |                                                                                 
                                                           |
>   |                                                                                 
                                                           |
>   >---------------------------------------------------------------------------------------------------------------------------------------------|
> 
> 
> 
> At 12:29 PM -0500 2002/11/06, neilg@ca.ibm.com wrote:
> >Xerces has never shipped the transform half of JAXP.  That's because we've
> >always felt it's misleading to users--especially newbies--to ship
> >interfaces we neither need nor implement.  If you just want a parser, you
> >don't need to know about the transform half of JAXP and you can happily
> >stick with xerces; if you need an XSLT processor, you can grab Xalan which
> >will come with an appropriate xerces implementation and all the APIs you
> >need.  (Does Xalan ship our xmlParserAPIs file?  I doubt they do; I hope
> >they don't.  :) )
> 
> Having been bitten by the same thing as James this week (using a
> Maven xml-apis.jar that didn't have the transformation part of JAXP),
> I would tend to agree with Shane -- just ship a single XML jar with
> all of JAXP, all of SAX, and all of DOM.
> 
> The confusion could be dealt with with documentation, and the classes
> can't add up to more than a few kilobytes.  I think the current
> situation is more confusing.
> 
> But then, I'm not a Xerces committer either.
> 
> Just my 2 shekels,
>              Joe
> 
> --

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Mime
View raw message