I note that in the SHACL AF spec (2021) it states, with regard to the use of sh:order:
*Note that this algorithm only covers a single "iteration" over all rules, without prescribing the behavior if the same rule needs to be applied multiple times after other rules have fired.* My question is, how does TBC handle rule order during iterative reasoning? Let's suppose I have a set of rules I want to run iteratively to completion, and after that, run a second set of rules iteratively to completion. Back in the SPIN days, I defined "waves" to accomplish this. Any advice? Steve -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAGUep85C7L4LxQnTp9h%3D6rS3SWUVxQC4yNnKxUx9%3D25cBomjjQ%40mail.gmail.com.
