Currently, the HashedNode class traps NoMethodError. This is necessary for patterns that use the :is_a? quantifier or do not specify a type. But if a type is explicitly specified, and the pattern contains a method that does not exist, then the Engine should throw the NoMethodError.

original LH ticket

This ticket has 0 attachment(s).

Investigate RuleML as a potential rule language for Ruleby. See http://www.ruleml.org .

I was originally going to use it, but opted instead to use an internal DSL. Now we are working on an external DSL and I think we should revisit RuleML.

original LH ticket

This ticket has 0 attachment(s).

The bridge node currently has to make an awkward check for the head atom. This needs to be changed so that the head atom is a special case.

original LH ticket

This ticket has 0 attachment(s).

The MatchResult class has some unneeded attributes and extra code. We need to clean this out.

original LH ticket

This ticket has 0 attachment(s).

The Fact.token value is not really necessary any more. The assert_fact method should have a retract_fact sibling in every occurrence.

original LH ticket

This ticket has 0 attachment(s).

Currently, Ruleby does not allow for parameters in method names. For example, the following is not allowed:

[m.get(:name) == ’Joe’]

This needs to be accepted in all syntaxes. Other cases where this is need include:

[m[:name] == ’Joe’]

The Atoms and Nodes are already prepared to accept the arguments. The only area of development needed is in the DSLs.

original LH ticket

This ticket has 0 attachment(s).

An ‘exists’ keyword in the DSL would represent an existential quantifier that checked for the existence of a a particular pattern in working memory. The rule would then be satisfied only once if that pattern is matched. This is as opposed to firing ‘for each’ by default.

original LH ticket

This ticket has 0 attachment(s).

Add a method to the Engine class that will allow the caller to enable some kind of tracing. This tracing will record what rules have been fired.

original LH ticket

This ticket has 0 attachment(s).

Create external DSL. Original DSL’s are internal and written in Ruby. To be able to store rules externally an external DSL is needed. This would allow for a lot of new functionality to be created, i.e. a BRMS.

original LH ticket

This ticket has 0 attachment(s).

The LHS of a rule should be able to chain methods. This would look something like:

rule [:m, m.foo.bar.value = 'hello'] do |v|
... end