Ruleby - All

Wiki - Ruleby

Sun, 03 Aug 2008 19:24:51 GMT

Ruleby is a rule engine written in the Ruby language. It is a system for executing a set of IF-THEN statements known as production rules. These rules are matched to objects using the forward chaining Rete algorithm. Ruleby provides an internal Domain Specific Language (DSL) for building the productions that make up a Ruleby program.

If you are just getting started, take a look at the “Quic…

Wiki - Quick Start

Mon, 23 Jun 2008 20:15:37 GMT

This page provides a brief tutorial on how to get up and running with Ruleby.

First, make sure you have Ruby installed.

Installing the Gem

Download the Ruleby Gem from RubyForge, and install the Gem with the following command

gem install ruleby

Downloading the Source

Install an Git, and enter the following command

git clone git://github.com/mattup/ruleby.git

...

Wiki - Ferrari

Sun, 09 Dec 2007 01:33:04 GMT

Ferrari is one of the syntaxes in The Ruleby DSL. It defines four parameters for the ‘rule’ method:

An optional Symbol that is a unique identifier for the rule
An optional Hash that contains rule attributes (such as priority)
A variable number of Arrays representing patterns (the “left hand side”)
A block that will be executed if the rule is satisfied (the “right hand sid…

Wiki - Le Tigre

Sun, 09 Dec 2007 01:31:59 GMT

Le Tigre is one of the syntaxes in The Ruleby DSL. It defines four parameters for the rule method:

An optional Symbol that is a unique identifier for the rule
An optional Hash that contains rule attribute (such as priority)
A variable number of Strings representing patterns (the “left hand side”)
A block that will be executed if the rule is satisfied (the “right hand side…

Wiki - Interface Description

Sun, 09 Dec 2007 01:30:35 GMT

Ruleby provides a pure Ruby Domain Specific Language (DSL) for defining rules, and asserting facts to the system. This interface takes advantage of the language features in Ruby that make it a good base for creating DSLs.

The following figure is an example of a Ruleby rule.

rule [m.status == :HELLO] do |v|
  puts v[:m].message
end

In this example, the left hand side of the prod…

Wiki - Benchmarks

Fri, 21 Sep 2007 20:12:59 GMT

Miss Manners

Ruleby supports the standard “Miss Manners” rule engine benchmark. This performance test, as described in Effects of Database Size on Rule System Performance: Five Case Studies [PDF], uses a depth-first search to determine the alternating seating arrangements of males and females with one common hobby.

Disclaimer

Miss M…

Blog post - A DSL can change the way you think

Mon, 03 Sep 2007 14:30:42 GMT

A domain specific language (DSL) is often nothing more than a clever API. But in many cases, a DSL redefines how a programmer thinks about a program. That is the goal in the Ruleby project. Ruleby is a rule engine written entirely in Ruby. As such, it supports a DSL that is based on the Ruby language. This DSL gives programmers the ability to think about “what” a program is going to do, rather …

Blog post - Ruleby: the Rule Engine for Ruby

Mon, 03 Sep 2007 14:25:31 GMT

Good programming depends on selecting the right tool for the job. In most cases imperative languages like Ruby, Java and C++ are good solutions. But they are not perfect. This article will present some of these cases and introduce a new tool that improves one imperative language: Ruby.

Lessons from Dijkstra

Imperative programming often results in complex code with a myriad of state tran…

Wiki - The Ruleby DSL

Sun, 02 Sep 2007 22:41:43 GMT

All rules in Ruleby are created using the ‘rule’ method. This method is dynamic in that the arguments it takes can vary. It accepts three different syntaxes, and will detect which is being used when it is invoked.

The three syntaxes are:

Ferrari (Array based)
Le Tigre (String based)
Blue Steel (Block based)

It is important to note that most rule engines do not consi…

Wiki - Technical Description

Tue, 28 Aug 2007 18:52:04 GMT

Rules

Each rule in a Ruleby program is made up of a pattern, and an action. The pattern is the left hand side (LHS) of the if-then production, and the action is the right hand side (RHS).

The pattern (LHS) is actually made up of one or more sub-patterns. Each pattern either checks that an object exists in working memory, or that an object does not exist in working memory. If there are m…