Re: Detecting presence of attributes
Hi Peter, >> It has the advantage that you can deal with bad values (e.g. if >> 'blort' wasn't actually allowed) within the stylesheet - if that's >> an advantage. > > Fortunately the whole point of making them entities is so that only > the ones declared in the DTD can be used. This is to prevent J. > Random Student running amok with unnecessary stuff. I was thinking in cases where the DTD wasn't available for some reason - you wouldn't have the information about the @options attribute being an ENTITIES attribute *or* the entities that they could use in it! Basically, the stylesheet could be used for validation even if the source XML couldn't be validated according to the DTD. But probably you've got procedural things in place to make sure that's never an issue. Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ 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