Currently when multiple sessions get executed PROLOG doesn't differentiate between information found in the sessions. This is important because the historic information should be used by next sessions.
Solution
Only see information found in the scans from the current session as valid information. This could be done by checking the scans from the current session and checking if the information comes from a recent scan. To do this issue #15 needs to be solved first. Once the information can have multiple scans a check needs to be done what scans have been executed in this session. To do this the executed/2 predicate can be used to check if the command has been executed in this session or not.
This could lead to performance issues with big ontologies.
Problem
Currently when multiple sessions get executed PROLOG doesn't differentiate between information found in the sessions. This is important because the historic information should be used by next sessions.
Solution
Only see information found in the scans from the current session as valid information. This could be done by checking the scans from the current session and checking if the information comes from a recent scan. To do this issue #15 needs to be solved first. Once the information can have multiple scans a check needs to be done what scans have been executed in this session. To do this the executed/2 predicate can be used to check if the command has been executed in this session or not.
This could lead to performance issues with big ontologies.