RE: [xsl] Selecting First Direct Sibling

["Wasiq Shaikh" <wasiq911@xxxxxxxxxxx>]

I understand what you are saying and yes I would not run into these minute 
yet important problems had I used documentation tags.

However, using documentation tags in a large XSD document creates 
uneccessary processing and overhead for our framework which parses this 
file. Documentation elements are read and processed, while comments are 
ignored completely. It also decreases file size.

According to our development team, performance is greatly increased with 
comments in place of documentation elements. Since my XSL is apart from the 
framework, parsing comments isn't too much of a big deal. However, "fine 
details" such as stripping spaces are what stop it from being 100% accurate 
(which it is thanks to many helpful people on this list).

Cheers,

W.S

----Original Message Follows----

This thread has been drilling down into extremely fine details that are 
required only because the original XML has been misused.

There is using proper markup and there is using markup properly.

That is, the OP is processing valid comment elements and text nodes, but 
putting 'invalid' information into the comments. Schemas have documentation 
elements for this stuff, and these elements allow elements from other 
namespaces, so the markup is unrestricted. I've done it and it is simple, 
unambiguous, and clean.

I understand that the OP may have no choice, maybe the XML can't be changed 
so we need to make XSL do backflips, but these DTD/schema/whitespace 
complications contradict the spirit of XML.

Brad

_________________________________________________________________
Show Your Messenger Buddies How You Really Feel 
http://www.freemessengeremoticons.ca/?icid=EMENCA122