Re: [jats-list] Can an Editor Write Schematron?

["Alexander Powell ap.cybercraft@xxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

It was a feeling that Schematron imposes rather a heavy burden on those who
wish to check their content, and probably an excessive one for your typical
editor (who would lack the time or motivation to dig deep into technical
arcana and CS major-like ways of thinking), that led me to try my hand at
creating a validation tool 'for everyone else'.

CheckMate was the result (see
http://www.epistemic-systems.co.uk/cm/cm-index.htm). It was used
successfully by a UK university press client of mine for a couple of years,
who lacked the technical resource (people) to implement Schematron for
them, or write rules, or possibly even execute scripts and comprehend the
results, and lacked the budget to acquire those capabilities.

I ran out of time to develop the tool to the point I'd hoped - its
scripting language could do with a few more predicates or what you will,
there are some residual issues in various areas, and probably a few
outright bugs still to be put right. It will never compete with Schematron
for sheer depth of capability, but hopefully it's possible to see what it's
trying to achieve. I do think there's a place for something like this that
majors on ease of use.

Best,
Alex

Dr Alexander Powell
https://www.linkedin.com/in/alexander-powell-34735a9/


On Thu, 11 Feb 2021 at 23:02, Gareth Oakes goakes@xxxxxxx <
jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Codifying the logic as English statements in a spreadsheet seems like a
> good approach. I wonder if you can "sync" this with the Schematron by
> generating English language statements from the Schematron asserts/reports?
> That way once the programmer interprets the latest spreadsheet they can
> regenerate the spreadsheet from the Schematron file, ready for the next
> time an editor wants to update the spreadsheet. This gives a handy point of
> reference for the current logic as well as a clue to the type of language
> (and thought process) the editor should be using.
>
> // Gareth Oakes
> // VP Content Technologies, GPSL
> // www.gpsl.co