[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Conditional document merge
If things subsequently change the order of any missing elements has to be based on some default; in this case, after the closest element that was known at the time document B was created. I didn't understand this, you said doc a was essentially unordered, I can understand going through doc b and producing the output, you describe but the only way I understand to get all the @required elements from doc a that are not in b is to put them all at the end. If you go the document B you don't know until the end that any required elements are not listed do you? But you have a notion of closest above and in your original you said any missing nodes can be substituted immediately following any previous match. neither of which I understand:-) In your example required output <d> got out out because it was required, but why did it come at the end (unless all such come at the end) 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|