Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error reporting for txt-1 #141

Closed
ewoutkramer opened this issue Oct 10, 2022 · 0 comments · Fixed by #181
Closed

Improve error reporting for txt-1 #141

ewoutkramer opened this issue Oct 10, 2022 · 0 comments · Fixed by #181
Assignees

Comments

@ewoutkramer
Copy link
Member

For most invariants, the StructureDefinition contains enough details in the human-readable string for such an invariant to make clear why the invariant failed ("min should be smaller than max" type descriptions). For txt-1 this is not the case: to validate txt-1, we run an XSD validator, which will return the exact reason why a given piece of Narrative is not valid. However, currently we will just return the fixed text provided with txt-1, which means we will just say something along the lines of "XML for narrative is not valid". For large bits of narrative (think documents), this means it is practically impossible to understand why the narrative fails validation.

To improve this, we should output the results of the XSD validator component, in addition to the fixed human readable text for the txt-1 invariant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants