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

Hello Bergfrid, So: I guess that we need to switch to two-pass profiling to use profiling/profile.xsl ? The enhanced validation would be totally separate from publishing. The publishing would not be changed at all. But validation would first need to apply the "profile.xsl" in order to

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

Thanks! We currently use single-pass profiling with a custom version of fo/profile-docbook.xsl (Includes our custom docbook.xsl rather than the stock stylesheet. No customizations to the actual profiling). Our only profiling attribute is profile.audience, and it is usually 1:1 mapped to a

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

Hi Dave, Yes, sure, you can either create a validation scenario and apply it from the Project view on multiple XML documents, or you can associate the Schematron with the XML using the xml-model processing instruction. Regards, Radu On 10/26/16 5:44 PM, Dave Pawson wrote: On 26 October

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

On 26 October 2016 at 14:07, Radu Coravu wrote: > 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

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

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

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

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