Re: Minute of telecon of 20 March 2007

I'm just finishing up the language/dialects extension. This means that 
witin the DRL the predicates, return values, evals and consequences can 
use any pluggeable language; we will have initially implementations for 
MVEL and Java. I'm also just finishing off the Clips driver, showing 
that you can use DRL+dialects or a completely different rule engine 
language. We could probably work on some MVEL extensions with you for 
opaque and non-opaque actions.

Mark
Adrian GIURCA wrote:
> We can do that with R2ML 
> <http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=R2ML>. This is a 
> rule language of REWERSE  <http://www.rewerse.net> Rule Markup Working 
> Group <http://oxygen.informatik.tu-cottbus.de/rewerse-i1/>.
> Actually we translate R2ML into JBoss 
> <http://oxygen.informatik.tu-cottbus.de/translator/R2MLtoJBossRules/> 
> but a limited inverse translator will be available soon.
> The limitation concerns with free Java code which is allowed by JBoss 
> Rules. Actually we have support just for a limited number and type of 
> actions.
> -Adrian
>
> Mark Proctor wrote:
>> The example rules (attached in email) for MISMO where done by me in 
>> the JBoss Rules format, but it should be easy for anyone to follow, 
>> it's simple propositional logic. I'm hoping to hear back from Said 
>> Tabet on a RuleML translation, as I'm going to hook up a limited 
>> RuleML driver for JBoss Rules for the purposes of a RuleML/Mismo 
>> demo, I can do the same for RIF, if someone can show me the XML that 
>> will work in a production rule system . I have advised them against 
>> using a vendor rule format, including jboss rules, and instead to use 
>> RuleML or Clips, both of which will eventually have a migration path 
>> to RIF.
>>
>> Mark
>> Francois Bry (Bry-Haußer) wrote:
>
>