Documentation on Schematron processing

[whyme]

Hi! I am trying to find documentation about the technical process Oxygen follows to run Schematron validation.

I had been under the impression that Saxon was at the heart of Schematron processing in Oxygen, but when I checked Saxon's documentation, the word "Schematron" appears only once, to cross-reference the standard. There are no Saxon command-line flags that cater to Schematron.

My version of Oxygen is equally silent. In Preferences, options that show up when I search for "schematron" do not tell me what processor is used. There is a section with the title "ISO Schematron," and Schematron warnings and errors in Oxygen are marked "[ISO Schematron]", but as far as I can tell that phrase refers to a document/standard, not a piece of software (see below). Further, Oxygen's Preferences section Editor > Document Validation seems to have nothing explicitly related to Schematron.

When I search for "schematron processor" in the Oxygen web help I don't see any pages that address this question. But that's after going through only 5 of the 24 pages of hits. (Shouldn't there be a page dedicated to the topic of Schematron validation processor(s), the way there are for XSL-T, XSL-FO, Ant?)

The official website schematron.com uses "ISO Schematron" to refer purely to the technical document that defines the standard, not to a processor or implementation of that standard. And in fact Schematron.com, under the "Software" section, refers to only three implementations/processors.

Does Oxygen have its own home-built Schematron processor working under the hood? Is it using Schematron Skeleton in conjunction with another processor? Using SchXslt in conjunction with another processor? Something else? What is happening inside the black box?

[Radu]

Hi,
From what I know the Schematron validation in Oxygen converts the Schematron rules to an XSLT stylesheet by applying another XSLT stylehseet on them and then uses that XSLT stylesheet over the XML document to produce the errors. We are using the Saxon 12 XSLT processor for the conversions. Other than that, we are a commercial application so we do not document exactly the internal process but are focused on presenting the benefits.
Regards,
Radu