Hi Eric, From what I understand in your case the namespace and schema location have the same value. The namespace is not interpreted as a schema location, it is just an identifier. Usually an xsd:import should have both schemaLocation and namespace. If the schema location is missing, Oxygen has a feature which allows it to try and resolve the namespace identifier through the set-up catalogs. Just go to the Oxygen Preferences->"XML / XML Catalog" page and check the "Process namespaces through URI mappings for XML Schema" checkbox. Then, if your namespace is mapped using URI mappings through the catalogs configured in Oxygen to a schema location, that location will be used. Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 4/22/2010 4:26 PM, Eric Jahn wrote:
In the past versions of the Oxygen Schema editor, an import statement would not work unless a schema association was configured. The W3C guidelines on import statements, though, states that schemaLocation is optional. Presumably, it would be optional if the import uri is the same as the schemaLocation, which is the case in my situation. However, oxygen fails to import without a schemaLocation attribute. Here is my schema: http://www.hmis.info/schema/3_0/HUD_HMIS.xsd Thanks!