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 have fancy backmapping, you
> might not have a clear indication where the particular error was originally
> located.
Radu, can we use oXygen to run the Schematron checks please?
(and add our own?)
regards
> 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
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
