Oxygen 9.1 - Failed to read schema document

[shudson310]

I'm trying to validate an external schema:
http://www.imsglobal.org/xsd/imscp_v1p2.xsd

Yet, I continue to get the following errors:
SystemID: http://www.imsglobal.org/xsd/imscp_v1p2.xsd
Location: 9:121
Description: schema_reference.4: Failed to read schema document 'file:/C:/Program%20Files/Oxygen%20XML%20Editor%209.0/frameworks/xml/xml2001.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
URL: http://www.w3.org/TR/xmlschema-1/#schema_reference

SystemID: http://www.imsglobal.org/xsd/imscp_v1p2.xsd
Location: 116:35
Description: src-resolve: Cannot resolve the name 'xml:base' to a(n) 'attribute declaration' component.
URL: http://www.w3.org/TR/xmlschema-1/#src-resolve

SystemID: http://www.imsglobal.org/xsd/imscp_v1p2.xsd
Location: 116:18
Description: s4s-elt-invalid-content.1: The content of 'Manifest.Type' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.

SystemID: http://www.imsglobal.org/xsd/imscp_v1p2.xsd
Location: 173:18
Description: s4s-elt-invalid-content.1: The content of 'Resources.Type' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.

SystemID: http://www.imsglobal.org/xsd/imscp_v1p2.xsd
Location: 226:18
Description: s4s-elt-invalid-content.1: The content of 'Resource.Type' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.


The main problem, is that it's not finding the xml2001.xsd, even though it is in the catalog! I even tried adding an entry to the xml/catalog.xml:
<system systemId="http://www.w3.org/XML/1998/namespace" uri="xml.xsd"/>

I think there is either a bug, or some setting I'm missing!

Thanks,

--Scott

[Radu]

Hi Scott,

Just open "C:/Program Files/Oxygen XML Editor 9.0/frameworks/xml/xml2001.xsd" in Oxygen and remove the DOCTYPE declaration from it.
The validation failed because the referred DOCTYPE could not be resolved.
We will also remove the DOCTYPE declaration and the next official build will no longer have this problem.

Regards,
Radu

[shudson310]

Thanks, Radu! That worked. I'm up and running again.

Best regards,

--Scott