IBM said that it will pay approximately €10 (US$15.74) per share of Ilog, for a total of €215 million ($338 million) in a transaction described as "concurrent cash public tender offers".
IBM said in its announcement that holders of about 10% of Ilog's shares have already agreed to sell them to IBM.
IBM's offer amounts to about a 37% premium over Ilog's July 25 closing price of €7.32 ($11.52). The exact acquisition price will depend on the exchange rate when the deal is settled.
The Rule Interchange Format Working Group has produced six documents which are now frozen before publication:
- RIF Framework for Logic Dialects
- RIF Basic Logic Dialect
- RIF Production Rule Dialect
- RIF Use Cases and Requirements
- RIF Data Types and Built-Ins 1.0
- RIF RDF and OWL Compatibility
Interested people should read them and comment on the mailing list
Jena deals with data sources represented in RDF(S) and OWL. Both of these languages provide an XML syntax. However, Jena Rules provides just a textual syntax for the rules.
The question is: Should Jena Rules have an XML Syntax?
We are waiting for the next stable version of JBoss Rules (v.4.0), which promises to offer a full access to all features already implemented in JBoss Rules 4.0 Milestone Release 2. These features convert JBoss Rules platform/rule engine into a reasonable, open-source alternative to other commercial products from the business market.
Looking to the RIF Core Working Draft it is easy to discover that one of the goals is to be as general as possible.
But is this an advantage of the language?
The Abstract syntax of positive conditions is done in ASN06 an object oriented syntax. Then another concrete syntax is written in an ENBF manner. Unfortunately it is neither explained which one is normative nor the mapping principles between them.
Two questions arise:
In November 2005 W3C set up a Rules Working Group. According with its charter document the group "is chartered to produce a core rule language plus extensions which together allow rules to be translated between rule languages and thus transferred between rule systems. The Working Group will have to balance the needs of a diverse community â€” including Business Rules and Semantic Web users â€” specifying extensions for which it can articulate a consensus design and which are sufficiently motivated by use cases."
The purpose of RIF is to be a markup language for rule interchange.
The Object Constraint Language (OCL) is originally a textual sublanguage of the Unified Modelling Language (UML). It can be used to express additional constraints on UML models that cannot be expressed, or are very difficult to express, with the graphical means provided by UML. OCL is based on first-order predicate logic but it uses a syntax similar to programming languages and closely related to the syntax of UML. It is, thus, more adequate for every-day modelling than pure first-order predicate logic.
Rules can be used in software applications to model and manage some parts of the application's business logic. They are best used in applications with a great deal of dynamic business logic i.e. applications where critical changes in the business logic are frequent and they need to be immediately reflected in the application's behavior.
This article describes the Rete algorithm as implemented by JBoss Rules. It was named ReteOO because it is an optimized version of Charles Forgy's original Rete algorithm, tailored for object-oriented forward-chaining systems. Two Rete Tree examples are provided for better understanding of the concepts.