comparison between the contents of the <Word> elements and the <TextEquivType><Unicode> elements : Schematron

[tboenig]

It can happen that a comparison between the content of the elements <Word> and <TextEquiv><Unicode> detects differences. To check any differences a schematron is necessary.

[bertsky]

You surely mean between some element's TextEquiv:Unicode and its sub-component element's TextEquiv:Unicode, as in:

• between TextRegion and its TextLine sequence
• between TextLine and its Word sequence
• between Word and its Glyph sequence

Should the consistency principle not be added to the spec in PAGE.md?

I sometimes use XSL transformations to concatenate sub-components (joining them by whitespace or newline, depending on position) – maybe this is a good starting point for such schematron. If you think those would in fact be useful, where can I put them?

(But then again, why not add a function to WorkspaceValidator.validate() in core instead?)

[kba]

Should the consistency principle not be added to the spec in PAGE.md?

It should.

Why not add a function to WorkspaceValidator.validate() in core instead?

We could. Preferably define it in the spec first and then implement it referring to it.

[bertsky]

Shouldn't we at least start an issue on core to support PAGE-related consistency in WorkspaceValidator.validate() before closing here? The problem is that we might have to actually look at the GT data in order to get the consistency principle right in the details. See this comment.

[kba]

Sure. Closed it because I thought OCR-D/spec#82 would be the fix, but that's just the spec not implementation.

[kba]

Implemented in OCR-D/core#223