- #ORF09 An introduction to the RETE algorithm
- #ORF09 Playing With the Rules Presentation
- #ORF09 Rule Patterns and Features Presentation
- #ORF09 Early Alert System Presentation
- #ORF09 Engineer’s perspective on Rule Technology Keynote
- #ORF09 Enterprise Architecture Presentation
- #ORF09 Enterprise Architecture Presentation Part II
- #ORF09 Model Driven Approach for BRMS Presentation
- #ORF09 Production Rule Systems
- #ORF09 Graph Based Knowledge Bases and Rules Presentation
- #ORF09 Truth versus Useful Lies Presentation
- #ORF09 Automated Verification of rules Presentation
- #ORF09 Agile Business Rule Development Presentation
- #ORF09 Rule Classification First Presentation
- #ORF09 Rule Violation and Over-Constrained Problems Presentation
- #ORF09 Generating Rules from UML presentation
- #ORF09 What’s Different about Rules in CEP Presentation
- #ORF09 Measuring your Rules’ KPI Presentation
- #ORF09 Designing a System of Rule Based Agents Presentation
- #ORF09 Extending General Purpose Engines Presentation
- #ORF09 Programming Rules using a spreadsheet interface
- #ORF09 Practical and Modern RBE Presentation
- #ORF09 Temporal Reasoning Presentation
- #ORF09 Business Rules in the Cloud Presentation
- #ORF09 October Rules Fest Think Tank
- #ORF09 October Rules Fest Think Tank – Part II
- #ORF09 CLIPS implementation of RETE Presentation
- #ORF09 Complex Event Processing Models Presentation
- #ORF09 Distributed Programming with Agents Presentation
- #ORF09 making Parallelism Available to Rule Developers Presentation
Luke Voss was presenting on how over time he was struggling on how to represent his knowledge for computers to use.
He recently worked on what he called a “toy rule engine” in which he uses relationships between facts, not just pure facts. So the rule engine uses 2 “fact” bases, the facts and the relationships.
His representation was then presented in a graph and he tells us that Graph Theory can be leveraged to give him some of the tools he needed to deal with the data when it is structured in such a way. But now how can you use this with a rule engine?
So he turned to pattern match for structural matching and also worked with helpers so that you could use a visual pattern designer to express your pattern matching statements. This is used to generate some code.
For exploring, he uses a sub-graph query viewer, working on the unstructured data set as well as a local navigation explorer to explore the data that you have available.
He then covered some of the theory behind dealing with graphs.
He closed his presentation saying that to him, it is easier to deal with visual models rather than text models. He is thinking that there is a relative closeness between rule applications and routing problems. He also sees opportunities to extend the rule engine language for joins by inject information. He is in tune with Mark Procter’s vision of some of the features that might come in future versions of rule engines.
Tags: Business Rules, Conferences, ORF09