Closed s-minoo closed 4 months ago
When using join expressions, ShExML engine produces inconsistent results based on the ordering of the expressions used in A UNION B JOIN C.
I interpreted it as follows:
If yes, there are currently two issues with it:
A simple test case using a variation of the input from mappingChallenges/JoinChallenge.scala can reproduce the aforementioned issues.
mappingChallenges/JoinChallenge.scala
I have attached the input shexml files and screenshots of the respective problems:
1) file: errored_a_c_neq.txt screenshot:
2) file: A_ignored.txt screenshot:
This has been clarified with the introduction of a proper join mechanism in ShExML. The old join clause has been renamed to substituting.
Issue
When using join expressions, ShExML engine produces inconsistent results based on the ordering of the expressions used in A UNION B JOIN C.
I interpreted it as follows:
If yes, there are currently two issues with it:
A simple test case using a variation of the input from
mappingChallenges/JoinChallenge.scala
can reproduce the aforementioned issues.I have attached the input shexml files and screenshots of the respective problems:
1) file: errored_a_c_neq.txt screenshot:![image](https://github.com/herminiogg/ShExML/assets/13002966/06cf8807-4a17-4a37-a354-1292f417ad5c)
2) file: A_ignored.txt screenshot:![image](https://github.com/herminiogg/ShExML/assets/13002966/78d5827f-f4c1-4576-b4ce-4962b84e7eb5)