Jeff, > 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:
I am not sure to what original description you are referring..? > "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 It does NOT say that list will _always_ take precedence. It will only take precedence in case targetNamespace is the same on both user specified schema and the one on xsi: attribute. > > Do you prefer values in the document to be completely ignored when the > > property is set? > > Yes. Hmm.. it seems like Ian is happy with that and you are not. And given some of your comments above.. I am not quite sure we understand each other. I will try to describe again how the property works: [1] validation will be performed against user specified schemas (on the property). [2] if validation fails to resolve one of the prefixes or namespace: -- try to see if xsi: attribute has schemas that allow to resolve a prefix. -- if resolution fails after that - report an error If this is not what you would prefer to have in your application, please let us know. The problem is.. I can see several use cases, and I wish the users could tell us what they prefer: -- specified schema overrides document's schema (completely ignores document xsi: attribute) -- specified schema has precedence over document's schema however will consult document's schema if required (current Xerces property) -- specified schema will be used only if document does not specify one (document overrides specified). Thank you, Elena --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
