Skip to content

Update reasoning.md #628

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.

Sign up for GitHub

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

Merged
bnouwt merged 1 commit into from
Mar 11, 2025
Merged

Update reasoning.md #628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/docs/reasoning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ From these example it becomes clear that a reasoner can also be used to orchestr

The reasoning mentioned in this section works by using the graph patterns defined in the knowledge interactions from all smart connectors in the network. Additionally, the reasoner of a smart connector can also work with domain knowledge that is not tied to knowledge interactions. This domain knowledge can be loaded into a smart connector and typically consists of domain rules and facts.

The KE reasoner only works with `eu.knowledge.engine.reasoner.Rule` objects, so both domain facts and rules should be encoded as rules. There are two ways in which domain facts can be represented as rules: 1) as rules with only a consequent (and no antecedent) that represents the actual triple (without variables), or 2) as a rule with only a consequent (without antecedent) of the form `?s ?o ?o` which functions as a source for multiple or all domain facts.
The KE reasoner only works with `eu.knowledge.engine.reasoner.Rule` objects, so both domain facts and rules should be encoded as rules. There are two ways in which domain facts can be represented as rules: 1) as rules with only a consequent (and no antecedent) that represents the actual triple (without variables), or 2) as a rule with only a consequent (without antecedent) of the form `?s ?p ?o` which functions as a source for multiple or all domain facts.

It is possible to load domain knowledge (i.e. facts and rules) from a file or string by using [Apache Jena Rules](https://jena.apache.org/documentation/inference/#RULEsyntax). This format allows both facts and rules to reside in the same file and the `eu.knowledge.engine.reasoner.util.JenaRules` class provides some methods to create/load these files. A very simple example of a fact and rule in the Apache Jena Rules syntax is:

Expand Down Expand Up @@ -284,4 +284,4 @@ Any **proactive** Knowledge Interaction (i.e. ASK and POST) that you trigger in
## Performance warning
When using large graph patterns and/or many bindings, the reasoner's time and memory consumption doesn't scale very well.
In those cases, you may experience out-of-memory issues, or very long processing times.
For this reason, it is advised to only use the reasoner with small graph patterns.
For this reason, it is advised to only use the reasoner with small graph patterns.