Regarding <empty/> it is certainly possible to 'ignore' elements and their 
children, thus deleting them out of the output document, by simply not creating 
a match template that looks for them. I don't know if this is in the spirit of 
<empty/> or not but it seems to have the desired (and sometimes undesired) 
effect.

	...edN

-----Original Message-----
From:	keshlam@xxxxxxxxxx [SMTP:keshlam@xxxxxxxxxx]
Sent:	Wednesday, November 04, 1998 9:18 AM
To:	xsl-list@xxxxxxxxxxxxxxxx
Subject:	XSL questions

It might be worth drawing up a table showing examples of old syntax
compared with new syntax, to help folks switch over.

Unless I'm out of date, Ecmascript/Javascript support has been dropped from
the current XSL working draft. I think folks have said that some kind of
scripting support may come back in future versions. That knocks out the
<eval/> and <define-script/> elements.

I'm not sure what the current equivalent of <empty/> is... a template with
no contents, perhaps?
______________________________________
Joe Kesselman  / IBM Research
Unless stated otherwise, all opinions are solely those of the author.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list