It seems that the syntax check in JessDE does not recognize the
set-current-module statement. All definitions following this statement
are still interpreted with whatever module was set before.
This behavior is different from running Jess. There the definitions are
treated as expected, meaning t
I think Felix Bachmann wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> It seems that the syntax check in JessDE does not recognize the
> set-current-module statement.
Indeed! Thanks for the report.
-
Ernest Friedman-Hill
Hello,
I'm faced with the following problem: we are just starting a project to
improve and monitor dynamically the quality of data in our reporting
system.
Ideally we would like a Data Quality module that:
1) can be used as a library to be called with specific checks when the
data is about to be v
Just a suggestion ...
So far in JessED when a file contains an error, then it seems that the
whole file is marked buggy and all references in all files referring to
the buggy file are marked as an error too, even if they don't depend on
something that has an error.
Here an example. Assume files
> 2) can scan a very large database trying to find exceptions
[alan]
The jess user contrib library:
http://herzberg.ca.sandia.gov/jess/user.shtml
has excellent framework written by Thomas Barnekow that you might want
to take a look at.
> 3) where the rules used to identify exceptions can be ent
I think Felix Bachmann wrote:
>
> Would it be possible to only mark something as an error if the dependent
> definition is wrong and not is something in the dependent file is wrong.
That's a good observation. Basically what JessDE does for dependencies
is call the moral equivalent of "batch" on
CLIPS has the "import" and "export" statements that deal with this
issue. That might also be a solution.
Felix
[EMAIL PROTECTED] wrote:
I think Felix Bachmann wrote:
Would it be possible to only mark something as an error if the dependent
definition is wrong and not is something in the dependent
