xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eduardo Pelegri--Llopart <Eduardo.Pelegrillop...@eng.sun.com>
Subject Re: parser-next-gen goals, plan, and requirements
Date Wed, 12 Jul 2000 17:31:22 GMT
[I'm reading this as digest - hope I can post..]

I agree with Brett.

+1 on having XPath.  We have many cases where people want to do XPath on
tag libraries in JSP without wanting to do XSLT for a number of reasons.

	- eduard/o

> Subject: Re: parser-next-gen goals, plan, and requirements
> Date: Wed, 12 Jul 2000 09:07:32 -0500
> From: Brett McLaughlin <brett.mclaughlin@lutris.com>
> To: general@xml.apache.org
> 
> Stefano Mazzocchi wrote:
> >
> > Donald Ball wrote:
> > >
> > > I'd like to see XPath and XInclude support built in to Xerces as
> > > modules.
> >
> > +1 for XInclude and XBase (they do together), as well as a way to
> > extract XLink information from the file, if found.
> >
> > -1 for XPath, it should belong to Xalan2
> 
> I'm actually in disagreement here - I know in JDOM, people want to be
> able to look up nodes/elements/attributes using XPath. Additionally,
> more and more APIs are using XPath outside of XSL/T. To include it as
> part of Xalan forces users to get an entire jar to do that.
> Additionally, based on Scott's reaction ;-), he wouldn't add in support
> for XPath on JDOM. That's another reason. Still, I think users that know
> XPath would love to do:
> 
> Element specific = root.getChild("foo/@bar='1'");
> 
> Not having to carry around XSL/T weight to do this is a major advantage,
> and prepares us for the APIs that use XPath outside of just
> transformations.
> 
> -Brett

Mime
View raw message