|
Subject: Re: The top 10 limitations of XSLT 1.0 (was RE: [xsl] RE: Designs for XSLT functions) From: Uche Ogbuji <uche.ogbuji@xxxxxxxxxxxxxxx> Date: Wed, 28 Feb 2001 10:50:30 -0700 |
> 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@xxxxxxxxxxxxxxx +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
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: The top 10 limitations of XSLT , Jeni Tennison | Thread | [xsl] select lang attribute problem, cutlass |
| Re: The top 10 limitations of XSLT , Uche Ogbuji | Date | Re: Designs for XSLT functions (Was, Uche Ogbuji |
| Month |