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

[schematron-pure] universalTests2.sch results in to many assertion messages #152

Closed
Katzor opened this issue Jun 7, 2023 · 4 comments
Closed

Comments

@Katzor
Copy link

Katzor commented Jun 7, 2023

ph-schematron-testfiles; external/test-sch/universalTests2.sch; external/test-xml/valid03.xml

In universalTests2.sch it says: "The result of running this should be four assertion messages: U7, U8, U9, and U10 only."

schematron-sch results in these four assertion messages.

schematron-pure results in 8 assertion messages:

U5: This assertion should never succeed because the rule should never fire.
U6: This report should never succeed because the rule should never fire.
U7: This assertion should always fail.
U8: This report should always succeed.
U9: This assertion should always fail.
U10: This report should always succeed.
U11: This assertion should never succeed because the rule should never fire.
U12: This report should never succeeed because the rule should never fire.

@pigelvy
Copy link

pigelvy commented Jun 7, 2023

This is probably a duplicate of #84

@phax
Copy link
Owner

phax commented Jun 7, 2023

Yes indeed it's a duplicate of this issue. The reason is the different resolution model in pure - it does NOT follow the "XSLT way" by visiting each element just once. Instead it behaves like each rule is independent from the pattern it is used in.

Maybe we should really define a separate query binding "java-pure" to solve all these incompatibilities...

Copy link

stale bot commented Jan 7, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 7, 2024
@phax phax added pinned and removed wontfix labels Jan 8, 2024
@phax phax removed the pinned label Feb 15, 2024
@phax
Copy link
Owner

phax commented Feb 15, 2024

I am closing this as a duplicate of #84 - however they are still linked, so we're not losing anything

@phax phax closed this as completed Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants