On Mon, 25 Jun 2001, Elena Litani wrote: > The problem is.. I can see several use cases, and I wish the users could > tell us what they prefer: > > (A) -- specified schema overrides document's schema (completely > ignores document xsi: attribute) > (B) -- specified schema has precedence over document's schema however > will consult document's schema if required (current Xerces property) > (C) -- specified schema will be used only if document does not specify > one (document overrides specified).
A and B suit a system where the application is expecting data in a specific format and needs to enforce the use of a particular schema. C is more appropriate for a system which can expect many different kinds of XML, which may or may not specify its own schema, but validation is desired if the document is in a well known namespace (e.g. XHTML or WML). A would be ideal for my purposes, although B is equivalent since we can guarantee that the application specified schema will always be available (we use an EntityResolver to load it from a local cache). Given all this, my vote is for B (the current behaviour), possibly with an option for C if there is enough demand. Ian -- Ian Roberts, Software Engineer DecisionSoft Ltd. Telephone: +44-1865-203192 http://www.decisionsoft.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
