<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Gary,<br>
<br>
When relying on the namespace instead of an explicit schema
association (xsi:schemaLocation), Oxygen only associates one schema
for the root element namespace of the XML instance. Any other
namespaces from the XML instance are ignored.<br>
<br>
<br>
Why do you consider using xsi:schemaLocation is a problem?<br>
As long as you have an XML catalog that resolves the schema
location, it doesn't really matter what location is being used.<br>
<br>
Instead of using a canonical location, you could use the actual
namespace as the schema location in xsi:schemaLocation and it would
work in Oxygen.<br>
e.g.<br>
<oval_definitions
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a><br>
xsi:schemaLocation=<a class="moz-txt-link-rfc2396E" href="http://oval.mitre.org/XMLSchema/oval-definitions-5http://oval.mitre.org/XMLSchema/oval-definitions-5http://oval.mitre.org/XMLSchema/oval-definitions-5#independenthttp://oval.mitre.org/XMLSchema/oval-definitions-5#independent">"http://oval.mitre.org/XMLSchema/oval-definitions-5
http://oval.mitre.org/XMLSchema/oval-definitions-5
http://oval.mitre.org/XMLSchema/oval-definitions-5#independent
http://oval.mitre.org/XMLSchema/oval-definitions-5#independent"</a> ...<br>
<br>
The alternative is to modify the main XML schema (or create another
main XML schema) to import all namespaces that are used in the XML
instance.<br>
<br>
Regards,<br>
Adrian<br>
<pre class="moz-signature" cols="72">Adrian Buza
oXygen XML Editor and Author Support
Tel: +1-650-352-1250 ext.2020
Fax: +40-251-461482
</pre>
<br>
<div class="moz-cite-prefix">On 21.12.2015 14:56, Gary Gapinski
wrote:<br>
</div>
<blockquote cite="mid:5677F712.7000004@garygapinski.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
I am attempting (perhaps wrongly) to have <a
moz-do-not-send="true"
href="https://github.com/OVALProject/Language">OVAL</a> document
validation to occur based on namespace (<u>without</u> using <tt>xsi:schemaLocation</tt>).<br>
<br>
I suspect my problem is related to the rather complex OVAL
schemata relationships, but I have not determined how best (if at
all) to accomplish this.<br>
<br>
I have a <a moz-do-not-send="true"
href="https://s3.amazonaws.com/xml.garygapinski.com/OVAL/example-oval-unknown.xml">sample
document</a> and a related <a moz-do-not-send="true"
href="https://s3.amazonaws.com/xml.garygapinski.com/OVAL/catalog.zip">XML
catalog</a>. The XML catalog has been configured in the project
preferences.<br>
<br>
When I attempt to validate the document, it appears that the
schema in namespace <tt><a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent">http://oval.mitre.org/XMLSchema/oval-definitions-5#independent</a></tt>
has not been associated. The primary (root) schema is associated
and is obtained from the catalog.<br>
<br>
If this sort of implicit association is not possible, any
suggestions on how to knit together the many discrete
(sub-)schemata of OVAL would be much appreciated. I would prefer
to avoid the use of <tt>xsi:schemaLocation</tt> if at all
possible (since a "canonical" location for such is not assured).<br>
<br>
Regards,<br>
<br>
Gary<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
oXygen-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a>
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>