<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Gary,<br>
<br>
Oxygen treats the schema determined from the namespace of the root
element (namespace resolved through the XML catalogs as an URI) as a
fallback schema association (implicit), if no explicit schema
associations are present.<br>
An xml-model PI is explicit and thus overrides this fallback schema
association. It's impossible to tell if the xml-model PIs complement
or override the implicit schema (just from the PI declaration), so
it was decided to always override it.<br>
<br>
I see you have already found the workaround, it may seem
superfluous, but right now if you make one explicit association, you
also need to specify the one that was implicit.<br>
I've submitted a request on our issue tracking tool to discuss
if/how we should allow the implicit association to stick.<br>
<br>
<br>
BTW, the option "Process namespaces through URI mappings for XML
Schema" does no affect XML instances, only XML schemas.<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 08.09.2016 21:39, Gary Gapinski
wrote:<br>
</div>
<blockquote
cite="mid:c5f4bac2-730c-f177-896a-5322e0941a47@garygapinski.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p>Hello:</p>
<p>I have found that a document that used namespace-implicit XML
Catalog driven XML Schema validation (via the "Process
namespaces through URI mappings for XML Schema" in XML Catalog
preferences) works as expected until an <a
moz-do-not-send="true" href="https://www.w3.org/TR/xml-model/">xml-model</a>
processing instruction for an additional (Schematron) schema is
added to the document. After the addition, the XML Schema based
on the document's namespace is no longer applied. Removing the
xml-model PI restores the implicit XML Schema validation.</p>
<p>This can be avoided by adding a (seemingly superfluous)
additional xml-model PI for the XML Schema citing the document's
namespace in its href pseudo-attribute.</p>
<p>Is this the expected behavior? I had expected the namespace URI
mapping to implicitly associate the XML schema and the xml-model
PI to explicitly augment this.</p>
<p>Regards,</p>
<p>Gary</p>
<p><br>
</p>
<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>
</body>
</html>