[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: Future XSLT expansion.
Subject: RE: Future XSLT expansion. From: "Didier PH Martin" <martind@xxxxxxxxxxxxx> Date: Tue, 21 Mar 2000 05:50:24 -0500 |
Hi Paul, Paul said: We should be capable of transforming text which is XML into node-set ( like document() function does ) and we should be capable of transforming result tree fragment into node-set, like xt:node-set() does and we can do that adding node-set() typecast. Didier replies: Now this is clearer Paul. So, basically, the proposal is to include the node-set() function in the next recommendation. before saying that I agree (even if this sounds a good idea) I will do some experiments in my lab to see how the plethora of XSLT engines treat the case when structured content is set as value for a variable. Then, see by experience what is the behavior which is the most useful and practical. I expect that some process structure content as node-set and others as result tree. Maybe not, but nothing is better than real testing ( a good balance of Bacon and Descarte mindsets never hurt). Cheers Didier PH Martin ---------------------------------------------- Email: martind@xxxxxxxxxxxxx Conferences: Web Chicago(http://www.mfweb.com) XML Europe (http://www.gca.org) Book: XML Professional (http://www.wrox.com) column: Style Matters (http://www.xml.com) Products: http://www.netfolder.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Future XSLT expansion., Paul Tchistopolskii | Thread | Re: Future XSLT expansion., David Carlisle |
Re: Future XSLT expansion., David Carlisle | Date | errors when validating stylesheets , Carsten Ullrich |
Month |