W3C Workshop on Rule Languages for Interoperability Colleen - - PowerPoint PPT Presentation

w3c workshop on rule languages for interoperability
SMART_READER_LITE
LIVE PREVIEW

W3C Workshop on Rule Languages for Interoperability Colleen - - PowerPoint PPT Presentation

Apr 27,28 2005 W3C Workshop on Rule Languages for Interoperability Colleen McClintock (cmcclintock@ilog.com) 1 Christian de Sainte Marie (csma@ilog.fr) W3C Workshop on Rule Language Interoperability Business Rules and Product Rules


slide-1
SLIDE 1

1

Apr 27,28 2005

W3C Workshop on Rule Languages for Interoperability

Colleen McClintock (cmcclintock@ilog.com) Christian de Sainte Marie (csma@ilog.fr)

slide-2
SLIDE 2

2

W3C Workshop on Rule Language Interoperability

  • Business rules are highly specific and structured statements

that constrain some aspect of a business process or activity, and that control or influence its behavior.

  • Business rules execute some actions that enforce underlying

business policy.

  • Production rules are a convenient representation for most

business rules. Driver must be 21 or older If the driver in a car rental request is less then 21 years old Then reject the car rental request

Business Rules and Product Rules

slide-3
SLIDE 3

3

W3C Workshop on Rule Language Interoperability

  • Execution of Rules
  • Expressiveness of the Language
  • Usability and Adoptability of the Standard
  • Compatibility with Other Standards

Requirements for a Standard Rule Language

slide-4
SLIDE 4

4

W3C Workshop on Rule Language Interoperability

  • A standard rule language must be able to represent

rules in a way that is unambiguous with respect to execution.

  • Rules applied on the same data in two different

environments must produce identical results

  • 25 commercial products and 18 open source

products in the Java rule engine space

  • Forward-chaining RETE engines, decision tables,

decision trees, procedural engines… Execution

slide-5
SLIDE 5

5

W3C Workshop on Rule Language Interoperability

  • A standard rule language must be expressive

enough to represent most (if not all) of the rules allowed by the main business rule engines.

  • Rule authors should not be required to write rules

using the standard rule language

  • Condition part of rules must include: typed first
  • rder queries, with variable definition and binding,

and standard logical, arithmetical, and set theoretical operators

  • Action part of rules must include: assert, retract,

modify and execution of application specific functions Expressiveness

slide-6
SLIDE 6

6

W3C Workshop on Rule Language Interoperability

  • Mainstream business rule engines must implement

the standard

  • Translation from/to internal languages used by main

rule engines must be reasonably simple

  • XML-based format

Usability and Adoptability

slide-7
SLIDE 7

7

W3C Workshop on Rule Language Interoperability

  • OMG PRR – Modeling of business rules and

exchange of business rules between modeling tools and engines

  • JCP JSR-94 – standard API for acquiring and using

a rule engine

  • Compatible and convergent standards for modeling,

executing, and exchanging rules Compatibility

slide-8
SLIDE 8

8

W3C Workshop on Rule Language Interoperability

A Layered Architecture

APPLICATION VOCABULARY EXECUTION/ INFERENCE LOGICAL EXPRESSIONS Imports Imports Application-specific information models application-specific languages Unambiguous composition semantics languages specific to classes of rule/inference engines Uniform way of representing assertions

  • ne common language