DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13719>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13719 Schema error with external-noNamespaceSchemaLocation ------- Additional Comments From [EMAIL PROTECTED] 2003-07-04 17:16 ------- The answer is, it depends what you do with the schema and instance document. For namespace aware parsers like Xerces, elements and attributes are identified by their expanded name, their local name (file_metadata in your example), and their namespace name (which should be http://www.eg.org/filemetadata in your example). Both these values must be equivalent for an attribute or element to be considered equivalent structures. In your example, the namespace name for file_metadata is null, and thus the parser looks for a definition of file_metadata in a schama which has no target namespace. It cannot guess what you intended on the fly. I think your best option is to remove the target namespace from your schema, so you can validate against documents that don't explicitly use namespaces. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
