Elena, > Can you clarify what do you mean by "override"? The document does not > override value of the property.. unless there is a bug or there is a > misunderstanding of how the property works. > > As it was mentioned in documentation, document values are not ignored. If > we can't resolve namespaces using values on the property - we will try to > resolve those using the schemas on the document.
It seemed in the original description that if values were supplied from both the external property and the xsi: attribute that the attribute within the instance document would take precedence: Elena wrote: "Note! The parser does not ignore schemaLocation/ noNamespaceSchemaLocation attributes. If schema with the same targetNamespace appears in both the list user specified and on schemaLocation, the one from user's list will be pick up for validation" That seems to indicate that the user's (instance) list will always take precedence. I think this is the behavior that Ian wanted to override. I haven't been able to test which one takes precedence yet--if any. > Do you prefer values in the document to be completely ignored when the > property is set? Yes. Even though there are some cases where the document value is preferred-- it is very application specific. It seems that if the property took precedence (if the property were included the document values are ignored) then it would be possible in each application to program in a simple check to see if the document has included values. If so then the application can decide whether or not to set the properties or use the included values. Does this make sense? Thanks a ton! Jeff Rafter Defined Systems http://www.defined.net XML Development and Developer Web Hosting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
