This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: The top 10 limitations of XSLT 1.0 (was RE: RE: Designs for XSLT functions)
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: The top 10 limitations of XSLT 1.0 (was RE: [xsl] RE: Designs for XSLT functions)
- From: Uche Ogbuji <uche dot ogbuji at fourthought dot com>
- Date: Wed, 28 Feb 2001 10:50:30 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
> In defining a W3C spec for evaluate(), I would expect
> that to be a matter for debate. One option would be an SQL-like solution:
>
> evaluate("item[@code = '$1' and @desc = '$2']", $code, $desc)
I do like this approach.
> I do think evaluate() is a very necessary extension to the spec,
Hopefully it can be tested out with an exsl:evaluate() first.
--
Uche Ogbuji Principal Consultant
uche.ogbuji@fourthought.com +1 303 583 9900 x 101
Fourthought, Inc. http://Fourthought.com
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list