RE: xsi:type and broken contracts
> The code doesn't have to be part of a library, it could just be > code that manipulates documents coming in from external sources. > The fact is that the combination of xsi:schemaLocation and > xsi:type make it very likely that a type aware application will > come across derived types in instance documents unless these > attributes are specifically mandated against. Understood. I had neglected to factor in the effect of schemaLocation attributes. So depending on the service offered, it may be useful to programatically ignore "helpful" schemaLocation hints and rely solely on a local cache. Section 4.3.2 of the XML Schema Part 1 http://www.w3.org/TR/xmlschema-1/#schema-loc leaves the door open for products to allow this. Thanks for your patience. Michael.
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