Just thought I'd throw out something we ended up doing here.
A while ago some of our clients were putting more and more
info into comments in some locations of the instance files.
After some internal discussions, we ended up making a schema
change, allowing an element called XmlComment in various
places (it can have text or other element children).
Sounds a good idea, except it was a poor choice of name - names beginning
XML in any case combination are reserved...
But even better is to revise your development processes so that schema
change is less difficult. If people start doing sneaky things in their
document instances because it's too hard to change the schema, then you need
to make it easier to change the schema.
(I've seen worse sneaky things designed to circumvent schema designers: like
using a namespace declaration xmlns:dummy="some.boolean.flag" whose presence
or absence conveys a boolean value.)
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--