Subject: Re: [xsl] The evaluate function From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 10 Jan 2002 14:52:04 GMT |
>> Actually, I'd be surprised if the list archive contains a single real-world >> example which can't be solved without evaluate() and isn't also an example >> of bad design. The ones I remember included reading XPath expressions from >> XML files, which could have been avoided by "XML-ifying" the expression. If your input document is (say) an XML schema, or an XSL stylesheet it will contain XPaths in attribute content. How can you "XML-ify" those without invalidating the documents? Maybe you would argue that Xpath should have been like XqueryX a fully expanded XML tree representation of the path, perhaps so, but Xpath is what it is, so it probably ought to be able to handle itself. > BTW, if I'm not mistaken, it's the lack of a standard "evaluate" function > that forces systems like Schematron into being two-pass (generate and > execute). Ah that would require an XSLT-evaluate rather than an Xpath one, I don't think anyone has suggested that (yet) It would be nice though: you generate two rtfs by applying templates, then you say <xsl:apply-transformation stylesheet="$x" source="$y"/> hmm..... David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] The evaluate function, Mark Feblowitz | Thread | Re: [xsl] The evaluate function, Joerg Pietschmann |
[xsl] Re: Re: mapping (Was: Re: Re:, Dimitre Novatchev | Date | [xsl] xpath, Maneshi Tuli |
Month |