Schematrons are not valid against Schematron Grammar about eforms-sdk HOT 3 CLOSED

Thanks for reporting this issue.

We will probably have to add a fixed prefix to all phase identifiers, for example: <phase id="phase_3">

We always execute the Schematron files before committing them to check that they work. And for the addition of the phases, I've tested them with several Schematron implementation. But it seems none of those do a full validation against the RELAX NG schema defined in the ISO standard.

Did you detect this when trying to execute the Schematron files, or when opening them with a "Schematron-aware" editor? Which implementation or editor did you use ?

In order to avoid this kind of errors in the future, we plan to add in the SDK Analyzer a check that will do the complete validation against the schema.

from eforms-sdk.

Did you detect this when trying to execute the Schematron files, or when opening them with a "Schematron-aware" editor?

Yes, we use a commercial "Schematron-aware" XML editor which automatically validates Schematron files. But we also validate in CI/CD pipelines.

In order to avoid this kind of errors in the future, we plan to add in the SDK Analyzer a check that will do the complete validation against the schema.

sounds good :)

from eforms-sdk.

This will be resolved in the upcoming version 1.11.0: the phase identifiers will all have a prefix "eforms-" (for example "eforms-16").

This change is already available in the "develop" and "prepare/1.11.0" branches.

So I'm closing this.

from eforms-sdk.