I would search the archives for information about this, but the archives
appear to be down (I think they've been down for a while).
I'm about to get into a situation where a particular group is producing
XML along with a schema, but some of the elements are defined to have
"any" content in the schema. The people producing the XML decided that
that meant they needed to "hide" the XML structure of that content,
particularly by "escaping" the content ("<" to "<", for instance).
I've already prototyped code to "fix" this escaped content before
transformation, but I also remembered an article written last year on
XML.com about "Dealing with change" that I believe addresses this. I've
recovered the article, but I haven't reviewed it yet.
In short, if I'm using recently released versions of Xerces and Xalan,
and my schema specifies "any" content for specific elements, should I
expect any problem (validation, etc.) if the XML content for those
elements is NOT escaped? If this should work, then I'll build a
prototype to demonstrate it, so I can convince them to not generate
their content this way.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
