Re: [docbook-apps] Custom ISO Schematron validation for modular Docbook XML with extensive profiling

[Radu Coravu <radu_coravu@sync.ro>]

Dear Bergfrid,

Schematron is in the end translated to XSLT.
And the XSLT can be applied directly over the XML content and it will 
generate messages for each assert.
As you will do it outside of Oxygen you will not have fancy backmapping, 
you might not have a clear indication where the particular error was 
originally located.
There is also a Docbook XSLT stylesheet:

> OXYGEN_INSTALL_DIR/frameworks/docbook/xsl/profiling/profile.xsl

which can be applied over the XML along with parameters which specify 
profiling in order to filter the XML and remove from it the excluded 
content.

So if you first apply the profile.xsl and then the XSLT generated from 
Schematron over the original XML, you should also get reports about 
missing IDs.
This cascade of stylesheets should probably be applied on the XML for 
each combination of profiling attribute values that you are using.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 10/26/2016 3:17 PM, Bergfrid Skaara wrote:
> What are our options for adding custom ISO Schematron validation to our
> DocBook publishing pipeline ?
>
> The code base is large and extremely modular. We also use extensive
> profiling to leverage single source reuse as much as possible. The
> output is currently PDF only, but we might add HTML to the mix next
> year. Our technical editors use oXygen, and we validate and transform
> single documents there. In addition, we have a continuous integration
> pipeline that builds all PDFs when something is committed to Git.
>
> On-the-fly Schematron validation seems doable in oXygen. However, I find
> it tricky to combine profiling with validating after a commit to check
> that changes did not break other documents and that business rules are
> adhered to.
>
> Bergfrid Skaara Dias