Page 1 of 1

Configure Validation Scenarios does not detect phases in Schematron with includes

Posted: Thu Jul 23, 2020 7:17 am
by whyme
I have a Schematron file that is for the most part empty, except for the <sch:include> elements that point to included Schematron files that have the intended <sch:phase> and <sch:active> elements that define the phases. When I go to Configure Validation Scenario(s) > Edit Scenario, and then specify the master Schematron file, the Schematron phase drop-down menu is disabled, I think because oXygen hasn't fetched the included files. Maybe this is more of an enhancement request than a bug report?

Re: Configure Validation Scenarios does not detect phases in Schematron with includes

Posted: Thu Jul 23, 2020 11:55 am
by tavy
Hello,

Thanks for your feedback.
Yes, the phases from the included files are not collected when you associate a Schemaron in the validation scenario. We collect the phases from the included files only when the validation scenario is applied, and we display them in a dialog. This is because we do not expand the includes when the Schematron is selected in the validation scenario.
I added an issue on our issue tracker to analyze this situation. We need to consider also the performance because this detection must be fast and you can have complex Schematron files with multiple includes.
We will update this thread when the issue will be solved.

Best Regards,
Octavian

Re: Configure Validation Scenarios does not detect phases in Schematron with includes

Posted: Thu Jul 23, 2020 12:38 pm
by whyme
Thanks Octavian. I don't know if the following would be persuasive in the decision whether to implement this feature, but Schematron includes, unlike XSLT includes, have a small iteration limit. To fetch a Schematron phase that has been included, you need (I think) go no deeper than one round of inclusion, because it has to be a child of the root element.

Re: Configure Validation Scenarios does not detect phases in Schematron with includes

Posted: Fri Nov 20, 2020 4:19 pm
by teo
Hello,

Just wanted to update this thread and let you know that the recently released Oxygen 23 should have a fix for the issue you reported here.

Kind regards,
Teo