Document Type Association > Schema Tab request 1/2

Are you missing a feature? Request it's implementation here.
whyme
Posts: 71
Joined: Fri Mar 08, 2013 8:58 am

Document Type Association > Schema Tab request 1/2

Post by whyme » Fri Jan 26, 2018 10:13 pm

In the Document Type Association > Schema Tab it would be nice if one could pick a Schema type that is pure Schematron (i.e., not mixed with other schema languages).

Radu
Posts: 7119
Joined: Fri Jul 09, 2004 5:18 pm

Re: Document Type Association > Schema Tab request 1/2

Post by Radu » Mon Jan 29, 2018 11:52 am

Hi,

That "Schema" setting is used only when the XML has no additional reference to a schema or there is no validation scenario configured for that particular type of XML document.
If you want Schematron-based validation added to the base validation (DTDs or XML Schemas directly referenced in the XML document) in the same framework configuration dialog there is a "Validation" tab where you can configure a validation scenario and check it to be the default validation scenario. You need would probably two validation stages, one for validating with the DTD/Schema specified in the XML and one for Schematron validation. You can edit the DITA framework configuration and look in its Validation tab to see how various validation stages are configured there.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

whyme
Posts: 71
Joined: Fri Mar 08, 2013 8:58 am

Re: Document Type Association > Schema Tab request 1/2

Post by whyme » Mon Jan 29, 2018 10:18 pm

Thanks -- perfect! It might help future users if documentation made this suggestion more explicit.

Now that I'm using the validation tab, it's unclear to me what function the schema tab has. That is, what does the latter do that the former does not do?

Radu
Posts: 7119
Joined: Fri Jul 09, 2004 5:18 pm

Re: Document Type Association > Schema Tab request 1/2

Post by Radu » Tue Jan 30, 2018 9:30 am

Hi,

So:
Now that I'm using the validation tab, it's unclear to me what function the schema tab has. That is, what does the latter do that the former does not do?
Good question. The "Schema" tab was a framework configuration option long before we had validation scenarios. So once we added validation scenarios we needed to still keep the "Schema" tab for backward compatibility.
And also the "Schema" tab is easier to use, maybe in most cases people just have only one schema so instead of having them understand the concept of validation scenario, validation stages and default validation scenarios they just need to add there the reference to the schema and they are ready to go.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

Post Reply