This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Conditional document merge
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 27 May 2002 18:19:54 +0100
- Subject: Re: [xsl] Conditional document merge
- References: <601F6322AD71D5118D6C0003472515290660CE8A@sjmemexc1.stjude.org>
- Reply-to: xsl-list at lists dot mulberrytech dot com
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