This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Future XSLT expansion.


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@netfolder.com
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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]