-
Notifications
You must be signed in to change notification settings - Fork 18
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
Give pointers for forward/backward chaining #141
Comments
I did not describe that in my thesis, but you are right, it would be nice to have a document about that and we need to write one. In general: forward-rules are executed till we get the full answer to our query (starting from the facts), backward-rules are executed "on demand" when the body of a rule requires the information (in that sense starting from the query or the queries). But instead of an informal(and incomplete) text as the answer to your issue you deserve a document. I will bring that up in our next group meeting. |
I understand the general principle but
|
As far as I understand, forward rules are executed first; evaluating statements in their rule body (condition) may involve running backward rules. I.e., backward-chaining rules are executed purely "on-demand", when needed. But, @josd and @doerthe may shed more light here.
Then this rule will become part of the ruleset and will be executed as well. Try the example here:
Unsure what you mean. |
Hybrid reasoning
Rule dynamics
Rule scoping
|
This is how it works in EYE https://eyereasoner.github.io/eye/#architecture-and-design |
https://w3c.github.io/N3/spec/#n3rulechaining:
That is fair.
However, please provide some references to info about forward/backward chaining, in particular their sequencing/interaction.
eye
tests, can you give pointers?BTW change the last word "primer" -> "specification"
because the doc does start with "This document defines Notation 3"
The text was updated successfully, but these errors were encountered: