Hi,
thank you for the helpful answer. It works flawlessly. Still I think that a master switch in the Schematron constructor to let it fail on report would be useful. I updated the code, docstring and tests and sent a pull request to make it happen.
I vaguely remember that it really was a conscious decision to not count report results as errors. That said it might (?) be practical to allow changing behaviour without subclassing but I'd probably prefer to use the standard error-counting XPath as a default argument, rather than a switch. Which would then also solve potential other requirements as to what to deem an error. So essentially this boils down to the question if there is a nicer way or at least a choice other than customization-by-subclassing. I've seen Stefan already merged your pull request; but does the switch really play well with the current customization-by-subclassing? svrl_validation_errors_complete should imho then be added as a class attribute, otherwise a subclass can not provide customized "complete" (in lack of a better word) error validation. But it's really nice to see that anyone else is finally using isoschematron... :-) Holger Landesbank Baden-Wuerttemberg Anstalt des oeffentlichen Rechts Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704 Amtsgericht Stuttgart