yes, my custom xml may be read & generated by different apps,such as an aspx page which may be often modified and requires a neat code, and has a relatively complex structure and restrictions must be carefully handled. now it seems that one thing that i can do is to extract and translate those custom "xml markups" into a real XML DOM and validate it with my schema, and then go back to process the embedded inner contents within these markups. It's a boring thing...
a customXml Markup validation mechanism may suggest a transparent view of the customXML content which is embedded within the wordprocessingML,i think it may be important to facilitate inter-operation among multiple schemas, as may be a funny architecture, if such a mechanism(with extended model and functionality) is provided directly from the SDK.
I would be pleased to see a model amendment be appended to the SDK with customXML markup validation and customDOM support, when the developers could operate XML within XML while these XMLs are actually isolated by <customXML> simply(rather than being put into an isolated part) and meanwhile sharing contents with wordprocessingML as well. Let's call it what? 3D XML or noodle XML? lol, anyway it's worthy of discussing...
My point is: Since it's Custom,it shall be FREE,while since it's XML,it shall be well-managed & validated. Don't leave wild grass growing in the corner which is built under the name of the decent XML. Otherwise, why customXML?
Welcome to visit my Blog:xiaoyuvax.spaces.live.com
Follow me on Twitter: twitter.com/xiaoyuvax